Emulated Hue not populating exposed domains - 0.97 Beta

[grantclem]

Home Assistant release with the issue:

Last working Home Assistant release (if known):
0.96.5

Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
Hi, since 97 beta, trying to run discovery(after purging the list) in the Amazon interface and only lights (no scenes, switches or booleans) are being discovered (~18 devices in total) . Rolled back to 0.96.5 and they are all present again (~65 in total).

host_ip: 192.168.1.2
listen_port: 8300
exposed_domains:
- light
- switch
- scene
- input_boolean

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
Possibly related?

#25581

[croghostrider]

Hi,
could you please post the result from http://home-assistant-local-ip/api/pi/lights

[grantclem]

http://192.168.1.2/api/pi/lights - not sure if this is the correct url, but "site cannot be reached" came back

[croghostrider]

please try http://192.168.1.2:8300/api/pi/lights
if you have changed the default listen_port replace your port with 8300

[grantclem]

lights.txt
So you know I have rolled back to 0.96.5 and it is working ok

[croghostrider]

can you give me the result with 97 beta running?

[grantclem]

I can and will post shortly - will have to roll back when testing is done
grantc#2859 on discord if easier

[grantclem]

lights_0.97b.txt

[grantclem]

From 66 devices down to 14 after running discover

[croghostrider]

you're right it is related to #25581.
which Alexa you have?

[grantclem]

Dots 2nd and 3rd Gen

Glad it was picked up, only noticeable after "forget all" and then re-discover

[croghostrider]

I think the issues is the 3rd Gen Dot.
On my 2nd Gen Echo everything works.
Can you try to change the listen_port to 80, turn off the 3rd Gen Dot and try to re-discover?

[grantclem]

4/5 of my echos are Gen 3 and all work fine under 0.96.5. Will try turning them off in the next day or so. If this is a Gen 3 issue what is the proposed solution? Tried it just on port 80 (Gen 3's connected) and just the Amazon devices were discovered.

[grantclem]

Test 1: All 4 Gen 3 Dots unplugged, listen_port 8300= no change (still just lights found) after discovery, emulated_hue_ids.json file re-generated (after being deleted) and showed 60+ devices

Test 2: All 4 Gen 3 Dots unplugged, listen_port 80= nothing showing after discovery, emulated_hue_ids.json file did not re-generate at all.

[croghostrider]

Test 2: All 4 Gen 3 Dots unplugged, listen_port 80= nothing showing after discovery, emulated_hue_ids.json file did not re-generate at all.

can you try to change on 0.96.5 HA the listen_port to 80 and check if you receive an output from http://192.168.1.2:80/api/pi/lights.
I think emulated Hue doesn't have the permissions to run on port 80 or the port is occupied.
The 2 Gen Dot will only work on port 80 click.

4/5 of my echos are Gen 3 and all work fine under 0.96.5. Will try turning them off in the next day or so. If this is a Gen 3 issue what is the proposed solution? Tried it just on port 80 (Gen 3's connected) and just the Amazon devices were discovered.

I thought the 3rd Gen will also only work on port 80 and one 1st or 2nd Gen Alexa is required in the same network.

Official supports the Hue Bridge V1 max 63 devices, more devices can cause problems.

[grantclem]

Test 3: Rolled back to 0.96.5 and set to port 80 = Just discovering the echos (no lights now), it did not pick up the theatre device, which is the Gen 2 device

The fact remains that all was fine prior to 0.97 beta regardless of what Gen I was using. I have purposely kept the one Gen 2 device online because I do recall reading elsewhere that it was advised. I have had 70+ plus devices before and it worked ok.

[balloob]

I am going to rollback the change because we're doing a release tomorrow. New PRs will have to be signed off by @grantclem before merging.

[croghostrider]

Hi @balloob
I did a few tests and noticed that it has nothing to do with my PR.
The issues create the black PR #25584 on the homeassistant/components/emulated_hue/upnp.py file.
Since changes on this file, the discover for the new device didn't work more.
Already known devices works.

[grantclem]

I can confirm the rollback of change #25581 has fixed the discovery issue. All exposed domains are now being discovered.

[Petro31]

None of the changes in #25584 change the code... They just make the code pretty.

[croghostrider]

you're right my Alexa had a fault.
After a factory reset all works again.

[grantclem]

Glad you found the issue - I am hoping that there won't be a repeat during 0.98 beta?