-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
topic ems-esp/thermostat_data
does not get updated
#268
Comments
can you post your settings? |
Which version did it work on so I can do a comparison? Take a look at https://emsesp.github.io/docs/#/Troubleshooting?id=mqtt-is-not-always-working |
You can download both the settings and info JSON files from the Help tab. Or call it directly via the API using a URL. I'll update the doc here to explain a little better. https://emsesp.github.io/docs/#/Support |
Here it is
and some telegrams from the console:
|
Everything looks fine. I Can't think of what can be causing it. Try the ideas in https://emsesp.github.io/docs/#/Troubleshooting?id=mqtt-is-not-always-working and also look at the Mosquitto logs |
I see some strange things:
normaly emsesp send every minute, this much to low sendings, do you have set Also the log does not show any telegram send to emsesp, it's 2 minutes but no request. And the log does not contain any 0x0A telegram from thermostat, but this telegram holds the roomtemp and seltemp. Can you switch to tx-mode 1 and read the telegrams in telnet: BTW: the 0x0A telegram should be 26 databytes, but we know only 4 of them, there is some more information from thermstat. |
@balk77 any update on this? Do you still want us to look into it? |
Sorry, I was distracted by the year-end activities.... Issue is still present but worked around (I am reading through the Nefit Easy custom component instead of ems-esp). The tx-mode was set at 2, now set at 1 (after the below stats were produced).
Result of
|
I think this is the same as #282, the easy monitor needs to be fetched and this is stopped after a tx-error. |
Ok I'll wait before releasing 331 |
@MichaelDvP that works! Topics get updated after installing the alpha version listed in #294 . Thanks (and also @proddy !!!!!) for your help 👍 and for creating this fine piece of firmware 🥇 |
Bug description
The topic
ems-esp/thermostat_data
does not get updated. Actually, new topics are being issued but with old values. When the EMS devices gets restarted new values are being read and published, but nothing new after that. I own a Nefit Easy thermostat; although I am aware of the limitations this reading used to work properly until I installed 3.3.0.Is there anything I can do to track the issue down?
Steps to reproduce
Reboot of the EMS device results in fresh values. No updates after that. I have a long list of identical MQTT topics in MQTT Explorer.
Expected behavior
Updated temperatures every now and then. It used to work with same hardware with earlier versions of EMS-ESP32.
Screenshots
The MQTT output on
ems-esp/thermostat_data
stayed like this all day.while at the same time:
![Screenshot_2021-12-27-19-32-07-032_nl nefit easy main](https://user-images.githubusercontent.com/10166350/147498738-0ea1aa8f-93a3-4db7-bd9b-5c7c2ff7c441.jpg)
![Screenshot 2021-12-27 at 19 39 00](https://user-images.githubusercontent.com/10166350/147498842-56cd5a4e-63e1-40a1-8c07-3b1ed53a320d.png)
Also the web frontend shows the old values:
Device information
The text was updated successfully, but these errors were encountered: