Blue Series 2-1 Firmware Changelog | VZM31-SN

What is the mapping for the new LED notifications? What number correlates to which notification animation?

  • Added LED notifications: “falling”, “rising”, “aurora single”, and others. (2.02)

The new notifications are not listed in the Blue Series manual.

1=Solid, 2=Fast Blink, 3=Slow Blink, 4=Pulse, 5=Chase, 6=Open/Close, 7=Small-to-Big, 8=Aurora, 9=Slow Falling, 10=Medium Falling, 11=Fast Falling, 12=Slow Rising, 13=Medium Rising, 14=Fast Rising, 15=Medium Blink, 16=Slow Chase, 17=Fast Chase, 18=Fast Siren, 19=Slow Siren, 0=LEDs off, 255=Clear Notification"

3 Likes

Also currently for individual LED notifications -

0- Off
1- Solid
2- Fast Blink
3- Slow Blink
4- Pulse
5- Chase
6- Falling
7- Rising
8- Aurora
255- Clear

2 Likes

Also note the distinction between an “Off” notification and the “Clear” notification:

‘Off’ is an actual ‘effect’ to force the LED off when it might otherwise be on. It’s still considered to be an active notification. If it has a duration, the LED will turn off for the duration and then turn back on. IF it has an indefinite duration then that LED stays off until the notification is cleared

‘Clear’ is not an ‘effect’ but rather, it is the action to stop the notification. Typically this is used to stop (clear) a notification that was set with indefinte duration

9 Likes

Has anyone had any problems in Z2M where the update doesn’t show for some 2-in-1 dimmers? I was able to update 3 of my dimmers to 2.08, but one dimmer only updated to 2.07 and another didn’t find an update and is stuck at 2.00

3 Likes

Maybe it’s already updated? There is a z2m bug where it may not show the correct firmware version on the ota page.
Here is a workaround:

1 Like

Thanks for that pointer, looks like it was the same bug and the workaround fixed it for me.

1 Like

Hoping for some help from the friendly community. Smarthings user here who recently purchased a Sonoff Zigbee dongle to update firmware on my Blues. Ventured into HA (what a learning curve…) for the first time and managed to get a blue switch paired and controlable through the zigbee stick on HA running on a virtual machine.

I am not clear on steps to update firmware though. I added code to the configuration.yaml following these intructions: Zigbee Home Automation - Home Assistant , and saved the latest Inovelli OTA file in it’s own folder on the HA. Am I missing something? Are there any easy to follow instructions for someone new to HA… thanks in advance.

Once you have added the update code to your config yaml file and you have restarted HA you simply wait for the update to happen. In my experience it starts very quickly within a few minutes of connecting the new switch.

You might not even notice it updating unless you’re watching the LED on the strip. Occasionally I have had one update and I only knew because the firmware version changed on the device page.

Yes it’s been overnight and firmware version is still showing old. I’m wondering if configuration.yaml is not correct. Do I just paste this in on top like in my image? Thanks.

1 Like

Literally as I posted this the device updated. LOL. Thank you.

1 Like

I paired my blue switch back to smartthings after having updated firmware using HA.

Now none of the routines involving scenes and button presses will trigger on that switch. I’ve confirmed the switch paired to smartthings as I can control though smarthings app and voice (Alexa) and it was rediscovered as the original device.

Any ideas? Routines all look good. Also it looks like it added back with the original settings on the app, ie… Dimmer mode, but the device itself seems to have all default settings (ie. Set to on/off mode) . Is there a way to “push” a refresh of settings from the hub to the switch on smartthings?

1 Like

Is there a thread on the ST community where we can tag along?

@sdbigio There is a “bind” command that is executed when the device is first added that needs to be ran again after the device has been factory reset. I’ll work on adding that to the driver as well as the ability to re-send the configuration options.

@Mith This is the only thread that I see mentioning it in the SmartThings community. [ST Edge] Is it possible to upgrade device’s firmware using OTA? - Developer Programs / Writing Edge Drivers - SmartThings Community

1 Like

This should be fixed in the latest ST Edge driver release. It should automatically be pushed out to your hub within a few hours. Still working on the other request.

Edit: I also have the fix to reconfigure the parameters after you re-include it (after a factory reset). I am just doing some testing on it and I will try to push it tonight or tomorrow.

1 Like

Thanks so much. Let me know if you need someone to test out in the wild.

Thank you it looks like another Inovelli customer posted. I added my own comments. At least publicly it sounds like they have no idea

Suggest also opening a ticket. You can email [email protected]… Putting some pressure on wouldn’t hurt most likely.

1 Like

@EricM_Inovelli Can a configuration parameter be exposed to allow the switch to operate as an end device rather than a router or set to default to an end device for devices with bad IEEE addresses. That would allow those of us with defective switches to keep using them without damaging the mesh.

Probably best to default to an end device for those with bad IEEE addresses so the user doesn’t have to do anything.

4 Likes

Ok I must be missing something. I have a ble switch I am trying to update the firmware on as it shows its on 2.00, my drives is 2022-11-05.

I thought all I had to do was click on update firmware on the device details page in Hubitat.

Nothing ever happens.

1 Like