Proddy

I can't reproduce. I used connected the EMS-ESP to a Wifi AP, then switched off the AP and back on after a few minutes. As soon as the WiFi reconnected...

Can you try the latest beta? Looks like you're using an older firmware. Not sure it'll make a difference but worth trying. The problem we need to fix is why...

ah ok. The emsesp_info.txt file which you can download from the Help page (latest beta) would be useful as it shows the settings and also your WiFi strength (called RSSI)....

Looks like the MS100 is sending out on new telegrams unknown to EMS-ESP (0x7a9-0x7ad, 0x7b1, 0x7e0). We''ll need to work together to reverse engineer and decipher them

It's also normal not to see any data from the controller. It's been removed in v3.4 from the UI to avoid confusion.

Do you think you could summerize all the new values you found into one table, so we can implement them?

I get this all the time too and haven't been able to figure out how to remove the old ones. Usually, remove all the discovery entries from MQTT and restarting...

but saying that, I haven't seen this problem in the last month or two with the latest v3.4

Are the entities there in the ems-esp? (Web, api, mqtt, console etc) or just missing in ha?

and using MQTTExplorer and searching for `outdoortemp` doesn't show a `homeassistant/sensor/ems-esp/boiler_outdoortemp` topic?