#Should we also consider restarting community addons on firmware updates as the list could be endless

1 messages · Page 1 of 1 (latest)

cobalt meadow
#

Question is probably for @patent bobcat

amber bridge
#

I don't understand the question. 😄

cobalt meadow
#

Sorry wrong link

#

The PR want to stop also a community addon during firmware upgrade

#

and the question is if we want to do that

#

Because there could be other community addons and so not sure were to cut the line

#

Should we also consider restarting community addons on firmware updates as the list could be endless

amber bridge
#

Yeah, I don't really like that, but I'm not going to argue it. I think the whole hardware integration design is flawed in that sense that we're not in control of the device that we update the firmware of. But that train has gone I think.

pseudo path
#

OTOH, it's not that there are 300 zigbee/thread apps around, I would assume Nikita has a good overview of all the ways a device could be used, also because of issue reports. I think by doing it like this, you already cover probably a big majority of users

craggy phoenix
#

Yeah, I don’t see the list ever expanding beyond OTBR, ZHA, and Z2M (+ multiprotocol addon).
ZBT-2 is advertised to work with Z2M as well, so I think it’s fine to include this logic in the hardware integration. I’m not a huge fan of how this all ties together either, but unless there’s virtual serial ports for addons to use and/or supervisor magic to assume full control of a port, I can’t think of any other good solutions.

Just stopping Z2M during firmware updates would avoid a ton of issue reports every time a new firmware is released.