I really like getting a notification that someone is at the door when I’m out. Yeah maybe it would be better with a video or picture, but I paid less than a fiver for it, including shipping from fucking China
Haha I literally setup this exact thing yesterday, and then spent ages making Telegram notifications that delete themselves after a set time, so as not to clog up the feed. Because what’s the point of knowing that someone was at the door after they’ve left?
I have been a few times. I connected a screen and nothing seemed out of the ordinary. One error message popped up though, about not starting overlayfs. It might be that my SD card has corrupted all of the sudden. Trying a restore onto a new SD card now.
I run HA as a container in a vm. I back HA data up nightly and the compose script for running HA is archived on github. If the vm dies there is another vm that can bring it back up. If the host dies (I have a pool of xenserver (xcp-ng) hosts, so it would be a major domestic disaster if they all croaked) I have a fallback to run HA on docker on wsl. If the house burns down all the scripts are on GitHub and the backups get sent to Azure monthly. I think I’m covered.
HA might be possible in a active passive configuration if you don’t have any dependencies on external hardware like a zigbee stick. Active active would need support by HA and I don’t think that is implemented.
I think the most secure thing is to keep regular backups so you can roll back easily.
Thanks, yes, I think active-active would be another magnitude harder… and would need database, history, etc on shared storage… over the top to jist ensure the lights stay on.
And backups are essential for all use cases (and not just the built-in HA backup left on the device / VM / container that just failed!)
Correct, OPs needs is describing what kubernetes was made for. Fault tolerant container orchestration. Or any other orchestration framework.
However it’s a best to learn and get set up. Migrating all of my containers over took a couple of months of learning and trial and error. Each person has to decide is that level of effort worth it in a home application
You’ll need to learn a lot more about kubernetes to decide fully if you want to do it. I’m more or less telling you that yes there are ways to keep it highly available, but they’re going to be literally 10x if not more the amount of effort to spin up and probably maintain.
Proxmox has their own flavor of HA that is a lower level of virtualization. They’ll be able to failover a specific VM/CT to another node if one fails, but again pros and cons. The major annoyance for both is where do you put your data so 2 separate nodes can access it? Both k8s and proxmox have different approaches.
K8s and Proxmox operate at different levels. You can run k8s on Proxmox, and that’s what I’ve been (very slowly) building up to at home.
With Proxmox you can failover VMs between nodes as long as storage (including VM boot disk) is external to the nodes. This can be NFS on a NAS, iSCSI, Ceph or many other options.
It’s even possible to failover a USB device (e.g. a Zigbee controller or similar) by attaching one on each node and mapping them using Resource Mappings (search on the announcement post: proxmox.com/…/proxmox-virtual-environment-8-0).
This can also be used if you’re deploying k8s on top of Proxmox just as well.
Take a look at zigbee2mqtt this is what I use to add any of my ZigBee devices to home assistant. You may find there is more frequent reporting/polling with this so you have more updated information in your home assistant instance.
ZigBee is the way to go IMO for the most “local control”. Your thermostat is probably pretty good and would not need replacing for a long time.
For automation of your thermostat and other items in the house you will need to setup your own automations that work for you. Home assistant won’t do this for you automatically like other 3rd party thermostats that “learn” your patterns.
Home assistant is pretty powerful in what you can do with automation as it’s allows you to use other sensors around the house, even poll outside stats like weather. So in theory you can set automations that turn off your heathing if your phone or all phones have left the house. You can set automations that turn on the heathing when the outside temperature reaches a certain temperature and the house temperature drops to a certain point.
I definitely recommend zigbee2mqtt over ZHA. I originally went with ZHA and just recently went through the hassle of converting over. It was worth it. IMO, it’s best to just start with zigbee2mqtt, and to convert before you have a lot of devices and automations.
Edit: before I posted this comment, I couldn’t see any comments other than the one I was responding to.
I should add you need to install Mqtt broker from the addin store as well.
Once you get this installed under integrations you should see Mqtt and this is where your new ZigBee devices will be listed. (As opposed to the ZigBee integration)
No need to hard reset the thermostat as once you add it through zigbee2mqtt and get mqtt integration added the device will be new to your HA installation.
Odd I have done the full setup several times As I run pure dockers / separate HA, Mosquito MQTT and Zigbee2mqtt and the devices all just auto discover and appear in HA has devices with entities with full control.
I haven’t had this issue specifically but I’ve noticed when adding color changing bulbs, the color changing ability doesn’t show up in Home Assistant until I change the color in the dashboard of zigbee2mqtt. After that, home assistant recognizes the bulb’s capabilities. What hub do you have?
homeassistant
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.