DennisC

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.

Yes, variable substitution works fine. UD Mobile notifications work just fine and I haven't missed one. Pushover will work with UD Portal. Consider adding the Notification node server which allows you to use Pushover. It makes things very easy and opens a lot of possibilities.

ok

I'm saying, in UD Mobile, under Settings - Systems - system in question - System Status is set to disable. I also disabled Use ISY Portal for remote connections from the same menu. This particular system is a legacy device that I haven't turned off yet because it is not local. It is not the current production unit for that location. When you have multiple device at different locations, having control over if it should be monitored in necessary.

When you have multiple devices (ISY-Polisy-eisy) across multiple locations, is there away to disable one unit from reporting offline? I appear to have an ISY at a remote site that is bouncing between offline-online. In UD Mobile I have turned off System Status for that device, but I am still receiving the notifications.

That is not overly helpful if you are remote and not near a computer. Isn't that the benefit of UD Mobile?

No, you should not have a manual IP address. The reason UD is forcing DHCP reservations is because the use of a manual IP was causing issues resulting in many service tickets. DHCP reservation is the way to go.

From 3:16 am to 6:12 am I received 2 offline messages and 2 online messages. Which raises the question: @bmercier& @Javi 1. How do we know from the notification if there is an issue with UD's Service or on our end? 2. Does UD have or intend to relatively soon setup an UD Service status (all services are up or certain services are down) link? 3. I opened UD Mobile and reviewed and acknowledged the notification, however, the notification did not disappear from my phone. From my phone, I had to click on each and every notification itself, allow it to open UD Mobile, and then close out & go back and repeat for the remainder of the notifications. Not sure that is the best approach to clearing the notifications, especially if UD service goes down and we receive a lot of notifications. Why doesn't acknowledgement of the notification in UD Mobile clear the phone notification? Phone is Samsung Galaxy S20+ Edit: Received another set of offline/online at 9:32 am & 9:36 am.