lilyoyo1

https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY

There's minimal delay in starting the scene but a delay in the whole program running since I separate each room with a 1 second wait. This is to ensure all communication has occured prior to moving on to the next room. Typically, I start my program with the most important room and end it with the least important. For example, if i hit my away button in the kitchen on my way to the garage (in the evening), it'll turn on the hall light, unlock the door to the garage, open the garage door, turn off the kitchen, master bedroom, etc. Rooms that we generally do not use such as the dining room and scullery are processed last since the likelihood of them being on are low. The same applies to my goodnight. Hitting it in the living room will dim my lamps, turn on the step lights, and turn off the fan and other lights. Then the kitchen, and other rooms with the least used rooms being last. The more things that happens in a program the longer it will take. A wait between each one actually helps you more since you don't have to worry about collisions and so forth. Running 20 scenes with a 1 second wait will be more efficient than trying to run a single program with 100 different devices.

Being such an old system, it may not support newer devices since the firmware has not been updated for it. If it does work with the 99i, factory reset the device and make sure that the ID number was typed in correctly. I prefer to use start linking and pressing the set button so that I don't have to worry about typing something in incorrectly.

1 way to save link space would be to link basic multi-way switches together outside of the Isy. Obviously if your changing brightness levels throughout the day or other programs, you would want to avoid this.

While this nodeserver is great for seeing what your isy has, basic device and scene count is a poor way to figure out link count. For example, an eight button keypad is 9 links but still only 1 device. A 2477d however is 2 links but 1 device. If your house had 50 eight button kpls, you'd have 450 links while a house with 50 dimmer switches would have 100. That's even before you get to scenes. Using the 2 houses described above, 1 scene with 20 kpls will show as 1 scene but the links would then be maxed out while 1 scene with 20 dimmers would still have space

Not necessarily. Link count is more complicated than a simple 1 to 1 comparison. Outside of kpls, most insteon devices do not use many links (1 to 2 depending on device) Since you're close to the PLM limit, it does help to use zwave devices since it's on a different board.

Zwave is not insteon so you are not adding to the PLM link count. That's why it has its own separate board. To eliminate the extra nodes, simply right click on them and delete. You'll also want to go to the zwave tabs and choose freeze additional nodes (something along those lines) once done.

That thing is pretty much worthless beyond being a paperweight. Its been discontinued for years and hasn't seen a firmware update in over 5 years. Definitely wouldn't work with the launcher. If you do not have a PLM hooked up to it, it will be in safe mode.

You shouldn't use a dimmer on non dimmable bulbs.

You could with a program. You would write it like you stated. I would add a delay to account for the device turning off however. If switch is turned off Then wait 2 seconds And turn switch on 10% You'll probably have to play around with the percentage to get it to fit your needs

What happens when you control the scene from the isy directly

Thats a sign of a poor network. I would still take Asbril's advice as it doesn't take much to knock a poor network down and it could potentially affect future automations you may attempt to do. What you are experiencing is akin to your wife yelling at you from the other side of the house. You may hear her and respond most times, but there may be some moments where you don't such as other things creating noise

Currently is not supported. While there's no guarantee a developer will take this on as a project, it'll help your chances if you could find out if they have an open API to use to develop against. If there is an open API, i would post that. The more you assist with providing the necessary documentation, the heater the chance someone will be in helping you

I think the last 2 posters are trolls.

Does it matter? Unless you can supply them it's a moot point.

Actually I do know for certain this is related. It's affecting more than just them. Do you know that it's not? With many companies struggling right now and all saying the same thing, what position are you in to say what a single company is doing? If they were simply trying to raise prices they would have already (not to say it won't ever happen). Even their new line is delayed due to the shortages. Going off your reasoning, if there wasn't a chip shortage wouldn't they have already released the new line to make money off it vs. holding back?

The same reason why you don't see many sales on a lot of electronic items....short supply. Unless something changes in regards to this silicon shortage, I doubt you'll see much bigger sales come black Friday either. Since you're ok with the TPlink, you could always buy the TPlink switches you want and then use keypads where you need them.

The steps for port forwarding varies when it comes to different mfg. and setups (ie:double Nat), the mfg. of your router should have that information on their support page or a Google search for port forwarding with you router model number should give you the necessary links (possible videos) to properly set up port forwarding. In regards to the isy, I would recommend using their portal service as it negates the need for port forwarding

Surprised with multiple break-ins in the neighborhood they didn't do more... especially with it on video. The Elk alarm has native integration with the isy and its the one i would recommend. DSC can be added via nodeservers but I don't know much about that one.

The pool deck floods switch is a response not a controller so that is part of it. Make sure the devices are configured in all controllers too, not just the scene. Simply remove the responder and add it back to the scene as a controller

I acknowledged that you updated to 5.3 in your original post which is why I asked if your UI matched. If it doesn't you will have issues such as what you're experiencing. Downloading something doesn't mean your UI matches. The instructions says to clear your Java cache which you did not say whether you did or not. A quick look at the help>about tab would show the information I'm asking for. Your pictures so not show the scene itself from the device column on the left hand side of the admin console.

The isy is not aware of an unplugged device so it will still attempt to do its job by wiring to that device. This week slow down both protocols since the isy is still controlling the whole system. The best way around this would be to either leave the device plugged in or disable removed devices do it will skip it. Upgrading to the pro version allowed you to disable writing to wireless devices

You never said if your UI matched your firmware. If they do not, this could be why your isy is behaving this way Check your scene itself. Controllers should be in red while responders are blue. If you want these lights to behave as if they were a multi-way switch then all should be controllers

In addition to what was already posted, I would verify your 6 button is not in non toggle on mode. If it is, the button will always stay on. If all devices are associated together and controlling each other the same exact way, I would add each one to a single scene (if it's not already) as a controller and making sure all are triggering each other the same. Since you've recently updated, make sure that your firmware and UI matches.