CoolToys

@MrBill and @DennisC are correct, but if it was working, did you follow the thread here or the wiki to replace a PLM. Mine recently died as well and I needed to follow all of the steps.

@oberkc, no green arrow, and yes I have done that more than once, thanks for reminding me to look at the basics. @apostolakisl, interesting idea, to run a separate program for Dark. That way I can see if it is "true" separately in the details. Also I could simply use sunset to set a state variable of $Dark and sunrise to return it to "0". The $Front Door state is used to start a 15 minute timer in another program to turn all the lights back off. That is why I also check if the switch is on first. I don't want it going off any time someone manually turns it on or a scene already has it on. I agree the order shouldn't matter but you never know. I did already try to add a notification line each time the door opens and the program runs. That worked just fine I got the notice each time the program ran and I verified "true" was also on the program in the details panel. It is possible the Elk status of the door is also in a scene that I have missed, and it is also possible that the program just didn't restore from the ISY backup to the eisy perfectly. When I get home tonight I will remove and replace the Sunset to Sunrise program first just to check, but even if it works I like your solution better and will rewrite all three of the programs that way.

@Brian H, Thanks. I didn't think about mesh v wireline only modes. I will look at that tomorrow. For the short term I just deleted it because it was doing odd things. The PLM is the Serial with USB to serial adapter and the PLM and eisy are on the a phase with the 2450 on the b phase. I have a repeater about half way between as the crow flies. One of the many things that went stupid when i upgraded from ISY to eisy.

@JCBond yup tried that and still didn't work. The other remote is in toggle mode but set as controller for the scenes. It works fine. The one I use upstairs doesn't appear to accept the change to toggle mode, so maybe that is the issue. For the money I'll order another one and see what happens.

@DennisC,Yes I wrote this for the exact situation that you mentioned and @Goose66you are correct. If the lights are already on and I open the door I don't want to run this program. I have a two other programs that turn the outside lights on with other conditions, i.e. we are home or alarm is set so it looks like we are home. This program is only to work if the lights are off and someone rings the bell and I open the door like my mother showing up at 3 am. Yup it happens. @apostolakisl, As background all of this worked on my ISY just fine. The problems started when I upgraded to the eisy and changed the ELK module to the ELK node. While 99% of the new elk node is way cooler and lets me do more things. the one odd ball thing is that none of the three programs with sunrise to sunset programs work any more. The new i3 outlet also randomly turns back on from time to time, but Steve Lee thinks my lamp doesn't have enough of a load so the auto sensor is kicking on. I am on the road today, and home tomorrow so I will try @garybixleridea to re arrange the "if" and put the sunset to sunrise command first. If the house is dark and I enter the house the ISY used to turn lights on at night for 15 minutes with a program I labeled "late arrival". Now that program also ignores the sunset to sunrise stamens and does it 24x7. I don't know why. The same for leaving my bedroom at odd hours. That is my "auto snack" program that used to work at night only and now works 24x7. The MSII's did fail to transfer and I had to delete all four of them and relink them so maybe there is something there so I will double check that. Late Arrival and Auto Snack both use the MSII inputs. Possibly I linked them to scenes but that doesn't explain the front door which is an elk sensor not an MSII. I will do the searches tomorrow when I get home and see if somehow the new elk node changed the code or if there is a //error somewhere that I missed or if I linked any MSII to a scene for testing and forgot to unlink after I fixed the // error lines in the programs. I might also delete the sunset to sunrise lines in the program, reboot and then add it back in just in case there is some latent binary that didn't transfer to the eisy. None of the MSII transferred, so clearly there are some odd issues with the upgrade. Thank you all for looking at this and giving me ideas to look at.

So as a status, it can activate the lights 24x7? That makes zero sense to me, If opening the door causes a condition and the program runs it should run. But just for fun here is the updated version and same problem. Open door 3:44 pm and lights turn on. The Niche is the landscape lighting which also turns on. Front Door Open - [ID 0013][Parent 0001] If 'Area 1 / FRONT.DOOR' is switched On And 'Entry Front Door Light' Status is Off And From Sunset + 5 minutes To Sunrise - 5 minutes (next day) Then $Front_Door = 1 Set 'Entry Front Door Light' On Set 'Garage Front Porch Lite' On Set 'Courtyard Niche Top' On Set 'Courtyard Niche Bottom' On Else - No Actions - (To add one, press 'Action')

Roller Shades Manufacturer : Graywind Model: Roller Shades with Zigbee Motor Support Page https://www.graywindblinds.com/pages/contact Commands requested "up", "down". "Favorite", Status requested "battery low". Sold on Amazon, Alexa Compliant, Alexa discovered and operated as soon as powered up in programming mode. Amazon shows as yooksmart smart device, manufacturer says same as "IKEA" also. eisy 5.7.0 w USB Zmatter finds them and lists them as "unavailable". https://www.amazon.com/stores/page/FCD06F74-9BD9-470A-B117-07AF4C4218E4?ingress=2&visitId=4356e004-e963-4dfb-a403-c8724130777d&ref_=ast_bln 11/1/24 Update, IoX 5.8.4 sees all of them, and lists them as "Main". but when selected the options are identify and query, and nothing happens.

