rea

Even from OS3.0, to OS3.4, the changes have been absolutely massive under the hood too. We're talking absolutely epic changes which people take for granted these days until they try an older driver. Features like:
Our drivers can add their own drivers now (so, AutoSetup in our Shelly driver as an example or almost all of our light drivers). In the past, you would have had to have added every driver manually. A Shelly job which these days takes 5mins to provision would have taken potentially an hour in the past or longer Native ColorWheel Custom Interfaces for drivers (which we use for Contact us and the Chowmain scheduler driver). And a huge amount of stuff that we use in the backend for troubleshooting. Bunch of Camera stuff, etc. So things are still moving really quickly

It's a bug. It's being fixed currently 

I can say that it is awesome as well. It is very fast and its great to finally have video playback in the control4 app. The features at release are really great and they plan to keep improving it with more software features and updates. It is limited to 4 cameras, but for how fast it recognizes and positively identifies objects it's worth it. For the entire time I have had it false notifications have been really limited to challenging night scenes with multiple objects. So a person may have activated the event but because there is a car that is closer it might say it was the car that was the trigger rather than the person. Keep an eye on our patreon we will have a video showcasing its features and how to use and program it in control4 yourself with just composer home with limited involvement from a dealer.
https://www.patreon.com/waltstv

The driver is available and will be sold through Drivercentral.io shortly.  If anyone wants early access, please PM me

Its coming guys

I have not stopped on it and presently have. it in my home.  I need to integrate licensing and then it will be released.

Another vote for the Kasa outlets. I have several and they work great with C4 and have been very reliable. As mentioned above, being able to add new Kasa products in Composer HE without a dealer makes them even easier and effectively cheaper than most other options. Amazon routinely has great deals on multi-packs of the plugs too. 
Just be aware that TP-Link has two different lines of products on Amazon: Kasa and Tapo. Someone else may be able to confirm, but the driver seems to be specifically for the Kasa branded products (I've never tried any of the Tapo products). 

One of the best most useful 3rd party drivers out. Devices are inexpensive and the driver works flawlessly.


Sent from my iPhone using Tapatalk

funny 

Rachio iro. But why integrate? It's awesome on its own 

I personally only had 4 new support tickets this morning for the drivers I wrote/contributed to. My tickets were:
Feature request for LIFX (for a feature which most Automation platforms don't even support an option for) An implementation question about TRVs and boilers.  Integration issue between LIFX and Alexa (which is not a bug, but more a behavior) VLAN's and Wiz issue due to UDP broadcasts. At worst, its network, at best, they forgot to configure C4 for the correct broadcast range. In regards to phone calls
Had a call about Govee. Customer seems to have moved the lights to their own account, so the API key of course broke. Our Inbuilt diagnostics made this easy to diagnose.. TPLink call regarding outlets. It was mentioned to them we have a new driver, so they simply wanted to upgrade it to our 2nd generation driver. 
I'd personally expect a lot more tickets from dealers/end-users if there was "constant troubleshooting".  In fact, for drivers like Big Ass Fans V2, I've literally only received 1 issue on an existing system, ever...
There are a lot of systems using our drivers.. Based on my experience (and my previous experience as an installer), I'd have to totally disagree..  

While I agree 100% with the sentiment… I would say the percentages are a bit wrong… it would be the 0.1% who like to tweak and the 10% who get a poor dealer setup (my view - and this is not a dig at C4 or any of the dealers on this forum).  Admittedly many of the 10% won’t find their way here.

To extrapolate on what @msgreenf said: If you're using the same programming for multiple things, it is pretty easy to just copy and paste programming over in C4 HE. But, if 6 months from now you decide to change something in your programming, by using the macro you can just go into the macro programming and modify the programming. Everything that uses it changes. If you copy and paste to all your actions, you have to go into each action and edit your programming and it's pretty easy to forget some of the places you used said programming once it becomes automated. 
It's a similar rationale to creating advanced lighting scenes and programming against those instead of just having an action modify several lights individually in programming. 

Maybe consider a system like this for more reliability / accuracy?
https://www.networketi.com/snow-and-ice-melting-systems-control-pd-pro/
https://www.networketi.com/eti-snow-owl/
https://www.networketi.com/git-1-gutter-ice-sensor/

Whatever you do, I'd recommend coming up with something to automate/control better. I have heat cables as well and initially thought it was a great idea to have a thermostat controlled switch and, being a newbie to the mountains, I didn't realize it just stays cold where I live all the time during the winter and the heat cables ran basically all winter. After running through my electric bills, I bypassed the thermostat control and just put the heat cables on a manual controlled C4 switch that I have setup on a 4 hour run-timer that I turn on when it snows. My electric bill during the winter months is now half what it was. Those things draw a lot of power. 
I've thought about programming it against the weather app as well, but I've found that where I live the weather apps are generally not very representative of my actual weather--a few miles each way makes a big difference in the mountains. Just something to consider depending on where you live. 

Whatever you do, I'd recommend coming up with something to automate/control better. I have heat cables as well and initially thought it was a great idea to have a thermostat controlled switch and, being a newbie to the mountains, I didn't realize it just stays cold where I live all the time during the winter and the heat cables ran basically all winter. After running through my electric bills, I bypassed the thermostat control and just put the heat cables on a manual controlled C4 switch that I have setup on a 4 hour run-timer that I turn on when it snows. My electric bill during the winter months is now half what it was. Those things draw a lot of power. 
I've thought about programming it against the weather app as well, but I've found that where I live the weather apps are generally not very representative of my actual weather--a few miles each way makes a big difference in the mountains. Just something to consider depending on where you live. 

Whatever you do, I'd recommend coming up with something to automate/control better. I have heat cables as well and initially thought it was a great idea to have a thermostat controlled switch and, being a newbie to the mountains, I didn't realize it just stays cold where I live all the time during the winter and the heat cables ran basically all winter. After running through my electric bills, I bypassed the thermostat control and just put the heat cables on a manual controlled C4 switch that I have setup on a 4 hour run-timer that I turn on when it snows. My electric bill during the winter months is now half what it was. Those things draw a lot of power. 
I've thought about programming it against the weather app as well, but I've found that where I live the weather apps are generally not very representative of my actual weather--a few miles each way makes a big difference in the mountains. Just something to consider depending on where you live. 

I apologize for my negative comments about ari .  just wasn't a good fit.

I am sure there are many glamour pics out there but here is a few of mine
 

Good news everyone. 
Our new Major KASA update 20221222 (5 months worth of work) is now on driverCentral. 
This brings 4 major new enhancement, and many smaller ones 
MAJOR Performance improvements (which consumed 90% of the time). Systems which were previously running at 25% CPU load (with 40% CPU spikes) were tested in this new version as maintaining a CPU load which never increased beyond 10%. Many of these are optimisations we originally added to Shelly. For this reason alone, we recommend everyone upgrade (as your primary controller should also run a bit cooler too if you have a lot of lights) Improved responsiveness. Control from C4 is now faster than ever, and feels more responsive. Improved VLAN Discovery support for TPLink Agent More consistent latency across all drivers on Controller (we stagger the driver load). This generally only affects large TPLink systems running on overloaded controllers. Keep in mind, if you are operating buggy drivers with major latency issues (such as the ping driver), this code may not be effective, and you will have to fix the root cause of your issue. This code will generally only help if the controller is overloaded or in very large installs.   
Full changelog is below 
 
## Version 20221222 - 2022-DEC-22
This is a Major Performance release which changes some fundamental ways the driver works. On large installations running underpowered controllers, this update has been demonstrated to bring the system load down from 25% load (with 40%+ spikes) to less than 10% running stable whilst allowing long polling and reduced latency across the entire system. This release introduces some of the similar optimisations which we previously added to Shelly. We no longer require fast polling for this driver to work reliably. User experience is improved and the entire experience should appear faster overall
 
Some major changes are as follows:
- Bulk Adjust all Poll Rates at once. This is ideal to speed up the drivers, or slow them down as required. (Agent)
- Stagger Polling between drivers over 30s to reduce CPU spikes. Instead of trying to pull all of the drivers at once, this means drivers will be polled gradually over a period of 30s or more (Light / Outlet)
- Increase Default Auto Discovery Poll Rate (Agent V2)
- Drivers will no longer report back their device details to agents every packet. Only when their Mac Address changes. Less Processing is now required (All V2)
- Only update provisioning directory when a device changes (All V2)
- Track less information for Provisioning purposes. Generate it only as required (All V2)
- Only try to receive data from a device after requesting it. Previously, we were regularly checking if there was data (Light V2 / Outlet V2)
- Low-Level major Performance improvements thanks to improvements made by SnapAV in OS 3. When upgrading from an earlier version of the driver, the controller requires a reboot for these optimisations to take effect
- Commands on average will now execute 500ms faster and feel instantaneous due to connection system enhancements (Light V2 / Outlet V2)
- Upgrade to new generation documentation system (All)
- Commands now include Device name to facilitate management (Outlet / Light)
- Split Code Base to facilitate bug finding (Outlet / Light)
- Ability to adjust Energy poll rate, or disable entirely. Some people may want to turn off energy polling if it isn't being used to reduce system load (Outlet)
- Light Status not updating correctly when using light bound directly to "outlet" WITHOUT outlet in place (Light)
- Add Support for subnet masks which are different to 255.255.255.0. Useful for Discovery on VLANS (Agent) - Requested by multiple people
- Major improvements to the connection stack to improve handling
 
Thanks everyone for the assistance including (but not limited to):
- Trey Nolan
- Clint Watkins
- Mitch Greenfield
- Nicolai Landschultz @ IndigoZest
- Snap AV Team
- Chris @ Electronic Living
- Everyone who responded to our facebook thread regarding documentation
- Everyone else who requested features or assisted with testing
 

Its coming... been doing extensive testing to accommodate some of the nuances of SleepNumber and their platforms and random things.

Not reverse engineered.  Yes its via cloud as local control is via bluetooth only.
 
Working to get it up on driver central.
 
Updated version supports the following now:
Supports Multiple Sleep Number beds
Setting Base Left / Right to Presets
Setting Left / Right Sleep Number
Setting Position of Left/Right for Head / Foot
Setting Sleep Number for Left/Right Sleeper
Driver is 2 way supporting the following properties:
Left/Right Sleep Number
Left/Right Occupancy Sensor
Left/Right Head/Foot Position
 
 
The driver also raises events when occupancy of left / right change.
 
 
 
 
Still to come is management of foot heater and lighting for the bed.

Name and shame... 
RyanE

Andrew is a rock star! Pinpointed drivers that were slowing the system. Now deleted and problem solved. So the brain trust was 💯 right! Thanks to all 

Just an update.  This problem has been mostly solved now (removing other 3rd party drivers fixed the issues).