madmartian

Amazon is having a ginormous sale for Prime members on July 15. I am hoping they lower the price of the Echo for that day so I can pick up another one for the bedroom. Then I'd have the kitchen Echo controlling the upstairs lights and the bedroom echo controlling the downstairs lights, with remotes in the living room and the office. That would be perfect, though I prefer not to spend another $180 to make it happen. Amazon Prime Day

Click on the link and message him, requesting access to his program. The 0.4 emulator is written by a different programmer. In theory they should do the same thing, but I haven't tried it. The one I posted a link to is written by "armzilla". The one you have is written by "steveyo". Both programs are considered "alpha" at this stage, so there could be issues. Has anyone tried both emulators and has a preference for any reason?

I'll summarize here so you don't get lost in the mud or miss steps that aren't there or download the wrong version since folks had issues with version 0.1.1 of the JAR file. 1. Install Java runtime 8 2. Download Hue Emulator JAR file v 0.1.3 3. Download user g1of4's awesome configuration app from this thread. 3. Run the JAR file: Open up a command prompt by clicking the start button and typing cmd Copy and paste the following line at the prompt: java -jar -Djava.net.preferIPv4Stack=true FULLPATHOFJARFILE\amazon-echo-bridge-0.1.3.jar --upnp.config.address=192.168.X.X The "X.X" is the IP address of your computer, NOT the ISY You can minimize the window, but don't close it - it stays active 24/7. 4. Run g1of4's configuration tool. Remember to use the Computer IP address on the left and the ISY IP address on the right. 5. Click "Get Devices". 5. Double-click on each item you want to add. You have the option of selecting a voice command different from the name of each device. 6. When happy with your device list, ask Alexa to "discover my devices". All should work now by saying "Alexa, turn on/off XXXXXXX". 7. You want the JAR file to run automatically when you reboot your computer. Create a text file called "HueEmulator.bat" or some such and copy and paste the JAR run command from above as the only line in the batch file. 8. Put this batch file in the Startup folder. You can get to the startup folder easiest by clicking on the Start button, clicking All Programs, right-clicking on Startup, and selecting Open for All Users. Then just drag the file there or create it there in the first place. That's it! Notes: If you delete any devices, you will need to ask Alexa to forget all your devices before discovery, which can only be done through the Echo app. Go to Settings/ConnectedHome, scroll to the bottom, and click Forget. When completed, click Discover (or ask Alexa to discover). If you are adding devices but not deleting any, then you do not need to run Forget, just Discover. If g1of4's awesome configuration tool freezes when you click "Get Devices", that just means you got the address of either your ISY or your Computer wrong. Exit and rerun the app and try it again. He has not added error trapping yet. If Echo cannot find any devices after you have configured some, it is likely you have a port conflict on your computer. Of course make sure the JAR file is still running. In my case I had to uninstall CyberLink PowerDVD and reboot the computer. 1. Open another command prompt (cmd) 2. Change to the Windows\system32 folder (cd \Windows\system32) 3. Copy and paste the following, one at a time: netstat -ano | find "8080" netstat -ano | find "1900" netstat -ano | find "50000" You are only interested in conflicts listing your computer's IP address. Run Task Manager, click on the Services tab, click on the PID column to sort by PID, and look up the PID numbers listed next to the conflicts from the netstat commands that are next to your computer's IP address. You can ignore normal processes used by Windows (wcncsvc, SSDPSRV, FDResPub). You are looking for applications. Do not risk doing something bad by playing with services - once you discover the problem app, just uninstall it like you normally would and reboot. I will update this IN POST #1 as needed so it can remain the only thing you need to read to get your ISY and Echo working together via the Hue Emulator.

I'm pretty sure any "module" at this point would be a software update on the Amazon side. No need for anything else on the ISY side. It would basically add direct support similar to the Hue, which does not require additional modules. For anyone waiting for direct support who has not tried the Hue emulator, I highly recommend giving it a try. Pros: It works! It's fast! Only 4 words needed - "Alexa, turn on kitchen" Cons: 28 device limit (not a problem for me as I only use the Echo in one room, which reaches about 8 devices). You have to run an app on the PC (not a problem for me as I have my PC on 24/7 for my security system anyway). Since the only two cons don't affect me, I am pretty happy. I will use direct support when it's available, just to have one less program running in the background on my PC, but this works well. And much thanks to g1of4 for the awesome configuration app that makes setup simple.

Well, um, I was able to solve the problem. Perhaps this video will help explain it: I think the REAL problem was I had to uninstall CyberPowerDVD, which was also using the port, and even though the uninstall did not prompt me to reboot the computer it was necessary to reboot to reclaim the port. I am now in Echo/ISY nirvana. Thank you all very much.

