lilyoyo1

It's a dealer installed automation system. https://www.control4.com/solutions/whole-home. I wanted to use Ra3 when we moved but UDI didn't support RA3 by the time we moved. Thanks to @bpwwer the caseta nodeserver now works with Ra3 switches and dimmers. The main load of the keypad shows up but no control of the other buttons yet. Anyone wanting to at least use Ra3 switches @DAlter01can at least have those managed by their polisy/eisy now.

I'm not as wary of ecobee being cloud since ecobee as company has proven to be open and friendly to integrators with their open API and no fees to use it. They may have fees for their smarthome garden (don't use it so I don't know), but none for API access and basic thermostat use. In addition, they have shown a willingness for long term support for their line of thermostats. For example, my sister has my original first Gen ecobee 3 from 2014. It still works manually, via the app, and voice. Venstar can even change it's business model to where it's no longer local or accessible. I doubt they will but it is possible. As I get older, the more I value ease of use which the ecobee has. The app easily works at home or away without any additional configuration required. It can be added to multiple systems for multiple points of control without issue. For example, I can connect all 3 of mine to my control 4 system, Ra3 app, polisy, Alexa, Google home, or use standalone. All major automation platforms support it so regardless of path I take, I'm good. The best thing is that it works wonderfully out of the box without any control systems. The only thing I do with mine is shut it off if a door or window within that zone is left open to long though everyone's use case will be different.

Something must have corrupted the add as Zwave devices will only work with 1 controller. I would remove from the system, delete the additional devices and follow the recommendations from above when re-adding.

When the eisy was first released udi stated polisy support would last at least 3 years. We're starting year 2 now. It makes sense from a marketing and business standpoint to stay pushing people to the new system now vs waiting until the last minute.

@bpwwer, I just wanted to let you know that the nodeserver doesn't work with Ra3. Once the IP address was set and button pushed, the notice disappeared but no nodes showed up. I clicked discover but nothing shows up either. This is on Polisy 5.7.1 and PG3x 3.2.17. I've downloaded the log if you want me to send it to you.

Not really. If it’s that important, you can probably pick up an extra 994 for cheap on eBay and connect it to that to see if it works

C4 is Control 4. I switched over to Radio Ra3 switches. I now have a system that I need to connect to my polisy to see if it can connect using the caseta nodeserver. Just havent had time to sit down and try.

In my opinion yes for various reasons (Looks mainly). I love mine. We use the ecobee premium but it works with all versions. I only chose the premium due to the looks. While it has features the others do not, I don't really use them and wouldn't say it's worth paying extra for. While I no longer use the nodeserver since I use C4 now, it is actively being developed and worked really well when I did use it.

You wouldn't be able to unless someone adds support to the nodeserver. You're next best step would be to use a supported device like the ecobee

I dont believe Matter support has been officially released with the EISY yet.

This was many of ours concern from the start and why I have no interest in Matter. At the end of the day, they all have too much to lose by truly working together. This is why is stick to single source....I know everything will work the way I want together without any compatibility issues

I haven't been able to get it to work with the newer LG OLED series TV's. It works with my old B6 that's on the patio but not with my G1, C2, or G3.

No there is not. It automatically goes to the next number.

Zwave doesn't use the plm. Did you follow the instructions in the wiki in regards to removing the device first then adding? Is your sensor close to the zwave dongle?

There's no way to override what happens when a switch is manually controlled. Javi's idea is the closest you can get. The double tap is built into the code. You can have the light immediately turn off if turned fast on. The only way to accomplish what you want is to use an embedded module connected to the lights or what bulbs with the switch controlling that.

I know the st-sonos updates whether you control hings via the app or polisy. I used the free one years ago with my isy and it worked as well. There may be a bug or an issue with the install.

These are all questions you'd need to ask udi directly by submitting a ticket. With this being a peer to peer forum, we wouldn't have the answers you're looking for.

While Zigbee support is available for some devices, I do not believe they've released full Matter support at this time.

No it does not.

I have the hue floor lamp. When I used it with my polish, I had it working via network resources. Never used it with the plug in so I can't confirm that route. Just letting you know that there are alternatives to controlling it if it doesn't work with the nodeserver

In short no. Everything 5.0 brings will make things more complex, especially at this point since you'd need to upgrade your controller to take full advantage of the capabilities

I don't know if it works because I don't have x10 but I don't see why not as others have said. I know the x10 module is no longer available which would allow you to name your x10 devices in the admin tree like you could with Insteon. Since you already have a backup, it doesn't hurt to try it.

Ra3 is a basic control system. Outside of simple timers, there isn't any logic. I use mine with Control 4. The next house I do with ra 3, I do plan on seeing if the lutron nodeserver works with it out of curiosity

Yes. The easiest way to set a scene is to add responders first, configure them, then add the controllers. The controllers will auto update

I don't use the nodeserver anymore but that was not possible when I did. You may not want to set up Alexa if you dont want to use it. Otherwise you'll need to mute it through the app.