Error in log WARNING (MainThread) [aiohue.util] Received unexpected bridge id: 93xxxbxxx13 #56902

[davek00997744]

SUMMARY

This error is flooding my log since the last OS and Core updates, over 462,000 entries in 4 days

ECHO DEVICES

Dot

MODULE VERSION

CONFIGURATION

CONSOLE OUTPUT

STEPS TO REPRODUCE

Just leave Home Assistant running

EXPECTED RESULTS

No errors

ACTUAL RESULTS

From log file:-

Logger: aiohue.util
Source: /usr/local/lib/python3.9/site-packages/aiohue/util.py:21
First occurred: 15:39:19 (413 occurrences)
Last logged: 15:47:19

Received unexpected bridge id: 93eadbeef13

It is logging error many thousands of time a day

[nikadaika]

I'm also facing exactly the same issue.

[GrigoriOH]

According to home-assistant/core#31708 (comment) the issue is rather prominent and might be fixable by deleting "the files mentioned in the node-red-log (found this solution in some forum)". I will search for more info and leave an edit here whether I am successful or not.

Edit:
Well, two things:

1. I was not able to get rid of the error his way, exept from just ignoring it in the logs via

logger:
  default: warning
  filters:
     aiohue.util:
      - "Received unexpected bridge id: *"

2. I should have read a bit more, as mentioned commenter said a few weeks after his solution: "Guess what’s back: the warning. Guess who has no clue why: me."

[msymms]

I am having the same issue, and the node itself has stopped working.

[oztourer]

I was getting the same error, and had suppressed it by commenting out the log message in Home Assistant. This is unfortunately a temporary fix which gets overwritten the next time my Docker instance of Home Assistant gets rebuilt.

The problem would appear to lie with the serial number 93eadbeef13 defined in this repo's /api/hue/templates/description.xml, line 17. Changing the serial from 93eadbeef13 to 93deadbeef13 should fix the problem.

I am guessing that eadbeef was a typo. I checked all the forks of this repo that are available in Node Red and none of them have changed the serial number, so all will cause the same endless log messages in Home Assistant.

[davek00997744]

I was getting the same error, and had suppressed it by commenting out the log message in Home Assistant. This is unfortunately a temporary fix which gets overwritten the next time my Docker instance of Home Assistant gets rebuilt.

The problem would appear to lie with the serial number 93eadbeef13 defined in this repo's /api/hue/templates/description.xml, line 17. Changing the serial from 93eadbeef13 to 93deadbeef13 should fix the problem.

I am guessing that eadbeef was a typo.

So how (as someone that does not understand) do we fix this issue please? :)

I can see the file and the error by clicking the link in the page header here, but how do i get that into my Node Red setup?

[oztourer]

I was getting the same error, and had suppressed it by commenting out the log message in Home Assistant. This is unfortunately a temporary fix which gets overwritten the next time my Docker instance of Home Assistant gets rebuilt.
The problem would appear to lie with the serial number 93eadbeef13 defined in this repo's /api/hue/templates/description.xml, line 17. Changing the serial from 93eadbeef13 to 93deadbeef13 should fix the problem.
I am guessing that eadbeef was a typo.

So how (as someone that does not understand) do we fix this issue please? :)

I can see the file and the error by clicking the link in the page header here, but how do i get that into my Node Red setup?

Depends on how you installed Node Red. In my case I have a volume mounted to my Docker container and this module can be found at node_modules/node-red-contrib-amazon-echo/api/hue/templates/description.xml. I edited the file in place. It will get overwritten if I reinstall this module but is easily edited again.

Hopefully this repo will get updated with a permanent fix.

[davek00997744]

I am running HASSOS, on Pi4, Node Red was an add-on I think.

I have no idea how to update this item alone, its in the pallette so an update will need to show up as an update in NR Pallette for me to get it?

[oztourer]

I am running HASSOS, on Pi4, Node Red was an add-on I think.

I have no idea how to update this item alone, its in the pallette so an update will need to show up as an update in NR Pallette for me to get it?

I have no experience with HassOS, perhaps someone else can chime in with an answer. You will need command line access to the Node Red Docker container. Can you SSH into the Pi?

[enbrander]

I was getting the same error, and had suppressed it by commenting out the log message in Home Assistant. This is unfortunately a temporary fix which gets overwritten the next time my Docker instance of Home Assistant gets rebuilt.

The problem would appear to lie with the serial number 93eadbeef13 defined in this repo's /api/hue/templates/description.xml, line 17. Changing the serial from 93eadbeef13 to 93deadbeef13 should fix the problem.

I am guessing that eadbeef was a typo. I checked all the forks of this repo that are available in Node Red and none of them have changed the serial number, so all will cause the same endless log messages in Home Assistant.

This worked for me, thank you.
I am running HASSOS with the Node Red add-on. The description.xml is stored in /config/node-red/node_modules/node-red-contrib-amazon-echo/api/hue/templates/

[davek00997744]

This worked for me, thank you. I am running HASSOS with the Node Red add-on. The description.xml is stored in /config/node-red/node_modules/node-red-contrib-amazon-echo/api/hue/templates/

Many thanks - I found the file, edited and it seems to have fixed the issue :)

I guess this will be overwritten on an update - is there a way the core could be fixed so this never returns??

[oztourer]

I guess this will be overwritten on an update

True, but this repo has not been updated in two years so you should be safe for a while...

[davek00997744]

Ok, thanks, I've bookmarked the fix at least :)

[oztourer]

I have created a pull request with a proposed fix for the serial number - hopefully datech will respond, in which case we will get a permanent fix for the issue.

[oztourer]

I checked github activity for datech and he appears to have gone AWOL. Rather than wait for a response to my pull request I have published my own fork of the code to Node Red. It is a drop-in replacement for this library with the only difference being the correct length serial number. I have not experienced any Home Assistant error messages using my version.

If you decide to give my version a try you may need to refresh your Node Red palette manager to find it.

[msymms]

I will certainly try it

On Sun, Jan 2, 2022 at 5:30 PM oztourer ***@***.***> wrote: I checked github activity for datech and he appears to have gone AWOL. Rather than wait for a response to my pull request I have published my own fork of the code <https://flows.nodered.org/node/node-red-contrib-amazon-echo-oztourer> to Node Red. It is a drop-in replacement for this library with the only difference being the correct length serial number. I have not experienced any Home Assistant error messages using my version. If you decide to give my version a try you may need to refresh your Node Red palette manager to find it. — Reply to this email directly, view it on GitHub <#176 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETKSMSUETO6DVSK6NQIXYDUUDN23ANCNFSM5FGAOZXQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

-- Mark Symms, Esq.

[davek00997744]

Thanks for your efforts here, appreciated.

[datech]

Serial number length has been fixed in v0.1.11