Ive tried several time on several devices with no luck .. under (Current State) there is nothing , ive tried to update inovelli switches and bulbs both with same outcome .. is there something im missing? any setting that have to be changed in hub ??
Which devices? And where are you loading the new firmware from?
Yeah. That message and 100%. Also the confirmed read of 2.30. I’ve done 21 of 42 bulbs so far here. Now the ones that are furthest away from the hub and that will take the longest to update....
1 Like
awesome , how are your updated bulbs performing?, i got about 20 total but i
had reverted back to my phillips hue because my LZW42s were very irresponsive
BTW have you update any Switches ? im ive been looking for a .hex link but cant find it
how did you power cycle the switch ? my was a sleepy device as well when i tried to update.. now its completely unresponsive .
same exact issue here.
If your switch has the air gap tab at the bottom, pull that out for a few seconds, then push back in. Otherwise go flip off power at the breaker for a few seconds.
1 Like
Individually they perform great. Using associations with my switches the on/off and dimming is great. Calling out a color change to a single bulb via Alexa is less than 1-2 seconds before responding. When you add them in a group you will have the popcorn effect (one light turning on after the other - due to Z-Wave not multi-casting like Zigbee does from what I have read) but it is much improved. My dining room light is 5 bulbs and they all turn the proper color within 2 seconds of issuing the verbal command. I can now string color commands back to back and they "just work" instead of eventually everything grinding to a halt and a single bulb may or may not change up to 30 seconds later like before. All-in-all I am impressed with the change. I have moved to the Hubitat Built-in Driver here as @bcopeland is now staff and maintaining it.
Check out the video of the speed of the bulb changes now that @Eric_Inovelli posted...
Good times...
I have updated my switches to 1.41 to fix the notification issue but not moved to 1.44. Most of those fixes are for LED bulb/Hue bulb issues from what I can tell. The firmwares are here...on the right side...
https://support.inovelli.com/portal/kb/inovelli/downloads/firmware
-Travis
nice so built in driver works better than inovelli ?
I was using the @bcopeland version so it essentially turned into the Hubitat driver when he joined the team. He had a hand in the Inovelli one too but @ericm is more versed in what changes he has implemented that may not be in the Hubitat driver.
You can't assume that until there is an official word from @bcopeland. All standard built-in Hubitat drivers are closed source and not available to us mortals. If Bryan's drivers do get incorporated into Hubitat, I would expect the ones in the communities to be pulled or listed as no longer supported rather than Bryan needing to keep supporting his drivers and whatever he is doing internally with Hubitat.
3 Likes
True..this is all I could get out of him when asking for clarity a while back...
1 Like
Correct.. My drivers that are “feature complete” in the hub.. I will be deprecating.. The community versions are different than the built in versions, so if someone wants to take the ones I deprecate over, for some reason, they can... There are a few drivers that won’t be making it into the hub any time soon due to their nature and not wanting to create a support nightmare..
6 Likes
It could take months to find and deprecate all the drivers you have created. 
2 Likes
Right.. I need to sit and go through them.. because there are a few that are feature complete that I can get moved... I'll create a deprecated directory on my github and move them there..
4 Likes
Do you see the updater tool becoming part of the platform? It could add a lot of support and you wouldn't likely be able to post firmware like you have. It would be great to have something like this built-in though.
1 Like
One day..
3 Likes
