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

Alexa don't discover devices #1309

Open elgybe opened 3 years ago

elgybe commented 3 years ago

Hello,

I am a new HA-Bridge user. I have an Echo Dot gen.3, and Ha-Bridge (5.4.0) installed on a raspberry Pi 3B (Buster). I created a HTTP device but Alexa can't discover it. I found an interesting ressource here: Web Server IP Address I have checked:

This is the HA-Bridge configuration: image image

This is the device configuration: image image

If you need extra information, please ask. Can somebody help me? Thanks in advance!

bwssytems commented 3 years ago

Install this release https://github.com/bwssytems/ha-bridge/releases/tag/v5.4.1RC1

elgybe commented 3 years ago

Thank you for answering.

I just tried with this release, but I got no detection: image The echo dot just detects itself!

I tried to restart the echo dot, and many detections without result.

bf3883 commented 3 years ago

I have the same problem. I tried with 5.4.0 and 5.4.1rc1

Guillaume-De commented 3 years ago

Hello!

Same problem for me.

The system has not worked since yesterday.

To try to fix it, I reset all my echo, deleted all my device, deleted my ha bridge db...

I switched to RC1 and since impossible nothing works.

npaisnel commented 3 years ago

many many Other threads on here with the same.

many many people with this issue...

Not something that any one has come up with a reliable solution to fix.

All sorts of ideas, but none that are repeatable.

Changing Unique ID's renumbering , 8 9 Octet setting De register-re registering the Amazon Dot Devices.. finding and deleting Amazon Devices History Deleting all and starting again..i just tried that ..and after 4 hours..still not got them back again..

Leaving 24 hours with everything de register might be the answer

Goes back beyond 5.4.0RC1 5.3.0..even further ..some times it works some times not.

npaisnel commented 3 years ago

Here is random thought..

What versions of java are people using that are having an issue ..is that going to make any difference?
I am still on Java 8...

elgybe commented 3 years ago

I am on Java 11:

$ java -version openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment (build 11.0.11+9-post-Raspbian-1deb10u1) OpenJDK Server VM (build 11.0.11+9-post-Raspbian-1deb10u1, mixed mode)

elgybe commented 3 years ago

Sorry, I just clicked on the bad button... and closed the issue

thiagoralves commented 3 years ago

I'm pretty sure HA-bridge is broken. I had the same problem and spent a whole day looking at the wiki, documentation, reading the issues here, trying everything that was suggested. I had a bunch of devices on my Alexa (legit devices made to work with Alexa out of the box) and removed them all in an attempt to add my DIY device with HA Bridge. Alexa would recognize all my devices back again, except for the HA Bridge device. Then I heard about fauxmoESP, which is basically the same thing as HA Bridge (it also emulates a HUE hub), but that goes on a microcontroller instead of a Linux/Windows host. I grabbed a little ESP8266 that I had laying around, burned the firmware on it, and my Alexa detected it in a matter of seconds! Same network, same router, same internet, same everything. My point here is not to "advertise" about another project, especially because HA Bridge is perfect for people that don't want to deal with microcontrollers and hardware. But given that fauxmoESP is open source, perhaps some of the concepts and code implemented in there for the HUE protocol could be ported over to HA Bridge, making it work back again.

Boykster commented 3 years ago

I was having the same issue - new devices not being seen, removing and re-adding not working, etc. I went through the motions - manually removed all devices, rescanned, etc. I was able to get rid of the phantom devices by manually removing each one via the alexa UI (not the remove all button) which were messing with my setup, but even after several reboots of the HA Bridge nothing was being found.

Installed 5.4.1RC1.jar and all seems OK now - all 53 of my devices were found, no duplicates, and no 'device is not responding' issues.

Make sure you fully flush your devices - one by one...painful but worth it.

npaisnel commented 3 years ago

@Boykster How does your system start the HA-Bridge JAR running? Does it use the start habridge.sh script and run as a service using systemctl ?

Secondly... if it does start like I mention above.... did you STOP the service and delete the habridge.jar and devices. db too when you upgraded the JAR ?

Or did you just leave service enabled and running ?

Boykster commented 3 years ago

I start it on boot with systemctl - here is my script that goes in /etc/init.d/