Thanks for all the replies and research on this topic. I am trying to get the Hue bridge working. I created one device and said "Alexa, discover my devices", but Alexa could not find the device. I switched to the 1.3 version of the jar as someone else suggested, but still no discovery. I suspect it has something to do with port 1900 as I get the following netstat results: C:\Users\admin>netstat -ano | find "1900" UDP 0.0.0.0:1900 *:* 17380 UDP 0.0.0.0:1900 *:* 12752 UDP 127.0.0.1:1900 *:* 2720 UDP 192.168.0.2:1900 *:* 2720 UDP 192.168.56.1:1900 *:* 2720 UDP [::]:1900 *:* 12752 UDP [::1]:1900 *:* 2720 UDP [fe80::6d6b:f5a3:fb70:b1b3%19]:1900 *:* 2720 UDP [fe80::714c:8c8f:e077:f7f6%24]:1900 *:* 2720 I think the important one is: UDP 192.168.0.2:1900 *:* 2720 That's the machine the emulator is running on. Looking up PID 2720, I find the following: wcncsvc SSDPSRV FDResPub I don't believe these are things I can kill without consequences. How have others gotten past this problem? I'm on Windows 7 64 bit.

I'd like to see a new category in the 3rd party forums for Amazon Echo so we can get discussions going. I would love to see the day when I say "dining room, dim fifty percent" and the Amazon Echo tells the ISY to dim the dining room light 50% without me touching a controller. I know that voice control already exists, but not at the $99 price point and not with the additional features of the Echo. You can request a purchase invitation here and it's half price for Amazon Prime members: http://www.amazon.com/oc/echo --------------------------------------------------------------------------- [HUE BRIDGE EMULATION SETUP INSTRUCTIONS FOR ECHO-ISY] [i AM RE-POSTING THIS IN POST #1 SO IT'S EASY TO FIND. THE NEXT 10 PAGES OF POSTS OCCURRED BEFORE THIS] [WEMO EMULATOR INSTRUCTIONS ARE BELOW] I'll summarize here so you don't get lost in the mud or miss steps that aren't there or download the wrong version since folks had issues with version 0.1.1 of the JAR file. 1. Install Java runtime 8 2. Download Hue Emulator JAR file v 0.1.3 3. Download user g1of4's awesome configuration app from this thread. 3. Run the JAR file: Open up a command prompt by clicking the start button and typing cmd Copy and paste the following line at the prompt: java -jar -Djava.net.preferIPv4Stack=true FULLPATHOFJARFILE\amazon-echo-bridge-0.1.3.jar --upnp.config.address=192.168.X.X The "X.X" is the IP address of your computer, NOT the ISY You can minimize the window, but don't close it - it stays active 24/7. 4. Run g1of4's configuration tool. Remember to use the Computer IP address on the left and the ISY IP address on the right. Add :8080 after the address on the left, thus 192.168.X.XXX:8080 5. Click "Get Devices". 5. Double-click on each item you want to add. You have the option of selecting a voice command different from the name of each device. 6. When happy with your device list, ask Alexa to "discover my devices". All should work now by saying "Alexa, turn on/off XXXXXXX". 7. You want the JAR file to run automatically when you reboot your computer. Create a text file called "HueEmulator.bat" or some such and copy and paste the JAR run command from above as the only line in the batch file. 8. Put this batch file in the Startup folder. You can get to the startup folder easiest by clicking on the Start button, clicking All Programs, right-clicking on Startup, and selecting Open for All Users. Then just drag the file there or create it there in the first place. That's it! Notes: If you delete any devices, you will need to ask Alexa to forget all your devices before discovery, which can only be done through the Echo app. Go to Settings/ConnectedHome, scroll to the bottom, and click Forget. When completed, click Discover (or ask Alexa to discover). If you are adding devices but not deleting any, then you do not need to run Forget, just Discover. If g1of4's awesome configuration tool freezes when you click "Get Devices", that just means you got the address of either your ISY or your Computer wrong. Exit and rerun the app and try it again. He has not added error trapping yet. If Echo cannot find any devices after you have configured some, it is likely you have a port conflict on your computer. Of course make sure the JAR file is still running. In my case I had to uninstall CyberLink PowerDVD and reboot the computer. 1. Open another command prompt (cmd) 2. Change to the Windows\system32 folder (cd \Windows\system32) 3. Copy and paste the following, one at a time: netstat -ano | find "8080" netstat -ano | find "1900" netstat -ano | find "50000" You are only interested in conflicts listing your computer's IP address. Run Task Manager, click on the Services tab, click on the PID column to sort by PID, and look up the PID numbers listed next to the conflicts from the netstat commands that are next to your computer's IP address. You can ignore normal processes used by Windows (wcncsvc, SSDPSRV, FDResPub). You are looking for applications. Do not risk doing something bad by playing with services - once you discover the problem app, just uninstall it like you normally would and reboot. ------------------------------------------------------------ WeMo Emulator Instructions Install Python 2.7: Download from: https://www.python.org/downloads/release/python-2710/ Select the MSI Installer for your version of Windows (there are versions for other OS', but I only played with Windows) Run the installer Install "Requests": Download from: https://github.com/kennethreitz/requests/zipball/master Copy the folder inside to a desired location Rename the folder to PythonRequests (optional) Open a command prompt and paste: python setup.py install If that doesn't work, add your Python27 folder to your path: at the command prompt, paste: PATH=%PATH%;C:\Python27 (or wherever your python folder is) Now try the install again: python setup.py install Download fauxmo.py: Download from: https://raw.githubusercontent.com/makermusings/fauxmo/master/fauxmo.py Right-click and SaveAs... Should default to fauxmo.py Put the file in your Python27 folder Edit the file with your modules: BEFORE: FAUXMOS = [ ['office lights', rest_api_handler('http://192.168.5.4/ha-api?cmd=on&a=office','http://192.168.5.4/ha-api?cmd=off&a=office')], ['kitchen lights', rest_api_handler('http://192.168.5.4/ha-api?cmd=on&a=kitchen','http://192.168.5.4/ha-api?cmd=off&a=kitchen')], ] AFTER: FAUXMOS = [ ['office', rest_api_handler('http://user:pass@192.168.X.X/rest/nodes/XX XX XX 1/cmd/DON','http://user:pass@192.168.X.X/rest/nodes/XX XX XX 1/cmd/DOF')], ['down hall', rest_api_handler('http://user:pass@192.168.X.X/rest/nodes/XX XX XX 1/cmd/DON','http://user:pass@192.168.X.X/rest/nodes/XX XX XX 1/cmd/DOF')], ] Note: remove preceding zeros from modules. If a module is 1A 06 E3, drop the zero from the 06. Run the python file: CMD cd \Python27 (or where you put the faumo.py file) python fauxmo.py -d You should see the following: C:\Python27>python fauxmo.py -d Listening for UPnP broadcasts got local address of 192.168.X.X UPnP broadcast listener: new device registered FauxMo device 'office' ready on 192.168.X.X:PORT UPnP broadcast listener: new device registered FauxMo device 'down hall' ready on 192.168.X.X:PORT Entering main loop Now ask Alexa to discover devices. This should be successful and should result in responses in the command window: Responding to search for office Responding to search for down hall Responding to search for office Responding to search for down hall Responding to setup.xml for office Responding to setup.xml for down hall Responding to setup.xml for down hall Responding to setup.xml for office If discovery doesn't work and you see no response at all below "Entering main loop", then try rebooting and running the python script again. Once you have tested everything, add the python command to a batch file and add the batch file to your startup folder. You can read lots about how this works here: http://www.makermusings.com/2015/07/13/amazon-echo-and-home-automation/ NOTE: the code above will re-assign port numbers every time you re-run the python file (such as after re-booting). However, this should not be a big issue as the Echo asks the emulator for an update every few minutes. If this is an issue for you, there are methods for hard-coding the addresses at the above link. ------------------------------------------------------------ I will update this post as needed so it can remain the only thing you need to read to get your ISY and Echo working together via the Hue Emulator.

