lilyoyo1

To add to what MrBill said, there was a zigbee module for the ISY (just in case you happened to see that). However, it was used solely for compatible smart meters....It is not compatible with zigbee HA which is what you would need.

I think the point everyone is trying to make is that other things will cause a switch to fail faster than burning through the memory so it's something that most here just aren't concerned with including myself. If that is a major concern, create multiple scenes with the devices as responders and set to your desired levels. Then you can simply create a program which triggers those scenes. No additional writes necessary

Yes, that is what you use when you migrate from 994 to eisy. There are about a dozen recent posts on how to migrate in addition to the wiki instructions. Just google eisy migration.

I say proprietary because its designed for UDI systems not other 3rd party systems like zooz

Proprietary, ZigBee, zwave, material/build quality, additional programming support

How do you normally write your programs in the isy? It's the same way

I havent noticed any delays in my programs once they're saved. All of mine ran instantly when testing. There are alot of users of the ELK nodeserver. The Elk nodeserver channel on here will give you a great chance to see what others are experiencing to know whether or not it's stable enough for your needs. I assume the charge for the new ELK nodeserver is due to it being a much more robust system. With the additional capabilities added, its pretty much a whole new system. Nodeservers and modules are the same thing just by a different name. UDI has commented that this is the path they're taking. At some point, Insteon and zwave will be nodeservers as well.

Id say give it a try and see. Everyone is looking for something different so experiencing both is probably the best thing. I can say, UD Mobile works with their newest capabilities so that may be a reason to switch. UD Mobile is also free so you could see how well it works for your needs without investing a large sum of money

Range wouldn't increase without 800 series devices

Sounds like the op left that little tidbit of information out......I cant name a single company that would do that much for someone for free.

What did you need help with

Simply change status to control. Anytime your door is open your then will run

@bpwwer, I know you're busy with everything else everyone throws at you so there is no rush on this request/inquiry. I was just wondering if it were possible to add Sub support to the ST-Nodeserver? Thank you

With you using the ISY, I believe that you must be on the latest firmware and have to query your devices since leviton uses hail vs sending status automatically like other modern zwave devices do.

It's not necessarily that they are too complex for people. UDIs concerns are probably different then epson's being that they cater to different situations. With udi, they want to ensure that the different systems which encompass polisy/eisy are able to talk to one another. Being that they are a much smaller company, I'm sure they want to limit support calls due to someone not configuring their certs properly and breaking their system in the process.

I think they are looking at things from a commercial standpoint vs individual user needs.

https://forum.universal-devices.com/topic/41362-important-new-google-home-action/

From the post The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure and enable features based on remote access. Polisy users may update their systems to use PG3x if they want access to the new features. PG3 will continue to get updates for the foreseeable future.

That would work for devices but not the plm itself. The only issue with that is there could be half links left over in devices which will carry over as well resulting in more work to fix things than simply coming in with a clean slate. While possible, the forum is also filled with horror stories from others who attempted this method

Best practice would be to reset everything and start fresh since you're moving from a different system

I doubt they're looking at a timeline to be able to give you one at this point since it's barely 6 months ago

I misunderstood you earlier in regards to being able to use it with the ISY as well if they were to update everything for that as well.

Why would they do that for the isy? A system they have repeatedly shown through their words and actions is dead and gone? Besides, your own words even lessens the chance of that nodeserver or not. The fact that they would be writing code within the firmware itself rather than simply updating a few repositories and calling it a day makes that more likely. With that said, Michel has made plenty of similar statements about being inside the eisy while referring to noderservers. It's unfortunate for isy users but reality is- it's dead.

Michel has mentioned many times that they're moving to a nodeserver set-up for everything. Besides that, why update something they have no plans of supporting