lilyoyo1

You may want to read mine and @MrBillstatement for context. We didn't say anything needing to constantly manage the Isy itself. Our statements pertained to udi and changes that they make to their systems and operations. Babysitting the isy and keeping up with what's going on in the Isy world are 2 different things. You don't need to babysit your system when it's running well and you have no desire to add anything or make changes. However, while your system may stay the same; UDI is moving forward. Take work for example. You go in everyday and do the same thing. Do you not attend meetings and read emails to keep up with things that may change? If you skipped every meeting or never read your emails (outside of someone telling you), how would you know when policy changes or system upgrades happen? The same thing applies to UDI and automation in general. As the automation world changes, they have to keep up. Individuals demand new features and capabilities. If they don't provide customers move on. In short, the isy and subsequent systems are set and forget systems. No vigilance or maintenance needed. One can set, forget and never look at anything else again. But the rest of the world (and UDI) still moves on. When a person is ready to do something different, who does it fall on when they feel lost due to the multitude of changes?

Your switch may be an actual scene controller (not all zwave devices are scene controllers).

The same as for scenes. Red is for controllers only. Blue is for responders/controllers. Your sensor can only be a controller which is why it's red.

Generally with advanced products, it's on the consumer to keep up as things can change significantly in addition to the capabilities and flexibility it provides. Its easy to sight of everything that's going on causing one to be overwhelmed and frustrated. It's ok to wait for a finished product but even then, the constant changes that happens causes you to end up in an endless vicious cycle of learning and relearning. While UDI can have pages upon pages of tutorials and how to's, the shear amount of information can and will be overwhelming. This is why it's better to stay involved and on top of things. If that's not what you choose to do, you only have yourself to blame for feeling lost. So, what you're saying is that there is no way to connect my ISY994i to a polyglot server online any longer. Right? This is correct. The 994 is disco'd so no further development will be had with it. Once eisy is released, you'd be able to use that to connect to polyglot and access node servers And the only way to do so is by installing PG2 it on a Pi or Linux machine and going that route or buying the old Polisy (ha! I thought this would be the new device going forward. I was fooled) Polisy was a new device at the time for the future when it was initially released a little over 3 years ago. At that time, COVID wasn't a thing, the world wasn't upended in shortages that caused most things to be out of stock, Insteon was a thing, nor was inflation out of control. It was literally a completely different world in all facets of life. Just like virtually every other company, UDI had to pivot which they did. In the grand scheme of things, a 10+year life cycle of a product such as the 994 is a thing of the past. Sit on the sidelines long enough, eisy 2, 3, and 4 will be coming out. That's the name of the game. The great thing is; unless you want to take advantage of newer capabilities any system adds, your current system would continue to operate. And I assume that since UD isn't selling the Polisy any longer, there won't be any development. I'll wait till you guys get the new eisy. You'd be wrong in your assumption. Polisy and eisy will be developed in tandem going forward. The only thing left behind will be the 994 I feel it would be better to create something that doesn't require UDI to produce hardware for. Something that can run in docker or K8s or just on a Pi. I'm not understanding this. You complain about having to use an Rpi for polyglot but then say UDI should create software for users to run on an Rpi. Sure, UDI can do that. However, should you run into any issues, who will you turn to for help? By creating the hardware to run their system, UDI has a way to controlled medium to assist. If they leave it to end users, they'll end up with many more customers complaining about having to be able to get something up and running on their Rpi. This is amplified by the number of users that lack the technical skills to even do so. At the end of the day, they're in the business of making money not losing it. Having to help end users troubleshoot stuff or set things up with different systems is costly. The Wiki and forum don't have an easy way to find that this functionality is just gone unless you use a Pi. Sorry, without the knowledge you guys have for years, finding stuff that's still relevant on UDI isn't easy. I'll go the Pi route. Nothing is gone in regards to the path someone wants to take. Products are out of stock not abandoned. While polisy is no more, there is a new system on the horizon that's been talked about countless times. If one chooses not to be engaged with what's going on, they can't really complain about not knowing what's going on. It's like that for anything in life. This is no different. Sorry, I may sound frustrated because I am now. I love my ISY but it seems the documentation on where to go today isn't great. Don't let the bus run you over as you stumble in the road guys... The documentation is there. It just gets quickly covered up as new things come up. UDI could do better, but then again, a person would still need to dig through to find any single piece of news depending on how long it's been since they've checked on things.

Click on your controller (red) verify all devices that shows up are configured to operate the way you want them to. You can also delete the controller from the scene and re-add it. Doing so will automatically configure the device with the scene attributes.

Click on the controller in your scene. In this case the kpl (it should be red). Look at all of the devices that shows up and make sure that your switch is set to be off.

Sounds like you didn't update the controller too. Just the scene itself. You must set the parameters for the scene and controller

Have you verified that the device isnt set to be off in the scene

That's all it is

It's not telling anything. Depending on angle you see that in most of them.

Did you try to factory reset the device? Try bringing it closer to your polisy if it isn't close already

I thought Michel said the instructions were in the package

Technically so does insteon

Here we go again... You know much more than you realize

I think you meant to quote the op. I already know the level is more than 35 devices

I wouldn't believe marketing materials from a mfg about another

For me, a high rate of failure compared to others is a good indicator that the environment itself may be the issue. Since you've provided no details, we can't say for certain. While ge feels cheap, they generally last as long as other mfg.

I found this wiki page which details what to do. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide

It's not a problem for me. The Node server potentially could. However, I'm referring to the built in controls that the isy has already

I wish they would add an annual button to the Isy so it wouldn't take this amount of program. Just set the date range like normal and click. Then every year it triggers

That hasn't been updated since the matter board isn't out yet. Those with pre orders should receive there's in the next few weeks. At that point, instructions will probably be updated for it. I suspect it'll be the same as from the 300 to 500 board. Backup and restore

What are you talking about? There's no subscription to use the isy. Take the time to learn your system (especially if installing for others) and you'll know exactly what you're paying for. The ONLY subscription that you would pay for with UDI is the portal which gives you remote access to your Isy in addition to allowing you to connect ifttt, Google and Alexa. If you do not need any of those, then you do not need a portal subscription.

The isy994 is discontinued so there wouldn't be updates. Reality is; it's a 10+ years old controller and support for it has ended (outside of security updates)...ditto for the PG2 version that you're running. You're complaining about a free unsupported product that's been discontinued in regards to rpi. The forums are a great place for support. The fact that you haven't posted about having issues or seeking help on here in 2 years is all on you nor can it be as difficult as you say....after all you found the time for your post but not ask basic questions. Direct support takes a couple of quick steps. I just signed up for a new account and it took less than a minute. If it's that hard then how important is it to you to receive executional care? Those steps are there to enhance your experience to help you....but they can't do that if you're not willing to help yourself. I've used every update since 5.xxx came out with minimum issues. Over time some stuff was broken due to bugs but subsequently fixed. In regards to update notifications, one just has to read. There's a notify via email button on the current release page which will email you anytime there's an update. No one is here to convince you to buy anything. Buy it because you want it and the ecosystem. If how they operate is not to your standards, then there are other systems out there...

They do. That's why it was on presale before eisy. It can also work with eisy.

Stay with what you have. Insteon will still work