oberkc

I have no experience or knowledge to supect that this is true, but maybe it is my turn to have a good day

I believe the solution from @dbwarner5 is the simplest (thus most elegant) solution. The program will be triggered upon chage of status of ANY of the six switches and evaluated based upon the entire program logic. Problem solved.

Well, in fact I DID get some ambition. Unfortunately, I must have recycled my -994. The only backup device I kept was the Polisy. Sorry.

I have the same recollection about needing the IR "module" for proper operation. If installed I expect it would show up under Help>>About>>Product. I also recall that the IR hardware could be added and removed but I don't remember enough about it to describe how one would recognize whether or not the hardware was installed. I think my old 994 had the IR module and, perhaps, still does. If I get ambitious, I will check.

I can also mean that there is something interfering with communication between valid linked devices. Hopefully, the advice from @paulbates will solve your problem. Troubleshooting communication problems is more trial-and-error, in my experience.

Yes, that is how I understand that the plug-ing should work. The notifications look a lot like this: I also recall that my notifications did not come up at first, but I don't remember what I did, if anything, to resolve that problem. I can tell you that restarting the node server and rebooting the EISY are often methods to solve such nuisances and maybe that was my solution. Once one has this code, I added it to apple home. The single code will add the Insteon devices in your system, but I recall that other devices (z-wave, govee, hue, etc....) may not add as part of the matter node server.

I experimented with adding a hue bulb via zigbee. I remember that it "worked" (I could add the device and it showed up in the admin console) but that the options for control were more limited than when using the hue hub and PG3 plugin. I don't specifically recall what options were missing from the zigbee method, but think it was color and scenes and groups and things along those lines. I am of the same thoughts as @Guy Lavoie ... I prefer the hub/PG3 method and see no compelling reason to change, so I don't closely follow the hue-via-zigbee methods.

Unless I am missing something, I see no reason to put this into two programs. Assuming the wiring to the IOLinc is correct and tested, and assuming that the relay is in the correct mode (latching), and assuming that the low- and high-water sensors are the same sensor, and assuming the sensor will not trigger except at the high and low marks (and not somewhere in-between) I am failing to see why the single program would not work. Use "STATUS" condition for the water level sensor (IOLinc sensor wired to something, I assume). As GuyLavoie points out, the low water sensor will remain set until the water reaches the high point where it will trigger the sensor to the opposite state. Adding the 10 minute wait would not get interrupted as near as I can tell. The only way for the wait to get interrupted would be for the pump to turn on and fill the tank to the high water mark. I agree also with paulbates: I would include a backup plan. It is not worth risking overflow of the tank. I would also be surprised if there is not a standard commercially-available solution to this problem. What is the "tank"? An aquarium? Sump? Water storage? Other?

It might help to describe what it is you are trying to do, under what conditions cause the tank sensor to open and close, and what it is that the program is, or is not, doing that you expect it to do. It is also helpful to see the exact program rather than a paraphrase. Control (switched on) versus status conditions behave differently and can affect how programs work and it seems unclear to me which type of conditions you have in your program. Having said all that, I suspect Guy Lavoie has identified the most likely problem, short of a communication problem between devices.

I was not s sure that “restre” was in reference to going back to an earlier version. I thought it might be in reference to reatoring the individual device. If on right-clicks on it, there is some type of option to re*interview the matter device. I would be inclined to try that.

UD mobile has a "geofence" feature which recognizes the location of the cell phone within a certain radius of your chosen location. Whether that radius can be set to 250 ft, I am unsure. Geofence could be a trigger to perform some action in the EISY such as setting a variable or turning on a switch.

One can do it with a single scene, or multiple scenes. The benefit of a single scene is, in my mind, simplicity. If all you need to do is control a fanilinc with a keypad, it works well and does not overly complicate your device and scene listing and arguably make it easier to visualize. However, if you plan to use programs, ud mobile, or external control (such as alexa, google) then multiple scenes has definite advantages in the ability to call the various fan speeds. What are your intentions?

I just added a new device and continue to get the same message, and I am on v6.0.5. Rebooting is the primary solution...being on 6.0.5 does not solve this problem.

I feel your pain. There is a bit of a learning curve to this, and some instructions are better than others. As others pointed out, from the PG3 dashboard and, hopefully, find your KASA plugin. Then click on it (the name) and look for "more info". Click on that. From there, you should see a "readme" file. Click on that. Hopefully, you will find the installation instructions. Fortunately, the Kasa installation looks relatively simple.

How hard is it to move the chime module closer to the PLM?