-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Inspelning Voltage wrong reading #2323
Comments
Please add the IEEE of the device to the DP zigbee.0.info.debugmessages, wait for the device to report the voltage and then post the respective warnings in the log , which contain the reported value for the voltage and the keyword 'ELEVATED'. For an explanation of the warnings and the use of the zigbee.0.info.debugmessages state please see the wiki |
2024-12-23 15:36:07.113 warn ELEVATED publishToState: value generated '22.200000000000003' from device c4d8c8fffeeea414 for 'Load voltage' Thats the result. Its reporting a wrong voltage by itself. |
That is only half the message. What is in the matching 'message received' warning message with the raw data from the device ? A. |
ELEVATED: Zigbee Event of Type attributeReport from device "0xc4d8c8fffeeea414", incoming event: {"type":"attributeReport","device":"0xc4d8c8fffeeea414","endpoint":1,"data":{"acPowerDivisor":10,"activePower":1,"rmsCurrent":13,"rmsVoltage":223},"linkquality":160,"groupID":0,"cluster":"haElectricalMeasurement"} Here you can see rmsVoltage 223, which sounds promising. I couldnt reproduce the load voltage message. Tried everything. Rebooting, reconnecting, attached a big load and so on. |
This indicates an error at the zigbee-herdsman-converters. There will be no fix for this in the adapter. A. |
describe the problem in Detail. What do you expect to happen ? What does happen ?
It shows 22V instead of 230V. I think there is a mapping problem.
Adapter version
1.10.13
Coordinator firmware version
20230507
Coordinator
CZC
Setup
Intel NUC
Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections
No response
The text was updated successfully, but these errors were encountered: