Founder of Home Assistant here. Let me know if anyone has any questions about the project or the Open Home Foundation (which now owns Home Assistant, ESPHome etc)
Hi Balloob, great project, thanks for all your work! I've been using it for over 10 years now.
I am wondering if you've ever considered a change to your release rules. Monthly releases are great, but having breaking changes in every release can get to be a bit of a burden. I think it would make end users lives easier if you were able to limit breaking changes to only once (or twice) per year.
I try to read the breaking changes list every time, but sometimes I don't mess with HA for a few months as it's all running smoothly. Then when I do log back in I have a large backlog of breaking changes to review. Usually at this point I just don't upgrade and the problem keeps getting worse. If instead I knew that certain upgrades do no include breaking changes I could more easily keep up to date, and only look more closely at the yearly (or bi-yearly) update that includes the breaking changes.
We've actively managing our backwards incompatible changes, but sometimes it's out of our control (ie an API change). For things we deprecate in Home Assistant, it is a minimum of 6 months period where we print warnings with alternatives. Integrations set up via the UI, will only change for improvement if we can ensure there is a migration path (sometimes requiring adding some extra info).
Some backwards incompatible changes like requiring a new Z-Wave JS version are also able to be managed automatically by Home Assistant. However, because of choice, there are many ways Home Assistant can be installed and we're not always responsible for the installation.
I believe that we can do better in knowing what integrations you use, and mapping that against the integrations that require changes.
First, thank you. Home Assistant is an outstanding example of having control of our electronics rather than giving money to data harvesting companies.
Second, I'm curious, how often do you guys have to deal with negative actions taken towards you by those same data harvesting giants? I'd imagine they aren't huge fans of this technology. Any Cease and Desist or other fun examples you guys have had to defend yourselves from?
We have very good relationships across the industry, especially the bigger companies. I literally just came back from a meeting with Google Home :)
Where we see the most pushback is from industries adjacent to the smart home, as they don't appreciate the openness. Think garage doors, cars, or cloud data providers for info that can be useful in the home.
When someone complains, like Mazda [1], we pull their integration and communicate their stance to our shared users, and people considering buying into their products. We don't fight for access, as a manufacturer with a cloud service will always be able to find a way. If it is a local device though, our community tends to find a way[2]
Organizing devices and creating automations is still very tedious.
I'd love to be able to add a device and describe it (where it is, what it does, etc.) and have HA automatically integrate it with existing automations or fuse it with other sensors. Maybe leveraging LLMs for this.
e.g.:
I buy a new leak sensor and add it to HA. I should just tell HA it's a leak sensor and it's in my laundry room and have it create an automation to send alerts, etc. when there's a leak.
Or I add a temperature sensor in my living room and have it automatically be fused with other sensors to update my living room average temperate.
You're right. Home Assistant is the best toolbox out there, but people need to build things themselves. That's something we plan to tackle, but no timeline. Leak sensors, smoke detectors, CO2 sensors, garage door openers, they can all have benefit from some built-in automations to warn when a problem is detected.
Add to HA, and set 'area' or 'label' to the same as all your other leak sensors. Use the area or label in your automation.
I find HA joyously easy to use. I have my garage door, lights all around the house, thermostats, hot water recirculation system, doorbell, lutron blinds, and ceiling fans. The automations are easy to make, and have been getting easier over the last few years with HA improvements. (and same as others in this discussion, I use zigbee smart switches. The GE brand ones are great).
One trick: Add your automations.yml (and ideally, all HASS config/ymls) to a git repository, so you can track changes, organize and observe how automation changes behave.
Like the other commenter said, smart switches are the way to go. I prefer the Shelly modules behind light switches. They are tiny, affordable and their new generation does Zigbee/Wifi/Matter/Bluetooth, so always something that suits your installation.
Not the fella you asked but let me offer some wisdom: smart switches are a lot easier to live with than smart lights. If you also want color control, HA can do a decent job of making smart switches work well with smart lights.
The core problem with a smart light is that it very likely has a switch somewhere. If someone turns that switch off, that smart light just lost power and became dumb. Turning it back on now involves a trip to the switch.
A smart switch is smart so long as utility power is running and you never find yourself in a position where the managed device is in an unknown and/or uncontrollable state.
Are there any plans to add automations based on People and Areas (not zones)? I found the cool project Bermuda[0] and it triggers person entered/left area events based on bluetooth devices. This works great in my testing with a phone being tracked by Shelly switches. But I can't seem to find a way to actually make these events do anything. It would be even better if I didn't have to set up area specific automations at all and just be able to say "turn on the lights in an area to 20% if someone enters it after sunset".
The old automation in YAML is very cluncky as the author also mentioned. The new UI guided creation is not powerful and can become confusing for complex cases on the other side. I do all my automation with the node-red Integration. But the combination of the node-red flows with the Homeassistant dashboards is not very good.
Do you plan to change the automation to something like node-red but better integrated? Or change the yaml to sonething less declarative and more code centric?
Just wanna say thanks for leading such a strong and comprehensive open source project. A lot of open source tools are wonderful in and of themselves (being that they are free) but might not always live up to expectations or offer a whole lot. With Home Assistant, I feel like it is the opposite and the capability/power of the tool (particularly out of the box) is really quite impressive. So keep it up and thank you again!
- Home Assistant Cloud (paid)
- VPN
- Port forwarding
Is there any plan to make something like Home Assistant Cloud available for self hosting? Like a simple docker container to put on a VPS?
I don't want to deal with DynDNS to expose my home network but would prefer a Server component on a VPS with a static IP which connects to my home server and allows remote control.
seems completely out of scope for HA? if you want to proxy it from the internet then you can just do that using any of the tools used for this - NGINX, wireguard, rathole, etc etc etc.
> Founder of Home Assistant here. Let me know if anyone has any questions about the project or the Open Home Foundation (which now owns Home Assistant, ESPHome etc)
Every time I visit the big box stores, I see Wi-Fi as the primary means of connecting to the smart home ecosystem. Do you see this trend changing in the future, why from the average consumer prospective? Especially with thread?
Hi @balloob. No question but I moved yesterday night from a Home Assistant Supervised on Raspi 3 to an HAOS on Raspi 4 + SSD and the migration had been flawless. Thank you very much to you, the team, and all the contributors for making such a great and fair piece of software and building such a great community.
Any plan to update the GUI for conditional logic inside of automations? It's really clumsy to do IF/THEN or switch style constructions. Too much visual space and clunky overall.
Not much a question, but a RANT. As an user I'm grateful for HA slick UI and functionality but while the best on the market is... A damn hell.
YAML instead of pure Python is a hell. Trying to push things to be configured via WebUI is a big discomfort because well... Generic users do like clicking around, but generic users will not use HA simply because it's not and will not be possible in future to create a no-code usable IoT. All low-code/no-code stuff COMPLICATE life instead of simplify. External deps like InfluxDB to just prune past data and keep them as I wish it not much nice, having a built-in option to state how to prune and for how long to keep each specific sensor or default policy would be very nice.
Essentially the RANT could be condensed in: please consider designing for people who know how to code, because they will anyway be the most common users. IoT OEMs will only be hostile for most because they still fails to understand how to makes business in an open world, so professional integrator will not much choose HA anyway since it's way too time consuming to really customize and keep it up. A pure code approach with NO energy wasted in config WebUIs/low code/no code on contrary could makes HA an interesting "base for system integrators" in a much broader sense. NanoKVM PCIe, JetKVM show the start of a feature-rich light-out management for anything, they will be the bridge between home IoT and classic homelabs/IT. HA could play a very nice role there, essentially offering a platform to bridge the not-really-IT-ready world of ModBUS and co appliances to the TCP-enabled and digitally controlled stuff. A future where small devices could be fitted in most appliances to "makes them smart" like being in the middle of a washing machine control panel connected to home p.v. system to start programmatically depending on available p.v., a connected oven pre-loaded with food the user start when he/she knows the time he/she will be at home.
This is a potentially nice niche market who could explode in the relatively near future. It's not possible as low code/no code/pre-packaged black box stuff. Being a component anyone could easily plug in a larger system is needed.
YAML might be ok if we limit HA to some smart bulb, just having a Victron battery inverter with some 40+ sensors demanding a significant load of YAML it's nightmarish. In python native it's HYPER quick.
It's a major pain to write YAML for Home Assistant. Some parts of Home Assistant lack complete examples which are up to date. The documentation doesn't include examples for every single thing. Part of writing some automations was just a lot of trial and error, looking things up on the Internet, validating the configuration, and restarting Home Assistant. It's just not a great experience.
Discovering what has to be selected to use as an action in the automation GUI is another nuisance. The most recent example is with a light I wanted to set to 20% brightness. I had no means to find something with the keyword "brightness" or anything similar. It turned out that this was exposed as turn light on.
Breaking changes are their own source of friction. My only advantage has been that many of my automations are now just GUI automations with some custom YAML where it can't be avoided.
All of these things are far beyond what a non-technical user could be able to do. It can be difficult even for someone who knows how to look things up, read documentation and update everything when breaking changes are made.
Home Assistant isn't the kind of tool one can put in someone else's hands to use it without additional maintenance or supervision. It's also not the tool to use in any commercial setting due to its countless problems.
I regularly test disconnecting my HA server from the network and make sure nothing home critical stops working.
I do have a few internet integrations (weather, upcoming sports events, etc) and those all stop when I do a “no internet” test, but Home Assistant runs just fine without any network access.
Do you think there is any hope of convincing Tuya to make their devices easily flashable?
They'd be the unquestioned king of the space if us local only people could reliably convert them to ESPhome, and they're the way a lot of brands end up making things "smart".
Tuya's entire business model is about getting their customers' data and getting them to pay for their services through vendor lock-in. They're not going to give up on all that juicy data collection and on the money they currently charge.
It's enough for just a single direct or indirect dependency to be compromised to have a botnet or turn it into something used for surveillance against the users.
Preventing it from exfiltrating data by isolating it from the network with Internet access is the only option if you want to run it. This requires local only devices.
The way the world works, you need to be either a company or a non-profit to be able to partner with the industry. Just being an open source project is not enough.
Since the launch of the foundation, we see a large uptick in companies and universities reaching out to partner with Home Assistant. A lot of manufacturers are very happy to see that an independent platform is being established as alternative to the big tech platforms. Universities want to collaborate on energy and privacy research for the smart home. We've also seen some industry donations (ie DuckDuckGo) to support our work.
I've been using Home Assistant for about three years. I was very glad it exists. I wanted to make the most out of it. It has numerous problems and regressions are very frequent. The disappointment lies in it not being as it's described and in the fact that its development process doesn't appear to improve, nor does its overall quality appear to improve. It still gains new features in spite of all of these issues.
Home Assistant's dashboards and UI have regressions in every single release. Many such regressions aren't fixed quickly or remain that way permanently. Github issues get closed by the bot. New features ship in every release without fixing these bugs. This gave me the impression that the developers employed by Nabu Casa have very little time to focus on bugs and that there's no pre-release QA. The graphs and their history had plenty of bugs in the 2025.1 release. Are there plans to improve the development process to improve quality?
Home Assistant is described on its home page as "Open source home automation that puts local control and privacy first.". A Home Assistant OS download is useless offline and without the Nabu Casa infrastructure. A download of a Home Assistant OS image obtained today would be completely useless in 5 years for now. These are completely useless if Nabu Casa's infrastructure goes away for any reason. Do you have plans to address this?
Another point related to Home Assistant being local and making privacy a priority, Home Assistant downloads all icons from [1]. The GitHub issue [2] has been open for a while without any involvement from the developers. The Home Assistant container image doesn't include all the assets required for it to provide a Home Assistant deployment in a container. Is this something you plan to address or should it be handled in a fork of Home Assistant meant to be run completely locally?
Home Assistant bundles numerous dependencies [3]. The Home Assistant container bundles and has all of these available. Are there any plans to let users disable all cloud only integrations? What's done to assess the security of these numerous packages? This matters because people allow Home Assistant to access their indoor cameras, door locks and other potentially sensitive devices. Some malicious code run from one compromised dependency's __init__.py could have serious consequences.
Home Assistant is a Python monolith. Adding something as simple as a shell command to my configuration requires a restart of Home Assistant. Are there any plans to split this up or to improve the architecture to not have such issues anymore?
The energy dashboard is extremely limited. Are there plans to make this more flexible?
Why are you forcing people to use encryption since 2025.1? I was including these backups in my encrypted backups anyway.
The voice functionality for Home Assistant and voice PE require a cloud service or a local machine with a GPU for good performance. Are there any plans to address this to provide higher performance local voice control? The old Rhasspy (the version released before Nabu Casa hired its developer) seemed to work a lot better with defined sentences and was faster.
I've seen Home Assistant become faster over the last three years. My YAML had to be updated a few times. New features have been introduced to the dashboards. Old issues and limitations are still there. The dashboards gain new features while the number of bugs and regressions also increases. The custom resources for custom cards don't always load in the mobile app. The UI still loads all the icons from the Nabu Casa icons site [1]. Home Assistant frequently stops updating my location (home vs away) and requires deletion of the device from HA to get it to work again. Entities don't update in the dashboard sometimes.
Home Assistant is described as being an open source project which has been donated or moved to the Open Home Foundation. Why does it still require a CLA to be signed, just like corporate open source projects?
Setting up Home Assistant for someone who's non-technical is a terrible idea. This is an even bigger issue if they want it set up and left alone without updates/maintenance. The mobile app would probably stop working properly with this installation or they'd break it at some point by installing updates.
I'll wait for a bit longer while I prepare to migrate away from Home Assistant and Home Assistant OS. I'm considering a setup which uses Home Assistant core to trigger automations and to display a dashboard. All the automations and device integrations would be done with other tools. This would reduce exposure to Home Assistant's regressions and avoid Home Assistant OS's limitations.
I’ve been using HA for 10 years and I share almost all of your concerns.
Particularly annoying is automated issue closure on GitHub. Imagine spending your free time debugging an issue and describing it meticulously only to see it ignored and closed a few months down the line. I can’t but think about all the burned users who’d inevitably stop reporting anything at all. How does that affect project’s quality?
FWIW frenk clarified that their issues was not licensing, but support.
> For me, this was not about licensing specifically. However, that point unfortunately is missed and got lost. Which is unfortunate. A lot blew up on the route, which just sucks for both parties.
> In the end, I think the way this project distributes Home Assistant (and its integrations, including Ambee) is not providing the intended working and thus may surprise the end user. In the end, those users are likely to knock on the doors of the Home Assistant project and their integration maintainers, not this project. As a matter of fact, most of my packages in this project are outdated and don't match the distributed version of Home Assistant.
Home Assistant and the Home Assistant Operating System have a log of bugs, regressions, shortcomings and usability problems. They have far too many problems for me to even track them or write all of them down. That's not related to your experience. There are other issues which stand out based on what you've written.
The so called issues you've encountered appear to be due to insufficient knowledge and experience. It might be a good idea to learn more to better understand what's going on. What you've done is similar to complaining about being last in a swimming competition without learning how to swim properly first and without proper practice for several years.
seems your issues started from the beginning. you bought a HA voice believing it was a home assistant server.
it says right on their sales page it is a "voice assistant" and that it is "built for home assistant". [1]
then you didnt want to buy the HA green that is a home assistant appliance with HAOS already setup for people who don't want to diy it (like you didnt).
next you downloaded a .vdi and didnt research what it is or how to install it.
then you complain about docker images, although it is
absolutely possible to run in docker as long as you understand the limitations [2]. did you even read this?
> hmm. new macs dont have apt-get anymore.
they never did. why dont you read whats in all of your screenshots? it says right above "if your OS don't have that, look for alternatives".
> Installing Virtualbox and double clicking the .vdi file i downloaded from earlier gives.... nothing
well, what do you expect? it's a disk image, not a executable. again, the installation instructions for macOS can help you here, you should read it [3]
> anyway, it looks like the default vdi ships with some well known bugs but ALSO its now just straight up missing the \EFI\BOOT\BOOTx64.efi file it expects to load. I found one you can download here and learned that you can import them into the vm via shared folders.
you found a post from 2021, it is not relevant today.
then you started replacing files... oh man!
your actual issue is that you didn't configure the vm like the installation guide showed you.
next you got it running in docker. advice to you: don't. you will not be able to use addons and thus no hacs.
> of course it just expects the networking to work when of course it wont fucking work
> i tried ngrok to setup a tunnel but it just resulted in a bunch of bad 400 bad request errors
you must learn how docker networks work to progress here. docker only listen locally by default and you need to instruct it otherwise if that's what you want.
TLDR:
you should have just started by reading the installation instructions, it explains to you:
> Home Assistant offers four different installation methods. We recommend using Home Assistant Operating System.
then you should follow the recommendation and be done long ago.
you seem frustrated and not keen on reading or learning.
not sure who you expect to take action based on that rant.
I've built a KNX house about 10 years ago and I'm still quite happy. Let me share some experience:
Having the light switch on the smartphone does not make it any smarter, just more complex.
The following automations are the most valuable for me:
- automatic blinds. Go down when too much sun hits the facade, go down when dark outside, go up with too much wind.
No concern leaving for work, and coming back to an overheated living room (no AC needed). But still automatically collect the direct sun in winter/spring.
- motion sensors, turn on lights when dark and motion in the room, every room
- night mode - low level motion-activated light in all bedrooms, corridor and bathroom. No automatic lights in bedroom, orientation lights on, night light sockets on, blinds down
This brought me to rarely touching a button/switch, twice a day, maybe?
And then there is toys
- blinds can fully close when room is empty, but go to half tilted with presence, angles following the sun, for maximum natural light without direct sun
- TV lowers the blinds behind that would give a reflection
- opening the terrace door opens the blinds and turns off indoor lights, to not attract mosquitos (idk if that even helps)
- shower motion sensor turns ventilation on high
- some sockets go on/off for Christmas lights
- logging of appliances, water, ventilation, heating.
I like that the low level stuff in KNX does not need/have a central hub. But the higher level requires extra smarts. I plan to migrate those to Home Assistant this year.
Oh man. I love Home Assistant. But I think of it as a really fun hobby. Maintaining, getting dashboards working, integrating with wireless local network standards… It ends up very technical, very quickly, as Mr. Petersson so ably demonstrates. That said, using it has put me hard on the side of preferring home devices with open management platforms. I keep feeling there’s a chance my smart home could stay off the cloud and have good automation if only I buy the right nerd tech..
I have been using Home Assistant since before "Lovelace" UI was available. It has come a long way but there's still an ongoing maintenance demand. It's less than it used to be... but it's still not zero.
> That said, using it has put me hard on the side of preferring home devices with open management platforms.
I feel like this is the true purpose of HA and the ecosystem around it. Similar to how matter is forcing IPv6 adoption on micro-controllers, really.
Every holiday season, I go looking for a bunch of cheap stuff on Ali express to tear down. Every year there's new LED light controllers and 2024 was the first year where the manufacturers were almost _bragging_ about how they label the GPIO pins and expose the programming interface so you can throw your own firmware on there if you want. Seriously, never before have I seen these controllers BRAG about how they support WLED natively. The FOSS / DIY / I'm not using _your_ cloud, I have one at home, already movement is ... actually being catered to!? That's _new_.
"Offline" has been my number one rule for home automation since I started using HA about a decade ago.
I have a couple of hundred devices connected to it now, and the _only_ cloud integration I use is Spotify, for obvious reasons; I have been careful when buying smart things that they're completely offline, and anything I buy that _is_ smart but isn't offline-only gets hobbled into a "dumb" appliance; e.g. my new dishwasher has "smart" stuff, if I connect it to Wi-Fi, I found the maintenance menu and disabled the network interface entirely and it's just a regular dishwasher now, which is how I like it.
I try to avoid all smart devices, but I moved into a house that already had "smart" garage door openers installed, so I thought I'd try the smartness. It is indeed ridiculous in that it requires an Internet connection to work. Here I am, with a remote control device (my phone) that is on my LAN and a garage door opener that is on my LAN, but I need to do a round trip to the Internet to communicate with it? What idiot designs these things?
I worked around this by exposing most HA entities to HomeKit using the built-in HomeKit bridge.
That way you get all the "this is just integrated with Siri and it's easy for non technical people to control" as well as much more powerful automations.
For example, my home presence detection is actually powered by HomeKit automations which flip binary sensors I've exposed from HA.
For me the number one priority is to make the "smartness" additional, and not change how I interact with my home in general. This is mostly to satisfy the SO-acceptance factor and also not to confuse visitors, especially elderly like my parents.
In particular:
1) there are light switches that work as expected
2) you can adjust the temp on the TRVs
3) if the HA instance blows up, shit should still work
What this means in practice:
1) I have motion sensors in some rooms that might turn on the main lights or some smaller lamp in a corner if it's past midnight (eg in kitchen), but the light switch will always turn on/off the main lights. If no motion is detected for X minutes all lights turn off.
2) if my mom comes to visit and feels cold in the evening, she can just turn a dial like she did her entire life. No app, no touch buttons on the TRV, no "hey Google... Or was it sori? Siri? Son, help me out!" The smartness lies in having a general schedule, and then again motion detectors that reset the TRVs back to that schedule if they were adjusted manually and no motion was detected for 15 minutes.
3) This means I don't have smart bulbs, but relays in the light switches that do not run in detached mode. For TRVs this obviously works since they have dials.
Personally I consider the fact that my DIY thermostat has no buttons to change the temperature a feature, but lots of people have varying feelings on who's allowed to be adjusting the thermostat and it's good to have options :)
It doesn't help that half of the population seemingly doesn't understand how to use a thermostat. More than one person in my family treats it like an on-off switch. When they feel hot, they turn it down to the lowest temperature, and when they feel cold, they turn it up to the hottest temperature, and basically repeat this all day. No amount of explanation helps, about how you're just supposed to pick a comfortable temperature and it will maintain it.
At least in the guest room I think you might want that, people have widely varying preferences for sleep temp, but I feel similar about the other rooms. This is why the "reset on no motion" was important to me, so my mom won't turn up the heat in the living room at 10pm and then the next morning I discover my living room has turned into a sauna. ;)
I might have to add that our house is really old and has shitty insulation, so having a schedule that lowers the temp at night or when at work is also important. Keeping the temp up at acceptable levels 24/7 would be rather expensive. So when you unexpectedly are at home during those down times it's nice to be able to adjust directly at the TRV. I'm still thinking about whether I want to automate this more via motion, but since heating is not instant like turning on or off lights, you don't want to toggle the trv all the time as you enter or leave rooms...
An ultra-smart thermostat could have buttons and temperature display but have a setting so it doesn't actually do anything. So people can feel like they are doing something and feel good, while still not messing up anything.
> This means I don't have smart bulbs, but relays in the light switches
In my experience, many good smart bulbs have the option to act like dumb bulbs on regular light switches. Some just return to the state they were last in when power returns, others to a "default boring light". It's one of the things that keeps me buying the more expensive smart bulbs because they are easier to configure between such options (and the third option: stay off when power returns; avoid the "bright flash wakeup" in overnight power outages in bedroom lights, for instance).
You can also emulate that somewhat easily enough in software, even if the bulb doesn't support it right, if your hub notices a light disappeared from the network and then came back, it can default the light to some useful state.
The trouble with the bulbs is that if you turn off the switch, now your automations can't control the bulb.
I've got one bulb that occasionally loses connection. Then I have to turn it off on the switch, and the next time I go to turn it on with the automation I've got to turn the switch on again and let it connect first. This is not a seamless system.
I have Inovelli switches that have a "smart bulb" mode that lets them send commands instead of physically switching the build. I use that to make my smart bulbs respond like dumb ones to a switch, but means I also make them do smart things based on holding the switch down, double tapping, etc.
I’m moving away from this level of automation in my home. At the most, I’m thinking of a smart panel that can turn on/off/dim simple, non-smart LED bulbs throughout the main living area, and that’s it.
Right now I have expensive (at the time) GU10 LIFX bulbs you can no longer get. They’re not operating on and off at the wall, because my wifi settings changed and I couldn’t be arsed having to reconfigure 14 bulbs by manually resetting them, unscrewing them, and then slowly and painfully register g them on the wifi. I’ve probably created a lot of my own pain here because I could have used a dedicated SSID for that infra that never changes… oh well.
Also, in the time the smart bulbs have become idiot bulbs, I’ve never needed to really dim them, change their colour, or do anything smart.
I sort of feel like the idea is a good one but really it’s overthinking a really simple idea: turning a light on.
I don’t know. Maybe I’m under thinking this? Would love some thoughts.
Most smart home tech is sold because it sounds or looks cool, not because it is actually helpful. For instance, smart bulbs are dumb because they break the most obvious correct control in your house: The light switch. Smart switches are a lot better of an idea, and they recognize the reality that most of the time the best time to turn on the light is by touching the switch when entering a room.
Monitoring can be really useful and some subtle scheduled controls can be a nice touch, but people go very dumb and very overboard.
> Smart switches are a lot better of an idea, and they recognize the reality that most of the time the best time to turn on the light is by touching the switch when entering a room.
i went with precense sensors instead, stuff light up as i move across the house, and will be removing the switches.
Smart switches (at least for lights) seem to me like a solution in search of a problem. Why would I ever need to turn on lights when I'm not there? If I am there, what's wrong with just using the switch?
I am using HA for something else. I'm building some ESP32 based "smart" thermostats to collect temperature and humidity data as well as exert some control over my minisplits. The only viable interface is IR so that's taking a little work to place a transmitter and receiver appropriately s.t. my wall mounted device meshes well with the existing remote control. The end goal is to integrate with the hydronic backup to create a hybrid heat system.
It's frustrating I have to build all this myself. This shit should all just work that way out of the box, without the "GE Cloud" or whatever. But I'm glad it's made relatively easy by tools like HA and microcontroller dev boards.
I'm currently building a local LLM (multiple threads - one for each sensor suite) sensor array for more proactive needs. I don't want it else conditions, and I don't want to turn lights on when I do x or y. The sensors are cheap and plenty on AliExpress and all it takes is an esp32-s3 or similar.
A smart home should predict my needs dynamically rather than do stuff based on predefined conditions and is more than just "turn living room red."
"This was before Home Assistant offered their own hardware... Home Assistant uses SQLite, and when you have a ton of sensor data flowing in, SQLite can start choking."
Their $99 hardware works great. Some devices are chatty but it's two lines in the startup config to filter the bulk of it, with no useful functionality lost.
If the data being generated by your living room is overwhelming SQLite on an eMMC, wow.
Home Assistant is one of the few recent products to delight me during setup. The sheer number of weird things it found on my network was impressive. The number of them that are dropping off as various cloud vendors try to lock things down, even more so. It has definitely motivated my future purchase choices and pushed me to simplify.
I had problems in the past with the sqlite database getting corrupted on shutdown. I moved it to a postgresql database on the same VM and it's been fine since.
Yeah, past experience with RPi/SD cards certainly gave me pause. No problems yet, knock wood. $99 well spent. Didn't see anything widespread in the forums and they made online backup a priority in the latest version. I like these folks, their priorities, and the community they built.
Interesting that Google Nest and Tesla are pissing everyone off at the moment. The forum is a leading indicator of brands to avoid.
Yes, that has been my experience with RPi in general. But there's a lotta Pis and lotta Linux versions and a lotta SD cards and a lotta hobbyists out there. Using the $99 Home Assistant Green with eMMC soldered to the board was a leap. So far no problems, nor much griping in the forums.
Does SQLite really start choking? I feel like the issue is on configuration/ code side rather than on the database itself. It should handle thousands of writes per second, even on older Raspberry.
For this use-case, you can even likely implement own writer queue for every sensor type, and then batch insert them.
I would like further detail about this also. I suspect that SQLite wasn't choking and it was something else. I cannot imagine a single home being able to overwhelm SQLite [0]. Unless the OP has a couple thousand devices all looking to write to it at the same time and they cannot queue and take turns.
Author here. The problem with SQLite is when you start having a lot of sensors. That's when SQLite failed to keep up on a Pi. Mind you, this was back on Pi 3s. It might be better today, and I know there has been performance improvements to SQLite, but for me moving to Influx for time series and MySQL for the database solved things.
Also, even on the best SD cards, you will eventually break them if you write this much.
Came here to question this too. I have trouble with this claim because I do not see how a bunch of sensors could produce so much data as to overwhelm a Raspberry Pi...
Maybe the problem was having the database on a super-slow micro-SD card?
Low power sensors are only being polled every few minutes anyway. I have a dozen temp/humidity sensors and several dozen lights etc and my HA on a Pi 4 has no lag issues from it.
Yeah the microSD will die eventually even if it’s a high endurance one - but it’s fine for a small installation, I’ve been running a quality one until I really started building out the sensor network. With just switches it was fine. Now running on a mid tier usb3 ssd.
Like many other commenters here say, however nice and increasingly better Home Assistant is, in effect you will manage 10, 20, 50+ devices that may receive updates, live in your network - whether wifi or zigbee, all have their issues - interfere with each other or just plain break.
I love the possibilities, it's often calming and nice to show off, but like with all things personal infrastructure, I have an increasing nausea and regret, along with the sunken cost fallacy.
I suspect that what's actually needed is containerized integrations, if we can't get a real standard protocol that everyone uses(Is Matter going to take over?).
WebAssembly seems like it could be a reasonable possibility for making plugins that don't need constant maintenance.
HA isn't (usually) the problem, the smart devices are. Our LIFX bulbs work almost flawlessly, and the Ikea bulbs using zigbee (not the ikea hub) are yet to fail, but the small number of Tapo bulbs require an API authentication that expires eventually or whenever there is a blackout so they require me to re-enter the password.
So the tapo bulbs are getting replaced with more Ikea bulbs and I won't be buying Tapo again.
Readit News
I am wondering if you've ever considered a change to your release rules. Monthly releases are great, but having breaking changes in every release can get to be a bit of a burden. I think it would make end users lives easier if you were able to limit breaking changes to only once (or twice) per year.
I try to read the breaking changes list every time, but sometimes I don't mess with HA for a few months as it's all running smoothly. Then when I do log back in I have a large backlog of breaking changes to review. Usually at this point I just don't upgrade and the problem keeps getting worse. If instead I knew that certain upgrades do no include breaking changes I could more easily keep up to date, and only look more closely at the yearly (or bi-yearly) update that includes the breaking changes.
Some backwards incompatible changes like requiring a new Z-Wave JS version are also able to be managed automatically by Home Assistant. However, because of choice, there are many ways Home Assistant can be installed and we're not always responsible for the installation.
I believe that we can do better in knowing what integrations you use, and mapping that against the integrations that require changes.
Second, I'm curious, how often do you guys have to deal with negative actions taken towards you by those same data harvesting giants? I'd imagine they aren't huge fans of this technology. Any Cease and Desist or other fun examples you guys have had to defend yourselves from?
Where we see the most pushback is from industries adjacent to the smart home, as they don't appreciate the openness. Think garage doors, cars, or cloud data providers for info that can be useful in the home.
When someone complains, like Mazda [1], we pull their integration and communicate their stance to our shared users, and people considering buying into their products. We don't fight for access, as a manufacturer with a cloud service will always be able to find a way. If it is a local device though, our community tends to find a way[2]
[1]: https://arstechnica.com/cars/2023/10/mazdas-dmca-takedown-ki... [2]: https://www.home-assistant.io/blog/2023/11/06/removal-of-myq...
I'd love to be able to add a device and describe it (where it is, what it does, etc.) and have HA automatically integrate it with existing automations or fuse it with other sensors. Maybe leveraging LLMs for this.
e.g.:
I buy a new leak sensor and add it to HA. I should just tell HA it's a leak sensor and it's in my laundry room and have it create an automation to send alerts, etc. when there's a leak.
Or I add a temperature sensor in my living room and have it automatically be fused with other sensors to update my living room average temperate.
I find HA joyously easy to use. I have my garage door, lights all around the house, thermostats, hot water recirculation system, doorbell, lutron blinds, and ceiling fans. The automations are easy to make, and have been getting easier over the last few years with HA improvements. (and same as others in this discussion, I use zigbee smart switches. The GE brand ones are great).
The core problem with a smart light is that it very likely has a switch somewhere. If someone turns that switch off, that smart light just lost power and became dumb. Turning it back on now involves a trip to the switch.
A smart switch is smart so long as utility power is running and you never find yourself in a position where the managed device is in an unknown and/or uncontrollable state.
Deleted Comment
Thanks for all your great work!
[0] https://github.com/agittins/bermuda
Now the community should be able to create such things, as our automation engine is very powerful.
I think the challenge in general with room presence detection is that these systems are not very common/reliable yet for us to aim to standardize.
- Home Assistant Cloud (paid) - VPN - Port forwarding
Is there any plan to make something like Home Assistant Cloud available for self hosting? Like a simple docker container to put on a VPS?
I don't want to deal with DynDNS to expose my home network but would prefer a Server component on a VPS with a static IP which connects to my home server and allows remote control.
Or is there already a way to do this?
You set up a reverse proxy (including websocket proxying) for your HA subdomain on your VPS and you're done.
But tldr is that you don’t need any cloud VM or other service for remote access. Works great.
Every time I visit the big box stores, I see Wi-Fi as the primary means of connecting to the smart home ecosystem. Do you see this trend changing in the future, why from the average consumer prospective? Especially with thread?
(this can also be seen on our roadmap update https://www.home-assistant.io/blog/2024/11/15/roadmap-2024h2... )
YAML instead of pure Python is a hell. Trying to push things to be configured via WebUI is a big discomfort because well... Generic users do like clicking around, but generic users will not use HA simply because it's not and will not be possible in future to create a no-code usable IoT. All low-code/no-code stuff COMPLICATE life instead of simplify. External deps like InfluxDB to just prune past data and keep them as I wish it not much nice, having a built-in option to state how to prune and for how long to keep each specific sensor or default policy would be very nice.
Essentially the RANT could be condensed in: please consider designing for people who know how to code, because they will anyway be the most common users. IoT OEMs will only be hostile for most because they still fails to understand how to makes business in an open world, so professional integrator will not much choose HA anyway since it's way too time consuming to really customize and keep it up. A pure code approach with NO energy wasted in config WebUIs/low code/no code on contrary could makes HA an interesting "base for system integrators" in a much broader sense. NanoKVM PCIe, JetKVM show the start of a feature-rich light-out management for anything, they will be the bridge between home IoT and classic homelabs/IT. HA could play a very nice role there, essentially offering a platform to bridge the not-really-IT-ready world of ModBUS and co appliances to the TCP-enabled and digitally controlled stuff. A future where small devices could be fitted in most appliances to "makes them smart" like being in the middle of a washing machine control panel connected to home p.v. system to start programmatically depending on available p.v., a connected oven pre-loaded with food the user start when he/she knows the time he/she will be at home.
This is a potentially nice niche market who could explode in the relatively near future. It's not possible as low code/no code/pre-packaged black box stuff. Being a component anyone could easily plug in a larger system is needed.
YAML might be ok if we limit HA to some smart bulb, just having a Victron battery inverter with some 40+ sensors demanding a significant load of YAML it's nightmarish. In python native it's HYPER quick.
Discovering what has to be selected to use as an action in the automation GUI is another nuisance. The most recent example is with a light I wanted to set to 20% brightness. I had no means to find something with the keyword "brightness" or anything similar. It turned out that this was exposed as turn light on.
Breaking changes are their own source of friction. My only advantage has been that many of my automations are now just GUI automations with some custom YAML where it can't be avoided.
All of these things are far beyond what a non-technical user could be able to do. It can be difficult even for someone who knows how to look things up, read documentation and update everything when breaking changes are made.
Home Assistant isn't the kind of tool one can put in someone else's hands to use it without additional maintenance or supervision. It's also not the tool to use in any commercial setting due to its countless problems.
I regularly test disconnecting my HA server from the network and make sure nothing home critical stops working.
I do have a few internet integrations (weather, upcoming sports events, etc) and those all stop when I do a “no internet” test, but Home Assistant runs just fine without any network access.
They'd be the unquestioned king of the space if us local only people could reliably convert them to ESPhome, and they're the way a lot of brands end up making things "smart".
It has access to security cameras and having to trust a ton of code downloaded with Docker is a no go.
It's enough for just a single direct or indirect dependency to be compromised to have a botnet or turn it into something used for surveillance against the users.
Preventing it from exfiltrating data by isolating it from the network with Internet access is the only option if you want to run it. This requires local only devices.
Accessing it through the web UI or through the mobile app will still load icons from https://brands.home-assistant.io. The details are in this ticket https://github.com/home-assistant/frontend/issues/18549
[1]: https://github.com/VictoriaMetrics-Community/homeassistant-a... [2]: https://github.com/VictoriaMetrics-Community/homeassistant-a...
The way the world works, you need to be either a company or a non-profit to be able to partner with the industry. Just being an open source project is not enough.
Since the launch of the foundation, we see a large uptick in companies and universities reaching out to partner with Home Assistant. A lot of manufacturers are very happy to see that an independent platform is being established as alternative to the big tech platforms. Universities want to collaborate on energy and privacy research for the smart home. We've also seen some industry donations (ie DuckDuckGo) to support our work.
Home Assistant's dashboards and UI have regressions in every single release. Many such regressions aren't fixed quickly or remain that way permanently. Github issues get closed by the bot. New features ship in every release without fixing these bugs. This gave me the impression that the developers employed by Nabu Casa have very little time to focus on bugs and that there's no pre-release QA. The graphs and their history had plenty of bugs in the 2025.1 release. Are there plans to improve the development process to improve quality?
Home Assistant is described on its home page as "Open source home automation that puts local control and privacy first.". A Home Assistant OS download is useless offline and without the Nabu Casa infrastructure. A download of a Home Assistant OS image obtained today would be completely useless in 5 years for now. These are completely useless if Nabu Casa's infrastructure goes away for any reason. Do you have plans to address this?
Another point related to Home Assistant being local and making privacy a priority, Home Assistant downloads all icons from [1]. The GitHub issue [2] has been open for a while without any involvement from the developers. The Home Assistant container image doesn't include all the assets required for it to provide a Home Assistant deployment in a container. Is this something you plan to address or should it be handled in a fork of Home Assistant meant to be run completely locally?
Home Assistant bundles numerous dependencies [3]. The Home Assistant container bundles and has all of these available. Are there any plans to let users disable all cloud only integrations? What's done to assess the security of these numerous packages? This matters because people allow Home Assistant to access their indoor cameras, door locks and other potentially sensitive devices. Some malicious code run from one compromised dependency's __init__.py could have serious consequences.
Home Assistant is a Python monolith. Adding something as simple as a shell command to my configuration requires a restart of Home Assistant. Are there any plans to split this up or to improve the architecture to not have such issues anymore?
The energy dashboard is extremely limited. Are there plans to make this more flexible?
Why are you forcing people to use encryption since 2025.1? I was including these backups in my encrypted backups anyway.
The voice functionality for Home Assistant and voice PE require a cloud service or a local machine with a GPU for good performance. Are there any plans to address this to provide higher performance local voice control? The old Rhasspy (the version released before Nabu Casa hired its developer) seemed to work a lot better with defined sentences and was faster.
I've seen Home Assistant become faster over the last three years. My YAML had to be updated a few times. New features have been introduced to the dashboards. Old issues and limitations are still there. The dashboards gain new features while the number of bugs and regressions also increases. The custom resources for custom cards don't always load in the mobile app. The UI still loads all the icons from the Nabu Casa icons site [1]. Home Assistant frequently stops updating my location (home vs away) and requires deletion of the device from HA to get it to work again. Entities don't update in the dashboard sometimes.
Home Assistant is described as being an open source project which has been donated or moved to the Open Home Foundation. Why does it still require a CLA to be signed, just like corporate open source projects?
Setting up Home Assistant for someone who's non-technical is a terrible idea. This is an even bigger issue if they want it set up and left alone without updates/maintenance. The mobile app would probably stop working properly with this installation or they'd break it at some point by installing updates.
I'll wait for a bit longer while I prepare to migrate away from Home Assistant and Home Assistant OS. I'm considering a setup which uses Home Assistant core to trigger automations and to display a dashboard. All the automations and device integrations would be done with other tools. This would reduce exposure to Home Assistant's regressions and avoid Home Assistant OS's limitations.
[1] the Nabu Casa run icons site - https://brands.home-assistant.io
[2] https://github.com/home-assistant/frontend/issues/18549
[3] Home Assistant Python requirements https://github.com/home-assistant/core/blob/dev/requirements...
Particularly annoying is automated issue closure on GitHub. Imagine spending your free time debugging an issue and describing it meticulously only to see it ignored and closed a few months down the line. I can’t but think about all the burned users who’d inevitably stop reporting anything at all. How does that affect project’s quality?
Nada.
1. https://news.ycombinator.com/item?id=27505277
> For me, this was not about licensing specifically. However, that point unfortunately is missed and got lost. Which is unfortunate. A lot blew up on the route, which just sucks for both parties.
> In the end, I think the way this project distributes Home Assistant (and its integrations, including Ambee) is not providing the intended working and thus may surprise the end user. In the end, those users are likely to knock on the doors of the Home Assistant project and their integration maintainers, not this project. As a matter of fact, most of my packages in this project are outdated and don't match the distributed version of Home Assistant.
this is my friciton log. i am left with a $60 brick. hope your folks can use this to improve the experience.
The so called issues you've encountered appear to be due to insufficient knowledge and experience. It might be a good idea to learn more to better understand what's going on. What you've done is similar to complaining about being last in a swimming competition without learning how to swim properly first and without proper practice for several years.
it says right on their sales page it is a "voice assistant" and that it is "built for home assistant". [1]
then you didnt want to buy the HA green that is a home assistant appliance with HAOS already setup for people who don't want to diy it (like you didnt).
next you downloaded a .vdi and didnt research what it is or how to install it.
then you complain about docker images, although it is absolutely possible to run in docker as long as you understand the limitations [2]. did you even read this?
> hmm. new macs dont have apt-get anymore.
they never did. why dont you read whats in all of your screenshots? it says right above "if your OS don't have that, look for alternatives".
> Installing Virtualbox and double clicking the .vdi file i downloaded from earlier gives.... nothing
well, what do you expect? it's a disk image, not a executable. again, the installation instructions for macOS can help you here, you should read it [3]
> anyway, it looks like the default vdi ships with some well known bugs but ALSO its now just straight up missing the \EFI\BOOT\BOOTx64.efi file it expects to load. I found one you can download here and learned that you can import them into the vm via shared folders.
you found a post from 2021, it is not relevant today. then you started replacing files... oh man!
your actual issue is that you didn't configure the vm like the installation guide showed you.
next you got it running in docker. advice to you: don't. you will not be able to use addons and thus no hacs.
> of course it just expects the networking to work when of course it wont fucking work
> i tried ngrok to setup a tunnel but it just resulted in a bunch of bad 400 bad request errors
you must learn how docker networks work to progress here. docker only listen locally by default and you need to instruct it otherwise if that's what you want.
TLDR: you should have just started by reading the installation instructions, it explains to you:
> Home Assistant offers four different installation methods. We recommend using Home Assistant Operating System.
then you should follow the recommendation and be done long ago.
you seem frustrated and not keen on reading or learning.
not sure who you expect to take action based on that rant.
1: https://www.home-assistant.io/voice-pe/
2: https://www.home-assistant.io/installation/#advanced-install...
3: https://www.home-assistant.io/installation/macos
Having the light switch on the smartphone does not make it any smarter, just more complex.
The following automations are the most valuable for me:
- automatic blinds. Go down when too much sun hits the facade, go down when dark outside, go up with too much wind. No concern leaving for work, and coming back to an overheated living room (no AC needed). But still automatically collect the direct sun in winter/spring.
- motion sensors, turn on lights when dark and motion in the room, every room
- night mode - low level motion-activated light in all bedrooms, corridor and bathroom. No automatic lights in bedroom, orientation lights on, night light sockets on, blinds down
This brought me to rarely touching a button/switch, twice a day, maybe?
And then there is toys
- blinds can fully close when room is empty, but go to half tilted with presence, angles following the sun, for maximum natural light without direct sun
- TV lowers the blinds behind that would give a reflection
- opening the terrace door opens the blinds and turns off indoor lights, to not attract mosquitos (idk if that even helps)
- shower motion sensor turns ventilation on high
- some sockets go on/off for Christmas lights
- logging of appliances, water, ventilation, heating.
I like that the low level stuff in KNX does not need/have a central hub. But the higher level requires extra smarts. I plan to migrate those to Home Assistant this year.
My sense is that with independent dumb motion sensors you achieve much of a smart house with less cost, wifi dependency.
> That said, using it has put me hard on the side of preferring home devices with open management platforms.
I feel like this is the true purpose of HA and the ecosystem around it. Similar to how matter is forcing IPv6 adoption on micro-controllers, really.
Every holiday season, I go looking for a bunch of cheap stuff on Ali express to tear down. Every year there's new LED light controllers and 2024 was the first year where the manufacturers were almost _bragging_ about how they label the GPIO pins and expose the programming interface so you can throw your own firmware on there if you want. Seriously, never before have I seen these controllers BRAG about how they support WLED natively. The FOSS / DIY / I'm not using _your_ cloud, I have one at home, already movement is ... actually being catered to!? That's _new_.
I have a couple of hundred devices connected to it now, and the _only_ cloud integration I use is Spotify, for obvious reasons; I have been careful when buying smart things that they're completely offline, and anything I buy that _is_ smart but isn't offline-only gets hobbled into a "dumb" appliance; e.g. my new dishwasher has "smart" stuff, if I connect it to Wi-Fi, I found the maintenance menu and disabled the network interface entirely and it's just a regular dishwasher now, which is how I like it.
That way you get all the "this is just integrated with Siri and it's easy for non technical people to control" as well as much more powerful automations.
For example, my home presence detection is actually powered by HomeKit automations which flip binary sensors I've exposed from HA.
In particular:
1) there are light switches that work as expected
2) you can adjust the temp on the TRVs
3) if the HA instance blows up, shit should still work
What this means in practice:
1) I have motion sensors in some rooms that might turn on the main lights or some smaller lamp in a corner if it's past midnight (eg in kitchen), but the light switch will always turn on/off the main lights. If no motion is detected for X minutes all lights turn off.
2) if my mom comes to visit and feels cold in the evening, she can just turn a dial like she did her entire life. No app, no touch buttons on the TRV, no "hey Google... Or was it sori? Siri? Son, help me out!" The smartness lies in having a general schedule, and then again motion detectors that reset the TRVs back to that schedule if they were adjusted manually and no motion was detected for 15 minutes.
3) This means I don't have smart bulbs, but relays in the light switches that do not run in detached mode. For TRVs this obviously works since they have dials.
I might have to add that our house is really old and has shitty insulation, so having a schedule that lowers the temp at night or when at work is also important. Keeping the temp up at acceptable levels 24/7 would be rather expensive. So when you unexpectedly are at home during those down times it's nice to be able to adjust directly at the TRV. I'm still thinking about whether I want to automate this more via motion, but since heating is not instant like turning on or off lights, you don't want to toggle the trv all the time as you enter or leave rooms...
In my experience, many good smart bulbs have the option to act like dumb bulbs on regular light switches. Some just return to the state they were last in when power returns, others to a "default boring light". It's one of the things that keeps me buying the more expensive smart bulbs because they are easier to configure between such options (and the third option: stay off when power returns; avoid the "bright flash wakeup" in overnight power outages in bedroom lights, for instance).
You can also emulate that somewhat easily enough in software, even if the bulb doesn't support it right, if your hub notices a light disappeared from the network and then came back, it can default the light to some useful state.
I've got one bulb that occasionally loses connection. Then I have to turn it off on the switch, and the next time I go to turn it on with the automation I've got to turn the switch on again and let it connect first. This is not a seamless system.
(I had to look that up)
Right now I have expensive (at the time) GU10 LIFX bulbs you can no longer get. They’re not operating on and off at the wall, because my wifi settings changed and I couldn’t be arsed having to reconfigure 14 bulbs by manually resetting them, unscrewing them, and then slowly and painfully register g them on the wifi. I’ve probably created a lot of my own pain here because I could have used a dedicated SSID for that infra that never changes… oh well.
Also, in the time the smart bulbs have become idiot bulbs, I’ve never needed to really dim them, change their colour, or do anything smart.
I sort of feel like the idea is a good one but really it’s overthinking a really simple idea: turning a light on.
I don’t know. Maybe I’m under thinking this? Would love some thoughts.
Monitoring can be really useful and some subtle scheduled controls can be a nice touch, but people go very dumb and very overboard.
i went with precense sensors instead, stuff light up as i move across the house, and will be removing the switches.
I am using HA for something else. I'm building some ESP32 based "smart" thermostats to collect temperature and humidity data as well as exert some control over my minisplits. The only viable interface is IR so that's taking a little work to place a transmitter and receiver appropriately s.t. my wall mounted device meshes well with the existing remote control. The end goal is to integrate with the hydronic backup to create a hybrid heat system.
It's frustrating I have to build all this myself. This shit should all just work that way out of the box, without the "GE Cloud" or whatever. But I'm glad it's made relatively easy by tools like HA and microcontroller dev boards.
A smart home should predict my needs dynamically rather than do stuff based on predefined conditions and is more than just "turn living room red."
Just move the phones and laptops onto a fresh 5ghz ssid
Then the old 2.4ghz becomes the iot one
Too bad so many of these "smart" devices insist you talk with a server in China (or anywhere other than your own LAN!) to turn on the lights.
Their $99 hardware works great. Some devices are chatty but it's two lines in the startup config to filter the bulk of it, with no useful functionality lost.
If the data being generated by your living room is overwhelming SQLite on an eMMC, wow.
Home Assistant is one of the few recent products to delight me during setup. The sheer number of weird things it found on my network was impressive. The number of them that are dropping off as various cloud vendors try to lock things down, even more so. It has definitely motivated my future purchase choices and pushed me to simplify.
Interesting that Google Nest and Tesla are pissing everyone off at the moment. The forum is a leading indicator of brands to avoid.
For this use-case, you can even likely implement own writer queue for every sensor type, and then batch insert them.
[0] https://sqlite.org/whentouse.html
Also, even on the best SD cards, you will eventually break them if you write this much.
Maybe the problem was having the database on a super-slow micro-SD card?
I love the possibilities, it's often calming and nice to show off, but like with all things personal infrastructure, I have an increasing nausea and regret, along with the sunken cost fallacy.
WebAssembly seems like it could be a reasonable possibility for making plugins that don't need constant maintenance.
I'm HA-curious, but I use HomeKit (with Homebridge) and rarely touch it between device additions/reconfigurations.
So the tapo bulbs are getting replaced with more Ikea bulbs and I won't be buying Tapo again.
Yes, there are exceptions, like non-local-control devices. But fingers crossed, those have not given me much grief yet.