Yes, if you're using the manufacturer's half-assed smartphone app, but if you're on Home Assistant, like basically anyone who's serious about their smart home, having multiple kinds of smart devices isn't really a problem. It's just one more radio to configure. Some people run both Zigbee and Zwave, some people run Zigbee + Wi-Fi or even Zigbee + Zwave + Wi-Fi + cloud integrations, Home Assistant doesn't care.
1) no electricity, everything down but fiber, wifi, HA and the doorbell (they run off an UPS)
2) internet down: no problem, you just cannot reach the home automation from outside
3) Home assistant down: zigbee devices are paired together (like buttons + bulbs) or I have physical zigbee relays controlling dumb bulbs.
But, as said, I have some subsystem not fully working when (3) happens, like a zigbee button controlling a tasmota-based fan control.
We survived for over 100 years by getting up and flipping a wall switch, so the risk of a few hours without smart features shouldn’t be a showstopper.
Alternatively, both Sonoff and Home Assistant do a thread dongle for about $30 that you can use simultaneously with a zigbee one. Plus if you have any of the following, they can be used as a Thread border router: Apple TV, HomePod, Echo G4, Eero 6/7, Nest Hub, Nest Wifi, Google TV Streamer. There's also the OpenThread Border Router which can be used on certain ESP32 hardware (ESP32-S3 for $10 or ESP32-H2 for $6?) but that obviously requires more work.
I didn't really care for the way it became a sysadmin job where the stakes of a bad update or me not reading some release notes were that my light switches didn't work until I sat there and futzed around with it. I'm a programmer, enjoy Linux admin, run a whole bunch of servers....but having to dive into logs and YAML configs because the lights in my kitchen won't turn off is just not ideal. Similar issues with HomeKit, except when things mysteriously stop working there's even less ability to diagnose, given Apple's design principles that everything "just works", so apparently providing detailed error messages or diagnostics is gauche.
Usually when I had some zigbee issue, it was because of a crappy product (eg some wired air sensor that would spam the zigbee network every 1 second with a lot of data), so then I just stop using such devices and before I buy I check compatibility with HA / zigbee2mqtt.
This makes me a little weary of your comment. I don't think I'd really care if my lights not working was due to a "manufacturer being flaky" if they worked yesterday, but don't today.
Are you talking about devices being flaky on first setup (which sucks, but is understandable), or are you talking about them being flaky after an update?
That is, the flakiness isn't due to HA updates breaking connections or an unstable server, but rather manufacturers designing closed and/or brittle systems. Try as they might, the HA authors and surrounding community can only do so much for such devices.
Also, I believe the word you're looking for is 'wary' (as in, to be skeptical or suspicious), not 'weary' (as in, to be tired). :)
(For temp and humidity sensors the Bluetooth Xiaomi sensors are great and they're about $5 each)
I feel like half the griping about HA is people realizing all the hardware errata and physical reality bullshit embedded developers have to paper over on a daily basis.
E.g. no, you can't just read contact sensors without debouncing
I should probably just remove them, but I don't have any automations that depend on them.
It's been a bit since I was operating it, but I did at times certainly have issues with updates—perhaps just individual plugins or system updates that created an issue, either way, still a situation where I had to sit at a terminal and debug. I only ever ran the Docker version, not the OS, so perhaps this is less problematic in a more completely controlled stack.
I don't think I'm alone in this view, broadly speaking: https://www.reddit.com/r/homeautomation/comments/18hvl3b/i_g...
At the beginning (0.7 or maybe even earlier) I remember to have to reconfigure or reset my instance a few times a year. Those times are long gone.
I ran the docker version on a QNAP for a long time, now on a Home Assistant Green.
https://homeautomation.substack.com/p/setting-up-home-assist...
00. Installation method - you don't flash ISO into your thumb drive, no you boot ubuntu from usb drive, THEN download ISO and THEN flash your boot drive. This caught so many people. RTFM of course but FM should just say this in huge letters - BOOT UBUNTU FROM USB FIRST.
0. Host method - you either run this in docker and don't get like half features (add-on store) OR install HAOS and don't have access to your device anymore. Wanna use your computer for something else? Tough choice.
1. Integrations vs add-ons vs HACS - why is this so complicated. Add-ons only work when you run HAOS, but HACS works on any installation method. I've spent so much time moving from docker to HAOS just to realize HACS store works with with docker.
2. Root - I've succumbed to running HAOS and now I have no idea how to get root remote root access. Yes I can connect keyboard and a monitor which I had to get for this reason only and there's 0 fun to work on basic terminal on a high res monitor where you can't change font size.
3. UI performance - wanna explore data from one of the devices - either select all sensors from it and let UI crash trying to display 50 charts or pick sensor one by one (with broken scroll on desktop app).
4. Copy paste - how did they managed to break this on their desktop app is beyond me.
5. Disorienting UI - whenever I wanna reboot something I'm pissed off. Whenever I wanna find integration or add-on - I'm pissed off. Why there's media and to-do list? Why do I have to enable professional mode to unlock some menu's?
6. Bizarre way of doing things - wanna add derivative sensor? Install file editor, find some file, then fight fucking YAML syntax and then maybe reboot or reload or restart. Good luck! Why I need to add home assistant user and create password for my light switch?
Bonus. They are not selling their own device (which is great way to get started) and offering some cloud subscription which usually is on path of enshitiffication.
And don't get me wrong, there are things that it does't great and is very powerful and useful, but man it is difficult.
Integrations are running under control of Home Assistant, while addons are separate applications, running under control of the OS. With HAOS they have that control as they are delivering the OS. They are simply lacking the manpower and experience to deliver a smooth control of external applications for every OS.
> 2. Root - I've succumbed to running HAOS and now I have no idea how to get root remote root access.
Yes, that is a pretty big flaw. They are trying to make it a simple as possible, they are probably flooded with complaints and issues from too many people with barely enough knowledge. But this whole setup they maintain with HAOS is really annoying. Though, there is documentation[1] for this.
> 5. Disorienting UI - whenever I wanna reboot something I'm pissed off. Whenever I wanna find integration or add-on - I'm pissed off. Why there's media and to-do list? Why do I have to enable professional mode to unlock some menu's?
They are doing too much, want to serve everything to anyone. Really annoying, but I guess the loud voices kinda demand this one-fits-all-solution. They should really rethink they focus and architecture. Maybe making clear, distinctive apps for specific jobs might be better.
> 6. Bizarre way of doing things - wanna add derivative sensor? Install file editor, find some file, then fight fucking YAML syntax and then maybe reboot or reload or restart.
To be fair, that's really depending on the devices and nowadays often an old solution. They have worked really hard to get rid of YAML for the normal jobs. But at the end of the day, HA is a hacky tool in a vibrant, extremely diversified environment. They are doing their best to deliver a unified solution, but it takes time, and sometimes still some hacking. HA has come a long long way, and is changing really hard, and they probably have still many technical debts left from a decade ago. Their biggest problem at this point is probably history and complexity. People who are using it for years, which are still knowing the old ways, or encountering old documentation.. And it's hard to get a clear picture with all the things that HA is offer and doing.
[1] https://developers.home-assistant.io/docs/operating-system/d...
2. Ssh and vscode addon?
6. Been using it for 2 years and have yet to touch yaml.
Something about HAOS uses docker to install and manage extensions, whereas if you run the HA docker container it can't as docker-inside-docker isn't supported (?), and thus some functionality is unavailable (at least at the surface level).
Here are a few “smart” things my home assistant can do in my home, which are impossible with an “appliance”:
- when washer or dryer is done (detected via power monitoring), send push notification. But ONLY send it to the people that are home at this moment. If nobody is home, send it to the person that left home last. (i store this state in a custom _last_person_departure_ variable).
- if the washing machine door was closed after it was emptied, send push notification to the people that are home. Remind them to leave the door open. (front load washer where closing the door leads to mildew)
- If a water leak is detected, send a push notification. if not ACKed within 3 minutes, send a “critical alert” to everyone’s phone.
- If nobody is sitting on the couch (pressure sensor under the cushions), and no media is playing on the tv, turn off the tv after 20 minutes.
- turn on the hallway light if motion detected or if the front door is in an open state. but keep it on if the door remains open (chatting with a neighbor, bringing in packages, etc) Importantly, delay the “turn off” action with a timer and reset that time if more motion detected or the door is re-opened.
- when i’m on a work zoom call, automatically turn on a red light next to my home office, so family doesn’t interrupt.
That’s just the tip of the iceberg. I also get a push notification when the printers ink is below 20%, and more.
Unfortunately a truly smart home requires effort to set up. Because a smart home is unique to YOU. Everyone has different workflows, habits, and preferences. It’s not a generic off the shelf component like buying a washing machine, where the user preferences can be simplified to a handful of settings.
I even once had my wife add a bulb and while it wasn't easy, she did it.
When a year later I asked brother about the some random bulb he had - didn't work anymore.
It's even better, because Norwegian law gives 5y guarantee on electronics - could just have this bulb replaced as faulty in the shop.
Pairing a Matter device takes much longer than pairing a Zigbee device through Z2M in my experience, and the Matter add-on still sometimes needs restarting as it refuses to allow any more devices to pair after a while.
But - rather than need a Zigbee dongle (or manufacturer hub) if you've got Apple or Google devices such as HomePods you've got a ready made Thread network as they act as border routers.
If I now get a _single_ Thread/Matter/Zwave device to replace one that's broken, ignoring the cost of a new radio for HA, I have to give very serious thought to where it's going to live vs signal availability as I build out yet another network.
tldr: HA is fantastic for coordinating disparate devices, but RF still bites.
I can't just add a new Thread device at the other side of my house as the walls attenuate the signal between it and the border router. Equally I can't start replacing Zigbee devices willy-nilly in case I create Zigbee dead zones.
Not the biggest problem in the world but it does mean I'll likely need to get some pointless Thread smart plugs as temporary network extenders when I add my first Thread device.
This doesn't work when mixing Zigbee+NonZigbee devices.
I would think that as smart homes become more popular the number of people not using the defaults will rapidly decrease and manufacturers will be less and less beholden to them.
It always seems like you need $100+ dollars of hardware to run it well, not just a pi and an SD card.
It seems like it's a lot better now, but until recently it didn't seem like it was anywhere near PLC grade reliability.
Is it up to the level where you could install it at a non-technical users house and expect it to run for five years without maintenance?
And despite it not being open enough for open source enthusiasts, it's also got a bad name with manufacturers. I work for one and I asked why we wouldn't implement matter and thread and it was laughed off because apparently marketing will never give up their own app as a data collection and cross selling vehicle. Of course those are exactly the reasons I don't want this.
I didn't even know about the certification that only big players can do and the locked firmware requirements. It's ridiculous. Why were thread and matter hailed as the open revolution when they're exactly the opposite?
Subterfuge PR or the subversion of original intention by greed.
Also, wasn’t there recent news that thread was being abandoned by manufacturers, even declaring it EOL? Or am I conflating that with something else?
On the other hand, I believe all the major Thread Border Router manufacturers (Apple, Google, Amazon, Samsung) have updated their Thread routers or committed to updating their Thread routers to Thread v1.4, which is a pretty major upgrade.
[1] https://matter-smarthome.de/en/interview/nanoleaf-ceo-gimmy-...
Because consumers are lazy and dumb, and do not do any kind of research. They believe what is written on the tin. Why is OpenAI called "open"?
As long as people keep claiming this asymmetry doesn't exist we will keep getting things like Thread
Now, something like Google Home might decide to go online to talk to a Google Home Hub device, which is where Google wants to initiate all Matter communication from, but that's a Google thing, not a Matter thing.
A border router is used to bridge e.g. Thread networks onto a regular IP network so that your non-Thread smartphone can talk to it, and so Matter devices on different network types can link up directly if you want a Thread switch to control a WiFi light for example.
Matter devices use link-local IPv6 addresses and cannot route packets onto the internet even if they wanted to.
Spoiler alert: No. There's a whole bunch of bullshit: https://developers.home.google.com/matter/integration/pair#p...
You can sort of run your own device if you're fine with giving google far too much information and they can block you at any time.
Face it, bigtech has a hardon for closed ecosystems. If they could they'd make it so every computer that wants to send an ethernet packet has a private key blessed by some bigtech cabal which they can revoke, but luckily for us this standard predates this gross new fetish.
And besides, so far I've been able to use 100% of my Zigbee devices with Zigbee2MQTT and it's been wonderful.
a closed ecosystem means hermetically sealed: nothing gets in or out. matter is just treating their brand with respect. not different from any other industry standard.
if you're saying "I want all industry standards to become governmental ones", well, I happen to agree.
> NOTE for Android users: You need to follow the instructions at the bottom of the page to add the test device to the Google developer console, otherwise commissioning will fail.
Anyway, you absolutely should care about Google Home support if you want to sell a device. It'd be ridiculous to sell something that only works with Home Assistant even if I'd personally be perfectly happy with that.
Are you saying the home assistant docs are wrong? Please, elaborate.
> This process is a bit more involved but is also pretty straightforward and easy to do in most setups, though it is not officially supported and is intended for developer use.
I'll stick with my zigbee flow of "press 2 buttons"
I do not want another crappy USB C type experience to satisfy the zero dollar hobbyist. We'll just end up with zero dollar garbage from large manufacturers named Xhflk.
Thank you for the clarification?
You can connect devices without this, it just shows a warning during commissioning that the device is not certified. No impact whatsoever.
It doesn't even enforce that. You are free to use uncertified devices on your Matter network, as hobbyists making their own Matter devices can attest.
In both cases can ignore certifications and have a working product. I run uncertified, open source Matter things myself.
It's not like HDCP in that HDCP is a technology no end-user wants, but something certain content creators want.
Here is the Silabs explainer on the certification process: https://docs.silabs.com/matter/latest/matter-certification/
You can! You just can't ship it/sell it without certification.
https://www.reddit.com/r/homeassistant/comments/1adh8ah/esp3...
I did exactly that last week... Certification is required if you want to use the trademarked logo in your marketing materials (same as with Wi-Fi and Bluetooth afaik).
If "closed" means open to anyone that has their product certified to adhere to the rules, then I'm ok with that.
Just like Apple HomeKit you can add devices that aren't certified. It shows a warning, but apart from that it functions like a normal device (for as far as I can tell).
I have been using https://github.com/t0bst4r/home-assistant-matter-hub to expose my home assistant devices to Google Home without having to expose my Home Assistant to the cloud.
Second, certification is what separates Z-Wave from Zigbee which in my (n=1) experience means less issues in terms of compatibility.
Of course, with that GitHub package I shared all of that goes through the window, but who cares? I can clone the code and modify it.
Correct.
Basically, it’s not much different than when an Open Source project is supported by a company that separately offers an “Enterprise” option where they host the application and provide additional Enterprise features and support. It’s not required, but a business might choose to do it.
I mean, that PKI doesn't exclude non-approved manufacturers from producing Matter devices, you can always trust their PAA (their CA) in your border router if it's not a well-known manufacturer. And also, I am pretty sure that if this is the case the Matter border router should warn you of this and ignore the fact that the PAA is not in the local store of root CAs (as we did in the times when we had https without Let's Encrypt and didn't want to pay Comodo to sign our certs)
Matter has a public blockchain with certificates added to enforce which products are considered certified. This is called the distributed compliance ledger (DCL). The hardware devices are expected to ship with certificates on them that match the public ones, and it’s generally not possible to change the on-device certs.
This is distinct from “normal” internet PKI certificate authority where you can just swap out a few files or grab a new cert from Let’s Encrypt. Because this uses a dedicated blockchain with a history of signatures. Depending on how you want to control the device, you’d need to rebuild the whole chain of trust, including eg signatures from Google or Apple.
Also, from a practical perspective, I’m not sure of any actual controllers that let you point to different certificate sources. You can create devices with a “test vendor ID” (0xFFFF) and the controllers are supposed to ignore certs. This has downsides, like OTA updates require signing, you can’t encode proper identifiers in the device so info pages in apps are wrong, etc.
Also, the “border router” isn’t really the point of trust here, it’d be the actual controller device. A border router is just that, an IP router, like a WiFi router or a Ethernet router.
On top of that, the switch breaks compatibility with existing hardware (except for the Touchlink functionality). If you have a bunch of Zigbee devices, but at some point want to add some of the new ones, you need to start thinking about replacing all the perfectly working Zigbee devices or have a fragmented network.