hank31980

This is an Android device so just running C4 App on it. Fully functional but Intercom only available in Portrait orientation, in Landscape functionality disappears. I think the C4 App checks Pixel count Wide and High to block Intercom. Pity because Landscape was my intention for this little device.

I have just received my little 5.5" Axion touchscreen, which on first inspection looks to be well constructed. First job was to hook it up to a Poe network cable for Power and Network. Then added the C4 OS3 APP and all looks good so far, the screen Autorotates depends on physical orientation Landscape/Portrait etc. so thats good and the Intercom seems to work fine. So so far all good.

I get that, but with the PCI I have currently (5500PCU), I wonder if there is a way to convert the USB port it has, to a Serial Port. Maybe I’ll try the CBUS forums for advice. thanks for reply anyway.

Hi there, I am definitely interested in this driver, as I have a couple of customers with Clipsal C-Bus lighting systems, who also have Control4 systems, but not yet hooked up. I have purchased a Clipsal PCI, but it has a USB port and I wonder if I should have bought the one with a 9 pin D-type serial connector as I’m not sure how to link the USB port of the PCI to a Control4 controller. can you help on this hardware question? hank31980

Hi there, I made my own IR based driver for the Sky Stream Pucks, see attached driver file regards David sky_stream_glass_puck.c4z

Same for me too. URL from Touchscreen is valid. Allows me to add Username & Password. Says it is successful, but when checking Status of Account says Logged Out. Going round and round in circles here.

Seeing the same issue with a HC-800 running 2.10.6 and Amazon Music Driver version 66. I'm not sure what is the cause, Amazon end or Control4 end but very frustrating! Would be interested to hear the fix. I have a second system with an EA-5 running OS3 (3.2.3) software and no issues with that, so I do wonder if its an OS2 issue?

I previously had the C4-16Zone Matrix & C4-8 Zone Amp108, but recently I switched to a Triad 8 Zone Matrix & Triad 8 Zone Amp. The previous Amplifier was controlled from a Relay output on my EA5 and had the Amps Status reported back via a Contact Input of the EA5 controller. I am not sure what cables or connections are required with this newer Triad Matrix/Amp? It looks like I need maybe a Mono or Stereo Jack cable to either link Matrix to Amp or do I just connect such a cable from Amp to Controller Relay Outputs/Input Contacts? Any info would be most welcome. I did look today on the PDF Install documentation, it looks like a 3.5mm Male Stereo Jack is required to link the Matrix 12v Trigger Output to the Amps 12v Trigger Input, but I am not exactly sure & so more info from someone to confirm what is required here would be great.

So, do you set a particular Steam URL in the Driver? Any particular Camera driver or doesn't matter?

So how do you direct the Video to the Touchscreen, using a IP Camera Video stream or something?

Hi Gary, I’ve bitten the bullet. I’ve upgraded my cherished HC800BL1 for a nice shiny new EA5. The History works now? Big deal I hear you say, but this is the only change I have made to my system, nothing new on router or network or anything, just controller and now it works. Not sure if there are like V1’s and V2’s of HC800 as like you History just didn’t work for me. Anyway I promised you an update, was going to install EA3, but gone full fat version EA5. Like most things though once you have it you probably won’t bother with it.

Ok great to know, thanks for info.

Thanks, is this a general streaming rule for Control4 or just a Spotify rule? Does this also apply to MyMusic, so am I limited to how many rooms I can navigate through My Music Digital Music?

Firstly, do you know if there is a Limit to how many Spotify Room Drivers can be added to a Residential Home project, I heard it may be 11, but not sure? Secndly if there is a limit, is it related to type of Controller used, ie EA-1, EA-3, EA-5 etc? Final question, if there is a limit, dos this equally apply to MyMusic and Sharebridge distribution throughout a project? Any advice welcome on this limit question.

Doorbell.wav file is the Audio that is being played, not sure if the type of format or size of sound file is the issue here? Is there any guide as to what works and what doesn't? It seems to work, as the sound file is being heard in every Audio Zone that is configured to receive it, but only with this hefty delay being added to the Announcement tself. So I get the C4-DS2 pinging its Doorbell sound, the T3 Touchscreens Intercom kicking in and ringing, then this big delay and eventually the Ceiling speakers make the Doorbell sound. So certainly better than no sound, but still not quite what I want. As a test, I guess I will switch the Amp to ignore the trigger therefore keeping it on and play around with this delay to see what I can get it down to.

Control4 Audio Matrix Switch (C4-16ZAMS-V3-B) with a Control4 8-Zone Amplifier (C4-AMP108) The C4-Amplifer is set to be Triggered on from one of the assigned Main Controller's Relay Outputs.

I get the Announcement to work every time, but I had to install an 8 second delay in the Announcement to the various configured rooms for it to be heard, otherwise if this delay was shorter you would start to hear a shorter/clipped version of the Doorbell and eventually if you reduced the delay further, then no sound, just the amp clicking ON and eventually timing out. I wondered whether to use the Motion sense of the Door station camera to at least trigger the Amp to fire up in advance or anticipation of a Call button being pressed. To achieve this I am not sure whether to use a Fake Relay within the programming so that the trigger for the amp might be manipulated from other means, not just the start of an Announcement. Director version: 3.2.1.592369-res

