In the process of setting up my FanLink & 5 Button Keypad following https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration#Firmware_5.x ,

I noticed that the program folder path no longer shows up in the program script;

This is what it looks like in the example:

Is this an artifact of the V6.x upgrade? Am I causing this by doing something different?

It does show up on the 'Program Summary' page:

Unless there is a good reason for this it would be nice to be consistent.

I can not replicate this behavior, both Conditions and Actions show the path in Admin Console on my eisy.

Are you sure the device is in a user-created folder, not the main folder? The default name for the main folder is iOX, but may have been renamed by user, the icon is a monitor. If in this "folder" it is at root.

Thanks Javi; I had the programs in folders, but the devices were in the main ISY folder. I've moved everything fan related into a folder for the living room and now I see the paths.

I'm wondering if there exists a 'Best Practices' document somewhere? Beginning with isy994 I've been adding and modifying devices and programs fore the last 12-13 years, and it has become quite unorganized. I'm looking for tips on naming convention, folder use, and a more organized system. Naturally what organization works for oneself is best, but maybe there are some common practices that work best.

Thanks again!

9 minutes ago, Breezyken said:

I'm wondering if there exists a 'Best Practices' document somewhere? Beginning with isy994 I've been adding and modifying devices and programs fore the last 12-13 years, and it has become quite unorganized. I'm looking for tips on naming convention, folder use, and a more organized system. Naturally what organization works for oneself is best, but maybe there are some common practices that work best.

I'm still rather new at this (a year and a half) but the things that work for me: Put all programs related to a common function or area in distinct folders. So I have a folder for all shade related programs, another folder for water leak detection, another one for locks, etc. For device naming, I'll tend to name devices with a prefix for the type of device it is, so Leak_<name> for leak detectors, Motion_<name> for motion sensors, etc. IoX tends to do that by default too for devices like ZWave (ZW_<name>) Matter (ZM<name>. Of course you can rename them anything you want, but I like to keep that prefix. For light switches, well as an X10 user for the previous 25 years, I knew the rooms by their house/unit codes by heart, so I kept the naming scheme as a prefix: eg C4_living_room, B2_office, etc. They did have a natural progression throughout the house and each house code grouped something or a floor, so that remained meaningful. For variables, status variables get name s_<name> and integer variables as i_<name>. For Alexa, I keep the spokens to single words, for reliability ("living", not "living room"). Sounds a bit awkward sometimes.

1 hour ago, Breezyken said:

I'm wondering if there exists a 'Best Practices' document somewhere?

Take a look at the document below. While not specifically for eisy, it is still relevant.

https://docs.universal-devices.com/production/The+ISY994+Home+Automation+Cookbook.pdf