madmartian

Upgraded today in hopes of fixing the "always green 10101" problem for some z-wave battery devices. At first the problem was worse - with "cannot communicate with" errors. I tried synching and Update Neighbors for individual devices, but that did not fix the problem. I removed and re-added the devices - THAT fixed the problem for two of the three devices. Sadly my smoke detector still has the green 10101 even after removing and re-adding, and then later changes to "!" with a "cannot communicate" error. Problem was happening with these battery devices: Fibaro The Button FGPB-101 v3.2 US (fixed by removing/re-adding) Fibaro Motion Sensor FGMS-001 ZW5 v3.3 US (fixed by removing/re-adding) First Alert Smoke/CO Alarm ZCOMBO (NOT fixed by removing/re-adding) Problem was NOT happening with these battery devices: GoControl Remote WA00Z-1 NodOn Remote CRC-3US-6 Dome Mouser Ecolink Flood and Freeze Sensor FLF-ZWAVE5-ECO Things I tried before removing/re-adding: Disabled automatically putting devices back to sleep Put all devices within 2 feet of the ISY Triggered the devices so they would not be sleeping Synchronized individual z-wave devices Ran "Update Neighbors" on individual devices Tried "Query" and "Write Updates" for individual devices

Yes, all that is correct. It appears my issue is one of wanting to do something that is not possible - automatically load all devices, defaulting to their name for the spoken word. After further reading it appears one-at-a-time is the only way to load the modules into the portal. Please let me know if that is not the case. I likely did this when I set it up originally and just didn't remember.

New devices were not being added with "Discover my devices" in the Amazon Echo app. I noticed the list of devices in the portal was out of sync with my ISY admin console. Renamed devices still had old names and new modules were missing. I tried "Delete All" but then could find no way to refresh the list. I then deleted the ISY entirely and started the setup all over again, adding the ISY UUID and approving the connection via the admin console. I have the green light, but still no modules in the Amazon list in the portal and discovery via the Echo app does not find anything. How do I fix this without adding each device one at a time?

I gave up on the semi-repaired PLM and purchased a new one (v2.1 for the curious). The new PLM exhibited the same issues as the semi-repaired one. It appeared that trying to use the semi-repaired PLM had resulted in some corruption that would cause the Restore Modem procedure to run through four modules and then fail (though without an error) with no links stored in the PLM. I did an ISY restore (thankfully had a recent backup) and the Restore Modem worked - everything was up and running again. However, it had created duplicate PLM links in every module instead of replacing the old ones. Thus I had to do a Restore Devices to clean everything up. Turns out some of the link tables had old controllers in them anyway, so probably a good thing to do that after several years. All is good now. I realize now that my little experiment of putting the PLM daughter board on an Access Point might have resulted in the corruption and that the semi-repaired PLM might actually be working. Not going to mess with the working system now, though. I'll put the old PLM in a drawer and play with it in 2 years when the new one fails. I can't say enough good things about the support provided by Michel of Universal Devices in multiple emails. Most companies would have taken hours to respond and thus days to solve this problem. Michel rocks! One of the many reasons the ISY is the controller of choice.

Thanks. I installed the 4 caps I found at Fry's and got the green light. So far so good. Unfortunately, any time I try to turn something on via the admin console, I get the dreaded "cannot communicate with..." error. Could this be the fifth cap that I didn't replace - the 16 volt one - or is it something else? I tried "Restore Modem (PLM)" three times and also rebooted the ISY. All caps are in correct orientation. PLM status shows "Connected" but Show PLM Links Table comes up blank after doing it's thing. Any ideas?

Rats. Oh well. I found 4 of the 5 caps I needed at Fry's. I was wondering if there are any substitutes for the 10uf 16v as they do not stock that one. They also did not have the 10uf 400v but I assume the 10uf 350v I picked up will suffice.

Thanks to this thread, I know the Access Points (2443) are identical to the 2413s without the daughterboard. So I tried to "fix" my dead 2413s by simply removing the daughter and connecting it to the Access Point. I thought this should work since the main board is identical - same part number and everything. Unfortunately when I try to restore the PLM, I get the errors "could not open config file to read" and "failed resetting the plm". I tried to view status of the PLM and ISY says it's not connected. Things I've tried: Unplug ISY, plug in PLM, plug in ISY. Made sure all pins were seated in daughter board. Made sure RJ45 cable was plugged into PLM (and ISY). Green light is on PLM. Any ideas? Do I need to reset the access point before connecting the daughter board? Or is the mainboard slightly different even though it looks identical and has the same part number?

