paulbates

Rudy, correct. But the ISY Lancher looks at that and downloads the right one. They should not be out of synch if you're using the launcher. Here is the link to the correct ISY FW to download for 5.0.16

Rudy Your UI should be the right level if you are using the ISY Launcher. Something it wrong right there. Are you starting by running Start.jnlp only, not admin.jnlp Paul

Rudy Yes, because its a Release Candidate (RC) and not the official release, you have to download it from the site. Scroll down to 3. and pick the firmware that's appropriate for you set up. If you're not sure, respond back with your setup... insteon only, zwave only.. and/or have a smartmeter connected to your isy Paul

Before starting the upgrade, first switch to using the ISY Launcher. It automatically makes sure you use the right UI for any firmware. From that point on, run the ISY Launcher, start.jnlp and not admin.jnlp Paul

Polisy is designed to be a Polyglot platform that comes read-to-go. Meaning you take it out of the box and linux, polyglot and nodelink are there and ready to go with a web config interface. There's no difference in nodeservers, same store, etc. It allows users that don't want to deal with linux, command line, installs, ect. to use V5 and nodeservers. It also has HW options like BT, io ports. UDI has mentioned that at some point in the future it will be the ISY as well... but this is not there or being tested in the "geek batch" Paul

Nano does simple things quickly and simply. If it comes with polisy out of the box, great. If not, I can install it. I'm not planning add other HA tasks to policy, only Nodelink, Polyglot and eventually 994i functionality. There's been a couple of times I've needed to edit the config for Nodelink, I'd primarily have nano ready for that or creating SYSCTL entries... I don't want to relearn VI or emacs, I use them too infrequently. Paul

Ugh. Not 100% sure. That would go beyond the PLM, unless the broken PLM corrupted the data in the ISY, and that was written back out in the restore PLM. I'm speculating more about that then knowing for sure. Paul

Believe me I know how frustrating this is. Literally years of perfect operation, and then something goes sideways. One more problem is a beaconing device. If restore device on the problem devices doesn't make progress, turn on "blink on traffic" in options of one of your devices that supports blink on traffic and you can see easily. If its led is blinking constantly with no pauses, a device has failed or was confused by the replace PLM traffic... another explanation for the slow response Good luck, you'll get it worked out Paul

It depends if the backup is before the PLM started failing, possibly before you noticed. However, there is secondary set of steps if you are down to a few devices. Right click on the device and pick restore device. That should force the new PLM information into the device and delete the old PLM's link. The old PLM's link data being in these devices is one explanation for the several second delay

One thing I've run in to is that the failing PLM "polluted" the Insteon system of record information in the ISY. If you have an ISY backup of prior to the PLM starting to fail; restore that backup... then perform the restore modem Paul

What happens when you manually trigger the scene with the admin console? In the program's then segment, are there other insteon set commands? If yes, is there an at least 2 second wait statement between the set commands? Paul

Hmmm ok. The problem must be localized somehow. I just opened my garage door and the notice came within 3 seconds, which is normal. It varies normally from almost instant to maybe 10 seconds.

AWS Route53 / DNS was hit yesterday and the day before. I believe pushover uses AWS. I don't see any stories about pushover specifically. I have 6 expected messages throughout the day. Is there a link to a story?

I never would have known. I've received what I expected. Specifically I noticed the garage door notifications since I'm home and opened it. It came right away.

Answered above. I've been using Nodelink since the beginning, and its predecessor venlink before. Great support and continuity since 2014 for me. Agree 100% with @Bumbershoot Paul

+1 for the Venstar color touch. Have 2 of them with indoor sensors and one shared outdoor sensor that I also use for other purposes in the ISY

☝️ This. I monitor and try to make the most efficient use of electricity during and right after installation of ha controllable devices. Then I hand it over to the device and/or the ISY and not try to modify our behavior. I didn't bother to explain the benefits of the dynamic peak power program option from our power company to my wife. The projected savings are not worth having to stop and have the ISY have alexa say "don't run the appliance right now". It would undo all of the WAF halo effect of my automation efforts.

Its my incessant need to one-up everybody ? Seriously, the only thing I can think of, is that I have the pro version. It adds the ability for more programs and devices, and the featurers supported by those last 2 icons. Its not possible to change those Paul

hart2hart's task list is time tested by a number of users here. He came back and edited the first post to contain the fully tested list of steps. If you have no z-wave devices you can red-line those steps / sections. Now is a good time to move to V5. Plan a an hour or 2 to familiarize yourself with his steps and do it. That will get you on the latest ISY FW. One note, if you have the pro ISY, you don't need to disable all wireless devices. You can use the control that causes them to be skipped until the end, see the pic below. However I did not need to do this when upgrading to V5; I think that comment may have been from zwave users. Since you are insteon only, and your are not changing your PLM address, you should not need to do this. Paul

To clarify geisen and others above (including myself) The first PolISYs delivered will serve only as a ready-to-go local nodeserver - Polyglot and Nodelink ... that's all. As delivered, they will not initially have ISY994I replacement capability.. its been stated in numerous threads by UDI that it is a longer term goal Today, the best option based on the original request by the OP is to order and install the ISY994I zwave card to their existing ISY Paul

It will in the future. I agree with the thoughts of getting the z-wave expansion card now and let your future desires to expand drive additional purchases.

Thanks for doing this io_guy. I appreciate that Mono has been there in the past, but running on the actual MS stack will be better for me. Paul

There is a lot written above... here are things to think about Use Momentary B in the iolinc configuration. Either on or off will trigger the door. Garage door openers with the iolinc will operate just like the manual opener unit.... one button for everything. In this case setting it on or off will be just like pressing the manual opener button Also, you may be trying to hard by checking the status at all. Have no if statement for the program. Simple say "set garage relay on" for both programs. That will have the same effect as your voice command having alexa press the manual garage door opener button Paul

Nodelink working here as well, updated via the script. When it came up, config.xml hadn't been copied over, but probably due to me having my config.xml in a directory I had used since the xxxxlink days...it was easy to diagnose/fix. Paul

cool. In a related question, I'd be curious how you feel about the service after you've used it a few weeks. I take it that its a mobile data to lan type of service? Paul