Add Buderus RC100(H) support #590
Comments
|
It seems there is something mixed up with heatpump module and remote thermostat. @MichScha Please post the debug information from emsesp-help page, we need the product id of the thermostat. The remote thermostats do not have much values, the control is done by the main thermostat (RC300) and the remote only send actual temperature and, in this case, humidity and dewtemp (frst two bytes in 0x47B) . Actual room temperature is first 16 bits of telegram 0x42B, this is sent to RC300 and RC300 also publishes this temperature as roomtemp. The other bytes of these telegrams are unknown for now. |
|
Jep thats why I am wondering why there is no value for those attributes. Strange is that there is no ProductID present from the device. (The count of bus reads failed is high because I just connected for tx cable a few days ago) Debug |
|
Oh, First you need better tx quality to get the right infos from the devices. Check the cable connection, use thicker cable, try a different tx-mode. |
|
Like I wrote before it related to the missing tx cable (just connected the rx before...) which fixed the whole connection. After a complete restart of the heating system / ems esp the device is now recognized correctly (sorry for that - should have done before!) but the value of humidity seems to be incorrect. Currently it reports 28% but I know from another sensor that it should be around 60%. Could there be an error while decoding the value? |
|
You can try with my dev build.
It's your turn to check the values and determine the right position in the telegrams. We only can add things that user reports and not all is right. The product_id 200, device_id 0x35 was first identified as heatpump outdoor unit, but now it seems more probably that it is the remote thermostat. I don't know, i have a old ems oil-burner system and can not test this. |
|
A missed your first line in the comment. Used the current stable one to catch the changes. Got the first batches with small changes in the values. On what part do I have to look now in specific? You mentioned frst two bytes in 0x047B would be the interesting one. I will try to catch more also for the dewpoint where no other values are changing. |
|
@MichaelDvP with your development build I get the following error |
|
Please refresh browser cache (reload page). |
|
That was the problem ;-) Here a bunch of value changes. The concrete value has been read from the display with the corresponding message for the value below.
How can we interpret those values or how can those bytes be converted to "normal" text? BTW: Have we probably lost the reading for
|
00E7 is the temperature in 1/10°C -> 23.1°C, 09 0A 01 are unknown, check if there is a change if you change operation mode or whatever can be changed on the thermostat.
0E is 14°C dewtemp, 0x35 the humidity 53%, 00 E8 unknown I don't think we have lost values, may they needs a few minutes to show up after an update? |
|
Hm maybe with your experience you can identify something here. It is only possible to
Regarding the lost values I will wait some time but it doesn´t seem to come up. Reflashing the old stable version it is present after a few seconds. |
|
Setting roomtemp is done in master thermostat 0x10 in hc settings: I'll take a second look to the missing values. |
|
Please test with a new build on my GH. I've added the correction to remote thermostat and the remote setpoint to master.
Could you explain exactly what you mean? Maybe with pictures. I don't have a heatpump.
Which device? Emsesp an be set to factory defaults in menu, telnet (format) or via button. Boiler reset command is implemented an can reset blocking errors and mainenance messages. |
|
Just flashed with the dev-build and the device is correctly identified but currently without values. It is also not appearing under customization.
Thanks for clarification, works!
The RC100H does have a humidity sensor (the H) included and is able to provide temperatur and humidity for the heatpump. You need both values when you want to enable the cooling mode in the heatpump. The device has to be placed in a reference room from where it measures those two values and the system is calculating the dew-point. This is very important to get no moisture along the pipes and thats the minimal temperatur you should put in your flow temperatur. (normally you are +3 C over it to be sure). The RC100H can only be used for exactly 1 heating circuit (if you have more you need an additional one. 1 heating circuit can be used for cooling and heating thats not exclusive) and you have to tell the RC100H for which it is measuring the data. Thats what you need to do on the RC100H side. You also have to tell the heatpump that for heating circuit 1 there is a modul that is able to remote control and provides temperatur and humidity.
Hopefully that makes it a little bit clearer?
That was just the last option you can select on the RC100H - reset the device itself - for the sake of completeness |
Oh, that's bad. Values and commands should be mapped to heatingcircuit. Whats the output of http://ems-esp.local/api/thermostat and http://ems-esp.local/api/system.
For all you can select on the RC100H you have to log the telegrams and set this option on the thermostat to see what telegram/value is sent. But an internal function in the thermostat is maybe not accessible via ems-bus. Just try. |
|
Your GHA have been skipped so no release available. http://ems-esp.local/api/system |
No, the last dev is one hour old. |
|
My fault... Now it seems to be a little bit better. One value present |
|
The handlers 42B and 47B are pending, are they send periodically or only on change. Should we fetch these handlers every minute? |
|
They are send periodically How is it currently fetched? When a telegram comes in it updates the value I would expect? |
|
After first send of these telegrams they should be listed as |
|
Hm still pending here. Should I restart EMSESP? |
|
Ahh, it was wrongly mapped to the dest. thermostat 0x10. Please update again. |
|
Looks good! Just checked the values they are also correct
I don´t know how we should treat the heating circuit part because in my case it is hc1 but it could be for someone else hc2, hc3,... Like I said for now I won´t touch this particular setting and change the heating circuit in the device because the heatpump is finally after a lot of research doing what it should. |
|
Please check a new update, i've cleaned up the code, making it more consistent. There should be no change in displaying data. |
Looks good still all values are present and correct.
Not yet as I never used the writing mode, will have tomorrow time to check. |
|
Do we have now a doubling in attributes? I am talking about the temperatur values.
The currtemp is currently relaying on the same device like it is for the remotetemp. I currently don´t know which temperature on the heating pump will be shown if there are more devices that can report a temperature. I would expect it relates to the selected heating circuit that is displayed at that moment. |
|
currtemp is reported from master thermostat 0x10, remotetemp is what 0x38 sends to 0x10, it's the same value it RC100H is correctly configured as remote. |
|
Just a question regarding writing commands. When changing the correction value for temperature I only can verify that value on the remote thermostat. Is it also recognizing that value because what I have understood is that the command will be sent to the master thermostat. |
|
The temperatursensor correction is a telegram stored in remote thermostat, we have to read and write to the RC100H. |
|
@MichaelDvP has some of this gone into the latest 3.4.2 dev release? |
When I change the value in ems-esp the correction value should be updated in the remote thermostat right? I will test it this afternoon. If thats working we can close this issue - works like charm. |
|
Does it work? |
|
Hm unfortunately not. Changing from 1.0 to 1.1 or back doesn´t work. What kind of value will be accepted or expected? 1.1 or 1,1? It doesn´t matter because both don´t work - I have used both values. @MichaelDvP do you need logs for the sended message or what can I do? |
|
Could you please |
|
Okay just tested now and there is no telegram like the one you are describing. "READ Mode" is deactivated in settings and I have changed the value / watched for the telegram. There is just nothing different from the normal "update" telegrams. |
|
Please make sure you use the latest dev build, in doubt reinstall. Select log all and change the value. Post the log and your system info here. |
|
Latest dev did the trick. Imho everything works now like expected. Closing this issue. Great work! |
Hi, I have a combination of
The device RC100(H) seems to be recognized as HP module and has a humidity sensor integrated in contrast to the RC100 device
Captures telegrams
The identified information in the customization page shows the following two attributes which make perfectly sense
What can I do to support the device?
Thanks!
The text was updated successfully, but these errors were encountered: