Qolssys sending UTF-16 but qolsqw looking for UTF8 maybe?
Closed this issue · 4 comments
Before submitting this form
-
I have checked that there hasn't been a similar issue submitted in the past
-
I have updated the issue title to something relevant and clear to understand the bug I'm facing
Description of the bug
Should be able to decode the messages, but it seems IQ Panel 4 might be sending it in UTF-16. MQTT Broker isn't seeing any of this.
Expected behavior
Should see actual MQTT messages
DEBUG logs
2024-09-08 23:42:48.858152 INFO MQTT: Unable to decode MQTT message
2024-09-08 23:42:48.858522 ERROR MQTT: Unable to decode MQTT message, with Traceback: Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/appdaemon/plugins/mqtt/mqttplugin.py", line 271, in mqtt_on_message
payload = payload.decode()
^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte
2024-09-08 23:42:49.119569 INFO MQTT: Unable to decode MQTT message
2024-09-08 23:42:49.120493 ERROR MQTT: Unable to decode MQTT message, with Traceback: Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/appdaemon/plugins/mqtt/mqttplugin.py", line 271, in mqtt_on_message
payload = payload.decode()
^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte
Additional context
Issuing commands in the panel and getting these errors. Looking to decipher the payloads.
According to the error message, these seem to be raised directly in the MQTT plugin of AppDaemon ?
AppDaemon
I posted the issue at AD just recently because I noticed this also in the AD logs.
just curiious, has the new AD update to 0.16.7 solved this for you? I'm not seeing these in my logs anymore but i just updated 20 minutes ago so perhaps its to early to tell....