MrBill

The node count includes Insteon Devices, Z-wave nodes, Scenes, Node Server Nodes, and Folders. My guess would be that you weren't counting something. If you're on Version 5 and have polyglot there is a nodeserver named ISY Inventory that does the counting for you.

@Kentinada Your scene's are in fact configured correctly. (sorry for pushing the point, but 98% of the time posters don't understand the concept that scenes can be programed based on the controller used.) The next step that I would try, is right clicking each device that is included in the scene and select "Restore Device" (I would do these one at a time, i.e. not queuing them up with the "disable automatic writes" button.) This will resend the links stored in each device to the device. If the problem persists after that you likely have a standard Insteon noise/signal sucker issue.

I you haven't already done the above you might just try right clicking devices and selecting restore device. If you need to go to the extreme of removing devices from the ISY, I would suggest factory resets before readding them. Factory reset procedure can vary slightly by model.. a 2477. is pull out the air gap switch and wait 10 second... Push back in all the way and Hold... keep holding until the long beep STOPS.

I dislike Caseta switches immensely they are way too busy with all the marks and buttons. RR2 the simple and elegant look that high end customers would be looking for.

Sounds like the two controllers are programmed differently. Take 2 screen shots, one with the Root Level "RL Lighting" highlighted showing the right hand window, then take highlights or click on "RL UP - 2" and showing the right hand window, and post both.

There are actually two controllers in that scene. The root level that's highlighted "LR Lighting" is the controller settings that are used when the ISY itself is the controller. "RL UP - 2" is also controller because its name is Red. The scene can be programmed to behave differently based on which controller was used. Also NOTE, this isn't the problem in this case, but that little gray 1011 icon means there are things in queue that need to be written out to the device. The fact that it's gray means that you also have wireless writes disabled which is fine for short term while getting things ready, but you really shouldn't leave unwritten instructions hanging around, they will come back to bite.... To resolve put the device in linking mode, and release the wireless write hold by clicking that icon.

To add to what @lilyoyo1 mentioned. click the scene name in the tree, are the devices configured correctly there? each scene must be configured at the root level, and each red controller link.

That's also true! In this case tho, the OP upgraded to V5.3.0 but was still using V4.6.2 admin console... those two don't mix at all....

the easy way to buy the caps is the Ebay deal. I bought 2 sets just to have on hand. Looks like the sellers out of town until the 26th tho, and it does ship from Canada which adds a day or 2 if your in the states... Arrived quickly tho. Edit to add: note there is two kits a 5 cap and a 7 cap... the slector box chooses.

The important issue is that the Firmware version number and the UI version number must always be exactly equal. When the firmware is upgraded, you must make certain to get the new admin console. After clearing the java cache, the link https://isy.universal-devices.com/start.jnlp should get the correct version of the UI automatically. What won't work is clicking an admin console that you already have saved.

A great thread about z-wave to go read is this one from @lilyoyo1

I just discovered this treasure trove of old Developer Docs. Thought you'd like to have the link,,, it's buried in a folder in the PyInsteon project on github.

In the Admin console, Tools > Generate Topology will produce a list of devices then scenes it's not the greatest but it's workable.... TIP: After the HTML file opens in a browser click in the window and Ctrl-A (select all) then Ctrl-C copy, Then open a blank Excel worksheet and click in A1 and right click, paste special, match destination formatting. Once it's in Excel you can clean it up and make it more useful.

Are you aware that the ISY must be rebooted to find a PLM... It only looks for a new connection on startup.

Another option that's in Alpha testing at the moment is "ISY on Polisy" which can use the USB PLM, however we don't know how far in the future this will be ready for production usage. We also don't know when smarthome will be restocked on serial PLM's.. it will be interesting to see how fast they sell out when they are restocked.

@Mikes The largest difference is being able to use node servers to add more node types to power your automation. Nodeservers run locally on a pi running Polyglot, or a Polisy from UDI. (the pi running polyglot may be phased out in the future) The local nodeserver store can be viewed here: https://polyglot.universal-devices.com/ There are also cloud nodeserver that can be run if you have an ISY portal subscription. The cloud nodesever store is a more limited list https://polyglot.isy.io/store Some nodeservers are better suited for local, and some better suited for cloud, while a limited number are available both ways. Beyond that upgrading from 4 to 5 goes fairly smoothly nowadays however if you have ISY programs that use the feature "Adjust Scene" all of those programs will need to be manually repaired. If your interested in using nodeservers then you'll want to update... if not the path of least resistance is stay at version 4.9.

Unless as I believe what Brian is suggesting is that one may become a signal sucker.

I tried to like that post, but apparently I've over-reacted today... silly forum.

I was about to resposnd until i got to this part.... which is probably the issue but I don't have the experience with 2 PLMs in the same plug (which might lower signal to the other) nor experience with houselink to point the finger.... @CPrince If diming these keypads is truly all Houselink does get rid of it, remove that has a potential issue.

If using windows, Install the ISY launcher on your desktop. Follow the instructions in the first post of Essentially if Java is installed go to https://isy.universal-devices.com/start.jnlp which the first time it's used will install an icon on your desktop named "ISY Launcher" When clicked, this takes you to Finder... which starts the admin console.

