DennisC

Are you on eisy or Polisy? What firmware are you running? Are you on the latest UD Mobile? Have you tried rebooting eisy/Polisy?

It has been a long time since I set this up, so I needed to go back and look. You can turn on a function key from either a zone or an output. Once you have either the zone or output setup, then go to ElkRP2 - Keypads - Keypad # (you would need to do this for each keypad you want the F key to light for). In the definable key selection, go to the line that corresponds to the F key you want to light, and select either the zone or output from the drop down under "Illumination Event". Then place a check mark in the box for that F key under "Blink Light". If you want, you can invert the light by placing a check mark under "Invert Light". When finished, don't forget to save and upload to controller.

I am running the same setup and I can confirm mine works without an issue. Just before the winter I tested my generator which is connected to a manual transfer switch. My procedure is to turn off house power, which powers down all of the devices on the manual transfer switch. This causes the UPS to power eisy and the USB PLM to loose power until I start the generator and activate the transfer switch. The PLM reconnects without issue. The

I do this for my garage door also. In the meantime, you can use ElkRp2 to do this. You can trigger an output when the item (example garage door) is open/closed and then create a rule in ElkRP2 to turn the keys backlight on/off as wanted.

With no offense ment to the plugin author, I have found the success rate with the WOL to be 50/50 on multiple Win 10/11 computers. I have tested other WOL software and the ones that utilize both a Mac address and an IP address appear to work successfully. You can also try to use the subnet mask of 255.255.255.255. Sometimes that improves the success chances and sometimes it doesn't.

I am not sure why you have not been able to create a WOL favorite. I have one set up using Command type with a status of status. That works fine for me.

That is correct, 170001 is an informational message and you do not need to be concerned about those.

Did you try going to each program and resave the program? After migration this step sometimes clears up issues,

Right click on the program and select copy to clipboard. Then post the program here for comments.

Have you tried power cycling by pulling the plug?

Try rebooting, maybe even power cycling Polisy.

First, check that date and time is displaying the correct information. Next, make sure there are no conditions on the master folder and any sub folders. Conditions on folders can be flaky and prevent programs from running. A few things to try: Check the error log and look for any error messages. Right click a program and select status and check what last run time was. Does it align to when the program should have run? Open event viewer, set to level 3 and watch log around time a program should run. See what messages are logged.

Are you sure the user code works? Have you tested it from an Elk keypad? When you setup the plugin configuration, did you use the non secure port? Is your configuration correctly setup in PG3(x)? How about errors in PG3(x) log when set to debug?

Right click on the program and select copy to clipboard. Then paste the program here.

At one time, programs needed to be resaved after the migration. Not sure if that is still the case. However, that doesn't explain your new programs not running. Suggest you try power cycling and after the restart, resave all of your programs. If that doesn't work, try running upgrade packages.

It was my understanding that a UD Zwave dongle was required for a migration. I wasn't aware that no backup was available for the Zooz stick.

Make a backup of your Z-Wave network (Admin Console | Z-Wave | Backup)

Be sure to do a full Zwave backup before an sY backup.

Did you try using the new password to login in to Polyglot?

You should think about upgrading your firmware. If you are using a 500 series Zwave board, you can go up to 5.3.4. If you are using a 300 series Zwave, you can move up to version 5.0.16c. Be sure to backup first. You can migrate your ISY 994 to easy. Here is an announcement from UD: https://www.universal-devices.com/4x-migration/ You can read up on migration instructions here: https://wiki.universal-devices.com/Eisy:User_Guide#Migrating_from_994_to_eisy The UD Mobile app is available and is actively being developed with new features being added all the time. I do not regret dropping Mobilinc.

What ISY firmware version and UI are you using?

Thank you

UD Mobile has an Armed Next Stay Mode and an Armed Next Away Mode. Neither allow you to change the armed state without disarming first. Is that what you wanted me to test?

I don't have a strong opinion on buttons vs selections. Although, that might be moot point if you are using the new Custom Tiles. If possible, I would be interested in being able to change arming modes without having to disarm. To be clear, this is during the exit delay countdown. I never tried it once the delay has timed out. For keypads, I have ELK-M1KPNAV & ELK-M1KPAS and they both allow you to change arming type during the arming countdown delay.

@Jimbo.Automates I tried your sample custom tile for Elk today, and it performed as expected. While this is unrelated specifically to your Custom Tile, as it also happens in UD Mobile, I keep forgetting to ask about it, so here goes: When arming in UD Mobile and the Custom Tile, you can not change the arming type without first disarming the system. Example: You accidently arm away mode, but intended to arm vacation mode. You can not then select arm vacation mode, you first need to disarm the system. This is not consistent with how the Elk keypads work. With an Elk keypad, if you make a mistake, you can correct the mistake by selecting the intended arming type. Is it possible to have the Elk Plugin replicate this behavior?