lilyoyo1

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

Most likely there's a program with a control condition causing this. Go to your programs, right click on the my programs tab, and choose find/replace. Pick the device you're having problems with. It'll show you all the programs that device is part of. You can also factory reset the device and then test it by turning on/off. If it works properly, re-add to isy by right clicking on device and choosing restore. If it happens once you do that then that confirms a program issue

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

What kind of lights are they controlling? How close is the nearest dual band device

It's always been there

Keep in mind, if your numbers are correct, you're still going beyond what the dimmer can handle. If your relay fused shut due to the current, most likely you'll be waisting a precious dimmer by swapping it in only for it to fail too while potentially having a fire hazard in waiting.

I'm glad it's working for you. Mine was a clean install not ported over. Subsequent restore devices did not change anything. The software is in alpha so I'm certain things will get better which is why I added I haven't tested with the latest updates as things could've changed. I tried 2 different USB sticks just in case 1 was bad and continued to have the same issues. Even adding new devices was problematic as I would have to attempt it multiple times to get some devices added. The amount of restores that was needed and lack of confidence in it working is why I abandoned the USB for now. I'll end up testing it again in the future but for now I'm focused on a setup that works for Polisy testing

There is absolutely no difference in insteon super amongst isy994 versions.. I've never seen a message from the isy. Post a screen shot of the exact message and error code.

Personally i don't think BT or wifi is needed for Polisy but to each their own. I tried the insteon USB stick in my test polisy and it sucked. They've had updates to polisy since then so it may be better but the experience was bad enough that I've never went back to test again. For some details about my experience, I used my polisy with the USB stick and 2413s. Same location with the same devices. 2413s had zero hiccups. Instantaneous along with 100% communication rate. The USB was noticeably slower to/from polisy. Most times, I'd have to hit a button or switch a couple of times before polisy would see the event. I'd get a red blinking light from failed communication when this happened which let me know the signal wasn't getting through. Your experience could be different however. Like i said, I haven't used it since the latest updates so things may be better. I haven't heard anyonensay they use aeotech's stick. Since you already have it, I'd say try it. If it works great, if it doesn't, you know where you can get another one at least.

Did you try updating the stick prior to using it

What dongle are you using? Did you check zwave in the admin console and reboot? What firmware is your polisy running

When scene control 2 is used, what options does command give you?

A 600w max dimmer is not fine to control a load that's more than double it's rating. Besides potentially damaging the device itself, he's at risk of starting a fire due to the heat.