paulbates

Not sure if Larry’s advice fixed it... if no; Are you sure the expected programs aren’t “stepping on each other” ? Disable all but one and retry. Also, if you have scenes and programs for the same function, that could be causing it Paul

- One suggestion is to verify that its not something else, e.g. the problem is not a program. What happens if you use the ISY admin console to: Turn the device on / off directly? Turn the scene on / off directly? Same behavior or different? - Another suggestion: There's a way to get the program(s) to reveal when they've been run, you can use this after recreating the issue: Go to the programs tab in the admin console Click the Summary tab to the left Find the Last Run Time column in the table Click it twice so it shows the most recently run programs on top Test the switch to recreate the issue, then press the refresh button on the right the program(s) will be on the top of the list Paul

Good point, I missed that one. The ISY needs to be factory reset prior to that. The updated steps are: Make sure the new ISY has all of the modules (network, climate, etc) the old ISY does Alternatively work with UDI support to transfer the modules from old ISY UUID to new UUID Don't remove or do anything to z-wave on the new ISY at this time. Attach the PLM and network to the new ISY Factory reset the new ISY Restore the old v4 backup to the new ISY, makes sure its running. Add the new ISY to the portal, if there is a portal account, make sure everything's working Upgrade the new ISY to v5.015a z-wave version (not the one with zigbee, etc) Follow the 10 steps under Install on the first post of the V5.0.15 thread Ignore the section about migrating zwave from the 4.x branch since there is no existing zwave on the existing ISY After the upgrade, look through the programs tab for any yellow colored program icons that need attention, usually scene related Sometimes just saving them fixes them backup the working result Let it run for ~ 1 week to make sure existing functionality works. Back it up one more time When ready for zwave devices, configure set up zwave card, etc.

The same task will be ahead though.... the current running v4 environment must needs to be upgraded to 5.x. That is done one of 2 ways: Upgrade the existing ISY to v5, back that up and restore to the new ISY,... or Restore the the V4 backup of the old ISY on to new ISY, and then upgrade the new ISY to V5 I'd recommend #2 and do it this way: Make sure the new ISY has all of the modules (network, climate, etc) the old ISY does Alternatively work with UDI support to transfer the modules from old ISY UUID to new UUID Don't remove or do anything to z-wave on the new ISY at this time. Attach the PLM and network to the new ISY Restore the old v4 backup to the new ISY, makes sure its running. Add the new ISY to the portal, if there is a portal account, make sure everything's working Upgrade the new ISY to v5.015a z-wave version (not the one with zigbee, etc) Follow the 10 steps under Install on the first post of the V5.0.15 thread Ignore the section about migrating zwave from the 4.x branch since there is no existing zwave on the existing ISY After the upgrade, look through the programs tab for any yellow colored program icons that need attention, usually scene related Sometimes just saving them fixes them backup the working result Let it run for ~ 1 week to make sure existing functionality works. Back it up one more time When ready for zwave devices, configure set up zwave card, etc. Paul

Tom With that method you may be able to cut down the number of programs by utilizing the Else: add the notification for off after the Else clause Paul

Tom Assuming this is an Insteon thermostat? Wired or wireless version? You will want to look at your event log and see if the ISY is catching the events from the thermostat Start with tools / log it will save to excel filter the first column for your thermostat Do you see the events your looking for at the times you expect? If you don't see what you are looking for, something is wrong on the thermostat side, try the next test below: If you don't find what you're looking for, use the even log Tools / diagnostics / event viewer set to level 3 - device communications force a cool cycle by lowering the temperature to make the ac come on wait 5 minutes and then set the temp back up (you don't want to short cycle an AC unit) Did you see traffic related to those events in the event log? Paul

Can you access the pump motor and read the specs? See the switch capability specs below. Motor operating noise could be a problem for the insteon switch (dual band or not), so you'll also want to put a filter some kind on the pump motor if the motor is close (in wire feet) to the switch. I've used the XPNR for motor noise successfully before. Easy to install. Here's the specs for the 2477 S Paul

If the bedroom_AC_on_2 program is supposed to turn it off, it should be <= 27 (or 27.5 or something lower than 28)? You will want to make sure that there is at least .5c between program _1 and _2 so that its not constantly cycling. Paul

