Andrew luecke

I just got that too. I use it all the time.. However, honestly, this arrangement with Amazon never made sense, and it's probable that Microsoft are going to use their own store instead or work with Google

You'd have to be more specific than network crashes..I'd start by loading a Linux live cd, and seeing what happens. Check also your network settings are set to dynamic IP. If you're running 3rd party av, Get rid of it (it could be doing stupid things). Etc There isn't enough information happening here.

Yep. Using outlets directly as lights was simply designed for convenience and was added after the initial design to speed up deployment as requested by installers. And it won't work for all outlet devices either. Auto setup will provision it as Outlets instead by default, and you can use the Auto-Setup Outlet Lights to link the lights. This is the recommended way (explicitly for energy monitoring). The lighting driver would be too complicated if I added the energy code too (the TPLink code is already fairly complicated, which is why it's taking so long to add new presets support). Andy

As @msgreenf said.. Also, whilst it might not break things in this case, DO NOT CHANGE THE Light Category! That does something different than you think it does (ie, it affects the communications, not the icon or anything else)

Gday sorry, what are you driver names for both types of driver. Don't delete any drivers.. they might be there for a reason Workaround for power State is because tplink reports old power information when polled for a short time after setting the power from c4. So we assume it's wrong for 5s. If you change that, in some circumstances the power State might be wrong. Don't change that unless chowmain tech support tells you, or power status flicks to the wrong state temporarily after being changed from c4 Don't select device from list. That's used for auto provisioning and is used to change the device it's connected to, and even then, we don't recommend using it unless you're changing it to a device with similar specs. If you select that, you might even break things. You should only ever generally use that once (and it has probably already been used)

You can in some cases (ie, noise on the outputs etc). In this case though, the important part is actually the fact one of them is HC800, and there are SO many advantages of upgrading regardless at this time which aren't even related to the audio/ I think the Core also has more sound configuration on its outputs too (but, its been a while since I've used EA). They're just simply a better unit overall (including audio), and if we're talking Drivers, the performance difference is HUGELY noticeable (to the point that our really intensive driver is set to automatically speed up communications on Core/CA10). And thats probably the bigger factor honestly. During inhouse benchmarks, the Core series is MUCH faster. And thats a good reason to update imho regardless

Honestly.. Not sure you'd notice the difference between them. Different products can sound different. But, there isn't enough distortion in any of them in my opinion, for the sound to appear bad (which is the real factor). But at the end of the day, EA might be a tiny bit noticeably better theoretically than HC800.. And more Core might sound better. But none of these products sound bad (at least to my ears)

We do have support for some manufacturers.. But yeah, unlikely these will be supported for a while. I use various products at home, but my bedroom uses Wiz at the moment (internationally, that's probably the closest to something like Hue).. It can be combined with Chowmain Light Group for Group lighting too All paid Chowmain Lighting drivers which are still being sold support ColorWheel

No Tuya driver available anymore (we only support certain manufacturers now). My recommendation would be return them and get something else (internationally, Wiz is a good option and integrates well). In US, there are lots of good options

Also, not sure what you mean by subscription? Control4 doesn't require a subscription in your case unless you want Intercom anywhere, or When/then

Are you using a generator? Lighting problems really aren't that common honestly. Most of the time I see them, it's even caused by the lights themselves exceeding the max wattage or other problems.

In summary.. Get Shelly Plus/Pro modules which support Blinds.. They're awesome And use the Chowmain shelly driver

The blind code also got a major update yesterday too for people not using calibrated blinds (which works best for plus / pro / gen3 modules)

Whilst Composer HE is popular amongst C4 Forum users, there are actually limited people using it in the general population (especially since the introduction of When/Then, which will only grow in popularity). When I was an installer, we only had 1 customer using it at all. Ideally, we aimed to put endusers in a position it wasn't required with the use of other drivers, and the person who did buy it, mainly purchased it because he wanted to mess around with it (he didn't have any actual usecase) That being said, Control4 has a long list of bugs they fix (every product does) constantly, and the list would be something that needs updates on a daily basis (furthermore, there are always invalid bugs, lower priority ones, or ones with easy workarounds). Furthermore, this bug only affected OS 3.4.1 users. So in practice, it's not something many installers would encounter at all, unless they're monitoring these forums. In fact, I can certainly think of issues which are far more prominent than this one, but still not common (I think all were fixed) The only other time I recall people had issues with Composer, was with Apple Silicon/Microsoft ARM, and that was Apple's/Microsofts fault. Otherwise, we sometimes see issues with AV and routers and such As Ryan mentioned, very few people are using Composer HE, and even less are using it regularly. Because Pro and He are so similar, one would also normally assume since Pro was working, that HE would too, and my first assumption as an installer would have been something wrong with the customer computer at first, until more investigation was performed I only know about this fault because of C4Forums personally (it's not being mentioned at all really in C4 Facebook pages, or other places). And it's not an issue that affects many people (so I doubt C4 even got many calls about it)

