[Bug] 'VOC Density': characteristic was supplied illegal value: number 1181 exceeded maximum of 1000 about homebridge-z2m HOT 19 OPEN

Can you share the exposes information of the device?

I would expect that the plugin takes over the range provided by Zigbee2MQTT (so I want to check if one is provided).

from homebridge-z2m.

Well, the VOC does work and it shows fine in HomeAssistant for example. It's just HomeBridge that complains as soon as it goes above 1000.

{
    "air_quality": "moderate",
    "battery": 100,
    "battery_low": false,
    "humidity": 52.2,
    "last_seen": "2023-03-09T18:54:19+01:00",
    "linkquality": 18,
    "temperature": 16.2,
    "update": {
        "installed_version": 262145,
        "latest_version": 262145,
        "state": "idle"
    },
    "voc": 282,
    "voltage": 3000,
    "update_available": null
}

from homebridge-z2m.

The check on the limits is something that Homebridge does.
Like I said, I believe I pass the limits provided by Zigbee2MQTT to Homebridge everywhere in my plugin.

If you can share the exposes definition for the device, I can hopefully establish if:

• The limits in the exposes information are wrong.
• There are no limits in the exposes information.
• The limits are correct and the plugin probably isn't passing them on to Homebridge in this specific converter.

If it's one of the first two scenario's, a PR in zigbee-herdsman-converters is probably needed to resolve it.
The last scenario should be resolved in this plugin.

from homebridge-z2m.

Oh okay, where can I find this information that you need?

from homebridge-z2m.

As mentioned in the form when you created this issue, the device entry can be found on the MQTT topic zigbee2mqtt/bridge/devices. This includes the exposes information as well.
(note: this is different from zigbee2mqtt/bridge/config/devices)

from homebridge-z2m.

Currently I don't find this device under zigbee2mqtt/bridge/devices, I'll keep my MQTT client open for a while though to see if it appears....

from homebridge-z2m.

I have Aqara VOCKQJK11LM sensor and I've posted about these warnings here

Here is my device entry from topic zigbee2mqtt/bridge/devices:
voc_aqara.txt

My thoughts on this

1. There should be a conversion from ppb to μg/m3 before reporting voc density to homebridge
   z2m now uses μg/m3 by default but not for all devices (mine will still report ppb).
2. Default limit of 1000 is too low both for ppb and μg/m3 values, I've recorded at least 2000 ppb for my sensor

I will check display_unit setting to compare reported ppb with displayed μg/m3 value

from homebridge-z2m.

It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!

from homebridge-z2m.

Still having issue

from homebridge-z2m.

I found that my Prolight ZIgbee bulbs gave a similar issue:
[homebridge-z2m] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 555 exceeded maximum of 500. See https.. etc
The colour temperature ended up above what is considered "warmest"
I turned it down in the exposes of the bulbs. Will report back if error persists

from homebridge-z2m.

I got the same problem with some IKEA Trådfri light bulbs.
[5/1/2023, 12:22:08 PM] [homebridge-z2m] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 157 exceeded minimum of 250. See https://homebridge.io/w/JtMGR for more info. [5/1/2023, 12:22:08 PM] [homebridge-z2m] Error: at ColorTemperature.Characteristic.characteristicWarning (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:3011:105) at ColorTemperature.Characteristic.validateUserInput (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2923:14) at ColorTemperature.Characteristic.updateValue (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2328:20) at Lightbulb.Service.updateCharacteristic (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Service.ts:795:35) at PassthroughCharacteristicMonitor.callback (/homebridge/node_modules/homebridge-z2m/src/converters/monitor.ts:28:24) at /homebridge/node_modules/homebridge-z2m/src/converters/light.ts:137:34 at Array.forEach (<anonymous>) at LightHandler.updateState (/homebridge/node_modules/homebridge-z2m/src/converters/light.ts:137:19) at Zigbee2mqttAccessory.updateStates (/homebridge/node_modules/homebridge-z2m/src/platformAccessory.ts:360:15) at Zigbee2mqttPlatform.handleDeviceUpdate (/homebridge/node_modules/homebridge-z2m/src/platform.ts:283:19) [5/1/2023, 12:22:08 PM] [homebridge-z2m] Handled device update for hallway_light: {"brightness":254,"color":{"x":0.3171,"y":0.3152},"color_mode":"xy","color_temp":157,"state":"OFF"}

from homebridge-z2m.

It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!

from homebridge-z2m.

This is still an issue

from homebridge-z2m.

It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!

from homebridge-z2m.

not stale

from homebridge-z2m.

@Veldkornet / @addvanced : The issue with the lights is different. As far as I know Zigbee2MQTT includes the range for these properties in the exposes information. If you get a value outside of this range from Zigbee2MQTT, that simply means that the range provided by Zigbee2MQTT is incorrect and should be adjusted in zigbee-herdsman-converters.

With regards to the VOC devices: I would have expected zigbee-herdsman-converters to provide the measuring range of the device as well, but apparently it does not provide this. That means the default range of HomeKit is being used, but I can extend this for sure (if I find time to do so).

from homebridge-z2m.

It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!

from homebridge-z2m.

💩

from homebridge-z2m.

It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions!

from homebridge-z2m.