Guy Lavoie

Maybe it wasn't unrelated. I would have worked on the Insteon discovery problem first and once fixed, tried reloading UDM after. You want the controller to be in a normal operating condition first.

It's a fanlinc that identifies as a lamplinc... Might it be part of a scene? If you look at the fanlinc device in Admin Console, do you see it as a responder to any other device.

Any hints at what is new or different about it, vs 5.9.1?

I agree that the plugin is mainly a bridge to programs, and that the usual IoX programming should be used for logic and performing actions. Any additional baked in functionality is ok as long as it doesn't interfere with that. Thanks again for maintaining it!

So nothing out of the ordinary. You have the ZMatter dongle. One quick thing you could check is in the Admin Console Configuration screen. Make sure that Z-Wave support is "On", and that it's not showing a button underneath to migrate to ZMatter, which would indicate it's configured to use the Zooz dongle.

Just wondering: which IoX version were you running before 5.9.1? Also, is your eisy using a Zooz dongle or the ZMatter one?

I've been doing that kind of thing using a virtual switch (with the Virtual plugin). It looks just like a switch in UD Mobile, but you can then have a program turn the virtual switch off, so that the next press is always to turn it on. There might be a slight delay before it turns off, but it will.

Well, show us an alternate programming model for home automation. Here is a simple example to try: a light that can be turned on manually with a wall switch, or triggered by a motion sensor. If triggered by the motion sensor, have it turn off automatically after two minutes. If turned on manually, leave it on, and ignore the motion sensor until the light is manually turned off. With the eisy, it would look something like this: If Motion_sensor is On //motion sensor to turn on light And Light is Off //and it hadn't been turned on by another method Then Turn Light On Then s_motion_variable = 1 //flag to indicate that motion sensor triggered the light If s_motion_variable > 1 //if motion sensor turned on the light Then Wait 1 second Then s_motion_variable +1 //increment the variable once per second If s_motion_variable > 120 //if it's been incrementing for 2 minutes Then Turn Light Off Then s_motion_variable = 0 //stop the "timer"/flag variable How would you program this in another way, using a programming wizard interface like the Admin Console does (to prevent syntax errors)?

You need to understand that this programming model provides a multitasking language (not operating system). It is based on the ladder logic model that programmable logic controllers have used for decades. The interpreter loops constantly, looking for any changes in status (of devices, state variables, time of day, etc) that warrants executing a THEN or ELSE statement. It simulates being everywhere at the same time. You'll find the same programming model in other home automation devices, such as the Elk M1, Ocelot, JDS Time Commander and such. I wouldn't want it any other way.

The problem with that is that the programming model is too different. There is very little conditional branching in ISY. Essentially, its just THEN and ELSE. Then there is no nested logic at all (If...then if), instead you need to create separate programs that interact through variables. Creating such a compiler would be an exercise in artificial intelligence 😉

You mention going back to the ISY994... do you have a separate PLM for it? If yes, it might be simpler and faster to get a USB to serial adapter for it, and use that to connect it to your eisy.

I've wished for that too.

Try a resync of UD Mobile. Press on the three little dots at top right and then "Synchronize". This is normal after changes.

In the Program content window (top window), click on "Add And (..)" at the bottom right corner. This will add two parenthesis lines to your program. Then move the parenthesis lines up or down to where you want them.

Have you tested it manually? For example, looking at your state variables in Admin Console and verifying that $sSunrise_Daytime is indeed set to 1, and then right clicking on that program and trying "Run (If)".

It's also important to note that if you were already in the Admin Console when you configured the devices in the plugin, you need to log out of Admin console and then log back in again to properly see the changes.

How did you define it in the plugin? I have several such switches defined, like this:

In Admin Console, did you just click on "Start Linking" or did you scroll down to "Link a Sensor" -> "Leak Sensor"?

It's especially handy in UD Mobile, because it's both a button and status indicator, like a keypadlinc. One main use for it is to trigger programs on scene on/off commands, since IoX doesn't offer "If scene command..." directly. I include a virtual switch in the scene I want to watch and the program triggers on the status change of the virtual switch (which can't ever get turned on manually...). I often use two virtual switches in pairs. One use is to control my garage door opener, and indicate open/close status, even if the opener is controlled manually. Another pair controls/indicates watercop valve atatus. Again for pool solar heat control The only downside is that you don't get control events, only status.

Virtual is a hidden gem among the plugins. I use it for several different things, though not the garage option. Thanks!

Sounds like the devices already belonged to another Z-Wave network, and needed to go through an exclusion procedure in order to allow them to join a new network.

Yes, that's right. I think that for the Polisy, the only difference was that the pro version had wifi capability.

Yup that's a classic. It looks like a field label, but it's actually a button to write the new value.

Next step: Alexa, please remind me your device name for the living room lights? 🤨

Programs and scenes are the best ways to get the most out of keypadlincs and status indications. The only annoying thing when using programs is the slight delay before seeing the backlight update.