G'day Guys, We've pushed an updated driver today for this as well as Shelly and Govee 1. Even more performance works to reduce system latency overall. Especially with Debugging enabled, worst-case benchmarks showed a CPU processing time drop from 6.6s to 0.06s for 10000 log entries (28x-100x speedup). Other benchmarks showed a 9-22ms improvement for certain operations (which in some circumstances may have appeared to be a random CPU spike every so often). Either way, even lower end controllers should operate better now 2. Scenes will work correctly now on CCT Only Wiz lights (in this case, there were no reports, but a few people using certain lights were reporting some random issues that maybe related) 3. You can now see diagnostics for ALL Wiz drivers in one click 4. Huge new Diagnostics tools, which not only identify more potential issues with our drivers, but, also if your Control4 Controller might be experiencing certain issues 5. Improvements to commands to improve light latency. This only affects some people however Andy

G'day Guys, We've pushed an updated driver today for this as well 1. Even more performance works to reduce system latency overall. Especially with Debugging enabled, worst-case benchmarks showed a CPU processing time drop from 6.6s to 0.06s for 10000 log entries (28x-100x speedup). Other benchmarks showed a 9-22ms drop in time for certain operations (which in some circumstances may have appeared to be a CPU spike). 2. Scenes will work correctly now on CCT Only Govee lights 3. You can now see diagnostics for ALL Govee drivers in one click 4. Huge new Diagnostics tools, which not only identify more potential issues with our drivers, but, also if your Control4 Controller might be experiencing certain issues Andy

G'day Guys, We've pushed an updated driver today that mainly: 1. Greatly improves handling of Toggle blinds in Shelly (when you're not using the slider). Let us know if you have any issues with the new behavior. The Gen 2+/Plus/Pro devices in particular should be a much better experience (and will now actively show the moving / stopped state correctly, but you MUST have new enough firmware). The Gen 1 should improve the feedback too, so at least you know which direction the blind is moving in (but not if it's moving or not really) 2. Even more performance works to reduce system latency overall. Especially with Debugging enabled, worst-case benchmarks showed an improvement of 6.6s to 0.06s processing time for 10000 log entries (28x-100x speedup). Other benchmarks showed a 9-22ms drop in time for certain operations (which in some circumstances may have appeared to be a CPU spike). 3. Scenes will work correctly now on CCT Only lights like the Shelly Duo (which may have had issues) 4. You can now see diagnostics for ALL Shelly drivers in one click 5. Huge new Diagnostics tools, which not only identify more potential issues with our drivers, but, also if your Control4 Controller might be experiencing certain issues Full Changelog is below Andy https://chowmain.software/drivers/control4-shelly-generic#revisions Version 20240217 - 2024-FEB-17 [Feature] New Support for Blind Levels in Toggle mode on Gen 2/Gen 3 devices. Now allows Stopping on these devices (Blind, ModuleNG, Module) [Feature] Improve support for Blind Levels in Toggle Mode on Gen 1. We can't identify the position, but we can make it better (Blind, Module, ModuleNG) [Feature] Add Extended Diagnostics Support (All) [Bug] CCT during Scenes was being incorrectly changed to the equivalent RGB (but the equivalent). This also broke scenes on old Duo CCT lights (Light V2) - Thanks Paul Lang [Bug] Fix Minor Crash on Light which occurs after Controller reboot in some circumstances. We do not believe this affected the operation of the driver however (Light V2) [Performance] Speed up some certain operations by 9ms-22ms (or more). Particularly on large Shelly systems or slow controllers (such as a CA1), this may reduce CPU spikes, and in all cases, it will improve latency further (All) [Usability] Show Brightness Property on On/Off Lights (Light V2) [Troubleshooting] Major new Diagnostics. Some Diagnostics take 24hrs to become fully active (All) [Troubleshooting] New Action. "Display All Related Diagnostics". This provides Diagnostics for all Shelly Devices/Drivers in Project (All) [Performance] When Debugging is enabled, Up to 28x-100x speedup in logging performance improvement in some benchmarks of 10000 logs (ie, 6631ms vs 60ms in the best case). [Performance] Print and Cloud Debugging will switch to cloud only after 24hrs automatically.

