rossarmstrong

The wiki merely states "Create a sub-account." Since there is no option listed to select "sub-account" when adding an account, am I to assume that any account other than [Main account] is automatically a sub-account? Also, since Amazon only lets you share two accounts, how are folks with more than two devices choosing to setup their system? Obviously I'm not getting a good picture on the relationship between multiple echos, amazon accounts and UDI portal accounts and the different configuration options when setting up a system. Perhaps someone can edit the wiki to help map this out.

I'm trying to configure my system to work with multiple Echo/Dot devices. The wiki talks about setting up sub-accounts in the Portal. But I can't find instructions on how to do so. It is not obvious to me when adding an account how to select it as a sub-account. Also, once I'm able to create the sub-accounts and complete the multiple Echo/Dot setup, will it result in each device accessing its own amazon alexa account for things like the shopping list? Thanks

I too would continue to use the emulator. I've just aquired the Echo Dot and plan to add it to the theater room to add voice control to my Harmony controller system. I'm a Pi noob and had everything setup (minus Harmony control) and working great with the Echo for the past 9 months or so. But now it looks like I need to start fresh and upgrade my Pi to Jessie and then reinstall everything again from there in order to add control of my Harmony. I'll patiently wait and see what happens in this thread.

Best Practice Strategy Question; As I have understood the ISY/Insteon philosophy, it is often better to control via scenes instead of devices. Does the same hold true for configuring with the ECHO? Does it make a difference between using the SKILL and CONNECTED HOME? Edit: It appears the use of PROGRAMs and THEN/ELSE could be more useful as well. I am in the process of transitioning from the use of emulators to the ISY Portal and was wondering how all the really smart folks are configuring! BTW - the emulator and their associated configuration programs are still valuable to HARMONY users wanting to control via ECHO. Thanks to everyone here for sharing, it is really all coming together now - exciting times indeed!

Benoit, Thanks for the info. I purchased and configured the new ISY portal. Sorry to ask this in the ECHO thread, but the using the Portal user/PW to configure the Mobilinc only works from outside my home network. The local URL and port use my normal console user/pw. Should I just not use the local option and direct both home and away locations to go through the secure ISY Portal? The settings for m

Was there a definitive answer regarding the ability to use both the Mobilinc Portal and ISY Portal for Echo at the same time? I don't want to lose the ability to remotely control my system with my iPad when away from home.

Its great to see users who have successfully integrated the Sonos into their system. My initial "copy, modify, paste" of others people's settings is causing some error messages in the networking module. I just need to search and read more. Although it has been a bit of an adventure getting everything setup on my RPi, it really does work quite well. It will be a worthwhile comparision using the emulator versus the skill once things mature or both sides a bit.

I errantly forgot to change the port in the emulator section of the ini file. Once I made that correction, all was well so I deleted the post since it was prior to any replies. So much for erasing evidence of my mistakes! Harmony is working great. Just need another Echo for the theater room. Hoping another $129 special pops up on slickdeals before Christmas. I guess I can work on trying to troubleshoot all the pieces needed to add Sonos to the Echo in the meantime!

Barry - that change now no longer causes the 404 issue. You are very helpful!

Thanks for your help Barry in getting my RPi up and running. I'm now adding the Harmony capability to my system. I've installed the resful-harmony-0.1.4.jar and assigned it port 8085. I use the command: nohup java -jar -Dserver/port=8085 /home/pi/echobridge/restful-harmony-0.1.4.jar 192.168.1.172 [username] [password] > /home/pi/echobridge/logs/log85.txt 2>&1 & It appears to run correctly from my rc.local because when I enter 192.168.1.75:8085/harmony/list/activities, I get a page full of data. The log85.txt file contains lots of data and I saw the following, FAILED Serverconnector@172b21d{HTTP/1.1}{0.0.0.0:8085} And when I run your config file, it reports that the harmony returns a 404 not found. I can confirm the username/pw is correct in the ini file. Reading back through this thread, am I supposed to run another instance of the ha-bridge with the following harmony info included (from your post dated 11 Nov): nohup java -jar (space) -Dvera.address=<IP address of ISY994> (space) -Dupnp.config.address=<IP address of Raspberry Pi> (space) -Dserver.port=808x (space) -Dupnp.response.port=5000x (space) -Dupnp.device.db=/home/pi/echobridge/data/device84.db (space) -Dharmony.address=<IP address of your Harmony Hub/remote> (space) -Dharmony.user=<your harmony account userid> (space) -Dharmony.pwd=<your Harmony account password> (space) /home/pi/echobridge/ha-bridge-1.0.7.jar > /home/pi/echobridge/logs/log84.txt 2>&1 & Your config app works great with my 4 emulators running on the RPi when I remark out the Harmony section. Any thoughts? I know you don't have a Harmony and your troubleshooting may be limited.

@barrygordon I've finally been able to overcome my rc.local not executing the commands. It was a round about fix for me so it may not work for others. I simply put the commands from the sample rc.local file into a new script file I created called startup.sh and then called that single file in the rc.local. I still think my problem relates to having intially configured my RPi and following the "how to post" here while logged in as the user pi and not root. Anyway after getting things up and running successfully with your program, I went to add Harmony capability and noticed BWS released a new ha-bridge1.2.2. After updating that file, your AWS_config popped up a "This version of the program will not run with this version of the HA Bridge emulator." (I was running your version 5.0.50 at the time) So I changed back to v1.2.1 which was working just fine. But your program still pops up the same warning. Today I updated to your 5.0.57 and still get the same warning. Any suggestions? Overall, I've been really impressed with how easy it was for me, a non-programming noob, to use your program and how well it works. Many thanks for sharing and supporting!

I have done all my setup of my RPi as the user pi. I never logged in as root. The echobridge folder and subfolder/files all were set with pi as the owner. I logged in as root and set ownership to root, manually ran the full command and the HA-bridge was running. There was also a log81.txt file that was created and had data. However, nothing in the data folder. I rebooted and hoped that all four listed in the rc.local file were start - no luck. None started. I will email barrygordon my rc.local file to give it a QC check, but perhaps my problems are related to the fact I did all the setup and while remotely logged in as the normal user pi. Although I remember several of the steps I followed included commands with sudo. I think we're getting close to solving this!!

Thanks for the replies - but still not working. I do use TightVNC and WinSCP to remotely manage my headless RPi. The directories home/pi/echobridge/data and home/pi/echobridge/logs do exist. I had previously created an empty file of device81.db and log81.txt in case they needed to exist in order for the startup command to work properly. But the emulators fail to start whether those files exist or not. I did a fresh reboot (still using my edited rc.local) and ran the sudo ps -ef | grep java and got the following results: pi 1537 1526 0 13:57 pts/0 00:00:00 grep --color=auto java So it appears none of the emulators actually started from the rc.local script. Is using this command: nohup java -jar -Dvera.address=192.168.1.45 -Dupnp.config.address=192.168.1.75 -Dserver.port=8081 -Dupnp.response.port=50001 -Dupnp.device.db=/home/pi/echobridge/data/device81.db /home/pi/echobridge/ha-bridge-1.2.1.jar > /home/pi/echobridge/logs/log81.txt 2>&1 & supposed to create the device81.db and log81.txt files if they don't yet exist or update/replace them if they do? If so, that is my problem as they are never created when I enter that whole command and the HA-bridge never starts. If not, is there any guidance or copies that I need to install? (I would think not since the early posts never mentioned the need to do so). It still appears to me that the section of the command -Dupnp.device.db=/home/pi/echobridge/data/device81.db and > /home/pi/echobridge/logs/log81.txt 2>&1 & are causing my issue. Again, the stripped down command nohup java -jar -Dvera.address=192.168.1.45 -Dupnp.config.address=192.168.1.75 -Dserver.port=8081 -Dupnp.response.port=50001 /home/pi/echobridge/ha-bridge-1.2.1.jar does at least result in the emulator starting. I'm at a loss why the full command listed in the how-to posts is not working for me. Thanks again for your assistance.

I initially used the command line in order to ensure the jar ran correctly. When I had success with the shortened command, I went ahead and modified my rc.local, just as barrygordon described to run 4 emulators. But when I rebooted, no emulators started. So I also think my issue is with the device and log files/directories. I can't find info describing the syntax of -dupnp to try and figure it out.

