Yeah, the home zone is somewhat… different Zones
I do most of my config in yaml and all the zones are configured in a separate file, however, the home zone has (had? I’ve not checked in years) to be configured in configuration.yaml under the homeassistant: section.
You should be able to do something like:
homeassistant:
latitude: 12.3356
longitude: 1.23456
radius: 50
If you’re configuring zones from the UI, I think editing the file should still work.
I have multiple zones: home and almost-home (same center coordinates, just larger diameter)
This allows the house to “get ready” before someone is actually home, ie trigger lights to come on earlier.
It also helps with random GPS jumps.
Then, when the wifi connection is slow (maybe low phone battery) and people are literally outside the door, there’s no awkward pauses before someone actually “arrives”.
I also have zones for our work places, intending to be used as a double-check, ie not-home isn’t usually good enough, I want the house to know we’re all at work and then the internal house cameras come on, etc.
I also have a “visitors” flag, so that if friends / family are in and we leave, then the TV and lights don’t turn off and they’re not attacked by the laser robots…
Also, (from memory) the person entity can be a combo of GPS and ping sensors to ensure it’s a correct reading
With… or without their knowledge? 😉
But yeah, there’s so many wifis around me, I could probably load balance across them all…
I hope that maybe this database will also help with that… if you can’t identify it, it’ll have less representation, so it won’t be bought… and the quality vendors will start to shine through.
Wow.
Ok, that sounds like that has evolved over some time!
Yeah, I think the firewall has a hardware issue… it reboots, starts stops fine under normal conditions, but, just sometimes a weird glitch throws it off.
Good point about VRRP, I’ll look into that some more as I think that’s the open, non-Cisco one.
That (2 FWs) was what I was considering initially.
But, looking at some other posts, I’m starting to rethink my design as I only have 1 WAN connection, then I only need 1 FW (maybe). SIM would be rarely used, I’m not sure the overall cost would be worth it
So separating FW from DHCP & DNS might be a better solution.
Not heard of BeeGFS, had a quick look on the Arch wiki… looks quite involved…
But, ok, at least I know that the DHCP part can be dealt with - thanks.
I’ve not looked at Proxmox clusters - can they restart VMs on a different host if they’re all using the same shared storage?
Ah… I was reading this thinking “ah, I’ll have to reply about the battery…”… glad you’re limiting the charging…
But an interesting point… I have a spare OLD Dell laptop kicking around which has various issues, but might be able to do what you’re doing. Thanks
Yep, all good with DHCP vs DNS… just my grammer was terrible.
Nothing was getting an IP from the DHCP, when the wifi returned…and… DNS was also not working for the few devices that still had an IP.
Sry bout the confusion there.
Good points there.
For 1. The ISP router is a Fritz one set to bridge mode running over a PoE adapter from the same UPS the firewall is using. It stayed up all the time (looking back at the logs)
Not sure what happened here, but the firewall is the DNS resolver and when everything else powered back up, nothing got an IP address. Now, whether thw service failed or the WAPs took longer to start than the devices could wait, I’m not sure, but as Scotty said: it’s dead Jim.
Good point. I don’t need it ALL to be redundant.
Also good. The UPS is directly connected to the firewall (which has NUT in), but it doesn’t inform anything else… I’ll look into that too.
Nice mental reset for me about over thinking it… thanks
Well, in my case the most crucial single point is the firewall.
The rest isn’t too bad
Nice.
Running different SSIDs too?
I put all my IoT stuff on a dedicated 2.4-only network, VLANd it to the (pfsense) firewall which allows the VLAN trunk to be split into separate logical NICs that I apply different policies to, like no access to the internet, etc…
You can definitely change a sensor’s type, but my recommendation is to change it as close to the sensor as possible.
I use zigbee2mqtt (so I don’t know if this applies to z-wave), but to change the 1 or 2 devices that were wrongly detected on my system, I changed them in zigbee2mqtt first and then HA will use the corrected data.
If I corrected HA, then corrected zigbee2mqtt I’d have to do this twice, plus I presume HA wouldn’t automatically pick up any other changes I made to that sensor because it had been overridden.
👆🏻 This is the link everyone needs to look at.
It covers things like keeping your phone active for 2FA, subscriptions that need to be paid until data is saved, etc.
It’s what my SO & I use.
Very thorough
BSD?
Ah, good old dd
When you have some spare time, take a look at partclone - clonezilla uses it because it only backs up used blocks, not free space, so more efficient.
Interesting.
Yep, I agree there’s 2 types of backups:
Out of curiosity, how are you doing the drive imaging?
I’m from ye olden times, when everything was done in the yaml configuration files - so I prefer that approach.
The zones you create from the UI, work fine.
It’s just that the default “
home” zone appears to have some quirks that can only be set fromconfiguration.yaml