Bridge Amazon Echo to Vera, on github!

[quote=“jeff3lo, post:60, topic:187039”]@integlikewhoa

I ran into the same limitation of 10 devices. When I did a GET to my /api/devices, I see a totalElements = 12, which corresponds to the 12 devices that I added for testing.

But when I ran discover on the Echo, it could only discover 10 devices max (the first 10 that I POSTed to /api/devices). At this point, I am guessing is a limitation on Echo side.[/quote]

Thanks for confirming. I was thinking the same things but no one has reported it. I have 50 plus devices and limiting to 10 is a huge draw back for me except for using it in one one room or for master all off and all on commands.

[quote=“integlikewhoa, post:61, topic:187039”][quote=“jeff3lo, post:60, topic:187039”]@integlikewhoa

I ran into the same limitation of 10 devices. When I did a GET to my /api/devices, I see a totalElements = 12, which corresponds to the 12 devices that I added for testing.

But when I ran discover on the Echo, it could only discover 10 devices max (the first 10 that I POSTed to /api/devices). At this point, I am guessing is a limitation on Echo side.[/quote]Thanks for confirming. I was thinking the same things but no one has reported it. I have 50 plus devices and limiting to 10 is a huge draw back for me except for using it in one one room or for master all off and all on commands.[/quote]

One workaround to help out with the device limit might be to fire a scene command instead of a device command to the Vera. I think I saw someone experimenting with that earlier in the thread, but I haven’t had time to try it myself. I.e. have the Echo think there’s one device called Kitchen, which fires a scene on the Vera that turns all of the lights in the kitchen either on or off.

Not perfect but would let me cover my whole house if we could get it to work.
Thanks for confirming. I was thinking the same things but no one has reported it. I have 50 plus devices and limiting to 10 is a huge draw back for me except for using it in one one room or for master all off and all on commands.

One workaround to help out with the device limit might be to fire a scene command instead of a device command to the Vera. I think I saw someone experimenting with that earlier in the thread, but I haven't had time to try it myself.

I actually used scenes for all my Echo commands, so my in case I’m limited to 10 devices (10 “on” scenes + 10 “off” scenes). At the end, I am just confirming that scene command will indeed work with this, that’s all.

[quote=“jeff3lo, post:63, topic:187039”]

One workaround to help out with the device limit might be to fire a scene command instead of a device command to the Vera. I think I saw someone experimenting with that earlier in the thread, but I haven’t had time to try it myself.

I actually used scenes for all my Echo commands, so my in case I’m limited to 10 devices (10 “on” scenes + 10 “off” scenes). At the end, I am just confirming that scene command will indeed work with this, that’s all.[/quote]

Don’t think that was directed toward u.

10 devices or scenes is still very limited for me to make much use of right now. I have all kinds of commands from lights, to ceiling fans, to TV just in one bedroom. To group all would be bad. I also have more then 10 rooms or zones, bedrooms, kitchen, living, outside porch/rear patio, laundry, pantry, garage… So again even one 1 per room doesn’t cover it. Right now might use for like one room and a sleep or all off command… But I would like to see it open up to alot more then 10 max devices.

Which this sounds like it make be a echo problem, and might need to ask them for that support.

Seems like the Echo has problems with the real thing as well. The post mentioned 18 devices and not 10.

Still looking

Arm

[quote=“arm, post:65, topic:187039”]Seems like the Echo has problems with the real thing as well. The post mentioned 18 devices and not 10.

Still looking

Arm[/quote]

Thanks,

I understand I can do a GET to list the devices and POST to add a device to the list.

Is there a way I can edit the list (e.g. change the device name) or delete a device from the list?

Thanks.

Hope you guys can help me. I have the new 1.1 jar file from GitHub, read everything here, got the jar running on my windows box, can hit it locally and from other PC’s on the network and it sees the devices. I have both the Echo and this device running on the same flat LAN. For some reason, Echo cannot discover the devices. Windows Firewall is turned off, all the ports are avail and attached to the same PID (the jave app/server)

Still no discovery. Any ideas?

Got it working! Had to turn off network discovery in Windows 8.1 - this was apparently conflicting. Nice work Arm, this is a great advancement and thanks for all your hard work. Let’s hope they increase this from 10 device limit to 100 or more.

I just got the invite to allow me to put an Echo on order for delivery sometime in July. What is the state of development for this device? Is it ready for prime (pun intended) time?

As far as using VERA and ECHO it’s not very far along. It works but not ready for prime time. Echo still has it own limitations and is growing and was never made to work with VERA. We are currently tricking ECHO to think the Vera is HUE controller.

Thanks for the response. I think I will hold off until they allow direct Vera interaction.

I just received mine today. Noise canceling mics are very impressive. Even when playing really loud music, it can still hear me from across the room.

It might not work well with vera yet (i have not yet tried), but it does what it was designed to do extremely well. It is a well designed, high quality device.

Sadly for google, it is exactly what the nexus q should have been

Did a little writeup on this since I was so excited and made a few videos to show you guys what Im doing with the Echo

Pretty neat stuff and thanks for your help in getting this going Arm and all the others that pitched in!
[b]

http://www.MyZwave.net

[url=http://www.myzwave.net/index.php/using-amazon-echo-to-control-your-vera-powered-z-wave-smarthome/]http://www.myzwave.net/index.php/using-amazon-echo-to-control-your-vera-powered-z-wave-smarthome/[/url][/b]

So… Love this absolutely love it. Works very well. Questions though…

Can this do dimmers and how do you remove devices? I kind of screwed up on one but don’t want to redo it all.

You can see how to remove devices in my writeup, Using the “Only resting” software you can select DELETE instead of post, and then take the deviceID and use http://x.x.x.x:8080/api/devices/deviceID as the URL

The device ID is listed on each device by using http://x.x.x.x:8080/api/ and you’ll see the ID such as 3433cf19-7d63-4ca3-a08b-6ca5c5c37853

I tried to run on my QNAP NAS. All went through well until the UDP port 1900 issue. I think my NAS has multiple services using that port for upnp, most likely the media sharing DLNA and other apps. Is there an easy way to force them close, so echo can find the devices I created? Does that mean once echo have saved the devices, then the 1900 port can be used be others? It should be as there are multiple devices using it right now and them are running just fine. Every time I tried to discover devices it asked me to press button on my hue bridge, it that the way they open the port for discover devices?

I tried this too. The port 8080 is blocked on the QNAP NAS. It is used by the QNAP UI…

That is easy to fix, you either to change it or simply force to https only which will free that 8080

the netstat print out the following

udp 0 0 10.8.0.1:1900 : //this should be the Kodi
udp 0 0 JnJHomeCloud:1900 : // this should the upnp discovery service for the NAS itself
udp 0 0 localhost:1900 : //not sure about this
udp 0 0 *:1900 : //no idea
udp 0 0 *:1900 :
udp 0 0 *:1900 :

The netstat can’t show pid on this one, so not able to kill them.

Also is that possible we add a feature to mimic the button press of hue bridge to sent out the discovery request?