[quote=“hmspain, post:420, topic:187039”][quote=“Roveer, post:419, topic:187039”][quote=“hmspain, post:410, topic:187039”][quote=“Roveer, post:409, topic:187039”]I’ve tried two:
first one from the guide: java -jar amazon-echo-bridge-0.2.0.jar --upnp.config.address=192.168.0.198
second one from a post: java -jar -Djava.net.preferIPv4Stack=true amazon-echo-bridge-0.2.0.jar --upnp.config.address=192.168.0.198
Have tried with both 0.1.3 and 0.2.0 versions of the bridge. Both windows PC and RPi connected to the same switch.[/quote]
Here is the line I use (note, my RPi is 1.125);
java -jar -Djava.net.preferIPv4Stack=true /usr/local/echobridge/amazon-echo-bridge-0.1.3.jar –
upnp.config.address=192.168.1.125 > /usr/local/echobridge/echobridge.log[/quote]
OK. I noticed that you appear to have your echobridge installed in /usr/local. This is different than what I have done. First, excuse my lack of unix. I have a 25 word unix vocabulary but usually manage to get it done.
first. I’m logging in at the unix console on the pi, not through ssh via putty.
I tried going into /usr/local and mkdir an echobridge directory and I was going to cp my echobridge jar file in and use your syntax. I was unable. access denied. I then used the following syntax on my setup:
java -jar -Djava.net.preferIPv4Stack=true /home/pi/echobridge/amazon-echo-bridge-0.1.3.jar --upnp.config.address=192.168.0.198 > /home/pi/echobridge/echobridge.log
Of course nothing printed to the screen because we are directing to the log file so I have no way of seeing what’s happening. I looked at the log file an it seems just like when it’s printing to the screen.
Still unable to discover devices. Am I doing something wrong with Raspbian on the Pi? Should I try another PI OS? I’m on PI 1.12 hardware[/quote]
You must do all this as “root”. Don’t try a non-priv’d user account, or even an account that is supposed to have privs. If you can’t create /usr/local/echobridge that is a huge red flag.[/quote]
Well, I think I found the problem. Sort of… After total frustration I decided to move my PI from the switch I had it hooked to, to a switch closer to the core of my network. I’ve probably got 6-7 total switches in my network. I plugged it into one of the LAN ports on my router which is what all of the other switches cascade from. Booted it up, Putty’d into it and ran the 0.2.0 version only using the -Djava and --upnp options. No paths, no logfiles. Low and behold, I was able to discover all the devices I defined. Not entirely sure why this is, none of the switches I use are managed or have any sort of firewalling etc, but making that one change suddenly made it work.
Now turning all my devices on and off with one exception. I have a z-wave siren and it’s showing off-line. BUT… I just noticed that it’s not working from the test url commands either so I have a bit more work to do on that one.
I guess I could wireshark my switches and do a “discover devices”. My understanding is that “discover devices” sends a upnp multicast which I should be able to see on wireshark. I could then wireshark the switch that was unable to discover devices and see if it was or was not getting there. That switch was probably 3 cascades away from the router but it really shouldn’t matter.