I'm in agreement with LeeG - it should be possible to turn off the LED completely, not just dim it really low. To me the A-D buttons are not really "scenes" but command buttons I use to set the house to a certain mode - such as shutting all lights off and turning on the hall light when I leave the house. I can ALMOST achieve what I want. As described earlier, I can get the lights to work, but not the LEDs, in non-toggle-on mode. I can get the LEDs to work (stay off) but not the hall light going on in non-toggle-off mode. I would love to get non-toggle-off mode to send commands as listed and not just turn all devices off. Since an accidental double-tap turns everything on in the non-toggle-on mode, that mode is kinda pointless. I accidental double-tap frequently since I am used to doing a double-tap for the instant on mode of the regular SwitchLinc switches. It should be easier to say "run this scene" - and do nothing else I didn't ask for - when pressing the button...

In non-toggle-off mode indeed the buttons flash and then go out as you describe. However, in that mode I can't get the scene to turn a light on. If I switch to non-toggle-on (as I had before) the scene works properly but the button stays lit. Non-toggle-on also has the weird side effect of not really being non-toggle. If you accidentally double-tap the button, all the lights in the scene go on! That doesn't happen in non-toggle-off mode. My scene is pretty simple - turns four lights off and one light on. No dimming or mood lighting. I'm not sure why non-toggle-off mode would prevent me from turning a light on, but it does.

Basicly I have some 6-button KeypadLincs and I don't want the LEDs under the A through D scene buttons lighting up - ever. Unfortunately, no matter what I do the darn things light up. I've tried setting the brightness level to 0. I've tried turning the LED off using button presses (I found instructions that work for the big ON and OFF buttons, but not the A-D buttons). There must be some way of disabling the LEDs in the scene buttons.