G'day, The HC250 was already out of date if installed in 2017, because the replacement (EA1) was actually released early 2016. HC250 was originally released in 2012 I'd try powering it down and ensuring things like lighting are still working before proceeding with anything. If they are, then it's just a matter of choosing what system you want to install. There are lots of options (like VSSL, Musiccast, Sonos, HEOS)

Super common story. Honestly, in lots of older homes they purposely dump outdated equipment there as a selling point, and the HC250 was EOL years ago That being said, you could still use it though. You'll need to speak to an installer (probably an onsite one in this case) unfortunately. They're like a computer, so they could be set up to do anything. And it might not even be plugged into the internet. In a lot of cases though, if they've left the controller there, sometimes it's also for more than audio, but lighting too (so keep that in mind)

bump

HC250 can go straight in the bin.. At chowmain our drivers still mostly support 2.10.X (theoretically, except our new ones), but, without OS3, nobody should be installing HC250's anymore unless they want problems. The cost of labor for OS2.10 was also significantly higher, because drivers like our shelly driver wouldn't have been able to self setup HC800 MAYBE, but nobody should be installing these either.. They only run OS3.3.0 max, so they're a dead product too. Our drivers will still support them, but because even OS3.3.1 added so many updates for the new color lighting stuff, even our os 3.3.0 drivers realistically need a newer OS then hc800 supports Core series absolutely slaughters the EA series (we've been doing a lot of performance work, and the performance often is double). HC is older. Friends don't let friends buy HC controllers though.. Unrelated, if you're using Chowmain drivers, you're going to notice a few performance improvements in all of our newer drivers rolling out, and our new Related diagnostics and Extended Diagnostics systems

Common mistake honestly. Easy one to make, and very few drivers are using extras for lighting either

Make sure all of your mobile devices use a email login (don't use 1 login for all devices). If you can't set an alarm, speak to your installer, they probably have to add the wake/sleep agent and configure it (I don't think its added by default). In regards to adding music services, your installer needs to have the Manage Music driver set to unhidden in various rooms. But this will only work if you're using Control4 for Audio. Depending on your needs, your installer might have installed something different (like VSSL or Sonos), which doesn't support that functionality

G'day, I was the developer who wrote V2. @alanchow wrote the original Chowmain V1 driver actually (which I basically enhanced and upgraded to support the OS3.3 colorwheel). The color wheel is the old style, and it is now a color bar instead. We haven't updated the documentation as its recent (but they're equivalent.. Color Bar is the new style). So basically, when lights don't have detectable Effect Support, we turn off the extras link. The other KL Series did support Effects / extras though (provided they are detected as LightStrip), so I suspect this should, but its also possible that it doesn't have a known mechanism for effects in the API.. Make sure you hold your finger down on the light, and Extras should pop up as an option. It should be mostly automatic though

You probably have Zigbee issues and something may have been disconnected or similar Worth noting the NEEO and Halo now are actually Wifi based, and thats a huge benefit if you're using a good Wifi network (but wifi likely consumes more power). As a bonus for Wifi remotes, most homes generally have full Wifi coverage, whereas, most homes have limited Zigbee