lilyoyo1

Your network does matter in regards to where you plug it in. If it's a different network access can be lost (like it was).That has nothing to do with insteon,x10, nor zwave. If you go with zwave, make sure you purchase multiples initially as zwave requires a strong foundation to work properly

No. Unfortunately zwave devices all have different ways of accomplishing this unlike instrument.

You need to upgrade to 5.0.16c Clear your Java cache before and after you upgrade

Firmware and UI? If you arent on the latest firmware, most likely it wont work. I would recommend using at least 5.0.16c then trying. This is especially true if you are still on the 4.0 branch.

That's been discontinued for years. It wouldn't surprise me if the 2 were no longer compatible due to updates to the elk.

This is (adding zwave devices) complicated but you are right. If all devices in a system supports network wide inclusion, you should be able to add devices from their location (assuming all devices are within range). From my experience, this isn't perfect (of course). I still add devices prior to installation in order of closest to farthest. The same with locks. I'll add those after, I've added, devices that I hope they will talk to.

This firmware makes using Yale locks even worse than 5.3. which isnt saying much when compared to 5.0.16. Even after removing the locks and re-adding, there is zero communication. The ISY shows the repeaters connecting to it but no communication at all when it comes to the isy actually seeing the locks.

In addition to what MrBill stated, I use a longer period between messages to lessen the chance of an "on" signal being sent. While the motion may trigger upon movement no message gets sent. This allows the motion sensor to see you but not cause any programs to respond to the motion

I would increase the time in the motion sensor itself for when it seems an on command to lessen the likelihood of an event being sent between motion triggers. One or 2 minutes should be sufficient. Once done you can use MrBill's example above, shortening the duration to suite your needs

You'll probably regret things. I tried that once and quickly realized it took me more time that way than had i done things properly from the start. One thing about systems such as the Isy is that shortcuts usually hurt more than they help. When you delete a zwave device, you're only deleting the node from the console. The information is still retained by the board. To truly remove something, you have to do an exclude. If I were you, I'd factory reset the zwave board and isy for a fresh start. You can always copy your programs (i prefer pictures) somewhere to use as a cheat sheet

How many devices do you have

You'll want to update to 5.0.16c. that's the latest and must stable you'll be able to use

I would recommend always using the link that comes on the page with the firmware that you are downloading. That ensures you have the latest links.

Firmware and ui of your isy? If you're not on 5.0.13 (at least), the ish doesn't not support multi channel devices so that could potentially be why.

Submit a ticket to udi

There's no help because the 99 is obsolete. You must use the launcher on the 5.3 firmware page

I think it's more of people trying to use insteon for security vs insteon trying to move into security. If you have zwave, there's an outdoor motion sensor that can be integrated into a flood light https://www.amazon.com/dp/B07KP4T3MS/ref=cm_sw_r_cp_apa_fabc_Wbb3FbHWHNNDJ?_encoding=UTF8&psc=1

You're on the Isy forums....people use the Isy for zwave.

As with all insteon scenes, in order to keep everything synced properly, you should control the scene itself. If your scene is only 1 device then you're fine. However, if it's multiple devices, the other devices will not turn on/off if you control the individual devices instead of the scene-which controls all

Probably wasn't the plm then. Id submit a ticket with udi

There will always be phantom nodes with zwave due to underlying code and how the isy handles those. Only the ones in the manual for the device will do something. You can delete the ones you don't need. Some may be for different classes that can be used by setting parameters. You'll want to check with the mfg. about that

The information on how to replace the plm is in the wiki https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29

The most you can do it put the elk command at the end and extend the wait between your last command and the elk command

I would read the upgrade instructions for 5.3.1 prior to upgrading and make a backup of your system prior to upgrading. You can also read about zwave in the link below as well as the wiki https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/

You'd be better served with fixing your comms vs trying to run a query to keep track of your device status. A query is a bandaid for something that should be fixed.