Skip to content
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.

RC35 Set room temperature value and Current room temp value missing #86

Closed
majo551 opened this issue Apr 4, 2019 · 17 comments
Closed
Labels
question Further information is requested

Comments

@majo551
Copy link

majo551 commented Apr 4, 2019

Bug description
Set and Actual room temperature from RC35 thermostat is not read. The value provided in telnet using info is "? "

Steps to reproduce
*sending "info" in telnet *

Expected behavior
real values to be seen for set and room temperature

Screenshots

Thermostat stats:
Thermostat type: RC35 (ProductID:86 Version:21.08)
Setpoint room temperature: ? C
Current room temperature: ? C
Thermostat time is 19:32:19 4/4/2019
Mode is set to auto

Additional context
Full output

info
EMS-ESP system stats:
System logging set to Verbose
LED is on, Silent mode is off
0 external temperature sensor connected
Thermostat is enabled, Boiler is enabled, Shower Timer is disabled, Shower Alert is disabled

EMS Bus stats:
Bus Connected=yes, Tx is active, # Rx telegrams=350, # Tx telegrams=0, # Crc Errors=55

Boiler stats:
Boiler type: Buderus GB172/Nefit Trendline (ProductID:123 Version:04.08)
Hot tap water: off
Central heating: off
Warm Water activated: on
Warm Water circulation pump available: on
Warm Water comfort setting: Eco
Warm Water selected temperature: 57 C
Warm Water desired temperature: 70 C
Warm Water current temperature: 44.1 C
Warm Water current tap water flow: 0.0 l/min
Warm Water # starts: 1420 times
Warm Water active time: 32 days 19 hours 0 minutes
Warm Water 3-way valve: on
Selected flow temperature: 5 C
Current flow temperature: 22.8 C
Return temperature: ? C
Gas: off
Boiler pump: off
Fan: off
Ignition: off
Circulation pump: off
Burner selected max power: 0 %
Burner current power: 0 %
Flame current: 0.0 uA
System pressure: ? bar
System service code: 0H (203)
Heating temperature setting on the boiler: 65 C
Boiler circuit pump modulation max power: 100 %
Boiler circuit pump modulation min power: 10 %
Outside temperature: 16.1 C
Boiler temperature: ? C
Pump modulation: 0 %
Burner # starts: 7759 times
Total burner operating time: 333 days 22 hours 0 minutes
Total heat operating time: 301 days 3 hours 0 minutes
Total UBA working time: 1334 days 18 hours 37 minutes

Solar Module stats:
Collector temperature: 42.8 C
Bottom temperature: 43.0 C
Pump modulation: 0 %
Pump active: off

Thermostat stats:
Thermostat type: RC35 (ProductID:86 Version:21.08)
Setpoint room temperature: ? C
Current room temperature: ? C
Thermostat time is 19:44:21 4/4/2019
Mode is set to auto

@majo551 majo551 added the bug Something isn't working label Apr 4, 2019
@proddy
Copy link
Collaborator

proddy commented Apr 4, 2019

I assume you're using the 1st heating circuit. Do set log v and thermostat read E3 and see if a telegram comes back.

@majo551
Copy link
Author

majo551 commented Apr 4, 2019 via email

@proddy
Copy link
Collaborator

proddy commented Apr 4, 2019

the thermostat read E3 command fetches the temperatures from the RC35. In your case it returns nothing back which is why it shows up as '?'. Can you try two more things

thermostat read 48 (for HC2)
to see if anything comes back

and the mother of all tests is log t and leave it for 1-2 minutes and see what messages are being broadcast by your RC35.

@majo551
Copy link
Author

majo551 commented Apr 4, 2019 via email

@majo551
Copy link
Author

majo551 commented Apr 4, 2019 via email

@proddy
Copy link
Collaborator

proddy commented Apr 5, 2019

sorry, made a typo. It's 3E and not E3. But I can see the values are coming in nicely in the logs you sent.
So right now I'm not sure exactly what the problem is anymore. Are you saying if the thermostat mode is in auto and you do a 'refresh' the temperatures don't get updated? It would help if you make an easy reproducible test so you and I can find out what is not working. And look at the code too and submit a pull request when any necessary changes.

@proddy proddy added question Further information is requested and removed bug Something isn't working labels Apr 5, 2019
@majo551
Copy link
Author

majo551 commented Apr 5, 2019 via email

@lobocobra
Copy link

lobocobra commented Apr 5, 2019

If you have 2 HC, then I would assume that your heating is on the 2nd one and if you have a floor-heating you have for sure the same issues like I had.
=> The current firmware does only support HC1 for a RC35

I had the same issues like you and solved them by adapting the firmware (PR pending). Meanwhile you might want to give a try to my changes, which can also be found here....
https://github.com/lobocobra/EMS-ESP-HC2

For me all is now working using my firmware and internal commands "thermostat mode xxx" etc work again (and I added some additional commands).

@proddy
Copy link
Collaborator

proddy commented Apr 6, 2019

@lobocobra I've merged your changes into the latest dev. Thanks for the graet work.
@majo551 still not sure why the values aren't coming in. can you try again with the latest dev branch. I don't have an RC35 so cannot check

@lobocobra
Copy link

lobocobra commented Apr 7, 2019

@proddy many thanks for merging.

I shortly checked the new code and it works partially....

MQTT

  • publish new mqtt messages => woks! displayed values are correct
  • thermostat mqtt reg. mess. => thermostat is not coming all 2 min, only when the values are changed
    this is a problem if you work with OpenHab
  • change temp by mqtt => does not work

CONSOLE

  • thermostat temp => works! on console
  • thermostat mode => works! on console
  • thermostat stats => does not display any temperatures

I will check which part of the adapted code does the difference.
@majo551 can you please check what works for you?

@proddy
Copy link
Collaborator

proddy commented Apr 7, 2019

thanks for testing.

change temp by mqtt => does not work - I confirm it works for me on a RC20. What do you see in the lof?

thermostat stats - this also works for me and I don't see why it shouldn't for an RC35. What do you get printed exactly?

thermostat mqtt reg. mess - so you want to always publish thermostat temperature values even if the values haven't changed? The logic now only sends if there is a difference since the last measurement.

@lobocobra
Copy link

lobocobra commented Apr 7, 2019

:-) While I still am searching for the reasons, let me meanwhile answer your questions....

  • change temp by mqtt => function CMD_daytemp,nighttemp,holidaytemp look like they were not subscribed.
  • thermostat stats show a "?" and no values. The reason here is, that only 1 of the 2 values have in my setup a value as I have no "current room temparature" sensor.
  • thermostat mqtt reg. mess
    => I fully understand the logic behind your code and its in general good. But if you have with Openhab a webinterface, then you need to have the values confirmed once a while, if not you will get empty values after a Openhab restart until you re-change the temps, which happens maybe all 4 month? This is why I had activated that all 120 sec, the status was published.

@lobocobra
Copy link

I finally found the problem and will make a new PR. :-)
=> I subscribed the new commands in MQTT
=> found what code sniplets were needed to have the thermostat stats working
(if you have a floor - heating guided by external temp (standard setup) then you do not have the temp sensor activated
=> By increasing the periodicity of the thermostat message over MQTT, openhab works again after a restart.

BTW.... I get some good programming lessons here by looking at what and how you corrected my sniplets. Many thanks for that. :-)

@lobocobra
Copy link

@majo551
Can you test the latest DEV code made by proddy and tell us, what is working/not-working?

As you have a similar setup to me, I believe that almost everything should workd

@majo551
Copy link
Author

majo551 commented Apr 14, 2019 via email

@proddy
Copy link
Collaborator

proddy commented Apr 14, 2019

the 33 vs 35 in that website is just a typo I think. So would it be useful to add this feature to this project too, like activate/deactivate the DHW once? I don't have an RC35 so never considered adding it. If so please create a new enhancement request.

Can we close this issue if you have the temp values coming in correctly now?

@majo551
Copy link
Author

majo551 commented Apr 14, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants