Awesome! Thank you!
Just in time to return a couple of Zooz switches and order some more Inovelli switches! Yay!
- Nate
1 Like
LOL – let me know if you need help upgrading the firmware 
1 Like
Wanted to follow up and see if this is a possibility going forward?
It’s a possibility as we work on alternate firmware, we’ll keep it in mind!
1 Like
Yay it works! I got two of my Inovelli Red Switches updated and tested.
Some Notes:
-
Had to update twice to get the firmware to report correctly in the updater software. The first time, it didn’t seem to take.
-
On the firmware update page for 1.19, probably want to mention that SmartThings users need to update the custom device handler or they won’t be able to set the instant on parameter 51. I even tried using zwave tweaker and it didn’t work. Only worked after I updated the DTH.
-
Definitely prefer to have it be on when “pressed” instead of on when released. The current setting is much better than previously, So I’m generally happy. However, I have a 3.5 year old who is learning to turn lights on and off. Many of them she can just barely reach the top. I think it would be much more intuitive for her to have it turn on when she presses the button as she doesn’t know to release it till she get it to turn on. That way she knows she hit the right button. I understand there is a tradeoff on the “held” scene options. Ideally it would be configurable but if there is a default, I would vote for on when pressed.
I love the idea of having the option for the main buttons for scene control as well as the config button with instant on and off for physical presses working as fast as dumb switches… I’ve been looking for this solution for awhile! It’s an awesome combo. I thought the new GE switch had potential with their basic scene controls, but alas nobody has a very good DTH for the new GE switch for Smartthings, they don’t offer firmware updates, there are issues with their line sensing features, and many other problems. So with this firmware update, I’m super happy to be standardizing on Inovelli Red switches! Love it.
Thank you!
- Nate
@Eric_Inovelli hi Eric, any news on OTA firmware upgrades for smartthings users? I’d love to have my switches and bulbs upgraded but I’m not very fond of doing it by myself with that special sold-separately dongle.
Unfortunately I cannot say due to an NDA we have in place with ST 
(Re)adding my $0.02 to this thread…
I really do appreciate having the ability to completely eliminate the 700ms delay. But the expense of all scene control is a hefty price! I would wonder if there is a way to make this a bit more adjustable? For example I find that double taps are by far the most useful scene control on any of the dimmers and switches in my home. I only have one scene triggered by a triple tap and that is easily achieved using some other means. But that double tap is extremely useful.
So perhaps there’s a drop down on the device page where it would be possible to choose the number of taps enabled for scene control vs milliseconds of delay. If absolute zero delay is most important and that particular switch/dimmer has no scene functionality needs then by all means disable all of them. But for some, like myself, double tap, triple tap, etc might be that “point too far.”
I’d also wonder if adjusting the amount of elapsed time considered as a multiple tap event could be shortened overall? I happen to find the double tap rate to be extremely “forgiving” on Inovelli switches in general.
Again my $0.02. I really like what I am seeing in the latest firmwares and the drivers on GitHub so I am eager to see whatever is next!
@Eric_Inovelli - thanks! I was just about to buy a bunch of Inovelli switches as we’re doing a major electrical remodel but the 700ms delay would be a showstopper. Should I wait until August to order to ensure I get the ones that do not have the delay? Thanks!
You’re welcome! Happy to help 
It’s hard to say bc there may still be old stock at Amazon, which is where we house our inventory.
What you could do is order the 10pks off our website as those will for sure have the new firmware on them as it’s a new SKU.
Hope that helps!
@Eric_Inovelli - Thanks! So it’s just firmware? So even if I get the old switches I should still be fine and just need to update the firmware?
Yes correct - the only thing that’s changing is firmware
You’ll find that making the delay configurable has been requested multiple times in this thread and Inovelli has said they’re looking into it as an alternate firmware (so it won’t be the primary firmware). Fingers crossed that we get that soon.
Delay for dimmer is configurable in beta 1.47, and frankly, its AMAZING!
1 Like
When you say configurable, I think you mean either “turn off the delay and lose scene control” or keep it around 700ms. When folks on this thread say “configurable”, they’re referring to “making it a value you set (e.g. 300ms) and keeping scene control”. So the delay is not yet configurable but can be turned off.
2 Likes
Agreed. There is no delay configuration parameter yet. That would be great.
1 Like
Yeah, I personally am waiting till it’s configurable. Folks in my house have gotten used to the scene control so even though they don’t like the delay, I can’t take away the scene control now.
Going to throw my hat in the ring here too.
I would much prefer to have the delay settable instead of just on or off and lose scene control (kinda defeats the purpose of paying more for Scene-Enabled “SN” devices).
Is it really that hard to make the 0-255 byte value be a timing value rather than just 0/1 off/on? It could be in 100ms or possibly 10ms increments. For example, values 1,2,3,etc would be 100ms, 200ms, 300ms, etc. Or possibly values 25, 50, 75, etc. would be 250ms, 500ms, 750ms, etc.
700ms just seems way too slow for all or nothing. I think a lot of people can “double-click” a lot faster than that. 500ms is very easy to double-click and 300ms (3 clicks per second) very do-able for most humans. This would allow full scene control to remain while provide a much quicker response to the single-click on / single-click off
@Eric_Inovelli INOVELLI please, Please, PLEASE make this a settable value…even it its as simple as a few fixed values to choose from a list (like 300ms, 500ms, 700ms). Locked-at-700ms or no scene control is not an acceptable solution
2 Likes
Not an acceptable solution? Dang you guys are hard to please!
Start Rant:
So, the problem here is that we’ve had to outsource our coding to our manufacturer, so it’s not as simple as just updating something quickly, especially when they’re working on multiple projects for us at once. We’re a small team of 7, with @EricM_Inovelli leading the way from a technological side, managing our firmware engineers. In addition, while he may know how to code this himself, our manufacturer has kept the firmware source code to themselves (long story for another day) so we don’t have the ability to just make some quick edits. We have to wait for them to help us, but as noted, we have multiple projects going on at once.
As for this feature (configuring the ms), yes, we recognize that this is something that a few people want and we’ll do our best to do it as we do try our best to incorporate everything.
Speaking of incorporating everything, it’s hard to do so given the space limitations on the Z-Wave 500 Series Chipset. As you may remember, we had to actually add an additional MCU to process the, “basic” commands while the Z-Wave chip processed the more advanced ones (hence Target 0 and Target 1), so it’s also very challenging to add this level of complexity as we run into space issues.
Anyway, sorry for losing my mind, just wanted to give some context as our team has worked incredibly hard on this firmware.
End Rant.
5 Likes
I appreciate the extra info behind the scenes and realize there is a lot in the coding and micro-code that you don’t have direct control over. I’m not looking for a quick solution, but I do think the current solution is really just a temporary band-aid and the dialog for a long-term solution needs to continue
I’m generally quite tolerant and don’t mind testing and using beta releases. But in this case I feel confident in saying that the given solution, which essentially DISABLES Scene Control and has been indicated as the target for production release, is not acceptable as a long-term solution. Its nice to have a band-aid, but that is not a solution.
Think about it. Why would anyone pay more for a Red Series if they have to cripple the scene control to get less on-delay? I might as well save money and buy the Black Series to get instant on with no scenes, right?
What am I missing here?