IKEA Vindstyrka air quality sensor successfully paired

[Aleksandrs_Frolovs]

Purchased today.
Resetted device, connected as Zigbee Humidity Sensor (SmartThings driver for Zigbee humidity sensor devices).
Have you found any driver to read air quality data?

[Typ44q (Michael Guidotti)]

I have a version 2 hub but can’t get it to pair. I press the link “reset” button 4x and the link icon blinks but smartthings does not see it.
Is there something i am doing wrong?

[Jeff_Gallagher]

I’m having issues in general adding to my v2 hub.

Hub v2 lost all ZigBee devices

I have powered off the hub twice for over an hour. I’ve tried putting devices in pairing mode and trying to add them to Smartthings, no dice, not found. I’ve deleted a couple on Smartthings and put the devices into pairing mode and attempted to add them by scanning for nearby devices or by choosing the device type, Sengled light. No dice. What should I be trying next? Is there any way to see if ZigBee on the hub is actually working? All my zwave devices are working fine.

[csstup (Corey Stup)]

I have a driver in development to support the VINDSTYRKA sensor. It uses the pm2.5 value as reported to calculate the CAQI (0-100) and the AQI (good, moderate, unhealthy, etc) capabilities. It is also reporting temp and humidity.

I plan on adding an attribute to display the actual pm2.5 value once I get more time.

I’ll have it for release on my channel soon.

[Andreas_Roedl]

Edit:

If you came here to find a driver for this device: here it is:

https://bestow-regional.api.smartthings.com/invite/Pw2DN18eRbj3

(Accept, Enroll, Available Drivers, …)

---

@csstup

I plan on adding an attribute to display the actual pm2.5 value once I get more time.

That would be awesome! And what about the tVOC value?

And is it possible to turn the display back light off?

[csstup (Corey Stup)]

@Andreas_Roedl

And what about the tVOC value?

And is it possible to turn the display back light off?

It doesn’t appear that the tVOC value is actually sent via Zigbee. It appears that internally it may only be calculating a relative tVOC value over time and on the small display only shows if its staying the same, rising or falling (the little arrow). There are several custom clusters that i’ve not fully explored yet though.

My backlight turns off after X minutes automatically. I doubt its controllable via Zigbee however.

[Andreas_Roedl]

Just ordered one a minute ago.

Going to examine the clusters when it arrives next week.

[csstup (Corey Stup)]

@Andreas_Roedl

Going to examine the clusters when it arrives next week.

On pairing, it reports:

Manufacturer: IKEA of Sweden Model: VINDSTYRKA
        [1]: server: Basic, Identify, Groups, TemperatureMeasurement, RelativeHumidity, 0xFC57, 0xFC7C, 0x042A, 0xFC7E | 
	   client: Identify, OTAUpgrade, PollControl, FanControl     [242]: server | client: 0x0021

[Andreas_Roedl]

IKEA E2112 control via MQTT | Zigbee2MQTT

temperature, humidity, pm25, voc_index, identify, linkquality

[csstup (Corey Stup)]

@Andreas_Roedl

pm25, voc_index

Yeah, pm2.5 is on cluster 0x0042, and voc_index (0-500) is on cluster 0xfc7e. I have voc_index implemented in code but don’t have a custom attribute for it yet either. And its odd since it cant be queried, it only sends it on a schedule.

[Andreas_Roedl]

@csstup

voc_index (0-500) is on cluster 0xfc7e

Correct.

pm2.5 is on cluster 0x0042

