Guy Lavoie

If you are using Insteon dual band devices (like almost all of them currently are) then they should work, since it's rf based. It depends on how far apart the two systems are, for proper communications.

I have an Elk ESM1 signal meter from my X10 days, and it has been handy for seeing Insteon powerline transmissions, and noise. Not perfect, but if the noise is bad enough, it can give you a quick hint.

You might need to hook up a hdmi monitor and keyboard, and see how it comes up. Have you tried reconnecting it back where it was to see what happens?

I'm always leery about versions ending in 0.0. I have no real need to update yet so I'll wait until the initial issues are worked out.

Another thing with scenes is that when you launch one that has several Insteon responders, Insteon communications will be busy for a noticeable period of time, up to a couple of seconds. This is because of the "cleanup" messages that are sent back and forth between the devices. If you have programs that launch scenes, avoid any programming that sends more Insteon commands immediately after launching a scene. Wait a couple of seconds. Commands sent too soon might not be reliable, and might even cause a dreaded "all on" event.

We love happy endings! But...make a backup or three, right now! And clean the contacts on your SD card. Then you'll be all set for a while yet.

I doubt that someone will rewrite the Hue plugin to use the V2 API. I'd try Matter, which is still in beta on the eisy. Matter was specifically created to allow interoperability between systems, and this is a good example of that. You'll probably get the basic functionality, minus some of the fancier features.

To avoid the loop, you could use a state variable as a timer, to disable the scene command trigger for a few seconds after having just sent one. But this only works correctly if you can detect the reception of the actual command (control), not a status change. Something like this: If zwave_control Turns ON And Variable_Timer = 0 Then set scene... Then Variable_Timer = 1 If Variable_Timer > 0 Then Variable_Timer +1 If Variable_Timer =5 Then Variable_Timer = 0

A quick search turned up this AI answer: "No, the Hue Bridge Pro does not support the deprecated V1 API; it requires the V2 API to function". So that's that. You might need to access your Hue devices as Matter devices instead, which the new bridge supports.

Is your ISY994 configured to get it's IP address by DHCP? If so, did your old router have a reserved IP address for your ISY994's MAC address?

I remember that the Hue api for a long time has been "version 1", and that they introduced a more secure version 2, hinting that version 1 would eventually be unsupported. Maybe that was the reason for requiring that you now log in to your Hue account on their phone app. If that's the case, then the plugin would need to be rewritten to use the newer api.

How about doing it through a program? If zwave_device turns ON Then set scene...

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.