lilyoyo1

It's the same exact board so I would think so.

Even with that, it'll still be your fault with the way people act on here sometimes

That doesn't necessarily work for adding devices. All must support Network wide inclusion. The op is better off bring it close to the isy to add, moving it to its final location and then choosing update neighbors

The ISY Cookbook is also a great resource for learning how to program. Programming starts around page 160

Post your program and we'll help you fix it.

The majors support it but its extremely buggy. UDI has stated their planned support but im sure they'll wait until the kinks have been worked out within the standard itself. Being that they are a much smaller company, they can't afford to support a buggy protocol that they cannot fix.

You'll generally find device specific information in the full manual of the device your using since different mfg. will have different requirements.

Not yet. UDI will announce when it's ready. From what little I've seen, matter is far off from what was promised so it may be a while

Yes. It's no different than linking any other set of lights

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.