Google enshittifying Thread So, because I am cheap as heck, I wanted to give some of the IKEA smart stuff a go. It's still manufactured in China, but a wireless temp/humidity sensor with display that only lights up on a button press (the case is the button) seemed to be a no brainer, especially at 7,99 per unit. Also, it takes dual AAA instead of stupid CR-anything batteries and if your fingernails are strong enough (mine are) you can plop off the back cover just so. The downside is that I had a really, really hard time to set up the devices. And it's all Google's fault. Intermission: I worked at Google for almost eight years. That's more than a decade ago now. Even then, back in the day, the answer to many problems people had with Googles products, hardware or software, was "give up and use multiple devices", primarily because many Google products were designed by people that could not imagine crossing borders would be a regular occurrence, or living in places with weather. California is a hell of a place that messes with people's heads. So, I have a HAOS install on a dedicated machine, not even virtualized, and I have a NabuCasa ZBT-1 with Thread firmware, and my system looks like everything is fine and dandy. Only if I try to comission a device via the Companion App, well, it tells me to add a thread border router. It's right there. So I go complain on the Home Assistant forum, and I learn the following: Be careful to define the correct network as preferred network before doing the sync, and don't delete that network afterwards! Android does NOT allow you to delete the Thread credentials (there are work arounds by deleting Google Play Store storage, but it has side effect like lost wallet etc.!) Once again, Californians cannot fathom people owning multiple identities, maybe even being in multiple places that may have separate networks, or any other thing that makes it an IDEA SO STUPID IT MUST BE MALICIOUS (this is Google, so the saying does not apply here) to tie a thread credential so deep in to Google Play Services that you need to break half your account to reset it, and well, yeah, I don't know if I may or may not have a Thread network's credential from earlier experiements that didn't pan out as expected. I am lucky. I am privileged. I happen to have an iOS device. With that, comissioning works. But do not be mistaken, this is using Apple's implementation for comissioning a matter device, including blacklists for devices deemed uncouth (just like Google). So yeah, if you are after home automation solutions you own, stick with ZWave, Zigbee, WiFi (tasmota and esphome do just fine), or BLE. Also, the automatic routing through the Thread network? It works like shit in my place, compared ot all the other solutions. Matter over Thread is a real proper downgrade over Zigbee, Zwave, WiFi, or BLE. It's too much magic and zero facilities to debug, and at a critical junction (device comissioning) wholly dependend on exactly the big tech companies you want to avoid when deciding to run with Home Assistant. #homeassistant #matteroverthread #iot #digitaldependency