Like @garybixler, I ordered the Graywind window coverings. I got the Zigbee motors, and added the USB adapter to my eisy. When I hunt for zigbee devices it it quickly found and listed as ZB34677.unavailable with an option to "interview" with a choice of seconds. Any ideas, manufacturer says it is ZigBee for Alexa but it appears to use wifi for that part. I have reached out to Graywind. Ideally I just want to add the shades to a scene. I did try to do the interview plugged in just in case the batteries went to sleep too fast. While digging around the forum, I found notes that the antennas had different color bands. I don't see any colors on the antenna. I added a request to add the blinds in Zigbee support and opened a ticket for the antenna question.

Here it is, If the light is already on, I don't want it to trigger program and turn off the lights unexpectedly. Front Door Open Copy - [ID 000C][Parent 0001] If 'Area 1 / FRONT.DOOR' Logical Status is Violated And 'Entry Front Door Light' Status is Off And From Sunset + 5 minutes To Sunrise - 5 minutes (next day) Then Set 'Entry Front Door Light' On $Front_Door = 1 Set 'Garage Front Porch Lite' On Set 'Courtyard Niche Top' On Set 'Courtyard Niche Bottom' On Else - No Actions - (To add one, press 'Action')

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.

Ah, I wouldn't sell them, I was looking at it as an individual emergency replacement program. If Insteon doesn't make it out of the ER, you could get a one off unit made. I have one off items made all the time for old cars, artwork and my studio. Yes it might be $200 or $300 but that is way cheaper than swapping all of my switches and outlets to Z-Wave or something else and then the hours to reprogram my iSY. Again as long as Insteon has a heartbeat, I'll buy from them and I would also try to find used online first and hope I don't buy a lemon.

It is interesting you had a dimmer fail. Of the hundreds I bought and sold over the years, I only had one fail, and it was under warranty within days of install. Too bad we don't have a local Fry's or Radio Shack any more.

Understood, and having a few patents and trademarks under my belt, I also know that there are people overseas that will make anything you want regardless. As long as new Insteon is around I will of course buy from them. If the 2448a7 is re-released by new insteon, maybe we can put it on the wish list for the eISY Michel teased us with. Has anyone uses a 2448a7? Reliability?

Given the failure rate of PLM modules, I wonder how much it would cost to OEM a block of them. I am still a bit confused why Insteon never created a wireless module or released the specs so someone could make a usb dongle that used the wireless side of the insteon mesh? In my 15 plus years of using insteon, I have had four PLM failures, one keypad and one light switch. Sadly I used to have a really cool X-10 tabletop remote with big lit buttons that failed just after they were discontinued. Maybe the new insteon will fix some of these issues?

Hmm, Ok Yes X-10 Pro still exists, and interestingly after a bankruptcy/shutdown/revival. So I'll agree I overstepped with that statement and retract it. I'll change it to the opinion that X-10 hasn't grown with the industry so it is not the leader it was in the 1990's when I started in the HA business. As far as the insteon announcements and blog, I hope it can pull the rabbit out of the hat and revive like X-10 appears to have done. But keep in mind X-10 did come and go more than once. I agree with several others that this isn't something that just turns on. Supply chain development took years. I'll disagree with a couple others about Ken. I think brining back an insider that might be able to rebuild those relationships faster might be a good move. As the wise man says "We'll see". Until then I am just trying to undo what I did that broke my system, and offer my apologies for appearing to "troll" the forum. Thank you for responding and keeping me in line and up to date.

That is excellent to hear, but I have not been able to contact them (or Michael). I look forward to hearing from them (him). If you want to call it trolling because I am trying to catch up on the craziness, I'll take that hit. None of the information provided is "False", some is my opinion. The phone number on the UDI website answers with "Could not validate this request". The latest update on the News section of UDI website is June 11, 2021 The latest Twitter update was the next day. Saying that I am worried there may be some trouble at UDI as well given those observations, isn't false, it is my opinion. I was in the high end AV and HA industry from 1990 - 2009, so maybe my ideas are outdated, but I'll stand by them. I believe UDI has a future regardless of Insteon. Before I posted, I did in read through several sections of the forum, went to the wiki, and the firmware update pages to get 404 errors, page not found. I admit my system has been rock solid since the last time Micheal and I talked almost two years ago. It was a failed ELK wireless window sensor sent me down this rabbit hole. Honestly I didn't even know that Smarthome/Insteon collapsed and Insteon is attempting to revive. It started out a bit exciting that there was a new possibly better version of UD Mobile v Mobilinq. I have both modules, so I swapped them and the trouble began. I am sitting here trying to undo that now.