Andrew luecke

Depends on the cause, priority and the impact of the bug.

Just more info on this. Basically, the primary controller does all the processing of the automation stuff. The rest are basically zombie units for io or interfaces I normally recommend core as a minimum unless you've got a very specific usecase

The fact it is taking Snap so long, should suggest though, its more politics at play tbh. As well as the lack of other devices with proper support

There are so many reposts of this topic now, I'm not going to repeat the arguments. Look at the following thread for starters But just to summerise, if you speak to ANY developer, they'll tell you that how Apple portrays themselves on stage is very different to the realities of dealing with Apple, and there is so much politics in the background, don't be surprised if its the case here. Control4 have an extremely talented team of programmers, so imho, its not because they can't do it

The advanced driver has advanced in the name

Try using the Advanced Camera and NVR drivers instead.. They're a huge upgrade and are the way forward (and they automate a lot of things)

G'day, Which version of the driver are you using? Justin I believe fixed this in: 20220307 - 07-MAR-2022. That being said, I assume this is with the standard driver? We now have an "advanced" camera and NVR driver which is part of the same driver license which is a complete rewrite and designed to be easier to troubleshoot. Alternatively, I would recommend testing the advanced drivers too (if you have a licenced copy of the normal Hikvision drivers, Advanced is a free upgrade as part of it, and your dealer simply needs to backup the project, delete the existing devices and swap with the advanced devices). If you are running a version newer than 20220307 in the camera drivers, we recommend your dealer submits a helpdesk ticket: https://chowmain.software/for-integrators/technical-support . Andy

I could be wrong, but I'd expect the behavior between pro and home to be the same.

Major versions need to be at least the version of the system.. So, For OS 3.3.0, you need at least Composer 3.3.0 (at least with Pro). So you'd need HE 3.4.1 or later. The main improvement is that Composer can be a newer version and work with an older controller though

Control4 are working on a fix

What drivers are you using? I am aware of a few that definitely cause issues

G'day, Just some updated info. ELK have identified an issue which may cause an issue on some systems (particularly with our driver). We've only seen it on 2 or 3 systems so far personally. We can provide affected dealers with updated firmware that should fix it. We've been trying to track this one down for weeks / months But it happens during some operations, and causes a loop where the driver keeps reconnecting on our stable driver (or the betas). In the latest beta of our driver though, even when the firmware issue is triggered, it no longer reconnects, but Display Diagnostics now detects when the issue has occurred. Andy

Just an additional note on the HC800, it supports OS3.3.0, but there were major improvements to the lighting in OS3.3.1-OS3.3.2, so if you're using colorwheels in particular, you still want to upgrade that controller anyway, even if the driver does technically support 3.3

Do it properly imho if its residential.. Configurable keypad, and properly zone the system.. The configurable keypad can stop the music

G'day, The driver can be downloaded direct from our website: https://chowmain.software/drivers/control4-blustream-cm100

Price has been Dropped

In that case, yes. In OS3.3.0, log to file may trigger a lua error in some drivers due to the new restrictions. Turning it off will prevent the error from happening. Andy

Turn off DEBUG, Log to File.. Only print

Could be anything.. Someone will likely need to log into your system

This is still available

I actually am in the process of selling my Mac. They're heavily hyped I wouldn't expect a Mac version of composer tbh.

I haven't used that product, but could be a few other reasons. 1. Latency issues on the controller caused by improperly designed drivers 2. Overloaded controller 3. Or as others have said, maybe incorrect ir placement 4. Old driver version, or really old control4 OS 5. Shonky network

Take a look at Blustream. They're awesome products: https://www.blustream.co.uk/converters When I was an installer (even before working at Chowmain), we used a lot of their products onsite

That error isn't actually sent by the panel. It's something defined in the code

The non Roku tcls can't be supported well, last I tested (I tried writing a driver a few years ago, and there were command limitations at the time). And you're better off with a seperate device honestly most of the time