lilyoyo1

Just to confirm, you're using the DB9 port and not the Ethernet port correct? I ask because the 994 doesn't have a DB9 port nor does polisy have 2 DB9 ports

If you had the PLM plugged into Polisy- and powered prior to peeing up Polisy, there may be something wrong with your polisy. You'll want to submit a ticket

A screen shot would help. They'll do what I'm doing and potentially miss something that could help others. This is what I see when I click the link:

All the links show up in blue for me on my phone, tablet, and computer. Are you seeing something different on your end? It may help them fix things if you post a screen shot of what you're fixing

I don't see it being shut down per se vs natural obsolescence. Those with current Rpi installs would still be able to use their stuff until API updates break their installs since those node servers wouldn't receive updates.

I'm with you on this one. Never saw a need to worry about the LEDs when I used them. Especially enough to need to turn them on and off via a program. Insteon probably felt the same way which is probably why it's not an exposed parameter like that

Does both your UI and firmware match?

Pregunta en el forum de insteon. Esto es solo por universal devices. O llama al suporte de insteon

He's not talking about the insteon signal being lost. He's troubleshooting why he's being flooded with X10 commands. With him killing power to the garage, the likelihood of his GDO emitting X10 commands with no power to it, is zero. @jim_ at this point, I'd factory reset each insteon switch and use restore & and write updates to get them reconnected to the Isy. This way you clear out anything that may be in them. If it starts happening again, you could pull the set button on devices one room at a time (at night) to see which area is causing the problem (if its a device). Once you narrow down the room, you can do it individually at the device.

That's because your program reevaluates the if during the wait. When you lock the door, it's no longer unlocked so the program stops running and the light stays on. I typically separate my off programs from my on program so that i have additional flexibility but you can accomplish your task with 1 program. If time is x and (door is unlocked and door is not locked) Then do what you said or else Wait 20sec turn off light

I'd contact the manufacturer at this point as it seems there's something with the devices themselves outside of the controllers

Disconnect the isy! Does it happen? Since it happens on all of them, is remove, manually factory reset and verify behavior prior to adding to the isy.

For security purposes, I don't open links from new users so i didn't look at your logs. I also don't use this device so i can't say how it's behavior should be. With that said, I do ask- is this behavior on all devices? If so, maybe there's a parameter that needs to be changed. You can go to the mfg. website to get the full manual to check. Another thing you could do is unplug the Isy and your HA installation together and control the device to see if the behavior continues. If it does, most likely, there's been a command input into the device to force the light on which would be a parameter. If it stops then it's probably a program. Also, verify that your firmware and UI matches. If you have the latest 500 series chip (no light in the back of Isy, then make sure you're on 5.3.4. if you see an led light in the back of your Isy, then make sure you're on 5.0.16c and clear your Java cache to make sure you're on the latest firmware to lessen the chance of any bugs. Verify your UI matches your firmware.

I've never had this happen myself so i would submit a ticket. What's your firmware

V2 is deprecated so there probably hasn't been any updates. V3 is it's replacement. Additional Note: PG2 packages will update if you run update from it's webpage. V3 requires Sudo at this time as listed above

I've upgraded all at separate times without regard to any specific order without any issues. They are all separate so i don't think it matters. Besides that, all of them get updates at different times so I doubt they are in any specific order

What port do you have the Ethernet cable plugged into? Does it show in your router? Are you using the isy launcher

Nothing they can do to fix it. It's no different from us as people not understanding what someone says for various reasons. You could potentially try to make your spokens clearer or easier to understand.

That's an Alexa issue. All of them do that unfortunately. You can look to see what Alexa thought she heard by going into the app.

I've experienced the same thing. In some cases I simply resaved the program (click a line hit update & save), in others I had to rebuild it because the program had different conditions (confirmed when I uploaded my backup). In 10 years and 100+ installs, I've never had folder conditions not update properly unless there were communication issues (including firmware upgrades and reboots) so i doubt that's your issue. I'd follow what whitehambone said and re-save your programs and verify what's written. ***You added additional information in between me being able to finish my post. One thing I'd verify is if other programs are running at the same time. It may be that the system isnt queuing to run properly or interrupting the program so your count becomes off

I'd add not yet though. While it works well, it's still not without issues....unless you don't mind troubleshooting

See MrBills post from earlier. It does not work. https://forum.universal-devices.com/topic/35428-programs-not-responding/?do=findComment&comment=332535

This is all done by the controller itself and it's something UDI has no control over. Siliconlabs designed this into the chip. It works for node servers because those are undefined. There's no protocol requirements that UDI must follow. UDI can do what they want with it https://www.google.com/url?sa=t&source=web&rct=j&url=https://cn.silabs.com/documents/public/user-guides/INS10244-Z-Wave-Node-Type-Overview-Network-Installation-Guide.pdf&ved=2ahUKEwiy58WexO32AhWDlWoFHXgmCQMQFnoECEgQAQ&usg=AOvVaw1R8d1pxdOmaYU545DVS4Rv

That's a known limitation of zwave and not something they can change since it's built into the zwave code itself

It's always been there