-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] 'VOC Density': characteristic was supplied illegal value: number 1181 exceeded maximum of 1000 #651
Comments
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.
|
The check on the limits is something that Homebridge does. 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. |
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 |
Currently I don't find this device under |
I have Aqara VOCKQJK11LM sensor and I've posted about these warnings here Here is my device entry from topic My thoughts on this
I will check |
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: |
I got the same problem with some IKEA Trådfri light bulbs. |
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
The text was updated successfully, but these errors were encountered: