Guy Lavoie

Plug in module, virtual switch... whatever works for you as a unique indicator of the status you want to look for in your program to control a scene and other non-scene devices. It would be easier if UDI added a "If scene on/off command..." in IoX, but at least we have a workaround. Glad it helped.

In that case you could create a program that would watch for any of your lights getting turned on, and have it turn on a virtual switch on, like this: If status light A is on Or status light B is on Or status light C is on. (Etc) Then turn virtual light on The virtual switch would also be added as a responder to your existing "turn off" scene. A second program would then watch for the virtual switch going to off, and execute your thermostat commands, like this: If status virtual light is off Then set thermostat mode...

Well thermostats can't just be "turned off" like a light bulb. You can do things like change modes, setpoints, etc. One way to do that with a scene would be to add a virtual switch to your scene (install the Virtual plugin) and then create a program that sends the desired commands to the thermostat when that virtual switch is turned off by the scene command. If there is a light in your scene that only gets turned on by that scene (and never manually), then you can watch the status of that light instead of a virtual switch in your program.

21100 is the software module number, when you look under "help, about" in IoX. What Techman is asking about is the hardware device. You either have a Zooz 700 series USB stick, or the ZMatter dongle pictured above.

I can't answer for IoS. The current version of IoX is still 5.9.1_18 and has been for over a week. With the android version, I've been able to add both a wifi and a Thread device, but it's still not very stable. The Thread device stopped responding to commands from the eisy, though it still works from Google home. It also sees the bulbs as on/off devices, so no dimming or color control. It's a work in progress.

For something like that, I'd use a regular appliance module to turn on a separate high capacity relay or contactor. It's more trouble because you'd need to make a separate enclosure, but it would be more robust. Pool pumps have a high starting load and draw lots of current.

In the motion sensors, inside the battery compartment.

Well you need to know exactly what you have first. If the bulb has a QR code printed on it along with a pairing code in the format XXXX-XXX-XXXX then it should be a Matter device. Cync is the name of a product line, not all of which are Matter. Sometimes you'll also get a printed copy of the QR code printed on a separate sheet, but it won't be on the packaging, since each code is unique. The second thing is that you need to know if it communicates via wifi or Thread. Chances are it's wifi for most line powered devices (though I have nanoleaf bulbs that are Thread). Assuming it's wifi, you should be ok with your current hardware. I just googled "Cync Reveal" and it's not showing as being a Matter device. You would see the Matter logo on the packaging (looks like three arrowheads pointing towards each other) so I don't think you'll get very far with those bulbs. They seem to be wifi bulbs that are compatible with Google home and Alexa (the most common platforms), Homekit isn't listed so it looks like you're out of luck there too.

Try control instead of status for the motion sensor. Also, how are the jumpers set?

Well it's essentially the same program, but with an additional time period and then an off statement. I have several motion sensors that are used like that. No variable is used to control it otherwise. MS basement kitchen - [ID 001B][Parent 006A] If From 5:00:00PM To 10:30:00PM (same day) And 'MS basement kitchen' is switched On Then Set 'basement kitchen light' On Wait 5 minutes Set 'basement kitchen light' Off Else - No Actions - (To add one, press 'Action')

I have a similar program, for turning on a video fireplace if motion is detected between certain hours in the morning. It looks like this: Ambiance turn on if MS morning - [ID 0037][Parent 0048] If From 7:30:00AM To 9:30:00AM (same day) And 'MS LR-Sensor' is switched On And $s_fireplace_already_on is 0 Then $s_fireplace_already_on = 1 ...trigger fireplace on commands... Else - No Actions - (To add one, press 'Action') The $s_fireplace_already_on state variable is a flag to prevent it from triggering twice on the same day. It gets reset to 0 during the night. I might add that if you use a flag variable like I did, then put the statement setting it to a new value as your last Then statement. I edited out some commands from my actual program for clarity.

I'm running the latest release (5.9 1) and the hostname shows up fine on my router, a eero 6. But there was an issue with the early release of 5.9 1. If you upgraded it in February and are only bringing this up now, go in Configuration and click on Update Packages, followed by any recommended reboot.

That's the correct format, though you might need to add the port number too. I just tested this on my own eisy http://admin:<password>@192.168.0.145:8080/rest/vars/set/2/2/2 It correctly changed state variable id 2

Are you able to turn the devices on and off from the Admin Console? Sounds like something is getting corrupted, or a device is becoming intermittent.

I had X10 for 25 years. Worked pretty well for such an simple technology. It was groundbreaking at the time. But I certainly don't miss the slow response (especially when doing multiple address commands, like A/1, A/2, A/3, A/ON) and the almost total lack of status tracking. How quickly we forget!

Hah, that's the dark side of a highly customized setup, using a mix of technologies (like Insteon and Hue). You end up with lots of scenes and programs! But it allows you to do things that wouldn't otherwise be possible. I do that kind of thing a bit at a time, testing everything as I go.

The announcement in January mentioned adding the plumbing for Homekit. I wouldn't call that "being tested" just yet.

Yes, one scene for each keypadlinc button that you want to update, and one program for each Hue light that you want to track. Programs would look something like this: aaa hue - [ID 009F][Parent 0001] If 'Hue / Hue-Lazyboy' Status > 50.0000% Then Set 'Scn KPL button' On Else Set 'Scn KPL button' Off You could also add more logic to the program, such as Or statements if one button controls a group of lights for example.

You're using the Hue plugin, right? You would need to create a program that watches the status of the Hue light, and update the keypadlinc button's backlight. That's done by creating a scene with just the button as a responder, and have the program turn the scene on and off as needed. The Hue plugin does track the status of the light, even when it's controlled by the Hue app. There might be a slight delay but it does work.

Have you tried running the update from the Admin Console instead of from UDI Mobile?

Insteon works in strange and wonderful ways... No idea really, but the first thing I would have tried would have been to "Restore Device" on the affected switches. This rewrites the links to them, without losing the references in programs and scenes.

The various suggestions are all valid. The approach you use will be based on how practical it is. I have a 6 button keypadlinc near the door we always go out through. Two of the 4 center buttons indicate if any light on that floor is on, including lamps, etc. For those, I have a scene that has nothing but a single responder (the button light) and two programs, one that look for any light being on to turn on the backlight, the other that looks for all lights being off to turn off the backlight. Any additions or changes to the lights I want to monitor are then done in the programs. Easier than tracking many links. In other cases, it's conventional scenes linking back to the button backlights.

If you have spare Z-wave plug in modules, have you tried adding a few, to try and re-jig the network?

Rereading your post caught my eye at the above quote. Both Z-Wave and wifi thermostats aren't getting updated? Now that would appear to be more of a program execution issue. The fact that it started after an upgrade to 5.9.1 is also suspect. I'd add test code, such as incrementing a variable in the same program, just to see that it's going through the statements. One before and one after. Something like this: Then increment variable 1 Then set Z-wave termistat Then set wifi thermostat Then increment variable 2 And check it every day to keep track of the variable values (or write them down along with the date).

How long have you had the "relatively new" UPS's? Just one of those things that can create electrical noise issues. Have you tried eliminating them, for test purposes? If your problem occurs frequently enough, you should have a quick enough conclusion as to it they're a problem or not.