Amazon Echo Integration -- Fast, Simple and 100% native Windows

Community Playground General Discussions
#1

I wanted to give this community something back…

Based on Armzilla’s JAVA app, this is a 100% native Windows service and includes an installer and a Windows based configurator. It simply and easily connects Echo to Vera without introducing the delays, security concerns or instability of a cloud-based bridge.

Enjoy!

#2

Can I run this if I already have the Hue Hub connected to my Echo?

#3

I don’t have a Hue hub to test that concept with. However, Echo should just see this as a second Hue hub. In testing with the emulator, if I run two applications on different machines, Echo thinks I have two hues hubs and works fine with each.

#4

That’s awesome! Thank you. I will give it a shot tomorrow!

#5

Would this run on windows 10 on the raspberry pi? Sorry if this sounds like a noob question, still trying to grasp everything.

Thanks

Sent from my VS985 4G using Tapatalk

#6

I haven’t been able to get this running on Windows 10 (probably something stupid).

The logfile reports:
2016-03-10 13:43:19.0787 | VeraHuesBridge.SSDPService | WARN | Error occured starting SSDP service. | Only one usage of each socket address (protocol/network address/port) is normally permitted

I have checked the IP (IP of the machine it’s running on) and tried several ports without luck.

#7

[quote=“bluezr1, post:5, topic:191465”]Would this run on windows 10 on the raspberry pi? Sorry if this sounds like a noob question, still trying to grasp everything.

Thanks

Sent from my VS985 4G using Tapatalk[/quote]

There is already a much nicer linux version that runs on the pi that inlcudes a nice UI, Harmony hub and Nest.

Also Windows pi is much different then real windows.

#8

Way to go @ integlikewhoa.

Kick an inspired developer to the curb.

#9

[quote=“wezley69, post:8, topic:191465”]Way to go @ integlikewhoa.

Kick an inspired developer to the curb.[/quote]

Not sure what you mean, the response was for the guy that wants to run it on a pi. This original version started on a pi and as kcasey1234 said its based off that version but created for windows. So to ask to run this on a Pi he should go back to the original version.

The other problem was, in that 111 plus page thread the original code on page 1 is very outdated and doesn’t include all the features that have been added over the last year. It’s also no longer maintained by Armzilla who this all originated from. There has also been nest and Harmony hub added along with a full automated ui to add the devices and scenes from vera, nest, and harmony hub. With a Harmony remote you can turn lights on and off or run scenes on the VERA.

Well, when Kcasey1234 copied this work on over to make it work on windows, he never read threw to the end of the thread to realized that the developer has changed and that there has been like 20 new versions since then. He still posted this new version in that post but it wasn’t until after we all thought it was the same until we realized there was an issue and realized he never read that thread where he based his work off.

That thread is here for anyone confused.
http://forum.micasaverde.com/index.php/topic,31920.msg274288.html#msg274288

I’m all for a windows version but I feel if your going to modify someones work and post it in their thread (“I have created a windows version”) you could have atleast read their thread and know what was going on first. I think we would all like the windows version, but it should be current with what everyone is using from that thread or it should be made clear that its not the same when you post it at the end of that thread. That was never done as he didn’t know himself. To this day there hasn’t been any clarification on that.

#10

@kcasey1234 - thank you SO MUCH for creating this windows version AND all the support provided on Github to work through minor issues (my port was blocked, not the app issue). I know it comes down to personal preferences, and mine is that I absolutely HATE Linux/Unix with passion and I have worked in IT for 20 years. I appreciate so much this effort because I finally was able to take advantage of the Echo/Vera integration without killing myself after reading 111 pages on the previous implementation (no offence to the original developers there).

Anyone who spends their personal time to develop or enhance something for Vera and this community (especially for free) is a fantastic person. So let me tell you from the bottom of my heart - THANK YOU for all your work and it is very appreciated!

@integlikewhoa - My apologies, where exactly is the code/plugin/utility that you created? I think I missed it… but thank you for your opinion.

#11

@integlikewhoa - this guy created a windows version. There is not a lot of “rework” translating to Windows. Right? That would be the assumption. Correct?

#12

I think your just making things up at this point. Where was that posted or how is that relevant to any facts I posted? Kcasey1234 is currently looking into the rest of the code on the linux version he missed and myself and others will be greatly appreciate when he has completed it so it has the same function that is already avaiable but in windows form. Before I bought the PI I was looking for a better windows version altho you can run java on windows too.

There is work involved but “created a windows version” is a word that not even he used himself (as that’s assuming it wasn’t based on something else) and I think what he said in this thread was proper and no harm was done. It was more the main thread where he posted first that he goofed a bit without ever correcting it.

My intent was never to point this out in this thread either I was merely responding to a post where someone with a PI was trying to run this version when the original version was made for a pi. It would be pointless to convert this version back to run on a Pi when this version is based off a pi version already.

#13

Thanks for this service, it works great! I appreciate the effort.

In addition to all of my normal devices I have used three switch relays to open and close my three garage doors. It works fine but my wife and kids can’t seem to remember to say “on” or “turn on” rather than “Open” when trying to operate the doors. What would be the simplest way to set these up as a Lock, or to change parameters to allow me to use “Open” rather than “On” with Echo?

I would really appreciate any suggestions.

Thanks,

Steve