There is a minor Software update out for 3.2.1, but I think that deals with issues on T4's and in particular TT versions.

Basic things to do would be; Reset of Touch using top button on T3 screen Reboot/PowerCycle Controller

Hi Gary, I checked with a friend who also has a HC-800 running OS3.2.1 and he has History working. So now not sure if it is HC-800 hardware related?

Hi Gary, sorry for tardy reply, just seen this. Like you I also have my old favourite HC-800-BL1. This was upgraded recently from OS2.10.6 to OS3.2.1, however I have never seen the History agent working on my system and upgrading OS hasn't solved that. So I am guessing its an issue with the HC-800-BL1, but not exactly sure. The History Agent has been added my system for some time now, originally on OS2 and still n OS3. I can see the History experience button available from T3 touchscreens & App, but nothing ever shows, just a circular symbol whizzing around whilst checking, then it times out? When checking around my Navigators, I can see various Time & Date stamps associated with various Sensor and Relay activities but nothing ever shows on History. I do have a EA-3 lying around, so I may get this rigged up to see f this works or not. I don't yet have 4sight, so I was never sure if that was the limiting factor for my lack of History? David

My system runs from my old HC-800, which I've had since 2014, and I guess for past year or so its been running on 2.10.6.561784-res OS quite happily. This Zigbee identify issue is odd to me, because I have around 40 Zigbee devices distributed all around my house, and the only ZServer in the house is the HC-800, which is centrally located in the house. I don't have any trouble identifying the newer firmware models (02.01.02). For a while I did have other ZAPS provided by HC-250's behind each TV, but no one bothers to use the local Navigator anymore & Lighting all works well, so I had those HC-250's removed a short while back. My lighting is all Control4 lighting, via C4-KC's keypads, C4-KD's dimmers, C4-SW's switches, C4-APD's adaptive phase dimmers and C4-DM201-Z's puck dimmers. So initially when I tried to identify these older firmware Wireless Motion Sensors (02.00.08) in my Garage, as this is a little bit remote from my house and therefore is a simple setup. I tried all of the above steps to Reset the devices, clear them off the system, but all to no avail, the older firmware sensors would not identify? In the Garage, ZServer and ZAP were provided by the locally installed HC-250. This secondary controller controls the Garage Door operation, some music via a Garage Speaker Point & some simple lighting via C4-APD adaptive phase dimmer (Zigbee) and Puck Dimmer (Zigbee). Even with the Zigbee mesh operational in the garage, ie Controller & Lighting I could not get these older WMS10-ZP to identify in the Garage. However just to try something I added a Card Access WMS-10R "Relay module" . I did this for no other reason than to try something to see if another Card Access Zigbee device would identify. It identified no problem. Also after this Relay was added, it then allowed my to identify the Wireless Motion Sensor to the system. However when I removed the Wireless Relay the Zigbee path was broken for the Wireless Sensor and it never reconnected to the HC-250 or the C4-APD dimmer switch which controlled the light. So I have swapped out a newer Motion Sensor from the Main House to the Garage and this identified no problem, without the presence of a Wireless Relay module. Back in the Main House was the same problem. So here in the house the Zigbee mesh was provided now by the HC-800, and contained quite a lot of existing Zigbee devices, light Lighting Dimmers, Switches, Keypads, SR-260 remote controls, other Wireless Motion Sensors & a Zigbee to IR devices etc. But once again no luck with identifying, only with the presence of a WMS10R Relay Module would this work. No Identified I can see that after a few days, the Zigbee path has migrated to other devices, so in theory all is working, but I reckon if I Disconnect the WMS10-ZP and try & re-identify I'll be back to the same problem. Its a mystery, but even more mystifying is that no-one else seems to have suffered with this. Anyway, thanks for your comments so far.

I have these Zigbee Pro devices identified and working so I have no immediate problem. however if the Wireless Relay module is powered off or removed from the system then it seems that these 02.00.08 firmware devices will be Offline. they then refuse to re-identify to main controller HC-800 or secondary HC-250’s?

I tried all of the methods you suggested, 13X, 9X, I already did the battery boot up and press the button. None of these helped unfortunately. What I don't understand is that all of the 02.00.08 Motion Sensor devices have only identified via the Wireless relay WMS10-R device being present. The baffling thing is that physically there are several other Zigbee devices very nearby, literally 2m or 3m metres away. These are like Light Switches C4-SW120, Kepypads C4-KC120, Puck Dimmers C4-DM201-Z, etc. etc. Yet it ignores all of the other devices and only identifies and links via this Wireless Relay module. Whereas the newer Firmware siblings on 02.01.02, as expected find a Zigbee device more local to them. You can see the older devices clustering around the Wireless relay device.

Change to Ch 14 didn't solve unfortunately. So only the Sensors with the newer ver 02.01.02 will identify to the local Zigbee. The ver 02.00.08 just go through the motions of trying to identify but just timeout, so not sure if I can solve this as it looks like its part of the older Firmware version. They physically look exactly the same devices, no matter the firmware version, as they are all WMS10-2-ZP. However in my Garage, remote to the main house there is just a single HC-250 controller. Its function is just operating Garage Door Opening/Closing & the Zigbee Mesh just for SR-250, Light Switch V2, Puck Dimmer V2 & this troublesome Card Access Wireless Sensor.