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

[quote=“integlikewhoa, post:7, topic:191465”][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.[/quote]
it took some doing but I was able to get it to work, make sure you set your windows firewall to allow the ports

This appears to be the most straight forward process to integrate Echo with Edge.

I have configuration issues and need some direction. The DeviceEditor is the easy route if I could make it work.

First question, what is the local IP address? Is it the computer running windows and this configuration software or the Vera Edge unit address?

If all else fails where do I find the information to manually enter the devices? The id and other info is not presented anywhere I can see.

In the DeviceEditor program nothing is found with either IP option but the service seems okay. At least the message in the services function says it is automatic and will not run unless there is a call.

Any advice or help would be appreciated.

Tom

This appears to be the most straight forward process to integrate Echo with Edge.

I have configuration issues and need some direction. The DeviceEditor is the easy route if I could make it work.

First question, what is the local IP address? Is it the computer running windows and this configuration software or the Vera Edge unit address?

If all else fails where do I find the information to manually enter the devices? The id and other info is not presented anywhere I can see.

In the DeviceEditor program nothing is found with either IP option but the service seems okay. At least the message in the services function says it is automatic and will not run unless there is a call.

Any advice or help would be appreciated.

Yes.

In the DeviceEditor program nothing is found with either IP option but the service seems okay. At least the message in the services function says it is automatic and will not run unless there is a call.

Try another port perhaps, 8081? and disable the firewall. The log file might help you.

Thank you conchordian.

With your help I have moved well down the road. All appears to be right and I am ready to get my switches included.

I am prepared to manually enter the info but I cannot find the individual device id information. Where is that recorded? Or alternatively is there an easy way for Amazon Echo to discover my devices now that I have the software working?

Tom

Help again, please.

At the point where both the Web Configurator and device editor seems to accept instructions. To try things I copied the id for my kitchen island switch (name island) and modified the on / off instruction to include the id number used by Vera. The device id is “4d494342-5342-5645-0014-000002aed683” and when I copy that in either the web or device editors I get the message “Failed to update record. StatusCode not foundReason Phrase failed to update device. Unable to locate device by id.” Then the id I put in is replaced with nothing from my system.

I am so close it is frustrating.

Tom

The device no. is just a short no., 309 in the example below.

This goes in the ON URL of the web configurator:
http://192.168.0.51:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1&DeviceNum=309

where 192.168.0.51:3480 is the IP and port of the Vera.

To run a scene:

http://192.168.0.51:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=174

to run scene no. 174.

First, I would suggest using the web editor. It’s much easier and faster as it populates all the fields and allows you to test the device. The device ID is easy. Just log into your Vera. Go to Devices and select a light you want to add. Then select “Advanced” In the upper left of the advanced screen you will see Device # followed by the ID number you need.

Thanks to conchordian and everyone of the help. Things are working and I have most of my switches included. The dimming function is wonderful.

Alexa is a challenge. It took me a while to realize that in most cases where there was no acceptance of an instruction it was the word. A little creativity to get accepted words (foyer did not work).

Now I would like to include some scene control. Looking at the scene configuration instruction, the only difference between scene on and scene off is the 15 and 16. Where does the scene number get inserted? Also (just because I was so dense on the switch id) is the scene id the number on the Vera home page following the scene name?

Is there a way to save the Hues Bridge Device Editor to a separate file so I can export it to a small 24/7 Windows computer and also to make a backup. It was a great deal of work and I would hate to recreate it.

“C:\Program Files (x86)\NanoLogic Inc\NanoVeraHuesBridge\DeviceConfig.txt” is the default location. Just copy and paste it somewhere else.

In exactly the same place as the on and off. As slief suggested, just use the web config “C:\Program Files (x86)\NanoLogic Inc\NanoVeraHuesBridge\Web Configurator\Configurator.html”, and copy and paste the scene link I posted above, changing 174 to your scene no.; and the changing the IP of your Vera.

Also (just because I was so dense on the switch id) is the scene id the number on the Vera home page following the scene name?

Yes, or on U15, you click the little spanner to edit the scene, and up the top it says, ‘Edit scene no. 174’, for example. 174 is the scene no.

Maybe use Docker and run two instances? If somebody is willing to test this, it might make our lives easier as I don’t want to deploy VMware or KVM on my PC just for that.[/quote]

I am expanding my use of devices again and now have quite a few that are in Vera but I can’t control with Echo. Is the limit of 28 devices a set parameter?

I am not familiar with Docker? is there any other way to run more than 1 instance of the bridge?

Just got this set up and tested my first device, it works great I will be adding more thank you very much.

Question on KWIKSET locks.

I had success with this bridge on Windows 10 and am really impressed. Using the device editor was confusing, but the web editor made it easy to put in the Device ID, generate the URLs, and then test on/off. I’ve add a lot of lights and switch into the Alexa app…all good.

The problem is when I try to work with my KWIKSET locks. Am looking to be able to unlock/lock the doors using Echo via the bridge. I figured since someone was getting their garage door to open and close this way, I should be able to make this work too.

When I put in the Device ID for a lock in to the “Add a new device” section of the bridge Web UI and click the “Generate URLs” button, the ON URL generated looks like this:
http://192.168.xxx.xxx:3480/data_request?id=action&output_format=json&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1&DeviceNum=53

At that point, if I test using the “test on” and “test off” buttons, nothing happens with the lock but I get a new web page that opens (with the above URL as the address) that outputs something like this:
{ “u:SetTargetResponse”: { “JobID”: “58” } }

And if I update the Alexa app at that point and ask her to Open or Unlock the door, she barfs “I’m not sure how to help you”. If I ask her to Turn On/Off the door, she says “OK” but nothing happens. So obviously the device type in the web app and the URL that define the door as a switch needs to be changed.

So I edit the serviceId=urn …SwitchPower1 and replace it with the device_type string in the Advanced tab of the devices prop sheet in UI5: urn:schemas-micasaverde-com:device:DoorLock:1 for both the ON URL and the OFF URL. The Bridge web UI “Type” column for the lock still says “switch” like all of my other devices, and now pressing the ‘test on’ ‘test off’ buttons in the bridge web UI results in a new web browser tab with a URL like:

http://192.168.x.x:3480/data_request?id=action&output_format=json&serviceId=urn:schemas-micasaverde-com:device:DoorLock:1&action=SetTarget&newTargetValue=0&DeviceNum=53
and the text of the web page is:
ERROR: Invalid Service

If I ignore this error, “Forget” the previous Smart Device for the lock in the Alexa app, and re “Discover devices”, it gets added back but she keeps telling me she doesn’t know how to help me unlock/open the device but says OK to turning it on and off and nothing happens with the lock.

Does anyone see what I’m doing wrong? Seems like I need to get the device to change in the Bridge web UI from a switch to a lock, but I haven’t seen any discussion in the thread about how to do that and the messages about a garage door opener didn’t help shed light on my problem.

Hi All,

I had this service up and working on two seperate windows machines. I did a firmware update to my Vera Edge and locked it up. Vera Tech support finally gave up and said my controller was ruined. They took 3 weeks to send me a new one. In the mean time I migrated many of my devices over to a Wink hub. This worked fine for simple things like some switches.

I now have a new Vera and have added several devices back on it. I have restarted the Bridge with no problems, however i cannot get any of the devices working. when I test a command string I get

This 192.168.1.35 page can?t be found

No webpage was found for the web address: http://192.168.1.35:8080/data_request?id=action&output_format=json&DeviceNum=13&serviceId=urn:upnp-org:serviceId:Dimming1&action=SetLoadLevelTarget&newLoadlevelTarget=${intensity.percent}

The IP of the Machine running the bridge is 192.168.1.35 and the device is 13

I have tried this on both machines that i previously used. Same type of issue. Any Ideas???

Thanks for any help!

I have FINALLY got the Bridge able to control the lights in Vera. I am still having a strange issue with dimming, but I can work on that later. It works fine for “On” and “Off”.

My problem now is that I can’t get Echo to discover my devices???

Anyone have this problem and have any suggestions?

thanks!