#14

[quote=“Steve78163, post:13, topic:191465”]Thanks for this service, it works great! I appreciate the effort.

In addition to all of my normal devices I have used three switch relays to open and close my three garage doors. It works fine but my wife and kids can’t seem to remember to say “on” or “turn on” rather than “Open” when trying to operate the doors. What would be the simplest way to set these up as a Lock, or to change parameters to allow me to use “Open” rather than “On” with Echo?

I would really appreciate any suggestions.

Thanks,

Steve[/quote]

Open and unlock are all recognized by Echo now. People are already using that.

#15

[quote=“integlikewhoa, post:14, topic:191465”][quote=“Steve78163, post:13, topic:191465”]Thanks for this service, it works great! I appreciate the effort.

In addition to all of my normal devices I have used three switch relays to open and close my three garage doors. It works fine but my wife and kids can’t seem to remember to say “on” or “turn on” rather than “Open” when trying to operate the doors. What would be the simplest way to set these up as a Lock, or to change parameters to allow me to use “Open” rather than “On” with Echo?

I would really appreciate any suggestions.

Thanks,

Steve[/quote]

Open and unlock are all recognized by Echo now. People are already using that.[/quote]

Yes, but only when I add the word “Lights” to the command. For instance, with my Kitchen light switch, I can say “Echo open kitchen lights” and it works. If I say “Echo open Kitchen” it does not.

The doors I want to operate are Glass Garage doors on my patio. I also have two regular garage doors that are set up thru MyQGateway Chamberlain App and show up in Vera as a “Lock”. When i use the Echo Bridge these are initiated as a “Lock” device and using “Echo open Garage” or “Echo Close Garage” it works perfectly. The Patio Garage doors are only operated by a momentary switch and I cannot get those integrated into the Chamberlain Gateway. I know it sounds like a lot of trouble just to get the spoken command right, but it really would make my life simpler. ;D

#16

The wording and such is done by AMAZON. They recently added a bunch more words which threw off things that people had setup and were working before. So unfortunately you need to be creative on how you ask echo… as the app/plugin makers don’t choose how or what works amazon decides to use.

The way this bridge is I wouldn’t think or see why a door lock in VERA would be any different then a Light bulb in vera. An Http command is sent and yes that is a different command for a lock then a light, but ECHO doesn’t know that. Does the echo phone app pickup your doors not as light but as something else? Since this is a HUE bridge mine seem to see all devices as hue lights, which so should yours. I’m thinking you have something different going on besides just some are door locks in vera vs. lights. But anyhow…

There is a VERA virtual “garage door plugin” which takes a relay node and a door sensor node and makes them into a door lock virtually. You might give that a go to make a virtual lock to control your doors then use that door lock for Echo.

#17

Hello guys,

this looks very interesting allowing to avoid the whole Java maintenance portion. I downloaded the package and read the setup document which is well written. However, it doesn’t address people who are already running the Java version of this Amazon integration.

So first question:
Is there an upgrade path without having to re-enter all the devices to the Bridge solution again and have Amazon Echo rediscover all devices? If not, what is the best method to upgrade to this native Windows version minimizing any extra work preventing starting all over again. Having to re-enter 40 devices will take quite some time.

Second question:
There is this artificial limitation of 41 devices which makes it impossible to go beyond that number which seems to be an issue of Alexa and not the bridge. Emailing Amazon didn’t help at all. Should I assume that switching to this windows version will still have this limitation of 41 devices?

Third question:
I am running Windows 10 and the setup document states the OS versions tested which does not include Windows 10 and one person wrote that he faced issues with Windows 10. Is it now working with Windows 10?

Thanks for taking the time on releasing that. Much appreciated.

#18

[quote=“Pseudomizer, post:17, topic:191465”]Hello guys,

this looks very interesting allowing to avoid the whole Java maintenance portion. I downloaded the package and read the setup document which is well written. However, it doesn’t address people who are already running the Java version of this Amazon integration.

So first question:
Is there an upgrade path without having to re-enter all the devices to the Bridge solution again and have Amazon Echo rediscover all devices? If not, what is the best method to upgrade to this native Windows version minimizing any extra work preventing starting all over again. Having to re-enter 40 devices will take quite some time.

Second question:
There is this artificial limitation of 41 devices which makes it impossible to go beyond that number which seems to be an issue of Alexa and not the bridge. Emailing Amazon didn’t help at all. Should I assume that switching to this windows version will still have this limitation of 41 devices?

Third question:
I am running Windows 10 and the setup document states the OS versions tested which does not include Windows 10 and one person wrote that he faced issues with Windows 10. Is it now working with Windows 10?

Thanks for taking the time on releasing that. Much appreciated.[/quote]

I am running it on Windows 10 and it works fine, not a single hiccup. I first put in on my Desktop and made sure everything worked the way I wanted, then switched it to an old tiny laptop that I just leave running. Both are on Windows 10.

I am hoping for Amazon and Vera to get the integration done reasonably soon. If it takes too long I may move the bridge to a Rasberry Pi.

#19

Hello
For opening and closing shutters, which terms to use?
Similarly, for the lights : Turn on / turn off , right?

#20

Is it possible to run two instances of this Windows C+ version to get past the limitation on the number of devices? currently I can’t get past 28 devices or it wont see any of them.