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.
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
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.
Ah, it was full health & safety... large stainless steel vat containing hot molten chocolate, rotating stirring paddle, steps (unsecured) up to an open inspection hatch... but they wore hair nets...
And, I think they had that policy where all the staff could take as much chocolate as they wanted... so of course, all got sick & tired of that and never took any more.
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.