ZWave MCO CO2 sensor doesnt update all entities

[Mariusthvdb]

The problem

using the MCO Co2 sensor, I see all entities being created correctly upon inclusion / re-interview. However, only the CO2 level is updated frequently, while temp and humidity fall behind. Checking the Configuration options, all I see is:

while the DB shows the other entity configuration settings we'd expect: https://devices.zwave-js.io/?jumpTo=0x015f:0x0901:0x3102:0.0

a refresh value does update the entity to the correct value, so:

  - alias: Force update climate sensors
    id: force_update_climate_sensors
    trigger:
      platform: time_pattern
      minutes: /5
    action:
      service: zwave_js.refresh_value
      data:
        entity_id:
          - sensor.temperatuur_living
          - sensor.luchtvochtigheid_living
          - sensor.co2_living

in use for the time being.

What version of Home Assistant Core has the issue?

2022.10.0b6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zwave

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

zwave_js-62213aa5a398677a26e1a3354a861183-CO2 Monitor Air Quality Detector-f68980a610f4a6b39910c76e4525d6ab.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

device: MH9-CO2-WD (is printed on the backside label)

updating the temp:

while CO2 happens frequently upon change:

[homeassistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[Mariusthvdb]

more about this sensor in HA:

Apparently, the sensor's max reading is 2000. If it passes that threshold, the readings swing to 10000 and back to 2000 continuously.

Not sure this is causing havoc in the system, but there simply is no 10K reading on the device. When this happens the devoice shows ----

[MartinHjelmare]

Please capture driver debug logs from the device. If there are no driver messages for updates for the device, the integration won't see any updates either. If there are driver messages, there may be a problem in the integration.

https://www.home-assistant.io/integrations/zwave_js/#how-to-access-the-z-wave-logs

[Mariusthvdb]

ill have it run into trouble first, because currently the readings are ok, and I have automated the updating using:

  - alias: Force update climate sensors
    id: force_update_climate_sensors
    trigger:
      platform: time_pattern
      minutes: /5
    action:
      service: zwave_js.refresh_value
      data:
        entity_id:
          - sensor.temperatuur_living
          - sensor.luchtvochtigheid_living
          - sensor.co2_living

it should however update per state change, so way more frequently than 5 min. My automation wont interfere with that I suppose.

this is a quick search on the node:

mco log.txt

seems to update on my automation mainly...

and why it shows Carbon dioxide (CO₂) level: 12 is not clear to me tbh. Unless that's clipped for 1227 etc. wouldn't be very exact and helpful though to clip those values in the log?

[Mariusthvdb]

zwave_js-6.log

here's a bit more, I shouldn't have filtered on the Node 096, because it took out the value readings.... in above log, you can clearly see the alternating 10000/2000 value on the CO2 sensor.

btw, it would really be nice if we could add a filter in the logging, so we can focus on a single Node, and not have to read through these huge loggins are you maybe considering adding that filer option? it would certainly facilitate debugging

[MartinHjelmare]

If the device only sends updates for this value when your automation refreshes the value the integration won't see more updates than the driver. Please open an issue in the zwave-js project and hear if this is expected or if the driver can improve support for this device. Make sure to provide the captured driver debug logs.