`

!/bin/sh

SERVICE_NAME=echobridge

PATH_TO_JAR=/home/share/echobridge/ha-bridge-5.3.0.jar

PATH_TO_JAR=/home/share/echobridge/ha-bridge-5.4.1RC1.jar JAR_OPTIONS="-Dupnp.config.address=192.168.1.148 -Dvera.address=192.168.1.140 -Dupnp.device.db=/home/share/echobridge/data/device.db" PID_PATH_NAME=/tmp/echobridge-pid case $1 in start) echo "Starting $SERVICE_NAME ..." if [ ! -f $PID_PATH_NAME ]; then

        nohup java -jar $JAR_OPTIONS  $PATH_TO_JAR /tmp 2>> /dev/null >> /dev/null &
                    echo $! > $PID_PATH_NAME
        echo "$SERVICE_NAME started ..."
    else
        echo "$SERVICE_NAME is already running ..."
    fi
;;
stop)
    if [ -f $PID_PATH_NAME ]; then
        PID=$(cat $PID_PATH_NAME);
        echo "$SERVICE_NAME stoping ..."
        kill $PID;
        echo "$SERVICE_NAME stopped ..."
        rm $PID_PATH_NAME
    else
        echo "$SERVICE_NAME is not running ..."
    fi
;;
restart)
    if [ -f $PID_PATH_NAME ]; then
        PID=$(cat $PID_PATH_NAME);
        echo "$SERVICE_NAME stopping ...";
        kill $PID;
        echo "$SERVICE_NAME stopped ...";
        rm $PID_PATH_NAME
        echo "$SERVICE_NAME starting ..."

        nohup nohup java -jar $JAR_OPTIONS $PATH_TO_JAR /tmp 2>> /dev/null >> /dev/null &
                    echo $! > $PID_PATH_NAME
        echo "$SERVICE_NAME started ..."
    else
        echo "$SERVICE_NAME is not running ..."
    fi
;;

esac`

service name, paths, and options lines are modified to reflect where the tool is installed and what version.

When I upgraded to a new version I copy the new jar to the existing path (in my case /home/share/echobridge) leaving the older jar there, edit this script to change the path to the new jar, and then restart the service. I didn't delete the devices.db or any of the old jar files.

npaisnel commented 3 years ago

OK, so you do stop the service .. I kept forgetting to do that. and it was causing me problems

I was having a problem with lots of settings not deleting when deleting HABridge.conf and device.db...but that was BECAUSE i did not stop my service.

I was wondering if the duplicate devices was something simple like people not Stopping the service.

i have never had duplicate devices discovered by Alexa..and I just use the delete All option

I run with a much simpler start script ` cd /home/pi/habridge rm /home/pi/habridge/habridge-log.txt nohup java -jar /home/pi/habridge/ha-bridge.jar > /home/pi/habridge/habridge-lo$ chmod 777 /home/pi/habridge/habridge-log.txt

`

the service file much simpler too..this is on a Raspberry pi

`[Unit] Description=HA Bridge Wants=network.target After=network.target

[Service] Type=simple WorkingDirectory=/home/pi/habridge ExecStart=/usr/bin/java -jar -Dconfig.file=/home/pi/habridge/data/habridge.config /home/pi/habridge/ha-bridge.jar

[Install] WantedBy=multi-user.target `

lefoimpeur commented 3 years ago

Hi,

It doesn't work for me either :( So I installed the latest version 5.4.1RC1 but it doesn't solve my problem. But in the logs I see that my echo communicates with the bridge:

06-07-2021 20:23:17.748 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:18.403 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:18.403 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:18.421 INFO Traceupnp: request of description.xml from: 192.168.1.23:80 filled in with address: 192.168.1.17:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
06-07-2021 20:23:18.431 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:18.460 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:19.055 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:19.055 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:19.706 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:19.706 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:20.358 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:20.358 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:21.009 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:21.010 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:21.661 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:23:23.317 INFO Link button pressed.... com.bwssystems.HABridge.SystemControl
06-07-2021 20:23:23.460 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:23.460 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:23.468 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:28.487 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:28.489 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:28.501 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:33.512 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:33.512 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:33.521 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:38.534 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:38.536 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:38.543 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:43.553 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:43.554 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:43.560 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:48.573 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:48.574 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:48.585 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:53.598 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:53.598 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:23:53.608 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:08.317 INFO Link button time ended.... com.bwssystems.HABridge.LinkButtonPressed
06-07-2021 20:24:12.320 INFO Link button pressed.... com.bwssystems.HABridge.SystemControl
06-07-2021 20:24:15.826 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:16.477 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:16.477 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:16.542 INFO Traceupnp: request of description.xml from: 192.168.1.23:80 filled in with address: 192.168.1.17:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
06-07-2021 20:24:16.551 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:16.553 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:16.563 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:16.577 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:16.578 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:16.588 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:17.129 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:17.131 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:17.782 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:17.782 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:18.433 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:18.433 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:19.085 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:19.085 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:19.736 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.17:80 to address: 192.168.1.23:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-07-2021 20:24:21.578 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:21.579 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:21.587 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:26.603 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:26.603 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:26.636 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:31.648 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:31.648 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:31.658 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:36.667 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:36.668 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:36.683 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:41.696 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:41.696 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:41.704 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:46.724 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:46.724 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:46.735 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:51.758 INFO Traceupnp: hue api user create requested: {"devicetype": "Echo"} from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:51.760 INFO Traceupnp: hue api user create requested for device type: Echo#192.168.1.23 and username: ecf2253a43da41a7ba6b1f90ce1997c3 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:51.771 INFO Traceupnp: hue lights list requested by user: ecf2253a43da41a7ba6b1f90ce1997c3 from address: 192.168.1.23 com.bwssystems.HABridge.hue.HueMulator
06-07-2021 20:24:57.321 INFO Link button time ended.... com.bwssystems.HABridge.LinkButtonPressed

Is anyone else in my situation or can they help me please? Thank you

arnieSkyNet commented 3 years ago

I have just re-examined the logs. the habridge seems to think my Alexa is on another IP address that it may have been on before my BTHUB got upgraded

the Alexa echo is on ip 192.168.1.1 but I see no comms with that IP. I do see this I’m log after I Say Alexa discover

23:58:49.027 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.26:45367

This ip is the address of a kodi box now

Amazon Echo HA Bridge Version 5.4.1RC1

arnieSkyNet commented 3 years ago

I switched off kodi device with that ip .26 and did an Alexa discover after requesting a command (that works) but Alexa still can’t find any new devices (I’ve added 3 new ones)

log from same habridge Vers as above:

06-15-2021 10:00:19.117 INFO Tracestate: Decode Json for url items: [{"item":"/home/pi/sbin/arnieREM.pl --noaudio --noservercheck -dc tv:mute","type":"cmdDevice"}] com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:19.118 INFO Tracestate: Calling Home device handler for type : cmdDevice com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:29.823 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.075 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.076 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.123 INFO Traceupnp: request of description.xml from: 192.168.1.1:80 filled in with address: 192.168.1.5:80 com.bwssystems.HABridge.upnp.UpnpSettingsResource
06-15-2021 10:00:30.141 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:30.186 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:30.327 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.329 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.582 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.584 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.836 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:30.838 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:31.090 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:31.091 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:31.343 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.1:50000 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:34.308 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.25:10475 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:34.560 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.25:10475 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:34.561 INFO Traceupnp: SSDP M-SEARCH packet from 192.168.1.25:10475 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:34.813 INFO Traceupnp: send upnp discovery template 1 with response address: 192.168.1.5:80 to address: 192.168.1.25:10475 com.bwssystems.HABridge.upnp.UpnpListener
06-15-2021 10:00:35.187 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:40.257 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:45.303 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:50.342 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:00:55.371 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:01:00.404 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
06-15-2021 10:01:05.453 INFO Traceupnp: hue lights list requested by user: 700d595e8cfe4bac847b406115c52d43 from address: 192.168.1.1 com.bwssystems.HABridge.hue.HueMulator
smartypantsuk commented 3 years ago

I'm pretty sure HA-bridge is broken. I had the same problem and spent a whole day looking at the wiki, documentation, reading the issues here, trying everything that was suggested. I had a bunch of devices on my Alexa (legit devices made to work with Alexa out of the box) and removed them all in an attempt to add my DIY device with HA Bridge. Alexa would recognize all my devices back again, except for the HA Bridge device. Then I heard about fauxmoESP, which is basically the same thing as HA Bridge (it also emulates a HUE hub), but that goes on a microcontroller instead of a Linux/Windows host. I grabbed a little ESP8266 that I had laying around, burned the firmware on it, and my Alexa detected it in a matter of seconds! Same network, same router, same internet, same everything. My point here is not to "advertise" about another project, especially because HA Bridge is perfect for people that don't want to deal with microcontrollers and hardware. But given that fauxmoESP is open source, perhaps some of the concepts and code implemented in there for the HUE protocol could be ported over to HA Bridge, making it work back again.

HAbridge does emulate the hue and very well. Most of the issues here are caused by Amazon's junk software design and their caching issues. While your test of the fauxmoESP is interesting, it doesn't prove much. When I installed HAbridge for the first time it worked fine also. When it comes to deleting or renaming devices, that's normally when Alexa kicks you in the balls