This is a Hubitat architecture issue, not really a driver issue. There's not really much I can do about it. There's nothing at all in the driver that imposes any sort of switching delay. The Hubitat is just um... not fast at dealing with large numbers of LAN devices, especially UDP and Websockets based devices.
(FWIW, Hubitat people -- it'd be great if someday you could add a datagram listener service, or some other way to separate UDP send/receive functionality. I know several other people have asked for this, but far as I know, it hasn't yet been implemented. I love my Hubitat, but I'm pretty sure I'm going to wind up back in the Linux/HA/OpenHab world eventually over LAN device support.)
Just released v.1.2.7 - minor update to support the new 3 parameter setColorTemperature() capability. The package manager should pick it up shortly, or you can get it directly from the github repository.
Have you noticed any issues with the drivers not starting their polling of devices after they hub is restarted. I have noticed recently that to get the driver to poll for status I have to go into the device and click on SAVE for the driver preferences. Once i do that it seems to schedule polling and run fine after that.
I'll do some testing tonight. Just glancing at the code, it looks like it ought to work, but it's entirely possible that I've left out something that the newer firmware wants (like the 3 parameter setColorTemperature() thing above... )
Disclaimer: I'm an adamant no-cloud-allowed-in-the-home-controls person, so my knowledge of voice command systems is only generic, but...
This is something you'd have to write a custom Alexa/Siri/Google skill to get. Setting specific lighting effects by voice isn't generically supported by the Hubitat, and if any bulbs do support it, their manufacturer likely worked with the voice service provider to build the software.
However, if your voice system supports setting color temperature, you might be able to use the color temperature/effects trick that I've already implemented for the scenes app (which also doesn't support directly setting effects).
In case you haven't seen it, you can set any effect by setting the bulb's color temperature to 6000 plus the effect number. So to set effect number 11, you just set the bulb's color temperature to 6011. If the voice system can do color temperature, this is very likely to work -- at least worth a try.
OMG thank you that works the charm right there. You have to say the number like this
"set the wall color to sixty twenty five" This is just so awesome, now I can call all the dynamic effects out.
So this brings me to another question. In the Code since I am calling out the numbers I see for the name of the lightEffects, can I change those numbers to something like B18, or must it be just the integer?
Answering my own question. Looks like trying to call out a letter number combo causes confusion for the system and google changes H28 to 828...oh well this is still great. Just have to remember my fav numbers now.
Again, I know nothing about how the voice control systems are actually implemented, but if I were building one, I'd make it possible for users to make shorthand aliases for frequently used commands. It's worth asking Alexa or Hey Google if that's possible!
Do you have an iPhone? You can set up Scenes in the Wiz app and create Siri Shortcuts for each scene. I've set up each scene to respond to the command "Activate [Romance/Forest/Ocean/etc.]" when I ask Siri. You could also add these Siri Shortcuts to a widget or your homescreen as icons.
1st Thank you to the real coders here making our lives more enjoyable with these awesome lighting controls. Color lighting control adds moods and atmospheres to our spaces and that is just frikkn cool.
Not totally related to this thread but I finally have enough on the Hubitat that I noticed things got slightly slower. I turned of descriptive logging and all logging that was not needed and surprisingly the entire system became more responsive.
This is both a question and or a feature request. In my dashboards I have a "color bulb" button for various Wiz lights. When that button is pressed I get the very large window pop up that indeed controls that bulb. There is a lot of unused real estate on that window...so does a way exist or can the feature be added within that window to add light effect commands?
The Tasker app can achieve what you want. I think it's $4 in Play Store but definitely worth it. Search for "Tasker" in this community and you will find lots of threads about it.
In the meantime, I need to continue to use the local support. I'm having trouble finding the local protocol document you found -- can you repost the link. Thanks. [never mind -- I found it]
@bob.ma, I haven't seen the Pro Reference. Will check it out. Just as a guess, it's the internal API that works with the server/cloud service that Wiz sells for corporate installations, and they finally got around to documenting it. It'll be interesting to see what the server needs to do.
@dustin.carpio, I have no way to test support for the smart plug, but it's very likely that at least the on/off functionality would work. The Wiz wifi protocol has been very consistent across their whole product line.
