Regular poll requests for invalid telegrams are within error log about ems-esp32

[tp1de]

I am using a S3 gateway from @bbqkees. I am actually getting much less errors now since I changed to EMS, but nearly every day a WiFi or MQTT or NTP disconnect. Reconnecting is working.
I forgot to switch off auto channel in my Fritzbox - It was due to a switch in WiFi channel. I changed it now.

I am not in my vacation house anymore and I can observe only from remote. (Home assistant with MQTT is installed on a Raspberry Pi 4 locally). Everything is running stable - I just observed the differences to my home setup.

[MichaelDvP]

Are this all logged errors, or only some of them?
There are some boiler requests for telegrams 0x14, 0x26, 0x14, 0x33. The two 0x14 happen 14:04 and 14:41, so it is not every fetch (every minute). Have you tried read 8 14 if you get an answer?
Same for the thermostat requests, often 0x294 and 0x2B9 and some others.
Please post the system info. Have you tried with a different tx-mode (what mode are you using)?

[tp1de]

I was using EMS+ until now. I changed now to EMS mode.
Seems to work better.
I need to observe a bit longer. I had a reboot during the night. Why?

The Moduline 2050 thermostat seems to be quite different from RC200.
RC200 is EMS+ and 2050 is EMS 2.0.

[tp1de]

@MichaelDvP anything changed in 3.6.5-dev.18?
I do get less errors now, but still 5 errors in 3 1/2 hours. (using EMS instead of EMS+)

If I test the telegram types with telnet, I always get a response with data.
Just for RC300Summer2(0x0471) the data is empty.

The EMS-Bus quality is 100%. Just this 5 errors reported.
Could it be a timing problem within ems-esp poll read requests?

Or might this error messages be related to the S3 build?

[proddy]

In dev18 Michael did this PR (#1661) to ignore fetches if they're empty after 5 minutes, to stop the log spamming. this is the only change.

[MichaelDvP]

But this change have no effect to the above listed errors. The errors happen random and there are a lot of valid receives between. The fetch is only canceled if there is not a single valid telegram of this type in 5 minutes. I've asked for system info (i always ask for it and get no answer). In this we can see if the telegrams are lsted as received.

[tp1de]

systeminfo.txt

[proddy]

ok, I'll close this for now then.