Thanks Eric! I’m out of town till Sunday night, but I’ll have some time on Monday to try this out (I’m the Innr-plug-binding guy, so I’m eager to see how that goes with this version).
Cheers!
Just updated on 2 of my Blue switches in Z2M. I do love the way the LED bar updates to reflect percentage complete.
It looks like my flickering issue is now resolved. I should note, I don’t see the new LED notification types, I guess we’ll need a new Z2M converter update to support these. CC: @nathanfiscus (since you kindly made the recent updates).
Other observation is that after the update, Z2M doesn’t appear to reflect a new firmware version number (2.00) or firmware version date (2020805). I’m not sure if this is a Z2M bug or the firmware not tagged correctly.
I just updated using z2m 1.28.1, and my Blue shows version 2.05 with a date of 20221103
I haven’t updated my switches yet but I have 2 issues with them right now. The first issue is with quick start. I have noticed when changing the brightness from the Google home app the brightness goes to the quick start level before changing to the new brightness.
The second issue I have is with my second switch that is meshed before it gets to the hub. Apparently 27ft through a single wall is too far away to talk directly to the hub. I can control the second switch from the hubitat fine but if I try to control it from the Google home app the switch becomes unresponsive. It requires an air gap to reset it. I don’t know how the switch can even tell it’s being controlled from a different source. Maybe Google is turning the switch off and on rapidly before changing the brightness?
Check the MAC address of your switches and check out this thread–wonder if your is part of the affected batch. Blue Series 2-1 Signal / Routing / Performance Issue Troubleshooting Thread - #194 by dmulcahey
I had the same issue with one of my switches - one of them has 2.00 after the update and one of them reports 2.05. Both seem to work fine as before, though the LED effect is still not available as a device action in Z2M.
Ok, looks like 2/3 of my switches have that issue. I just updated the firmware to 2.05 on the “good” switch. Hopefully 94:DE:B8 is ok. I will have to re-enable quick start and see if the bulb flashing issue still exists on the new firmware.
How do I upgrade with ZHA?
Search the site below under ota for the text to add to your configuration.yaml, reboot, they will update automatically.
For info:
And if they don’t reboot, you can use the cluster command in the link to push them to go 
Just make sure your logging is set to debug if you want to see the update progress in system logs, otherwise you’ll get a visual indicator of progress on the switch’s LED bar.
Follow the instructions that @mbrink posted. Make sure to reboot HA once you’ve edited the configuration.yaml. Then just give it a bit of time. One of my switches was very quick to update (within 5 minutes), the other with lower LQI took some time (I want to say an hour but I’m not really certian). I did see the single bottom LED on the lightstrip turn on and blink while the update was performing the update. I just left it alone and 10 minutes after I updated it was completed.
Tried to update the firmware on my Blue switch on Hubitat, says it failed due to “cancel request from device”. The switch was untouched during the update. I did do the double click as requested in the logs. This is one of the UNaffected switches 04:0D:84…
Summary
dev:292022-11-06 10:08:43.382 PMdebugLight Switch Addition 2: MeterReport(meterType: 1, precision: 1, scale: 2, size: 4, meterValue: [0, 0, 0, 16], rateType: 1, deltaTime: 0, previousMeterValue: [])
dev:16232022-11-06 10:08:20.222 PMinfoApplication ID Received
dev:292022-11-06 10:08:18.277 PMdebugLight Switch Addition 2: MeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 182, 247], rateType: 1, deltaTime: 3610, previousMeterValue: [0, 0, 182, 245])
dev:362022-11-06 10:08:16.137 PMinfoManufacturer Name Received
dev:362022-11-06 10:08:16.032 PMinfoping()
dev:7702022-11-06 10:08:01.037 PMinfoMotion Front Door Stairs is inactive
dev:2022022-11-06 10:07:53.037 PMinfoApplication ID Received
dev:1732022-11-06 10:07:44.789 PMinfoApplication ID Received
sys:12022-11-06 10:07:38.427 PMwarnFirmware update for null failed due to a cancel request from the device.
dev:7702022-11-06 10:07:16.980 PMinfoMotion Front Door Stairs is active
dev:20282022-11-06 10:06:54.223 PMinfoApplication ID Received
sys:12022-11-06 10:06:47.477 PMtraceStarting firmware update for Switch Blue Zig 3.0 8278 at join, Inovelli from 01020200 to 01020205.
sys:12022-11-06 10:06:47.397 PMtraceDownloading firmware update for Switch Blue Zig 3.0 8278 at join, Inovelli.
sys:12022-11-06 10:06:46.516 PMinfoFirmware update for Switch Blue Zig 3.0 8278 at join, Inovelli 122F-0101-01020200 is not available.
sys:12022-11-06 10:06:46.510 PMtraceUnable to download firmware update for Switch Blue Zig 3.0 8278 at join, Inovelli, please try again.
dev:20342022-11-06 10:06:42.312 PMwarnFirmware in this channel may be “beta” quality. Please check Firmware Discussion - Inovelli Community before proceeding. Double-click “Update Firmware” to proceed
Then I tried again and got up to 40%, then same failure due to “cancel request from device”
Summary
sys:12022-11-06 10:19:39.589 PMwarnFirmware update for null failed due to a cancel request from the device.
dev:16232022-11-06 10:19:37.467 PMinfoApplication ID Received
dev:2022022-11-06 10:19:05.521 PMinfoApplication ID Received
sys:12022-11-06 10:18:40.614 PMtraceFirmware update for [name:Switch Blue Zig 3.0 8278 at join, manufacturer:Inovelli, imageFileName:122F-0101-01020205, fileVersion:01020205] is 40% complete.
dev:1732022-11-06 10:18:33.757 PMinfoApplication ID Received
dev:20282022-11-06 10:18:09.194 PMinfoApplication ID Received
dev:7692022-11-06 10:18:09.115 PMinfoMotion Front Door Hue temperature is 71.57°F
sys:12022-11-06 10:18:02.311 PMtraceFirmware update for [name:Switch Blue Zig 3.0 8278 at join, manufacturer:Inovelli, imageFileName:122F-0101-01020205, fileVersion:01020205] is 30% complete.
dev:17212022-11-06 10:18:01.054 PMdebugKeypad V1 : Presence : Last presence report 7 seconds ago.
dev:7702022-11-06 10:17:46.815 PMinfoMotion Front Door Stairs is inactive
dev:2432022-11-06 10:17:27.194 PMinfoManufacturer Name Received
sys:12022-11-06 10:17:24.346 PMtraceFirmware update for [name:Switch Blue Zig 3.0 8278 at join, manufacturer:Inovelli, imageFileName:122F-0101-01020205, fileVersion:01020205] is 20% complete.
dev:7702022-11-06 10:17:03.333 PMinfoMotion Front Door Stairs is active
dev:16232022-11-06 10:16:50.179 PMinfoApplication ID Received
sys:12022-11-06 10:16:46.168 PMtraceFirmware update for [name:Switch Blue Zig 3.0 8278 at join, manufacturer:Inovelli, imageFileName:122F-0101-01020205, fileVersion:01020205] is 10% complete.
dev:2022022-11-06 10:16:27.026 PMinfoApplication ID Received
sys:12022-11-06 10:16:07.770 PMtraceStarting firmware update for Switch Blue Zig 3.0 8278 at join, Inovelli from 01020200 to 01020205.
dev:20342022-11-06 10:16:07.536 PMwarnFirmware in this channel may be “beta” quality. Please check Firmware Discussion - Inovelli Community before proceeding. Double-click “Update Firmware” to proceed
dev:20342022-11-06 10:16:00.318 PMwarnFirmware in this channel may be “beta” quality. Please check Firmware Discussion - Inovelli Community before proceeding. Double-click “Update Firmware” to proceed
Yep, looks like 2.06 is up and they grabbed 2.05. Thanks.
This happened to a lot of us during beta. You just have to keep trying. Not sure if it’s the server, hub, or switch. It’s annoying, but at least it doesn’t break the switch. Maybe one day Hubitat folks will let us flash locally for zigbee.
2.06 isn’t listed in the prod firmware.json file, that’s why they’d grab 2.05 for now.
I am a bit confused about the firmware versions. I used ZHA to update the firmware and now it shows 0x01020205. Not sure what this translates to…is it 2.05? Thanks!
Yep, that’s 2.05, going to show up a little different in ZHA than some other hubs, but the main part you’ll care about are those last 4 numbers.
Welp… the INNR binding issue is not fixed – I just re-installed some 04’s and 94:DE’s and updated all of them successfully to the 2.05 firmware on Hubitat (also using latest available HE driver).
All switches have been installed for a couple hours, and one of my 94:DE has binded itself to at least one nearby INNR 224 plug.
I’m not using any zigbee-binding setups with any of my Blues and I don’t have the binding app or original binding driver installed anymore (I cleared those out and reset my Hubiat database since then, so any dregs of those should be long gone).
I’ll post this info in the performance thread too.
@hydro311 The issue may be related to a “group” bug or an invalid endpoint bug that we are working on right now. Should have a firmware update in the next few days for these bugs.