Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 902010/32 #1003

ma-ca · 2018-12-04T20:02:01Z

Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 902010/32

A sensor type ZHAThermostat is created with the following options in state and config:

EDIT: moved writable settings from state to config.

option	read/write	attribute	description
state.on	read only	0x0029	running state on/off
state.temperature	read only	0x0000	measured temperature
config.heatsetpoint	read write	0x0012	heating setpoint
config.scheduleron	read write	0x0025	scheduler on/off
config.offset	read write	0x0010	temperature offset
config.scheduler	read write	(command)	scheduled setpoints

Example sensor:

 /api/<apikey>/sensors/<id>/
    {
       config: {
         "heatsetpoint": 2200,
          "offset": 0,
           "scheduler": "Monday,Tuesday,Wednesday,Thursday,Friday 05:00 2200 19:00 1800;Saturday,Sunday 06:00 2100 19:00 1800;",
         "scheduleron": true
       },
       state: {
          "on": true,
          "temperature": 2190
        },
       "ep": 1,
       "manufacturername": "Bitron Home",
       "modelid": "902010/32",
        "type": "ZHAThermostat",
       ...
    }

Rest API example commands:

  -X PUT /api/<apikey>/sensors/<id>/config -d '{ "heatsetpoint": 1800 }'
  -X PUT /api/<apikey>/sensors/<id>/config -d '{ "scheduleron": true }'
  -X PUT /api/<apikey>/sensors/<id>/config -d '{ "offset": 0 }'
  -X PUT /api/<apikey>/sensors/<id>/config -d '{ "scheduler": "Monday 05:00 2200 19:00 1800;" }'
                                           -d '{ "scheduler": "" }'  (send get scheduler command)

Attributes (only a subset):

    ID      Type  Type    Description                     Default
    0x0000  0x29  int16s  Local Temperature               --
    0x0010  0x28  int8s   Local Temperature Calibration   --
    0x0012  0x29  int16s  Occupied Heating Setpoint       2000 (20 °C)
    0x0025  0x18  bit8    Programming Operation Mode      0
                          Bit#0 of this attribute controls
                          the enabling of the Thermostat Scheduler.
    0x0029  0x19  bit16   Thermostat Running State        0
                          Bit0=Heat State On
                          Bit1=Cool State On

Commands Received (Client to Server):

    Command-ID  Name
    0x00        Setpoint Raise/Lower
    0x01        Set Weekly Schedule
    0x02        Get Weekly Schedule
    0x03        Clear Weekly Schedule

Commands Generated (Server to Client):

    Command-ID  Name
    0x00        Current Weekly Schedule

Weekly Schedule format

   Octets 1           1       1     2           2/0         2/0       ...   2   2/0   2/0
   Type   enum8       bit8    bit8  int16u      int16s      int16s
   Name   Number      Day of  Mode  Transition  Heat        Cool
          Transitions Week    (1,2) Time 1      Setpoint 1  Setpoint1

   Day of Week: bitmap8 [Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Away]
                bit         0       1       2         3        4         5        6       7

Example:

   Monday, Tuesday, Thursday, Friday = 0011 0110 = 0x36
        |        |         |     ^-------^|  ||
        |        |          ---------------  ||
        |        -----------------------------|
        ---------------------------------------

@ebaauw would you be able to add thermostat to homebridge-hue?

…0/32 A sensor type ZHAThermostat is created

ebaauw · 2018-12-04T23:19:26Z

Not sure. I think the thermostat should be exposed as a /lights resource. The state attributes of a /sensors resource are not (supposed to be) updatable. See
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Supported-Devices#resources

ma-ca · 2018-12-05T14:14:18Z

I would like to have a thermostat in HomeKit that displays the current temperature and desired temperature. Also, it should be possible to modify the desired temperature and to enable/disable the scheduler.

I did not consider a thermostat belonging to /lights. A thermostat state is on/off when the desired temperature is higher/lower than current temperature. To me this seems different behavior than dimmable lights.

Anyway, I am happy to change the thermostat from /sensors to /lights if this is needed for HomeKit. Just let me know.

manup · 2018-12-05T14:17:56Z

Not happy so many non light devices become lights lately, guess it's really time to introduce the /devices endpoint or something similar.

It will be hard in the future to clean it up once installations are out there which rely on a stable API.

