jackal

Got it! Thank you so much!

Hi, I am currently on ISY994i IR Pro with Gen 1 zwave module (21100). I would like to buy the latest zwave module for my device. I found this https://www.universal-devices.com/product/z-wave-module/ but it says it is only for isy994. (mine is isy994i) Just want to make sure this is the correct module? Many thanks for any information!

I am going to get lots of flak for this...but I say this considering the life span of product support, I would classify native Insteon support to be "end-of-life". I would support Michel from not migrating native support to polisy (just an insteon node server supporting existing Insteon devices). This frees up Michel's time that would have been gone to support something that is increasingly irrelevant by the day. For existing users, just continue to use the old ISY for your insteon. And start porting to Polisy and new non-insteon devices henceforth (and migrate old insteon when appropriate). That's my 5 cents. I am so ready to move on from Insteon platform and its PLM which continually needs replacement.

I missed that. Thanks!!

Recently, I have been trying to replace some of the insteon devices and realized that many insteon products are marked as "Sold Out" for a few months already. I am especially concerned as this usually is a pre-cursor to a company closing for good. Does anyone has any knowledge or inside information about that?

@blueman2 Thanks for stating the ha-bridge version that AWS Conguration 6.03 system is compatible with. Will be useful when I added new devices in future! Even better if @barrygordon would update it in future! But very happy with this solution thus far!

I am one of those using the ha-bridge with Raspberry Pi without the use of the ISY portal to connect to Echo. see original forum here Well, the SD card finally died after running flawlessly all these years. I bought a new card, installed the latest pi OS and loaded the latest release from ha-bridge. To my surprise, ha-bridge is still very well supported and updated. (v5.3.0) I followed the installation instructions and copied my device.db into the /data folder. Done! This is an update for all those that are still on this system. Tip: You might want to store a backup copy of the device.db file. It seems AWS configurator by Barry Gordon doesn't work with the latest ha-bridge version. (You can obviously load an old version of ha-bridge to run) It will save you a lot of time. Good luck!

I encounter this issue too. I overcame it by adding the word 'lights'. Instead of "Turn xxx on", becomes "Turn xxx Lights on".

Apologies that I didn't elaborate that this setup is intended for the script written in my setup. The script in my setup deliberately load the emulator for Harmony separately for easier trouble shooting and a little more system resilience.

I had too much fun and bought a harmony hub. So here's the updated complete setup documentation with the updated harmony hub inclusion: Credits: updated shell script with modifications from apnar

A small tip: Currently amazon echo only allow 2 wake keywords: "Alexa" and "Amazon". However, I discovered that "Lexa" keyword worked equally well. For everyone who wants to shorten the echo command.

Hi Barry, I thought the new UDI skill requires the portal subscription? So there is no need to run any native/local application? *confused*

+1 The 1st post in this thread uses an entirely different method from the last 20 pages of the thread. Without reading all 40 pages, one can easily be confused which is being discussed.

Here's my entire setup The Amazon Echo project Tools for this project ================= 1. Raspberry Pi 2. Network module enabled for ISY 3. PC 4. Amazon Echo Replace: 192.168.1.99 with the address of your Raspberry Pi Replace: 192.168.1.88 with the address of your ISY 1. Setting up Raspberry Pi a. Download NOOBS b. SSH into Pi using user 'pi' and password 'raspberry' c. (Optional) Install TightVNC Reference: http://www.penguintutor.com/linux/tightvnc d. (Optional) Set a static IP address for Pi sudo nano /etc/dhcpcd.conf add the following: interface eth0 static ip_address=192.168.1.99/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1 interface wlan0 static ip_address=192.168.1.98/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1 Reference: https://www.raspberrypi.org/forums/viewtopic.php?p=798866#p798866 2. Run HA Bridge a. In RPi, wget latest jar from https://github.com/bwssytems/ha-bridge/releases b. Run nohup java -jar -Dvera.address=192.168.1.88 -Dupnp.config.address=192.168.1.99 -Dserver.port=8081 -Dupnp.response.port=50001 -Dupnp.device.db=/home/pi/echobridge/data/device81.db /home/pi/echobridge/ha-bridge-1.1.0.jar > /home/pi/echobridge/logs/log81.txt 2>&1 & c. Goto 192.168.1.99:8081 to ensure emulator is running d. Modify /etc/rc.local file in Pi to start emulator(s) sudo nano /etc/rc.local Add the following: #!/bin/sh -e echo "Running the RC.local Bash script, Getting my IP address" # Print the IP address _IP=$(hostname -I) || true if [ "$_IP" ]; then printf "My IP address is %s\n" "$_IP" fi #The following is for multiple emulators on the same machine echo "Starting the Echo Bridge Emulators" nohup java -jar -Dvera.address=192.168.1.88 -Dupnp.config.address=192.168.1.99 -Dserver.port=8081 -Dupnp.response.port=50001 -Dupnp.device.db=/home/pi/echobridge/data/device81.db /home/pi/echobridge/ha-bridge-1.1.0.jar > /home/pi/echobridge/logs/log81.txt 2>&1 & nohup java -jar -Dvera.address=192.168.1.88 -Dupnp.config.address=$_IP -Dserver.port=8081 -Dupnp.response.port=50001 -Dupnp.device.db=/home/pi/echobridge/data/device81.db /home/pi/echobridge/ha-bridge-0.4.9.jar > /home/pi/echobridge/logs/log81.txt 2>&1 & nohup java -jar -Dvera.address=192.168.1.88 -Dupnp.config.address=$_IP -Dserver.port=8082 -Dupnp.response.port=50002 -Dupnp.device.db=/home/pi/echobridge/data/device82.db /home/pi/echobridge/ha-bridge-0.4.9.jar > /home/pi/echobridge/logs/log82.txt 2>&1 & nohup java -jar -Dvera.address=192.168.1.88 -Dupnp.config.address=$_IP -Dserver.port=8083 -Dupnp.response.port=50003 -Dupnp.device.db=/home/pi/echobridge/data/device83.db /home/pi/echobridge/ha-bridge-0.4.9.jar > /home/pi/echobridge/logs/log83.txt 2>&1 & nohup java -jar -Dvera.address=192.168.1.88 -Dupnp.config.address=$_IP -Dserver.port=8084 -Dupnp.response.port=50004 -Dupnp.device.db=/home/pi/echobridge/data/device84.db /home/pi/echobridge/ha-bridge-0.4.9.jar > /home/pi/echobridge/logs/log84.txt 2>&1 & echo "Starting the tightvncserver, to handle SSL protocol for my skill 'Sarah'" /etc/init.d/tightvncserver start echo "The RC.local Bash script has completed" exit 0 3. Run AWS configurator a. Download exe from http://www.the-gordons.net/homepage/DLF_AWS_Config.html b. Install c. Open notepad in adminstrator mode and edit c:\programs files(x86)\AWS_Config\AWS_config.ini accordingly d. Open AWS Configurator and add the devices and scenes to the emulator(s) 4. Configure Echo a. Goto: echo.amazon.com/#settings/connected-home to login and configure Echo b. Say "Alexa, discover my devices" to add devices to it. You may have to do a few times. That's it!

I don't want to hijack the credit. Would Barry be kind enough to do the honor? And I would post my entire noob setup as a post after that. Thanks Barry!!