Worcestor Comfort II RF Support #138
Comments
|
The thermostat seems to be compatible with RC100, i've added it to the database, check with new dev. CRC errors are most common on low buspower. If you are on buspower, maybe the RF-thermostat draws more than wired thermostats. If you have a service-jack, try powering with this (jumper change) or try USB-power (jumper removed). If crc-errors stays with external power, check the bus connection and cable. Try different bus-connectors and cable length (not less 25 cm). |
|
Thanks for the quick response! That's certainly picked it up and I can see some values propagating through to Home Assistant! :) Unfortunately, that's where the joy seems to end :-o Whilst the "Current room temperature" seems to be reflecting the display, the "Setpoint room temperature" is always 0º. Looking through the code, Thermostat::process_RC300Monitor() seems to be the function used. It even notes that octed-3 can be zero and the description for octet-6 matches what I'm seeing. Indeed, if I add the following to the end of that function, and finally figure out how to get a working build-environment, I do seem to get actual numbers: I'd ask whether that would be a reasonable patch-request, but having also tried to set a target temperature (via Home-Assistant or 'call thermostat temp 20'), nothing happens (other than appropriate log messages and telegram-tx) — so I wonder if there's something else (perhaps more obvious to you) that mismatches? As for the CRC-errors: yes, I will check the cable and also try the service-jack tomorrow. Thanks. |
|
Seems that this thermostat is not 100% compatible to rc100 (see emsesp/EMS-ESP#249). The check with The 02A5 for this thermostat is very short, maybe we can use the length for checking. But first we have to check how to set the temperature. Can you log a |
|
@stewiem2000 To make the setpoint work for reading and writing we need a feedback from you with the mentioned log. |
|
My apologies! $DayJob and $Life popped-up; I had also hoped to switch over to the service-jack to gain cleaner logs (fewer invalid-CRC entries). In the mean time, here is the requested Show: Log:
Thanks. |
|
Ok, this is a new kind of thermostat, it does not support the telgrams RC300Set(0x2B9), RC300Summer(0x2AF), and RC300Curves(0x29B) Only the RC300Monitor(0x2A5) is used, but with different meaning of the values. It's only a few bytes: We have to figure out the mode and mode_type settings: What modes does the thermostat have? I can not find a manual in web. For the setpoint can you try if pos 6 is writeable. In telnet |
|
Manual: Modes:
Position 6 seems unwritable :( I tried both tx_mode 1 and 2. Same immediate response from the thermostat. |
That's sad, but expected. Normally the monitor telegram is not wrtiable and there is a setting-telegram for the parameters, that is published if a parameter changed. But this thermostat only publishes the monitor, seems that there is no way to write the values. I added the known values for this thermostat as special thermostat type. But i don't know what else we can do to write a value. @proddy, @norberts1 You know more about the different thermostats and telegrams, any idea how to write setpoint? |
|
I'd hope you wouldn't say that, but it fits. Thanks for adding the values, reporting will still be of some use. Do I have any other sensible control options, e.g. "unplugging" the thermostat competely and sending the boiler commands directly? Is that considered a Bad Ideaᵀᴹ? If there's any additional information I can provide, please let me know. |
Normally it is not the best idea to build a own thermostat logic, the commercial thermostats are very fail-safe and control strategy is a lot of work to rebuild. But your CRF seems very simple and it seems easy to replace it. What the CRF do is to measure the roomtemp and calfulate to flowtemp and burnpower and send it to the boiler. This is done in only a few telegrams: That is all i see in this log. There must be also a setting for ww-temperature in telegram 33 or 35. The best solution is to buy a (writable) masterthermostat, placed on the boiler and use the CRF as room temperature remote thermostat. I don't know much about the worcester models, but i think it's possible. |
From further monitoring, it seems the thermostat keeps the same flowtemp (0x55 / 85ºC, or 0x00 when sending "off"), and only modulates the burnPower, so having a dedicated command would certainly aid me replicating its functionality.
On a whim, over the weekend, I acquired a Comfort I RF room thermostat (a CRF100S) with the hope of being able to add it into the system and glean some extra telegrams. Unfortunately, I could not persuade it pair with either/both the CRF200S and/nor the boiler-fitted receiver :( So it looks like you might be right and I shall consider the options of replacing the thermostat or implementing my own, unless @proddy and/or @norberts1 have any further suggestions...? |
|
Hi, I also have a CRF200S thermostat called RF-NSC on ELM Leblanc branding (https://www.elmleblanc.fr/fr/fr/ocs/elm-leblanc/nsc-rf-878577-p/). In the post it is written What can I proceed to at least control On/Off of heating part of the Thermostat if I can control the thermostat ? Thanks for your help. |
|
You could try the latest dev build. No promises though as technically we
haven’t supported the crf200.
https://emsesp.github.io/docs/#/Supported-EMS-Devices
…On Sat, 30 Oct 2021 at 17:32, bed31 ***@***.***> wrote:
Hi, I also have a CRF200S thermostat called RF-NSC on ELM Leblanc branding
(https://www.elmleblanc.fr/fr/fr/ocs/elm-leblanc/nsc-rf-878577-p/).
Controller (HT3) and Thermostat (CRF200S) are not recognized even with the
last version of EMS-ESP32 3.2.1.
[image: image]
<https://user-images.githubusercontent.com/33985224/139539274-35e1270a-715f-49ec-80db-72d4d962352c.png>
In the post it is written We're able to read the mode, current
temperature and setpoint temperature but writing is tricky. but i nothing
is decoded :(
Is it in a dev version or is there another trick ?
log.txt <https://github.com/emsesp/EMS-ESP32/files/7446988/log.txt>
What can I proceed to at least control On/Off of heating part of the
Thermostat if I can control the thermostat ?
Otherwise how could I replace the thermostat to control boiler ?
Thanks for your help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJMO6DVSM2TJZKDQI7I4H3UJQMYBANCNFSM5FI4SVVA>
.
|
Thanks for your quick response. regards |
|
@proddy I also notice some errors in the console Thx |
|
@bed31 you should be at least able to see the details. Without details we can't help you. Have a look at https://emsesp.github.io/docs/#/Troubleshooting |
|
This is really a poor thermostat, not responding to hc2,3,4 telegrams. The error messages should now be fixed (only a few after startup), but it is cosmetic. |
@proddy Sorry I may did not understand your comment :( Controller is not recognized : Boiler : Ok In order to start / stop the boiler with an external thermostat, how can i proceed ? Which mqtt command should i send ? thanks in advance for your help |
looks like the controller is recognized. It has no data, but controllers normally do not publish any data. This is ok.
In your thermostat reading some boiler parameters: thermostat sets flow temperature setpoint: thermostat sets boiler warm water temperature: But the thermostat does not publish it's own values like the CRF200S from @stewiem2000. This was this telegram: |
|
@MichaelDvP Thank you for all these information.
|
|
Please post system info and settings, see buttons on the help page: |
|
Hi,
I have connected my EMS-ESP (an awesome EMS Bus Gateway Premium II (P2) from @bbqkees!) to my Worcester Bosch Greenstar 36CDi Compact Erp combi boiler with Comfort II RF wireless controller and "CRF200S" remote. I'm running the latest dev firmware, "2.2.2b0" via telnet, "2.2.2-dev(38a443e)" from the web-interface.
The boiler seems to be detected OK (I think, certainly getting sensible values out of it), but the thermostat isn't recognised and I'm not entirely sure about the controller, show devices yields
show ems bus information:
From the following log, I'm slightly concerned by the CRC-mismatches, but I can see that dev:0x18 is the thermostat because adjusting its target temperature emits 0x2AF IDs where the third octet (value 0x20) seems to be the call for heat (value 0x21 when wanted, 0x20 when not) and the the last octet (value 0x25) seems to be twice the selected temperature, ie. 0x25 = 37 = 18.0ºC:
I've yet to try sending the boiler commands.
What can I do to help resolve the CRC errors and get my thermostat supported? :)
Thanks in advance!
The text was updated successfully, but these errors were encountered: