I'm not able to use Mariano's Edge Beta Drivers for POPP Zigbee Thermostat

[Lech_Jonczyk]

I have a POPP Zigbee Thermostat 701721.

I’m trying to use Mariano’s Edge Beta Driver from channel: https://callaway.smartthings.com/channels/c8bb99e1-04a3-426b-9d94-2d260134d624

I can see the driver installed on my hub:

But I’m not able to select this driver in my device:

In the init.lua I can see that my device is there
https://github.com/Mariano-Github/Edge-Drivers-Beta/blob/main/zigbee-thermostat-stock-mc/src/popp_danfoss/init.lua

The Manufacturer Code and Model seem to be the same:

What am I doing wrong?

Thanks
Lech

[h0ckeysk8er (Bruce Pinsky)]

@Lech_Jonczyk

I have a POPP Zigbee Thermostat 701721.

I’m trying to use Mariano’s Edge Beta Driver from channel: https://callaway.smartthings.com/channels/c8bb99e1-04a3-426b-9d94-2d260134d624

I can see the driver installed on my hub:

But I’m not able to select this driver in my device:

In the init.lua I can see that my device is there
https://github.com/Mariano-Github/Edge-Drivers-Beta/blob/main/zigbee-thermostat-stock-mc/src/popp_danfoss/init.lua

The Manufacturer Code and Model seem to be the same:

What am I doing wrong?

Thanks
Lech

The screenshot of the AWA shows your model as eT093WRG not eT093WRO.

[Lech_Jonczyk]

@h0ckeysk8er

The screenshot of the AWA shows your model as eT093WRG, not eT093WRO.

Yeah - that is probably the issue. I did some research and it seems the “O” version is an older version and “G” is the newer version, but from development standpoint they are the same.
I guess I’ll try to contact the author of the drivers and ask him to update it—it should be simple.

Thanks

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Heard reports from other users who aren’t able to select drivers even though there a fingerprint match. Would be curious to know if it gets resolved for you.

[Mariano_Colmenarejo]

@Lech_Jonczyk

I guess I’ll try to contact the author of the drivers and ask him to update it—it should be simple.

I have seen that the stock driver was modified and does not use the thermostatOperatingState capability either.
The old driver did use it and it worked with the defaults.

If you want, I add it to the zigbee Thermostat Mc driver with the thermostatOperatingState capability and try it.

Have you used the stock zigbee Thermostat driver?

[Lech_Jonczyk]

@Mariano_Colmenarejo

If you want, I add it to the zigbee Thermostat Mc driver with the thermostatOperatingState capability and try it.

Please add it. Will you test it or should I do it?

Have you used the stock zigbee Thermostat driver?

I tried these drivers:

Please bear with me - I’m very new to SmartThings (but I’m a quick learner) - I’m not sure if any of the above are stock drivers.

[h0ckeysk8er (Bruce Pinsky)]

@Lech_Jonczyk

@Mariano_Colmenarejo

If you want, I add it to the zigbee Thermostat Mc driver with the thermostatOperatingState capability and try it.

Please add it. Will you test it or should I do it?

Have you used the stock zigbee Thermostat driver?

I tried these drivers:

Please bear with me - I’m very new to SmartThings (but I’m a quick learner) - I’m not sure if any of the above are stock drivers.

The Zigbee Thermostat without a named Driver Channel is a stock driver. Production stock drivers don’t indicate a Driver Channel while Beta stock drivers are denoted as " SmartThings Drivers (Beta)". Community developed drivers show the developer’s channel name.

[Mariano_Colmenarejo]

@Lech_Jonczyk

Please add it. Will you test it or should I do it?

Considering that you have used both the Popp driver and the stock smartthings, which removed the thermostatOperatingState capability, it is very possible that the device does not support that attribute.

I have done this TEST driver, which has the thermostatOperatingState capability just like the old smartthings stock driver had.

Install this TEST driver on your hub and make a driver change from the website or app
Try to see if it works and if it works I will update it to the newer driver version of smartthings, which has more features and settings

───────────────────────────────────────────────────
 Name         Zigbee Thermostat Mc-TEST
 Version      2024-04-04T20:24:40.121009706        
───────────────────────────────────────────────────
- id: "D5X84YU/eT093WRG"
    deviceLabel: POPP Thermostat
    manufacturer: D5X84YU
    model: eT093WRG
    deviceProfileName: thermostat-popp-danfoss

[Lech_Jonczyk]

@Mariano_Colmenarejo

Try to see if it works

I guess it doesn’t work…

I’m just wondering why so many more attributes are available in the Home Assistant related zigbee integrations (zigbee2mqtt, deconz and ZHA), that are not available for SmartThings. (see here)
Is it some kind of limitation of ST? Is there a workaround?

[Mariano_Colmenarejo]

@Lech_Jonczyk

I guess it doesn’t work…

Are try if operating status appears performing a refresh command by swiping down in the app or pressing refresh command button in web advanced users?

@Lech_Jonczyk

zigbee integrations (zigbee2mqtt, deconz and ZHA), that are not available for SmartThings. (see here )
Is it some kind of limitation of ST? Is there a workaround?

If what it says in the Zigbee2MQTT link is true, the running_state attribute should be functional; it is what the smartthings driver uses to emit the operating status of the thermostat. If it doesn’t work, it is because it is not supported or is incorrectly configured.

Smarttings also supports the pi_heating_demand attribute, which sends the % opening of the valve, I don’t understand why Popp doesn’t implement it in its driver.

If you want tomorrow, I will try to configure the running_state attribute and try to see if it works

smartthings supports most standard attributes of the thermostat cluster, but some manufacturer uses custom attributes for some functions:

function Thermostat.attr_id_map()
    return {
    [0x0000] = "LocalTemperature",
    [0x0001] = "OutdoorTemperature",
    [0x0002] = "Occupancy",
    [0x0003] = "AbsMinHeatSetpointLimit",
    [0x0004] = "AbsMaxHeatSetpointLimit",
    [0x0005] = "AbsMinCoolSetpointLimit",
    [0x0006] = "AbsMaxCoolSetpointLimit",
    [0x0007] = "PICoolingDemand",
    [0x0008] = "PIHeatingDemand",
    [0x0009] = "HVACSystemTypeConfiguration",
    [0x0010] = "LocalTemperatureCalibration",
    [0x0011] = "OccupiedCoolingSetpoint",
    [0x0012] = "OccupiedHeatingSetpoint",
    [0x0013] = "UnoccupiedCoolingSetpoint",
    [0x0014] = "UnoccupiedHeatingSetpoint",
    [0x0015] = "MinHeatSetpointLimit",
    [0x0016] = "MaxHeatSetpointLimit",
    [0x0017] = "MinCoolSetpointLimit",
    [0x0018] = "MaxCoolSetpointLimit",
    [0x0019] = "MinSetpointDeadBand",
    [0x001A] = "RemoteSensing",
    [0x001B] = "ControlSequenceOfOperation",
    [0x001C] = "SystemMode",
    [0x001D] = "AlarmMask",
    [0x001E] = "ThermostatRunningMode",
    [0x0020] = "StartOfWeek",
    [0x0021] = "NumberOfWeeklyTransitions",
    [0x0022] = "NumberOfDailyTransitions",
    [0x0023] = "TemperatureSetpointHold",
    [0x0024] = "TemperatureSetpointHoldDuration",
    [0x0025] = "ThermostatProgrammingOperationMode",
    [0x0029] = "ThermostatRunningState",
    [0x0030] = "SetpointChangeSource",
    [0x0031] = "SetpointChangeAmount",
    [0x0032] = "SetpointChangeSourceTimestamp",
    [0x0034] = "OccupiedSetback",
    [0x0035] = "OccupiedSetbackMin",
    [0x0036] = "OccupiedSetbackMax",
    [0x0037] = "UnoccupiedSetback",
    [0x0038] = "UnoccupiedSetbackMin",
    [0x0039] = "UnoccupiedSetbackMax",
    [0x003A] = "EmergencyHeatDelta",
    [0x0040] = "ACType",
    [0x0041] = "ACCapacity",
    [0x0042] = "ACRefrigerantType",
    [0x0043] = "ACCompressorType",
    [0x0044] = "ACErrorCode",
    [0x0045] = "ACLouverPosition",
    [0x0046] = "ACCoilTemperature",
    [0x0047] = "ACCapacityFormat",
  }
end

This version of the driver configures reports of the running_state attribute.

For the attribute to be configured you would have to uninstall or reinstall one thermostat, for the doConfigure lifecycle to run.

───────────────────────────────────────────────────
 Name         Zigbee Thermostat Mc-TEST
 Version      2024-04-04T22:17:22.46288096
───────────────────────────────────────────────────

[Lech_Jonczyk]

@Mariano_Colmenarejo

Are try if operating status appears performing a refresh command by swiping down in the app or pressing refresh command button in web advanced users?

Nothing has changed after refresh.

For the attribute to be configured you would have to uninstall or reinstall one thermostat, for the doConfigure lifecycle to run.

I installed the new driver, then removed the thermostat from the app, then factory reset the thermostat and then I re-added it in the app.

I double checked that the latest test driver is in use.
I can see there attributes:

[Mariano_Colmenarejo]

@Lech_Jonczyk

I can see there attributes

It would be necessary to check it with the CLI logs, to see what the device responds, but it seems that it does not support the attribute or responds with a value not recognized by the driver.

If you want to publish the pairing logs with the CLI I could analyze them, maybe device answer the PIHeatingDemand attribute

[Lech_Jonczyk]

@Mariano_Colmenarejo

publish the pairing logs with the CLI

Is this what you’re looking for?

https://pastebin.com/9e3ShngQ

Edit:
I noticed something. In the log I pasted, there is a line:

2024-04-05T11:50:20.040561308Z INFO Zigbee Thermostat Mc-TEST <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCA, rssi: -77, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x22, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, PIHeatingDemand: 0x04 > > > >

Later the following line appeared (it’s not included in the logs I shared):

2024-04-05T11:55:22.615852362Z INFO Zigbee Thermostat Mc-TEST <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -83, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x2A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, PIHeatingDemand: 0x07 > > > >

Later I changed the heating setpoint from 21 to 12 and the following line appeared in the logs:

024-04-05T12:00:24.670982207Z INFO Zigbee Thermostat Mc-TEST <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCE, rssi: -76, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x34, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, PIHeatingDemand: 0x00 > > > >

Then I change the heating setpoint to 35 and the following line appeared:
2024-04-05T12:12:20.249392846Z INFO Zigbee Thermostat Mc-TEST <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -83, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x43, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, PIHeatingDemand: 0x04 > > > >

Looks like the PiHeatingDemand changes when there is demand for heating.

[Mariano_Colmenarejo]

@Lech_Jonczyk
then I look at it, now I’m out.

Does not support OperatingState, does support PIHeatingDemand

[Lech_Jonczyk]

BTW - I noticed, that using your drivers, I can change in the app the heating setpoint with an interval of 1, whereas in the POPP drivers I can change it with 0.5 interval. Is it possible to update your drivers to handle the 0.5 degree interval?

Thanks

[Mariano_Colmenarejo]

@Lech_Jonczyk

Is it possible to update your drivers to handle the 0.5 degree interval?

Yes, is possible.

Could you set Heat set point to see valve open value in cli logs?

In sinope thermostar heatingDemand.value < 10 is valve closed, operating state = idle

In popp thermostat it could see differet

[Lech_Jonczyk]

@Mariano_Colmenarejo

Could you set Heat set point to see valve open value in cli logs?

I set the heat setpoint to 34.5 (measured temperature is 20)

2024-04-05T19:34:21.809980571Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:34:26.888561071Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:34:26.950187280Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xD0, rssi: -74, body_length: 0x000C, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0012, DataType: Int16, OccupiedHeatingSetpoint: 3450 >, < AttributeRecord || AttributeId: 0x0030, DataType: Enum8, SetpointChangeSource: SetpointChangeSource[MANUAL] > > > >
2024-04-05T19:34:26.966240446Z TRACE Virtual Devices V2  Received event with handler capability
2024-04-05T19:34:26.975876696Z TRACE Zigbee Thermostat Mc-TEST  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2024-04-05T19:34:26.989152280Z INFO Zigbee Thermostat Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OccupiedHeatingSetpoint
2024-04-05T19:34:26.996539863Z INFO Virtual Devices V2  <Device: dc8233fa-9aad-4f8b-aca6-71afaba81767 (Zielony Reczne Grzanie)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2024-04-05T19:34:27.011205321Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> emitting event: {"attribute_id":"heatingSetpoint","capability_id":"thermostatHeatingSetpoint","component_id":"main","state":{"unit":"C","value":34.5}}
2024-04-05T19:34:27.017299030Z TRACE Virtual Devices V2  Found CapabilityCommandDispatcher handler in vedgeDriver
2024-04-05T19:34:27.022214696Z INFO Virtual Devices V2  Virtual switch turned >> on <<
2024-04-05T19:34:27.030813446Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:34:27.035806071Z INFO Virtual Devices V2  <Device: dc8233fa-9aad-4f8b-aca6-71afaba81767 (Zielony Reczne Grzanie)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-04-05T19:34:27.043740905Z DEBUG Virtual Devices V2  Grzanie Zielony Reczne device thread event handled
2024-04-05T19:34:51.817440241Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:35:21.826855814Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:35:35.489916682Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:35:35.572201095Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCA, rssi: -79, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, LocalTemperature: 1974 > > > >
2024-04-05T19:35:35.583467100Z TRACE Zigbee Thermostat Mc-TEST  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2024-04-05T19:35:35.592370133Z INFO Zigbee Thermostat Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature
2024-04-05T19:35:35.609821187Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":19.74}}
2024-04-05T19:35:35.629824851Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:35:51.840211377Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:36:20.079838755Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:36:20.339827047Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, LocalTemperature: 2000 > > > >
2024-04-05T19:36:20.374774922Z TRACE Zigbee Thermostat Mc-TEST  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2024-04-05T19:36:20.387593130Z INFO Zigbee Thermostat Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature
2024-04-05T19:36:20.424444505Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":20.0}}
2024-04-05T19:36:20.507786589Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:36:21.840908464Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:36:51.847183134Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:37:20.013033054Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:37:20.070151971Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCE, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, LocalTemperature: 2010 > > > >
2024-04-05T19:37:20.077189888Z TRACE Zigbee Thermostat Mc-TEST  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2024-04-05T19:37:20.111002929Z INFO Zigbee Thermostat Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature
2024-04-05T19:37:20.221798221Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":20.1}}
2024-04-05T19:37:20.279830929Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:37:21.856289263Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:37:51.858045391Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:38:21.859424312Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:38:51.867018107Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:38:56.869769357Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:38:56.908105982Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -72, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, PIHeatingDemand: 0x64 > > > >
2024-04-05T19:38:56.919773316Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:39:21.876449780Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:39:29.189842650Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:39:29.218023024Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCE, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0012, DataType: Int16, OccupiedHeatingSetpoint: 3450 > > > >
2024-04-05T19:39:29.224302788Z TRACE Zigbee Thermostat Mc-TEST  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2024-04-05T19:39:29.228825381Z INFO Zigbee Thermostat Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OccupiedHeatingSetpoint
2024-04-05T19:39:29.233777273Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> emitting event: {"attribute_id":"heatingSetpoint","capability_id":"thermostatHeatingSetpoint","component_id":"main","state":{"unit":"C","value":34.5}}
2024-04-05T19:39:29.239345972Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:39:51.878189573Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:40:21.886780707Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:40:51.888547510Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:41:21.889256555Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:41:51.896708267Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:42:20.049791312Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:42:20.090347895Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCE, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x60, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, LocalTemperature: 1999 > > > >
2024-04-05T19:42:20.096945437Z TRACE Zigbee Thermostat Mc-TEST  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2024-04-05T19:42:20.101476395Z INFO Zigbee Thermostat Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature
2024-04-05T19:42:20.106674479Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":19.99}}
2024-04-05T19:42:20.112127145Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:42:20.399757895Z TRACE Zigbee Thermostat Mc-TEST  Received event with handler zigbee
2024-04-05T19:42:20.407571020Z INFO Zigbee Thermostat Mc-TEST  <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -73, body_length: 0x000A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x0C, mfg_code: 0x1246, seqno: 0x61, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x404A, DataType: Int16, Int16: 1 > > > >
2024-04-05T19:42:20.412870145Z DEBUG Zigbee Thermostat Mc-TEST  POPP Thermostat device thread event handled
2024-04-05T19:42:21.899648729Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:42:51.906013691Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled
2024-04-05T19:43:21.919110631Z DEBUG Zigbee Thermostat Mc-TEST  driver device thread event handled

[Mariano_Colmenarejo]

@Lech_Jonczyk

2024-04-05T19:38:56.908105982Z INFO Zigbee Thermostat Mc-TEST <ZigbeeDevice: 84e0554b-36f9-43a1-b820-13d44c9a1d33 [0xD52B] (POPP Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD52B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -72, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, PIHeatingDemand: 0x64 > > > >

It seems that the valve indicates 100% open (0x64)

So I’m going to set it so that when I send values < 10% it shows operatingState: Idle, just like Sinope?

This TEST version is identical to the last stock version, with open window settings…and others, adding the ThermostatOperatingState capability and the code to handle it.

For it to work you have to reinstall the thermostat with this version of the driver or since it is already configured you can change to another thermostat driver and then return to this TEST version.

If it works well I will merge it with the Mc version

───────────────────────────────────────────────────
 Name         Zigbee Thermostat Mc-TEST
 Version      2024-04-05T19:57:17.146634191        
───────────────────────────────────────────────────

[Lech_Jonczyk]

Just one more update before I test the new drivers. I extracted the chronological record of setting heat point, measured temperature and PIHeatingDemand. Not sure it helps, but I’m posting just in case:

time	action	value
2024-04-05T11:40:44.335295860Z	SetHeatingPoint	21
2024-04-05T11:40:44.473483148Z	TemperatureMeasurement	19.74
2024-04-05T11:40:44.800164809Z	TemperatureMeasurement	19.74
2024-04-05T11:41:42.923009689Z	TemperatureMeasurement	19.74
2024-04-05T11:42:43.385095002Z	TemperatureMeasurement	19.84
2024-04-05T11:43:43.844760718Z	TemperatureMeasurement	19.85
2024-04-05T11:44:44.305109005Z	TemperatureMeasurement	19.83
2024-04-05T11:45:44.764665345Z	TemperatureMeasurement	19.85
2024-04-05T11:46:45.215970936Z	TemperatureMeasurement	19.82
2024-04-05T11:47:46.029875526Z	TemperatureMeasurement	19.81
2024-04-05T11:48:21.447931918Z	SetHeatingPoint	21
2024-04-05T11:48:46.481230755Z	TemperatureMeasurement	19.76
2024-04-05T11:49:46.699481262Z	TemperatureMeasurement	19.76
2024-04-05T11:50:20.040561308Z	PIHeatingDemand	0x04
2024-04-05T11:50:47.077877769Z	TemperatureMeasurement	19.8
2024-04-05T11:51:47.531225776Z	TemperatureMeasurement	19.8
2024-04-05T11:52:48.026099187Z	TemperatureMeasurement	19.83
2024-04-05T11:53:48.490090018Z	TemperatureMeasurement	19.8
2024-04-05T11:54:48.966275983Z	TemperatureMeasurement	19.8
2024-04-05T11:55:22.615852362Z	PIHeatingDemand	0x07
2024-04-05T11:55:49.421135157Z	TemperatureMeasurement	19.82
2024-04-05T11:56:49.850888626Z	TemperatureMeasurement	19.81
2024-04-05T11:57:50.311359716Z	TemperatureMeasurement	19.81
2024-04-05T11:58:25.785251679Z	SetHeatingPoint	21
2024-04-05T11:58:26.854334637Z	SetHeatingPoint	12
2024-04-05T11:58:27.327959179Z	SetHeatingPoint	12
2024-04-05T11:58:50.770795140Z	TemperatureMeasurement	19.79
2024-04-05T11:59:51.247082689Z	TemperatureMeasurement	19.78
2024-04-05T12:00:24.670982207Z	PIHeatingDemand	0x00
2024-04-05T12:00:33.955064249Z	SetHeatingPoint	12
2024-04-05T12:00:34.180066249Z	TemperatureMeasurement	19.77
2024-04-05T12:00:51.714977252Z	TemperatureMeasurement	19.77
2024-04-05T12:01:52.170665300Z	TemperatureMeasurement	19.78
2024-04-05T12:02:52.632516058Z	TemperatureMeasurement	19.8
2024-04-05T12:03:53.091550356Z	TemperatureMeasurement	19.78
2024-04-05T12:04:53.934577074Z	TemperatureMeasurement	19.78
2024-04-05T12:05:54.386115790Z	TemperatureMeasurement	19.78
2024-04-05T12:06:54.574890505Z	TemperatureMeasurement	19.77
2024-04-05T12:07:54.950539637Z	TemperatureMeasurement	19.79
2024-04-05T12:08:31.425144571Z	SetHeatingPoint	12
2024-04-05T12:08:55.631937824Z	TemperatureMeasurement	19.78
2024-04-05T12:09:55.863075581Z	TemperatureMeasurement	19.78
2024-04-05T12:10:40.880026003Z	SetHeatingPoint	35
2024-04-05T12:10:40.998752170Z	SetHeatingPoint	35
2024-04-05T12:10:56.386051255Z	TemperatureMeasurement	19.79
2024-04-05T12:11:56.958601387Z	TemperatureMeasurement	19.98
2024-04-05T12:12:20.249392846Z	PIHeatingDemand	0x04
2024-04-05T12:12:57.306526699Z	TemperatureMeasurement	20.12
2024-04-05T12:13:57.750989461Z	TemperatureMeasurement	20
2024-04-05T12:14:58.197022176Z	TemperatureMeasurement	19.92
2024-04-05T12:15:58.670676600Z	TemperatureMeasurement	19.92
2024-04-05T12:16:59.130165641Z	TemperatureMeasurement	19.87
2024-04-05T12:17:22.372781227Z	PIHeatingDemand	0x0C
2024-04-05T12:17:59.634940899Z	TemperatureMeasurement	19.86
2024-04-05T12:19:00.060986906Z	TemperatureMeasurement	19.86
2024-04-05T12:20:00.512454205Z	TemperatureMeasurement	19.85
2024-04-05T12:20:45.429938197Z	SetHeatingPoint	35
2024-04-05T12:21:01.323596282Z	TemperatureMeasurement	19.85
2024-04-05T12:22:01.758750622Z	TemperatureMeasurement	19.85
2024-04-05T12:22:24.663670250Z	PIHeatingDemand	0x0E
2024-04-05T12:23:01.939304671Z	TemperatureMeasurement	19.86
2024-04-05T12:24:02.331165525Z	TemperatureMeasurement	19.91
2024-04-05T12:25:02.863940453Z	TemperatureMeasurement	19.92
2024-04-05T12:26:03.262807919Z	TemperatureMeasurement	19.93
2024-04-05T12:27:03.724632426Z	TemperatureMeasurement	19.96
2024-04-05T12:27:27.290479054Z	PIHeatingDemand	0x11
2024-04-05T12:28:04.186490652Z	TemperatureMeasurement	19.95
2024-04-05T12:29:04.675288235Z	TemperatureMeasurement	19.92
2024-04-05T12:30:05.183276095Z	TemperatureMeasurement	19.91
2024-04-05T12:30:50.041439100Z	SetHeatingPoint	35
2024-04-05T12:31:05.718505602Z	TemperatureMeasurement	19.92
2024-04-05T12:32:06.064460523Z	TemperatureMeasurement	19.94
2024-04-05T12:32:29.304621924Z	PIHeatingDemand	0x13
2024-04-05T12:33:06.515344010Z	TemperatureMeasurement	19.96
2024-04-05T12:34:06.961692238Z	TemperatureMeasurement	19.99
2024-04-05T12:35:07.413610787Z	TemperatureMeasurement	20.02
2024-04-05T12:36:07.886505843Z	TemperatureMeasurement	20.05
2024-04-05T12:37:08.410851630Z	TemperatureMeasurement	20.06
2024-04-05T12:37:31.583654633Z	PIHeatingDemand	0x16
2024-04-05T12:38:09.247845596Z	TemperatureMeasurement	20.06
2024-04-05T12:39:09.465727603Z	TemperatureMeasurement	20.08
2024-04-05T12:40:09.810012933Z	TemperatureMeasurement	20.06
2024-04-05T12:40:54.890460550Z	SetHeatingPoint	35
2024-04-05T12:41:10.200997927Z	TemperatureMeasurement	20.06
2024-04-05T12:42:10.661239184Z	TemperatureMeasurement	20.08
2024-04-05T12:42:33.871494687Z	PIHeatingDemand	0x18
2024-04-05T12:43:11.114046317Z	TemperatureMeasurement	20.09
2024-04-05T12:44:11.572843997Z	TemperatureMeasurement	20.09
2024-04-05T12:45:12.061421803Z	TemperatureMeasurement	20.09
2024-04-05T12:46:12.621704819Z	TemperatureMeasurement	20.09
2024-04-05T12:47:13.030973043Z	TemperatureMeasurement	20.1
2024-04-05T12:47:36.243904004Z	PIHeatingDemand	0x1B
2024-04-05T12:48:13.488461510Z	TemperatureMeasurement	20.1
2024-04-05T12:49:13.981055532Z	TemperatureMeasurement	20.09
2024-04-05T12:50:14.471700413Z	TemperatureMeasurement	20.07
2024-04-05T12:50:59.370981390Z	SetHeatingPoint	35
2024-04-05T12:51:14.981891142Z	TemperatureMeasurement	20.07
2024-04-05T12:52:15.402122489Z	TemperatureMeasurement	20.07
2024-04-05T12:52:38.592444572Z	PIHeatingDemand	0x1D
2024-04-05T12:53:15.839874545Z	TemperatureMeasurement	20.08
2024-04-05T12:54:16.670127294Z	TemperatureMeasurement	20.07
2024-04-05T12:55:17.090325487Z	TemperatureMeasurement	20.07
2024-04-05T12:56:17.363952061Z	TemperatureMeasurement	20.07
2024-04-05T12:57:17.725093848Z	TemperatureMeasurement	20.07
2024-04-05T12:57:40.911311583Z	PIHeatingDemand	0x20
2024-04-05T12:58:18.155192578Z	TemperatureMeasurement	20.07
2024-04-05T12:59:18.580689835Z	TemperatureMeasurement	20.06
2024-04-05T13:00:19.042176266Z	TemperatureMeasurement	20.06
2024-04-05T13:01:03.923118903Z	SetHeatingPoint	35
2024-04-05T13:01:19.779957904Z	TemperatureMeasurement	20.06
2024-04-05T13:02:20.021053948Z	TemperatureMeasurement	20.07
2024-04-05T13:02:43.385701603Z	PIHeatingDemand	0x22
2024-04-05T13:03:20.519367286Z	TemperatureMeasurement	20.05
2024-04-05T13:04:21.040820590Z	TemperatureMeasurement	20.06
2024-04-05T13:05:21.492893565Z	TemperatureMeasurement	20.06
2024-04-05T13:06:21.932249985Z	TemperatureMeasurement	20.05
2024-04-05T13:07:22.297795370Z	TemperatureMeasurement	20.03
2024-04-05T13:07:45.471107213Z	PIHeatingDemand	0x25
2024-04-05T13:08:22.737888755Z	TemperatureMeasurement	20.05
2024-04-05T13:09:23.152388318Z	TemperatureMeasurement	20.05
2024-04-05T13:10:23.587431687Z	TemperatureMeasurement	20.03
2024-04-05T13:11:08.425441639Z	SetHeatingPoint	35
2024-04-05T13:11:24.399862016Z	TemperatureMeasurement	20.02
2024-04-05T13:12:24.885188648Z	TemperatureMeasurement	20.02
2024-04-05T13:12:47.811151315Z	PIHeatingDemand	0x27
2024-04-05T13:13:25.161311153Z	TemperatureMeasurement	20.02
2024-04-05T13:14:25.473038243Z	TemperatureMeasurement	20.01
2024-04-05T13:15:25.862705417Z	TemperatureMeasurement	20.02
2024-04-05T13:16:26.321154494Z	TemperatureMeasurement	20.02
2024-04-05T13:17:26.852817191Z	TemperatureMeasurement	20.02
2024-04-05T13:17:50.038358278Z	PIHeatingDemand	0x2A
2024-04-05T13:18:27.314878907Z	TemperatureMeasurement	20.04
2024-04-05T13:19:27.735521164Z	TemperatureMeasurement	20.05
2024-04-05T13:20:28.227641025Z	TemperatureMeasurement	20.04
2024-04-05T13:21:13.022120027Z	SetHeatingPoint	35
2024-04-05T13:21:28.689923987Z	TemperatureMeasurement	20.02
2024-04-05T13:22:29.109563827Z	TemperatureMeasurement	20.05
2024-04-05T13:22:52.302532872Z	PIHeatingDemand	0x2C
2024-04-05T13:23:29.584945001Z	TemperatureMeasurement	20.09
2024-04-05T13:24:30.023679231Z	TemperatureMeasurement	20.05
2024-04-05T13:25:30.493384425Z	TemperatureMeasurement	20.05
2024-04-05T13:26:30.955220224Z	TemperatureMeasurement	20.04
2024-04-05T13:27:31.561377940Z	TemperatureMeasurement	20.03
2024-04-05T13:27:54.593144276Z	PIHeatingDemand	0x2F
2024-04-05T13:28:32.401715491Z	TemperatureMeasurement	20.06
2024-04-05T13:29:32.551063122Z	TemperatureMeasurement	20.06
2024-04-05T13:30:32.846769671Z	TemperatureMeasurement	20.08
2024-04-05T13:31:17.892494134Z	SetHeatingPoint	35
2024-04-05T13:31:35.319868761Z	TemperatureMeasurement	20.09
2024-04-05T13:32:33.771825793Z	TemperatureMeasurement	20.08
2024-04-05T13:32:56.891872751Z	PIHeatingDemand	0x31
2024-04-05T13:33:34.250237836Z	TemperatureMeasurement	20.09
2024-04-05T13:34:34.702044802Z	TemperatureMeasurement	20.09
2024-04-05T13:35:35.124990601Z	TemperatureMeasurement	20.08
2024-04-05T13:36:35.672435553Z	TemperatureMeasurement	20.08
2024-04-05T13:37:36.021828358Z	TemperatureMeasurement	20.08
2024-04-05T13:37:59.193232819Z	PIHeatingDemand	0x34
2024-04-05T13:38:36.489018865Z	TemperatureMeasurement	20.06
2024-04-05T13:39:37.011219581Z	TemperatureMeasurement	20.07
2024-04-05T13:40:37.403098918Z	TemperatureMeasurement	20.07
2024-04-05T13:41:22.212595555Z	SetHeatingPoint	35
2024-04-05T13:41:37.875380807Z	TemperatureMeasurement	20.07
2024-04-05T13:42:38.492215981Z	TemperatureMeasurement	20.07
2024-04-05T13:43:01.561593608Z	PIHeatingDemand	0x36
2024-04-05T13:43:38.895199529Z	TemperatureMeasurement	20.05
2024-04-05T13:44:39.248488490Z	TemperatureMeasurement	20.08
2024-04-05T13:45:40.096240682Z	TemperatureMeasurement	20.08
2024-04-05T13:46:40.321772231Z	TemperatureMeasurement	20.07
2024-04-05T13:47:40.629948321Z	TemperatureMeasurement	20.07
2024-04-05T13:48:03.761708158Z	PIHeatingDemand	0x39
2024-04-05T13:48:41.091437553Z	TemperatureMeasurement	20.09
2024-04-05T13:49:41.564115497Z	TemperatureMeasurement	20.08
2024-04-05T13:50:42.022788796Z	TemperatureMeasurement	20.08
2024-04-05T13:51:26.822117009Z	SetHeatingPoint	35
2024-04-05T13:51:42.480980636Z	TemperatureMeasurement	20.09
2024-04-05T13:52:42.933327112Z	TemperatureMeasurement	20.1
2024-04-05T13:53:06.281222363Z	PIHeatingDemand	0x3B
2024-04-05T13:53:43.429865701Z	TemperatureMeasurement	20.12
2024-04-05T13:54:43.852113999Z	TemperatureMeasurement	20.14
2024-04-05T13:55:44.339857382Z	TemperatureMeasurement	20.28
2024-04-05T13:56:44.766657829Z	TemperatureMeasurement	20.56
2024-04-05T13:57:45.221408862Z	TemperatureMeasurement	20.61
2024-04-05T13:58:08.384609323Z	PIHeatingDemand	0x3D
2024-04-05T13:58:45.695483577Z	TemperatureMeasurement	20.56
2024-04-05T13:59:43.498383293Z	SetHeatingPoint	21
2024-04-05T13:59:43.552215418Z	SetHeatingPoint	21
2024-04-05T13:59:44.281079876Z	SetHeatingPoint	20
2024-04-05T13:59:44.827846710Z	SetHeatingPoint	20
2024-04-05T13:59:46.169867418Z	TemperatureMeasurement	20.49
2024-04-05T14:00:46.606006046Z	TemperatureMeasurement	20.43
2024-04-05T14:01:47.485116313Z	TemperatureMeasurement	20.4
2024-04-05T14:02:47.786587098Z	TemperatureMeasurement	20.34
2024-04-05T14:03:10.670757059Z	PIHeatingDemand	0x40
2024-04-05T14:03:48.242381356Z	TemperatureMeasurement	20.33
2024-04-05T14:03:56.526775648Z	SetHeatingPoint	20
2024-04-05T14:03:56.581996273Z	TemperatureMeasurement	20.33
2024-04-05T14:03:59.859872982Z	SetHeatingPoint	20
2024-04-05T14:04:00.030394940Z	TemperatureMeasurement	20.33
2024-04-05T14:04:01.863299024Z	SetHeatingPoint	20
2024-04-05T14:04:46.503890737Z	SetHeatingPoint	20
2024-04-05T14:05:01.814721994Z	SetHeatingPoint	20
2024-04-05T14:05:24.823399503Z	SetHeatingPoint	20
2024-04-05T14:05:24.871237284Z	TemperatureMeasurement	20.24
2024-04-05T14:06:11.185761712Z	SetHeatingPoint	20
2024-04-05T14:07:20.100773511Z	TemperatureMeasurement	20.21
2024-04-05T14:08:13.281285434Z	PIHeatingDemand	0x43
2024-04-05T14:09:49.046122981Z	SetHeatingPoint	20
2024-04-05T14:12:22.441120203Z	TemperatureMeasurement	20.16
2024-04-05T14:13:15.311912970Z	PIHeatingDemand	0x44
2024-04-05T14:14:51.155195617Z	SetHeatingPoint	20
2024-04-05T14:17:25.329854789Z	TemperatureMeasurement	20.1
2024-04-05T14:18:17.591472706Z	PIHeatingDemand	0x45
2024-04-05T14:19:53.389945101Z	SetHeatingPoint	20
2024-04-05T14:21:26.240478614Z	SetHeatingPoint	20.5
2024-04-05T14:21:27.257457433Z	SetHeatingPoint	20.5
2024-04-05T14:22:27.009876678Z	TemperatureMeasurement	20.08
2024-04-05T14:23:19.901526417Z	PIHeatingDemand	0x44
2024-04-05T14:25:57.669877852Z	SetHeatingPoint	21.5
2024-04-05T14:27:20.256624945Z	TemperatureMeasurement	20.19
2024-04-05T14:28:14.957117743Z	TemperatureMeasurement	20.33
2024-04-05T14:28:22.059682494Z	SetHeatingPoint	20.5
2024-04-05T14:28:22.219955244Z	PIHeatingDemand	0x09
2024-04-05T14:33:17.555858032Z	TemperatureMeasurement	20.27
2024-04-05T14:33:24.009875158Z	SetHeatingPoint	20.5
2024-04-05T14:33:24.582906158Z	PIHeatingDemand	0x0A
2024-04-05T14:38:19.428819736Z	TemperatureMeasurement	20.2
2024-04-05T14:38:26.291786903Z	SetHeatingPoint	20.5
2024-04-05T14:42:20.021854699Z	PIHeatingDemand	0x0B
2024-04-05T14:43:21.850828206Z	TemperatureMeasurement	20.19
2024-04-05T14:43:28.946471040Z	SetHeatingPoint	20.5
2024-04-05T14:47:22.411008152Z	PIHeatingDemand	0x0C
2024-04-05T14:48:24.019727034Z	TemperatureMeasurement	20.13
2024-04-05T14:48:30.885099201Z	SetHeatingPoint	20.5
2024-04-05T14:52:24.662249379Z	PIHeatingDemand	0x0D
2024-04-05T14:53:26.361168866Z	TemperatureMeasurement	20.12
2024-04-05T14:53:33.281752138Z	SetHeatingPoint	20.5
2024-04-05T14:58:20.113712753Z	PIHeatingDemand	0x0E
2024-04-05T14:58:28.705172379Z	TemperatureMeasurement	20.11
2024-04-05T14:58:35.565412589Z	SetHeatingPoint	20.5
2024-04-05T15:03:22.332221126Z	PIHeatingDemand	0x0F
2024-04-05T15:03:30.914921473Z	TemperatureMeasurement	20.08
2024-04-05T15:03:37.799881182Z	SetHeatingPoint	20.5
2024-04-05T15:08:24.661416433Z	PIHeatingDemand	0x11
2024-04-05T15:08:33.245365851Z	TemperatureMeasurement	20.04
2024-04-05T15:08:40.119944893Z	SetHeatingPoint	20.5
2024-04-05T15:13:26.971087152Z	PIHeatingDemand	0x13
2024-04-05T15:13:35.541097058Z	TemperatureMeasurement	20.03
2024-04-05T15:13:42.419935051Z	SetHeatingPoint	20.5
2024-04-05T15:18:29.435032272Z	PIHeatingDemand	0x15
2024-04-05T15:18:37.949948939Z	TemperatureMeasurement	20
2024-04-05T15:18:44.915074607Z	SetHeatingPoint	20.5
2024-04-05T15:23:31.550831349Z	PIHeatingDemand	0x17
2024-04-05T15:23:40.286575516Z	TemperatureMeasurement	19.96
2024-04-05T15:23:47.005234142Z	SetHeatingPoint	20.5
2024-04-05T15:28:33.860016439Z	PIHeatingDemand	0x1A
2024-04-05T15:28:42.449906857Z	TemperatureMeasurement	19.94
2024-04-05T15:28:49.364577608Z	SetHeatingPoint	20.5
2024-04-05T15:30:00.108983296Z	SetHeatingPoint	19
2024-04-05T15:33:36.449171520Z	PIHeatingDemand	0x1C
2024-04-05T15:33:44.799862878Z	TemperatureMeasurement	19.93
2024-04-05T15:33:52.059606441Z	SetHeatingPoint	20.5
2024-04-05T15:38:38.480971160Z	PIHeatingDemand	0x1F
2024-04-05T15:38:47.373793370Z	TemperatureMeasurement	19.9
2024-04-05T15:38:53.943340787Z	SetHeatingPoint	20.5
2024-04-05T15:43:40.771668878Z	PIHeatingDemand	0x21
2024-04-05T15:43:49.339678087Z	TemperatureMeasurement	19.91
2024-04-05T15:43:56.209880505Z	SetHeatingPoint	20.5
2024-04-05T15:48:43.121004980Z	PIHeatingDemand	0x24
2024-04-05T15:48:51.691275440Z	TemperatureMeasurement	19.89
2024-04-05T15:48:58.855154899Z	SetHeatingPoint	20.5
2024-04-05T15:53:45.451432773Z	PIHeatingDemand	0x26
2024-04-05T15:53:54.036083593Z	TemperatureMeasurement	19.85
2024-04-05T15:54:00.907700692Z	SetHeatingPoint	20.5
2024-04-05T15:58:47.681454474Z	PIHeatingDemand	0x29
2024-04-05T15:58:56.272205058Z	TemperatureMeasurement	19.86
2024-04-05T15:59:03.139863601Z	SetHeatingPoint	20.5
2024-04-05T16:03:49.962065360Z	PIHeatingDemand	0x2B
2024-04-05T16:03:58.539839528Z	TemperatureMeasurement	19.87
2024-04-05T16:04:05.405037821Z	SetHeatingPoint	20.5
2024-04-05T16:08:52.337302255Z	PIHeatingDemand	0x2E
2024-04-05T16:09:00.920531256Z	TemperatureMeasurement	19.81
2024-04-05T16:09:07.758763507Z	SetHeatingPoint	20.5
2024-04-05T16:13:54.721700884Z	PIHeatingDemand	0x30
2024-04-05T16:14:03.349863604Z	TemperatureMeasurement	19.83
2024-04-05T16:14:10.169950397Z	SetHeatingPoint	20.5
2024-04-05T16:18:56.981163132Z	PIHeatingDemand	0x33
2024-04-05T16:19:05.559675954Z	TemperatureMeasurement	19.81
2024-04-05T16:19:12.434956794Z	SetHeatingPoint	20.5
2024-04-05T16:23:59.395493044Z	PIHeatingDemand	0x35
2024-04-05T16:24:07.850036617Z	TemperatureMeasurement	19.79
2024-04-05T16:24:14.792037298Z	SetHeatingPoint	20.5
2024-04-05T16:29:01.512935704Z	PIHeatingDemand	0x38
2024-04-05T16:29:10.469637288Z	TemperatureMeasurement	19.82
2024-04-05T16:29:16.989919664Z	SetHeatingPoint	20.5
2024-04-05T16:34:03.812480034Z	PIHeatingDemand	0x3A
2024-04-05T16:34:12.394863577Z	TemperatureMeasurement	19.83
2024-04-05T16:34:19.269873161Z	SetHeatingPoint	20.5
2024-04-05T16:39:06.102804303Z	PIHeatingDemand	0x3D
2024-04-05T16:39:14.675127638Z	TemperatureMeasurement	19.84
2024-04-05T16:39:21.960801472Z	SetHeatingPoint	20.5
2024-04-05T16:44:08.411848393Z	PIHeatingDemand	0x3F
2024-04-05T16:44:16.997908061Z	TemperatureMeasurement	19.85
2024-04-05T16:44:23.881728895Z	SetHeatingPoint	20.5
2024-04-05T16:49:10.691296756Z	PIHeatingDemand	0x42
2024-04-05T16:49:19.323480299Z	TemperatureMeasurement	19.86
2024-04-05T16:49:26.139863216Z	SetHeatingPoint	20.5
2024-04-05T16:54:13.022329186Z	PIHeatingDemand	0x44
2024-04-05T16:54:21.587051309Z	TemperatureMeasurement	19.84
2024-04-05T16:54:28.445275565Z	SetHeatingPoint	20.5
2024-04-05T16:59:15.371356914Z	PIHeatingDemand	0x47
2024-04-05T16:59:23.925346898Z	TemperatureMeasurement	19.79
2024-04-05T16:59:30.799937351Z	SetHeatingPoint	20.5
2024-04-05T17:04:17.691626003Z	PIHeatingDemand	0x49
2024-04-05T17:04:26.324340879Z	TemperatureMeasurement	19.83
2024-04-05T17:04:33.195150713Z	SetHeatingPoint	20.5
2024-04-05T17:09:19.980885198Z	PIHeatingDemand	0x4C
2024-04-05T17:09:28.545052907Z	TemperatureMeasurement	19.78
2024-04-05T17:09:35.445199074Z	SetHeatingPoint	20.5
2024-04-05T17:14:22.593592247Z	PIHeatingDemand	0x4F
2024-04-05T17:14:30.855229155Z	TemperatureMeasurement	19.78
2024-04-05T17:14:37.799837614Z	SetHeatingPoint	20.5
2024-04-05T17:19:24.603779139Z	PIHeatingDemand	0x51
2024-04-05T17:19:33.451098130Z	TemperatureMeasurement	19.78
2024-04-05T17:19:40.029921107Z	SetHeatingPoint	20.5
2024-04-05T17:24:26.892670963Z	PIHeatingDemand	0x54
2024-04-05T17:24:35.469874009Z	TemperatureMeasurement	19.8
2024-04-05T17:24:42.339850470Z	SetHeatingPoint	20.5
2024-04-05T17:29:29.180674706Z	PIHeatingDemand	0x56
2024-04-05T17:29:37.757635707Z	TemperatureMeasurement	19.79
2024-04-05T17:29:45.020141167Z	SetHeatingPoint	20.5
2024-04-05T17:34:31.626599665Z	PIHeatingDemand	0x59
2024-04-05T17:34:40.509921232Z	TemperatureMeasurement	19.79
2024-04-05T17:34:47.054987964Z	SetHeatingPoint	20.5
2024-04-05T17:39:33.934500270Z	PIHeatingDemand	0x5B
2024-04-05T17:39:42.499230638Z	TemperatureMeasurement	19.73
2024-04-05T17:39:49.369849195Z	SetHeatingPoint	20.5
2024-04-05T17:44:36.202753411Z	PIHeatingDemand	0x5E
2024-04-05T17:44:44.699857526Z	TemperatureMeasurement	19.74
2024-04-05T17:44:51.572942890Z	SetHeatingPoint	20.5
2024-04-05T17:49:38.401935222Z	PIHeatingDemand	0x60
2024-04-05T17:49:46.986399640Z	TemperatureMeasurement	19.77
2024-04-05T17:49:53.845187224Z	SetHeatingPoint	20.5
2024-04-05T17:54:40.745232188Z	PIHeatingDemand	0x63
2024-04-05T17:54:49.359934183Z	TemperatureMeasurement	19.81
2024-04-05T17:54:56.179867345Z	SetHeatingPoint	20.5
2024-04-05T17:59:43.030325242Z	PIHeatingDemand	0x64
2024-04-05T17:59:51.600986993Z	TemperatureMeasurement	19.82
2024-04-05T17:59:58.469886494Z	SetHeatingPoint	20.5
2024-04-05T18:04:53.834711365Z	TemperatureMeasurement	19.81
2024-04-05T18:05:00.835652228Z	SetHeatingPoint	20.5
2024-04-05T18:09:56.574400372Z	TemperatureMeasurement	19.81
2024-04-05T18:10:03.045411540Z	SetHeatingPoint	20.5
2024-04-05T18:14:58.459863568Z	TemperatureMeasurement	19.81
2024-04-05T18:15:05.345149486Z	SetHeatingPoint	20.5
2024-04-05T18:20:00.811119657Z	TemperatureMeasurement	19.79
2024-04-05T18:20:07.729889366Z	SetHeatingPoint	20.5
2024-04-05T18:25:03.150861809Z	TemperatureMeasurement	19.81
2024-04-05T18:25:10.015200976Z	SetHeatingPoint	20.5
2024-04-05T18:30:05.400494279Z	TemperatureMeasurement	19.75
2024-04-05T18:30:12.277888197Z	SetHeatingPoint	20.5
2024-04-05T18:35:07.715187794Z	TemperatureMeasurement	19.75
2024-04-05T18:35:14.602651389Z	SetHeatingPoint	20.5
2024-04-05T18:40:10.105372650Z	TemperatureMeasurement	19.75
2024-04-05T18:40:16.969924741Z	SetHeatingPoint	20.5
2024-04-05T18:45:12.395001298Z	TemperatureMeasurement	19.75
2024-04-05T18:45:19.215421632Z	SetHeatingPoint	20.5
2024-04-05T18:50:14.681672349Z	TemperatureMeasurement	19.75
2024-04-05T18:50:21.529908767Z	SetHeatingPoint	20.5
2024-04-05T18:55:17.082089351Z	TemperatureMeasurement	19.75
2024-04-05T18:55:24.229871673Z	SetHeatingPoint	20.5
2024-04-05T19:00:19.575020816Z	TemperatureMeasurement	19.75
2024-04-05T19:00:26.209864873Z	SetHeatingPoint	20.5
2024-04-05T19:05:21.642342937Z	TemperatureMeasurement	19.75
2024-04-05T19:05:28.495268094Z	SetHeatingPoint	20.5
2024-04-05T19:10:23.877911959Z	TemperatureMeasurement	19.75
2024-04-05T19:10:30.770881835Z	SetHeatingPoint	20.5
2024-04-05T19:15:26.230888942Z	TemperatureMeasurement	19.75
2024-04-05T19:15:33.099863734Z	SetHeatingPoint	20.5
2024-04-05T19:20:28.519840853Z	TemperatureMeasurement	19.74
2024-04-05T19:20:35.379936437Z	SetHeatingPoint	20.5
2024-04-05T19:25:30.929866235Z	TemperatureMeasurement	19.73
2024-04-05T19:25:37.759853981Z	SetHeatingPoint	20.5
2024-04-05T19:30:33.169102566Z	TemperatureMeasurement	19.74
2024-04-05T19:30:40.050941650Z	SetHeatingPoint	20.5
2024-04-05T19:34:27.011205321Z	SetHeatingPoint	34.5
2024-04-05T19:35:35.609821187Z	TemperatureMeasurement	19.74
2024-04-05T19:36:20.424444505Z	TemperatureMeasurement	20
2024-04-05T19:37:20.221798221Z	TemperatureMeasurement	20.1
2024-04-05T19:38:56.908105982Z	PIHeatingDemand	0x64
2024-04-05T19:39:29.233777273Z	SetHeatingPoint	34.5
2024-04-05T19:42:20.106674479Z	TemperatureMeasurement	19.99
2024-04-05T19:44:20.089855840Z	TemperatureMeasurement	20.11
2024-04-05T19:44:31.985197779Z	SetHeatingPoint	34.5
2024-04-05T19:46:20.058139346Z	TemperatureMeasurement	20.29
2024-04-05T19:47:20.081622534Z	TemperatureMeasurement	20.4

[Mariano_Colmenarejo]

@Lech_Jonczyk

Not sure it helps, but I’m posting just in case:

Yes, can see perfectly in the logs how the valve opens or closes progressively to reach the HeatSetPoint temperature.

The capability operstingStste does not allow any value to be able to show the % opening of the valve.
I could use the capability switch level to show % valve opening from 0% to 100%