I concur. Tap off now works with on/off SBM enabled. Thanks @EricM_Inovelli for fixing it so quickly! 
Thanks for looking into it. I look forward to hearing what you find out. 
Agreed!
@EricM_Inovelli It took a few tries to get the right timing but I was able to get the switch to exclude and that seems to have fixed the problem. Once excluded the LED bar changed to default blue and I was able to include it again with no problems. Thanks for your help!
Well I seem to be having a different issue with a different switch on 1.55 now. I flashed one and it wonāt allow me to set any parameters. My 50-52 Parameters wonāt change at all and 50 and 51 look to be flopped when it comes to values.
Current Values:
parameter50value : 0 - Canāt get this to change to anything other than 0
parameter51value : 4 - Canāt get this to change to anything other than 4
parameter52value : 1 - Canāt get this to change to anything other than 1
Isnāt Parameter 51 supposed to have only 2 options? 0-1?
I have tried toggling all of these back and forth and have tried using the drop down menus, the set parameter button, and also switching the driver to a zwave tool and setting them that way but they donāt budge. Any help would be greatly appreciated.
Nice!
I hate to say it, but you may need to do a factory reset on it and re-include.
After updating all of my dimmers in hubitat, half of them still say Firmware 1.52 after flashing both targets twice. When I change them to the updater device type it says 1.55, but not when device type is set to the red series dimmer.
Also, a couple of my dimmers say āPlease wake up your sleepy deviceā when updating. Iāve fixed this before by excluding, including without security, and then updating again. Is there any explanation for this or any other fix?
I see this fairly often after firmware updates. As far as I know, there is no automatic event that updates the hub with the new version number even though the device has been updated. You have to ātickleā it to get the updated firmware version number updated in hubitat. Try using the Configure command button on the Device screen in Hubitat. That usually updates the firmware version field in my experience. It also seems to just be a good practice after any firmware update as it forces your non-default parameter settings to be re-sent
Ah, I was doing āRefreshā. āConfigureā seems to fix it. Now to wake up those other dimmersā¦
Youāre on a roll, that did the trick. Thanks again!
I ran the gambit of tests on this last night, and I feel like I am living in a utopian future world where I have literally zero requests to improve this switch. I am truly thankful to @EricM_Inovelli and his dev team for making this a literal ādreamā switch.
Piggybacking off of others, I do think there is room for research and development on the following, either for firmware updates or v3 of the dimmer switch (in no particular order):
3-way On/Off SBM mode
Min level increase (corresponding max level min input increase)
Ramping choppiness fix
Toggle dimmer to default level on button 1 press, regardless of state (currently only when off).
Iām just over the moon right now!!!
3 Likes
I mostly agree 
but did you mean āutopianā world? 
A dystopian world is bad and undesirable 
Beta 1.54 was unusable for me (due to the non-tap-off bug) but the quick fix to beta 1.55 solved that and I can run with it now 
Thanks @EricM_Inovelli for getting that out so quickly! 
However, 3-way SBM mode is still acting very weird. Since this is beta firmware thatās ok with me. But in my utopian world, this would either need to be fixed, or at least dis-allowed in the device handler before it becomes official production release.
I agree with that wish-list
But I would modify #1 to include both modes of SBM (mode1=on/off, mode2=always on)
And I would add #5
Better LED bar dimming using gamma curve (top example in illustration below)
(initial request posted here: LED Bar Intensity values - big gap/jump between 10% and 20% - Firmware Discussion - Inovelli Community)
Haha you are correct! Fixed.
I remember another one Iād like to add:
#6 Make the Dimming Speed and Ramp Rate params be 100mS increments not 1-sec increments
3 Likes
Thanks, that is a huge compliment. 
We will continue to try and bring the features and enhancements that the community is asking for!
3 Likes
Hi @EricM_Inovelli ,
I updated all of my red dimmers to the 1.55 target 0 firmware (with hubitat) and that went fine.
However, when I updated the target 1 firmware to 1.44 the first time on one of my dimmers it failed and bricked the device. Right now its not responding to anything. I ried air gapping it and also resetting it by holding the button down for 20s with no luck.
Anything more I could try or is it dead?
Does the LED bar do anything when you air gap it? I had a switch that would boot up after air gap but became completely unresponsive after booting. I was able to get an exclusion to happen as it was booting and that allowed it to start working again.
Nope. Completely dead after attempting the update. No lights or anything. Even after the air gap.
I updated the target 1 firmware to 1.44
Hopefully you used the v1.44.bin file for target 1 and not the v1.44.otz file
Yup. Double checked that. Used the right file. One of my switches is fully upgraded. This one failed partly through and got bricked. I canāt get it back to life.
Has anyone else noticed that this firmware or another recent version (I was updating from 1.48) seems to have resulted in a different minimum dimming level being required?
Example, I have ~15 Halo RL56129S1EWHR on a four different circuits. Since updating to firmware v1.55 Iāve had to increase parameter 5 to as high as 50 on one of these circuits where a value 38 was working 100% reliably previously (and continues to work on the other circuits). Really the only thing different about this circuit compared to the others is that it has two extra lights and is also using a dumb auxiliary switch.
I have not tried flashing back to v1.48 to confirm if this issue goes away.
EDIT: I am actually still able to reproduce this on the older firmware. Very strange. Iām now wondering if changing the CCT setting makes a difference (Iāve changed it twice since I originally tested these).