Emulated hue after .103.2

Configuration
1

So i nuked my emulated_hue_ids.json and upgraded to .103.2. Now my log is flooded with these entries.

2019-12-19 11:15:50 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 16 not found in emulated_hue_ids.json
2019-12-19 11:15:54 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 20 not found in emulated_hue_ids.json
2019-12-19 11:16:03 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 14 not found in emulated_hue_ids.json
2019-12-19 11:16:13 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 27 not found in emulated_hue_ids.json
2019-12-19 11:16:14 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 18 not found in emulated_hue_ids.json
2019-12-19 11:16:18 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 12 not found in emulated_hue_ids.json
2019-12-19 11:16:20 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 18 not found in emulated_hue_ids.json
2019-12-19 11:16:24 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 20 not found in emulated_hue_ids.json
2019-12-19 11:16:28 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 26 not found in emulated_hue_ids.json

I then proceeded to remove emulated hue from my configuration.yaml. restarted HA, then brought it back and restarted HA again and still the system is failing to create a new emulated_hue_ids.json.

2

From the release notes:

Emulated Hue - As previous entityid were not Hue compliant, emulated_hue_ids.json will need to be cleared out and devices re-discovered and configured in Alexa / Google Home. This is a necessary growing pain to move the integration forward in a Hue-compliant fashion. - (@NobleKangaroo - #28317) (emulated_hue docs)

Sounds like the contents of emulated_hue_ids.json needed to be emptied, but still retained (as opposed to nuked altogether). What happens if you stop HASS, recreate an empty emulated_hue_ids.json manually, and start again?

3

I have tried with an empty emulated_hue_ids.json and the result is the same.

4

I figured out what is going on here. If you dont remove all emulated_hue exposed devices from alexa and google home, then those services will continue to ping the emulated_hue api. So not only do you need to nuke the emulated_hue_ids.json, but you also have to remove those devices from alexa and google home. Once removed then restart HA, then rediscover and add them. This will then trigger the emulated_hue_ids.json file to populate.

5

And Google Home? How? Did you add it to Google originally? I’m getting all these pings, too, but I removed them already. I just emptied out my Alexa devices, and I’m still getting pinged. I don’t know who’s dong it… I never added it to Google Assistant (I use google_assistant: integration).

6

Google home integration with emulated hue would only work if you grandfathered it in. I use the google assistant integration Here. Ensure that home assistant is stopped and that your emulated_hue file is removed. Then login to Alexa and remove the devices. Then start up home assistant.

7

Thanks. I figured out my problem: using tcpdump, I found out it was still my echo dot. I ended up having to un-register and re-register it to finally remove the excessive spamming of hue calls.