Start reading that thread from the point I linked, I think it will get you through it.

You might want to add two NR's first. One to send direct from the ISY, and one to send via the nodesever. Receiving both is a pretty good indication of when that point was reaches becasue as you know Pushover is pretty much instantaneous. From the ISY direct to pushover I use: (of course you don't have counter variables established so delete that part) token=[redacted]&user=[redacted]&message=ISY Rebooted ${sys.date} ${sys.time}\nUptime before reboot: ${var.1.42} \nSaved Value: ${var.1.43}\n\nSent direct from ISY. and then the ISY sends one thru the notification node server too: ISY Rebooted ${sys.date} ${sys.time} Uptime before reboot: ${var.1.42} Saved Value: ${var.1.43} Sent via NotificationNS Receiving both tells me the ISY is talking to Polisy.

I don't have a Mac but I've heard of this problem before. There is a solution in a thread somewhere, you might get lucky and find it... If not someone that uses Mac will reply here soon and give you the piece of information you need to select the zip file itself.

Just out of curiosity how long is it before you get the first email? As I mentioned above then end of my 9 minute wait is really about 20 minutes after ISY reboot. If I intentionally reboot ISY, I tend to reboot Polisy at the same time, however Polisy reboots in a fraction of the time. My polisy doesn't loose power during an outage (unless it's an extended outage), ISY does. I have a windows computer that I can power up remotely, I can then enable the VPN on my iPhone or iPad and use the app "RD Client" to connect to the windows computer using Remote Desktop. The windows computer has the admin console ready to go, and I can access Polisy that way too via a web browser on the computer. Due to the small screen of the phone it works better to use the iPad but i've done it all with the phone too. That in a nutshell is the plan should I need to manually intervene from somewhere remote. So far I've never had to use it but I have run tests.

Does this mean you had to log into Polisy and restart the nodeservers, or did you have to log into Polisy AND set the credentials of the ISY in the section shown below: If you had to set the credentials there, that's why nothing connected. The question then is how did saved the credentials get reset or removed. I have the same boxes checked. Startup for the ISY is rocky. There's always a raft of queue full errors in the error log. I've experimented with shutting Polisy down during reboot, but it really doesn't seem to make much difference. I do have a few programs (but not many) that I delay start. I have a few programs that I delay the start of, the method that I use involves killing two birds with one stone. First I use this program: Startup/UptimeCounter - [ID 008D][Parent 0126][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 9 minutes Resource 'ISYnotification.Reboot.Notification' Wait 10 seconds Resource 'NotificationNS.1704.ISYRebootNoticiation' Wait 1 minute $iUptime.Counter.old = $iUptime.Counter.curr $iUptime.Counter.old Init To $iUptime.Counter.old $iUptime.Counter.curr = 10 $iUptime.Counter.curr Init To $iUptime.Counter.curr Run Program 'Start HeartBeats and Misc' (Then Path) Wait 5 seconds Run Program 'Startup/UptimeCounter' (Else Path) Else Wait 10 minutes $iUptime.Counter.curr += 10 $iUptime.Counter.curr Init To $iUptime.Counter.curr Run Program 'Startup/UptimeCounter' (Else Path) Wait 9 minutes to make sure the modem and router had time to recover (if this 'run on startup' was restore from PowerFail this delay is needed for the modem and router to come up before send a notification) then wait 1 min so notification goes out before counters reset (yes they reset too quick without a wait) Updated 2020-02-15 now minutes in 10's (instead of hours) (slower update to reduce load) From this programs use, I know that the ISY does alot of thrashing about at startup. I don't actually get the reboot notification until about 20 minutes have elapsed, instead of the expected 9 minutes. The notification is sent twice... once directly from a NR to Pushover, and the second time it's sent 10 seconds later is via the Notification node server, that serves the purpose of telling me that both the ISY rebooted and that the ISY is talking to at least one node server. This is also about my only "run at startup" program, but you'll note that it runs a program called "Start heartbeats and Misc" which is quite a list... with wait 2 between each entry. You'll note that on startup the THEN body of this program runs... during that initial 10 minutes the status of the program is TRUE. The last statement of the THEN body runs the ELSE body of the same program, which itself is a never ending Loop, when the ELSE body run, the status of this program becomes FALSE. I use this fact to delay the start of some programs by using a folder condition. If Program 'Startup/UptimeCounter' is False Then Allow the programs in this folder to run. The programs contained in the folder don't run during the initial startup when the THEN body of the uptime counter is running. It should be noted that most programs don't cause an issue and don't need to be prevented from running. The ISY seems to not get to running programs very quickly in the startup process anyway, based on notifications that I've had programs send. One more thing... When I do reboot the ISY, I never try to start the admin console until I've gotten the notification. I usually tell Alexa to set a 20 minutes timer when I reboot and it usually goes off around the same time as the arrival of the notification. I hope that the startup process gets streamlined somewhat via ISY on Polisy. Edit to add: The Folders that I delay are specifically things that might try to send Insteon commands. Of course, if you've prevented something from catching up during startup, you've got to make sure it will catch up somehow.