I am not seeing the update_available at the moment.
Looks like you have to publish a message to zigbee2mqtt to perform the update.
Yes, I looked and decided that an older working firmware was better than a bricked one as they are still working it out and basically I will wait for someone to bring out an idiot proof way of updating.autolog wrote:Take a look at this page: OTA updates
I am not seeing the update_available at the moment.
Looks like you have to publish a message to zigbee2mqtt to perform the update.
Actually that command is supposed to tell the device to reset it’s counter. I haven’t implemented it in the shim because I have no idea what it’s supposed to look like. Does the documentation for the Salus plug show how to do that via MQTT?autolog wrote: I think it is because that function isn't available in the MQTT Shim plugin. It effectively tells Indigo to zero the Total Usage. It isn't a zigbee2mqtt problem AFAICS. I expect it will be added in due course once it is reported to Joe.
Unfortunately they don't say anything, it is a case of buy the Salus hub and update with the app, no mention of zigbee in the very useless docs.FlyingDiver wrote:Actually that command is supposed to tell the device to reset it’s counter. I haven’t implemented it in the shim because I have no idea what it’s supposed to look like. Does the documentation for the Salus plug show how to do that via MQTT?autolog wrote: I think it is because that function isn't available in the MQTT Shim plugin. It effectively tells Indigo to zero the Total Usage. It isn't a zigbee2mqtt problem AFAICS. I expect it will be added in due course once it is reported to Joe.
autolog wrote:Take a look at this page: OTA updates
I am not seeing the update_available at the moment.
Looks like you have to publish a message to zigbee2mqtt to perform the update.
autolog wrote:Take a look at this page: OTA updates
I am not seeing the update_available at the moment.
Looks like you have to publish a message to zigbee2mqtt to perform the update.