Problems communicating between Echo and Raspberry Pi

[hdonis]

I recently installed the amazon_echo_ha_bridge_0.2.0 on a Raspberry Pi 2 running off a wifi network. The installation of the program and the setup of the devices went OK but I'm unable to get the Echo to detect the devices. Both the RPI and Echo are on the exact same network using 2.4 Ghz wireless connection.

I turned on debugging for he amazon_bridge and can see that its receiving SSDP Discovery packets from the Echo but it doesn't appear to be responding back.

Any advice on how to fix this? I am using a Linksys e4200 (as router with WiFi) and ATT NVG589 (as modem in passthrough mode, WiFi disabled).

Thanks in advance for the help

[armzilla]

Can you also post the parameters you are sending?

[hdonis]

This is what i'm using to start the binding on the Raspberry Pi

"java -jar -Djava.net.preferIPv4Stack=true /opt/amazon_echo/amazon-echo-bridge-0.2.0.jar -–upnp.config.address=192.168.1.252 --logging.level.com.armzilla.ha.upnp=DEBUG --logging.file=ha.log"

Binding location = /opt/amazon_echo User = Running as "root"

Raspberry PI = 192.168.1.252:8080 Amazon Echo = 192.168.1.126 OpenHAB = 192.168.1.252:8081

Item configured through the configurator page

"http://192.168.1.252:8081/CMD?lightMasterWall=ON" "http://192.168.1.252:8081/CMD?lightMasterWall=OFF"

[hdonis]

One thing I noticed is that every time i restart the binding i loose the my configured items in configurator page.

Are the items supposed to be stored somewhere on the Raspberry Pi? If so, where?

[hdonis]

A TCPDump of the RPi shows this communication when i have the Echo discover devices

This is the JSON file that is being generated from the Configurator Page

[armzilla]

The embedded ES should be storing the index in the "data" directory where the jar is running. Can you try changing the name from Lights to something more unique? We have seen some issues with certain names.

[hdonis]

I changed the name from "lights" to "fan" but it didn't seem to help.

Maybe I installed the binding incorrectly.

I just downloaded the lastest .jar file to a directory and then launched it by running the command line I listed earlier in this thread.

Was there something more I needed to do? Is there an actual install process or command that I should have initially conducted?

[KevinCanon]

same problem with me, Echo doesn't find the devices. Any help?

[elliottshane]

This sounds like the problem I initially had. When I monitored the traffic with tcpdump I noticed the response to Echo had 192.168.1.1 and not the address I had the has-bridge running on. I had to edit the upnp.config.address= in the file located at: src/main/resources/application.properties before I compiled. Did this, works great! BTW, I am using with node-sonos-http-api to turn my sonos on and off....works perfect.

[twykr]

@smelliott100 - HUGE thanks for your note / fix about modifying the application.properties with the customized IP & port. This is exactly what I needed (with v0.2.1) to get my setup working.

[friedpenguin]

Without creating yet another thread with the same issue I just want to say that 0.4.0 was suffering the 'could not be discovered' issue so I launched 0.2.1 it and worked right off the bat. Strange but I'm not gonna argue since it works now!