search

diyhue / hassio-addon

33 stars 11 forks source link

Entertainment not working with Hue Sync Box #25

Open Jerroder opened 7 months ago

Jerroder commented 7 months ago

Hi,

I am trying to get rid of my Philips Bridge but I'd like to keep my Hue Sync Box. I tried the Emulated Hue add-ons but it's not really maintained anymore so I went with diyHue instead.

My Home Assistant is setup with a Tube's ZB dongle to connect to every Zigbee lights and ZHA to control them. diyHue connects to Home Assistant via its REST API.

I added a single bulb to diyHue just to try. I then created the Entertainment Area and I can connect the Hue Sync Box to diyHue but when I start syncing, it picks up the first color and then nothing more happens.

Here are the logs (192.168.xxx.yyy is the IP of the Sync Box):

-
2023-12-09 13:17:52,372 - flaskUI.v2restapi - INFO - start hue entertainment
x: 0
x: 0
2023-12-09 13:17:53,376 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:17:53] "PUT /clip/v2/resource/entertainment_configuration/41cdc557-cfe0-57a1-869f-ac92305a7e27 HTTP/1.1" 200 -
2023-12-09 13:17:53,407 - services.stateFetch - INFO - start lights sync
x: 0
2023-12-09 13:17:53,580 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:17:53] "GET /clip/v2/resource/entertainment_configuration HTTP/1.1" 200 -
2023-12-09 13:17:56,077 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:17:56] "{"action":"start"}GET /auth/v1 HTTP/1.1" 405 -
2023-12-09 13:18:02,040 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:02] "GET / HTTP/1.1" 200 -
2023-12-09 13:18:02,059 - werkzeug - ERROR - 192.168.xxx.yyy - - [09/Dec/2023 13:18:02] code 400, message Bad request syntax ('{"action":"start"}')
2023-12-09 13:18:02,059 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:02] "None /auth/v1 HTTP/0.9" HTTPStatus.BAD_REQUEST -
2023-12-09 13:18:02,762 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:02] "GET /api/config HTTP/1.1" 200 -
2023-12-09 13:18:02,829 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:02] "GET /auth/v1 HTTP/1.1" 200 -
x: 0
2023-12-09 13:18:03,064 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:03] "GET /clip/v2/resource/entertainment_configuration HTTP/1.1" 200 -
2023-12-09 13:18:04,419 - services.stateFetch - INFO - start lights sync
2023-12-09 13:18:08,085 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:08] "GET /auth/v1 HTTP/1.1" 200 -
2023-12-09 13:18:13,332 - werkzeug - INFO - 192.168.xxx.yyy - - [09/Dec/2023 13:18:13] "GET /auth/v1 HTTP/1.1" 200 -
2023-12-09 13:18:15,428 - services.stateFetch - INFO - start lights sync

This issue looks a lot like https://github.com/diyhue/hassio-addon/issues/11 where it uses HTTP instead of the UDP entertainment protocol, but it's supposed to be fixed in 2.0.8? (I'm running 2.0.10) Although "{"action":"start"}GET /auth/v1 HTTP/1.1" 405 might be the problem?

Maybe there's a more direct way to do this with less overhead using Zigbee2MQTT instead of ZHA? Because right now, it goes: Hue Sync Box -> diyHue -> Hass REST API -> ZHA -> dongle -> bulb

From what I understand, using Z2M would bypass the REST API and ZHA to control the bulbs through the dongle directly. Would that be better?