DennisC

Absolutely, I have been using DHCP router reservations for years to lock down all of my devices IP addresses. This way I always know what the IP address for each device is and there are no mistakes resuting in duplicate IP addresses. The best part is it is all assigned and managed from one device, no need to go to each device to check, update, or change.

When you are in the production store, there is a button that says "more info". Pressing that button will take you to the instructions. Here is a link: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md There is also a log for open issues here: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues As for F keys, there is some functionality, but there is an open issues that you can read about here: If you are having an issue, use ElkRP rule to set an output when the F key is pressed, then in Polisy, have a program run when the output turns on/off.

I did this while the node server was being developed as a tester. While the M1XEP can only handle one connection at a time, I don't think the Elk Module on ISY or the Elk Node Server is always actively connected. Think of it this way, if you are running either the Elk Module or the node server, you can still connect thru ElkRP. When you make that connection, the module or the node server stops updating until you disconnect ELKRP.

That's what I am hoping for. Thanks for your input.

I am aware that I can have them both on the same controller. Since associations work without involvement of the controller, I am not sure if it is relevant to my question about expanding the Zwave mesh. Maybe I am not making my question clear, so let me try again. My question is regarding the Zwave mesh and if S0 and S2 will all be part of the same mesh and be considered "neighbors" to each other? Or, would you need to build out two different Zwave meshes by adding sufficient devices for each security protocol?

I understand the ability to mix and match Zwave 300, 500, and 700 devices, just not sure if they can mesh together if some are S0 and some are S2, or does one protocol skip the other? Also wondering if UD's specific implementation can impact functionality.

With UD's support of ZMatter on both Polisy and eisy along with their implementation of S2 protocol, I was wondering if you have a Zwave system with both S0 & S2 device, would they share the same mesh network? Or would there be one mesh network for S0 devices and one for S2 devices?

You can also use Tasker on an Android phone and there are directions for doing it in the Wiki. I have been using it for many years and it has been rock solid. You can also setup a task to detect wifi connection and disconnect as a back up or for other purposes.

@bpwwer Is there a post/list somewhere, or a way for us to tell which Node Servers update this node?

I am wondering if your IP address may have been reset if you were not using DHCP? Can you connect to your router and find the ISY IP address? Once you know what it is you can manually enter it in the finder. If you are not sure how to proceed, maybe you should open a support ticket with UD.

Understood Thank You!

I am aware of past comments and indicated as much in my question. I am also aware that he is in the best possible position to offer some forward thinking insights to the possibilities, without revealing details and promises. That is why I indicated "somewhat speculative". It doesn't hurt to ask.........

@Michel Kohanim You may have made comments about this before but now that it's decision time, would you please comment on future plans and what eisy might be able to do that Polisy would not be able to do between now and 2026? I realize this is somewhat speculative, but it would help clarify our decision on if we should jump up to eisy now. Thank you.

Try the 2 links posted by @Geddyabove. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Migrating_from_994_to_Polisy https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide

I think the space issue is referring to the amount of nodes the ISY can have, not the SD card. You should exclude/include again with the lock 1-2 feet away from ISY. Once it is added and relocated, you can update neighbors.

See @Bumbershoot's post. Once you have upgrade packages in IoP, you shouldn't be using ssh to upgrade. It causes issues like you are experiencing due to the order of the packages upgrading. If this is your issue, you may need to wait for UD's help.

Maybe update packages on Polisy from the configuration tab? Be sure to wait 20-30 minutes before trying to login.

I always found programing in the ISY much easier then in the Elk. However, if you have a need for this, one workaround would be to have the Elk rule turn on an output and in reaction to the output turning on, ISY would run a scene.

If your Zwave devices are giving you a problem when you upgrade ISY firmware, then everything is not fine with your system. There should be no issue when upgrading ISY firmware. Switching to another device was when upgrading the Zwave firmware which only happened a few times and will not happen again for the ISY.

Sounds like you should be speaking with the developer of Mobilinc about adding support for UD's new products and their lack of updates.

Polisy is not currently available due to supply chain issues. UD will be coming out with a new Matter compatible unit to reace Polisy. It was scheduled to be available before the end of the month.

Sorry to but in on this, but I am wondering what version of UD Mobile you are on? I was experiencing random disconnects on v0.173 and the issue was corrected in v0.174.

FYI, I have had the latest update running for over 24 hours now. Other than the portal outage from this afternoon, I haven't seen any errors in UD Mobile.

One other suggestion is that it is recommended to do an exclude before an include with zwave devices, even new devices.

Thanks for taking care of the issue so quickly and for the explanation of what was happening. Very much appreciated!