paulbates

That's a sign that the the links table in the PLM, which allows it to decide what insteon network events to receive/send to the ISY, is empty. To find out, Try Tools / Diagnostics / Show PLM Links Table / Start You can try factory resetting the PLM and Restore. Yes - complicated sometimes, but that's the only way I know if the PLM links table is evidence of the problem Unplug both ISY and PLM, Wait 10 seconds Plug in the PLM and hold set button 3 seconds release the set button and wait for the led to light plugin the ISY Restore modem This is the sign of dying PLM, maybe the factor reset will help. Paul

Hey @larryllix, take a look at this post Paul

The idea is that you can close the ports into your house and get rid of dyndns (if you aren't accessing other things with it). That's exactly why I have the portal. My ISY "dials out" to the ISY portal, and I connect to the portal to access my ISY when I'm remote. You can access the ISY web interface and the Home Automation Dashboard (HAD) which is a fancier ISY web page. You can pick between those from the portal. You can also use the portal to access the admin console. Paul

No, it didn't actually get a true open. The door was down, and had been down. Over time it slowly, and only a little, traveled from right to left. It waited until we were 90 miles away at my daughters college to trigger a phantom "up". I guess the point is I spent some time chasing an Insteon phantom that didn't exist, is it was a physical problem. I eventually nailed a shim in so it wouldn't move around. I could see that potentially if something got into the wiring. Paul

Eddie Any chance there is something going on (short, etc) with the wiring on the output contact side from the iolinc to the door..causing it to open? I had a physical related issue when mine false indicated an open when the door would travel a little further away from the contact sensor. Paul

Whatever the 'something else' is has to be a controller in the scene you are using, or, control the scene and not the device. If "something else" is a program or mobile app, have those set the scene on/off and not the device directly. Paul Sent from my iPhone using Tapatalk

Version 3.3.10 FW is the end of the line for the 99i. I don't think you have to have a PLM, you might get errors when it boots up, but it should be ok. The thing to keep in mind is that the network module for 3.3.10 does not support the latest SSL, and specifically TLS. If your network resources are local to your LAN and http://, probably you will be ok. But if you are connecting to cloud services like pushover, or want to use gmail, its not going to work. FWIW, with those vulnerabilities, I would firewall it and keep all activity in the house. Its probably worth an hour or so of experimenting to see what will work. Paul

Its on its way to PLM heaven. You can try restore modem for temporary relief, but the operative word is temporary. Get another one soon. Paul

Neal Its not a bug, its working as designed. "Press and hold"= activate dimming. Even on/off switches exhibit this behavior for when they participate with load responders that dim. I have a number of keypad buttons and switches that I use this feature/behavior on. Paul.

I might have not stated it right. There was a version that I had to backgrade to and stuck with, passing up new features, until HS3 came out. I didn't have the willpower to put my family through another wasted upgrade even when later versions of HS2 supposedly fixed the problem, when HS3 was just about there. I don't recall having stability problems with HS3, it was more that my lab experiments to estimate upgrade effort showed it was considerable.. so I stopped and shopped around. I had a significant amount of vb scripts to directly control my 2 ezfloras, and that was basically a re-write for me, just to get back to where I was. Nothing really new was introduced in HS3, so it was a lot of work to get back what I had. The only problems I have had with insteon devices have been: Notorious production flaws like the bad Keypadlinc caps in 2011. Replaced several of those Bad outdoor design of the original MS, which can be addressed by putting a bead of superglue round the outside front bezel Knock on wood, been pretty luck with PLMs. Into year 3 with refurb version I bought from orchestrated with my refurb ISY. Really agree on UDI and keeping insteon at the next level. You can live with the hub, 'roll your own' code or use ISY.

I did ok with HS1 and HS2 until the zwave debacle. WAF had been good and then went down. There were things I had to "un-automate". When HS3 came along, it was a large enough recreate of some of my functions (vs upgrade) that I decided to look around and landed here. I went Insteon early to bridge off of X10 with those first gen products. Most of mine are still installed, I've done very well with them, inlinelincs, togglincs, and lamplincs, followed closely by outletlincs, and iolincs. Paul

+1. Having personally upgraded through all 3 versions of HS, this says a lot. If you recall, HS went through a long period of trying to jam Zwave into the main product code base rather than make it a plugin like other technologies like insteon, and paid dearly for it. Do you remember how many years of fixes to fixes, memory leaks, crashes, etc? I love having code that works and wait for it to be released when ready, rather than wonder if I can fly out of town and have to have backdoor access to upgrade downgrade and restart a server. I have significantly automated more functions on the ISY because I can count on it to work once I have it done. Paul

Hi tommyrob, welcome to the UDI forums! The program below is for a door sensor, but the concept is the same Battery Doorwall Heartbeat - [ID 0059][Parent 0019] If 'Zystem / Battery Alerts / Doorwall Sensor-Heartbeat' is switched On Then Wait 25 hours Resource 'Pushover Doorwall Sensor Battery Low' Else - No Actions - (To add one, press 'Action') Since the heartbeat comes approximately every 24 hours, sometime before 25 hours it should restart the program. If it doesn't, the program completes and does whatever you want, send an email, etc Paul

Things have been in a state of flux for a few years, I doubt much relief is on the horizon. Realities for ISY users: If you have Insteon powerline control (switchlincs, keypads, lamp, iolinc, etc), those work and will be available and working on the ISY for years to come. I have 50+, their functional and work. I don't have the time, money or reason to swap out a perfectly working system. For items where the API is in flux, like the MS; the old one does the job as an MS. I'm going to stock a few extra (menards is closing the old ones out at discount) We're exposed on the things like sirens, new MS and analogue sensors. I think if you need those kinds of things, a zwave card and aeotec is in your future Node servers will open a big doorway, via developers or in the portal itself. The beauty of the ISY is integration, and playing on the strengths of each technology. Paul

Cool! Its always harder than we want. As a future note, sometimes but not always, you can change the subnet that the router uses to what your current one is, so the isy and everything else don't even see it happen Paul

Change the ISY's gateway to 192.168.0.1 Change the ISY's DNS to: 192.168.0.1 Your new router uses the 192.168.0.y subnet, nothing with 192.168.1.y is getting out

Interesting that its back to 192.168.1.168 in the error message. If you have a good backup, there is this. Paul

There are 2 things that appear in the finder. One is ISYs it finds by pinging your network. The other is manual entries. I believe what you're seeing this the manual entry created based on the suggestion a number of posts back. Paul

If the router supports IP address assignment by MAC address, give that a try and restart both MAC=00:21:b9:02:2c:44 and IP=192.168.0.161 If all 3 entries in the ISY got changed from 192.168.1.y to 192.168.0.y it should have found it Paul

Can you ping 192.168.0.161 from your windows system? Does the new router provide a table of connected clients with IPs, usually you can find the ISY there Paul

Assuming you kept 192.168.0.161 as the address (and nothing else randomly picked up that address) add this to the finder http://192.168.0.161/desc

The router may have the ISY's mac address at the old IP stuck in ARP. Unplug them both for ~2 minutes. Bring the router up first, wait 2 more minutes, then plug in ISY. I think you are very close Paul

ok, the pictures suggest that changing the 3rd octet from 1 to 0 should make it work. There was no route to the internet for 192.168.1.y Paul

Ok, I see what Larry is saying, this the other problem Where you have 192.168.x.y : Right now, x=1 In the ISY, change x=0 Paul

Yeh there may be multiple things going on. The DNS relay was one them for sure. I'm also assuming that turning on relay provides the local DNS server at the router's of 192.168.1.1... is that the router's address? Go to a window computer, open a command window and type in ipconfig... check the gateway and dns addresses provided.. the ISY's should be the same Paul