lilyoyo1

Did you clear Java cache

Can you copy and paste it as I don't see it. This way it can be corrected so others are no confused as well by incorrect information. This is what I see

If you do not have zwave, then you need to update your ISY to 5.3.3 in order to set those. IF you have zwave devices then you need to go to 5.0.16c

https://wiki.universal-devices.com/index.php?title=ISY_Users:V5:ZWave:Advanced_User_Guide:NodeMenu

is your messaging going through your repeater? What are you using to repeat? Bring the lock close to the isy and do your testing. That will ensure that everything works properly. Then its easier to troubleshoot other issues.

Is it updating while you're testing? If its not then thats why you arent receiving notifications. Do you have any repeaters between your lock and ISY

Does the lock update in the ISY? Post your full program

Its not an error. You wrote your program wrong. The second line of your program shouldnt be included

Did you clear your entries in alexa from your mobilinc setup prior to switching over to the portal? If not this may be why you're getting duplicate entries. If you are specifying a device in a 3 way, then yes, you must specify the device that is attached to the light otherwise you would control your switches and not the light You do not have to unscrew the devices from the wall to find the load bearing switch. Turn your light on, and then air gap the switches. Whichever causes the light to go off is the load.

If everything works properly on all of your other echos, then it would not be a portal issue as the same would happen on those as well. It's either the unit itself or something on Amazon's end.

You're probably better off asking Amazon as it sounds like an issue with them. I suspect you have too many redundant skills going which may be confusing Alexa to the point it doesn't know which skill to trigger

It doesn't fit in with the Isy and Polisy. The Isy doesn't support Homekit and in regards to future support, I wouldn't count on it in the near future (if ever). There is a way you can integrate the Isy with Homekit but you would need to do the work to get things running.

The instructions and what you need comes in the box with the Isy. If you Google ISY wiki you'll find what you're looking for. The 2413s is out of stock and will be for quite some time

You can't! It requires 2413s

It probably will but that's not saying much. X10 will outlive them all. ?

I prefer zwave sensors over insteon but that's about it. Zwave sucks for lighting but what bothers me may be ok with you. Zwave direct communication is limited to 4 devices. However, with an isy scene, you can add any number of devices. The downside to this is every device will turn off 1 at a time unlike insteon (popcorn effect and my biggest gripe). There are other issues but as I said before, what bothers me may not bother you. You're showing 14 devices due to the extra nodes that zwave creates for your devices. That's normal. I wouldn't worry about it. I am surprised you were able to cover things with just 3 devices. Since you're planning on adding more, you'll be fine long term. The downside with a small number is that should anything change or interfere, you could potentially have issues

Theoretically you could have none or you could have a bunch. It all depends on how often your programs are triggering in regards to insteon. If the devices you're using with the second controller are triggered infrequently you will be ok. The more familiar you are with your systems the easier things are to manage and compare for should you have problems If your devices are constantly triggered somehow, then likelihood of a collision goes up. Since you say it's only a couple of devices, I doubt you'll have much issues. i say go for it. There's only 1 way to find out

Where did you read that at? In the very beginning of 5.3 (in bold red letters) it says you need the 500 board which is what you have

Something smells fishy

At this time, you'll have to set up port forwarding to access it https://forum.universal-devices.com/topic/30848-polisy-remote-access-options/

At this time polisy is in alpha testing for insteon only. No zwave yet so you are left with using the isy. You could wait until it supports zwave and then start building out your system. That way you won't have a leftover Isy once everything is complete.

None.of them are dual band so its possible the access point being dead (the light could just be out as well) is causing issues. However, if everything works from the console i doubt that's your issue. With everything being extremely old power line only devices, I expect some issues....especially if you're using led, CFL, or florescent lights. If the PLM was the culprit, I would expect your issues to be more widespread. The same with the access point. If that was the issue, I would expect more communication issues with devices on the opposite leg.

Long term Polisy would be an all in one box for Isy and polyglot. At some point in the near future support for Rpi will no longer be available. You will need to have Polisy to run local nodeservers

Does your regular programs run and devices update their status properly? If so, it's not your PLM. Do you have dual band devices or older power line only devices such as the 2476 devices

If he has zwave then it's definitely the 300 board