Skip to content
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

Closed
kamaradclimber opened this issue Jun 9, 2024 · 10 comments
Closed

Invalid json sent to MQTT #491

kamaradclimber opened this issue Jun 9, 2024 · 10 comments
Labels

Comments

@kamaradclimber
Copy link
Contributor

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.

@kamaradclimber
Copy link
Contributor Author

@Egyras would that issue ring a bell?

Here is a count of those events on my installation (sadly I can't share the logs but you would see what I wrote in my first message, repeated over and over).

@kamaradclimber
Copy link
Contributor Author

@geduxas and @IgorYbema might also have ideas on this

@geduxas
Copy link
Contributor

geduxas commented Jul 18, 2024

I had noticed something like this in past.. but it was mqtt server issues..

In other cases, it could lead to memory issues..

Copy link

github-actions bot commented Oct 9, 2024

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.

@github-actions github-actions bot added the Stale label Oct 9, 2024
@kamaradclimber
Copy link
Contributor Author

I don’t see traces of this anymore, let’s close for now.

@kamaradclimber
Copy link
Contributor Author

Actually I can see traces of this in the last 15 days (around 60 occurrences)

@geduxas
Copy link
Contributor

geduxas commented Oct 9, 2024

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..

@kamaradclimber
Copy link
Contributor Author

It seems to happen quite infrequently, I’ve setup a tcpdump of mqtt traffic from heishamon and will be alerted when the issue reoccur.

@geduxas
Copy link
Contributor

geduxas commented Oct 10, 2024

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)
kamaradclimber/heishamon-homeassistant#248 (comment)

@github-actions github-actions bot removed the Stale label Oct 16, 2024
Copy link

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.

@github-actions github-actions bot added the Stale label Nov 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants