I have several Blue zigbee dimmers that appear to load new firmware, but never actually update to a new version. I’m using Hubitat and have gone through several iterations of pairing/resetting and deleted the driver and re-installed, but no luck. They are multi-way with aux switches and a neutral. They are on 2.08. Is there an alternate way for me to load firmware manually?
If these are from the first batch of production switches, they need a bootloader flash before they take newer firmware updates. This has to be done via a cable with instructions from Inovelli. Email [email protected] and they should be able to help you out.
1 Like
Thank you for your quick response. I’ll reach out to them.
Where do I find the firmware ver. Using Hubitat? All I see is 122F-0101-01020304
That’s the most recent version (3.04). If using the Inovelli driver, the f/w info is on both the device’s Commands tab page and the Device Info tab page.
Thanks, It showed up after I tried a firmware update.
I think 3.04 release is broken. I’m able to force update to 2.18 without issue on the same switches that won’t update to 3.04. It seems the 3.04 release is the problem, not the bootloader.
I have 50 of these switches, not a single one updated properly to 3.04. They rebooted and still running 2.18. Yet I can downgrade to 2.08 and back to 2.18 without issue. I have pin flashed these and they still won’t update to 3.04.
My advice hasn’t changed. [email protected] will be able to help you.
I can tell you that there is a bootloader problem and it only affects switches from the first batch. All of my switches from the first batch needed a new bootloader flashed via a cable which reset them to firmware 2.0 and then they were happy to upgrade to any of the 3.x firmwares.
It’s not a bug in 3.04, this problem existed with all 3.x firmwares and can only be corrected by flashing an updated bootloader via a cable.
What’s different between 2.18 and 3.04 that would require a different bootloader? This makes no sense.
I have a copy of that bootloader and application that flashes 2.00. That bootloader is the same bootloader on these switches.
How do I know? Well, I pulled the current bootloader from the switch and it matches 100%.
No offense, but what you’re stating does not make any sense.
I have pin flashed these with the bootloader file and then the 2.00 application file. Went to update them to 3.04, failed and now it’s stuck on 2.00. Force-flashed to 2.18 using Z2M, success. Went to try to update again to 3.04, failed - stuck on 2.18 now. The pin flash is not a solution to a bad OTA update file.
Is the real problem that the bootloaders are locked by a Chinese manuf and this process unlocks the bootloader? I don’t see anything different. Also - pin flashing did not allow me to upgrade any of my switches to 3.04. I tried on 7 of them and gave up at that point. Each time the switch is fully wiped, to do this 50+ times would be insane. It also doesn’t work so no reason to waste time there.
Questions:
1.) Why would 2.18 consistently flash without issue but 3.04 consistently fails if it wasn’t a OTA file issue?
2.) These switches have been pin flashed in the past just to get them to 2.18. Do they need pin flashed every time a release comes out? If so, I think these switches would need to be recalled as it’s likely a hardware problem.
3.) None of this explains why when I pin flash them and then try to update to 3.04 it still fails, why?
@EricM_Inovelli @Eric_Inovelli any ideas?
1 Like
@SamJWard I’m sorry you are having a hard time with this, but I assure you the process has worked on many, many switches. As @rohan explained there is a bug in some 2022 VZM31-SN bootloaders that will sometimes require a USB flasher to fix. We have worked with many customers to resolve the issue and if you want to open a support request with me (just tell support that I requested to handle the ticket), we can work through it. We have actually created a support document to walk through this issue here:
Blue Series Switch - Troubleshooting OTA (Over-the-Air) Updates | Inovelli Help Center
2 Likes
Thank you for the quick response. I understand. It worked prior when I had issues updating to 2.18, but this is different. I have pin flashed 12 switches now and all 3.04 updates failed with 2.00 being on the switches. I was able to force flash 2.18 though. So I’m not sure where to go from here. It seems all my switches are the same problem with trying to get to 3.04.
Pin flashing is also a huge pain to do each time. It’s strange that it’s not working for me this time. What exactly is causing this issue? Can it be permanently resolved? Why do the new build date switches not have this problem? Is it a physical hardware issue?
@EricM_Inovelli do you guys have a better cable for a segger that makes it easier to install in the switch? It’s really hard to line them up when they’re installed in the wall.