btreinders

Now we just need a SmartThings emulator!

I can only get 9 devices to discover. So I now have 37 total. 28 Hue and 9 WeMo. Weird.

I get 28 and then it stops discovering. Maybe that is because some of my devices only have an off or on command? 44 total commands?

Other than the electric bill, no. If you already have a PC running 24/7 then no other reason at all.

I have found that for the garage door Alexa will recognize "open garage door" or open any device as on but "close garage door" results in her adding close garage door to my to do list. Close any other device that I have works as off.

Does this mean Universal Devices will have an interface soon?

Has anyone run into a 28 device limit with the emulator? Once I add 29 and run Add new devices on the Echo app, all devices show offline.

It is great for lights. Very fast, was surprised how fast even after reading all the comments. Still need full ISY integration so we can say things like "arm the house", "water the garden", "play music outside", "close the garage door", etc. (Open Garage door does work which is strange) Would be nice to be able to change the response back from just "OK" as well. Also, don't forget Tasker on Android. Integrated with Google voice via Autovoice it can do anything you need it to via voice commands to the ISY. Tasker is something everyone with an ISY should have. Siri will get there I guess, but Android has had this for a few years now.

Has anyone had trouble adding a device that has the same ISY on or off command in the HUE emulator? Once I add my irrigation sprinklers since each one has the same off command Echo stops seeing all my devices. Also happens if I try to make two voice commands do the same thing. For instance, "Alexa, turn off the outside music" or "Alexa, turn off the music outside" are both tied to the same program in the ISY so it fails when both devices are added. They all say offline until I delete the offending device. I can work around it by creating another program just not very convenient. Another quirk I have found is using Echo to open and close the garage door. I create a device called garage door and use one program for opening it on the on line and one program for closing it on the off line. If I ask Alexa to open the garage door she has no issue with it. If I say close the garage door she just adds close the garage door to my to do list. I have to say turn the garage door off to close it. Strange because she will open and close lights with no issues vice on and off.

Thanks! I figured it out. I had to add a device. Once I did that, Echo discovers them and everything works! Thanks! The reason I bought the Echo in the first place!

Please help with getting the emulator up and running. I have the .jar file running in windows but the Echo does not find it as a home automation device. Am I doing this correctly? Thanks! Also, assuming the Echo should see it, how do I set it up to control the ISY? I do many things with the ISY through the REST interface but I do not understand how to get the emulator to post HTTP commands.

larryllix, That was it! Thank you so much! I had no idea that it worked that way. I don't like using a timer since it does delay being able to turn something on and off quickly but I guess for now I will live with it. Also a big thanks to oberkc! I have a much better understanding and will be using the control option in the future instead of status.

Sorry, yes I have a program that is running the "then" section even though the variable in the "if" is not 0 at the same time as it receives the X10 command. In the program below I can see the program icon going green even when the timer is set to 1. This is why the program is looping infinitely. If X10 'A15/Off (11)' is Received Or X10 'A/All Units Off (13)' is Received Or X10 'A/All Lights Off (1)' is Received And ( $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER is 0 ) Then Set Scene 'Scenes / KeypadLinc / KeypadLinc LEDs / KeypadLinc LED - D' Off Resource 'Cabinet Lights Off' $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER = 1 Run Program 'Keypadlinc_D_Cabinet_Lights_Off_Timer_Reset' (Then Path) Else - No Actions - (To add one, press 'Action')

I only have one insteon keypad and about 12-14 X10 devices left in the system. Mostly outlets and lamp modules. I do have about 15 insteon devices as well. The PC resource is X10 only. I only eliminated the X10 address from the keypad based on the statements in the keypad manual about communication issues. That statement is not in other insteon manuals. I also removed all X10 addresses from all other insteon devices as well just in case. Maybe I should just go back to having X10 addresses in all my insteon devices? That seemed to work for the most part but I still would see a mis-match between the state of the LED and the state of the light intermittently. So I read the manual and thought maybe the X10 address was the issue. Do you know why a program can execute when one of the conditions is false? I would really like to understand that.

oberkc, Yes taking it out resolves the issue. I do have to have it issue another command or else the widget will not work to turn the light on and off, it would only provide status. I guess what I do not understand is how the program can execute when one of the conditions is not true. Makes no sense to me. Also, yes the backup is necessary if the ISY cannot reach the X10 device. I do have a phase coupler and X10 signal amplifier and have done extensive testing to determine that sometimes backup is just necessary. Thanks!

I may have to sleep on this. I switched to integer variables with the same results. Not sure that is what you were saying to do but I tried it anyway. Thanks for all your time! I may have more questions and appreciate the answers!

oberkc, Thank you for the quick response! I did try your programs and they do work just fine. I did not know about control as a condition. I will have to read up on that one. Once I add the network resource is where things go bad. The resource sends out an http command to a program running on a PC. That program in turn sends out an X10 A15 on or off command. I guess that's where the looping happens. ISY tells that program to turn on A15 and it receives that command back and acts on it. I use that program called Active Home Vista to provide usable widgets on my Android phone since Mobilinc does not have a widget that can change it's image based on states. I also use it as a backup in case the ISY signal does not make it to the switch for some reason. Some switches and units do not always receive the signals from the ISY reliably and vice versa but that's another issue altogether. That's why I chose the ISY and Insteon to migrate with like a lot of other people have. I still have many X10 devices though. I tried adding timers to your programs using a state variable as a condition to enter the receive programs. What I see is the receive programs turn solid green (running) even though the state variable condition is not true yet. Is that possible? I even set the timer for well past when the program on the PC sends out the signal. Here are the three programs now along with one of the timers at the bottom. If Control 'KP Button - D - Cabinet Light' is switched On And Control 'KP Button - D - Cabinet Light' is not switched Off Then Send X10 'A15/On (3)' Else Send X10 'A15/Off (11)' If X10 'A15/Off (11)' is Received Or X10 'A/All Units Off (13)' is Received Or X10 'A/All Lights Off (1)' is Received And ( $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER is 0 ) Then Set Scene 'Scenes / KeypadLinc / KeypadLinc LEDs / KeypadLinc LED - D' Off Resource 'Cabinet Lights Off' $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER = 1 Run Program 'Keypadlinc_D_Cabinet_Lights_Off_Timer_Reset' (Then Path) Else - No Actions - (To add one, press 'Action') If X10 'A15/On (3)' is Received Or X10 'A/All Lights On (5)' is Received And ( $KEYPADLINC_D_CABINET_LIGHTS_ON_TIMER is 0 ) Then Set Scene 'Scenes / KeypadLinc / KeypadLinc LEDs / KeypadLinc LED - D' On Resource 'Cabinet Lights On' $KEYPADLINC_D_CABINET_LIGHTS_ON_TIMER = 1 Run Program 'Keypadlinc_D_Cabinet_Lights_On_Timer_Reset' (Then Path) Else - No Actions - (To add one, press 'Action') If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 10 seconds $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER = 0 Else - No Actions - (To add one, press 'Action')

I was wondering if anyone has a solution to my issue. I have an 8-button keypadlinc and two of the buttons run X10 lights. I would like to be able to make sure the LED stays in-sync with the state of the light. I created a program to turn the light on and off using X10 commands sent from the ISY when the button is pressed. I do not have the button itself responding to received X10 commands because in the manual it states that can create unwanted reception issues. From the manual: "If you are no longer going to utilize an X10 address associated with KeypadLinc, it is very important that you remove its X10 address. Otherwise, KeypadLinc will still listen for X10 commands (somewhat hindering INSTEON reception) and may respond to spurious X10 “noise” which is unavoidable. Furthermore, KeypadLinc will transmit an X10 address and command every time the button is tapped." So, based on that info from the manual I removed the X10 address from the buttons and just use programs based on the insteon signal to send out an X10 signal instead. One issue with this comes when another X10 controller sends out a command and the LED on the Keypadlinc does not turn on indicating the status of the light. So I created a program that would look for an X10 on command received and turn on the LED. I also created one to look for an X10 off command and turn off the LED. Now, when I send an off and then on or vice versa, the ISY receives the signal it sent out and then loops infinitely. I have tried timers, program status, everything I can think of to stop the looping with no success. It seems that once the ISY receives an X10 signal there is no way to stop it from acting on it. Thanks so much in advance for any help. Here are the programs: Program that looks for the button to be pressed. <Cabinet Lights - D> If Status 'KP Button - D - Cabinet Light' is 100% And Status 'KP Button - D - Cabinet Light' is not Off Then Run Program 'Cabinet Lights - A15' (Then Path) Else Run Program 'Cabinet Lights - A15' (Else Path) Program that actually turns the light on or off. The resource is to keep the X10 controller in sync for widget use. It also sends out an X10 A15 on or off signal. <Cabinet Lights - A15> If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send X10 'A15/On (3)' Wait 1 second Resource 'Cabinet Lights On' Else Send X10 'A15/Off (11)' Wait 1 second Resource 'Cabinet Lights Off' Program that receives the X10 off signal: <Cabinet Lights Off X10 Signal Received> If X10 'A15/Off (11)' is Received Or X10 'A/All Units Off (13)' is Received Or X10 'A/All Lights Off (1)' is Received And ( Status 'KP Button - D - Cabinet Light' is 100% And Program 'Cabinet Lights On X10 Signal Received' is False And $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER is 0 ) Then Stop program 'Cabinet Lights On X10 Signal Received' Set Scene 'Scenes / KeypadLinc / KeypadLinc LEDs / KeypadLinc LED - D' Off $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER = 1 Else - No Actions - (To add one, press 'Action') Program that receives the X10 On signal. <Cabinet Lights On X10 Signal Received> If X10 'A15/On (3)' is Received Or X10 'A/All Lights On (5)' is Received And ( Status 'KP Button - D - Cabinet Light' is Off And $KEYPADLINC_D_CABINET_LIGHTS_ON_TIMER is 0 And Program 'Cabinet Lights Off X10 Signal Received' is False ) Then Set Scene 'Scenes / KeypadLinc / KeypadLinc LEDs / KeypadLinc LED - D' On $KEYPADLINC_D_CABINET_LIGHTS_ON_TIMER = 1 Stop program 'Cabinet Lights Off X10 Signal Received' Else - No Actions - (To add one, press 'Action') Program that resets the timer for off. <Keypadlinc_D_Cabinet_Lights_Off_Timer_Reset> If $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER is 1 Then Wait 4 seconds $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER = 0 Else - No Actions - (To add one, press 'Action') Program that resets the timer for on. <Keypadlinc_D_Cabinet_Lights_On_Timer_Reset> If $KEYPADLINC_D_CABINET_LIGHTS_ON_TIMER is 1 Then Wait 4 seconds $KEYPADLINC_D_CABINET_LIGHTS_ON_TIMER = 0 Else - No Actions - (To add one, press 'Action')