If I need to replace the PLM is there any benefit to go with USB module or the Serial since I already have the serial cable?

Not sure is it's just a coincidence but had a power failure at my house and power out about four hours before power was restored. Next morning water softener is locked in permanent recharge cycle at 4:30 am and running for hours. House is 65 degrees. Didn't notice the Tuxedo Keypad being dead until later. Same with the eisy. Could just be weird timing and coincidence.

KeyPadLinc secondary button (Master Off) set up as Non-Toggle[Off] (so it only sends off to any responders in a scene where it is the controller). Works perfectly.

I noticed that when I click the button it flashes twice - I am guessing that this is just to let you know it did something.

I created a program that turns the "Master Off" keypadlinc LED "On" when a user clicks any of the other switches that this "Master Off" controls - works perfectly.

Here is what I have found that is weird (took me literally HOURS of trying to work this out due to the debugging I put in the program).

I created another program that will turn this LED light off when the "Master Off" is clicked - but what I found is that unless I program a 5 second delay into the program just before the command to turn off the "Master Off" LED - the LED will stay lit....If I program a 5 second delay you can see the button doing its own "flashing" thing - then a couple of seconds later the LED will dim. If its anything less than 5 seconds - the LED will flash away - but will then stay lit....

If the delay is less than the 5 secs - then the program is definitely triggered (I created some variables to debug and capture what the program was going) - its just that the LED "off" command seems to be sent before the "flashing" process concludes - and for some reason the LED stays on.

Has anyone encountered this - and have any insights why this might be happening?

I suppose I can live with the delay at the Master Off when I click it - it just is a little weird......

Thoughts/pointers/ideas?

Has anyone set up a Non-Toggle[Off] - "Master Off" like this (that becomes lit when any of its "children" are On and Off when not, and will also turn off when you push it)?

In a bit of a quandary related to the best way to approach a process - so looking for advice. I will describe below the situation - and then what I "think" is the best way to do this (then ask for guidance related to the specifics).

Situation:

I have a Rec Room in my basement that has three banks of lights. Each bank of lights is controlled independently from both sides of the large room (so each bank is set up as a two way). In this case I have an I3 Paddle connected to each "load" and then on the far side of the room there is a 2477S for each circuit. Each I3 Paddle and 2477S is set up in a scene to act as the two way - with both objects as controllers. Works perfectly fine.

At the top of the basement stairs I have installed a 6 button keypad linc - and one of the buttons on this keypadlinc I want to use to either turn on or off all three banks of lights (so one keypad linc button to rule them all).

I can (and have) created a scene where the keypad linc button is the controller - and each of the other objects are responders (lets call this the "Ruling Scene") - so when I use the button at the top of the stairs this has an immediate response from everything else (either quickly on or quickly off).

This issue is when someone turns one of the banks of lights on or off directly from the I3 Paddles or 2477S switches - I need the keypad linc button to stay "in-sync" with the status of the lights in the basement. Basically if anything is on - or partially on as the lights are dimmable - then the keypad linc button should be either turned on/lit or should stay on (if it was already lit), and vice versa - if someone in the basement turns off the last light from either a 2477S or a I3 paddle then the keypad linc button light should get extinguished.

I thought that the best way would be as follows:

1. Create a scene with the keypad linc button as a responder (to use in a program) - lets call this the "Master LED" Scene (using a scene as not sure about the effectiveness of directly addressing a keypad linc button in a program).

2. Create a program that is initiated when ANY action is performed on ANY of the switches in the basement (any of the I3 paddles or 2477S switches) - this ties in to a previous post I made about trying to find any easy way to determine if any action has been performed on a switch) - in this program if anything has "happened" then check the state of any of the basement switches (are any on, or partially on - and if so then set the "Master LED" scene to on - otherwise set the "Master LED" scene to off).

3. Just in case the above sometimes flakes out and maybe a signal gets dropped create another program that schedules itself at regular intervals (say 5 minutes?) that polls the state of the I3 Paddles or 2477S switches - and again - if any are on/off then set the "Master LED" scene on or off respectively - then wait 5 minutes and initiate the polling program (i.e. call itself) once again

Does anyone have a different or better approach to do this?

