CoolToys

I have a program set (I thought) to turn on the porch lights and yard lights anytime the front porch light is off and the door is opened. Ideally this would only happen at night so I set sunset to sunrise the next day. It comes on all the time, so I added +5 and -5 The "Front Door" is an elk zone. (BTW, new ELK module once I got it figured out, waaaaaay better) Same issue. As soon as door open, 24x7 lights come on? Any ideas?

@Techman - Found it, Thanks! I was looking for ISY or eisy...

Trying to figure out a wife approved way to use the mini remote. Ideally every time I press the A Down button the "Bedtime" or "All Off" program should run. I tried to use both On or off so no matter what it was before the press the other answer would run the program. Didn't work, not sure what a Mini keypad sends. I have two, one is an 8 Scene and it works great for turning scenes on and off with a single press. The other is a 4 scene. Same model numbers. They both appear in the admin console as 2432-222 v.39. I tried options to change the four scene to an 8 scene it didn't help. Only the bottom four buttons were read by the admin console when I did that. I can see the status of all 8 buttons, but if a button is "off" and I press it, it changes to "on". When only the "off" option was in the program it was better but took two presses sometimes. Trying to make it more consistent like the scene controller mini I use downstairs. Is there a way to use a single keypress to start a program? I have tried "Toggle" and "non-toggle" 8 scene options. Neither work. The "Master Bed Cabinets" is a wall switch, and those lights come on just after sunset. That works every time. The Kelly Bed Keypad is a Insteon 5 Button in a plug in adapter. It has the same issue as the mini keypad. If it is off, pressing "off" does nothing. I added the keypad to an "all lights" scene as a controller so it would give her the temporary illusion of working. Everything turns off, but not as the "All Off" program does. I understand that the Keypad status changes to "on" when the scene is on, so that is why it works as a scene. Does the eisy ignore commands that equal the current state? The MB Mini keypad I need to press on, wait about four seconds and then off each night. Adding it to the scene didn't really help like it did for the 5 button. The 8 button toggle downstairs controls 8 different scenes perfectly which makes it all the more confusing. Is there a way for the eisy to "see" a button press and react regardless of the current status of that button? i.e. pressing "off" when status is already "off" still sends "off" so the eisy can run the program or am I stuck with scenes in toggle mode? The 4 scene only appears to work as a four scene keypad, I tried to update to 8 scene toggle like the other one and the bottom two buttons become toggles the top two don't appear to do anything. No activity in the event viewer so I changed back to four scene. Four on and four off buttons. I also tried adding it to a "scene" that included just one of the lights in the program. When I pressed off, that light turned off but the program didn't run. The program makes it look like someone walking the house turning off all the lights, like Lutron does after you use learning mode to teach it your patterns.

I thought it would be that easy, but while in the "Then" area of the admin console I haven't found "ISY Query" on the eisy. Under "action" Then "your devices" it is only individual devices now, the "ISY" isn't there.

One other question, the "Daily Query" program didn't migrate to eisy. I didn't see anything about that in the forum or wiki. If anyone knows why, thanks, if I find it I will post here.

After migrating to eisy from the ISY, I am down to two issues. One is my gate bell/controller. I use an I/O linc 2450 as both a contact closure for my gate relay. I can press a button and the relay opens. It is also used for a door bell trigger. When someone presses the door bell button on the keypad it closes the input contact and triggers a program to make the siren make a loud chime. The eisy could not communicate with the I/O linc so I did as I did with the MS II sensors, and deleted it, then tried to re link it. When trying to re-link the first try couldn't find the device, second and third found it just fine but "couldn't determine insteon engine". so for now no visitors I guess. Any one else find a way for eisy to work with a 2450.

Ok so things are really looking up. My system has been stable for many many years so I don't mess with this and forget more than I know for sure. ISY to eisy migration almost completed with ELK module. I am still working on the mini remotes. 1. Elk module. I didn't understand the variables so I tried "elk all" for name and the number of the user and it's pin I programmed in ELK RP that the old elk module used to connect non secure on port 2101. I have two areas but the second one I do odd things with in elk so I changed to one area, restarted the elk Node Server with these three adjustments and within seconds everything populated and I just needed to correct the If lines in my programs where the old elk conditions were remarked out. 2. Motion Sensors II aka MS II or MSII - One at a time, I put them in multi link mode, removed them from the system and quickly re-added before they timed out and all are working well. I hope this helps someone!

9/5 Evening Update, After I left the system for several hours, the Elk icon changed and the information populated. Not in the way I expected from the help files, but using standard ELK terminology that I understood and could use. One of the MSII's started working, no idea why. I came home and the kitchen scene worked all by itself. I tested the other three MSII's and the "activity block" is still blank. Working through it. 9/6 Morning update - A second MSII is now "sending" or being "received" by the eisy. One shows the temperature and battery status as well as "Status" in the Activity event, and on the "motion" page it shows blank. The second one only shows "Status". and "off" on the motion page. For the two that the eisy is not receiving, one shows the temperature and battery status the other is all blank. Factory reset and restore did not work. Next is to remove and start over as a new device I think.

