lilyoyo1

I wouldn't recommend putting that load on a dimmer switch. It's not like you're going slightly over the rating but effectively doubling what it's rated for (even worse if next to another switch). Overloading a dimmer not only heats it up to the touch but could be a potential fire hazard

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.

The serial version hasn't been discontinued for years which is why. Besides, both serial and USB versions are now out of stock so it doesn't matter. Also, UDI already has a new controller out which supports the USB version called Polisy.

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?

It works great for the market it was designed for. The market is geared towards those who want simplicity and app control. Using it outside of that does make it seem limiting but only because it's not designed for that purpose

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

I have a few of those. I swapped back out to the PLM. During testing, had nothing but problems. Polisy was in the same location trying to talk to the same devices. Tried 2 different USB sticks. Communication was much slower and many times polisy wouldn't see the button presses. Swap to the PLM, the issues were gone. This was before the latest updates so it could have changed

And yet here you are jumping into the fray as if that changes anything. You could've very easily not said anything... Yet you did and not once did you help him

Actually i was willing to help and I did. If you look back at all the posts,l (which we know you won't) I left many comments and links trying to help. I didn't say anything until he asked about what password to use for ssh which was in one of the links that was left for him. Still doesn't change what I said. Outside of bugs out hardware issues, if people took the time to educate themselves and prooerly prepare, many support issues could be eliminated

That sucks. Still a good find anyway

Good find. Cheap way for someone to get a new cable as well if they don't have their original one

The reading isn't about the hardware. It's about preparation.

2 days later the same question will be asked right above that question

If memory serves correct you'd use smoke or CO2. They'll go off based on the specific condition. The crazy part about it is I had it when they first came out in my old place in California. I set off the smoke. The sensor trigger my program to run a second or 2 before the detector actually started sounding

Mine showed blank as well until I triggered them. All of mine came back though at least.

Control (switched) on means the device is physically turned on. Status is referring to status itself. Great if you use voice or apps to turn stuff on/off

Im not a fan of the USB stick's performance. It was much slower than the plm and many times I would need to press buttons multiple times to get Polisy to see the changes. Swap over to the Plm with the same exact devices and all of those issues have disappeared. Swap to another USB stick that I had and the same stuff started happening again. This was prior to the latest updates so things couldve potentially changed.