One thing I am not sure about - if the program sends an "on" to the "Master LED" scene due to ONE of the banks of lights being turned on in the basement - will this then trigger the "Ruling Scene" thereby turning on all the lights in the basement (which I do not want to occur - I want to just light the LED on the keypad linc so it can then be used to turn anything off that is "on' in the basement if someone leaves the basement via the stairs and uses the button at the top of the stairs)?

Any help/guidance (and best practices for the programs) would be most welcome.

I know I have to be careful not to have them both on at the same time, but is it OK to plug one system in during one day (EISY), do some work, such as upgrade the firmware, and tested download, and then at the end of the day turn the EISY off, unplug the PLM from the EISY, and then connect the PLM to my ISSY, and use it for a day or two, etc.?

I also have a spare PLM, so am I better to plug it into my EISY, use that pair, each on its own system?

When creating if statements - one has the option of using "Control" or "State". I just want to clarify the difference to see if my understanding is correct.

Control:

An if statement that uses "Control" means that the program is triggered automatically by the EISY if the appropriate action has been taken from the control. For example, if the program (Program A) has "If x-control is switched on" - this will automatically fire the "Then" statements - so if someone turns on that switch - this program will automatically be initiated by the EISY. Conversely if the program contained "if x-control is switched off" then if someone turns off the control then the "then" part of the program would be initiated y the EISY. Finally - if the if contained "if x-control is switched on OR if x-control is switched off" then the EISY would initiate the "then" part of the program with the control is switched on or off.

Follow up to this - if the x-control is turned on via another program - would this also trigger "Program A" as defined above - in other words - it does not matter whether the switch is physically or logically turned "on" - the EISY would initiate "Program A"?

Status:

This simply allows you to check the status of a control from within a program - but is not automatically initiated by the EISY if something physically happens at that control (or if the control status is changed by a program).

Can someone confirm that this is the case? Or am I missing something?

I don't even know where to look to find the best upgrade method/steps.

Any direction and cautions VERY MUCH appreciated!

(My ISY has gone bezerk, taking 10seconds to minutesto respond, and some "out of memory" errors have crept in from somewhere)

I do have in ISY backup from before this mess started, so can I use that to start up the EISY?

Can I get the EISY up and running and still get to the ISY to "look" at things while I switch over?

THANKS!

Current setup:

I have two 2477S switches - each are in a "two way" with an I3 Paddle (each switch is in its own 2 way - so two separate circuits). So each has a scene where both are controllers (the load is connected to the I3 in each case, with the 2477S being the "distant" on/off). (its basically two rows of lights across a basement rec room - each row controlled by each 2 way setup).

All worked perfectly.

I later decided to add a 2487S keypad at the top of the basement stairs - and I wanted one of the buttons to be able to turn on and off the rec room lights (both rows) - simple enough. I realized that this would potentially have issues with keeping things "in-sync" - so I have a couple of programs that monitor all this and make sure the LED's etc. all stay in alignment.

In addition I created a scene where I added the keypad linc button as a controller - and all the other devices (2477S and I3 paddles) as responders in this scene - so the button at the top of the stairs would directly turn on/off all the lights in the rec room and control all the other devices (the individual devices if switched on or off would only impact the button at the top of the stairs via the programs mentioned earlier).

When I added the I3 Paddles - all good - everything still worked (except the 2477S switches did not appear "on" - until the programs monitoring status picked it up). I also wanted to add the 2477S switches so they would all respond instantly as appropriate.

So here is where it got weird.

Everything was working fine until I added the 2477S devices to this new "key pad linc all on/off" scene as responders - when I did this - the individual 2477S switches would no longer operate the lights themselves directly (the I3 paddles continued to operate as they have the load connected of course).

I could click on and off the 2477S switches - and no response from the lights.

I tried "restoring" each device - this had no effect.

The thing that worked - I had to remove the 2477S devices from their original scenes with the I3 Paddles - and then re-add them to those scenes. When I did that they all worked again.

So my question is this - has anyone had this issues where when you add a device to a scene - it suddenly stops another scene from operating (and even the retore function does not correct)?

Would be interested in any feedback - also - if this happens to anyone else - then hopefully this will provide guidance as to how to correct (note that I only found out about this when other folks in my family complained that the switches were not working......... and I then started to scratch my head about what could be the issue).

Thanks!

I've spent the better part of an hour trying to find the other numbers in my system and browsing the forum for hints.

Also, I cannot seem to find out how to upgrade the Firmware. I've done it in the past but cannot seem to remember how I did it. When I go to Configure > System the "Upgrade BIOS" button doesn't function (doesn't respond to clicks). I found a link to an old YouTube video describing the process but the video is way out of date and the screen images do not match my EISY Admin Console displays.

Help!

Copied from Michel's post:

Hello All,

I am happy to announce a set of updated software and OS for your eisy/polisy:

OS v14.3p9

UDX - v4.4.0_6

IoX - v6.0.5_1

eisyui - v0.10.1

I have successfully installed my first I3 Paddles. I have them configured in a 3 Way with a 2477S via a scene defined via the Admin console for my EISY. Both objects are controllers in the scene and I moved both of the nodes for the I3 to the scene.

Everything is working fine - both ends of the 3 way turn the lights on and off and I can also dim the lights (I set the I3 up as dimmers).

The only issue is that when I use the 2477S to turn on/off the lights - the in device light flashes red a few times after the action has been performed.

I cannot find anything wrong with the setup in the Admin Console.

Does anyone have any thoughts about how I can trouble shoot this red flashing a few times after using the switch?

Thanks!

I get wanting to simplify. But logging in is a pain.

I have to use my portal login which is a much longer user name and has a randomly generated password, which means I have to log into my password manager to get the password. It's a much longer process to get in. With local, I have a simpler username and a simpler user password.

Any way to retain a local login?

Thanks.

Then awhile later I went to my kitchen and turned on one of the three wall switches. No response. I tried a second switch, and it was nonfunctional as well. The third switch (master switch connected to the load) worked OK. I had to re-link the two slave switches to the main switch again (in both directions).

Later I went to my bedroom and turned on the light switch. A pole lamp on an appliance module formerly linked to the wall switch no longer worked. I had to link it to the switch again.

When I told Alexa to turn off the lights, the pole lamp didn't react. I had to go to the "Bedroom Lights" scene in Admin Console and remove and then re-add that module to the scene again.

My memory is faint, but I believe this is not the first time something like this has happened to me (I've been using EISY and Insteon for 25 years). It's very rare, but then I don't make changes to my Admin Console very often.

I haven't checked all my other devices to see if anything else was messed up, yet.

Why did the simple act of adding devices to a scene corrupt so many links, both in the devices themselves and in the EISY? Rather frustrating.

The r2 price hasn't increased at the Canadian ditributor yet. If you're in Canada and want one, don't wait!

This morning (Saturday) I struggled to get my eISY back online. I could see that is was connected to my router, but I could not even putty into the box. And after dragging out my monitor and keyboard to connect to my eISY and after several hours of googling, multiple reboots and trying different things, I determined the eISY had lost its internal IP and DNS ability. I eventually tracked down the command to manually reload the IP and DNS . At that point I could "finish" the update I never requested. Which, by the way, left me on the exact same version I was already on (5.8.4 BTW).

I thought that upgrades were only requested manually. Which I have avoided but was getting ready to do in the next week or so. But only at my choice of time.

Anyone else have something similar happen?

I'm on 6.0.3. I'm attaching an event log that shows me doing the following:

• Device on, then off

• Set on level to 50%

• Write changes

• Turn device on (it's still at 100%)

• Change the On value to 50%; device stays at 100%) & there is no traffic in the log for doing this

I've debugged for a while. Rebooted the device. Not sure what else to try.

sys-info.txt

• "If our IoX Version is below 5.9.1, do not upgrade as your unit may get bricked"

I am currently on IoX v5.8.4.

So what is my option to update my EISY? Do I have to use some intermediary version and do two upgrades? If so, what version and any instructions on how to do it?

Thanks

But I don’t see anything in the UD Mobile app or on the admin interface that tells you how to add this to Apple HomeKit. There is no Apple HomeKit QR code on the device, and no matter number anywhere. The whole point of me buying this was to do so. If this is not possible, then I have to return it.

So someone, please let me know

My start-up in the eisy went well, the backup from my 994 updated beautifully. I then went to work on the Schlage locks. As per Schlage customer service, they mention that many ZWave folks have issues in getting new third party's like ISY to see them and that the solution is very simple. Their procedure is as follows:

1) Use the "Remove a Zwave device" for any and all previously used devices.

2) Factory reset the device removing all previously used data like codes, etc.

3) "Add a ZWave device" as the eisy calls for.

The key here I believe was to factory reset the locks. I initially tried to just add them and got a continuous "writing" within eisy. After the factory reset and second removal from eisy, the locks came on line perfect. The only other bit of work was re-writing the programs I use to look for the new devices, ZYxxx rather than the 994's naming of ZWxxx. All is well and as of now I have zero issues.

That said, my firmware is 6.0.4 and I see 6.0.5 is available. Tech said I should update it. The 994 had a dedicated upgrade option on the main page. I don't see that on the new eisy. Can someone give me directions or steer me toward the procedures to update this? I am a bit concerned to do it as there are so many temperamental issues associated with ZWave and eisy.

Lastly, I would like to add the Hunter Douglas blind app to eisy. Has anyone done that and as it's my first add-on, how do I go about doing that? As a side question - Is there a way to control older Gen1 HD blinds, or just the new models?

Thanks.