Techman

Do you have another open/close sensor installed that shows a heartbeat node, or do you have one that isn't installed that you could test? Either the sensor is defective, or depending on your device firmware version, maybe they eliminated the heartbeat node, which is unlikely What's the 4-digit date code and hardware version of your device. it should be printed on a sticker inside.

To factory reset an IOLinc: 1. Unplug it for 10 seconds 2. While holding down the set button plug it in and continue to keep the set button pressed in for 5 seconds 3. The IOLinc LED will blink once, then the IOLinc will beep as the LED turns back on

Make sure that your admin console is the same version as your ISY firmware. Try doing a factory reset on the device then a restore device. If that doesn't add the heartbeat node than I would uninstall it, factory reset it, and then re-install it If then you're still unable to see the heartbeat node, then you might want to update your ISY firmware to the latest version which has numerous bug fixes and improvements.

@wes Here's a sample of two programs I use to monitor heartbeat. The first program should be "enabled at startup". After you create it, manually run the IF clause to initially start the timer. If the heartbeat is detected, then the first program will restart the timer. If it's not detected, then the second program will run. Program 1 ----------------- IF Sensor heartbeat is not switched on or Sensor heartbeat is not switched off THEN wait 28 hours run program sensor heartbeat Fail (then path) ELSE (blank) Program 2 ---------------------- IF (blank) THEN send notification to your email ELSE (blank)

@Javi Yes, the app is set for local connection. All was working fine until I installed the latest update, 1.0.14. I tried rebooting the Android device yesterday without success. My LAN is a Wi-Fi 6 mesh system. I don't know what changed between yesterday and today, but all is good now

The Aeotec ZW078 is compatible with the ISY Here's their compatibility list https://aeotec.com/compatibility/ Note: the compatibility list contains devices and Hubs that Aeotec has tested and deemed compatible. They don't show the Polisy or eisy yet, but if they work with the ISY994 then they most likely will work with the Polisy and eisy.

It's on Wi-Fi. It's working this morning. I'm not sure what the problem was. I didn't change anything on this end.

The sensors use the Insteon RF protocol. You would need an Insteon dual band device, such as an on/off module, lamplinc module, etc. close to the leak sensor to relay the signal to the PLM. To receive notifications, you would write a program to send you an email or text when the sensor is activated.

The sensors are compatible with the ISY, Polisy and eisy

@Javi Just installed the latest UD Mobile update on Android 13. I now get "Starting Subscription" error when I try to connect to ISY, Polisy, and eisy. UPDATE: I'm now getting "unexpected close, failed to connect". and "connection refused" All was working prior to the update

@wes What is your ISY firmware and UI version What's the model number of the sensor you're adding

Try removing power from the eisy, wait a minute, then let it boot up, which can take a few minutes.

@GRoehrborn When you updated your ISY firmware did you clear your Java cache, including installed applications, and then download a new IoX Launcher? In help about, does it show the correct firmware and UI versions? If not here's the link to the IoX launcher. Current ISY firmware is 5.3.4 https://isy.universal-devices.com/start.jnlp

What's your ISY firmware and UI versions? Is the power led on your PLM on? What leds on the ISY front panel are on?

Your username and password may have reverted to the default admin/admin Clear your java cache, including installed applications, then download the IoX Launcher, as it's possible your UI and ISY firmware don't match. A match is necessary for the ISY to properly work. Make sure DHCP is enabled in your router

Upgrading from 4.xx to 5.3.4 may require some user intervention. Read the release notes for updating from 4.xx to 5.xx. The update should not affect your network resources.

In addition to what @kzboray mentioned, what is your ISY and UI firmware versions? Your ISY Zwave version indicates that you have the 500 series board. If you have the Zmatter dongle plugged into the eisy you should have a migration button option in the configuration tab. When you press that button it will give you 3 options, the middle one is the migration from the ISY 500 to the eisy Zmatter.

Migrating Z-wave from the ISY to the eisy or Polisy requires the 500 series board. If you only have a few Z-wave devices, then it shouldn't be too painful to manually install them in the eisy or Polisy after first uninstalling them from the ISY

@dakall re: network resources Once you migrate, your network resources need to be saved, they should then work

@Chris Jahn I would like to test a few Z-wave devices with the eisy. When I plug the Zmatter dongle into the eisy I get a "Z-wave dongle not responding" error. I'm assuming that I need to push the Migrate button in order for the eisy to recognize the Zmatter dongle. Will I then lose the ability to migrate my 500 Z-wave network to the eisy, as once the migrate button is pushed the options are no longer available as was the case with the Polisy.

after local you need a colon (:) not a period.

As of 1/4/2023, the PLM cable kits are back in stock at UD Serial PLM Kitfds - Universal Devices (universal-devices.com)

The range extenders will probably show up in a future UD firmware release.

Wi-Fi is disabled when the ethernet cable is plugged in and connected to your router. If Wi-fi has been previously setup, then when you disconnect the ethernet cable it will automatically revert back to wi-fi.

Is it possible to create a run widget for an "if" or "then" clause in a program?