Techman

Try to rename or modify the the customization, if successful then try to delete it.

Probably best to open a support ticket

You followed the correct procedure. Try reboooting the eisy and if the customization is still there, at the bottom of the window click delete then click save. Let me know if that worked

Click on one of the sounds, then enable it. You'll probably have to write a program to apply the sound to an event. UD Mobile - Universal Devices, Inc. Wiki

@JSchumann If you scroll down you should see a line for Notification Cateagories. Clicking on that line will give you more options. If you don't have a line for Notification Categories then you probably have no options for additional sounds

Can you do another "upgrade packages" or open a support ticket

The new interface is called eisy-ui. It's still in development so some options are net yet available Here's the link: http://eisy.local/

If you can't access eisy-ui from your browser It's possible that eisy-ui didn't get installed There's been no change in the login You don't want to revert back to 5.xx, Are you on a Windows or a MAC computer? Is your eisy connected via ethernet or wi-fi? It's best to open a support ticket: My Tickets - Universal Devices - The Most Powerful Automation, Energy Management, and IoT Platform

Connect your eisy r2 to your router in the admin console click on the line with your eisy, log in, click on the configuration tab, then click on upgrade packages. When the upgrade is complete you'll have a window that tells you to reboot. Do not reboot before the upgrade is complete. After the upgrade you'll need to 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

You can also log into PG3 via eisy-ui http://eisy.local/

@SSamuels Let me known if deleting and recreating the program fixed your issue

Your controller is seeing the status of the IOLinc When you trigger the alarm does your program, '12129Td/Alarm/ALARM - Intrucsion-Sensor' show as red or as green in your program tree? You might also try deleting and recreating the program.

The IOLinc is a powerline only device, if you have noise on the powerline at the time the alarm triggers the IOLinc may not send its status.. Can you put the controller log into level 3 mode and then set off your alarm and post a copy of the log.

The ISY994 is no longer supported, so there's no option to update the portal account

What exactly are you using to trigger The IF clause ?

"Cannot determine Insteon Engine." means that the PLM is unable to communicate with the device. Either your're entering the wrong address, or the device is out of range of the PLM or the device is not in the linking mode. What address are your using for the device?

What type of power supply are you using to charge it, voltage and current?

The Professional version is free. That's the only option

@kurelgyer Check for a loose connection(s) at the terminals on the IOLinc

Here's the instructions for replacing the PLM Replace PLM Procedure (EISY or POLISY).pdf

@jim_ Generally speaking all on events will not show up in the ISY logs as the ISY is not aware of the events.

Almost all the carriers have permanently blocked email to text due to abuse from spam There's no work around

In windows its located here. I believe the app data folder is hidden so you may have to enable "show hidden items" under view in file Explorer C:\YOUR USER NAME\AppData\Local\Temp

@MWoods329 Try removing power from your ISY for a minute If that doesn't fix it then, if your on a windows computer, exit the admin console and delete the 5 files in the windows temporary folder that end in STATE. those files will be rebuilt next time you open the admin console Let me know if the above solved your issue

Try this. Clear your Java cache, be sure to check all 3 boxes which will delete the IoX Launcher from your desktop, then download a new IoX Launcher from here: https://isy.universal-devices.com/start.jnlp You may have had an older version of the IoX Launcher The correct version of the Launcher has the UUID BEFORE the URL