DennisC

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?

How about posting one of the programs not working? Right click one of the programs and select copy to clipboard near the bottom of the list and paste here.

Make sure you are using the non secure port 2101 on the configuration tab of the plugin.

If you followed the configuration instructions and have specified the areas on the plugin configuration tab and then restarted the admin console, the zones should show up. The zones are not listed under Elk Controller, however. They should appear in your device list separately. If not, go to PG3 Elk plugin, set the log to debug, and then restart the plugin. After startup, check the log for errors. Just in case, here are the Configuration instructions: To Configure the ELK Nodeserver Custom Configuration Parameters Set temperature_unit to F or C Set host to the host or ip address and port, e.g. 192.168.1.15:2101 Set user_code, suggested to create a unique usercode for this NodeServer Set areas to the range of areas you would like to include Set outputs to the range of outputs to include Set change_node_names to true makes ELK the source of node names so if they are changed then ISY names will be changed to match. Set light_method to one of the following. IMPORTANT: If using ELKID or ELKNAME you must enable the "Allow ISY Access by PLugin" on the configuration page. NONE Use this if you have no need to control ISY lights with your ELK. ELKALL This creates an ISY Light node for every definded Light node on the ELk If you change light_method from ELKALL to another method, the Light nodes will be removed ELKID This works by right-clicking on a node in the ISY and adding a note with "ELKID=n" where n is a unique integer Then click on the "export" link provided below which will appear once your ELK is synced Note: Depending on how many devices on your IoX it may take a while to process and generate the export file. Once the file is downloaded, open ElkRP connect to your System, then right click on Automation -> Lighting and import the file. ELKNAME This attempts to match the name of an ISY Node with the Name of an ELK Light node to control. The table on this page will show the matches. IMPORTANT: The Elk limits the light name to 15 characters. So the plugin will first check for an exact match of name or address and if not found then it will look for partial matches. This means if you have a light called "My Long Light Name 1" and "My Long Light Name 2" you will only be able to create an ELK light name of "My Long Light " so it won't find an exact match, then it will relook and match one of the others. But if you only have a light called "My Long Light Name" then it will always work as expected. Instead of using the device name, you can also put in the IoX device address in the Elk. Note that if you remove an Area, it will not be removed from the ISY or Polyglot. This is intentional just in case it's an accident and your scenes or programs reference the nodes. You can go to the Nodes Page in the Polyglot UI and delete leftover nodes from changing ranges or light_method using the X to the right of the node. Ranges A range can be comma seperated to include just those numbers, or seperated with a dash to include numbers in between. For example 1-3,5,7-8 will be 1,2,3,5,7,8 All ranges start at one just like the numbering the Elk uses.