281–290 of 344 posts
Earlier quoted context omitted.
My friend has lost 15GB of sensor data because of corrupted MariaDB on his HA instance after an upgrade. It's definitely not a hands-off system.
I have been using HA for 4 years, no such issues. But even if, restore from backup seems like an easy fix?
Earlier quoted context omitted.
If it can be done quickly enough that ya only need to charge 20 or 30 bucks, it might be a business model to reflash gizmos like this ?
You mean exploiting FOSS for personal profit would be a business model? Yes, yes most definitely it would be. We see that all the time in the world. Extract money with the easy tasks and leave the hard stuff (actually building things, long-term support, you name it) to "someone else". And it's perfectly legal too; Just a shameful thing to do. privatize profits, socialize costs
It's perfectly fine to make a business implementing, installing, or supporting FOSS software. I would even consider that a positive thing. Even if you don't (or can't!) help the upstream development.
Is anyone else trying to run HA with deCONZ & Conbee II ? AFAICT the documentation is scattershot and the software is ugly and fickle. OTOH maybe I'm just stupid.
HomeAssistant is running inside a VM with the stick passed through from the host.
It works mostly well, hasn't lost any of the Sonoff and Lixee sensors. The only issue is that I need to reboot the VM after an update, or it will lose access to the stick for some reason.
Earlier quoted context omitted.
What I wish I had known: HA is just a python program, it's pretty easy to run it manually. After my Pi's sdcard died, I wanted to use an old laptop (more reliable with a built-in backup battery) so I followed the deployment recommendations and used the VM image. After that, for the first time I started having problems with HA not running - because VirtualBox would run only about a month before crashing. And I didn't…
Just use Docker?
Earlier quoted context omitted.
Just use Docker?
USB passthrough for docker (and LVM) is a massive pain. Avoid if you're just starting out. VMs or physical deployments are much more straight forward.
devices:
- /dev/ttyUSB0:/dev/ttyUSB0Earlier quoted context omitted.
Good advice, except that I’d try whenever possible to get AA/AAA devices rather than button cells. Not only do the button cell devices burn through batteries, causing a maintenance headache if you have a non-trivial number of devices, but the rechargeable battery ecosystem is much better developed for AA/AAA. We’re currently working on swapping out all our button cell remotes, especially. Also, the replacement proces…
A battery detection automation really helps with the maintenance (even for AA/AAA): https://community.home-assistant.io/t/low-battery-notificati...
Most of my devices hover around 90% for months, then drop to 60% and die within a day. I've stopped bothering with preemptive maintenance, and just replace batteries when devices drop offline.
Earlier quoted context omitted.
Why is that?
RDBMS isn't the best place to store time series data. There are better and more efficient options for that.
If you are thinking of deploying Home Assistant (HA), let me give you a few tips that I should have known when started. HA environment is vast. There are myriads of options, features, and functions. There are some gotchas that can be costly down the road. All of the following are "for now, as you start out": Do not gyrate over which version of HA to run. Run the HAOS loaded on RasPi, or a dedicated machine. You can m…