Well that's disappointing. My current setup is a Hub for devices and a Wemo emulator with ISY for scenes and a couple older modules that the Hub doesn't support. I guess that's what I'll stick with going forward. Odd that an emulator would do something that the hardware it's emulating won't allow me to do.

Why does the ISY require a cloud service when the Insteon Hub, Wemo, and Hue do not? Why would Amazon require Universal Devices to do things differently from the others?

Some of us suspect this is caused by an Amazon-imposed 20-second timeout. If it isn't finished discovering all the devices on your emulator in 20 seconds, it fails and nothing is discovered. I contacted Echo support and they said they would note it as a feature request to be able to set the timeout in settings. It is not currently configurable. Discovery using an emulator runs much slower than with an actual Hue or WeMo bridge.

I am still waiting on the programmer to respond. I tried Python 3.4 and it fails at multiple points. I made the appropriate syntax changes in the code, which allowed it to run, but then it crashed. So Python 2.7 is a must. One thing - the guy did a good job of explaining in detail what his code is doing: http://www.makermusings.com/2015/07/13/amazon-echo-and-home-automation/ Someone could take this info and rewrite it in any language. Since the only language I know is Delphi, I won't be doing that.

I discovered that I have a 14 device limit with the WeMo emulator on Windows 10 64-bit. Discovery fails if I add a 15th. I ran it without the -d and this did not change. I asked the creator of the emulator if he has any ideas. Will let you know if that improves. I will also try it with the current version of Python (3.4).

So far the WeMo emulator is working every bit as good as the Hue emulator. So far I prefer the WeMo method because everything is in one file (though you do have to install Python). Moving the WeMo emulator from one computer to another is as easy as moving the fauxmo.py file (after installing Python and the Requests module).

I will repost in message 1 when I have the kinks worked out... 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 X XX 1/cmd/DON','http://user:pass@192.168.X.X/rest/nodes/XX X XX 1/cmd/DOF')], ['down hall', rest_api_handler('http://user:pass@192.168.X.X/rest/nodes/XX X XX 1/cmd/DON','http://user:pass@192.168.X.X/rest/nodes/XX X XX 1/cmd/DOF')], ] Note: remove preceding zeros from the middle digit. 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.

Oooh, I found a WeMo emulator: http://www.makermusings.com/2015/07/18/virtual-wemo-code-for-amazon-echo/ Will play with this over the weekend and post instructions.

Maybe. You might have to run them on different computers. It might be possible to mess with the default ports such that one would be on 8080 and the other would be on a different port on the same computer, but I don't know if anyone has tried that. I don't know where the port numbers are stored. It is possible that all three ports need to be different (8080, 1900, 50000) but 8080 for sure. Not sure, though, if you can get each echo to see different emulators, even if they are on different computers but connected to the same network. I intend to try this once I get a second echo (next time they have a sale that lasts more than 15 seconds). An upstairs echo and a downstairs echo would be ideal for me. Ideally it should be possible to create an emulator that can handle more modules. There are at least two different Hue emulators - perhaps more. It is possible someone has licked this problem already, just not with the emulator most of us are using. Someone may also be working on a WeMo or Wink emulator...

Excellent point. I have copied the instructions to post #1.

http://forum.universal-devices.com/topic/14525-amazon-echo-and-isy/?p=142127

I would first try exiting and rerunning the hue emulator. Then ask Alexa to discover again. If that doesn't fix it I would try forgetting and re-adding the devices in Echo settings on your smartphone. The only time I have had a problem is when I moved the folder I am storing everything in. I have to forget/re-add (in Echo settings) when I do that or it leaves all the offline modules and adds everything again as new modules. Otherwise I have had no issues with the emulator. The module data is stored in the "data" folder, so you should not have to do anything through the mapper just to get it working again. In fact you should be able to move it all to another computer without using the mapper just by copying the folder containing the data folder + rest program + hue emulator + batch file and adding the batch file to the startup. Just make sure you have removed it from the old folder/computer so you don't have it running twice. You will need to update the batch file to reflect the new location. Note also that it is possible for something else running on your computer to hijack one of the 3 ports the hue emulator uses, which would also cause the described symptom. In that case you would need to reboot the computer.

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.