Need a bit of help trying to setup the BWS emulator on my new RPi2 (I'm a noob at RPi but do try to learn by searching and reading) I have been trying to closely follow barrygordon's and jackal's excellent posts on getting things configured, but I am not getting the emulators to successfully start. I have copied the latest ha-bridge.1.2.1.jar into home/pi/echobridge When I enter the suggested run command (modified with my ISY and RPi IP addresses) nohup java -jar -Dvera.address=192.168.1.45 -Dupnp.config.address=192.168.1.75 -Dserver.port=8081 -Dupnp.response.port=50001 -Dupnp.device.db=/home/pi/echobridge/data/device81.db /home/pi/echobridge/ha-bridge-1.2.1.jar > /home/pi/echobridge/logs/log81.txt 2>&1 & I get no response when I try going to 192.168.1.75:8081 However, if I enter only nohup java -jar -Dvera.address=192.168.1.45 -Dupnp.config.address=192.168.1.75 -Dserver.port=8081 -Dupnp.response.port=50001 /home/pi/echobridge/ha-bridge-1.2.1.jar I get the following in terminal: nohup: iognoring input and appending output to 'nohup.out' But I CAN successfully access the ha-bridge when I goto 192.168.1.75:8081 On my RPi, I initially only created the home/pi/echobridge folder and put the jar file in it. I thought perhaps the command references to the data/device81.db and the logs/log81.txt needed to exist as well so I tried creating them as empty files. But that had no effect. Obviously I don't have something configured or typed correctly in the suggested full command, but I haven't been able to figure it out. Any help is greatly appreciated.

Barry, Google searches have been helpful getting my Pi up and running, but my Interfaces file (running the latest Raspian installed via NOOBS) doesn't closely match examples found with the search. My Interface file reads: # Please note that this file is written to be used with dhcpcd. # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'. auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet manual auto wlan0 allow-hotplug wlan0 iface wlan0 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf auto wlan1 allow-hotplug wlan1 iface wlan1 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf I could not find a file named man dhcpcd.conf, but the dhcpcd.conf file reads: # A sample configuration for dhcpcd. # See dhcpcd.conf(5) for details. # Allow users of this group to interact with dhcpcd via the control socket. #controlgroup wheel # Inform the DHCP server of our hostname for DDNS. hostname # Use the hardware address of the interface for the Client ID. clientid # or # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361. #duid # Persist interface configuration when dhcpcd exits. persistent # Rapid commit support. # Safe to enable by default because it requires the equivalent option set # on the server to actually work. option rapid_commit # A list of options to request from the DHCP server. option domain_name_servers, domain_name, domain_search, host_name option classless_static_routes # Most distributions have NTP support. option ntp_servers # Respect the network MTU. # Some interface drivers reset when changing the MTU so disabled by default. #option interface_mtu # A ServerID is required by RFC2131. require dhcp_server_identifier # Generate Stable Private IPv6 Addresses instead of hardware based ones slaac private # A hook script is provided to lookup the hostname if not set by the DHCP # server, but it should not be run by default. nohook lookup-hostname I don't want to hijack this thread and turn it into a Pi support topic. I did use my router to reserve an IP address based on the Pi's MAC address and that appears to be working fine. On to setting up everything else. Barry, thank you for your development work, how to guide and support here in the forum. I've always been impressed with the helpful folks here in the ISY community!

I'm new to Pi and have just set up the Pi2. But the method for setting a static IP must be different because the online instructions don't match what is in the new files. Anyone set the IP on the newer version yet? Itching to move the emulator off of my PC and get the combined ISY - Harmony action up and running!

I just found that there is a Windows option to select "disable display scaling on high dpi settings" in the shortcut properties. Right click the console shortcut and select PROPERTIES Select the COMPATABILITY tab In the Settings section, select the box next to "Disable display scaling on high dpi settings." These instructions are from my Windows 10 desktop, earlier versions may be slightly different. After making this change, the admin console now opens in a perfectly readable scale. Combined with the recent console update that remembers the previous screen location, using the console on a multi-monitor setup is now pain free!

Wow, this setup is working sweet! Thanks to everyone for the tools and the instructions to make this happen so easily! Question though, I would like to host these files on my aging Windows HomeServer 2011 machine. While the Javascript and the mapper run properly, the Echo can't reach it. Obviously the higher security of the server OS is blocking the necessary access that is open on my Win8 machine. But I've been unable to figure out what it is I need to open on the server to allow communications with the Echo. Only port 1900 shows activity with some of the standard windows services. And creating in/out firewall rules allowing connections on ports 8080, 1900 and 50000 did not fix it. Any help is greatly appreciated. I will ECHO (pun intented) previous postings that you need to add this voice capability to your home setup now. It is easy and surprisingly cheap. I can only image what the ISY integration capabilities will be 6 months from now.

Thanks for that. I was afraid other ways might overwhelm the traffic.

Thanks for the replies. Given that the links are retained and that the bulb should turn on (assuming that was its last state) when the lamp is turned back on, then I should be able to create a program like: If Status 'Insteon bulb 1' is ON Then Set Scene 'Family Room Insteon Bulbs' on Now to figure out how to turn them off. Could I simply use a If Status 'Insteon bulb 1' is not On Then Set Scene 'Family Room Insteon Bulbs' Off Or is failure to respond (because bulb is depowered) not interpreted as either true or false by the ISY? Perhaps I just need to learn about setting varialbles because I think that will be the key to figuring out how to determine when the lamp gets turned off and can't respond. Thanks folks.

A few questions for those who have used any of these conncected bulbs (insteon or zwave) 1 - Are all links retained when all power is removed from the bulb? (I do see that the Insteon bulb can be software configured to NOT enter linking mode when power is reapplied) 2 - Is its last power state retained when all power is removed from the bulb? I realize these bulbs are designed to have constant power so they can be controlled via the normal Insteon control methods. But I still have a few standard lamps that really lend themselves to simply using the standard twist knob at the base of the bulb. The idea I have is to try and monitor the status of a bulb that is powered/depowered via the normal lamp switch and use that to trigger the on/off of other bulbs that are installed in lamps that are left in the power on position. Knowing the answers to questions 1 and 2 above will help me determine if this configuration might be possible. Thanks in advance.

Sorry, the device type was only in the topic subject. It is the Insteon 2470D Stand-alone Dimmer. Yes. I know this is non-communicationing. I would like to use the pair in my stash to simply turn on/off a single light in a 3 way circuit. I have no desire to send it Insteon control messages or have it in a scene. I was just wondering if there was any way I could replace the existing flip switches with these. My very basic understanding of the 3 way circuit leads me to believe that I would still need to use the traveler wire. But not knowing how the mechanical switches are built, I don't know how how to replicate its actions with the 2 stand-alone switches. I was thinking perhaps the load switch of dimmer #1 might use the traveler (red) wire to connect to the line of dimmer #2. But then dimmer #2 is essentially unpowered when dimmer #1 is off. Which might not be a big deal since it doesn't need to send/receive communications. But then how can the two work togther like a normal 3 way circuit? This is really just an academic issue now. This light circuit controls an entry light and the two switches are right across from each (almost within arms reach). It was poor design to have this light on a 3 way circuit to begin with. So unless the switch location I no longer want to use is the load (knowing my luck. . .) I'm just going to break the 3 way circuit and put a regular switchlinc in the other location to control something else. I'm still interested in knowing the official answer from someone more learned in home wiring than me. Thanks.

These are the old non-communicating switchlinc dimmers. I've had them in my stash and finally found a possible use for them in a 3 way light circuit that I don't need any additional control over. Question is, can it be done? My intial guess is that it is not possible because they are each designed to control the load. But my very rudimentary understanding of household wiring and multi-circuits leads me to ask the experts. Thanks for you help.

Thanks everyone! I successfully created single themes and then mapped the similar KPL buttons as controllers to that scene. Once I understood that I needed to copy the scene attributes to each of those controllers, I was finally able to achieve the "status syncing" of the scene buttons on the different KPLs. Spent the weekend cleaning up all the scenes originally created with Homelinc many years ago. Much easier and nicer on the ISY. (Although I did find the need to upgrade to the PRO option so I could queue up writing all the changes - didn't realize it was now an option when I moved from the 99 to the 994).