Ok thanks, I will write in the coming days to Sinope to see if the "display off" capability is still available and if yes, what is the id of this capability.
I would not be supprised that this capability is simply no longer there, since it can not be called even with the GT130 hub.
Hum interresting - that would mean not that type of thermostat in a bedroom... at least not in my wife's bedroom.
Thanks
Yes and no, the luminosity of the thermostat dim according to the luminosity of the room. The thermostat make almost no light when it is very dark in the room. On my side on don't use this capability.
Interresting .... thanks for the cue....
Just had a little chat with CustSupport @ Sinopée... G2 will dim to 10% at a slower rate than G1 by design.
They also mention that they have a "Bedroom" mode supported by the Thermostat but not implemented yet in their app. This Bedroom mode shuts down the thermostat display completely. Look like DIsplay/ON/OFF to me does it So they claim they didnt remove that functionnality from the G2. Remain to be seen why it does not react to the driver commands.
Thought I'll share this
J.
Thanks, I've contacted the technical support at Sinopé. Depending on the answer, I will may be able to add this functionality for G2 thermostat.
Hi, So here the translated answer from Sinopé (I've communicated in french). "Unfortunately this information is not public. Sinope does not disclose this information. The request must come directly from Hubitat"
@bobbyD , Will you be able to add the functionality on the default Sinope driver for the TH1124ZB thermostats?
For the G1 thermostat the command was:
zigbee.writeAttribute(0x0201, 0x0402, DataType.ENUM8, 0x0001) for display to be on and,
zigbee.writeAttribute(0x0201, 0x0402, DataType.ENUM8, 0x0000) for the display to be off.
However, this command was modified for the G2 version of the thermostat.
I believe that @mike.maxwell handles the Sinope drivers.
the current platform release has a dedicated driver for this thermostat with appropriate display options.
"Sinope TH1123ZB-G2 Thermostat"
Thank you, I did not realised it. I've look too rapidly yesterday probably.
Not sure if it is of any help... tell me if I am spamming.
J.
Loaded the G2 Driver from Hubitat :
Command tiles are the following :
The only thing I see that ressemble Display Off is this below. I did toggle / saved and provided the Debug trace in case of any help ... I figure not a lot have a G2 available right now..
And no effect on the display BTW. I would have expected that On Demand would blank the screen off waiting for me to touch a button... Maybe I am wrong...
dev:1002022-12-07 11:41:50.113debugdescMap: [raw:catchall: 0104 0201 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:0201, clusterInt:513, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:41:49.716debugdescMap: [raw:catchall: 0104 FF01 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:FF01, clusterInt:65281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:41:49.310debugdescMap: [raw:catchall: 0104 FF01 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:FF01, clusterInt:65281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:41:48.907debugdescMap: [raw:catchall: 0104 0201 01 01 0040 00 19EF 00 00 0000 04 01 860204, profileId:0104, clusterId:0201, clusterInt:513, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[86, 02, 04]]
dev:1002022-12-07 11:41:48.509debugdescMap: [raw:catchall: 0104 0204 01 01 0040 00 19EF 00 00 0000 04 01 00, profileId:0104, clusterId:0204, clusterInt:516, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:41:48.152debugdescMap: [raw:catchall: 0104 FF01 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:FF01, clusterInt:65281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:41:48.016warndescription logging is: true
dev:1002022-12-07 11:41:48.015warndebug logging is: true
dev:1002022-12-07 11:41:48.015infoupdated...
dev:1002022-12-07 11:38:50.465debugdescMap: [raw:catchall: 0104 0201 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:0201, clusterInt:513, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:38:50.064debugdescMap: [raw:catchall: 0104 FF01 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:FF01, clusterInt:65281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:38:49.665debugdescMap: [raw:catchall: 0104 FF01 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:FF01, clusterInt:65281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:38:49.256debugdescMap: [raw:catchall: 0104 0201 01 01 0040 00 19EF 00 00 0000 04 01 860204, profileId:0104, clusterId:0201, clusterInt:513, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[86, 02, 04]]
dev:1002022-12-07 11:38:48.856debugdescMap: [raw:catchall: 0104 0204 01 01 0040 00 19EF 00 00 0000 04 01 00, profileId:0104, clusterId:0204, clusterInt:516, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:38:48.523debugdescMap: [raw:catchall: 0104 FF01 01 01 0040 00 19EF 00 01 119C 04 01 00, profileId:0104, clusterId:FF01, clusterInt:65281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:19EF, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:119C, command:04, direction:01, data:[00]]
dev:1002022-12-07 11:38:48.363warndescription logging is: true
On Demand:Adaptive mode only enabled when user uses the UI (buttons). Backlight Off when UI is idle.
Sensing (default):Adaptive mode enabled. Backlight controlled using light sensor.
Always On:Backlight is always ON 100%
These options will only work with the G2 thermostat.
This has no effect on my Thermostat, unless it takes more that 2 minutes to be effective ( the time I waited before calling it "no effect".... unless I dont understand.
J
don't know what to tell you, these setting options were straight from my contact at Sinope...
I'll try them again on my sample.
That is why I provided the Raw Debug traces for each of the settings I tried ( On demand / Sensing) , hoping it might mean something to the developper 
ok, i think i found it (despite the standard cluster, its a manufacturer specific attribute, which Sinope didn't mention to me...) so it will be updated in the next hot fix.
Also changed the preference setting from Sensing to Adaptive, maybe that will make more sense.
At least it was not a code 22 on my part Have a great day
J.
@JM4522, once the default driver updated on the HE side, I will try to identify the attribute ID by sniffing the Zigbee communication. I've never done it before, but should not be too difficult. In the mean time, can you validate that all other functionality that was implemented for the Gen 1 version works properly, for example the energy meter? It should be (I believe) since all of the other functionality are somewhat standard cluster ID and attribute ID since they are listed in the following document: Zigbee Cluster Library (zigbeealliance.org).
What are you trying to accomplish by doing this?
Download the Hubitat app
