Is this in Z2MQTT?I don’t see a Refresh All option.
TBH, this isn’t just an Inovelli thing for me. I have some Sonoff smart plugs that had an update, and after update about half of them show the old firmware, with no option to upgrade, too.
The 20221110/2.08 as “latest version” is exactly what I’m seeing as well. No manner of restart, reconfigure, etc. updates the values.
in zigbee, the Level_Control_Cluster uses 0-254 as levels 0-100% and 255 (0xff) reserved for special meaning. For example P13-14 uses 255 to mean “use previous level”.
In the case of P55-56 it appears the firmware is only accepting 0-254
Sorry, I am unaware of what is available in Z2MQTT, my comment was in response to a Hubitat related question. Maybe someone familiar with Z2MQTT can chime in.
responded in github but it looks like there is probably some remapping from 255 to 254 for brightness
If you want to check to see if the update was applied you can use this method:
Blue Series 2-1 Firmware Changelog | VZM31-SN - Switches / Firmware Discussion - Inovelli Community
Ah, that did the trick, all my switches (and my other devices showing old firmware) are actually updated. Thanks EricM!
sigh I think I’m limited to updating one at a time.
Not because of the 2-1 switches per se. But because I’m using the Sonoff Dongle-E with Zigbee2MQTT. The driver itself is still marked as ‘experimental’ and still has some issues (pairing more than one device at once often causes it to crash).
Well, this is gonna suck for 60 switches @ 1/2 hour each. Though, doing it one at a time IS working, and they’re updating to 2.14.
TY. I guess I’m still stuck. Firmware still reports as Firmware: 0x01020208 using ZHA
I had added this to configuration.yaml:
And downloaded the OTA files and saved in the corresponding folder here:
No amount of reboots seem to have any impact. No sign of any updates on any swtich. Could I have missed something? I feel like it’s straight forward enough, but I am not getting the anticipated result. Thanks in advance.
Have you tried a service call to zha_toolkit.ota_notify from the zha toolkit integration?
You can also do it without that integration by calling a cluster command like this:
service: zha.issue_zigbee_cluster_command
data:
ieee: <device_ieee>
endpoint_id: 1
cluster_type: out
command_type: client
cluster_id: 25
command: 0
args:
- 0
- 100
otau_directory is commented out. Remove the # at the beginning.
awesome I think that was it. Now I’m seeing this though :
2023-04-12 20:30:35.113 DEBUG (MainThread) [zigpy.ota.provider] OTA image directory ‘\config\zigpy_ota’ does not exist
Except that it does:
Any ideas? Thanks
The fastest route of flashing seems to be directly to the chip. 
Change to forward slashes: otau_directory: /config/zigpy_ota
that did it thanks. Flashing green light now, looks like it’s in progress.
It seems Z2M isn’t properly updating its own database after the update intermittently. This is because the switch is still doing some process and the version value responded from switch is still the old one, then the switch reboots a second time and Z2M never reconfigures or pulls the values again. Performing a reconfigure fails to pull the new version number. This seems to be due to the “last seen” ISO being set. If you turn last seen off and reconfigure the switch manually it will pull the new version number.
Seems a bug is present in Z2M when dealing with Inovelli switches while “last seen” is set to the ISO value.
Seems like it occurs when doing more than 1 update at a time. The first one updates the version in the database correctly, anything after fails and keeps the same version number. When querying the switch, it reports back the new version. The database remains confused. Rebooting Z2M and HA, no change.
I’ve been able to get the version update number to go to 2.14 without changing last seen parameter. To get the switch version number to update do the following:
Go to dev console and put the following (Endpoint 1, Cluster genBasic, Attribute swBuildID) and click Read
then go to About and click reconfigure (small green arrow circle) and it should update
after reconfigure:
Also FYI you can do the same for the firmware build date by entering dateCode under dev console and reconfiguring
I’ve been reading swBuildID and then just waiting… after about 20-30 seconds the version # is updated in the About tab for the switch and the OTA tab.
Strange - I tried all of those and it still didn’t work.
Seems the ones I updated at the chip (not via Z2M) are still having the issue, but even some I updated via Z2M still won’t state the new firmware version.
Update: No matter what it still states the old version, yet when reading the buildID it responds with 2.14. As soon as I turn off last seen, it updates.
Update again: Re-paired the switch and it’s fixed.
