-
Notifications
You must be signed in to change notification settings - Fork 122
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
Invalid json sent to MQTT #491
Comments
@geduxas and @IgorYbema might also have ideas on this |
I had noticed something like this in past.. but it was mqtt server issues.. In other cases, it could lead to memory issues.. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I don’t see traces of this anymore, let’s close for now. |
Actually I can see traces of this in the last 15 days (around 60 occurrences) |
Is it possible to run some wireshark/tcpdump in mqtt server and capture network traffic from heishamon for a while.. it's important to get network level data.. |
It seems to happen quite infrequently, I’ve setup a tcpdump of mqtt traffic from heishamon and will be alerted when the issue reoccur. |
Personally I suspect some TCP stack buffer overflow.. or coruption.. strange things happens while trying to update frimware while listening in console window.. so i think something simmilar could lead to corruption of MQTT packet.. almost same happens for other's in rules... i had in past some problems with connection stability, but everything went away after i stoped accessing web page of heishamon at all. IgorYbema#138 (comment) |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
From time to time it seems invalid json messages are sent to MQTT.
For instance:
{"uptime":2253526185,"voltage":3.33,"free memory":70,"free heap":28224,"wifi":100,"mqtt reconnects":7368,"total reads":450255,"good reads":450244,"bad crc reads0]�panasonic_heat_pump/logSun Jun 9 18:03:34 2024 (2253531506): Requesting new pana
or
{"uptime0]�panasonic_heat_pump/logSun Jun 9 08:03:46 2024 (2217544209): Requesting new panasonic data0m�panasonic_heat_pump/logSun Jun 9 08:03:47 2024 (2217544756): sent bytes: 111 including checksum value: 18 0��panasonic_heat_pump/LWTOnli
it seems to happen only on
panasonic_heat_pump/stats
topic.The text was updated successfully, but these errors were encountered: