Guy Lavoie

That's a suggestion I also made a while back, to create a "user only" mode for use by non technical people (ie: other family members, guests) and that there could be a small icon to touch in a corner that would prompt you for a password, to access the main menu.

Cloud dependency takes another hit.

Speaking of TODO list...the temperature device (for Alexa)? 🙂

What communications technology do the blinds use? IP, zigbee, zwave?

Ok, but first of all, did you manage to do an actual factory reset of the bulb? The bulb cannot belong to two hubs at the same time.

In your case, you should be quite pleased with the Hue plugin. I have Hue bulbs in lamps, that my wife controls with Alexa and are also part of scenes. They're more expensive, but worthwhile.

I don't have a MyQ system so I have no idea how they work, but most garage door openers only allow you "press the button" to open or close the door. Knowing the door position would involve using a separate sensor, such as magnetic contacts and an input module, such as an Insteon iolinc module. That's what I have myself. I have an alarm system-like magnetic sensor connected to the input of a iolinc, while the output of the same iolinc presses the button. The input sensor tells me if the door is closed or not, and I use program logic to press the button.

But I also keep in mind @Papa C 's original post, that he's just experimenting with zigbee, and might not be expecting to fully control a Hue bulb this way. Experimenting is also my way of learning, and I'll often use what I have on hand. Just getting the bulb to be recognized as a zigbee device is the first step. That's why I mentioned doing a factory reset on the bulb.

Have you factory reset the bulbs? That's usually by turning them on and off several times. They should blink a few times when that's successful. If the bulbs have ever been set up before, this really needs to happen first. Then, try adding them, usually from admin console. If you do get them added, you'll probably find that the control you get will only be basic, such as on/off and dimming. To get the full feature set, Hue bulbs are much better set up with a Hue hub, and then controlled using the excellent Hue plugin.

Yet you're able to log into eisy-ui with your portal credentials? Have you tried accessing the portal online, at https://www.universal-devices.com/ ?

You're still new to the eisy, or have never worked with plugins? Click on "plugins" at the top in admin console and then "Launch Polyglot", and log in with your admin login and password. You'll probably get a safety warning, which you can override. Once in, click on the "Plugins store" and find the VenstarCT plugin, and install it. Try it first in demo mode. There are instructions in "more info". I'm not familiar with a ADT plugin and don't see one listed. Anyone else familiar with this might be able to say something about that.

Yes, the typical trouble free way to add a Zwave wave device is to use the remove function, which does a zwave exclusion on the device. Sometimes you need to do this even on a brand new device. Looks like that worked well for you. The upgrade from 6.0.4 to 6.0.5 is a minor revision, mostly small fixes. It shouldn't affect your device configuration in any way. To do a version upgrade, go into "Configuration" and then click on "Update Packages". This will launch the download and installation of the update. It should then prompt you to reboot your eisy, which you do by clicking on "Reboot" on the same screen. I cann't offer any answers about the blinds.

Have you tried removing power from your eisy for 30 seconds, then reconnect the power and turn it back on?

Well your secondary condition is actually taken care of automatically by the status change of the same input that triggers the program. In essence, if the triggering condition is detected as a status, it remains true until the status chnges again (level sensor closes again). If you hadn't wanted the 10 minute delay, it would be a straight if/then like this: program 1 If Status level sensor is ON Then Turn on pump program 2 If Status level sensor is OFF Then Turn off pump The desired 10 second wait before turning on the pump is done by adding a line to program 1: program 1 If Status level sensor is ON Then Wait 10 minutes Then Turn on pump That works because the status of the level sensor will remain at ON during the time that the program is waiting 10 minutes before continuing and turning on the pump. Adding a wait like that is a good practise, it adds hysterisis to the control system, preventing short run cycles of the pump.

When your program has a Wait statement, make sure it's triggered by a static condition, like a status change. Looking for control events ("is switched on") won't work because it doesn't remain true other than the first time it's detected. One effect is that if the detector turns off before the 10 minutes is up, then the pump won't turn on at all, which is what you might be wanting here.

In fact, you can't "restore" to a previous version. Backups are of your devices and program information.

Rebooting the eisy will usually resolve this issue. You might need to redo the module linking. Check first. The last (bottom) option is usually to remove existing links. If you cannot successfully link it to your eisy, you might need to factory reset the switch first. In that case, also recreate the direct link with the mini controller, though I'd use a scene would be better.

I've never done upgrades from within eisy-ui but that's likely how you would do them, yes.

The best one stop shop for version numbers is in eisy-ui. Set your browser to http://<eisy ip address> This should bring up a black login screen, where you enter your UDI account information. Once in, click on the three little lines at the top left, and then choose "System". You'll see all your version numbers.

Use a variable and two programs. Like this: If event trigger is True Then Variable = 1 If Variable = 1 Then first thing Wait x Then second thing Wait x .... Then Variable = 0

@IndyMike That would work for sending option changes, but not for a PLM replacement, since the motion detector would be sending it's on/off events to the old PLM Insteon address, and doesn't know about my new one yet.

Yes, two antennas: zigbee and zwave. The dongle isn't used for Matter, well not yet. If it does eventually, it would likely eliminate the need for a border router for Thread devices.

Update: I went ahead and replaced my PLM. Another thing I noticed a few days ago is that it was unreliable at sending X10 commands. I only have a couple of X10 devices, but one important one is sending a command to my Ocelot, to trigger an automation routine involving transmitting IR commands. Replacing the PLM is a pain because I have about two dozen battery powered devices (motion detectors, leak and open/close sensors), so I have to go to each one, put it in linking mode, and tap on "write changes" for that device in UD Mobile. Ugh. I then took the bad PLM and installed it in place of the usual one on one of my test Polisys, and tested turning an X10 appliance on and off. It works, but with varying delays, up to 8 or 10 seconds. I saw retries on the Elk ESM1 meter. Put back the usual PLM and X10 commands are very consistent. So trying out sending X10 commands might be another test to add for a suspected bad PLM. We all have a few old X10 modules in a box somewhere!

I don't think you can "learn in" an existing PLM. Part of the module linking process is to learn the module type and create the appropriate node(s).

Yes, I'll wait, to see if this was just a freak one time occurance. For the link count, are you suggesting that I check if the link count has changed, or just if the link count is getting high? I only have about 340 links.