Now that you say it - Maybe I even have some in my network?
Could be - for example - a wall switch which not only has various locally attached relays (lights, fans, etc.) but at the same time interacts with hygrometers and/or buttons which are not physically attached but visible (and maybe even controllable) from HA thru that very wall switch?
No As said I prefer devices that I can “really” own
Aren’t rules there to be broken and standards to be… deprecated?
The best one can do imho is to bet his or her horses on the most open (and widely supported) hardware possible. For example while one probably still can use Zwave devices of the series 300 or older it might not be the best idea because they do not support encryption - and one (who posses “only” the hardware) can’t role their own So while the device (probably) still works because the zwave system is backwards compatible it might not be the smartest choice to make use of such devices
Mitigations for these vulnerabilities vary based on the chipset and device. In some cases it may be necessary to upgrade to newer hardware, for example, 500 and 700 series chipsets that support S2 authentication and encryption.
On the other hand esphome didn’t had a dedicated encrypted api (but obviously supports encrypted wifi) back in the year 2020 but as of it’s open nature a full api encryption was “shipped” a year later Also esp’s couldn’t work as a bluetooth proxy 3 years ago - but now they can. Esphome didn’t “comply” with the bthome standard - but now it does. Also the improv-wifi standard wasn’t supported the time I deployed already more than 50 devices around my house - now all my esp devices support it (even the ones I bought more than 5 years ago). Last but not least the time I started it was necessary to have a local program to install esphome on my devices - now things once improved drastically again and thank’s to espwebtools all that’s needed is just a browser The thing is: If it is open it can be “shipped” later - things improve and so does your own(ed) hardware
For some (open) type of hardware it’s possible to support “standards” which didn’t even exist at the time of manufacture
Well we “saw” already ho good (or bad) tuya teamed up with the HA devs
- From a (commercial) company point of view I would say “free devs - we take them”.
- As a HA user I would really hope the devs wouldn’t “waste” time with other companies/people products. As the ecosystem is open everybody is free to have their product supported (if they really want).
To my knowledge there simply is no revocation “system” in place (yet?). I also really doubt that nabu casa can do much the moment a company turns out to not comply any more to the rules but continues selling / loads of the product (which now “doesn’t work with…”) but still have a fat “works with…” printed on