Value {} of type <class 'dict'> is invalid for Device.identify

bremby · February 1, 2022, 10:23pm

Hi,

any idea how/where I have to look to understand the meaning of this warning message

Value {} of type <class 'dict'> is invalid for Device.identify, expected value of type typing.Optional[aiohue.v2.models.feature.IdentifyFeature]

tom_l · February 1, 2022, 10:25pm

Looks like something to do with the hue integration.

bremby · February 2, 2022, 10:42am

Cool, there is something I can do to grab some helpful log?

tom_l · February 2, 2022, 10:44am

Enabling debug logging for the integration may reveal something.

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

pedolsky · February 2, 2022, 10:59am

It’s caused by a firmware update on the bridge with a small change to the API schema we can’t parse.
It can’t hurt although the error is annoying. Will be fixed asap.

github.com/home-assistant/core

Hue: Value {} of type <class 'dict'> is invalid for Device.identify

opened 09:49AM - 27 Jan 22 UTC

closed 01:26AM - 16 Feb 22 UTC

Mariusthvdb

integration: hue

### The problem started seeing these on each startup after latest bridge upda…te. been trying to figure out why it keeps reporting 76 times, and the only mathematics I can think of is it does warn on all lights, sensors, and bridges. So leaves out any type of switch. ### What version of Home Assistant Core has the issue? 2202.0b0 ### What was the last working version of Home Assistant Core? not sure ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Hue ### Link to integration documentation on our website https://www.home-assistant.io/integrations/hue/ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt Logger: aiohue.util Source: /usr/local/lib/python3.9/site-packages/aiohue/util.py:175 First occurred: 09:25:58 (76 occurrences) Last logged: 09:25:59 Value {} of type <class 'dict'> is invalid for Device.identify, expected value of type typing.Optional[aiohue.v2.models.feature.IdentifyFeature] ``` in the log: ``` 2022-01-27 09:25:59 WARNING (MainThread) [aiohue.util] Value {} of type <class 'dict'> is invalid for Device.identify, expected value of type typing.Optional[aiohue.v2.models.feature.IdentifyFeature] 2022-01-27 09:25:59 WARNING (MainThread) [aiohue.util] Value {} of type <class 'dict'> is invalid for Device.identify, expected value of type typing.Optional[aiohue.v2.models.feature.IdentifyFeature] 2022-01-27 09:25:59 WARNING (MainThread) [aiohue.util] Value {} of type <class 'dict'> is invalid for Device.identify, expected value of type typing.Optional[aiohue.v2.models.feature.IdentifyFeature] ``` ### Additional information seems to have started after this update on the bridge: ``` swupdate2: checkforupdate: false lastchange: '2022-01-25T21:16:28' bridge: state: noupdates lastinstall: '2022-01-25T20:58:29' state: noupdates autoinstall: updatetime: T21:00:00 'on': true ``` also, I dont notice any performance issue, and all devices still work as before. chatted on this with Marcel before, but after updating to the beta and still seeing this, it no longer seems a dev-install fluke.

bremby · February 2, 2022, 11:49am

lovely, thank you so much

purplenurpleha · February 11, 2022, 3:19pm

Any progress on this fix?

tom_l · February 11, 2022, 3:26pm

This was posted 4 days ago in the issue linked above:

That said, I’m still looking into solving this but it’s a bit more work as the parser needs a small rewrite to prevent this issue not only now but any time Signify changes the message format. I hope to deliver the fix somewhere this week.

edgehassio · February 20, 2022, 4:47am

Cheers! Looking forward to a fix for this. Start-up logs will be almost clean after this.