DennisC

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.

Maybe you need to re-think this. That is an extremely high failure rate that we have not seen reported here. The more likely correct answer to this problem.

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/

If you have a specific question when you start working on this, let us know.

What components are you using? Are you on Polisy/eisy, do you have the Elk node server? All can be accomplished very easily with the Elk node server and UD Mobile. All programing should be created in Polisy/eisy, using the Elk node server nodes. At a high level, create a program that disables the beeping program. It can be time based or with no If statement. If you go with no If statement, leave the program disabled and create a command item in UD Mobile that runs the Then command on the disabled program. When you tap on that icon the program would disable the beeping. I typically have the icon change colors when it is running the command (Then). If you want the beeping to resume in the morning and your If section is blank, create a second program to run at a certain time to enable the beeping command, or back in the 1st disabled program, add a Wait for x hours and then enable the beeping command. Elk node server can also handle the voice part of your question. There are instructions on the Elk node server help page on github, which you access through the node server store.

There are a few things you could try if you haven't already: With Event Viewer open to level 3, go ahead and re-add the lock (be sure to follow user manual instructions). Keep an eye on Event Viewer window. If after this, there is still an issue, with the Event Viewer still open try: Right clicking on lock in admin console and select ZWave - Synchronize - Update with Interview. Check Event Viewer window for errors. If there is still an issue, try right clicking on lock and select ZWave - Synchronize - Update. Check Event Viewer. If none of the above works, you could try removing the lock and re-adding while watching the Event View for any clues. To determine the nodes that should be present, right click on the device and select Xray. When the screen opens, select "Device/Channel Database Object" then hit Go. You can follow this with "Device/Channel Database File" then hit Go.

How was UD able to confirm you were in this mode?

The instructions are at the bottom of the page here: https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions

As do I, using their 4 volt rechargeable batteries. You charge them. Ia a USB charger. I have had 4 of them in use at two different locations for about 18 months. I recharged the batteries just recently when the battery voltage dropped to about 3.82 volts, only because I thought it was about time to charge them. There was no issue requiring them to be recharged.

I would suggest opening a support ticket with UD. Even if it has already been reported, the more data points they have the quicker it can be resolved.

Try rebooting eisy.

That really shouldn't be, maybe you are running a really old version of start.jnlp? Do you recall what firmware version your ISY is on? My suggestion is to proceed as follows: Clear your Java Cache, (be sure to check all 3 boxes to delete all apps), if you need instructions, follow the link here: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop Download a new version of start.jnlp from here: https://isy.universal-devices.com/start.jnlp When you double click start.jnlp, it should install the current Launcher on your desktop. You should be able to click on the Launcher and it should open and find your ISY. If it doesn't you can enter the address manually by clicking "Add". If the Launcher doesn't automatically find your ISY, you can troubleshoot the issue by starting here: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Finder_does_not_find_ISY Depending on your system (Windows, Mac) and the firmware version you are running there are some other troubleshooting guides available, but we will need more information. FYI: The ISY is at end of life and will not be developed any further. In addition, official support will be ending soon, maybe around end of year. The current hardware is called eisy and is much faster than ISY. In addition, eisy has a built in ability to run PG3x, which gives you access to numerous node servers. Node servers open up many automation possibilities that were not previously available.

Got it! You could copy the links and post them inside a document (Microsoft Word or similar).