oberkc

Well, lets start breaking this down into smaller pieces. Does the keypad button turn on/off when the door is open/closed? (close it via wired button or car remote for testing purposes.) If not, either the sensor is not changing state, the scene between sensor and relay is not set up correctly, or there is a comm problem. Does the LED light on the IOLinc turn on/off when the door is open/closed? Does the ISY recognize the change in state of the IOLinc sensor (the admin panel should show true state)? Double check the scene definition (sensor is CONTROLLER, button is responder, correct?) Start looking for clues. I assume that the "relay follows input" setting would cause the relay to close when the sensor is activated, and vice-versa. I do not think you want that option checked. you should want relay and sensor to operate independently.

DJBoombox... I don't do this regularly enough to know for sure, but I recall a possibility that alexa routines can only be triggered by ISY devices if they are sensors or variables. If you want to trigger a routine from an insteon switch, you may have to create a method in the ISY to toggle a variable when the switch is toggled. Then, trigger an alexa routine from the variable. FWIW, none of my switches or scenes show up as options in the "when this happens" dialog. Edit...I wonder if an insteon switch can be added to alexa as a sensor

I understand that you want the garage lights to come on only as you transition the radius boundary, and only during certain times of the day (sunset-to-sunrise). That was my assumption. Thanks. My suggested approach stands.

What LED is failing to light up? The one on the IOLinc? The one on the keypad button? Another? did you create two scenes? One would have the sensor as controller and button as responder. The second scene would have button as controller and relay as responder.

Assuming that I understand what it is that you are trying to accomplish, I would tackle this problem with two programs... first program: if occupied is true then run second program (if path) second program (should be disabled): if time is from sunrise to sunset (next day) then turn on garage lights wait 30 minutes turn off garage lights

My thoughts, also. So far, the phenomenon has been repeatable. It definitely does NOT seem random.

I do not claim to fully understand the relationship between insteon, z-wave, and the ISY-994. I have a scene with almost my entire interior devices that I use at the end of the day. Most are insteon, but more than a few are z-wave. I just added a new z-wave outlet the other day and added it to this scene. I noticed that, when I turn off this scene, the newly-added device is the last device to turn off, and it is likely 5-10 seconds before doing so. It makes me suspect that the ISY runs through each of the zwave devices within the scene and turns each off individually. This one is the last added, and is alphabetically the last zwave device in the list. I cannot help but wonder if re-ordering the devices somehow would result in response times being different for various devices.

I have not had luck with this approach. It may depend on the brand or version of switch one is using. It may also require the creation of a "button press node" and using that as a control condition. I am still not satisfied with z-wave switches as much as I am with Insteon. I also experience measurable delays in zwave devices. I just live with it. Most of my zwave responders are outlets, and they turn off at the end of the day. Delays do not bother me that much.

A couple of observations.... I don’t think the PLM (or lack thereof) will affect the ability to find and log into to ISY. you say that you are plugged directly into the comcast modem. Unfortunately, I have never used such a modem, but I cannot help but wonder if this modem is also a router. Do you knw?

I am not sure whether this will help (my guess is that you have something more sinister going on here), but I have almost universally had to run the alexa discovery process TWICE eac time I try to add new devices. I also think it might be worth mentioning...I recall a “refresh” button in the portal for alexa connectivity. It might be worth a try.

I think this confirms your problem. This program runs once per day, always runs TRUE, and never runs FALSE. The status of this program will always be true. Given this, your first program will always execute true when triggered at sunset.

Generally, I would say your understanding is correct. If it is sunset, sunrise, or anywhere in-between, the program should run true only if one (or more) of your lights are switched off. The one exception that catches my attention is your condition: "'timer bedtime shutdown' is true" Of course, you did not post that particular program, so I can only speculate at this point.... Keep in mind, a program being "true" is not the same thing as a program running. A program status will be true based upon the last action executed being true and remain true indefinitely or until it runs again and runs false. Look at the status of that program right now. Is it currently true? Have you ever seen a false status for that program? Feel free to post that program and let us confirm this as a potential problem (or not).

Yes, but you also said you use the "default" alerts. (Unfortunately, you have not shown the notification or program.) Rather than using the default text, why not create your own notification, using whatever language you desire? Trigger this notification from a "trouble" condition.

unfortunately, I don't use an elk. Were this me, however, I would be experimenting a bit. I would have two programs: one triggered by "trouble" and a second triggered by "violated". I would watch to see when each program is triggered and whether it is consistent with actual elk status. If so, then I would simply create specific notifications for each type of occurrence and be happy.

The syntax does not look familiar to me, but the first thing I would look at is the content of your notification called out in THEN action. What notification are you sending? As an aside, why are you waiting zero seconds in the ELSE action?

I have purchased everything directly. I recall folks complaining of receiving older versions and trouble with warranty coverage when purchasing from amazon or other.

Theoretically, insteon switches communicate via powerline and radio. I don’t know that number of sub-panels is a major factor regarding insteon comms. You are on a single transformer. Communication between two legs of your electrical system is typically handled by the RF comms of insteon. Inseon switches cannot be combined with standard switches to control a single load. Each switch in a multi-way must be replaced. It is possible, but would depend on number of insteon devices present, distance between them, contructuion and layout of house, etc. In general, the more insteon devices, the better performance of the insteon network. Neither insteon nor zwave will impact your wifi system. Neither connects directly to wifi.

I wonder if the missing appliance module caused a flurry of insteon activity which subsequently caused other insteon commands to be missed.

Just got one a few weeks ago and does not connect to hue emulator as far as I can tell. Still, for me, music (sonos) control was also important and it does this well.

strange. I have no explanation. Is this the case for all of your scenes?

I have been on 5.x for a while and am currently on 5.3.something. I am still able to add a program action to turn a scene on/off/etc... Is it possible that you have a version mismatch between your firmware and UI?

I guess yet another case where the Mac thinks it knows better what you want than you do.

Assuming that the switches are still working, if the status is not consistently updated in the admin panel, I would be looking at communication problems. Obviously, if the ISY cannot see the status changes, it will not trigger programs. Perhaps other electronics were affected by the power failure and are affecting insteon communications?

Have you confirmed that the programs have not been disabled, for some reason?

To clarify also, system variables for day-of-month, month-of-year, and year, were newly introduced in the 5.x build, if I recall correctly. However, if you are into the 5 software, an alternative would be to create a variable and use a daily program (I have included this in my 3:00am cleanup program) to set the variable to day-of-month. Once you have done this, you could then create a program such as: if newly created variable (day of month) = 1 then charge batteries.