I presently have one Blue Series switch and use a Samsung Smartthings Hub. How do I check the switch firmware and are updates automatic? Thanks.
1 Like
You can’t. SmartThings does not support OTA firmware updates since the move to edge, and has said they have no plans to do so.
1 Like
Your best bet for updating a Zigbee device would be to explore using an alternate hub temporarily to flash the firmware. You would remove the device from ST and add it to the hub . . flash . . . remove from the temporary hub and re-add to ST.
Hubitat and HA will both accomplish that, with Hubitat being easier and quicker if the only use is a firmware flash.
@spyze1, FYI, this is slightly incorrect - Do not remove it from ST, as this will delete it from any automations, scenes, rooms, etc, and erase all stored config settings.
- Perform a factory reset on the switch
- Pair to Hubitat/HA
- Flash updated firmware
- Perform factory reset on switch or remove from Hubitat/HA
- Pair to ST (it will be recognized as the previously known switch)
- In ST, re-send all configuration settings.
3 Likes
That’s the harder way to do it. The override files work fine, but I’ve only had luck with them by placing them both on my own GitHub and pointing to both files there externally.
You can also use external converters that will by default override existing converters. See here: More configuration options | Zigbee2MQTT
Or you can modify the source inovelli.js file where it says: ota: ota.inovelli
and change it to ota: ota.zigbeeOTA
I didn’t realize I already had this changed when I was messing with my own extension earlier.
At this current time the easiest way is to:
1.) Create an external converter.
2.) Place normal inovelli.js file in data folder.
3.) OPTIONAL: Change ota:ota.inovelli to ota.zigbeeOTA)
3a.) If optional was done, create index OTA overrides as usual.
3b.) If optional was NOT done, create OTA folder and copy script from GitHub, change json listed there.
FOR THE FUTURE: I will make an updater Z2M user extension to override OTA without any source code modifications and upload it on my GitHub for you guys to try. You will be able to point it to any OTA file and specify the payload and it will update any device.
1 Like
Hi, @EricM_Inovelli. Cross posting for clarity. It seems that this scaling issue is still present on smartthings when a routine is used to set the default level. Hoping it can be fixed too!
1 Like
How do you do a manual update using ZHA? I assume it is with a cluster command but I can’t find documentation about it. Thanks!
1 Like
Super helpful! This made the upgrade extremely simple.
1 Like
I’m surprised 2.15 hasn’t moved from beta to production. It is leaps and bounds better than 2.08.
Am I missing something?
4 Likes
Rare bulb incompatibility. Perfect is the goal, not just good.
I’m a little confused about this, too, since I have 3 recently received switches that came pre-installed with 2.15. So it seems that they’re shipping 2.15 already, which to me, implies “production”
1 Like
Don’t let perfect be the enemy of good.
3 Likes
Seems that if it’s good enough for newly-manufactured devices, it ought to be good enough for us too. What’s the deal @Eric_Inovelli?
3 Likes
https://github.com/InovelliUSA/Firmware/tree/main/Blue-Series/Zigbee/VZM31-SN-2-1-Switch/Beta/2.15
I haven’t been following this thread as much as the other Eric, but maybe he forgot to announce it and let you know we’re transitioning to GitHub for firmware so people can provide bugs and other suggestions there.
It’s been up on GitHub for about a month now 
It’s a manual update only. Are you going to update z2m to point to the new location?
1 Like
Paging @EricM_Inovelli. Looks like 2.15 was officially released without any notification here. And, it was released in a new location that isn’t being picked up by Zigbee2MQTT. Can you help get this back on track so that folks can easily upgrade to the latest firmware?
4 Likes
Just wanted to mention the 2.15 version is inside a beta folder. So even though it shows a release date its not a production release based on the folder.
2 Likes
What about for hubitat users? Are you no longer supporting us? I have a dozen switches stuck on 2.08 that I am waiting to install ever since 2.14 was pulled.
It’s been MONTHS with us sitting at 2.08. The dimming performance with 2.08 was terrible for me and I waited out 2.14 which solved the performance problems for me. I started installing and only made it halfway before the update was pulled… and now I have a box full of switches I don’t think I can install until a new firmware is released.
I get you have other issues to work out, and I want to be patient, but this is getting ridiculous at this point.
The Hubitat servers have v2.15 on them. I’m not sure exactly when it was loaded there but it’s there now.
1 Like
Can we get a definitive confirmation then? Is 2.15 still beta or is it released for the masses? Thanks.
2 Likes