The Blues have a lot more capabilities than the gen2 Reds (500-series zwave). But the new gen3 Reds (800-series zwave) will have capabilities similar to the Blue and the driver settings pages will look very similar
Are you running the most current device handler from the Inovelli website (not the Hubitat built-in one)? Earlier versions had a couple of those parameters reversed
I’m using the inovelli drivers not the Hubitat ones
Are you using the most current Inovelli drivers? Earlier Inovelli drivers had them swapped
I believe so
You showed the driver for the Blue Series. I was talking about the driver for the Red series since that’s where you said you found a bug
That’s because this is a Blue Series thread.
I was asked in the Red Series thread if the Blue Series had the same behavior, and it does.
But here is the driver I’m using
There is firmware version 0102020A available now.
FileName: 122F-0101-0102020A (v2.10)
Anyone have a changelog for this version?
Problems I see in v2.10:
-When two switches are paired with each other through zigbee binding, the opposite switch does not have the same dimmer speed that is configured in Hubitat. I have both switches configured with the same dimmer speeds (faster to turn on, 2.5sec to turn off) and yet the opposite switch from the one I’m pressing is doing it in an inverted order or just goes slower than the switch I’m using. It did not do this in the prior firmware release. I did perform a re-configure and refresh after the firmware update. I even pulled the air gap on both and let them reboot. Problem still exists.
Dim levels also fail to sync after turning light on and off a few times in a row.
Seems Zigbee Binding switches might be broken in this release. The dimming speed definitely is inverted. It’s like it’s sending the opposite command. Very strange behavior.
@EricM_Inovelli, @Eric_Inovelli any idea?
Parameter ID + configuration on both switches:
1- 1.0s
5- 2.5s
6- 2.5s
7- 2.5s
8- 2.5s
I’m not clear on what you mean. Can you post a video?
Air gapping does not sync or reload settings to or from the hub.
Configure sends settings from hub to device
Refresh pulls settings from device to hub
Also, what do you have for parameters 2,3,4?
When both switches are set to turn on faster and turn off slower…
Switch A (Master switch)
Switch B (Slave Switch)
When pressing UP physical button on switch A, it shows dim level going up fast, it dims up fast like it’s supposed to. Switch B shows it going up slow even though it’s going up fast.
When pressing DOWN physical button on switch A, it shows dim level going down slow, it dims down slow like it’s supposed to. Switch B show it going down fast even though it’s going down slow.
When pressing UP physical button on switch B, it shows dim level going up fast, but switch A goes up slow and the physical light therefor turns on slow.
When pressing DOWN physical button on switch B, it shows dim level going down slow, but switch A goes down fast and the physical light therefor turns off fast.
It’s not operating as intended. The previous firmware version (v2.08) had no issue with this.
After firmware upgrade I performed a configure all command.
Then 1 minute later I performed a refresh all command.
This is what you are supposed to do after a driver update and/or firmware update.
I am running driver version 2022-12-12 (latest).
Dim levels will eventually unsync entirely where switch B will show the light is on at medium brightness and switch A and the physical light are entirely turned off.
I don’t need to program parameters 2,3,4 they use the value from parameter 1.
I even tried to program them to see if the behavior changed, it did not.
This raises another question: How do you downgrade firmware to a previous release?
Thanks for tthe feedback, I will check it out. This firmware hasn’t been officially announced yet as our beta testers are still testing it out.
I accidentally (sort of) became a beta tester, lol.
I’m glad I was able to provide some feedback though.
Yep, thanks for the help in that case LOL.
I just posted this up top, but in case anyone comes looking at the bottom of the thread:
January 18, 2023 / v2.10 / 0x0102020A
Note: We haven’t officially announced 2.10, but it is available on Hubitat servers for our beta testers. It may have an issue with binding when you have a master and a slave Inovelli device (virtual 3-way). Please wait to update until we have the issue figured out.
Is 2.10 also problematic for smartthings users (who use zigbee binding)? Ty
I think @Eric_Inovelli isn’t having any problems with his ST architecture.
Does his setup include “3 way switches“ with two blues? Just want to make sure since that seems to be the sticking point for hubitat.
Potentially. I’d have to refer to Eric for his house setup, but I believe he does have a couple?
I run this configuration v2.10 on Hubitat and it’s fine as long as all dim/rate/max/min values are set the same on both switches. If the settings are different then the LED bars on each switch moves at its own rate
The issue with Hubitat and probably SmartThings is there is no facility to fall back to previous version. So if you update to beta 2.10 and want to go back to release 2.08 there is no easy way to do it
I’m using home assistant just for firmware updates and then adding back to smartthings… I think HA can roll back if I recall? Either way maybe. Either way maybe, better to wait it out.
Having an issue with a blue series dimmer in a 4 way aux configuration bound to a group of hue bulbs.
When I use the blue switch everything works as expected.
When I use the aux switch:
the bulb group turns off
the blue series meter goes down
the blue series light.entity stays on
this causes the group to at some point turn back on.
I am running home assistant and adaptive lighting.
Firmware 2.08
