DennisC

I took a slightly different approach with my 3D dongle holder. It needs some tweaking, as I am still learning how the drawing program works. I wanted something that was enclosed, so there was no chance of the dongle coming free. I added a cutout at the bottom for a USB extension cable connector and for good measure I included a script on the front for additional air circulation.

No issues now.

If you need anything, I will be available in about a hour.

Yes, it's still happening on my remote Polisy, which I believe is on v5.4. I haven't been there in awhile to upgrade.

Yes, it's still happening on my remote Polisy, which I believe is on v5.4. I haven't been there in awhile to upgrade.

Having the same issue. Flaging @Javi

I'm seeing the same problem tonight. FYI, @Javi

Try going thru the troubleshooting steps here: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cannot_Communicate_with_ISY_Portal and here: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored and here: https://wiki.universal-devices.com/index.php?title=Main_Page#admin.jnlp_does_not_start_the_Admin_Console

I would suspect the PLM is on the way out.....

Polisy came out 3 years ago and there is a commitment from UD to continue to develop and support it until at least 2026. The reason for moving to eisy was the availability of components used in Polisy were either no longer available or extremely long lead times. Everyone needs to make there own choice about what is right for them.

Here is the post I mentioned:

If your eisy version is 5.4.5, it needs to be upgraded first. Run the package upgrade button on the configuration page. Be patient, as it may take awhile to fully upgrade. If the button doesn't upgrade for you there are several posts describing a command to issue by ssh into eisy to start the upgrade process.

It is in the instructions starting at step 4: Migrating from 994/Polisy to eisy Note Z-Wave nodes are not automatically migrated: Note Z-Wave migration can only be done from 994/500 Series board Make sure the ISY994 is already upgraded to 5.3.4, The eisy OS should be at level 13.1 or greater. Just in case - Note the IP address of the ISY994 and the eisy. Backup your 994's Z-Wave dongle (Admin Console | Z-Wave | Utilities | Backup | Full) Backup your 994 (Admin Console | File| Backup ISY). Note where you placed the backup of the ISY994 it will be needed in step 7. Plugin the PLM to your eisy Restore the backup of the ISY994 on the eisy (Admin Console | Help | Restore ISY) from the location saved in step 2 Log back in to IoX and make sure INSTEON Support is enabled (default username/pwd = admin/admin) If this is a new PLM, Restore the PLM If you have Z-Wave Make sure Z-Wave Support is enabled Reconfigure any software utilizing the ISY994 to point to the IoP (From Step 4), restart the other software, if necessary. If you have ISY Portal on your 994, follow these instructions to migrate your account, license, and Alexa/Google Home settings This will also migrate all node server licenses from your Polisy to eisy If you have Network Resources, please make sure you open and save each and every one individually Make a backup of your newly configured IoX.

You should take a look at these steps if you haven't already: Can't Find eisy First and foremost, all VPN software block discovery of eisy on your network. As such, if you have a VPN software running, please turn it off. If you have a modern router, eisy advertises itself as eisy.local on your network. As such, and in most cases, you should be able to find eisy at https://eisy.local:8443/desc. What you need to do is: In IoX Launcher, click on the Add button Enter https://eisy.local:8443/desc into the dialog Click on the OK button If you are still having a hard time finding your eisy, it's best to check your router's DHCP client list and look for a device that has the same MAC address as the one the label at the bottom of your eisy. eisy's MAC address starts with 00:21:b9. Once you find the IP address for eisy, in this example, 192.168.1.122, then In IoX Launcher, click on the Add button Enter https://192.168.1.122:8443/desc into the dialog. Note 192.168.1.122 is an example. You should use the IP address for your eisy. Or this: ISY Launcher cannot find ISY Make certain that you are using ISY Launcher. This is a MUS If you have VPN software running, Admin Console cannot search for ISY on your computer. Please disable the VPN, find ISY's IP address and then click the Add button and enter it manuall Make certain that, after reboot, the pattern of lights is as described her If you have recently changed your modem/router, please follow these instruction If you have any firewall software, make sure it's configured properl If all the above have been checked, it's almost a guarantee that that your ISY is not on the same network as your computer. Perhaps at some point you might have configured ISY with a static IP address. Or, that your WiFi network is not connected to the wired network.

Try going thru the troubleshooting steps here: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cannot_Communicate_with_ISY_Portal and here: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored and here: https://wiki.universal-devices.com/index.php?title=Main_Page#admin.jnlp_does_not_start_the_Admin_Console

When you are ready for your move, you can exclude first, then include all on eisy. It is best whenever adding a Zwave device, even brand new, to exclude before adding.

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?