Replies: 8 comments
-
could be related to https://emsesp.github.io/docs/#/Troubleshooting?id=changing-a-value-works-at-first-but-is-then-reset-to-it39s-original-value ? |
Beta Was this translation helpful? Give feedback.
-
Hi Proddy, Thanks for pointing me to a solution to my problem. However, is this a temporary solution to the problem of the restfull API to the EMS-ESP gateway? It's only recently that I've been experiencing this problem. Will this be fixed in an upcoming update? Regards, Mark |
Beta Was this translation helpful? Give feedback.
-
Hello proddy, If I send the same value (5 degrees Celcius) to both the HeatingTemp and the SelFlowTemp, the HeatingTemp goes to 30 degrees Celcius and the SelFlowTemp to 15 degrees Celcius. Is this coming from the EMS-ESP gateway? Previously, the EMS-ESP gateway took exactly the values that were sent. After receiving the advice, I notice this. Regards, Mark |
Beta Was this translation helpful? Give feedback.
-
I don't know to be honest, there are some default resetting and overrides from other EMS devices. @MichaelDvP knows this area better than I do. What devices are you using (sending your system debug profile will help) |
Beta Was this translation helpful? Give feedback.
-
Hi Proddy, I understand. I have a Nefit Trendline boiler and a Bosch EasyControl thermostat. Apart from the fact that the EMS-ESP gateway cannot read/write the data from the Bosch EasyControl, I do this in a roundabout way. I read the status from HomeBridge, manipulate it via NodeRed and then send it to the boiler via the EMS-ESP gateway. I don't think it's anything weird really. Despite this, the boiler still assumes different values than what is sent from the EMS-ESP gateway. At first I assumed that the Bosch EasyControl was causing the problem, to also send data directly to the boiler. I managed to rule out this cause by only allowing the Bosch EasyControl to communicate via a Bosch EasyControl Adapter. As a result, no data from the thermostat can reach the boiler (directly). Only through editing and control from Node-Red, from a Restfull API. Regards, Mark |
Beta Was this translation helpful? Give feedback.
-
Here my logs;
|
Beta Was this translation helpful? Give feedback.
-
It is very confusing:
|
Beta Was this translation helpful? Give feedback.
-
Hello, I understand that the thermostat itself also sends a HeatingTemp to the boiler and the boiler takes over. However, if I now do this via the EMS-ESP gateway, both the HeatingTemp and the SelFlowTemp assume a different value. This was never before. Therefore I assumed that this was influenced by the thermostat. However, by placing an EasyControl adapter in between, the signal to the boiler is provided entirely by the EMS-ESP gateway. It is therefore strange that these values are adjusted, compared to the controlled one. Regards, |
Beta Was this translation helpful? Give feedback.
-
Hello,
I have had an EMS-ESP32 gateway with (the latest) firmware v3.4.3 for several years now. I control the boiler via the Rest API, by adjusting the "HeatingTemp", which is then taken over by the "SelectedFlowTemp".
If the "CurrentFlowTemperature" is low enough, relative to the "HeatingTemp", with the associated hysteresis, the boiler will start heating.
However, if I do not have a thermostat connected to the EMS, the SelectedFlowTemp falls back to 5.0 degrees. Regardless of what I (continue to) send to the "HeatingTemp". Subsequently, the boiler will therefore not start heating.
What could be the cause of this happening, that it falls back to 5.0 degrees at "SelectedFlowTemp"? The EMS-ESP gateway should also only (and only) be controlled via the Rest API.
I'd like to hear about it.
Kind regards,
Mark
Beta Was this translation helpful? Give feedback.
All reactions