Bridge Amazon Echo to Vera, on github!

[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.

This is awesome. I’ve got the server running on my Netgear Ready NAS Ultra 4.

Now all we need is a Text To Speech interface so we can have Alexa give spoken feedback.

I do have one problem with my setup though. I’m not sure how to make the server and armzilla app start up on their own.

I use putty to ssh into my ReadyNAS and run the armzilla. This works fine but when I close the putty session, it apparently also kills armzilla. I need to figure out a way to have the ReadyNAS run armzilla on boot.

Try to replace the command line you use:

somecommandlinewithargs

With

nohup somecommandlinewithargs &

[quote=“mike Q, post:422, topic:187039”]This is awesome. I’ve got the server running on my Netgear Ready NAS Ultra 4.

Now all we need is a Text To Speech interface so we can have Alexa give spoken feedback.

I do have one problem with my setup though. I’m not sure how to make the server and armzilla app start up on their own.

I use putty to ssh into my ReadyNAS and run the armzilla. This works fine but when I close the putty session, it apparently also kills armzilla. I need to figure out a way to have the ReadyNAS run armzilla on boot.[/quote]

I used the guide here and you’ll notice towards the bottom they give an example of adding it to your rc.local to automatically start. Be careful with your pathing, his examples use different values and could cause problems. Also, it’s always – (two dashes) before for the --upnp.config.address statement. His example makes you think it’s just a single dash.

http://www.airedalez.net/?p=263

Roveer

Does this work with UI 1.5 ?? I have all working except my URL’s do not work

@bgrubb1 If you mean UI5 then yes it works fine.

TU is there anything wrong with this url ??
http://192.168.1.142:8080/api/devices:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1&DeviceNum=21

Yes it looks wrong as you have port 8080 listed after the IP address and it should be 3480 which you have listed further along.

So assuming that 192.168.1.142 is your vera IP and not the bridge that you’ve set up, then the format of the URL for on would be:

http://192.168.1.142:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1&DeviceNum=21

off would be:

http://192.168.1.142:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=0&DeviceNum=21

You can try these in a browser to see if they work.

If you say “Alexa, simon says …”, she will repeat anything you say. Here is an article from Hackaday where a guy hacked the Echo remote and get’s the Echo to say anything he wants. http://hackaday.com/2015/07/18/hacking-amazon-echo-through-its-remote/

Are there any settings on the Vera or anything on a networks that would prevent a direct url call to the vera from working ??

I have confirmed the vera is at 192.168.1.142 and the switch is device 21 when I launch

http://192.168.1.142:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1&DeviceNum=21
Nothing happens I can see the emulator, echo can discover devices, but the command does not work
I get the response

{ “u:SetTargetResponse”: { “JobID”: “2913” } }

Nevermind Pilot error was using altid instead of ID from advanced. Thanks for all help

First, this is an awesome bridge! However, I am having some difficulties. I have the bridge (0.2.0) up and running, configurator page up and devices added. From the configurator, I can turn lights on and off without fail.

The problem is that Alexa can’t discover the devices. I have tried to shut down everything that was using SSDP but haven’t gotten them all shut off yet. I haven’t tried moving the raspberry closer to the main switch, but will do that tonight. I’ve attached the log file for reference.

Any other ideas?

Came home this evening to find that my Echo control is no longer working. I can access the configuration page of the bridge and control lights from there, but the Echo is getting no response. I wiped out and rediscovered the devices, and it discovered all of them, but it won’t control them any longer. I know there was an update to the Echo today, has anyone else seen this issue?

nevermind - I restarted my Synology and reloaded the bridge and it started working again

I have tried everything I can think of, here is a quick snapshot of my results, I need some idea, I have googled and read, until my eyes hurt.

java -jar amazon-echo-bridge-0.2.0.jar ?upnp.config.address=192.168.2.72 TheDOS window never closes. I can get to: http://192.168.2.72:8080/configurator.html and can configure a device, name it and save it.

Then if I go to http://192.168.2.72:8080/api/devices with IE11 i get: "DO you want to open or save devise.json from 192.168.2.72

I have no idea what this is??? But of If I use Chrome I can see that the device is configured properly.

I have tried everything I can think of, here is a quick snapshot of my results, I need some idea, I have googled and read, until my eyes hurt
java -jar amazon-echo-bridge-0.2.0.jar ?upnp.config.address=192.168.2.72
DOS window never closes. I can get to: http://192.168.2.72:8080/configurator.html and can configure a device, name it and save it.
Then if I go to http://192.168.2.72:8080/api/devices with IE11 i get:

I have no idea what this is??? But of I use Chrome I get:
[{“content”:[{“id”:“3d6cc6e0-2ea0-490e-8578-6d0b78b57c31”,“name”:“Den”,“deviceType”:“switch”,“offUrl”:“http://192.168.2.243:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=0&DeviceNum=10",“onUrl”:“http://192.168.2.243:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1&DeviceNum=10”}],“facets”:[],“totalPages”:1,“totalElements”:1,“size”:1,“number”:0,“last”:true,“numberOfElements”:1,“sort”:null,"first”:true}]

So I can see that the device get configured.
ECHO can not find any devices. UGG and If I reboot my PC then can get to either URL. I have uninstalled Java and reinstalled, turned off the windows firewall. About out of ideas, I do have a PLEX sever running on this PC, if that could be an issue.

I don?t know what to try next. I even bought a WINK Hub, but that sucks, I like Vera, have had everything up on it for a year.

Is anyone running Windows 10? I am currently using Windows 7 and everything is pretty stable. I would like to upgrade to Windows 10, but don’t want to lose the ability to have Echo work with Vera.

I installed W10 on the 29th on an older laptop for testing and most of my W7 stuff still works. In all honesty, if W7 works and you use the box daily, stay away from W10 for at least 6 more months as it doesn’t look wholly stable yet. There is no way in h*ll I will be installing it on my workstation any time soon.

It’s pretty much tattling everything you do back to Redmond unless you switch off a lot of that.
You can’t use Cortana unless you are logged in with an MS account
Unless you disable it, hidden in the advanced settings, MS uses your internet connecting for it’s P2P Windows updates. Which can adversely affect your bandwidth. Especially if you pay for MB.
The built-in Edge browser does not support Java.

Those are just some of the little gems I’ve found so far and I am sure there are plenty more…

I also can not get the Echo to discover any devices if I have > 28 devices setup on the bridge

I also can not get the Echo to discover any devices if I have > 28 devices setup on the bridge[/quote]

Suggestion? Just use the bridge to trigger scenes, and don’t try to control each and every device?

Thanks BOFH. Did you try to bridge the echo to vera on the test laptop? Curious if all of this will work on Windows 10, but don’t have the resources tottery on another machine without upgrading the computer running the bridge.

"I installed W10 on the 29th on an older laptop for testing and most of my W7 stuff still works. In all honesty, if W7 works and you use the box daily, stay away from W10 for at least 6 more months as it doesn’t look wholly stable yet. There is no way in h*ll I will be installing it on my workstation any time soon.

It’s pretty much tattling everything you do back to Redmond unless you switch off a lot of that.
You can’t use Cortana unless you are logged in with an MS account
Unless you disable it, hidden in the advanced settings, MS uses your internet connecting for it’s P2P Windows updates. Which can adversely affect your bandwidth. Especially if you pay for MB.
The built-in Edge browser does not support Java.

Those are just some of the little gems I’ve found so far and I am sure there are plenty more…"

If someone wants to donate an Echo to me, I’ll be game to give it a try. :slight_smile: I’m figuring come BF, Amazon will put them on sale again so I am waiting for that as I missed the $99 Prime deal.

Vera3 UI5 UI7
Trane TZEMT400AB32 | Schlage BE369 FE599 | GE 45601 45602 45603 45604 45606 45609 45631 | Intermatic HA01C HA03C HA05C HA07C CA600 CA3000 | Aeon DSC06106 | Telguard GDC1 | Foscam FI8910W FI8905W FI9821W | D-Link 930L | Wanscam JW0011 | ZModo ZPIBH13W

…and you are waiting to save $79.99? :wink: Just saying! LOL