I’d have to check my iptables syntax again but I’m not sure you want the FORWARD between the networks unless C has a manual route to get traffic for the 192.168.15.0/24 network back via B. You just want to NAT A behind B’s IP on 192.168.38.0/24. I think the forwards are sending the traffic without doing NAT on A.

Phillips SonicCare for 20+ years. I think it’s helped me a lure with my dental care. Various models as the batteries wear out. The latest has Bluetooth that I never use but that doesn’t affect the cleaning part.

This. Basically few addons are ‘fire and forget’, almost all of them need some sort of configuration that’s listed in the Documentation tab, or in the add-ons repo. You’ll need to read up on it and look at the Configuration tab to set whatever you need to allow it to work.

Right now - easy, with the difficulty going up over time as the main Chromium codebase continues to change (and especially as it gets security updates). I think I’ve read that some variants (Brave?) have committed to supporting ManifestV2 for as long as possible, for instance with their own fork.

WoL packets are usually sent to the ip broadcast address for the network as they’re not ip based. I don’t know if this would ever work well across networks. Can you do send the wol packet from the opnsense router instead? Does it work then?

If you’re sending it to the IP of the server, it likely works soon after your turn the machine off because the ARP entry hasn’t timed out yet, but once it times out it won’t work anymore. The router doesn’t know how to get to the machine. You may be able to add a static arp mapping to get it to work long term.

The add-on store that’s managed and updated via the supervisor. It does the same thing as your setup, but integrates into HA nicer (automatic connectivity to HA for the containers, when they need it). If you’re happy with how your setup works then there’s no compelling reason to switch.

I use an Emporia Vue device, it uses an ESP32 internally and you can find instructions on how to flash it with esphome code onto it. No cloud dependency, just wifi.

You can get various kits for one/two/three phase mains, and monitor up to 16 individual circuits via passive current clamps.

Yes. There’s no support (hopefully just yet) for multiple Home Assistant instances with the same account.

It’s called Badges - edit the dashboard page, then click on the edit button beside the tab.

apropos to search man pages, otherwise I use man

Try executing just /config/backup.sh - the config directory is mapped into the HA container under /config, not under /root.

In general, if you haven’t taken steps to expose your service to the Internet, it’s not accessible over or to the internet. Your router that connects you to the Internet should have a firewall that blocks all inbound, unsolicited requests, and you also need to do something explicit with most self hosted service to expose them, they will not announce themselves to the world.

In addition if you’re using an ipv4 network address that’s likely a private address (like 10.x.y.z, 172.x.y.z, or 192.168.x.y), which also isn’t accessible outside of your network.