Closed Tillmann-E closed 2 years ago
what are your system settings - are you publishing the data via MQTT or polling the API and at what frequency? If it's "on change" then perhaps EMS-ESP is not detecting a change. Does it always happen after the same # hours?
Next time you notice no data is coming in go to the console do a read 10 23a
to see if there is actual data.
I'm publishing every 10 seconds via MQTT to home assistant. The number of hours are not always the same.
I'm going to check this next time, but I think there ist no actual data, because the value in the EMS-ESP UI hast also been static.
Edit: Sorry, missunderstood you. I think there will be actual data on the thermostat. I guess there is an error in reading the telegram and after that it is ignored.
yes, we need to figure out if the interface board or the Rx UART has stopped working
The issue is that the boiler stops replying to 0x23A here:
2022-01-04 00:32:17.354 E 62: [telegram] Last Tx Read operation failed after 3 retries. Ignoring request: 8B 90 FF 00 20 01 3A
This generates a empty dummy reply and toggle the fetch of this telegram. After this the telegram is not fetched anymore. We have introduced this, because some boilers/thermostats does not reply to some telegrams (or version request) and emsesp will endless query this telegrams. This dummy reply is also used for Tado- and modem-detection.
Maybe 3 read-retries are not enough, or too fast if the bus is currently disturbed. We can try with a delayed send of the last retry, like the delay for post-send-queries, insert here:
delayed_send_ = (retry_count_ < MAXIMUM_TX_RETRIES) ? 0 : (uuid::get_uptime() + POST_SEND_DELAY);
Or, better or in additition, set a marker to telegram function if we have received a non-empty telegram and prevent the toggle afterwards.
this ist the result to read 10 23a
001+21:08:32.493 N 0: [emsesp] Thermostat(0x10) -> Me(0x0B), RC300OutdoorTemp(0x23A), data: 00 14
with an outdoor temperature of 1.8 °C a damped outdoor temperature of 2.0 °C seems fine.
@Tillmann-E did you try the latest v3.4 build to see if it resolved your issue?
I updated to 3.3.1 a week ago and it's working now. Thank you!
Bug description Reading the damped outdoor temperature (thermostat) fails after a couple of hours. After restarting its working again for some hours.
Steps to reproduce Has been working with version 3.1.1. Error occurs since update to version 3.3.0.
System log for the time of the error. Last value received should be around 2022-01-04T00:04:20.000Z.
Expected behavior Constant values for damped outdoor temperature. Screenshots