K-bert

I apologize, it has been some time since I added code to a post. I have also made the changes to my programs that you suggested. Here they are: Variable Control Rear Door Open - [ID 00F6][Parent 00AF] If 'Devices / 7-Doors / Back Door (On=Closed)' Status is Off Then $sRearDoorOpen = 1 Else $sRearDoorOpen = 0 Lights On Door triggered backyard light On - [ID 00B7][Parent 00AF] If From Sunset To Sunrise (next day) And $sRearDoorOpen is 1 Then Set 'Scenes / Outside / Path Lights' On Else - No Actions - (To add one, press 'Action') Lights Off Door triggered backyard light Off - [ID 00C2][Parent 00AF] If $sRearDoorOpen is 0 Then Wait 5 minutes Set 'Scenes / Outside / Path Lights' Off Else - No Actions - (To add one, press 'Action') The weirdness comes in with the motion sensor. I thought that it worked that so long as the Sense #1 wire was set to line voltage that the micro module would turn on, regardless if it were already on or off. Like using the mobile app to turn on any Insteon switch pressing the on button locally on the switch would not change it. I know that without the micro module in place the motion sensor provided line voltage to the lights so long as its light sensor deemed it dark enough and it detected motion. It then keeps the line voltage to the lights for as long as it is set to, which is changed by the dial on the bottom. Mine is about five minutes. What is happening to me is when the micro module is already in the On state activated by the door opening and then I step onto the porch the motion sensor puts line voltage on the Sense #1 wire and the scene is being turned Off. Looking at the manual for the micro module I am wondering if I have is set to "Single momentary" instead of "Latching" mode. The more I think about it the more adding a second micro module may be the best way to get my desired outcome. As other have mentioned separating the sensing and the control is the best way to go. I would like it to come on for five minutes when motion is detected. The motion sensor turns the lights off after its built in timer regardless if there is still motion, but it will turn them on right away again if there is. I would also like them to come on when the back door is opened and then off again five minutes after the back door is closed. However, if I were entertaining in the back yard it the motion sensor would detect us and send an off signal to the module after five minutes, which would override the program keeping the lights on by monitoring the back door. I think the best course of action is: Acquire second micro module Wire second one in so it senses the motion Turn down the time the motion sensor provides line voltage to the module to keep triggering a motion detected program to set a variable Uses a program that turns on the light when either the back door is open or motion is detected Use a separate program to turn the light off five minutes after the door is closed or the motion detected variable is zero The program in step two I would probably set to set a variable to 1 when motion is detected, wait a minute and set it back to zero. This would start the countdown in the program in step 5, but if motion is detected again in the next four minutes it would reset the off program keeping the lights on so long as there is motion. Sorry, I realize I just did a stream of consciousness dump. K-bert

Its a possibility, but the cost of two outdoor smart floodlights that would fit into this fixture is not much less than a second micro module, and in some cases much more. At least according to my quick internet search. I also currently only have Insteon and z-wave devices in my house. Depending on which type of smart bulb used I would have to get some controller hardware that polyglot can talk to.

I have lived with it without having the door control for this long, so I can live with it in its current configuration for now. I will play with some options and programs and see if I can get it working like I would like to. Otherwise I will pick up a couple more micro modules when my wife isn't looking. K-bert

I am not arguing. It is not an insteon motion sensor. It is a motion sensor that is triggering an insteon micro module. The micro module then controls the lights. As I mentioned before there is no way that I know of to prevent the output of the micro module from following the input, or sense wire. If I could pulling apart the sensing and control would be child's play. The only way I can separate the motion sensor from the lights in this setup is to add a second micro module. Because this is retrofitted into existing wiring I can't use the micro module at the sensor to detect motion and a switch on the wall inside to turn on the lights as there would be no power in the electrical box where the light is for the micro module. I also cannot use an insteon motion sensor as it simply would not survive outside in our harsh winters. K-bert

And I can now confirm that adding the condition in the "If" part of the program did not work. As before the lights came on when the door was opened. When i stepped out the lights went off as before, but then came back on as expected. However this continued with the lights turning off and on in about one second intervals. My neighbours must have thought i had a child flipping the lights on and off or something. I was able to disable the program in the mobile app. I left my laptop at work so i will give it another try this weekend.

The only reason I cant do this right now is that the micro module detects the motion sensor output and controls the lights at the same time. So far as I know there isn't a way to disconnect the output (Load) from the input (Sense #1). I could easily do this if I had a second module in the light so one would detect the motion sensor output and then the other control the load. K-bert

And of course I thought of this after posting my reply: If I simply add another argument to the program with "And Micro Module Status is Off" to the program it should turn the Path Lights scene on when the door is open and turn in back on if the motion sensor turns it off. K-bert

