lilyoyo1

That's what we discussed 2 weeks ago when the thread started. Launching the admin console is the old/worse way of doing things

I've experienced this as well. Currently the only Nodeserver i have running on PG3 is the Harmony Nodeserver and Sonos Nodeserver on pg2

You've lost me and it sounds like you're just rambling. I'm going to bow out now as nothing about this makes any sense

Once again, you are seeing things via your lens- not the lens of others. Most do not understand networking enough to know the difference between routers and access points...unless they buy your typical google nest mesh system or something similar. Even then, its still a consumer based product which can have problems the larger the installation becomes. A few devices. No issue. Large number- yes it gets to be a problem. The internet is filled with bad reviews where you can read into the issue and tell its not the device but the network itself. Even in review articles, ive seen the reviewer talk about problems they had getting things working and it would be due to the network and not the device itself. Even with access points, the router is still involved as the signal passes through it. The router may not be whats talking directly to the device but its still in the pipeline. You are correct that dhcp works. But if one is trying to connect those devices to other systems (such as the isy) then yes a static address is needed. Imagine you have a house with 25 wifi switches and 30 wifi bulbs. What do you think happens after a power outtage when all of those devices are trying to connect at once? Someone's address will get changed at some point. The last thing anyone wants is to come home at 9pm turn on a light and it doesnt work due to an ip change. Now, if you're using the app and alexa alone, then yes, dhcp is enough since the assigned address is less of a concern. Who do you think this stuff is made for? While you may not think of hobbyists as the masses, the manufacturers do. Of course some companies such as tuya, homeseer, etc. are hobbyist+ focused, but for most, the hobbyist is the so called masses. This is why every device taughts how a hub isnt needed and connects directly to alexa and google. Its why these companies are pushing Matter (if it matters long term remains to be seen). Everything about their actions says mass use, not hobbyist+. Parlor trick or not, they are where the money is and who things are designed for. We live in their world and try to adapt their products to our use. Not the other way around.

If your devices all support network wide inclusion, then you would remove those furthest from the isy first and those closest last. When setting up again, you'd add those closest first and farthest last. For new installations, I add all devices to the ISY first, test, install, test, run heal (update neighbors) if necessary. Your repeater will not work with the ISY if its associated with your RING hub. It MUST be part of the network in order for it to be included in the path.

Half links are bad and should be avoided as much as possible. However, if managed properly, one can avoid many pitfalls

I would add devices using another ISY/PLM and link those together using that setup. That way, I can configure the ramp rate and light level with the system and what they do, do not impact the isy. It also allows me to save the configuration should I ever need to restore it. Should a customer decide to add programming at a later date, I simply add them to the ISY thats on site. Should ramp rate and stuff not matter, this can be done manually (I have done it manually) Ditto for situations such as storage closets. In those cases, I would use insteon sensors linked directly to the light so that the light turns on/off when the door opens or closes. No controller is necessary unless someone wants more functionality. Keep in mind, this is not the norm. My main goal is to keep things under 1 controller and everything part of the system. However, there are times when you have to think outside of the box to make stuff work. In general, you should not have to reload your system unless something goes wrong. With these situations being basic on/off control, im not as concerned about configuration as I would be with the system itself. Responder scenes are just that. A scene created and configured with everything as a responder. I'll then write a program that will turn the scene on from it. You do lose flexibility this way in that you can't dim the lights on or off from the controller but thats not my concern when its done in this manner. When you're trying to save links, every link you dont have is a link saved. A controller in a scene creates 2 links while a responder is 1. Take (2) 8 button kpls cross-linked with each other. Thats 32 links minimum vs 16. Now multiply that by any given number of other switches that you may have as part of that scene as controllers/responders.

There are ways to avoid link limits but it takes a lot of planning prior to the installation. Offloading to the isy is one way though it does tie you to the Isy as you've stated. This isn't too big of an issue since you're tied to the Isy anyway. In larger installs that I've used insteon with, I've linked switches together outside of the isy such as 3ways in hallways and areas that arent managed. With the Isy supporting zwave, I've skip using insteon outlets and used zwave outlets instead (unless I needed the dual control). I use zwave sensors as well. Setting up scenes with all responders and using programs for the controller saves countless links while giving you the benefits of scene use. In critical stuff, I always use Controller/responder scenes since it's paramount those work at all times. For the rest, I'm ok with the isy managing things

You're comparing having networking knowledge and enterprise equipment to the avg person who's using cable provided equipment or the cheapest router they can find. When I talk about things here, I tend to focus on what the avg person can do as they are the majority. There are people here who use a high number of wifi bulbs successfully but they understand networking and use multiple routers to manage them. For most, that would become a recipe for disaster. When I look at the knowledge I have about automation and integration, I feel like I'd be doing people a disservice if i came on here acting like less than optimal setups can be easily achieved and managed because I don't have issues (or leave out pertinent info pertaining to what it took to become successful). This is why I tell people to avoid wifi based devices (and limit them for myself). Who wants to make reservations for every device they want to use? I get paid to do so and still don't feel like sitting in front of the computer to do so. Then depending on home and network, having to add a second or third router to the mix..... You see where I'm going with this.

If you've read the posts to come to this conclusion, our answers are in those same posts. In short, think about all the issues people currently have with their current wireless devices and wifi networks! Now extrapolate that across potentially dozens of additional devices.

Read the instructions prior to upgrading. It'll tell you to clear your Java cache AND use the launcher that is on the SE page as the upgrade.

Matching UI and firmware are more important than you realize. Clear Java cache and use the launcher from the 5.3.4 page. The rest sounds like communication issues. However, I wouldn't try to tackle that until your UI and firmware match

Yes

See what I said above. You have to resave your programs

I'd return your zwave board and get a new one.

That's not the issue. Most likely, he upgraded his firmware and didn't read the instructions where it states that he'll possibly need to resave them.

Did you upgrade your zwave usb stick

Did you try to remove first? How many button presses on the devices?

What devices are you trying to add and what process are you using

Ring does not yet exist on polisy. Most likely you will have to redo your set up

No quality zwave replacements for either unit. While you can Google zwave keypad and fan switch, what's currently available fail miserably when compared to how insteon works

I'd try to upgrade to 4.9 since that's the latest release. There could be updates that caused things to stop

Firmware and UI of your isy

Purge and discover doesn't work?https://github.com/jimboca/udi-harmony-poly

Nodeservers are designed by different developers so what one chooses to do with theirs may not be the same way for another. I've experienced what bpwwer with my ecobee and harmony nodeservers so I get his point.