Sorry, I’m feeling like a total idiot, but what’s the version you’re updating to? I enabled trace logs and when double-clicking the updateFirmware button I get:
dev:332022-11-11 09:55:42.996 PMtraceupdateFirmware [he raw 0x175C 0x01 0x01 0x0019 {09 01 00 03 64 FFFF FFFF FFFF FFFF}]
dev:332022-11-11 09:55:42.984 PMinfoKitchen Cans: updateFirmware(switch's fwDate: 2020805, switch's fwVersion: 2.00)
dev:332022-11-11 09:55:42.245 PMwarnFirmware in this channel may be "beta" quality. Please check https://community.inovelli.com/c/switches/switch-firmware/42 before proceeding. Double-click "Update Firmware" to proceed
dev:332022-11-11 09:55:42.238 PMinfoKitchen Cans: updateFirmware(switch's fwDate: 2020805, switch's fwVersion: 2.00)
And nothing visibly happens in Hubitat after giving it a minute and refreshing. Air-gapping and resetting the switch I’ll get some heartbeat info messages when it comes back online, then still the same FW versions.
I guess I’m confused by all the dates and versions it seems to report:
- State Variables
- fwVersion : 2.00
- fwDate : 2020805
- lastUpdateFw : 1668225435881 (6 minutes ago as I write this)
- Device Details
- firmwareMT: 122F-0101-01020205
- softwareBuild: 01020205
Comparing to non-updated one, it’s just the Device Details section that’s different with
- firmwareMT: 122F-0101-01020200
- softwareBuild: 01020200
So look at the last 3-4 digits for the version? …0200 → 2.00, …0205 → 2.05?
Is the fwVersion and fwDate a red herring in Hubitat (is it a driver thing, and “fw” means something else)…argh. Hubitat confusion aside, I’m still getting the blinking in my 4-way switch setup 