Zigpy has these clusters:

               INPUT_CLUSTERS: [
                    Basic.cluster_id,  # 0x0000
                    Identify.cluster_id,  # 0x0003
                    Groups.cluster_id,  # 0x0004
                    TemperatureMeasurement.cluster_id,  # 0x0402
                    RelativeHumidity.cluster_id,  # 0x0405
                    PM25.cluster_id,  # 0x042a
                    WWAH_CLUSTER_ID,  # 0xfc57
                    IKEA_CLUSTER_ID,  # 0xfc7c
                    VOCIndex.cluster_id,  # 0xfc7e
                ],
                OUTPUT_CLUSTERS: [
                    Identify.cluster_id,  # 0x0003
                    Ota.cluster_id,  # 0x0019
                    PollControl.cluster_id,  # 0x0020
                    Fan.cluster_id,  # 0x0202
                ],

Add support for IKEA VINDSTYRKA Air quality Sensor

[Andreas_Roedl]

Here’s an explanation for the VOC index:

Info_Note_VOC_Index.pdf

[Andreas_Roedl]

@csstup

I’ll have it for release on my channel soon.

If you don’t find the time for a release, could you upload the code as it is to GitHub?

[csstup (Corey Stup)]

I’ve not had a chance to clean it up yet, there’s an issue I was trying to debug where the device isn’t handling the reporting correctly and ends up flooding the network with reports every second.

[stillerson]

…as an alternative:

For those of you living in Europe: there is an affordable zigbee air quality sensor from “frient”, which works great within smartthings.

They also offer a dedicated edge driver for their device and you can use all the readings in routines as well.

This is not a sponsored post of course, i am just very happy with the brand and their devices.

[Andreas_Roedl]

But it only measures VOC and not PM2.5.

I already have the IKEA device and if I had a little more time, I’d write an edge driver for it. But that wouldn’t make sense since @csstup driver seems to be almost finished.

It’s perfectly integrated in HA by the way.

[Andreas_Roedl]

Almost there…

At this pace I’ll finish the driver by Christmas…

@csstup

there’s an issue I was trying to debug where the device isn’t handling the reporting correctly and ends up flooding the network with reports every second.

Last night I did something with my proof of concept driver and now the device is sending its data as it should. It stopped flooding the network and is sending pm2.5 at the correct interval.

Now I have to find out what I did at 3 am in the morning…

