search

maxbec / hassio-diyHue

Fully configurable diyHue add-on for home-assistant.
30 stars 17 forks source link

Bridge didn't find lights - Ambilight TV didn't find bridge (anymore) #17

Closed Burn-In closed 2 years ago

Burn-In commented 3 years ago

After some other issues at least the bridge wouldn't found anymore from my Ambilight TV. After 10s the scan aborts. Also HueEssentials didn't find the bridge by automatic scan. Manually i can add the bridge. But i haven't this option for my TV. And now HueEssentials didn't find any lights. So is there an opportunity to downgrade to the last version to cross check this issue?

Burn-In commented 3 years ago

That's the Debug log while HueEssentials searches for lights:

192.168.188.62 - - [03/Apr/2021 21:38:38] "POST /api/hueesscc94b211eba79c0242ac1e2103/lights HTTP/1.1" 200 - 2021-04-03 21:38:38,966 - root - INFO - in post method 2021-04-03 21:38:38,967 - root - INFO - /api/hueesscc94b211eba79c0242ac1e2103/lights 2021-04-03 21:38:38,967 - root - INFO - b'{}' 2021-04-03 21:38:38,971 - root - DEBUG - tasmota: invoked! 2021-04-03 21:38:38,974 - root - DEBUG - shelly: invoked! 2021-04-03 21:38:38,984 - root - DEBUG - ESPHome: invoked! 2021-04-03 21:38:39,000 - root - DEBUG - Hyperion: invoked! 2021-04-03 21:38:39,011 - root - DEBUG - wled discovery started 2021-04-03 21:38:39,719 - root - DEBUG - Sending M-Search response to 172.30.33.3 Assertion failed: htn.toclock_running == true (Target.cc: stopTimeOutClock: 503) Assertion failed: htn.toclock_running == true (Target.cc: stopTimeOutClock: 503) 192.168.188.62 - - [03/Apr/2021 21:38:41] "GET /api/hueesscc94b211eba79c0242ac1e2103 HTTP/1.1" 200 - Aborted (core dumped) Aborted (core dumped) 2021-04-03 21:38:41,983 - root - DEBUG - Yeelight search end 2021-04-03 21:38:44,473 - root - INFO - [] 2021-04-03 21:38:44,478 - root - INFO - registration fail, is the link button pressed? 192.168.188.62 - - [03/Apr/2021 21:38:46] "GET /api/hueesscc94b211eba79c0242ac1e2103/lights/new HTTP/1.1" 200 - 2021-04-03 21:38:47,322 - root - INFO - sync with lights 2021-04-03 21:38:49,729 - root - DEBUG - Hyperion search end 192.168.188.62 - - [03/Apr/2021 21:38:51] "GET /api/hueesscc94b211eba79c0242ac1e2103 HTTP/1.1" 200 -

Burn-In commented 3 years ago

I've changed the mac address, deleted the certicate and restarted the addon. When i perform a automatic search in HueEssentials nothing happens in the log, but when i search automatically with the all4hue app then following appears in the log and the bridge will be found. But i cant't still find lights.

192.168.188.62 - - [06/Apr/2021 12:36:11] "GET /api/368b55b096c311ebb3e60242ac1e2104 HTTP/1.1" 200 - 192.168.188.62 - - [06/Apr/2021 12:36:11] "GET /api/368b55b096c311ebb3e60242ac1e2104 HTTP/1.1" 200 - 2021-04-06 12:36:12,424 - root - INFO - sync with lights 192.168.188.62 - - [06/Apr/2021 12:36:13] "GET /api/368b55b096c311ebb3e60242ac1e2104 HTTP/1.1" 200 - 192.168.188.62 - - [06/Apr/2021 12:36:13] "GET /api/368b55b096c311ebb3e60242ac1e2104 HTTP/1.1" 200 - 2021-04-06 12:36:37,425 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443 2021-04-06 12:36:38,016 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 "POST / HTTP/1.1" 200 6 {"ok"} 192.168.188.62 - - [06/Apr/2021 12:36:40] "GET /api/config HTTP/1.1" 200 - 192.168.188.62 - - [06/Apr/2021 12:36:50] "GET /api/config HTTP/1.1" 200 - 192.168.188.62 - - [06/Apr/2021 12:36:51] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:51,228 - root - INFO - in post method 2021-04-06 12:36:51,229 - root - INFO - /api/ 2021-04-06 12:36:51,230 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:52] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:52,238 - root - INFO - in post method 2021-04-06 12:36:52,238 - root - INFO - /api/ 2021-04-06 12:36:52,239 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:53] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:53,224 - root - INFO - in post method 2021-04-06 12:36:53,224 - root - INFO - /api/ 2021-04-06 12:36:53,225 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:54] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:54,237 - root - INFO - in post method 2021-04-06 12:36:54,238 - root - INFO - /api/ 2021-04-06 12:36:54,239 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:55] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:55,258 - root - INFO - in post method 2021-04-06 12:36:55,259 - root - INFO - /api/ 2021-04-06 12:36:55,260 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:56] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:56,262 - root - INFO - in post method 2021-04-06 12:36:56,263 - root - INFO - /api/ 2021-04-06 12:36:56,264 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:57] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:57,257 - root - INFO - in post method 2021-04-06 12:36:57,258 - root - INFO - /api/ 2021-04-06 12:36:57,259 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:58] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:58,267 - root - INFO - in post method 2021-04-06 12:36:58,267 - root - INFO - /api/ 2021-04-06 12:36:58,268 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.62 - - [06/Apr/2021 12:36:59] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:36:59,303 - root - INFO - in post method 2021-04-06 12:36:59,304 - root - INFO - /api/ 2021-04-06 12:36:59,305 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 192.168.188.29 - - [06/Apr/2021 12:36:59] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 - 192.168.188.62 - - [06/Apr/2021 12:37:00] "POST /api/ HTTP/1.1" 200 - 2021-04-06 12:37:00,303 - root - INFO - in post method 2021-04-06 12:37:00,303 - root - INFO - /api/ 2021-04-06 12:37:00,304 - root - INFO - b'{ "devicetype" : "all 4 hue#SM-A715F", "generateclientkey" : true }' 2021-04-06 12:37:00,310 - root - INFO - [ { "success": { "clientkey": "321c0c2ebfa7361e55491095b2f5f9db", "username": "04ca4ed696c411ebb3e60242ac1e2104" } } ] 192.168.188.62 - - [06/Apr/2021 12:37:00] "GET /api/04ca4ed696c411ebb3e60242ac1e2104 HTTP/1.1" 200 - 2021-04-06 12:37:01,538 - root - INFO - sync with lights 192.168.188.62 - - [06/Apr/2021 12:37:06] "GET /api/04ca4ed696c411ebb3e60242ac1e2104 HTTP/1.1" 200 - 2021-04-06 12:37:08,060 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443 2021-04-06 12:37:08,277 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 "POST / HTTP/1.1" 200 6 {"ok"}

foxy82 commented 3 years ago

Can you confirm your settings? I found out that Hue Essentials requires both port 80 and port 443 to work so if you have no_serve_https ticked it wouldn't work on version 1.4.0.

Burn-In commented 3 years ago

No, it's not ticked. And i'm on 1.4.1 now.

Burn-In commented 3 years ago

Also the light seems to be ok. I had nothing changed while it stopped working. Anyhow i have setup another ESP. For [ip]/detect the light answers {"hue": "bulb","lights": 1,"modelid": "LCT015","name": "Hue RGB Light","mac": "5C:CF:7F:D5:97:BB"}

But when HueEssentials searches:

192.168.188.62 - - [06/Apr/2021 15:41:19] "POST /api/hueess3a96dd11eb8e670242ac1e2104/lights HTTP/1.1" 200 - 2021-04-06 15:41:19,804 - root - INFO - in post method 2021-04-06 15:41:19,804 - root - INFO - /api/hueess3a96dd11eb8e670242ac1e2104/lights 2021-04-06 15:41:19,805 - root - INFO - b'{}' 2021-04-06 15:41:19,807 - root - DEBUG - tasmota: invoked! 2021-04-06 15:41:19,810 - root - DEBUG - shelly: invoked! 2021-04-06 15:41:19,819 - root - DEBUG - ESPHome: invoked! 2021-04-06 15:41:19,824 - root - DEBUG - Hyperion: invoked! 2021-04-06 15:41:19,850 - root - DEBUG - wled discovery started 2021-04-06 15:41:20,152 - root - DEBUG - Sending M-Search response to 172.30.33.4 Assertion failed: htn.toclock_running == true (Target.cc: stopTimeOutClock: 503) Assertion failed: htn.toclock_running == true (Target.cc: stopTimeOutClock: 503) Aborted (core dumped) Aborted (core dumped) 2021-04-06 15:41:22,813 - root - DEBUG - Yeelight search end 2021-04-06 15:41:23,084 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443 2021-04-06 15:41:23,310 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 "POST / HTTP/1.1" 200 6 {"ok"} 2021-04-06 15:41:25,221 - root - INFO - [] 2021-04-06 15:41:25,229 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1:8080 2021-04-06 15:41:25,233 - root - INFO - registration fail, is the link button pressed?

foxy82 commented 3 years ago

I think that "core dumped" is very bad but would be a diyhue issue not a home assistant add on one

Burn-In commented 3 years ago

The error still occurse. Perhaps the main reason is actually this one: “Assertion failed: htn.toclock_running == true (Target.cc: stopTimeOutClock: 503) Aborted (core dumped)” This could be caused of a bug in nmap 7.80, fixed in 7.90. Unfortunatly i have no glue how i could find out which nmap version runs in Hass.io. Nmap seems not to run in the same container as Hass.io, so in the terminal i can not query for it.

foxy82 commented 3 years ago

Do you have the fuller log to show context?

Burn-In commented 3 years ago

See above. Or do you need even fuller?

foxy82 commented 3 years ago

If you want to see if it could be nmap try this in your config.json:

"network_scan": { "enabled": false },

Burn-In commented 3 years ago

This wasn't the cause. Same log output. :( But what could trigger this issue?

foxy82 commented 3 years ago

it is the https port - are you sure you aren't running anything on 443?

I had this issue before: https://diyhue.slack.com/archives/CC83YEPDZ/p1614428713031100

Although I'm surprised you are getting it if you are running the newer addon which doesn't use the host network.

Burn-In commented 3 years ago

I don't know what could be run on 443. Although this are the newest versions of all components.

Burn-In commented 3 years ago

After some Home Assistant updates, the issue still exists. Is there anything that I can try to pointing out the reason?

chillkiller commented 2 years ago

Same issue here, since a long time... Don't know if there is a port-double, but will make a fresh/clean HA in the next time to checkout if there is an other add-on or prog (Docker-Container) that blogs it (TV didn't find diyhue, diyhue didn't find deconz)

But I really don't have the nerve to do so at the moment, so no logs or more detailed descriptions, just wanted to report that you're not the only one... I've been hoping for over a year that diyhue in my constellation (deconz pairing) after a few bugfixes and updates running smoothly in HASSIO (OS)...

Burn-In commented 2 years ago

Hi chillkiller, My last post is almost 1 year ago. Meanwhile everything went fine and still works stable since several month. My setup: Home Assistant OS core-2022.4.6 deCONZ addon 6.12.0 diyHue addon 1.5.0 Philips Android TV