apostolakisl

I'm pretty sure it doesn't matter in most all cases. It isn't possible to test without rebooting my ISY which I don't fee like doing, but . . . 1) IF control programs will trigger regardless of what if anything is listed in the current status at the time of the "control" being sent. So there will be no impact at all on those. 2) IF Status programs I think will still trigger when it goes from unpopulated to anything. This is worth testing. You might get an unexpected run of an else clause on a program such as If status is on Then whatever Else somethingelse In the above example, the else clause might run going from unpopulated to off. Since you expect the else to run with a change in status from on to off, not unpopulated to off.

Good to hear. I'm not sure how the hub is doing this either, but it is best to not have multiple controllers. I use agave and it works nicely. The developer is fairly active at making it better as well.

I believe leak sensors are a once per day status reporting device.

yes, heartbeat. A query won't do it and for at least a while they will be unpopulated after an isy reboot.

The "issue" with no status is not really an issue. Here is the deal. Battery devices would burn through their battery very quickly if they were normal Insteon devices listening and responding to all the time to all the other devices in your house (including isy/plm). Battery devices only participate in Insteon commands when they choose. The choice is written into the firmware on the device and is designed to allow for proper operation and long battery. For the most part, they are transmit only devices. They will transmit a heartbeat at a time of their choosing, and they will transmit whenever their purpose is met (ie when a water detector gets wet or a motion detector senses motion). ISY does not store device status through a power cycele (which makes sense since the status could easily change while the ISY is off). When ISY comes back online, it queries all devices for their current status. However, battery devices are not listening for that query so they do not respond. The battery devices must be "woken up" either by you manually doing it or by the designed trigger (getting wet). Having ISY show status unknown on the device should not impact your program.

Hmmmmmm. Well I am at a loss. I was hoping it would only happen when you rebooted the relay. Another idea would be two swap the two relays and see if the problem follows the relay or stays with the application.

I don't know for sure, not owning one of these, but current sensors ingeneral use induction to detect current and it is certainly possible that if a sufficient amount of current is induced within the current sensor induction coil, then it can use that as its own power source. Basically it is a transformer.

OK, it's becase your 2476D is quite old. When you change the settings, you have to reboot the switch for the changes to take affect. And by reboot, I don't mean turn the switch on/off, I mean pull the tab or shut the circuit breaker off. The newer 2476D's and all the dual band ones don't require a reboot.

Sorry, you are correct. You do have to create a dummy scene and put the device in it as a controller. Or, if the device is already in another scene as a controller, you don't need to do that. In 4.x firmware, I believe when you do "adjust scene" you will see not only scenes in the drop down, but individual devices listed as well. You select the individual device as the "scene" (yes, I know it is not a scene), and then again a second time you select the device. It really is a very bazarre thing to program and it is different in 5.x so make a scene, lets call it "dummy scene" and put "my light switch" in it as a controller. Then in your programming do the following. In scene 'my light switch' adjust 'my light switch' on level to 25%

The fact that deleting the device from ISY and re-adding fixes the problem leads me to believe there is some issue with the relay itself, maybe the links are corrupted after a power cycle. There isn't any reason that removing then re-adding the device would change the behavior of a program. To test this 1) reboot ISY and not the relay 2) power cycle the relay and not ISY 3) power cycle both at the same time, but not the whole house Which if any of these 3 things reproduces the result. And I agree that it is a good idea to put ISY on a UPS (not the PLM). I have mine set this way.

If you reboot ISY only (power cycle it) but don't power cycle the whole house, does it still do it?

