paulbates

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.

Sometimes subnodea are organized under a + sign. Are you seeing that? If no, and it’s your first nodeserver you might have to reboot the ISY to get the node profile recognized. Typically that’s not needed, but worth a try Paul

@lilyoyo is correct. Neither the ISY or Insteon are architected / designed to be "active active" or "active passive" You'll also want your ISY Portal content/configuration moved, which are UUID specific as well. I'm not sure if that can be done via a support ticket, but I'd ask if you’re running v5 and nodeservers, you also have to think through IP addresses of the ISY and the local nodeserver server systems. If you have externally systems that contact the ISY like mobile apps, this needs to be thought through as well. Treat the recovery of the PLM as separate. If my ISY were to die for some reason, I would move the current PLM over the the new ISY and follow the procedure above. I keep an additional PLM around just in case. Historically that has been the weak link, but with SmartLabs changes to PLM hardware in the past few years, I don't think anyone knows how much of a problem it is any longer. But as a key component and <$50 on sale, I'll always have a spare. Paul

I've been on 5 for a few years on my main/only ISY. You can upgrade directly to 5.0.14 I think. I'm on 5.013, in that I don't necessarily upgrade every time if there's nothing in it for me. If I was going from 4.x, I would say go direct to 5.0.14 The V5 releases are stable, but there is a bit of a learning curve to get the first nodeserver running. You have to set up a nodeserver host as well to run nodeservers like polyglot on. For most people, this is buying and installing a raspberry pi computer. V5 is the way ISY is moving, so this would be a good time to change. Since you want something that's a function of V5, harmony, this is a valid reason. Upgrade to 5.0.14 - make sure what you have already is working the same (make a backup of your current setup before upgrading) Give it some time to get comfortable Get a pi and get it setup and running Give it some time to get used to the pi Install polyglot (from here on, you're ready to install multiple nodeservers, the first 4 steps were 1 time) Install the harmony server Paul

If you have ISY v5 firmware, you can use the Polyglot harmony v5 nodeserver. Look under the polyglot section of the forum. While you can control the harmony with the nodeserver, that’s typically easier with Alexa. The reason to use both is that Alexa can easily control the harmony to get equipment in the right state easily with voice commands: "Alexa watch tv".. The ISY can then see that things changed via the harmony polyglot nodeserver, and with ISY programs you can control lights etc in response to the harmony states changing Edit: For the portal- I haven't used this though Paul

They can help. I have one in my garage to support an iolinc (single band only) on the outskirts of my insteon network. The iolinc misses comms sometimes if I remove the 2443.

The answer is yes. The Insteon compatible controller is from SmartenIT and is called a EZFlora. These control 8 Zones each, so you need multiple EZFloras if you have more than 8 Zones. Also, if your system has a pump or master valve, you lose 1 zone (7 instead of 8 ) The ISY can directly install and control EZFlora zones. You write your own programs to determine time-of-day to water, zone cycle times, etc. You can use the ISYs weather module to help to avoid cycles when it thinks its rained or will rain. There is also an irrigation module for the ISY to determine runtimes. You find these under help / install modules on the Admin Console. Not to confuse things, but I had EZFloras for 6 years and spent a lot of time on my programs. I switched to the rainmachine that I use with ISY V5 firmware and Nodelink Paul

It can happen if the device status changed, and the Insteon network message did not make it to the PLM/ISY. For me it normally appears as a device status change, as the ISY treats it as such, but nothing actually changes at the time of the query. To answer the question with a question, did you notice an actual change in device status at 3am? iolincs also have unusual behavior for a query and will report back as if they were activated. Is Fire Shed an iolinc? Driveway Flood Light might be a missed message. If this shows up on many nights, it could mean that floodlights have poor communications... either way far way on the powerline, or the light itself is creating line noise, interfering with the message being returned to the ISY Paul

I’ve had 3 for a number of years 1 is in the attic controlling a motor for heavy duty dampers 2 in the garage... 1 reading a Hydreon rain sensor and the other controlling the detached garage door. I’ve been controlling the garage door since 2011 with the same iolinc and keypad key... if it missed even once my phone would be ringing.. it hasn’t. I get regular notifications when the hydreon cancels a sprinkler cycle due to enough rain. i consider my attic and the garage hostile environments with temps above and below the iolincs specs, but they continue to work

@Techman Where are the thinned out products? Looks like most of the same core products to me: I've seen the smokebridge discounted, but the First Alert Sensor Family (wireless, non z-wave) it supports is on FA's "End of life" warning list. Makes sense to start getting rid of the bridge and get z-wave for this type of product. Their clearance page has a lot of z-wave and some zigbee on it For the "succession of discounts", they've followed x10.com's lead on semi annual deep discount specials as long as I can remember. That's how I built most of my network. They are definitely in a "Status quo" state, can't argue that. No sign of new products, but I've found nothing in the rest of the product line that says anything has changed. Paul