search

bwssytems / ha-bridge

Home automation bridge that emulates a Philips Hue light system and can control other systems such as a Vera, Harmony Hub, Nest, MiLight bulbs or any other system that has an http/https/tcp/udp interface. This is a compact impl to run on small format computers. This is impl started from this project https://github.com/armzilla/amazon-echo-ha-bridge.
Apache License 2.0
1.45k stars 198 forks source link

Only one device detected / device doesn't get updated in alexa #1056

Closed robert1978 closed 5 years ago

robert1978 commented 5 years ago

Hy everybody! I'm running ha-bridge in a container (installed from aptalca/home-automation-bridge), no physical hue-Bridge in my home.

So far ha bridge is running, AIexa Echo (2nd gen) is shown in "manage Links", I can switch the lights from the ha-bridge webinterface, but 3 problems appear: 1) Only 1 device is detected ("Arbeitszimmer" as Royal Philips Electronics device) and shown on alexa.amazon.de, sometimes Echo itself is shown as 2nd device. But device 2,3,4 on habridge are not detected. 2) With the on detected device "Arbeitszimmer", I get the message "Arbeitszimmer does not answer, please check net work connection and power supply", even switching from the ha-bridge interface is working? 3) I deleted all devices in ha-bridge (no "Arbeitszimmer" anymore)) and created different ones ("Wohnzimmer"). Very strange but still alexa only detects 1 device still with the old device name "Arbeitszimmer", device 2,3... not detected.2) I deleted all devices in ha-bridge (no "Arbeitszimmer" anymore)) and created different ones ("Wohnzimmer"). Very strange but still alexa only detects 1 device still with the old device name "Arbeitszimmer", device 2,3... not detected.

I tried UPNP send delay 650/1000/250, but without effect. I deleted all devices on alexa.amazon serveral times, does not help.

As I'm running the container, I'd like to provide description/recommandation to timberwolf server community, which could add some 100 users to the ha-bridge community. But right now, I'm stuck, but don't want to give up.

Thanks Robert

bwssytems commented 5 years ago

Would like you to turn on trace upnp and post the log and how many of your devices would have special characters...

robert1978 commented 5 years ago

Hy thanks for your reply!

Log after starting ha-bridge: 2019-01-26 15:39:44.496:INFO:oejs.Server:Thread-268: Started @69157247ms 2019-01-26 15:39:44,497 [main] INFO com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.1.252-useIface:false on web server: 192.168.1.252:8080 2019-01-26 15:39:44,498 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started.... 2019-01-26 15:39:44,499 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting.... 2019-01-26 15:39:44,500 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: eth0 valid usable IP address: /192.168.1.252 2019-01-26 15:39:44,500 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth0 to our upnp join interface set. 2019-01-26 15:39:44,501 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.1 2019-01-26 15:39:44,501 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set. 2019-01-26 15:39:44,501 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....

Should I be worried about 127.0.01 in this log? Complete Log with 1 call "Alexa, Schalte das Licht im Arbeitszimmer ein" attached.

ha-bridge.log

Thanks Robert

robert1978 commented 5 years ago

Just one more point: I'm using EDOMI to convert http get to KNX telegram. I define http device + url etc., see screenshot below. Works if I press Test ON or Test OFF in ha-bridge. http_device Do I need to specifiy an interface in menu "bridge control"? Currently I put EDOMI as an FHEM device there: fhem_config_ha-bridge Is this config required at all, as login etc. is part of the url anyhow?

Thanks Robert

bwssytems commented 5 years ago

So, first, what is the ip address 192.168.1.11? Second, does the EDOMI support the FHEM API?

robert1978 commented 5 years ago

192.168.1.11 ist the Amazon Echo. Edomi does not support FHEM API, but it creates knx telegram when receiving the http GET (entered in the bridge device). Manual switching from ha-bridge works fine.

My understanding is, that ha-bridge is called from Alexa/Echo and ha-bridge sends http command. Is this correct? API means http interface? Does ha-bridge expect a http response?

Thanks Robert

bwssytems commented 5 years ago

Then you use a manual add of an http device. Using the FHEM will just cause issues as it calls using the FHEM API and the code remaps the URL.