smokegrub

I tried accessing the Admin Console and rapidly clicking on OK for the two problematic devices. That worked and the Admin Console loaded and did not freeze. Both problematic devices showed red exclamation points adjacent to their names in the device tree. I tried querying each device--no change in status. I tried Restore then Undate--no change in status. I assume I am going to have to wait until I return home and air gap both. If that doesn't work I will factory reset and restore. Any other ideas?

I am away from home on vacation. When I access the Admin Console it proceeds to a screen which says it cannot communicate with a device and hangs at that point. Clicking on the OK button does nothing. Neither does any attempt to use any Console feature except to Quit the app. I can access the ISY successfully using HAD and it says the ISY cannot communicate with two devices. I checked to see if I could restore the devices using HAD but I cannot find that capability. Rebooting the ISY is not possible until I return home. I can access also by MobiLinc. Any suggestions?

Stu: The light switch is interimittent. How do I proceed in bypassing it?

Current Status: Fan (3 Speeds + On/Off Using Pull Chain) Lights (2 Banks of 2; 1 Pull Of A Different Pull Chain Turns Bank 1 On; A Second Pull Turns Bank 1 Off And Bank 2 On; A Third Pull Is Supposed To Turn On Both Banks (Works Only Occasionally); A Fourth Pull Turns Off The Light. Objective: Fan (3 Speeds + On/Off) Lights (Turn On/Off Both Banks Simultaneously) Is it possible to do this with an On/Off KPL and a FanLinc?

Going to remove, factory reset and relink both. Can't do one until a week from now because it is remotely located. Will report back. Thanks for all the help.

Perhaps so, but doesn't it seem unlikely that both would be defective and behave in precisely the manner? Plus each is on a separate ISY. The heartbeat node in both indicates that the heartbeat is always on. Unless, of course, the fact that it is always on does not mean the signal is being sent continuously.

Techman: I have done that. Do you know if there is a way to set the time interval for the device to report heartbeat?

The batteries are Energizer Ultimate Lithium. Tested 1.75 volts in a replacement of the same group. The devices are 3415 REV 1.8. One device is only occasionally activated; there other was never activated during a 5 month period and went dead! My suspicion is that the batteries are being consumed rapidly because the heartbeat is constantly on. I have searched for a way to have the heartbeat only report once each 24 hours but there is no Options button as with the Hidden Door Sensors. Yes, I have reset the devices. #4 - No ISY Firmware and UI" Both 4.3.26

Adding to this post, I have installed 2 Open/Close sensors. The first had a dead battery in less than 5 months. Within less than a month since installing a fresh battery I have received a low battery notice. Within about 2 months the other device is also reporting a low battery. The only thing I see that could cause this is the heartbeat stays on all the time. Thoughts? Perhaps the answer is in the foregoing, but if it is I missed it.

Wrote a program using this approach. Will see if I did it correctly. Thanks.

I am a bit embarrassed to seek help with what should be a simple program, but I am stuck. I have a scene managed by a KPL button. When that button is pressed it turns on an IOLinc. The IOLinc, when on, sends power to an irrigation controller which executes its irrigation program beginning at 0500 and running until approximately 0830. I would like to have a program that: If the KPL button (or IOLinc) is On Turn the KPL button (or IOLinc) Off at 0900 the following day I can't figure out how to set the 0900 for the day following when the KPL button is pressed. I would like for the KPL button to show as OFF following the program running. This would safeguard against the pump staying On.

Thanks.

I will be back home in a week. I will dig into this thoroughly when I am onsite. Also, I am aware that I could write a program to turn the lights off a minute or so after they turn on but that is a bandaid rather than a fix.

I moved the query to 4:00 AM and, to be precise, the lights turned on at 4:03:33 whereas they turned on at 3:03:33 when the nightly query was set at 3:00 AM. Seems evident that the query is somehow causing a scene to trigger.

Duh! Thanks, Larry. At age 71 I frequently overlook the obvious. Will let you know how it goes.

The same two lights were turned on at the same time (3:03 AM) last night. I checked all my programs and can find no programmed actions for that time. The only thing even close is the Query at 3:00 AM. I will wait until I return home to do hands on research. Since this developed coincident with activation of the Trip programs (none of which activate these two lights), it will be interesting to see what happens when I deactivate those programs. More later.

I am away from home and managing things remotely. I plan to wait until tomorrow and see if this repeats itself again. Weird. I will pay close attention to when the program controlled by KPL A runs and will report.

Sorry for the confusion. When I activated a program called Trip and left our home two lights normally controlled by a KPL button A were found ON each day and had to be manually turned off. The first thing I did was check the subprograms controlled by the Trip program to see they might be triggering KPL button A (KPL A controls these two lights). None of the subprograms had any reference to KPL A nor the lights in question. I next turned to the data showing when all programs last ran. There I saw that the program controlled by KPL A had run at 3:03 AM. Seeing that, I then knew why the lights had turned ON. I wondered if the 3:00 AM Query might have somehow caused the program controlled by KPL A to run. That is my question. Could the Query have caused the problem? If so, how do I troubleshoot?

I have a program that runs with the press of a KPL button. We are away from the location at present and a Trip program is running several sub programs to create the illusion the home is occupied. The Trip program has nothing to do with the KPL button and program that is running on its own. I checked the Program Summary and it last ran at 3:03 AM. That suggests the 3:00 AM query may have something to do with this behavior. If so, what can I do to troubleshoot?

Andy, I am obviously doing something wrong. Would you be so kind as to draft example programs to handle two devices: House (37.D9.45 and Garage (38.D10.46)?

Thanks for the comprehensive feedback, Paul. Very informative. I appreciate very much your taking the time to put it together.

At the current time I am using an IOLinc to simply turn my old irrigation controller on and off. The controller is set up to begin irrigating the lawn at 0600 hours following activation and will continue irrigating each day unless I turn the controller off using the IOLinc. I would like to move past that level of control to something that will permit me to control individual zones and a variety of programs and irrigation options. I am considering the Blossom controller and the EZFLORA. Is there a site where I can see the control options offered by the ISY for the EZFLORA. I would prefer staying with that device and control using the iSY.

After bedtime, I plan to use it to alert me of door openings and ultimately of low temperatures measured by a stat at a remote location or motion at same. I foresee lots of potential uses both here at home and at a remote location.

Teken: I fear my remark was misleading. It was intended to indicate that I was smiling at the irony of the feedback I got when I posted. As an aside, however, I find it amazing that a company, with buyers waiting, is so indifferent at getting this information to UDI.

You must have somehow seen my smile.