ma-ca · 2018-12-05T16:53:15Z

So the thermostat remains in /sensors.

I have moved the writable settings state.heatsetpoint and state.scheduleron to config.heatsetpoint and config.scheduleron.

One question: The thermostat cluster only has reporting on the temperature attribute. How can I poll other attributes? The poll_manager.cpp only allows router nodes. This thermostat is a battery powered end device.

manup · 2018-12-05T17:31:29Z

Polling end-devices is tricky, first you need to find out when they poll (mac data request) the parent node for new data.

Knowing when the end-device is awake and polls the parent is crucial. Just sending a request to an end-device will likely fail since requests are stored only for max. ~7 seconds on the parent.

Do you have a sniffer available?

Kane610 · 2018-12-05T18:01:08Z

@manup I'd welcome a better class than lights for other devices. Move all currently supported devices over to this new endpoint. Just communicate it in good time to allow us to add support

ma-ca · 2018-12-05T18:05:24Z

This Bitron Thermostat does respond very well to commands. Reading and writing attributes takes several seconds but always succeeds. I just need to find the right place in the code to read the attributes every 5 minutes. Even missing some read requests would not do any harm. I don't have a sniffer.

ebaauw · 2018-12-05T18:06:16Z

if this is needed for HomeKit

HomeKit doesn’t care about the resource - it doesn’t even know. Homebridge-hue does. For /lights resources, it took me a lot of effort to collect multiple characteristic changes for the same “light” into one API request to deCONZ or the Hue bridge, in order not to flood the gateway. When recalling a HomeKit scene, there can be up to 50 changes at once. There’s no similar logic for /sensors resources.

Moving the writeable state attributes to config and sticking to /sensors actually makes more sense than using /lights, as the thermostat is battery powered. Afaik there’s no /lights resources for end devices that might turn their receiver off while sleeping.

ebaauw · 2018-12-05T18:10:38Z

This Bitron Thermostat does respond very well to commands. Reading and writing attributes takes several seconds but always succeeds.

That sounds similar to the Hue motion sensor, that seems to poll its parent every five seconds or so. What does the thermostat report for Receiver on when idle in the Node Info panel? And in the Power Descriptor (after you’ve read it using the leftmost of the two circles on the right of the node)? When it does turn the receiver off, it might be prudent to use config.pending as for the Hue motion sensor.

ebaauw · 2018-12-05T18:22:23Z

Not happy so many non light devices become lights lately, guess it's really time to introduce the /devices endpoint or something similar.

I'd welcome a better class than lights for other devices. Move all currently supported devices over to this new endpoint. Just communicate it in good time to allow us to add support

As would I, preferably one that follows the ZigBee structure of node, endpoint, cluster, rather than having to re-assemble multiple resources for the same device using the mac address.

This would however break compatibility with Hue apps, particularly with the likes of Alexa. I would probably remove deCONZ support from homebridge-hue and create a new homebridge-deconz.

ma-ca · 2018-12-05T18:45:03Z

Bitron Thermostat Node Info

ebaauw · 2019-01-11T12:29:26Z

@ma-ca, did you also add support for CLIPThermostat?

ma-ca · 2019-01-11T13:12:48Z

did you also add support for CLIPThermostat?

@ebaauw No, I just added a ZHAThermostat sensor type.

ebaauw · 2019-01-11T13:20:57Z

I'm also missing state.lastupdated, config.on, and config.reachable.

ma-ca · 2019-01-11T16:28:26Z

I'm also missing state.lastupdated, config.on, and config.reachable.

They all exist, but I did not show them in the in first sensor description above (because I wanted to highlight the attributes that are specific to the thermostat).

The full thermostat sensor looks like this:

{
    "config": {
        "battery": 100,
        "heatsetpoint": 2200,
        "offset": 0,
        "on": true,
        "reachable": true,
        "scheduler": "Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2300 06:00 1700 15:00 2300 16:00 2200 21:00 1800;Saturday 06:00 2200 21:00 1800;",
        "scheduleron": true
    },
    "ep": 1,
    "etag": "06745a49746f448cc3fd23bd6010accd",
    "manufacturername": "Bitron Home",
    "modelid": "902010/32",
    "name": "Thermostat 39",
    "state": {
        "lastupdated": "2019-01-11T16:20:15",
        "on": false,
        "temperature": 2260
    },
    "swversion": "V1b225-20151013",
    "type": "ZHAThermostat",
    "uniqueid": "00:0d:6f:00:0e:f0:df:19-01-0201"
}

