[Device Support Request] Full implementation of BOSCH Radiator Thermostat II (BTH-RA) #2476
Comments
|
After finally switching to a SkyConnect, I want to ditch my Bosch SHC but without a working quirk, I cannot fully control the thermostat. Please prioritize this. If needed, I might be able to provide neccessary information about the device. |
|
Same from me, If Information are neede, I'm happy to help, for the Bosh Thermostat 2 and the BOSCH Smart Home Roomthermostat |
|
I tried to connect the BOSCH Radiator Thermostat II today. On multiple attempts it connects each time, but most times without any entities. It only connected once with entities (battery 100% HVAC), but they didn't work. |
|
It worked for me. What you do is first you use the zha.permit zu give it the adress and installcode that is inside the battery lid. That you need to go in HA to adding new Zigbee devices. Then you reset the Themostat. (Hold the button while insterting the batteries till it blinks orrange.) Lastly press the button ont the thermostat once more so it enters pairing mode. |
Did this each time. I’ve got 53 working zigbee devices, but this one isn’t working. I bought it to replace a Tuya thermostat, even that worked okay (only battery drained every 2 months). |
|
I actually want to move awy from bosh for the don't hold the Set temperatur but hat up and cool down for about 2 degree all the time |
Same for me, it only holds the temperature, when I frequently update the Set temperature, which is Also, the Z2MTT dialog says for element With some tricks (setting up the thermostat target values about every 30 minutes reflecting the room temperature as needed) I got the thermostat working for me, but it is not very handy and intuitive. So, it seems there are some small bugs in the Bosch Thermostat Z2MTT implementation. I also could help with screenshots, experiences and I can support with testing. |
|
@Samueras @ulrichkamp61 @EverybodyElse Regarding the overshooting temperature: I believe this is intentional, to compensate that close to the heater the temp will rise very fast but not in the rest of the room. I have some trv's with external sensors that do not show this kind of wave overshooting the limit set. regarding the remote temp: As far as i can see, home assistant tracks "remote" and "current" temperature, but it is the same value all the time. So current is just mirroring remote values. I have not tried to deactivate the remote temp (because it will just keep the last state forever till reboot of home assistant), but it might end in mirroring an unavailable state - and the documentation on z2m means you have to reset the trv to enable local measurement again? I run these trvs on z2m now, which works as expected. But there is major setback in my installation: The device (without hub) has a build in schedule that cannot be wiped (as i do not know how, at least). this would be annoying but could be overcome with a simple time based automation. but it calls this in-device temperature target also every time when switched to auto mode… This has nothing to do with zigbee but the firmware itself. For any one interested, I made a rather big flow in node red (based on z2m) with this key capabilities:
I would be interested in collaboration and further joint development, although it is still work in progress and documentation limited..just pm me |
|
Here is all the relevant information I could gather. Maybe OTA would also be relevant for updates, but the endpoint is quite complicated. I will start writing a quirk this week. This thermostat deserves full support! Signature:
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4617, maximum_buffer_size=127, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": "0x0104",
"device_type": "0x0301",
"input_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x0004",
"0x0020",
"0x0201",
"0x0204",
"0x0b05"
],
"output_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "BOSCH",
"model": "RBSH-TRV0-ZB-EU",
"class": "zigpy.device.Device"
}
Endpoints:
Basic:
manufacturer: BOSCH
model: RBSH-TRV0-ZB-EU
generic_device_class: GenericDeviceClass.Lighting ???
generic_device_type: GenericDeviceType.LightBulb ???
Thermostat (Endpoint id: 1, Id: 0x0201, Type: in)
Attributes:
ctrl_sequence_of_oper (id: 0x001b)
values:
- ControlSequenceOfOperation.Heating_Only
- ControlSequenceOfOperation.Heating_With_Reheat
- ControlSequenceOfOperation.Cooling_Only
- ControlSequenceOfOperation.Cooling_With_Reheat
local_temperature (id: 0x0000)
read-only: yes
format: 2050 (20.5°)
local_temperature_calibration (id: 0x0010)
read-only: no
format: 25 (2.5°)
range: -50 to 50
max_heat_setpoint_limit (id: 0x0016)
read-only: no
format : 500 (5°)
range: 500 - 3000
min_heat_setpoint_limit (id: 0x0015)
read-only: no
format : 500 (5°)
range: 500 - 3000
number_of_daily_transitions (id: 0x0022)
read-only: yes
format: integers
number_of_weekly_transitions (id: 0x0021)
read-only: yes
format: integers
occupied_cooling_setpoint (id: 0x0011)
read-only: no
format : 500 (5°)
range: 500 - 3000
occupied_heating_setpoint (id: 0x0012)
read-only: no
format : 500 (5°)
range: 500 - 3000
setpoint_change_source (id: 0x0030)
read-only: yes
values:
- SetpointChangeSource.External
- SetpointChangeSource.Schedule
start_of_week (id: 0x0020)
read-only: yes
values:
- StartOfWeek.Monday
- StartOfWeek.Tuesday
- StartOfWeek.Wednesday
- StartOfWeek.Thursday
- StartOfWeek.Friday
- StartOfWeek.Saturday
- StartOfWeek.Sunday
system_mode (id: 0x001c)
read-only: no
values:
- SystemMode.Heat
- SystemMode.Cool
Commands:
clear_weekly_schedule (id: 0x0003)
PowerConfiguration (Endpoint id: 1, Id: 0x0001, Type: in)
battery_alarm_mask (id: 0x0035)
read-only: no
format: integer
values:
- 1
- 0
battery_alarm_mask (id: 0x003e)
read-only: yes
format: integer
battery_percentage_remaining (id: 0x0021)
read-only: yes
format: integer
battery_quantity (id: 0x0033)
read-only: yes
value: 2
battery_size (id: 0x0031)
read-only: yes
value: BatterySize.AA
battery_volt_min_thres (id: 0x0036)
read-only: yes
value: 22
battery_volt_min_thres (id: 0x0036)
read-only: yes
value: 22
battery_volt_thres1 (id: 0x0037)
read-only: yes
value: 23
battery_volt_thres2 (id: 0x0038)
read-only: yes
value: 27
battery_volt_thres3 (id: 0x0039)
read-only: yes
value: 29
battery_voltage (id: 0x0020)
read-only: yes
format: 27 (2.7 V)
UserInterface (Endpoint id: 1, Id: 0x0204, Type: in)
keypad_lockout (id: 0x0001)
values:
- KeypadLockout.No_lockout
- KeypadLockout.Level_1_lockout
temperature_display_mode (id: 0x0000)
values:
- TemperatureDisplayMode.Metric
- TemperatureDisplayMode.Imperial
|
Interesting! I don't have this issue. My heating setpoint is at 21°C and it stops at 21°C. What is your value for |
|
I've just purchased three bosch thermostats and was able to pair them using the QR-Code with ZHA. However I only have a couple of sensors there: temperature, mode (heat an off) , hvac(unknown) and battery. LQI and RSSI are not available. |
|
@coxtor Yes, I am currently writing a quirk to support it. It should be ready in the coming weeks. This thermostat actually supports even valve opening from 1-100%. Really nice! |
|
@jclsn Very good 👏 I'm really looking forward to being able to use more functionalities. |
You just became my personal Hero. |
If I can contribute with any log/data from running these on z2m, just let me know. Will gladly assist. |
No need. Everything is in the Z2M repo. I just need to find time. We have a lot to do at work atm. |
|
@jcsln willing to donate a beer (ASTRA, Best city you live in :)). 12 thermos are waiting for full support. |
|
@wallenium There are better beers if you ask me ;) So I have implemented the missing attributes and they react correctly If you want to try it out, add it as a custom quirk as described here, then click on the three dot menu -> manage devices and make the setting on the I still have to expose the attributes correctly to Home Assistant. Bosch's |
|
@jclsn You are right. But none which has a connection to this city ;) Short question: Seems to work. Do you know the setting for temperature offset? Need to set 1.5 degrees offset... ;) |
|
@wallenium The Regarding the beer, there are plenty of good other beers from private breweries in Hamburg: Ratsherren, Wildwuchs, Gröninger |
|
You are right. Favorite is Ratsherren. I will try. |
|
That is what I mean by exposing the attributes to HA. I don't know how to do that and the Zigpy code is not very intuitive. There is a guide on writing quirks, but it merely scratches the surface. I am in contact with one of the main developers, but he seems to live somewhere in America and only responds when we are about to go to bed. So a fully working quirk may take until Christmas. Sorry, I would also like to accelerate this somehow! |
|
Just wanted to say thanks @jclsn for working on this. I installed the quirk and like expected, it works for everything that worked before. For me, the only thing I really need added is the off mode. Though it seems there is no real "off" in the Bosch implementation. At least I did not find any working one. |
|
@pdsccode No, there is this attribute I called Anyway, |
|
Ah, good to know. But it seems I am either blind or too dumb. I can not find the attribute you mention. And my device page look like this: May I have missed something? EDIT: I just now saw it in the device management and was able to set it to pause. And after re-reading your comment, I think I understand that this is not yet available via another way. |
|
Yes, seems like I will have to implement the entities from the ZHA side. |
|
can anyone tell me here how i could use the remote temp? I can put a value in, but i would like to use a value from my sensor, like sensor.kitchen_roomthermostate_temp. I have some GoveeLife/Govee thermostates for my rooms which report me the temp of the room. Much accurater then the bosch one which is directly under the window / next to heater. |
|
@JericoPablo i think you could use better Thermostat for this |
|
@JericoPablo I recommend not doing that. There is a note in Zigbee2MQTT code that says you have to take out the batteries and reset the thermostat once you have set this attribute. Therefore I will not implement this functionality. You will be able to do all of this with Home Assistant, once the thermostat is fully integrated. |
|
I btw just wanted to say that I currently don't have the time and energy to fully implement this. I have been trying over the course of the last thee weeks, but I am just getting sporadic responses from the maintainers, which is not enough, as I am not an experienced Python or HA developer. If you want your thermostat to fully work, just use Zigbee2MQTT. It is a far more active project and all functionalities are implemented there! |
|
Thanks for the effort. For now i have switched back to z2m and the thermoststrs are working great. |
|
Thank you @jclsn for the response. I'm already using z2m I thought maybe if it's a sensor which delivers data continuously it would work. But I guess I'll wait till it's fully supported in HA. |
|
@JericoPablo You can also use https://community.home-assistant.io/t/advanced-heating-control/469873 It has a field for an external temperature sensor and much more |
|
Hello all, I tried to get the quirk implemented with the advise of @jclsn but I failed. What I did is the following:
This is the result I am getting:
Any ideas, what I miss? Thank you! |
You cant just pair it, You need to go to developer options, services. Tick the box for QR code and input the code from the QR code on the TRV under the batteries. I've paired fine like that (I scan with a phone, save to google keep and then just do the rest by copying it back on a PC :) - but any way you get the exact code into the QR code option will work |
first of all thanks for the answer for my other question, but since im not that often on github i just saw it. Im facing the same "issue" about overshooting. Sometimes it even goes below the temp i set for half degree and starts then to heat. Its not a huge issue for me but if there is any fix for this i would of course be happy 😄 sometimes one of my TRV gets stuck exactly on the temp i set and it continuesly heats but doesnt goes above the temp. I guess thats how its supposed to be? But the rest of them always has this rollercoaster like thing |
I noticed, that the internal time schedule is always playing around with the configured temperature and therefore I cot similar fluctuations. I did a dirty fix where I set that thermostat to the target value every 30 min. That seems to fix the problem... Not 100% sure if this is the problem... It seems to me that the here thought of implementation would fix a lot of these issues. I hope someone can spare the time soon, I'm very thankful for all your work 🙏 |
take a look here, to see what has been changed in the device converter lately (1.35.1) to address the issue: #6761 and #6742. Please take a look here too, about a possible change for the system mode of the trv: #6995. |
|
@dierochade I have started adding the cluster handlers to the core with the help of @dmulcahey. He is also pretty busy unfortunately. A few attributes are already working, but my coordinator is failing all the time. Just ordered a new one. Anyway, even if I did finish it soon, it would probably not get merged into the core before the winter is over... |
|
After getting the thermostat integrated I came across another issue: Adressing the thermostats temperature is working fine. However, the HLK-action is not working properly: 
The current temperature is far below the set temperature, however, it is still in heating mode. Do you have any suggestions? |
you are just misinterpreting the information: heating means: manual mode, opposed to off (and auto). It does not say anything about the valve position. Take a look at the attributes of the climate entity under developer tools/state. I am not sure what is exposed in zha at the moment (migrated to z2m), but there you will see the relevant device states… |
|
Great, that makes it clear! Thank you very much! As I am still working with ZHA am I right, that there is no state giving me the information about the valve position correct?
|
Technically this is true, but pi_heating demand is closely associated cause the device algorithm derives the valve position from this. It’s not linear though (only boost opens 100 for instance) and there is some more proprietary logic (as discussed on herdsman converters), but imho for normal use pi heating demand will do. |
|
I will implement the |
|
@jclsn have you considered adding remote_temperature attribute to your quirk? It can be used with some automation, to set the measured temperature from external sensor, like that: BTW |
|
I have a Bosch Room Thermostat II - 230V (RBSH-RTH0-ZB-EU), which has similar endpoints and attributes. I used zha_toolkit to scan for all availble attributes and made them available through a quirk: I still need to figure out the name/function of those addional attributes and their allowed values. For now I just named them according to their IDs (e.g. attr_0x4022): Maybe someone with a Bosch Controller can help to get the mapping? I don't think we are going to need Entities for all attributes, but at least have the attributes mapped and accessible from ZHA to control the device setup. We can do the same for the Radiator Thermostat II if someone could perform a scan in zha_toolkit and share the report. |
|
Hi! Many thanks for starting this quirk! Here is an updated version that converts from Bosch's operating_mode to HA system_mode. It is my first attempt at messing around with ZHA quirks, so it might not be perfect. What I tested and works:
|
|
@mrrstux Thank you, I will try it out soon. Pretty busy atm EDIT: Just tried it out. Seems to work, although I am getting an error message Tbh, I am not really motivated to continue working on this atm. Feel free to contact @dmulcahey and see if he can help you finish it. I could also push my progress on core somewhere, so someone else can continue. |
|
Here is a version quirk_v2_rbsh_trv0_zb_eu.zip that displays extra controls for:
Since I could not find specific strings inside HA for these, one would need to name/rename each in HA. @jclsn Sorry to hear that you encounter issues. Maybe they go away with this new version. If not, a more complete trace might help with the investigation. |
|
Latest version: #2808:
|
|
Anyone here who would be willing to help the whole community by adding some easy to follow how-to instructions in the ZHA integration documentation for new users pairing (joining) Zigbee devices that require install_code and/or qr_code please see here: https://www.home-assistant.io/integrations/zha#action-zhapermit and https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/zha.markdown That is, add some simpler step-by-step notes similar to these instructions copied from Zigbee2MQTT devices documentation: Pairing Zigbee devices that require an install-code or QR-code1. To pair this device you have to install the device via its installation code. I like suggest that it might be a good idea to put that in its own sub-section, or maybe the ZHA developers might feel that it belongs in the troubleshooting section(?). https://www.home-assistant.io/integrations/zha#adding-devices Also link to the ZHA limitations section which state that install_code is only supported with Silabs and TI Zigbee Coordinator's or or just add a comment like this; Note! The current version support is limited to using QR-codes and install-codes for secure Zigbee device provisioning/commissioning with devices from Aqara, Bosch, Consciot, and Embrighten. You also need to use a Zigbee Coordinator that is based on Silicon Labs or Texas Instruments Zigbee stacks. https://www.home-assistant.io/integrations/zha#limitations PS: Also see this related discussion thread in Home Assistant community forum to understand why users find this complicated: https://community.home-assistant.io/t/bosch-thermostat-2/492845/ PPS: I do not personally own any Zigbee devices that require install-code or QR-code to be paired/joined but I have seen the question being asked enough these days that I think that the ZHA integration documentation could do with some simpler step-by-step notes for beginners. |
Problem description
I use skyconnect+zha.
I am able to pair the device using zha.permit with install code and source-ieee.
It then shows up with 4 entitys:
(screenshot below)
[button.bosch_rbsh_trv0_zb_eu_identify]
[climate.bosch_rbsh_trv0_zb_eu_thermostat]
[sensor.bosch_rbsh_trv0_zb_eu_battery]
[sensor.bosch_rbsh_trv0_zb_eu_hvac_action]
I have got two main issues:
The state of climate.bosch entity is always "heating". If I change the target temparature I can hear the motor of the device closing/opening the valve, but it doesnt change the state.
If I do set the state manually in the developer tools, it changes but switches back after some seconds.
Besides, the HVAC action (entity 4) is shown as "unknown" all the time.
Most attributes are missing
From the integration via z2m it is known that there are many more attributes, some are importat/useful:
window open, boost, position of the valve, temperature offset, disabling of internal temp sensor, many more ++
As far as I understand, these attributes can be manipulated via a set command in z2m....
Additional wish
The device got a nice led color ring that can show status. I do not know if the led can be manipulated or is controlled locally by the device solely?
Solution description
Quirk?
Screenshots/Video
Screenshots/Video
Device signature
Device signature
{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4617, maximum_buffer_size=127, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": "0x0104", "device_type": "0x0301", "input_clusters": [ "0x0000", "0x0001", "0x0003", "0x0004", "0x0020", "0x0201", "0x0204", "0x0b05" ], "output_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "BOSCH", "model": "RBSH-TRV0-ZB-EU", "class": "zigpy.device.Device" }Diagnostic information
Diagnostic information
{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2023.7.1", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.11.4", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "6.1.34", "supervisor": "2023.07.1", "host_os": "Home Assistant OS 10.3", "docker_version": "23.0.6", "chassis": "vm", "run_as_root": true }, "custom_components": { "dreame_vacuum": { "version": "v0.16.4", "requirements": [ "pillow", "numpy", "pybase64", "requests", "pycryptodome", "python-miio>=0.5.6", "py-mini-racer" ] }, "hacs": { "version": "1.32.1", "requirements": [ "aiogithubapi>=22.10.1" ] }, "nodered": { "version": "1.2.0", "requirements": [] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "after_dependencies": [ "onboarding", "usb" ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "config_flow": true, "dependencies": [ "file_upload" ], "documentation": "https://www.home-assistant.io/integrations/zha", "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "requirements": [ "bellows==0.35.8", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.101", "zigpy-deconz==0.21.0", "zigpy==0.56.1", "zigpy-xbee==0.18.1", "zigpy-zigate==0.11.0", "zigpy-znp==0.11.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 59249, "manufacturer": "BOSCH", "model": "RBSH-TRV0-ZB-EU", "name": "BOSCH RBSH-TRV0-ZB-EU", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4617, "power_source": "Battery or Unknown", "lqi": 255, "rssi": -63, "last_seen": "2023-07-15T08:31:40", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4617, maximum_buffer_size=127, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": "0x0104", "device_type": "0x0301", "input_clusters": [ "0x0000", "0x0001", "0x0003", "0x0004", "0x0020", "0x0201", "0x0204", "0x0b05" ], "output_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "BOSCH", "model": "RBSH-TRV0-ZB-EU" }, "active_coordinator": false, "entities": [ { "entity_id": "button.bosch_rbsh_trv0_zb_eu_identify", "name": "BOSCH RBSH-TRV0-ZB-EU" }, { "entity_id": "climate.bosch_rbsh_trv0_zb_eu_thermostat", "name": "BOSCH RBSH-TRV0-ZB-EU" }, { "entity_id": "sensor.bosch_rbsh_trv0_zb_eu_battery", "name": "BOSCH RBSH-TRV0-ZB-EU" }, { "entity_id": "sensor.bosch_rbsh_trv0_zb_eu_hvac_action", "name": "BOSCH RBSH-TRV0-ZB-EU" } ], "neighbors": [], "routes": [], "endpoint_names": [ { "name": "THERMOSTAT" } ], "user_given_name": null, "device_reg_id": "8a705142eda33efd541b5bdceb7ac9c7", "area_id": null, "cluster_details": { "1": { "device_type": { "name": "THERMOSTAT", "id": 769 }, "profile_id": 260, "in_clusters": { "0x0000": { "endpoint_attribute": "basic", "attributes": { "0x0004": { "attribute_name": "manufacturer", "value": "BOSCH" }, "0x0005": { "attribute_name": "model", "value": "RBSH-TRV0-ZB-EU" } }, "unsupported_attributes": {} }, "0x0001": { "endpoint_attribute": "power", "attributes": { "0x0021": { "attribute_name": "battery_percentage_remaining", "value": 200 }, "0x0020": { "attribute_name": "battery_voltage", "value": 31 } }, "unsupported_attributes": {} }, "0x0003": { "endpoint_attribute": "identify", "attributes": {}, "unsupported_attributes": {} }, "0x0004": { "endpoint_attribute": "groups", "attributes": {}, "unsupported_attributes": {} }, "0x0020": { "endpoint_attribute": "poll_control", "attributes": {}, "unsupported_attributes": {} }, "0x0201": { "endpoint_attribute": "thermostat", "attributes": { "0x001b": { "attribute_name": "ctrl_sequence_of_oper", "value": 2 }, "0x0000": { "attribute_name": "local_temperature", "value": 2480 }, "0x0016": { "attribute_name": "max_heat_setpoint_limit", "value": 3000 }, "0x0015": { "attribute_name": "min_heat_setpoint_limit", "value": 500 }, "0x0011": { "attribute_name": "occupied_cooling_setpoint", "value": 2300 }, "0x0012": { "attribute_name": "occupied_heating_setpoint", "value": 2100 }, "0x001c": { "attribute_name": "system_mode", "value": 4 } }, "unsupported_attributes": { "0x0002": { "attribute_name": "occupancy" }, "0x0003": { "attribute_name": "abs_min_heat_setpoint_limit" }, "0x0004": { "attribute_name": "abs_max_heat_setpoint_limit" }, "0x0005": { "attribute_name": "abs_min_cool_setpoint_limit" }, "0x0007": { "attribute_name": "pi_cooling_demand" }, "0x0008": { "attribute_name": "pi_heating_demand" }, "0x0006": { "attribute_name": "abs_max_cool_setpoint_limit" }, "0x001e": { "attribute_name": "running_mode" }, "0x0013": { "attribute_name": "unoccupied_cooling_setpoint" }, "0x0014": { "attribute_name": "unoccupied_heating_setpoint" }, "0x0029": { "attribute_name": "running_state" }, "0x0017": { "attribute_name": "min_cool_setpoint_limit" }, "0x0018": { "attribute_name": "max_cool_setpoint_limit" } } }, "0x0204": { "endpoint_attribute": "thermostat_ui", "attributes": {}, "unsupported_attributes": {} }, "0x0b05": { "endpoint_attribute": "diagnostic", "attributes": {}, "unsupported_attributes": {} } }, "out_clusters": { "0x000a": { "endpoint_attribute": "time", "attributes": {}, "unsupported_attributes": {} }, "0x0019": { "endpoint_attribute": "ota", "attributes": {}, "unsupported_attributes": {} } } } } } }Additional information
https://www.zigbee2mqtt.io/devices/BTH-RA.html
Koenkk/zigbee2mqtt#14926
https://zigbee.blakadder.com/Bosch_BTH-RA.html
The text was updated successfully, but these errors were encountered: