oberkc

I think some of my older keypads are v2.D. I have never had any luck getting LED brightness of the older keypads changed via the ISY (regardless of software level).

There are Lots of internet-enabled thermostats out there, but I suspect that the fact that rschneid posted his question on a UDI/insteon/ISY-994 forum suggests interest in integration with the ISY-994. Recommendations for thermostats without such capability are, in my estimation, non-responsive.

if you simply want to turn hot water off at 1am and on at 430am, a simpler approach might be: if time is from 1am to 430am (same day) then turn hot water off else turn hot water on One benefit of this approach is that it is more tolerant of power failures during the period between 1 and 430.

For whatever reason, I found the morninglinc to be more marginal in communication than the rest of my devices. Perhaps your problems are completely unrelated to setup or firmware version. Have you tried temporarily moving the morninglinc closer to your PLM?

In addition to the access point suggestion by LeeG (which I second), there may be benefits to using a "program" rather than a "scene" to control brightness, but this has no effect on what you need to purchase. While you did not mention it, is integration with your Elk system important? If so, be aware that this requires an additional "purchase". There is an add-on software module required with the ISY-994.

The most common methods are: a) ensure you have communication between legs of your electrical system. This is typically assured by using two dual-band devices and verifying on opposite legs via the process described in the user manual identification and elimination of devices which interfere (either actively or passively) with insteon communication. There is no easy way to do this. First is to identify suspect problem-causers. Unplug suspects and see if communication improves (if so, filter that device). Initially, consider computer equipment, including UPS and surge suppressors, TVs and AV equipment. c) addition of insteon devices, to repeat signals to distant locations. d) reading of prior posts on this forum to learn the various methods and ideas.

Such as with a keypad button (which, I submit, is the most common of "clients"). Perhaps, someday, we can have a means to easily duplicate a configurable keypad function on a tablet, and use them in place of a keypadlinc. In my mind, we are not quite there yet.

It matters to me, where I use scenes to control status displays, and prefer "ON" to indicate open.

A progam is the best (may be only) way, in my mind. The logic, if not exact wording, is pretty simple If control motion sensor low battery is switched on then send email message else Of course, you have to initially configure the email message.

Cartman413 Your post, and the details you included, suggest you have a good sense of what is happening. The fact that the led is going on and off, and that you keypads are also responding, suggest that the sensor is working, and properly linked via scene. If this were me, I would be focusing on factors that would make communication with the PLM problemmatic. What other devices and gadgets do you have plugged into the same outlet and circuit as the PLM?

As usual, LeeG and Xathros were correct. The part that I missed was that the proposed second program would trigger at sunrise and ALWAYS evaluate as false, regardless of any light status. When this happens, the wait statement will, in effect, halt and no further action will take place (empty else statement). Yes, this is a pretty remote scenerio, but no need to adress it from a programmatic standpoint.

I stand corrected

Are you sure? If the lights were manually turned off during the night, the status would change at that time, triggering the wait program. If, at sunrise, if the lights were already off because of a manual intervention, there would be no status change, thus no trigger and no reevaluation. Am I missing something?

I have been staring at that first statement and I must admit that I am still confused. But...If you think you have it doing what you want, then I am happy.

One thing that you may have to watch out for with this second program is the possibility that someone turns off the nightlight less than ten minutes before sunrise. I am concerned that, were this to happen, the wait period would continue and turn the night light on AFTER sunrise. The simple solution might be a slight modification to the second program, such as: If From Sunset To Sunrise - 10 minutes (next day) And Status ‘nightlight’ is Off Then...

Your program will do nothing to enable the C button to control the pump. Perhaps it would be best to describe what it is you want the program to do.

That is what I suspected but was not sufficiently confident to suggest it. If so, I then wonder if there is a difference between "Status 13.83.0d.b is on" and "status 13.83.0d.b is 100%". That is the only thing that caught my attention. I suspect there is no difference. I also suspect that it may not even be possible to select a "100%" (versus "ON") status on a secondary button. Otherwise, I expect the program to do exactly what he said he stated he wanted (which may or may not be what he really wanted).

This looks about right to me. Does it work? If your keypadlinc is a dimmer version, I wonder whether there might be complications if less than fully ON (100%). I forget whether secondary buttons can have a status of something other than OFF or ON, but this would be easy enough to check, if you are so inclined.

Obvious things to look for: a) have you saved the changes to your program? Do you see little green arrows in your program listing? do you, or do you not, see in the event viewer, the command to turn on the kitchen door light? c) can you turn on the kitchen light from the admin panel? d) is the program disabled? Is the program in a folder that is disabled? e) what is the status (true or false) of the program? When was it last run? Is this the same time as receipt of the motion sensor signal? There is little to go wrong with the program, itself. There is something else in play here.

Yes, that is exactly what I meant. Perhaps a combination of two (aligned in such a way that only a car could block both, with some ISY program logic requiring both, along with a continuous minute, as you suggest. I don't think these are very expensive. Other topic has explored the use of a cell phone as a surrogate for the car. Perhaps some type of logic such if cell phone connected to the wifi and garage sensor gizmo activated and second garage sensor gizmo activated then do whateve

Maybe I misunderstood, but I thought the original request was to detect whether the vehicle was IN the garage, not whether it is coming or leaving. Still, if the sensor was off and suddenly turned on, I think one could reasonably infer that the car just arrived. Obviously, a combination of sensors and logic would be required to ensure that it was a car, and not a lawnmower (or a person), but this is an issue not necessarily unique to this particular solution.

I wonder if one of those garage door opener safety sensors, in conjuction with an IOLinc and power supply, could be adapted for this purpose?

My gut reaction is to solve the communication problem. Absent of that, I would try to understand the communication problem a little better. It is possible, in my mind, that the reason that your keypads are missing the programs is because the control/status signals are not getting TO the ISY. If this is the case, no amount of programming (short of a query) will solve this problem. I thought filterlincs were plug-in devices. I am curious what you mean when you say you have one "at the panel". Are you saying that your keypads are on filtered power!? This could impact communication. I just ran out of time, but I thought I would offer a few thoughts.

There is no "flash" command in insteon, so the only way I know to do this is through a program. I forget the exact program language, but it is something like: repeat three times turn light on wait x seconds turn light off

I would take a slightly diffent allocation of tasks, triggers, and programs: If Control 'Main: Trigger Drive-Opened' is switched On then Resource 'Driveway Alarm Beep' Send Notification to 'Rich Email' content 'Driveway Alarm Alert' Run driveway alarm (if path) else Modify your driveway alarm code, and disable this program: If From 6:35:00PM To 6:35:00AM (next day) Then Set Scene 'Outside' On Wait 5 seconds Set Scene 'Outside' On Wait 25 minutes Set Scene 'Outside' Off Wait 5 seconds Set Scene 'Outside' Off Else - No Actions - (To add one, press 'Action')