ebaauw · 2019-01-11T16:44:46Z

Ah, cool. As I said: I don't yet have a thermostat, so I cannot see for myself :-(

Did you look yet at homebirdge-hue v0.11.7?

bohtho · 2019-03-19T11:58:32Z

Would the work both the Deconz, Deconz REST API, adn Homebridge-Hue developers have put in to support the Bitron and Eurotronic zigbee thermostatic radiator valves (eg. supporting clusters, ZHAThermostat and CLIPThermostat) make any other thermostatic valve based on Zigbee HA 1.2 (example: https://www.plugwise.com/en_US/products/floor) also work with Deconz now ?

easybeat · 2020-01-04T17:50:08Z

Sorry, does deconz rest-api support the Eurotronic Spirit Zigbee by now...I tried to find out by reading this post but it is confusing me.

Thank you for the information.

Cheers
Beat

Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 90201…

09551b8

…0/32 A sensor type ZHAThermostat is created

Thermostat Cluster - moved writable settings from state to config

fe255c3

manup merged commit fe255c3 into dresden-elektronik:master Dec 8, 2018

ma-ca mentioned this pull request Jan 8, 2019

[Device Support Request] Eurotronic Spirit ZigBee #1098

Closed

ebaauw mentioned this pull request Jan 11, 2019

Support Thermostat ebaauw/homebridge-hue#426

Closed

KiwiHC16 mentioned this pull request Feb 22, 2019

Eurotronic Spirit KiwiHC16/Abeille#610

Closed

SwoopX mentioned this pull request Jan 2, 2020

Device Support Request Bitron 902010/32 Wall Thermostat #2248

Closed

ma-ca mentioned this pull request Aug 17, 2020

eCozy Thermostat and more #3087

Merged

keesj mentioned this pull request Nov 1, 2020

Thermostat 902010/32 (mode support) #3550

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 902010/32 #1003

Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 902010/32 #1003

ma-ca commented Dec 4, 2018 •

edited

Loading

ebaauw commented Dec 4, 2018

ma-ca commented Dec 5, 2018

manup commented Dec 5, 2018

ma-ca commented Dec 5, 2018

manup commented Dec 5, 2018

Kane610 commented Dec 5, 2018

ma-ca commented Dec 5, 2018

ebaauw commented Dec 5, 2018

ebaauw commented Dec 5, 2018

ebaauw commented Dec 5, 2018

ma-ca commented Dec 5, 2018

ebaauw commented Jan 11, 2019

ma-ca commented Jan 11, 2019

ebaauw commented Jan 11, 2019 •

edited

Loading

ma-ca commented Jan 11, 2019

ebaauw commented Jan 11, 2019 •

edited

Loading

bohtho commented Mar 19, 2019 •

edited

Loading

easybeat commented Jan 4, 2020

Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 902010/32 #1003

Add Support for Thermostat Cluster 0x0201 and Bitron Thermostat 902010/32 #1003

Conversation

ma-ca commented Dec 4, 2018 • edited Loading

ebaauw commented Dec 4, 2018

ma-ca commented Dec 5, 2018

manup commented Dec 5, 2018

ma-ca commented Dec 5, 2018

manup commented Dec 5, 2018

Kane610 commented Dec 5, 2018

ma-ca commented Dec 5, 2018

ebaauw commented Dec 5, 2018

ebaauw commented Dec 5, 2018

ebaauw commented Dec 5, 2018

ma-ca commented Dec 5, 2018

ebaauw commented Jan 11, 2019

ma-ca commented Jan 11, 2019

ebaauw commented Jan 11, 2019 • edited Loading

ma-ca commented Jan 11, 2019

ebaauw commented Jan 11, 2019 • edited Loading

bohtho commented Mar 19, 2019 • edited Loading

easybeat commented Jan 4, 2020

ma-ca commented Dec 4, 2018 •

edited

Loading

ebaauw commented Jan 11, 2019 •

edited

Loading

ebaauw commented Jan 11, 2019 •

edited

Loading

bohtho commented Mar 19, 2019 •

edited

Loading