Thank you for your replies! I don't want to crank up the time that the motions sensor is on for because if I have a program turn the light off after five minutes and then someone else is in the back yard the motion light will not re-trigger the micro module until the time on the motion sensor has passed. I took a look at the options for the module in the admin console the only thing I have changed previously here was turning off the LED. Its in an enclosure so it will never be seen anyway. There is an option to set it as "Line high always On; Line low always Off" Since I know that sending a high from the motion sensor turns the light on when it is off and now apparently off when it is on I wonder if I should check this option. The program I am using uses a variable called "sRearDoorOpen". I have it do a some other things in the system like turn the humidifier off if the door is open long enough to prevent wasting water. A screen grab of the program is attached. K-bert

When I first moved into my house I replaced the light by the rear door with a motion activated flood light for security reasons. Two years ago I built a detached garage in the back yard. In the winter months the back yard dark in the mornings and evenings. As such when the garage was built I installed two lights on the side of the garage to light the path around it for taking garbage and recycling to the bins in the alley. I automated this using an on/off switch for the lights in the garage, a micro module in the motion light, and button on a keypad in the house. I called the scene "Path Lights" The on/off switch is the responder in the scene and the micro module and button are controller/responders. The way I wired up the module is in the attachment of this post. I recently acquired an I/O module that is in the basement for controlling the humidifier on the furnace. I used the security rough in that came with the house and a magnetic sensor to connect to the input of the I/O module. This lets my EISY know when the back door is opened. I wrote a program with the conditions "if between sunset and sunrise (next day) AND back door open" then turn on the Path Lights scene. This worked great during testing. The scene turned on when I opened the back door. However, yesterday when I took some stuff out to the garage the lights came on when the door opened, but when I stepped outside and motion was detected the scene turned off. I shrugged it off at the time, but then it did it to me again this morning. The motion sensor should provide a latching signal to the micro module but having a program to turn the lights on seems to have reversed the on - off operation of the module. Is there a set up option I should change in the micro module? I am currently using the built in timer on the motion sensor to keep the lights on for about five minutes so it should be providing an on signal for that whole time. And because someone might ask: the reason I am not setting the I/O module as another controller to the scene is that I do not want the lights to come on when it is still sunny outside when the rear door is opened. K-bert

I had the "no proxies available" in my UD Mobile this morning before leaving for work. I didn't do anything to fix the problem. When I arrived at work I logged onto my home computer remotely and opened the admin console. Everything looked fine there. I checked the mobile app again and it was all good. I did nothing to actively try and fix it.

Thank you for the reply. That was the issue I had before and I was able to get everything running then. This new issue seems to have sorted itself out. I did have to generate a new API and put that into PG3. It then took about an hour to fill in all the weather conditions and forecasts last night. This morning it seems to be working fine. I am still using the free version. On my account at OpenWeather I have limited the number of calls my account will allow to prevent crossing over into where I need to pay for it. K-Bert

I have used OpenWeatherMap for a few years now and only had one problem which require I make a new API key. Now it is not updating at all. The current conditions haven't changed since two days ago. Same with Forecast 0. All the other Forecasts are blank. I went to OpenWeather and noticed that my Free Plan now has these limits: Hourly forecast: unavailable Daily forecast: unavailable Calls per minute: 60 3 hour forecast: 5 days So is this a problem with what I have set up in my system or has OpenWeather clamped down on what those of us who do not pay a subscription can see. Also not sure why I am not getting updated current conditions. K-Bert

My router set up has worked for years and nothing has changed. Pretty much everything is set to a static IP so I don't have to worry about conflicts. I did call my wife and tried controlling devices both through the admin console (remote desktop to the home PC) and the mobile app. It was all working. I wouldn't be surprised if the PLM is going bad. It is about eleven years old. I purchased it shortly after moving into the house. It is a USB PLM that I used with a Raspberry Pi running a free home automation server. Near as I can tell the person who wrote it sold it and it was removed from the internet. I then moved to an ISY994 and bought a Serial PLM. Since I, like so many others, disposed of the USB to Serial PLM cable (I didn't even know it was in the box) I just switched to the USB PLM when I upgraded to the EISY. As for the Z-Wave not working, my only guess would be that the EISY was spending all its time/resources trying to initialize the PLM that it just wouldn't do anything else. Doesn't sound likely though. I will order a new USB PLM from the Canadian distributor when they have them back in stock. It claims that the units built from 2023 has upgraded electronics and should be more robust. K-Bert

Unexpected update: While I was still at work my wife left the house and I received a notification from UD Mobile that the garage door was opened. I opened the app and it is all connected and working now. No idea why/how. K-Bert

I have done a full reboot with the removal of the power cord. I updated from 5.8.3 to 5.8.4. From the ticket I am told that the PLM likely has gone bad. Although none of my z-wave devices are working either. I have the next procedure to test when I am home again. From the ticket: 1. Unplug the PLM, wait 1 minute, plug back in 2. Press/hold the power button on eisy->red. Click again blue 3. Check the PLM status again. If disconnected, then the PLM is dead. You might qualify for some discounts from insteon (I am not sure when they expire): https://www.universal-devices.com/celebrate-insteon/ Please note that when you have a new PLM, you MUST do a Restore PLM. Please follow the instructions here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Modem_(PLM) K-Bert