lilyoyo1

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

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?

Smart move. It's not. I put half my stuff on my polisy. The things on the Isy work perfectly. Wrong devices get triggered on polisy, things turn on when they aren't supposed to, long delays etc. No such issues with Isy stuff.

I'd have to agree with you on this one. I've had more issues with devices i run on polisy than ive ever had with the Isy (as well as devices still on my Isy). Things will get better over time though since the software is still alpha.

I see that you're posting in the kasa sub-forum so I'm assuming you're using kasa devices. What devices are you having issues with? Is this on polisy or isy994? Firmware and UI?

That was the last discount code available. If that's not working then there aren't any available.

I'd take their advice since they did make the system. They would know best how to manage it. You can't brick the system by factory resetting. Factory resetting does just what it says....Puts it in the state it was in when it left the factory The few systems I've taken over, I've factory reset and started with a clean slate. It takes more time to figure out why someone did certain things than to simply program it from the start with your own methods. This is especially important with you being new with this. By starting clean and programming it yourself, you'll learn more about the system and how to manage it. Google isy wiki and Isy cookbook. Both are great resources to help you get started.

The more I see things like this, the more i like @asbril's idea to meet in LA with @Michel Kohanim/UDI to discuss different aspects of the ISY/Polisy future. I think it would be helpful to have a round table discussion with the different types of groups here to help lessen confusion and set on some common themes and ideals. From those helping UDI with coding, to vested developers such as @simplextech and @JimboAutomates, prosumers such as @MrBill, @Teken, and so called non technical people like @asbril(who isn't kidding anyone). I think it really would do long term good in regards to the next chapter of the ISY before we get so far ahead, its too much to clean up. With that said, from my understanding (I could be wrong), The connection status would stem from Link A. However, the Weatherflow (just using it as an example) may not actually be talking to weatherflow's servers. In this case, you'd see the connection though you arent receiving updates. To me, its similar to zwave. If you turn on a door sensor and then remove the battery, the isy will show that its on even though it no longer talking to it. In the eyes of the ISY, the device is connected though not working

Just to add addition information/confirmation- Michel has stated the isy994 will not be receiving any more updates to it's zwave board. 500 series is as high as it'll go. 800 series was just released by the alliance but it'll probably be 3-5 years before we see devices since 700 is just started to become readily available.aybe some of the holdouts will release 800 series but i doubt it. I do see the 994 receiving firmware updates for the foreseeable future however since they plan on selling it for a while. At the pace UDI does things, i can see this lasting the next few years. I know they mentioned working on moving away from Java. I'd be surprised if the 994 received that as it would be more expedient and less costly to focus on the future vs the past. All this is my assumption and thoughts except for the 500 board. I hope no one takes it as fact since I do not know myself

That's my plan with my test polisy. I just haven't gotten around to doing it.

My initial install was all new. I updated the firmware on the stick then added my devices. There's been another firmware release since then which i upgraded to the other day. My devices were still there and working after my upgrade. Having a back up is good practice. I was curious to see what would happen if i didn't do one. Now we have an answer for both scenarios

I didn't back mine up when I upgraded this last time and nothing happened. It worked like normal

I'm on the latest and there hasn't been any issues