lilyoyo1

I've been using 5.0 in homes (where I went with isy) since 5.0.8 without any issues. Some of those systems are still on the older firmwares (I don't upgrade unless it's needed for something specific or I'm on location for something else) People come on forums when they need help not when everything is running perfectly which is why you'll see the forums filled with issues. It's just the nature of the beast. The good thing is all of those people received help so you have a point of reference before upgrading and should you run into issues. That also goes to show that many more didn't have problems....at least none that weren't expected due to previous research.

Being that your stuff is behind an equipment rack and inside an electrical cabinet it's no wonder zwave has been a pain. It's rf only so you probably have a weak signal to/from the isy. Your zwave firmware can also tell you what you have as 4.55 is for 300 and 6 something is for the 500 series chip. For the most part there is always a beta when it comes to the isy. Not every release (back in the 3.0 and 4.0) days is official. Sometimes releases are made (beta) just to update the device database. There are quite a few posts detailing others experienced with upgrading the isy and issues theyve come across. This can be found in on the beta subforum as well. The main thing is backup your isy and zwave board (zwave is a separate backup) and have a copy of your programs to reference just in case they need to be re-saved or edited (will be in yellow)

I'm assuming you DID NOT read the posts because it WAS answered. 1) The response said the 300 board has a blue light sticking out of the isy and the 500 does not. 2, 3, &4) has been answered multiple times on page 2 and 3.

Was it turned on

Your locks are not zwave plus so they don't have any of the benefits of plus which means they need to be close to the isy in order to add

It's only advantageous if you need what it offers. Outside of that you have nothing to gain by upgrading

They should be added to the isy as part of a scene. When setting up in the portal, add the scene itself but add it as a light and not a scene

You're welcome it's pretty simple. Make a back up of the zwave board (it's separate from the isy back up). Then restore it to the new one https://wiki.universal-devices.com/index.php?title=Z-Wave_500_Series_Beta The transfer I believe was to update the zwave board itself (if memory is correct)

Thats ok. I was in your shoes when zwave first came out. I was lucky enough to meet one of the developers of zwave many years ago at a trade show and pick his brain. Ive also done countless installs over the years which helped me learn more. There are some here who still know much more than I such as @simplextech. Im assuming its battery powered. If thats the case it doesnt matter since nothing gets routed through it. If its hardwired, anything thats using it for routing would not take advantage of plus (just because its closest doesnt mean its part of a device's route). With that said, a strong mesh still beats the extra range you get from plus. If you have a strong mesh, all of it is a moot point. The extra range may help someone who has minimal use for zwave and keep them from needing additional devices. Some of the device specific features such as NWI, additional battery life, etc. would still benefit however.

I actually just thought of something. You may be able to add that switch to alexa as a motion detector. Then set a routine that causes the outlet to turn on. I haven't tried it to be certain but that may work

In regards to NWI- none since you should have other pathways for the messages to get to the isy. In regards to plus features, you should be ok. The devices routing to that would default to whatever firmware that is but the system itself shouldn't see much of an impact overall

All devices need to be managed by the isy for the skill to work. Alexa isn't for device to device communication. It's when devices are handled via alexa itself. In order for insteon to control your wifi switch you'll either need to set up a network resource in your isy or (if one supports your plug) use a nodes ever for it.

All zwave plus certified devices must support NWI. Older devices may or may not (depending on firmware. Depending on setup it may not work.

I misunderstood you. Not that I've seen. However there may be something in the newer firmware. I haven't upgraded yet my backup isy yet so I don't know. The timeframe you purchased your devices is a good indicator (though far from absolute). If after 2017 it's possible that it's plus. Anything before most likely not. Plus is also generally written on the device itself If you know your devices there's a website that could tell you. https://products.z-wavealliance.org/regions/2/categories/5/products

That's a different stick posted. The $19 one came from silicon labs

System would still need to support zigbee and pass that certification as well. That could be firmware 7.0. lol

You're better off staying where you are if you have the 300 board. All devices must be plus to fully take advantage of plus. If you have the current 500 series card then upgrading is up to you. As stated before, the newest firmwares is specific to the new card so you would not take advantage of anything if you stay put on 5.0.16 as the 300 series board wouldn't take advantage of anything in the new firmware even if you could upgrade

300 board had a blue light in the back. 500 doesn't.

If it's new enough send it back and get a plus

It seems 5.1+ is about zwave+ certification. There is no point in going to it without the 500 series board as you don't get the benefits of + with the 300 series board anyway

Insteon does not work with homelink. There are ways with x10. What exactly do you have in mind as there may be other ways to accomplish what you're trying to do

Michel stated previously that polisy will use an external usb zwave stick (off the shelf) once the isy is ported over. Hopefully something like this since it's low cost. https://www.mouser.com/ProductDetail/Silicon-Labs/SLUSB001A?qs=u16ybLDytRbJsMfgk3EnSA%3D%3D&gclid=Cj0KCQjw7ZL6BRCmARIsAH6XFDJ-lvwzGLHIc0_pKnZut3Orun9s2sY1lYRA3HXn4iQB3mEpWTe3-_YaAs71EALw_wcB In regards to timeframe of the port itself happening. I would guess late next year or 2022 as far as official release. It looks like they're finalizing certification and then could start beta next year for port. Everything I say is an assumption based off UDI's history. Only they know their timeline and I can't see them saying exactly when

Not necessarily. You can go to 5.0.16C. If 5.2 starts taking full advantage of 500 series features, you'll want to upgrade anyway for that.

You should not use the button groupings as these settings reside locally on the kpl and the isy would not receive the proper updates when button are pressed. Its much better to configure your devices using scenes. This will accomplish the same thing while at the same time keeping the isy in sync For example A- Controller B,C,D- Responder Off B- Controller A,C,D Responder Off C- Controller A,B,D- Responder Off D- Controller A,B,C- Responder Off