paulbates

Mark, take a look at this post (similar problem) and the one following it. Follow the same pattern for the directions and the backup should work. Also read this: If you have windows but don't have telnet: Install Telnet on Windows Click Start. Select Control Panel. Choose Programs and Features. Click Turn Windows features on or off. Select the Telnet Client option. Click OK. A dialog box appears to confirm installation. The telnet command should now be available from a command shell window Paul

I don't have any problems with them. Cons: The screen can be a little overwhelming to the family as opposed to a Nest. But my approach is for the thermostat, sensors and ISY programs to keep the house comfortable so that no one is wanting to change it. Probably my most complex programs determine how much cycle time for the fan to keep temp in check based on external temp and temp difference between floors. Also, if you turn on the cloud feature (separate from local api), the app can be used to control it. It took time to get used to configuring it when calibrating stage 2 kick in for heat. The 2 areas of my house, each with HVAC system and thermostat, required different deadband degrees / delay time. Also working how much humidity to deliver without frosting windows. I used the runtime programs posted in nodelink to observe how hard each system was working for heat and humidity. Once I had it set, I haven't touched either in a number of years. Paul

Nodelink is another node platform. It requires .net. I use a Pi and Mono. Its one exe, a very install via a provided install script. Its one exe and a config.xml file which the web interface maintains. I have both polyglot and nodelink on a single RPI 2B, which is taking a nap on that load. I have 2 thermostats and 3 wireless sensors : 2 internal, each installed in living spaces on the opposite floor than the thermostat, set to averaging between thermostat and sensor. 1 external installed on my deck and shared between the thermostats. The thermostats use the external temp, and the ISY can read it to anticipate high heat or very cold affecting the living spaces. I also use it for the ISY to kick off a "hot zones" sprinkling program Here are some images: One thermostat's nodes Runtime node Wireless Sensor Node Paul

I’ve been using 2 venstar colortouch T7900 thermostats for 4+ years. Local only api, reasonable hvac depth (humidity control, multiple heat cool stages, configurable stages calls, wired and wireless sensors- indoor and out... more). My wife uses the app to control temp, it supports Alexa. I use ISY firmware v5 and nodelink to control them. There’s a significant amount of features ISY programs can control. I’ve seen them for $170 delivered https://venstar.com/ Paul

Udi has been clear for several years that they’d include the ms II based on provided specs and popular demand to include it. They can’t make the sensor work. This discussion needs to be taken up where it belongs.

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.