paulbates

You can add a new eisy to your renewed account @ my.isy.io

To @oberkc's point: I went back and looked at the iox program you posted, and he has a point that plausibly explains what you're seeing Set 'MB Kelly Watch Winder' Fast Off Set 'Garage Lights' Off Wait 5 seconds Set 'Kitchen Main Lights 3 way' Off Set 'House Front' Off Set 'Garage Front Porch Lite' Off The commands inside of the 2 groups, before and after the "Wait 5 seconds", are banging into each other. Each "Set" command is creating messages to the Insteon device, and the Insteon device is responding. The next 'Set' command from the PLM is banging into that return message from the switch... then its retrying.. more collisions There are 2 ways to address this: (Recommended). Put each group of devices into a scene and turn the scene on or off. Scenes don't send clean-up messages, no wait is needed Put a 2 or 3 second wait after each direct device command.

You're almost there.... under Else Set "Missouri Christmas Lights" Off

Try the windows computer route: Copy the files off the current card, taking note of every file that it can't copy because it can't access it, but click continue each time so it keeps going Find those in the unzipped backup and replace them: If its more files than nodes I'd come back here and list them Copy the updated file set on a new card Hope that it works, you'll want to verify devices afterwards The card is FAT 32, but scroll to the second post here were it's recommended to format the new card on the ISY via telnet

I have several these directly linked to an Insteon chime/siren and with Notification plugin messages to pushover. One of them went off once near the well, I had placed it too close. I cleaned the sensor like you did, pulled the chime module out of the wall to shut it up for a while and plug it back and replaced the sensor on the floor a little further away.

I shows the last status change and that can take a while. "Blank" probably means the eisy was reset. Did you try pulling the battery after drying it with the towel and letting it sit an hour?

Add the keys to a scene and make them both controllers. Add the light too

You'll want to restart the isy after that change if you didn't

If what you have is working for you, I wouldn't.

Should work... I want the fewest physical connectors possible for wiring.

My suggestion, if you have a choice of which controller to have remote, is to switch to a serial PLM and get UDI's conversion cable.... there have been reports on different forums in the past of going 50' or more over serial. You might have to get a custom extension cable made or look them up on line as they are traditionally male- male and you'll need female - male. This post discusses the pin outs.

Did you just migrate to eisy? If yes, there is a know quirk with the first run programs that use time of day... leaving it as is and letting it run for a day or 2 will permanently resolve it

Yes... You've documented several symptoms, especially the restore that works temporarily

The eisy in unique in that there are different functions associated with pressing the power button X times... I don't have the link right now My suggestion is for you to submit a ticket

You can try factory resetting it and restore device, assuming it's insteon and especially if it's been running for years

In addition to Guy's comments, can you say what the previous switch was and how the wires were connected to it? Is it a 3 way in concert with another switch?

What you're describing is normal: Swtich 1: controls light and it's red lead connects to the actual load line to the physical light Switch 2: Joined to Switch 1 with a scene. Both switches control the light properly at the switch Remotely controlling Switch 1 from iox works Remotely controlling Switch 2 changes it's status, but the light doesn't come on Remotely controlling the scene should work as you expect. This is Insteon working as designed. Once you crate an N-way relationship with multiple switches in a scene, you've created a virtual circuit. You control the scene from iox and not the individual switch. In your iox programs' set commands, Set scene on/off, not the switch.

Wait would probably be easier. I'd use a variable $chime_active in this example If motion sensed and $chime_active = 0 then $chime_active = 1 (allow the 10 minute wait to complete) Set chime on (or however you make one chime) wait 2 seconds Set chime on wait 2 seconds Set chime on wait 10 minutes $chime_active = 0

That is a strange one. I have 2 on/off that don't exhibit that problem, I would notice. But they are v.49 Probably a bit of a long shot, but I'd suggest firing up iox and starting the event viewer and set it to level 3, as close to the problem time as practical, e.g. when going to bed. Look at that in the morning

If you have the portal, you can log in, click tools > information > ISY Information. There's a a specific url to your ISY listed there.

Ok. Try taking to the appropriate echo and say "Alexa, discover devices"

You don't have to link each one if you added it through portal and your account is linked. Are you up to date with your portal subscription?

I did the same after Nodelink stopped being developed. Nodelink actually had that humidex feature/capability built in for Venstar years ago and it worked great.

1- This is typically done with smart thermostat, I've done that with the venstar colortouch and ecobee. 2- The alternative is to get a zwave on/off outlet or on/of plug-in module and plug 12 volt ac plug-in transformer (hardware store) to it, and wire that to the humidifier's water control actuator. Based on humidity levels from openweathermap, turn the zwave outlet/module on or off. I'd be careful with that as the sole source of data, I'd want a zwave humidity sensor (assuming that it exists) to confirm the actual building humidity.. have some iox watchdog programs to not let it humidity levels get "outside the box'

You want to be in linking mode first, so that the PLM/ISY catches the Insteon traffic from the device(s) being put into linking mode.