aroedl@hydra ~/devel $ grep INFO /home/aroedl/logcat1
2024-11-15T09:50:45.491294903Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:0405:0000
2024-11-15T09:50:45.493108153Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:50:45.513374153Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:042A:0000
2024-11-15T09:50:45.518048528Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: 0x042A >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:50:45.631097153Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, lqi: 0xD0, rssi: -66, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x19, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint16, MeasuredValue: 0x125C > > > >
2024-11-15T09:50:45.654809153Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: RelativeHumidity, attribute: MeasuredValue
2024-11-15T09:50:45.658038819Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":47}}
2024-11-15T09:50:45.685041444Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0x042A >, lqi: 0xC4, rssi: -66, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1A, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: SinglePrecisionFloat, SinglePrecisionFloat: (1 + 0.726562) * 2^(7) > > > >
2024-11-15T09:50:45.702691819Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: 0x042A, attribute: 0x0000
2024-11-15T09:50:45.705524903Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"fineDustLevel","capability_id":"fineDustSensor","component_id":"main","state":{"value":221}}
2024-11-15T09:51:45.521810201Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:0402:0000
2024-11-15T09:51:45.523784701Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:51:45.634939576Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xCE, rssi: -64, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1C, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Int16, MeasuredValue: 2300 > > > >
2024-11-15T09:51:45.649055035Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
2024-11-15T09:51:45.653127868Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":23.0}}
2024-11-15T09:54:15.580011128Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:0405:0000
2024-11-15T09:54:15.581919211Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:54:15.609572878Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:042A:0000
2024-11-15T09:54:15.617755919Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: 0x042A >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:54:15.759378461Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, lqi: 0xCE, rssi: -66, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1D, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint16, MeasuredValue: 0x12C0 > > > >
2024-11-15T09:54:15.772700503Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: RelativeHumidity, attribute: MeasuredValue
2024-11-15T09:54:15.776916503Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":48}}
2024-11-15T09:54:15.802688045Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0x042A >, lqi: 0xCC, rssi: -66, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: SinglePrecisionFloat, SinglePrecisionFloat: (1 + 0.691406) * 2^(9) > > > >
2024-11-15T09:54:15.816413461Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: 0x042A, attribute: 0x0000
2024-11-15T09:54:15.819402878Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"fineDustLevel","capability_id":"fineDustSensor","component_id":"main","state":{"value":866}}
2024-11-15T09:55:15.596755218Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:0402:0000
2024-11-15T09:55:15.601519635Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:55:15.734435218Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xC6, rssi: -64, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x20, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Int16, MeasuredValue: 2300 > > > >
2024-11-15T09:55:15.748890302Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
2024-11-15T09:55:15.750743968Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":23.0}}
2024-11-15T09:57:45.661993088Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:0405:0000
2024-11-15T09:57:45.666899874Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:57:45.691109347Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:042A:0000
2024-11-15T09:57:45.692676089Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: 0x042A >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:57:45.824516559Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0x042A >, lqi: 0xCC, rssi: -65, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x22, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: SinglePrecisionFloat, SinglePrecisionFloat: (1 + 0.375000) * 2^(8) > > > >
2024-11-15T09:57:45.837123485Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: 0x042A, attribute: 0x0000
2024-11-15T09:57:45.847504256Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"fineDustLevel","capability_id":"fineDustSensor","component_id":"main","state":{"value":352}}
2024-11-15T09:57:45.875584080Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, lqi: 0xC0, rssi: -65, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x21, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint16, MeasuredValue: 0x11F8 > > > >
2024-11-15T09:57:45.886742490Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: RelativeHumidity, attribute: MeasuredValue
2024-11-15T09:57:45.888564025Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":46}}
2024-11-15T09:58:45.681364146Z INFO Zigbee Humidity Sensor AR  Doing health check read for [39D9]:0402:0000
2024-11-15T09:58:45.683132146Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x39D9, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-11-15T09:58:45.814640855Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x39D9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xCC, rssi: -64, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x23, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Int16, MeasuredValue: 2300 > > > >
2024-11-15T09:58:45.828738146Z INFO Zigbee Humidity Sensor AR  Executing ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
2024-11-15T09:58:45.832946063Z INFO Zigbee Humidity Sensor AR  <ZigbeeDevice: 8ddc0647-ecf7-4755-bd1c-5fcc42945503 [0x39D9] (Multipurpose Sensor Test)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":23.0}}

[Mariano_Colmenarejo]

@Andreas_Roedl

Now I have to find out what I did at 3 am in the morning…

What I see in the logs:

The device is not sending any configured spontaneous reports (reportAttribute command).

Since device is not sending reports, the healt_check function is being activated and it is sequentially reading the monitored attributes and the device is responding with the reportAttributeResponse command.

This attribute monitoring function will disappear for stock drivers in the new firmware version 55.x, or so they have announced.

EDIT:
@Andreas_Roedl
Rereading the clarification about attribute monitoring in firmware version 55.x post, the correct interpretation is that the default attribute monitoring is not removed by default and what they are going to do is remove it in the stock drivers and make it optional to disable it for other non-stock drivers, in order to improve some memory and latency.

language comprehension problems!

I have tested the new firmware 55.2 and indeed if you do not disable monitoring of the device attributes with the device:remove_monitored_attribute(cluster_id, attribute_id) function, after device configuration, they will continue to be monitored as before.

[Andreas_Roedl]

Thanks, mate!

@Mariano_Colmenarejo

This attribute monitoring function will disappear by default in the new firmware version 55.x

Even for mains-powered devices?

[Mariano_Colmenarejo]

@Andreas_Roedl

Even for mains-powered devices?

I have no idea, in their announcement they did not distinguish between types of devices.

They have not released the beta version either, which should have been released between November 13th and 14th to be able to verify how it really works.