You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With hass-emulated-hue I have 2 lights from zigbee2mqtt ("z2m") which aren't discovered by my Amazon Echo Plus (1st Gen, 2017), while my 2 lights from esphome are.
I suspect this is my Echo being weird, but I wanted to see if anyone has run in to this.
all 4 lights work from within home-assistant
the 2 z2m lights can be controller from the z2m web-ui or from Home-Assistant itself.
the /description.xml looks OK to me
the /api/$key$/lights does contain all the lights (2 from zigbee2mqtt + 2 from esphome)
in Hue Essentials (Android), the hass-emulated-hue bride lets me controll all 4 lights
I've hard-reset my Echo. It quickly finds the 2 esphome lights again, but never the 2 z2m lights
my devices:
❌ 1 IKEA Tradfri light connected to z2m via home-assistant addon.
Device Pantry Light; entity light.pantry_light; hass-emulated-hue "uniqueid": "zigbee2mqtt_0xe8e07efffe1ba1f5".
json response from .../lights
❌ 1 sonoff plug connected to z2m via home-assistant addon; plugged in here is a night light.
Device Switch2; entity light.switch2 (actually a plug); hass-emulated-hue "uniqueid": "zigbee2mqtt_0x00124b002456de8b"json response from .../lights
the 2 lights from z2m are devices themselves (with entities to power on/off) while the 2 from esphome are entities of my esphome device.
hass-emulated-hue generates a hue unique_id differently from the builtin/core emulated_hue. I don't know if Hue API requires a certain format.
the hass-emulated-hue unique_id is different in /homeassistant/hass-emulated-hue/emulated_hue.json than in the Hue bridge response. The JSON file stores a hash (e.g. 00:f6:9a:bd:ba:46:b1:46-bf), but API response is like zigbee2mqtt_0x00124b002456de8b.
Expected behavior
Alexa discovers all light exposed by hass-emulated-hue
Reproduction steps
with zigbee2mqtt, link a zigbee light
confirm the light does show up in emulated hue with something like Hue Essentials (android)
try to add the light to Amazon Echo
in the Alexa app: Devices > Add > Philips Hue Light > Discover Devices
result: the light is not discovered
Relevant log output
# logs of my Echo discovering emulated-hue
2024-10-21 14:31:13,510 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /description.xml
2024-10-21 14:31:13,526 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights
2024-10-21 14:31:13,680 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/6
2024-10-21 14:31:13,699 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/7
2024-10-21 14:31:13,708 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights
2024-10-21 14:39:14,089 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/6
2024-10-21 14:40:04,770 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/7
Operating system
HassOS
Install method
HassOS Addon
Version
0.3.0
Dev Version
No response
Any other information that may be helpful
Hardware
rpi3-64
slae.sh CC2652RB stick
Home-Assistant
Core 2024.10.2
Supervisor 2024.10.2
Operating System 10.3
Frontend 20241002.3
hass-emulated-hue (add-on) 0.3.0
zigbee2mqtt (add-on) 1.40.2-1
Mosquitto broker (add-on) 6.4.1
The text was updated successfully, but these errors were encountered:
@joeashcraft , i have a question. Were you able to establish the connection between the add-on and HASS without a problem?
I can use the a HASS Dashboard button to control the lights, so I'd say yes, I was able to establish the connection between the add-on and HASS. (if you had a specific test in mind other than a button on a dashboard, lmk)
Description
With hass-emulated-hue I have 2 lights from zigbee2mqtt ("z2m") which aren't discovered by my Amazon Echo Plus (1st Gen, 2017), while my 2 lights from esphome are.
I suspect this is my Echo being weird, but I wanted to see if anyone has run in to this.
my devices:
Device
Pantry Light
; entitylight.pantry_light
; hass-emulated-hue"uniqueid": "zigbee2mqtt_0xe8e07efffe1ba1f5"
.json response from
.../lights
Device
Switch2
; entitylight.switch2
(actually a plug); hass-emulated-hue"uniqueid": "zigbee2mqtt_0x00124b002456de8b"
json response from
.../lights
Bridge433
(sonoff rf bridge), Entitylight.my_floor_lamp_2
, hass-emulated-hue"uniqueid": "00:cc:d8:c1:19:d1:f8:e0-c5"
Bridge433
, Entitylight.my_reading_lamp_2
, hass-emulated-hue"uniqueid": "00:d7:50:fd:3e:47:4d:fa-99"
json response from
.../lights
my suspicions:
unique_id
differently from the builtin/core emulated_hue. I don't know if Hue API requires a certain format.unique_id
is different in/homeassistant/hass-emulated-hue/emulated_hue.json
than in the Hue bridge response. The JSON file stores a hash (e.g.00:f6:9a:bd:ba:46:b1:46-bf
), but API response is likezigbee2mqtt_0x00124b002456de8b
.Expected behavior
Alexa discovers all light exposed by hass-emulated-hue
Reproduction steps
result: the light is not discovered
Relevant log output
# logs of my Echo discovering emulated-hue 2024-10-21 14:31:13,510 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /description.xml 2024-10-21 14:31:13,526 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights 2024-10-21 14:31:13,680 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/6 2024-10-21 14:31:13,699 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/7 2024-10-21 14:31:13,708 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights 2024-10-21 14:39:14,089 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/6 2024-10-21 14:40:04,770 DEBUG emulated_hue.apiv1 -- [192.168.1.244] GET /api/redacted/lights/7
Operating system
HassOS
Install method
HassOS Addon
Version
0.3.0
Dev Version
No response
Any other information that may be helpful
Hardware
Home-Assistant
The text was updated successfully, but these errors were encountered: