DennisC

Here you go, just make sure you meet the requirements:

That's the IoX Launcher, thanks for the clarification. I would suggest pressing the eisy multifunction button once, wait about 10 minutes, then open the Java control panel to delete files (check all 3 boxes). Next download a new start.jnlp from here: ISY Launcher After running the start.jnlp file, a new IoX Launcher should appear on your desktop. I know you stated you have done this, but it helps to make sure something wasn't missed to do it again. If the Launcher still doesn't find your eisy, make sure you disable any VPN and try the following steps from the wiki: Troubleshooting 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. Click on the OK button Let us know how you make out.

When you say you can not see it in IoX, what are you referring to? Can you access the admin console? Are you using the Launcher? After an update, you may need to reboot a second time and then clear your Java cache, including deleting the 3 check boxes and then download a fresh version of start.jnlp. After that, run start.jnlp and it will create the Launcher icon on your desktop. If eisy isn't showing up in the Launcher, that's a separate issue, so let us know.

Well worth the change for improved functionality all around and fantastic support.

I have 2 Polisy's running v5.5.9 at two different locations and do not experience random reboots. Have you opened a UD support ticket? They can't fix something they don't know about. Have you checked your event and error log? Also haven't seen other Polisy owner's reporting this, could be this issue is specific to your installation. Try changing the power supply.

That would probably be a very practical thing to do. If you want to try and hold on a bit longer, you could contact UD and ask. You can open a support ticket here: https://www.universal-devices.com/my-tickets/

You are not answering all of our questions. It is hard to help you like that. After upgrading back to v5.3.4, clear your Java cache being sure to check all 3 boxes when you delete the files. Then download a new start.jnlp at: https://isy.universal-devices.com/start.jnlp After it downloads, without unzipping, run the downloaded file and it will put the Launcher on your desktop. Afterwards, if you still have an issue then look at the links I posted above. If they don't resolve things for you, then reply back with answers and we can try to help.

Check out this page on UD website regarding ISY: https://www.universal-devices.com/byebye994/ Do you have a UD portal account? You can also try logging in to your account at https://www.universal-devices.com/ and see what is listed for your ISY.

Why did you downgrade firmware? Are you using the ISY Launcher to access your ISY? The reason I am asking is because your firmware needs to match your UI version. Do they match? Check your About page for both, along with access to network module. Did you clear your Java cache and and download the correct UI for 5.3.0? All of the modules are being retired in favor of node servers. Node servers for a lot of devices are being created by developers. There are several weather node servers available.

I believe the climate module was depreciated some time ago. Are you saying it was working until now? We would need some additional information about your setup: firmware, UI version, installed modules, active portal subscription, ect. Be aware, ISY is at end of life and support for it will be ending soon. You might want to consider upgrading to eisy. https://www.universal-devices.com/store/

That's my guess.....

Have you tried rebooting? What firmware and UI are you running? What is the version of ZWave firmware? What version ZWave, 300 or 500? ISY ZWave Version 300 or 500 Series Identifying 300 Series Z-Wave™ By The Protruding LED The 300 series will have an LED protruding out of the rear of ISY and may have an antenna mount as well. Identifying 300 Series Z-Wave™ By Version From the Admin Console select the Z-Wave™ menu at the top of the screen. Select Z-Wave™ Version. If the version is 4.55.00 the ISY has a 300 Series Z-Wave™ dongle. If the version is 6.81.00 the ISY has a 500 Series Z-Wave™ dongle.

You can open a support ticket with UD here: https://www.universal-devices.com/my-tickets/ If you want to try and force an update you can try running the following via ssh: sudo pkg install -r udi pkg Then open the log by entering: sudo tail -f /var/udx/logs/log When the log shows the update is finished, run the following to reboot: sudo shutdown -r now

I see the following in the log, could that be the issue? mqtt_port</code> - defaults to 1883, the example in the thread uses 1884

127.0.0.1 is a local hose IP and is correct. 10.10.2.20 is the network IP for eisy. So far this is as it should be. I think you need to look at how MQTT is configured.

On the Customization email page under the body, there 3 boxes to specify the type of email you are sending. They are Text, HTML, & XML. If you select Txt and list your device underneath each other, it should display fine in an email. Otherwise use HTML and specify the formatting HTML command.

One of the reasons not to use static IP addresses. If you give us a better picture of your setup, we might be able to help.

Try creating a new program set to run at startup. In the Then section add a wait x minutes. X will depend on the size of your system, try starting at 5 or 10 minutes. Next add run Query All (factory default Query program) program. After your X wait, this should run the factory default Query program and populate the Zwave devices, providing they respond to a Query.

Sounds like you may need more of a float control then a leak sensor. Or, maybe you can raise the leak sensor to the lowest spot the pump can pump down to, or slightly higher.

Here is the link to user guide. https://wiki.universal-devices.com/index.php?title=UD_Mobile

You should have DHCP enabled and set a DHCP Reservation in your router. Have you restarted both PG3x and the admin console? Have you checked the configuration tab of the node server? Set the log to debug and try again. Afterwards check both node server log and PG3x log for errors.

UD is continuing to improve eisy, there have been at least 4 firmware revisions since your device was manufactured. Before determining if we can help you, we will need a little more information. Besides what was already asked, also run: sudo uname -a and post the output. You can run this command first if you would like.

FYI, you can set up a program with no IF section that will turn the pump off, disable the run program (for x amount of time or until you manually enable it). Next create a command icon in UD Mobile that runs the Then section of the program you just created. Whenever you want to run that program, open UD Mobile and hit your command icon. You can even have the icon change color when it's running.

You are running a fairly old firmware version and I suspect you might be caught in an endless upgrade loop. You can open a UD support ticket. Or Do you know how to ssh into eisy? If you can do that, connect via ssh and run: sudo tail -f /var/udx/logs/log With the log window open, go to the Configuration tab of the admin console and select upgrade packages. If the log keeps cycling through the same entries without actually completing the upgrade, that will confirm it.

Sounds like the file association between start.jnlp and Java is broken. You can try to manually reassociate them or possibly delete Java and start over. I believe there is some direction in one of the wiki's on this.