I'm currently tinkering my own custom Zigbee2MQTT converter for a PTVO firmware, but I'm facing an issue that may be a firmware bug.
I'm trying to expose UART sensor's Analog value and On/Off values with read access, so that I can issue manual reads from Zigbee2MQTT UI or API without waiting for a report.
It seems the firmware answers unexpected values when doing so.
When the value is reported by the firmware (manual wakeup or reporting interval), it works ok: I do have a serial reading on my mcu and it is received/parsed/displayed correctly by Zigbee2MQTT:
From https://www.reddit.com/r/ptvo/comments/1fdibfh/ptvo_zigbee2mqtt_custom_converter_issues/
Hello,
I'm currently tinkering my own custom Zigbee2MQTT converter for a PTVO firmware, but I'm facing an issue that may be a firmware bug.
I'm trying to expose UART sensor's Analog value and On/Off values with read access, so that I can issue manual reads from Zigbee2MQTT UI or API without waiting for a report.
It seems the firmware answers unexpected values when doing so.
When the value is reported by the firmware (manual wakeup or reporting interval), it works ok: I do have a serial reading on my mcu and it is received/parsed/displayed correctly by Zigbee2MQTT:
However, when requesting read from Zigbee2MQTT UI, the value received is not same scale and closely equals to zero (e-39 value):
The firmware configuration is the following:
Am I missing something?