Same here.
I jumped on Ryzen in 2017 when it seemed to be actually taking a step forward.
Then I’ve just…not needed a new CPU since then. A GPU 3 years later, but other than that, I’m trucking along nicely.

I hit this stumbling block.
And I don’t quite want to go the whole hog/headache of HA.
My solution was to run warm-spare: Once a week the VM can be synced to the second box, but never powered on.
And HA backups are pretty good anyway, it doesn’t take long to bring it back.

I have the ecowitt wh51, directly with rtl_433.
It’s the 866 version.
I had to set rtl_433 to also monitor 866, but other than that, it’s been very solid for…Blimey, years now.

I go to a half-way house: Smart bulbs, dumb switches, but a zigbee button next to the switch.
1 click toggles on/off in the last state.
Press+Hold for warm-white evening.
Double-click for daytime.
And now, a sticker on the 230v switch that says “don’t switch off!”

I can second the Hue bulbs.
They’re good quality, and connect directly to a zigbee dongle without the Signiant app/Hub.

I like to dump the whole VM every so often.
Overkill? Maybe. But I like knowing that no matter how hard I cock it up, I can spin an old version up.

I’m feeling a lot less crazy having my strict rule on AV equipment:
It should work out the box without connecting to the internet, and it shouldn’t be connected without a damned good reason.
To the point that I insisted on setting up the PS5 and playing a game on it before connecting, just to be sure.

Yep, through misunderstanding I left rtl_433 auto addition switched on for over a year.
I think I ended up with over 9000 unique tpms entries.
Clearing them out from MQTT was a pain in the backside, too!

I have alerts that push out when the fridge door is open.
And another that flashes all the lights in the house when the doorbell rings.

To be honest, part of the reason I leaned towards having the radios on the same box, was simplicity.
I have a box, with a VM, VM is backed up, new box could be stood up if needed and restored from a backup.
The other was, when I knock over the network (don’t ask…), I don’t lose logged data from the various sensors.

If you did want to be able to fail over quickly, so long as you make the USB device paths match (ie, have them on the same device in proxmox), you should be able to swap things over inside 10 minutes.

Is there a particular reason you want to put your z-wave controller on the network, rather than just plugging it into the proxmox hardware? (Assuming I’ve read your post correctly). Are you looking to do high availability on the VM or something?

I found running HAOS in a VM, and passing through USB devices worked really well, and I just bought the bog-standard z-wave dongle from Aeotec.

I haven’t had a single zigbee button need a battery replacement yet.

Do you have rtl_433 mqtt auto-discovery set up?

What type of radio is the weather station using? Are you pulling the data using RTL_433?

Boilers are kinda on/off, from a control perspective.
The boiler heats water to the set flow temperature, pumps it around the loop, and repeats until it’s switched off.
The amount of gas used is modulated by the boiler to make the water come out at the right flow temperature.
Unless all the rooms in your house are perfectly insulated, or so badly insulated that they lose heat instantly, ad-hoq temperature changes in individual rooms is tricky to do well.

I did have smart TRVs for a while, but actually ended up binning them.
So my current solution is:
HomeAssistant controlled call-for-heat. This is a relay that when connected, turns the boiler on.
Temperature sensors in each room. This allowed me to balance the radiators so they all warmed up evenly, and also feed into the HA thermostat to decide when the heat needs to come on.
Manual TRVs in each room set to slightly above the normal target temperature. So they’re normally open, but will close if something crazy happens, like someone turning on a fan heater.
Timed target temperatures in HA. So the target temperature drops at bedtime, and rises just before I get up.

I also lowered the flow temperature of the boiler, which improves efficiency.
I’m not 100% sure what you’re trying to achieve in your setup.
But adding TRVs to each room (and having one always-open, like the bathroom) would be a good step forward.

It was such a breath of fresh air when I finally put HA onto proxmox.
“Oh, I actually have resource now? Sweet!”

A little late to the party, but yes, I can confirm that Hue bulbs can be controlled directly over zigbee. You will need a zigbee radio if you haven’t already bought one (£20-ish).
They literally just appear like a zigbee device inside that integration.

You may need to reset them before they will pair.
I forget the pattern, but iirc it’s on 2s, off 8s, repeated until you see an acknowledgement flash.
Sometimes, you’ll get one that takes forever, then the next bunch will just hop right on.
I have several Hue hubs I still need to offload, as I sometimes buy the combo packs that include another hub.

I also found that the response time was a lot quicker over direct zigbee than farting around with Signiant/Philips’ API.

The trick is to buy reasonably open devices, then provide the smarts yourself.
If it can talk to / be configured by HomeAssistant, and doesn’t require internet to work, it’ll probably be fine.

That’s indeed useful information!
My boiler control for the central heating has the very useful function of a 30 minute button.
Which means even if I torpedoed HA in the middle of winter, I could still get the house warm.

Turkey’s main source of renewable power is Atatürk spinning in his grave.