lilyoyo1

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)

What is your firmware and ui

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

Insteon signals are based on the zero crossing to avoid collisions since both go out at the same time. This comes into play due to its use of broadcast messaging since every device will pick up the signal and repeat it. For the most part; when things work, they work really well. When they dont, its a terrible idea from the end users perspective. Whether its rf only, powerline only, or both- each has their own pros and cons. Had they not done something to lessen the chance of collisons, your system would probably end up being more unstable and rife with issues. Tying the signal to the powerline gives them a consistent point at which to send communication for all devices instead of something less consistent. Wireless devices are controller only and uses only RF (until the signal hits a hardwired device and re-transmits the signal). In general, the idea is for the remote to control other devices locally (meaning within the same area) so only the rf signal comes into play. When a device is out of range, other dual band devices will pick up the signal at which point the zero crossing comes into play.

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.

The RF is still tied to the zero crossing in regards to the timing of the signal. If that is messed up at the source (in your case, its the plm), then you will have trouble. While being dual band does help, it helps more with communication beyond the sending device (once the signal goes out).

I would unplug everything that you can for testing purposes. Especially the UPS. The lamps shouldnt matter. However to find the culprit, its better to start with a clean circuit and then add things 1 at a time until you find the problem device.

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 dont use crtlhome so I cant speak on that. However, I dont think the issue is the plm if those are the only devices the isy is showing errors for. Most likely you have communication (noise) issues in the area. Is the PLM plugged into a surge protector or battery backup? What else is on the circuit that its plugged into?

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 your firmware and ui? are these the only devices having problems with communication?

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

If you're just going for a CO, can't you manually link them? I'm assuming it's the multiway switches that are your hold up

According to their emails they'll be out until late Dec. but should have alot coming in early next year. Outside of ebay, the 2477dh could also be a replacement for the 2477d

What's your firmware and UI

Sounds like it's better to wait until ISY is ported to Polisy and release with 700 series

It would help greatly if you told us the device you were using, along with firmware and UI

Outside of what I previously told you, no. If it's a ceiling light, you could call it that and and it to the room as ceiling. Then you would simply say turn off the ceiling or whatever you want