Open Veldkornet opened 1 year ago
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).
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
}
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:
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.
Oh okay, where can I find this information that you need?
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
)
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....
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
I will check display_unit
setting to compare reported ppb with displayed μg/m3 value
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!
Still having issue
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
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"}
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!
This is still an issue
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!
not stale
@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).
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!
💩
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!
I got the same errors with this device.
https://www.zigbee2mqtt.io/devices/VOCKQJK11LM.html#aqara-vockqjk11lm
I starts spamming the log, which kills homebridge-z2m.
It comes alive again when the value is below 1000.
I also got problems with this device:
https://www.zigbee2mqtt.io/devices/E2007.html#ikea-e2007
If you turn off the fan, sometimes the pm25 gets below zero for some reason. This will cause the same error and kill homebridge-z2m
Is there an existing issue for this?
Describe the bug
The following warnings are shown in the logs often:
From the documentation here I understand that it should be able to go well beyond 1000, but according to this the maximum is 1000. So Unclear what's going on here...
For reference, I'm using a Frient AQSZB-110
Related devices
Frient AQSZB-110
Related Devices
No response
Steps To Reproduce
No response
Expected behavior
No response
Device entry
No response
Status update
No response
Messages from this plugin
No response
This plugin
1.9.2
Homebridge
1.5.0
Zigbee2MQTT
1.30.2
Homebridge Config UI X (if applicable)
4.50.2