Replies: 12 comments
-
most likely it's not a software bug. Can you give details of the hardware/gateway/circuit you are using, how and where it's installed. Also did you experience similar drop outs in previous EMS-ESP versions? |
Beta Was this translation helpful? Give feedback.
-
Looks like the thermostat is not answering to 0x16F requests. Also there was a 0xBE received from thermostat, which is an actual errorstate. The other devices seems to work proper, there is something wrong with the thermostat. This thermostat is implemented since a long time emsesp/EMS-ESP#128, the telegrams should be right. |
Beta Was this translation helpful? Give feedback.
-
@proddy thank you for updating the issue to "help wanted" 👍
|
Beta Was this translation helpful? Give feedback.
-
Ok, seems the thermostat does not reply to the read of higher offsets. This causes the tx-read errors and emsesp creates a dummy telegram with wrong offset. Because of this the set-telegram 0x165 is not fetched. In first step i've fixed the offset. This dev-build should show up the setpoints and fetch the settings. But will not fix the counting of tx-read-errors. I'm not sure how to handle this strange behaviour of that thermostat. |
Beta Was this translation helpful? Give feedback.
-
@MichaelDvP all good options. A retry with higher offset would be nice, but that's quite a bit of extra code. Personally I prefer just ignoring it and mentioning it in the trace or debug log, only because I'm too busy with other stuff at the moment |
Beta Was this translation helpful? Give feedback.
-
I have updated the FW to v3.4.2b5, it looks like more read tx fails are coming now |
Beta Was this translation helpful? Give feedback.
-
It's only few more errors at startup, when emsesp tries to fetch the other telegrams (which is workking now). |
Beta Was this translation helpful? Give feedback.
-
Thank you for the explanation! |
Beta Was this translation helpful? Give feedback.
-
Sad, so this thermostat has no, or a complete unknown, setting telegram. If you are missing a setting in emsesp for the thermostat, log all or use |
Beta Was this translation helpful? Give feedback.
-
Oh, i see we had this thermostat before in #468 with software 13.05 and telegram 0x165 implemented. Seems your thermostat is a bit older (Ver 13.03) and does not have this telegram. |
Beta Was this translation helpful? Give feedback.
-
here what i got from
|
Beta Was this translation helpful? Give feedback.
-
there are no errors in the log, that is true, the quality is about 80% |
Beta Was this translation helpful? Give feedback.
-
Bug description
The quality of the EMS Reads (Tx) is about 85% with Tx mode HT3, EMS and EMS+ even lower.
EMS-ESP version: v3.4.1
Expected behavior
The quality of 100% 🤓
Device information
Junkers Cerapur ZSB 14-3 A 23 S0000
Additional context
log.txt
Beta Was this translation helpful? Give feedback.
All reactions