Techman

Apparently the node server needs a token to retrieve the data, so it looks like you can't import the data. At least you have a local station you can look at.

@dbwarner5 I upgraded to 0.8.5 from 0.8.4 unfortunately that didn't solve the issue

@Javi Attached are two screenshots. The EISY shows "AC MAINS RECONNECTED" UDM is only offering a numeric value This is a Zwave device. UPDATE: The numerical values corresponds to the correct Text. By selecting a value of "3" the correct text value "AC MAINS CONNECTED" displays

If the Tempest battery is dead then it won't be sending any data. The difference between remote and local is that remote gets your Tempest data from the internet that is sent by the Tempest. Local is when the data comes directly from the hub. You can use the Tempest map to find another Tempest close by that is sending data.

@DennisC What is your UDX version I'm currently on 4.2.0

No synchronization errors, no other errors The synchronization time seems to be a lot shorter than before I've run synchronization several times with the same results. This appears to have happened after the last UDM update

The latest Android release, 1.5.2, is not properly syncing with 6.0.3 i.e. programs are not updating, and where there should be text options, only numbers appear

Your only option is to monitor the heartbeat of the triggerlinc, but you may not know the battery failed for 24 hours. If you have zwave installed, then the zwave sensors monitor the actual battery voltage Zooz 800 Series Z-Wave Long Range XS Open | Close Sensor ZSE41 800LR - The Smartest House

Bring that you bought them used they most likely contained link data from the previous owner, thus the need to factory reset.

Post a screenshot of the popup when you first try to access the admin console

It's possible that the contacts on the SD card oxidized. Remove power from the ISY, remove the SD Card and clean its contacts with a soft eraser.

In the admin console, under help, what is your current Firmware and UI versions? Clear your Java cache, be sure to check all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp Report back if your still having issues

Try doing a factory reset on the devices before you add them to the eisy If that doesn't work, then try doing a EXCLUDE then INCLUDE. Put the devices in the linking mode then exclude them from the Zwave menu.

After the update packages did you clear your java cache and download the IoX Launcher

My 6.0.3 happened when I did a reboot, I didn't use upgrade packages.

What is your zwave version number, it should be listed under the zwave menu

Per Insteon, there's no release date set for the new PLM. It doesn't appear to be in the foreseeable future.

Clear your java cache, be sure to check all 3 boxes, then download the IoX Launcher from here https://isy.universal-devices.com/start.jnlp The 5.3.4 upgrade can be found here: https://forum.universal-devices.com/topic/33287-534-isy994-last-release-for-isy994/ If your're still having problems then it may be your SD Card. You can try cleaning its contacts by removing power from the ISY, then remove the SD Card and clean its contacts with a soft eraser

Try putting some 2 second waits before your "run programs"

Another possibility is that your typing in the incorrect 6 digit address. It very easy to mix up the 8 and the B

@PapaBear Try doing a factory reset on the MS, then attempt to link it

Can you post a copy of the program

"Cannot determine Insteon engine" means that the PLM can't communicate with the device. Either the device is out of range of the PLM or the device isn't in the linking mode. Also check your batteries.

If you want to change the security setting you have to remove and reinstall with the new security setting

The pin code should be either under or above the QR code, you may need a magnifying glass to see it.