DennisC

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.

Remember, PLM can fail, it might be a good idea to have a spare around. Or, possibly order the cable so you can upgrade now and keep the USB PLM as a spare.

In addition to @MrBillcomments, which USB-serial adapter did you use (the one by UD) or? At least one other poster received a deflective USB-serial cable recently. Did you follow the migration guide? https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

If you have a USB PLM, just plug it in. If you have a serial PLM you need a cable like this: https://www.universal-devices.com/product/serial-plm-kit/

I added the bold: From the migration documentation: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Post Migration If you migrated your Z-Wave Network In most cases they are battery powered devices that were not awake during migration To migrate one of these devices, wake it up (see user manual for the device) and then do the following right+click on a placeholder node for the device, select Z-Wave | Synchronize | Update with Interview When it completes do the same for the next device From the eisy user guide: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide What to Expect During Migration Insteon The Insteon network on ISY-994 will be seamlessly transferred to Eisy / Polisy. Your nodes, programs, and scenes using Insteon will remain unchanged. Z-Wave The Z-Wave network managed by ISY-994 will be migrated to the ZMatter Z-Wave implementation on Eisy / Polisy. The devices in the network will remain the same, but their representation in ISY may change. Nodes Z-Wave ISY Nodes will be reused whenever possible, but new nodes may be created as well. Programs Z-Wave ISY nodes in programs will be migrated, however, node actions and conditions may no longer be valid if the node's support for them has changed. Scenes Z-Wave ISY Nodes in scenes will be migrated, but those using native links (i.e. association) may require updates. If you have any Z-Wave nodes with a type of (Placeholder) it means the device has not been migrated yet. From the migration guide: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration What to Expect During Migration Insteon The Insteon network on ISY-994 will be seamlessly transferred to Eisy / Polisy. Your nodes, programs, and scenes using Insteon will remain unchanged. Z-Wave The Z-Wave network managed by ISY-994 will be migrated to the ZMatter Z-Wave implementation on Eisy / Polisy. The devices in the network will remain the same, but their representation in ISY may change. Nodes Z-Wave ISY Nodes will be reused whenever possible, but new nodes may be created as well. Programs Z-Wave ISY nodes in programs will be migrated, however, node actions and conditions may no longer be valid if the node's support for them has changed. Scenes Z-Wave ISY Nodes in scenes will be migrated, but those using native links (i.e. association) may require updates. Programs Programs and variables will be transferred seamlessly, but some exceptions may occur if ISY Nodes or their commands and/or status have changed. All of the firmware releases reference the above documentation: Plus, all of the firmware releases have support posts which documents the actions everyone had to do to complete the migration. My point here is you shouldn't be blaming UD because you missed something. You have been around here long enough to know you need to read up on an upgrade before proceeding. Network Resources All Network Resources will be migrated seamlessly, however, you will need to open and save each one individually.

Yes it has been well documented in the firmware upgrade notices and the migration documentation. It also states what you need to do, resaving programs and network resources for instance.

None of this should have been a surprise, it has been well documented in the various firmware notices and the migration documentation.

For anyone else trying to set up Elk voice with the Elk node server, it is very simple and works well. There are two points to remember, make sure you have Chime Mode set to Voice or Chime & Voice, and you must use words not phrase from the drop down box in the program when setting up the Controller with the words to speak. The ability to use phrase doesn't seem to work and is a known bug. Setting this up in a program with the Elk node server allows you to set an active time period in the If portion of the program for quiet time. You can also add other conditions for example if armed away, or armed vacation, etc.

@pjjameso I just tried adding a voice message and it worked fine. Make sure you have Chime Mode set to Voice or Chime & Voice.

Why are you using network resources? Maybe I am not understanding exactly what you are trying to accomplish? The voice words I have coming out of my Elk speaker were set up way before the node server. They are set up in the Elk M1 & triggered by the Polisy/eisy system. So I have no practical experience doing it all from Polisy/eisy. However, take a look at these previous threads for ideas & guidance on doing it from the node server: https://forum.universal-devices.com/topic/35026-elk-pg3-voice-commands-now-active/ https://forum.universal-devices.com/topic/40067-silencing-voice-messages-from-elk-ns/