Thanks for the updates and yes I did understand that I was going down the Poly rabbit hole. There can be a better way but that isn't going to change today or even this year. I had planned to upgrade as soon as the eisy came out but had the same frustrations so I delayed it as long as I could. The failure of Insteon and rebirth with i3 was the beginning of the end of the ISY and since the ISY support will end at some point I decided now was the time. After loading the Elk NS, and following the directions in the help section a new light bulb icon appeared in devices with two sub-devices labeled ELK Controller. I have no idea what these do and this doesn't match the help files so I am still reading everything I can find. I found on the Programs>details tab from another post that all of the "Out of Memory" programs had an elk status or zone in the If statement. I had to remove the Elk <unknown> lines and then disabled the programs so I wouldn't lose them but could start eliminating the errors. I should have mentioned that as a workaround for anyone else so they don't just delete all their work. I bet there is a way to comment out programs, I just don't know how. You are correct, The MSII's were used to set "state variables" so that lights wouldn't turn off if I sat still for 5 minutes, not as part of the ELK. I agree these are two separate issues. Using MSII's like this was the most reliable way I found to do it and then I found I could create cool scenes based on the order. Someone leaving the guest room, turned on one path to the kitchen, someone leaving the master a different set based on which MSII was triggered first before hitting the one on the stairs. You get very used to the house doing things for you and now two days of zilch. The MS II's are discovered, and I can read everything except the motion status. Thanks for the link to the MS 6. I realize it is time to upgrade away from Insteon, I was just hoping to not have to toss 10 years of systems building to upgrade my ISY to an eisy.

I finally got around to migrating from the ISY I have used for at least 12 years to the new eisy. Just about everything that could happen did. I am not writing this to beat up UDI, but I learned if you need to write a manual, there is a better way to do it..... I have been doing a lot of reading as a 10 plus year ISY/Insteon/Elk user for what is called an "eisy upgrade". After failing miserably, I wiped the eisy and started over following the wiki step by step. Sorry it is no where near complete and at the same time has way too much information that isn't needed. As of now the eisy can see every device. I can use the buttons on the admin console to turn them on or off. Most of my programs use the status of the alarm as an energy saving feature since geofencing eats my phone battery. None of the ELK information migrates. There are two main issues. First, none of the motion sensors are being read (seen) by the eisy. I can query and fill in everything but activity and status boxes. The four sensors do a lot of the heavy lifting after the elk to trigger programs and save energy. Any ideas? I can't find anything on Insteon Motion II in the forums or wiki other than press the button to activate or program. Second the Elk module. I am still working on it, out of time today. Everything below is what I am finding out, but not much progress. I found all of this digging around the forum after several hours of frustration and I still can't get the eisy to do anything but act as a button. Use caution upgrading packages, you also need to delete and download a new Start.jlnp so you get a new admin console or they are not compatible. You don't find this out until after you upgrade and can't access the admin console. None of my programs worked, and none of the motion sensors are being read by the eisy. Most programs said "not loaded" and "out of memory". These errors are misleading. After digging around the forum I found a note that said check the programs, there is a device/variable missing. Sure enough, all non loaded programs were related to the status of my ELK security system. The module did not transfer with the upgrade from backup. Every line in every program with an elk module was an error. Which there is no documentation on the Wiki for and you can not "purchase modules" in the eisy as the wiki says to do. I assumed from the reading that there is something in the polyglot. Finally got it loaded and started to configure. Another hour of reading and it still isn't set up or working.

There is a variable with options of "True" or "False" in the admin console when setting up thermostats. Both thermostats defaulted to false. I have no idea what this does and entering it verbatim into the Wiki only shows me the thermostat modes which I understand. Is there a new feature? Is this part of the electricity module for flex alert? The admin console says to manage the electricity module in the "dashboard" which I do not like as it is over simplified and not easy to use on a mac. Thank you.

Well it was nothing, at least so far. IN 5.0.14(beta) the siren was found but has four functions that appear to be tied to the alarm only. Ironically I still can't get the elk to communicate with the ISY. With 4.6.1 and older, I had it set up so when the relay closed the siren sounded a chime. I have found the chime feature, but I can't trigger it with a scene or a program that I have figured out. If I do, I'll post it.

I upgraded to 4.7.3 and the siren is not supported. A little afraid to update to a beta but since the siren is my only door bell, here goes nothing....

Anyone know why these aren't supported? I upgraded to 4.7.3 while troubleshooting a link to my ELK and suddenly my door bell stopped working. I use a relay from a button on the keypad at the gate to close the remote relay and trigger the buzzer. Other than being a bit loud it worked fine for over a year, and with the new update it shows as "unsupported device" Why would UDI drop a device that had been working?

I got bored, did a factory reset, it took about 30 minutes and it appeared in the IP scanner. I had to reboot my mac to get the ISY launcher to find it (cached data?), but the ISY came back up. I reloaded my latest back up only losing one new program, which is my fault for not backing up after I added it.

At 2 am a closet light came on that is controlled by a motion sensor. No one was in there, so I figured the battery must be low and simply closed the door. This morning I tried to connect my ISY to my ELK M1 for the first time (second house doing this), and the ISY only has the Power light on. I rebooted it and the PLM, and it appears to check in normally and after the boot sequence back to power light only, IP scanner doesn't see it, network switch indicates a 10/100 device is connected, no activity and no address assigned or being requested. I did power off and re-insert the SD card, no idea why, I just did. No change. I have put in a support ticket and if anyone has Ideas in the interim, thank you for your help.

I too added a Siren to my network, and used a horrible workaround to get it to work. The contractor didn't move my doorbell when we added on to the house. Ring, and Skybell are great but don't work with gate intercom. Since I could not hear the doorbell in the new section of the house, I bought a 2868-222 Siren and 2450 I/O link (which came up "refurbished" on my 994 Console?). The horrible workaround is that I added the Insteon Hub back to the network with the sole job of activating the chime when the I/O link "sensed" the closure of the doorbell circuit on the gate intercom. Whoever wrote the marketing lit for the Siren saying it also has a "more pleasing chime" must like the door sensor sound at 7-11. It is horrible sounding and way too loud, but I don't miss visitors at the gate. Looking forward to 5.x beta so I can take the hub back out before my wife adds alexa to it. I know, but I am too cheap to add alexa to the 994i

Might have figureed it out. 1. link to a switch. 2. "Add links" from switch 3. add device and "remove links" It didn't accept the name, it added it as an address.

Re-wrote to the "Garage" 2845-222 and it appears to be working again. Still can't re-write "front door" but I linked a switch to it and it works fine as a controller, just can't connect it to ISY.

There are dual mode controllers on both phases. The system was working just fine before a recent power outage. Now I can manually turn on a program and it works fine. i.e. "night" whch used to come on at sunset +- 21 minutes random after sunset. It did not come on automatically last night or tonight. From the admin console I can control any scene or switch and yet none of the programs are working as they did. Very confusing. I have powered down, re-booted. Hub works fine when I plug it in and use iPhone app to control it. PLM status is "connected".

Thu 03/17/2016 08:57:52 PM : [2B 0 50 ] Added to list of devices to link to ISY Thu 03/17/2016 08:57:52 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00 Thu 03/17/2016 08:57:52 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00) Thu 03/17/2016 08:58:01 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00 Thu 03/17/2016 08:58:01 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00) Thu 03/17/2016 08:58:10 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00 Thu 03/17/2016 08:58:10 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00) Thu 03/17/2016 08:58:14 PM : [2B 0 50 0 ] Failed to add device, reason 3 Thu 03/17/2016 08:58:14 PM : [All ] Writing 0 bytes to devices Thu 03/17/2016 08:58:44 PM : [ Time] 20:58:54 0(0)

Yes, I got the device to go into linking mode. I can link it to other devices, or to the hub. Not the ISY 994i Both of the sensors that were working, are now not working. I have deleted them and tried to re-add them, and get "Cannot determine Insteon Engine". With Old software, auto detect didn't work and I recall that I had to select a different device to get it to work. Can't find the email I have tried auto detect, and 2845-222 and both give "Cannot determine Insteon Engine" Pretty large system, 24 devices,10 long programs. Don't want to start over.

Found a thread on linking mode. Got it to beep, Still get "Cannot Determine Insteon Engine"

Ok so. 1. How to put the hidden door sensor in "linking mode" it isn't in user guide. It shows how to add it as a controller and remove devices it controls. That works fine. 2. Now that I upgraded to 4.4.5 the Garage Sensor quit completely from the 994i. Both still work on Insteon Hub fine.

994i Running 4.3.26 UI and Firmware. I have two 2845-222 Hidden Door Sensors. They were working and then after the batteries died one went stupid. I have replaced the batteries, and they both add fine to insteon hub, but not the ISY. The first one "garage door" reloaded and works fine. The second one, "Front Door" doesn't work. The docs for the Insteon Hub are easy, click "Add" and then press button until it adds. For the ISY, I see all kinds of notes about making sure you have the right firmware and it is close to a dual band switch. It is 3' from a dual band switch, and the "garage" is 12'. When I attempt to "auto discover" I get the "Unable to add device" "Unable to determine Insteon Engine" I know I had this issue when I first bought these, and thought I kept notes, but I can't find anything. I recall it being something about adding them as a specific device that isn't a "hidden sensor" and not to use "Automatic discovery", but I have tried all other sensors, same results.