lilyoyo1

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.

It should do that on its own. If it's not then you're having communication issues

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.universal-devices.com/docs/production/zw.pdf&ved=2ahUKEwierI_kj8ztAhXRjFkKHY8nAxkQFjAGegQIExAB&usg=AOvVaw06Y-jDEW2pdc5k6MkNg-Qb

You will need to contact your devices mfg. This isn't the forum for that

Yes, that's the one. I like the feel of Eaton's plug much better(disappointed it doesn't contain beaming), but the ge works really well

Ge has zwave plus receptacles which also support beaming (which is needed for locks). Eaton also has a zwave plus outlet which is cheaper but does not support beaming. Leviton has a 700 series receptacles coming out but I don't know when as it's already passed it's initial release date (pushed back due to covid)

Make sure that you are using the isy launcher to access your Isy

I completely agree with that last statement. However, I'm not seeing anything that points to operator error. That's why I was looking at setup and timing. Those are the obvious points of failure that I can see

Delete one of the sensors from the program. What happens during testing then? Once you confirm the results, re-add and then delete the other one and test again.

Don't just install it. Make sure you read everything to avoid issues. The upgrade from 4 to 5 is alot different than normal.

I meant 5.0.16C

Why are you going to 5.0.15? At the very least, you should go to 5.0.06c. The links are on the very first page of whatever version you want. Read through everything that it requires and you will end up at the links

What is the timing set to on your motion sensor (before it sends another on command)? Also, are your sensors positioned so that both could potentially see the same motion close together?

If your firmware and UI do not match, it can cause issues with the isy. Since your app gets its information from the isy, it's important that both firmware and UI match. I just realized you said that you upgraded to 5.1. There were some issues with that firmware. If you do not have the zwave board (if you do it must be the 500 series board) you should upgrade to 5.3. if you have the old 300 series board, you'll want to use 5.0.16

Did you clear your Java cache after updating

Id let the self healing take care of that. You should be able to use Network wide inclusion since you have plus devices. Make sure that is checked as well

I've never seen a device disabled on its own by the isy but that doesn't mean it doesn't happen. I've noticed that sometimes programs have been changed so I would say it's possible (though improbable). Most likely it's inadvertent user error. As long as the ish was used to link 2 devices together, it is aware of the other link. You can factory reset a device and then restore it without issue. When it comes to battery operated devices, they need to be in linking mode during the restore process

What's your firmware and UI? Does the ISY see when you manually turn on the keypad? What happens when you run the "then" portion