com.zsmartsystems.zigbee icon indicating copy to clipboard operation
com.zsmartsystems.zigbee copied to clipboard

ZigBeeNode endpoint change due to firmware update

Open triller-telekom opened this issue 4 years ago • 3 comments

As found in https://github.com/zsmartsystems/com.zsmartsystems.zigbee/issues/1087#issuecomment-660905497 some devices might change their endpoints due to a firmware update.

Once the device announces itself via the DeviceAnnounce message, the corresponding ZigBeeNode has to be updated somehow.

triller-telekom avatar Jul 20 '20 09:07 triller-telekom

Throwing in a few thoughts here...

Ultimately we'd need to rediscover the node - this would need to remove all endpoints, and probably also the descriptors, from the ZigBeeNode and do a rediscovery. This would ensure that we account for any possible changes within the node (eg even changing it from a smoke sensor to a door sensor to a light bulb - if someone so desired).

I guess the big question is how to handle this - do we assume that since the firmware has changed, that the device could always have changed, and therefore after EVERY completed OTA that we should perform a rediscovery, or do we make this optional, or do we try and do something in-between. I'm tempted to say that we should always perform a rediscovery after every OTA completes - that ensures we know what the device has morphed into.

cdjackson avatar Jul 20 '20 14:07 cdjackson

My first thought was that I could simply update the current node with "whatever comes in", but then I realized that we not not have much information about the device inside the DeviceAnnounce.

So yes, I agree, we would need to query everything from the device.

I haven't seen many zigbee devices that change during a firmware update, but I remember from a discussion in openHAB, that a firmware is basically what makes a devices. So if you change the firmware, you (potentially) get a different (type of) device, since features might have been added and/or removed.

Based on this, I would vote for re-discovering the node after each successful firmware update.

triller-telekom avatar Jul 21 '20 08:07 triller-telekom

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Sep 19 '20 08:09 stale[bot]