oberkc

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?

I would be doing some investigations to see if I could find any further clues. Without those, we could only make guesses. Also, it would help if you describe your setup with a little more detail, especially the relationship between your switches and keypads (scenes? programs?) One thing I would look for are whether the EISY recognizes changes in switch or keypad status when you manually toggle them (in other words, does the admin console display the correct status as you toggle the switch)? Another thing I would look for is whether the switches and keypads respond to commands issued from the admin console. Also, you state that this problem exists for "any" switch for an "outside light". Do you have more than one outside light? Does this problem exist for all outside lights and no other lights?

Well...I am not quite sure what you are trying to achieve here, or what hardware limitations exist, that requires (what appears to me) to be a relatively complicated set of programs. One thing I noticed, however, is that the first program calls to "Run Program 'Motion1 - Timer Set' (If)" but when I look at the program 'Motion1 - Timer Set' , there is no (if) clause. But I tend to think like @Guy Lavoie , if it is working for you, I don't see a reason to modify the programs.

Well, I am quite confident that you can use a program to increase or decrease brightness or color or tone, I am unsure how the innovelli switches relate to the hue bulbs or weather you can adjust the response to the inovelli switches.

I once tried using a Hue bulb with the Polisy via zigbee. It did, in fact, connect and I was able to control it. I found, however, that the level of control and features did not match that of using a hue bulb with the hub. I have also used the hue bulbs/hub with network resources. This is quite reliable but does not provide the ability to use hue devices as a node in scenes. Given this, I prefer using the hue hub and hue node server. I have no experience with the inovelli switches.

If the suggestion from @larryllix does not work, make sure you have rebooted your EISY.

And, having just committed to avoiding new matter devices for a while, I may have to try one next time I happen to be near an Ikea store. I am so fickle.