That’s what they’re saying - you can use an ESP32 device as a serial proxy without having to do anything special. If you already have a device attached to it you could use the socket:/… syntax below.

Per the integration documentation:

Port

The serial port the TV is connected to. This can be a local device path or a remote serial proxy URL. For example, /dev/ttyUSB0 (USB adapter), socket://192.168.1.100:2000(network proxy), or socket://esphome-device.local:6638 (ESPHome).

Starting in 2023 (and updated over the years) I wrote an automation to auto apply updates every few days based on a bunch of criteria:

• consider all updates: HA, HAOS, add ons, HACS updates (I’d included HACS updates myself before they had integrated with the update framework)
• update is more than 1 or 3 days old (I’m not interested in being an early adopter for the most part)
• ’sensitive’ vs. standard updates (I wait longer for updates to HA, HAOS, Zigbee2MQTT, ZWave2MQTT, few others)
• order of updates, like apply standard HACS updates first, then update others
• logs everything it does
• keeps state, so if there’s a version bump between installs it delays another slot before considering to apply it
• skip all esphome updates by default now (didn’t initially, but don’t see the value in pushing updates to the devices unless there’s a material gain)
• I have controls on it so like if I’m going out of town I pause it until I’m back just in case

I usually get core HA updates to the y.m.2 version around mid-month so I skip teething pains of most new releases. I’ve had to do a roll back once - I’m still not sure why as I just reapplied the update manually and it worked. It has meant that I’ve needed to update parts of my configuration as HA has progressed, but for the most part that hasn’t been a lot of upkeep.

I think HA is still such a moving target, and especially now with AI beating on everything security wise it’s even more important if you expose it to the world. Given HA’s role leaving it unpatched could be opening your home up to being abused.

HA is still a bit of a hobby project and needs a bunch of care and feeding. I do hope that there’s a point when the dev team doesn’t need to reachitect and refactor configuration. Eventually I hope it’ll be more like phones where updates are relatively transparent.

I have air quality (Apollo and AirGradient both running esphome) sensors in a few places in the my home and use them to automate some ESPHome-converted Levoit air purifiers. I also have an AirGradient Outdoor sensor that I use to at least tell me the air quality is bad outside. I do use the outdoor sensor to notify me about opening door and windows to help cool the house (when the outside aq is ok).

My house is pretty well sealed so that’s benefit and a curse - the outside aq doesn’t affect the inside too much, but things like cooking need the air purifiers turned up to really clear. The charts from activities inside give interesting insights.

Wildfire smoke is a yearly occurrence here so I’ve had this set up for a while, I just keep adding to it.

Matter devices should be able to use your current wifi if that’s their network. Otherwise it would use thread similar to Zigbee. I’ve only looked at the ZBT2 as a thread router for connectivity to home assistant so I don’t have a lot of experience here yet with thread but I’ve been using Zigbee for years. Yes thread or Zigbee can interfere with 2.4ghz wifi as they’re in the same band, but my experience is the opposite: wifi has a bigger effect on them then they do on wifi. Zigbee and thread are designed for low power devices so they’re easy to drown out.

I don’t know if there’s a feature difference but I don’t think there should be. I’ve used matter devices on my wifi with no issues and didn’t need a separate router, and when I pick up a thread device I’ll use a zbt2 as the hub.