A leak sensor that didn't get wet shouldn't need to be reset. I would very much doubt that leak sensors respond to the scene "on" command so it would presumably still be off. If any device in a scene sends an "off", then the whole scene shuts off. My guess is that a leak sensor that is in a scene simply does not respond to that "off" command since they must be reset locally. A leak sensor would really only work properly if it could only be a controller. There is no logical reason for a leak sensor to respond to anything but locally getting wet. Having a leak sensor respond to an on/off remotely is like saying the leak sensor can control its wetness, makes no sense. Assuming standard Insteon logic, any leak sensor in the scene that sends an "off" would turn the scene "off" and thus turn the pump back on. Now, my question would be, if you reset a leak sensor that was never tripped, does it send an "off" or does it just do nothing? If it sends an "off" no matter what, the scene would turn off even if another leak sensor were still wet. Unless, of course, a wet leak sensor keeps periodically sending "on" commands even if it isn't reset (which would be how I would make it work).

A device pressed locally always responds according to the local on level. You have to change that. There is no need for a scene here at all. A scene with one device serves no purpose (except with kpl buttons, but that is different).

Whaaaaat? I don't know if there is something special about leak sensors, but scenes can have as many controllers as you want, anywhere from zero to every device in the scene. The converse is not true, a device can only control one scene, but there is no need for two scenes here. I don't see any need for and/or logic. It is a simple premise, if any leak sensor triggers (sends an "on") the scene turns on. From your description of "resetting" a leak sensor, I'm assuming that leak sensors only send an "off" when manually reset (which is probably a good thing). Run at startup would not be the issue. Once startup is complete, changing the status of the relay would not trigger the program. Frankly, I don't see how this program is triggering since it should only trigger on a change in status of one of the leak sensors. Do you have a program not listed here that calls this program? ie does a "run if", or "run then".

I don't have any leak sensors, but I looked at the manual and it appears that thy can be linked directly to other insteon devices just like usual. So why use a program? Just create a scene with the relay and the leak sensors and put the leak sensors as controllers. It looks like you have the normally open version of the relay, so you need to set the scene "on level" for the relay as "off" (yes that seems weird, but it works) This basically means any time the leak sensor is triggered either from wet to dry or dry to wet, the pump shuts off. This means that once a leak sensor has gotten wet, you would need to fix the leak, dry it off, and then manually turn the relay on. It would not turn back on automatically . .. which is a good thing in my mind. Power failures would have no impact on this setup. Except I suppose if you had a leak start during the power failure, then power came back on, it would not turn the pump off since the pump relay would be unpowered during the power outage and not get the signal from the leak detector. But what are the chances of that? I suppose you could set up a program that when isy reboots it shuts the pump off to be extra careful. EDIT: Just noticed you have the NC relay (it was in the title ). I made my NO assumption based on the fact that your program tells the relay to turn "on", which would open the connection and turn off the pump. Could that be your issue?

Why don't you make a nodelink for it? I know you can do it. The PITA with CAI is just that it has no wifi so you have to pull ethernet to it or use a pricey wifi adapter. I assume it runs some version of linux? Which I'm thinking means you can write the node software right on it rather than having an intermediary.

I found this https://www.adafruit.com/product/3010?gclid=CjwKCAjw_8jNBRB-EiwA96Yp1nJLOazeLas9kCjWeW1cY--9yIWVOCdwdF0ymhyEVf55xaljeH9uURoCyJQQAvD_BwE What board are you referring to? How do you interface that with ISY? The nice thing with cai is that nodelink makes it "native" on ISY.

1) float switch $5 http://www.ebay.com/itm/Liquid-Water-Level-Sensor-Horizontal-Float-Switch-Pool-Tank-On-Off-Full-Empty-/182168941294?hash=item2a6a1d72ee:g:UAIAAOSwMf1ZoFiM This is to alert you if water gets too high. 2) Relay with mounting $10 http://www.ebay.com/itm/JQX-13F-110-120VAC-Coil-DPDT-8-Pins-Electromagnetic-Power-Relay-w-DYF08A-Socket-/271344249983?epid=1038301975&hash=item3f2d60ac7f:g:UU8AAOSw8GtZSfsB 3) Pressure Switch $10 http://www.ebay.com/itm/RDEXP-Male-Threaded-Water-Pump-pressure-switch-control-Grey/272234567911?_trkparms=aid%3D555014%26algo%3DPL.DEFAULT%26ao%3D1%26asc%3D41375%26meid%3D141fa7744262455db79f1d79f60563a7%26pid%3D100506%26rk%3D1%26rkt%3D1%26&_trksid=p2045573.c100506.m3226 4) CAI $45 https://www.amazon.com/gp/offer-listing/B00U31CWEI/ref=dp_olp_new_mbc?ie=UTF8&condition=new Throw in a couple bucks for odds and ends and you can monitor it all for $80.

You really don't need to get so complicated and measure current. Since the pump itself has a simple on/off switch (the float switch), you can easily just wire a relay to that same output and effectively be monitoring the float switch. If you have an always on PC or RPi, you can put ioguys nodelink on it and put a webcontrol board directly onto an ISY (5.x firmware only). It works well. I have this setup with using a reed switch that webcontrol monitors and nodlink synchornizes to ISY. webcontrol has 8 of these inputs so for $40 you can monitor quite a few things. A relay and a float switch and a pressure switch together might cost another $40?

An alternative to using a synchrolinc which avoids running power through the syncrolinc itself is to use a relay and a I/O linc. The float switch closes the circuit to the pump. You can wire a relay in parrallel with the motor. When the motor is on, then relay is closed. Connecting the relay to the io linc will let you know when the relay is on or off and thus when the pump is on or off. For further knowledge, you can put a pressure switch on the pump outflow and connect it to an io linc. Now you will know that the pump is actually pumping water. A combination of an io linc on the power to the pump and to the pressure switch will tell you if the pump should be running but isn't (pump burned out). And furthermore, you could put a separate float switch higher up to trigger an io linc in the event that the water is getting too high. And if you are going to do all those io lincs, you could instead go with a webcontrol board and have 8 inputs all in one device. However, you need to get internet to the webcontrol board.

You can use "status" If status of kpl button is on Then whatever If the KPL button always tracks the scene, then this will always work. It won't work if you have the kpl mixed into some other scenes where it responds to other scenes. But I bet that that is not the case.

Just to re-iterate. You need to get rid of the "to" time. In the winter, if sunrise happens to be after 8:55 your program won't run at all. You don't need a "to" time since the program will end on its own once the repeats finish. Unless, of course, you actually don't want the program to run if sunrise is after 8:55. Then you've got it right. Also, if sunrise is at something like 8:54:45, then your program will start to run, but then terminate at 8:55 prior to completing the 12 repeats. The light will stay on or off depending on whether it was on or off at 8:55:00 as it goes through the repeats. It appears that you want the light to finish in the on state, so if it happens to be off, then it won't be what you want.

ISY is on UPS. my PLM is not.

1) Install self signed SSL on both ISY's. http://www.universal...urity Guide.pdf Be sure to fill out all the fields with something. 2) Install network module on sending ISY (go to help/purchase module) 3) Port forward your router on receiving ISY to your ISY (port 443) 4) Setup network resource using REST command. I have blacked out the authentication and my URL name. This REST sets a state variable at location 1 on the receiving ISY with the current temp. The 2/1 in the path means "state variable/spot 1" Of course you can substitute anything you like, for example, it could turn a light on, run a program, whatever.

Yes. You can set the two ISY's to use REST between them. The sending ISY needs the network module and both ISY's need SSL (self-signed or paid) (be sure to fill out all the fields on self-signed . . .I learned the hard way). Set up dynamic dns for the receiving location so you don't have to worry about your IP changing, then write programs to send a network command using REST upon whatever it is that you want to know about. You'll also need to port forward 443 on your router to your receiving ISY. Of course if you want bi-directional then both ISY's need all those features. I have one ISY set variables on the other ISY which initiate activities on the second ISY.