If you replaced your PLM, then you do need to put each sensor (and any other wireless device) in linking mode during the PLM upgrade. Do the sensors have the little 01010 icons next to them in the admin console? Even if you did put these in linking mode after replacing the PLM, sometimes is has to be done again. The original symptoms you described still can be explained with this as the root cause. Paul

Yes, thanks. That's still where it is... given the lack of defined messaging from SmartLabs, opinions are all over the place. Nothing against anyone's opinions, but that's all that they are - opinions.. mine included. I don't believe in universal, singular, one-size-fits-all answers. @Bumbershoot- thanks for the mention. I had already clicked "ignore this thread" when I saw it going down this rabbit hole again :D Paul

You can go from where you are directly to 5.0.15a, once you get your ISY back to a known state in V4 version you were on

The most current version of the 5.x branch is 5.0.15a, located here. That is the only version to consider at this point. To address where you are right now, my recommendation is to Follow the directions to Factory reset the ISY located here Use the launcher to get the latest admin console (it will be admin/admin) This is a link to download the launcher file Restore your current backup of your ISY prior to attempting to upgrade Make sure everything's working Follow the directions to the link on the top to go directly to 5.0.15a Paul

What was the version you were upgrading from, and what version are you upgrading to? Paul

Did you download the version of Admin Console you are upgrading to? If not, download the right version. Paul

When this happens, typically the credentials revert to admin / admin. Then change back to what you want Paul

Sometimes Insteon devices need updating after a PLM replacement. Assuming your garage door is monitored by an iolinc, I would right click on it in the admin console select "Restore device" Let if finish, test again. Paul

Welcome to the UDI Forums. Both changing to 50 is pretty specific. Do you have an ISY? What programs do you have for the thermostats? Paul

It of course comes after the 994iW. ??

No. There’s features starting in 5.0.9 admin console that facilitate the upgrade. Download the latest version of admin console and use it to upgrade 4.7.3 Paul

I think the question is about "recycling". I've kept a couple around too. When I had difficulty with the iolinc in the garage, I already had something in "the insteon box" to use and worked.. instead of placing yet another order. I agree that if I didn't have something to use and needed signal coverage, I'd get a lamp / on-off module. The packaging on the newer modules is smaller and looks cleaner, but I'm not looking for my garage to be depeche mode.

If you have an old phone charger and can plug it in with the light, that might help, if the problem is what @lilyoyo described. Very likely the problem. Also, being able to turn on, but not off, is sign that the load is introducing line noise and the Insteon "off" message is not getting through . I've had cases where line noise even overwhelmed the switches ability function with RF. You can test this by temporarily trying a different load and seeing what happens. Paul

Hi and welcome to the UDI forums! There is a way to debounce, it will take 3 small programs. 1. Capture the sensor trip and also don't re-execute for specified time. Its important that the second statement check for false. Its also important to run another program that sends the notification and not put the notification statement here. That won't work Capture sensor trip If Zwave sesnor switches on <enter your device statement here> And Program 'sensor tripped Recently?' is False Then Run Program 'Sensor Notification' Else - No Actions - (To add one, press 'Action') 2 - Cause the first program to not re-execute for the specified time window. Enter/change the amount of time that works for you for how long to wait before checking again Sensor tripped Recently? If From Last Run Time for 'Sensor Notification' For 20 minutes <you decide interval to wait> Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') 3 - Send the notification. Needs to be a separate program so that program 2 has something to check. I disable this program in the list Sensor notification [Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification...... Else Paul

I have the same experience as @larryllix with LEDs. I have one that I can only dim so far. Before you put a lot of effort into installing all switches, the best thing to do is test one of each kind bulb, and one at a time and see what happens. If you have a test fixture wired up use that and bring the bulbs to it... if not install 1 switch in each LED scenario and test it that way. Paul

On the main web page is an option to autoupdate nodelink. Check that and pick a time of day to do it. Then there is nothing to do Paul

To follow other comments, my RainMachine does +95% of the job on its own. I use Nodelink features to combine sprinkling notifications with my other ISY notifications in pushover. Nodelink lets me use my rain sensor to put RainMachine schedules to sleep for 48 hours when there’s been enough rain. I can also use nodelink to have a program automatically switch from every 3 days vs every 2 days sprinkling when it gets hot enough out, and back again in the fall, saving water. the RainMachine does do a lot on its own, but the ISY let’s me optimize it. When I sell the house, I can give the buyer options to keep everything, or disconnect the ISY and the RainMachine is standalone.