Unifi: Bad JSON data ''

[Mariusthvdb]

The problem

getting this without anything further
could it be Unifi updated the UDM pro firmware?

What version of Home Assistant Core has the issue?

2024.4.0.dev20240319

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Unifi

Link to integration documentation on our website

https://www.home-assistant.io/integrations/unifi/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: aiounifi.interfaces.messages
Bron: components/unifi/hub/websocket.py:80
Eerst voorgekomen: 19 maart 2024 om 19:05:34 (23 gebeurtenissen)
Laatst gelogd: 09:15:16

Bad JSON data ''

Additional information

on official release channel:

[home-assistant]

Hey there @Kane610, mind taking a look at this issue as it has been labeled with an integration (unifi) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of unifi can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign unifi Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

unifi documentation
unifi source
_{^{(message by IssueLinks)}}

[gigatexel]

same here

[Kane610]

If you enable debug log, can you see what websocket log was posted just before the error?

When you say "without any further" does that mean you get the log but nothing bad happens?

Fixed this a month ago, I think give it a few more weeks I can probably change it to a debug log. Kane610/aiounifi@f4026ab

[Mariusthvdb]

the logging 1 line before is also empty...

2024-03-20 21:52:16.744 DEBUG (MainThread) [aiounifi.interfaces.connectivity] Websocket ''
2024-03-20 21:52:16.745 ERROR (MainThread) [aiounifi.interfaces.messages] Bad JSON data ''

there is a huge log before that though, are you in fact looking for that?

When you say "without any further" does that mean you get the log but nothing bad happens?
tbh, I meant, nothing else was logged (level error).

dont think I noticed any 'bad' behavior either no..

odd you say you fixed it a month ago, and I was only now seeing the error.

[holdestmade]

Same here, getting the same as above in debug logs. Been getting the error for a while now (few weeks I think) I assumed it was because I installed an EA version so was waiting for it be updated to Stable version before I reported it. Currently running 8.1.113

2024-03-25 10:07:13.105 DEBUG (MainThread) [aiounifi.interfaces.connectivity] Websocket ''
2024-03-25 10:07:13.106 ERROR (MainThread) [aiounifi.interfaces.messages] Bad JSON data ''

[OwlSaver]

I am seeing the same thing. Everything on my system is the current stable / release version.

[Kane610]

Thanks for reporting!

If noone reports any bad behavior in relation to this print I will quiet it with HASS 2024.5 release

[gigatexel]

Thanks for reporting!

If noone reports any bad behavior in relation to this print I will quiet it with HASS 2024.5 release

Is there any additional logging that we can enable? For specific libraries for instance?

[Kane610]

Thanks for reporting!
If noone reports any bad behavior in relation to this print I will quiet it with HASS 2024.5 release

Is there any additional logging that we can enable? For specific libraries for instance?

If you don't experience any issues then you don't need to do anything. If you want to delve into the data you can follow the debug instructions on the integration documentation page

[gigatexel]

Thanks for reporting!
If noone reports any bad behavior in relation to this print I will quiet it with HASS 2024.5 release

Is there any additional logging that we can enable? For specific libraries for instance?

If you don't experience any issues then you don't need to do anything. If you want to delve into the data you can follow the debug instructions on the integration documentation page

I understand. I'm not the code owner but I would personally not feel comfortable muting warnings for which there is no clue what causes them :-)

[Kane610]

Thanks for reporting!
If noone reports any bad behavior in relation to this print I will quiet it with HASS 2024.5 release

Is there any additional logging that we can enable? For specific libraries for instance?

If you don't experience any issues then you don't need to do anything. If you want to delve into the data you can follow the debug instructions on the integration documentation page

I understand. I'm not the code owner but I would personally not feel comfortable muting warnings for which there is no clue what causes them :-)

That's why it's visible now so we can get some knowledge around it :)

[Birdman86]

Same here...

[Kane610]

Future people don't post a "I've seen it too" message. We know it is visible. What we want to know is if it affects anything negatively.