search

gordlea / fireboard2mqtt

8 stars 5 forks source link

Erroneous JSON: Warnings #51

Closed mattdevo1 closed 5 months ago

mattdevo1 commented 5 months ago

In my HA Core log file, I'm seeing a bunch of these non-descriptive MQTT warnings:

Logger: homeassistant.components.mqtt.mixins
Source: components/mqtt/mixins.py:557
integration: MQTT (documentation, issues)
First occurred: 9:06:29 AM (12 occurrences)
Last logged: 9:13:32 AM

Erroneous JSON:

After a bit of troubleshooting, I think it's the fireboard2mqtt add-on causing this.

I turned debug logging on for the MQTT integration and here are the logs leading up to the warning:

2024-05-05 09:10:11.309 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on fireboard2mqtt/GJKK6737J/drive/state (qos=0): b''
2024-05-05 09:10:11.309 DEBUG (MainThread) [homeassistant.components.mqtt.sensor] Ignore empty state from 'fireboard2mqtt/GJKK6737J/drive/state'
2024-05-05 09:10:11.309 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on fireboard2mqtt/GJKK6737J/drive/attributes (qos=0): b''
2024-05-05 09:10:11.309 WARNING (MainThread) [homeassistant.components.mqtt.mixins] Erroneous JSON:

@gordlea are you seeing this issue elsewhere? Any thoughts on how I can further troubleshoot/fix?

Thanks in advance!

mattdevo1 commented 5 months ago

Any thoughts @gordlea ?

I'm getting thousands of them...Are you seeing any?

Logger: homeassistant.components.mqtt.mixins Source: components/mqtt/mixins.py:557 integration: MQTT (documentation, issues) First occurred: May 13, 2024 at 10:12:02 AM (7005 occurrences) Last logged: 7:36:22 PM

Erroneous JSON:

gordlea commented 5 months ago

Sorry, I have been on other things, I will take a look this weekend.

mattdevo1 commented 5 months ago

Sorry, I have been on other things, I will take a look this weekend.

No worries! I'm fairly sure this add-on is causing the issue (if I disable it, the warnings stop). But the logs are not super descriptive and I'm not sure if there is something specific in my config that might be causing it.

Happy to help troubleshoot further if you have any idea. Thanks!

gordlea commented 5 months ago

Do you happen to have a drive hooked up?

mattdevo1 commented 5 months ago

Do you happen to have a drive hooked up?

I have a drive, but it isn't hooked up as we speak (the Fireboard is turned on/plugged into power, but I'm not currently BBQing, so the drive isn't plugged in).

I have one that I can test with if helpful though.

gordlea commented 5 months ago

I'm seeing the Erroneous JSON when i start the addon with the fireboard off. I wish it gave some indication of what the bad json was. Maybe it's sending a blank string?

This might take a little while to debug, but I will look into it 😄

mattdevo1 commented 5 months ago

I'm seeing the Erroneous JSON when i start the addon with the fireboard off. I wish it gave some indication of what the bad json was. Maybe it's sending a blank string?

This might take a little while to debug, but I will look into it 😄

Well, I'm glad I'm not the only one 😀

I'm happy to help you test, just let me know.

And thanks in advance!