-
Notifications
You must be signed in to change notification settings - Fork 710
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
Bosch RBSH-RTH0-ZB-EU Thermostat II switch between heating and cooling #2707
Comments
I am planning to write a quirk to expose all of the endpoints to Home Assistant. For now you can set the available modes by -> going to the ZHA device page I have found the following so far ControlSequenceOfOperation.Heating_Only But there is probably an easier way to query all possible values from the device. Ah, here they are: https://docs.bosch-iot-suite.com/gateway-software/API/modules/com.prosyst.mbs.zigbee.driver.api/com/prosyst/mbs/services/zigbee/zcl/hvac/ThermostatCluster.html |
Hey wow thats great. Would be very nice to see a quirk for this 👏 |
If it is possible you can also add the Installation mode for the heating: 230V, 24V or Boiler and if there are NO or NC valves |
@metallmanu There are also
The others with the 4_Pipes from the specification do not work. No idea what they are for. Anyway, I think the issue is that the only SystemMode settings are
There is not You can find all working Endpoints I could identify yesterday here Feel free to test it out and maybe extend the list. My thermostat seems to have connection issues and I may have missed some. |
Oh, we may not have the same thermostat. I have the TRV for radiators. Not sure if this supports boilers etc. I could maybe support it as well though. |
I have this one: It is for underfloor heating with cable system 230V. |
I see. I just don't see how my radiator valve would be cooling anything. Radiators only heat usually. Really weird! |
When you have a Heating pump instead of Oil, Gas etc. you can let cold water Flow through your heating cycle. Therefore you have to put the thermostat also in cooling Mode, so that the valve is Open when you want a cooler temperature and cold water can flow through your Radiator |
Interesting. That makes sense. Guess it is a quite sophisticated thermostat. It is a pity that I am losing the connection frequently. I have to take out the batteries to be able to access it again. I put back the Tado now that I want to get rid of and will buy a radiator valve tomorrow, so the thermostat can calibrate itself to something. I will then try to implement the quirk. I think the quirk for your device will be quite similar. There may be some endpoints working that don't work on mine and vice versa. Would be good if you could test those endpoints out, see what they return, compile a similar chart and post it here. On the Bosch documentation page you will find some examples. Some of them might be named a little differently though. Ha! It seems like you can download diagnostic information using the button and it will show you all supported and unsupported attributes! |
Yes the diagnostic is in my first post. Do you need more? |
Well, a bit of patience I guess. I have only edited a quirk so far. A have just tried zigbee2mqtt and everything is supported there. Even endpoints that do not work with ZHA. I wonder why that is. Pity that @dmulcahey is not responding atm. He is usually a great help! |
Hi @metallmanu, @jclsn - I stubled accross this thread as I am facing the same issue with my Bosch Thermostat II 230V. Thx to your hints, I created a small quirk which enhances the Thermostat with the possibility to switch it into cooling mode. However the widget now shows an additional button (the one on the left), which seems to be the auto mode, which is not supported by the affected thermostat. Maybe you guys know how to remove that auto mode ? Here is the simple quirk that I have written: |
A quirk only adds missing attributes that don't comply with the Zigbee specification. It does NOT at all determine what you see in Home Assistant. The ZHA code takes care of creating entities for those attributes. There are e.g. different cluster handlers Tuya devices that creates entities for Tuya custom attributes. None of this exists for Bosch and therefore ZHA tries to create entities according to the Zigbee specification. The problem is though that Bosch exposes "Pause", "Manual" and "Schedule/Auto" on one attribute and "Cool" and "Heat" on another. My idea would be to combine these somehow in a Bosch thermostat cluster handler. So you will not be able to fix it from the quirk side. The Bosch cluster handlers have to be added to the HA core, where ZHA lives. Probably here somewhere https://github.com/home-assistant/core/blob/dev/homeassistant/components/zha/climate.py I don't have the time or expertise yet to implement that unfortunately. It is also not documented specifically for ZHA. I guess if you know how to create general entities for HA, which is very well documented, it should not be too hard though. |
Appologies @jclsn, if my comment upset you - I just wanted to share my findings after hours of digging through the repository. I read through the Zigbee Cluster Library Specification and the problem is that the |
@markoberholzer-es No reason to be sorry. I just confused this with the other thread where a few people have asked the same thing over and over. I can also be quite impulsive sometimes. I edited the post to make it easier to understand and sound a bit nicer hopefully :) Yeah, there are different attributes. The ctrl_sequence_of_oper exists for almost every thermostat afaik and is never exposed in HA. If you want to have it, it would probably be best to add it as select entity. https://github.com/home-assistant/core/blob/dev/homeassistant/components/zha/select.py Then there is also the "heat" and "cool" and then "pause", "manual" and "auto". Those should probably be added to the climate entity. I suspect that it is not so easy, but I also could be wrong. I have added you as collaborator on my branch for which I have already created a PR. None of the maintainers has paid attention to it yet though. I think no one has time atm unfortunately |
@markoberholzer-es I did try to install your quirk.
But there is still no entity to switch to cooling mode. Hopefully you have a hint, why it is not working. Thanks in advance! |
Yes, because you need cluster handlers for this, which need to be implemented in the HA core. I have already started doing that, but it is not easy and the ZHA devs are very busy atm.
Btw, @markoberholzer-es did nothing else than set the `CtrlSequenceOfOper` attribute to `HeatingAndCooling` in his quirk. This is not something that is going to be supported any time soon.
|
Hi @docloy - when the quirk is correctly applied, your Bosch Termostat should show the following modes: If that is not the case - are your zha quirks correctly loaded ? Did you apply the following lines to your configuration.yaml?
|
@jclsn and @markoberholzer-es thanks for your reply and your input. In my configuration.yaml I have those 3 lines. But I don't know how to acitvate use the quirk.
And for heating:
At the moment I'm fine with this solution because I have only to switch twice a year. |
…hermostat cluster as config entity, so that the thermostat can be switched between cooling/heating (only). * Note: This is a thermostat that is used with a floor heating system. If cooling or heating should be used is defined by the underlying heat generator (for example a heat pump). Cooling/heating on the thermostat only defines how the thermostat decide if the valve should opened/closed (heat: current_temp<heat_target, cool: current_temp>cool_target).
…hermostat cluster as config entity, so that the thermostat can be switched between cooling/heating (only). * Note: This is a thermostat that is used with a floor heating system. If cooling or heating should be used is defined by the underlying heat generator (for example a heat pump). Cooling/heating on the thermostat only defines how the thermostat decide if the valve should opened/closed (heat: current_temp<heat_target, cool: current_temp>cool_target).
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions. |
Poorly the issue is still open with the new updates of 2024.8 |
Logger: zigpy.quirks.v2 add_to_registry_v2 is deprecated and will be removed in a future release. Please QuirkBuilder() instead and ensure you call add_to_registry(). |
Same problem with Schneider thermostat. It doesn't have a physical button to switch to cooling mode but it definitely support cooling mode (I have an hydronic floor and will need it this summer). This issue is probably common to many thermostats on the market. Both ControlSequenceOfOperation and SystemMode are read/Write attributes. Linking #3587 for cooling to be implemented if someone does the custom quirk. |
Problem description
The Bosch Smart Home Thermostat II Supports heating and cooling in the Bosch Smart Home App. Unfortunately this switch between heating and cooling is not possible through ZHA in Homeassistant. Over climate.set_hvac_mode it is only possible to switch between off and heating
Solution description
The hvac_modes cooling, heating and off are possible to choose
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: