0 Followers
0 Following
1 Posts
Another vote for this option. I’ve had mine for three years and it’s been rock solid. I’m not using the built in schedule, I’m controlling everything through HA
I have the same lock. Keymaster was way more complex than I needed/wanted, but Keymaster Basic is very smooth. By default, it gives you ten code slots and a Lovelace dashboard along with mobile notifications.
GitHub - desertblade/Keymaster-Basic: Simple Home Assistant Lock Manager

Simple Home Assistant Lock Manager. Contribute to desertblade/Keymaster-Basic development by creating an account on GitHub.

GitHub

I had this when I added time and date sensors. In your configuration.yaml, exclude those entities from the log book.

logbook: exclude: entities: - sensor.time - sensor.date - sensor.date_time
Eject the warp core!
I have a sunseeker x7 and love it. No HA integration, but I haven’t found a bed for integrating yet, anyway. Set up the boundaries and schedule in the manufacturer app and let it be. Rain detection is built in and the all wheel drive is surprisingly effective.

I finally bought a tiny PC to replace my aging APU border router/firewall (OpenBSD), so I’m trying to wrap my head around building a router currently inside the network that it will be protecting.

I have Debian installed as hypervisor, Incus, and sticking with OpenBSD for the firewall. pf makes too much sense to me too switch to firewalld. I’ll also move the network-related containers off my main lab host once this is up and running.

Same here. I have it installed, but I’m resistant to managing other people’s passwords.
Never stop making these.

I’ve been on US Mobile for several years. You can choose between the Verizon, T-Mobile or AT&T networks. I’m on the Verizon SIM. Yes, you are deprioritized. No, it’s not an issue.

I’ve been very impressed with US Mobile’s support, though I’ve only needed it a couple times.

Pretty sure mine was attached to the paperwork when I got my non-provisional drivers license at 18.