macjeff Posted March 31, 2022 Posted March 31, 2022 I have tried for a week (and even the new IoP 5.4.2 update) and cant find a solution. Its usually first thing in the morning when devices have sat for a while. My wife gets up and opens the garage door (IO-Linc). The status changes to ON but the program did not run. I can close it and open it agian and program runs fine. I can try another door and it may or may not work first try. I thought it was ONLY IO-Linc but this am she walked to the mailbox and triggered my driveway motion sensor (insteon). She said she saw it blink and I looked at log and saw that it did report motion. BUT the program did not run. About 10 min later, my son walked past it and it all worked. This is driving me crazy because every test I run works UNLESS it seems to have been sitting for a while. But once it fails it works after that. I checked the program (last time run) and confirmed these programs are NOT running. Any ideas? These are not new programs. They have worked for years on ISY 994i and the devices are showing correct status so the control trigger should work.
larryllix Posted March 31, 2022 Posted March 31, 2022 Are the programs in a folder with conditions? 1
macjeff Posted March 31, 2022 Author Posted March 31, 2022 The Driveway motion is. I have a different version for day and night so I have day and night folders. but the garage one is not. Its in a folder but not. Just had it happen again and I last ran it about 2 hours ago. Opened garage door- No program but status changed. closed garage- program ran. Opened garage same door worked. Then another door- already open- Closed it and status changed but no program. Opened it and program ran. Closed it and program ran. So its like the programs have to be WOKEN UP and then they work. I guess I could put the program in a continuous loop. Like the last line runs the if again every 5 min or so. But that uses processor.
Whitehambone Posted March 31, 2022 Posted March 31, 2022 @macjeff I had an issue with some programs on working. I change something in the program, saved in and changed it back with another save. Then the program worked fine. For instance if the program turned a device on, I changed it to turn the device off and then put it back to normal. Like forcing the program save again. I wonder if that might work for you. Maybe I had something else going on, and it was just a coincidence. I can remember if i reported it or posted about the problem here, but I believe that fixed my problem. Something to try...
macjeff Posted March 31, 2022 Author Posted March 31, 2022 I tried that. I have edited the program a million times. It works fine after it never runs. Driveway just happened and this is a good example I have two programs run off motion sensor. One counts how many times someone has come in driveway. If its greater than 10 it waits an hour. This is for the lawn mowers that set it off over and over and drive me crazy. THAT RAN but at the same time. Another program has alexa announce someone is in your driveway. It never ran. I made the motion sensor go off again and both programs ran. So if one of the two programs ran its not the device. Its a program thats asleep. Especially when a minute later it ran fine.
lilyoyo1 Posted March 31, 2022 Posted March 31, 2022 (edited) 48 minutes ago, macjeff said: The Driveway motion is. I have a different version for day and night so I have day and night folders. but the garage one is not. Its in a folder but not. Just had it happen again and I last ran it about 2 hours ago. Opened garage door- No program but status changed. closed garage- program ran. Opened garage same door worked. Then another door- already open- Closed it and status changed but no program. Opened it and program ran. Closed it and program ran. So its like the programs have to be WOKEN UP and then they work. I guess I could put the program in a continuous loop. Like the last line runs the if again every 5 min or so. But that uses processor. I've experienced the same thing. In some cases I simply resaved the program (click a line hit update & save), in others I had to rebuild it because the program had different conditions (confirmed when I uploaded my backup). In 10 years and 100+ installs, I've never had folder conditions not update properly unless there were communication issues (including firmware upgrades and reboots) so i doubt that's your issue. I'd follow what whitehambone said and re-save your programs and verify what's written. ***You added additional information in between me being able to finish my post. One thing I'd verify is if other programs are running at the same time. It may be that the system isnt queuing to run properly or interrupting the program so your count becomes off Edited March 31, 2022 by lilyoyo1
macjeff Posted March 31, 2022 Author Posted March 31, 2022 44 minutes ago, MrBill said: Show us the intermittent programs... I am out for the day so I will post it this evening 1
macjeff Posted March 31, 2022 Author Posted March 31, 2022 8 hours ago, MrBill said: Show us the intermittent programs... Remember this works just fine if I run it multiple times in a row. Its after sitting a while like first thing in AM that it does not work the first time. And I have checked to make sure program did not run Garage 1 Open - [ID 00C1][Parent 029A] If 'Garage / Garage Door 1- Sensor' is switched On Then $GarageOpen_1 = 1 Wait 1 second $GarageOpen_1 = 0 Else - No Actions - (To add one, press 'Action') 1
Techman Posted March 31, 2022 Posted March 31, 2022 Being that the processor and memory in the Polisy is much faster than the ISY, try increasing your wait times and/or adding waits to see if that makes a difference. 1
macjeff Posted March 31, 2022 Author Posted March 31, 2022 30 minutes ago, Techman said: Being that the processor and memory in the Polisy is much faster than the ISY, try increasing your wait times and/or adding waits to see if that makes a difference. correct me if I am wrong but if the logs have no mention of that program but DOES have it when it works then the wait times would not matter. The program is not even running. Correct?
Techman Posted March 31, 2022 Posted March 31, 2022 (edited) You're correct. Are you using Momentary or Latching in your I/O Linc to trigger your program? If you're using momentary then the Momentary hold time may be too short to trigger the program. Another possibility is that the wires going into the I/O Linc are not making a good contact, try tightening the screws. Edited March 31, 2022 by Techman 1
macjeff Posted March 31, 2022 Author Posted March 31, 2022 8 minutes ago, Techman said: You're correct. Are you using Momentary or Latching in your I/O Linc to trigger your program? If you're using momentary then the Momentary hold time may be too short to trigger the program. Another possibility is that the wires going into the I/O Linc are not making a good contact, try tightening the screws. If the wires were not making good contact then the status would not change. The status changes in the ISY so its working. I am using Momentary so let me play with the hold time.
Techman Posted March 31, 2022 Posted March 31, 2022 Increasing the hold time should correct the program not running.
macjeff Posted April 1, 2022 Author Posted April 1, 2022 1 hour ago, Techman said: Increasing the hold time should correct the program not running. it was on 2. Increased to 10. waited an hour and then opened door. Nothing. Closed door worked right away. Opened door- nothing. Remember this is also happening with motion sensors. The first trigger in the morning or after long wait does nothing. Then it works.
larryllix Posted April 1, 2022 Posted April 1, 2022 14 minutes ago, macjeff said: it was on 2. Increased to 10. waited an hour and then opened door. Nothing. Closed door worked right away. Opened door- nothing. Remember this is also happening with motion sensors. The first trigger in the morning or after long wait does nothing. Then it works. Try removing the light bulb from the GDO. The lamp goes on when opening the door, but may be off when closing the door, if left to time out first. Try unplugging both GDOs and then test the MSs. My Chamberlain GDO destroyed most comms on my ISY. The older unit with AC motor interfered and I never could figure it out, until I got a newer unit with battery backup and DC motor and it killed my Insteon comms down to about 25%. Then I knew the problem and I remembered reading about dozens f complaints about those units. Two FilterLincs basically fixed it 99%.
macjeff Posted April 1, 2022 Author Posted April 1, 2022 Nature did the unplugging. We just got power back after that. But that did not fix it. But everyone is concentrating on the IO-Lincs. Its also all my motion sensors.
larryllix Posted April 1, 2022 Posted April 1, 2022 (edited) 1 hour ago, macjeff said: Nature did the unplugging. We just got power back after that. But that did not fix it. But everyone is concentrating on the IO-Lincs. Its also all my motion sensors. The idea was to unplug the GDOs and then test other devices, not power cycle the GDOs. They are known Insteon signal killers and your MSes may not function either while they are swamping the whole environment with RF and/or power grid noise. You may have lost Insteon links in your devices, especially if you have had comm noise while operating devices. Insteon signals are not data signal secure. Have you tried to Restore each device? You may have to "write updates to device" after each Restore select. UDI has changed things in the admin console and made it more complicated to do any of these things. Edited April 1, 2022 by larryllix
MrBill Posted April 1, 2022 Posted April 1, 2022 18 hours ago, macjeff said: Garage 1 Open - [ID 00C1][Parent 029A] If 'Garage / Garage Door 1- Sensor' is switched On Then $GarageOpen_1 = 1 Wait 1 second $GarageOpen_1 = 0 Else - No Actions - (To add one, press 'Action') So this program isn't running the first time? but it runs successive times? I assume that GarageOpen_1 is a state variable? If so, is it running one other program? or multiple other programs? The Wait 1 second may not protect the other program from finishing.... especially if that program has a wait in it. As soon as GarageOpen_1 drops back to zero the other program is probably going to end (since I can't see the other program that's a guess. why are you doing it this way? Why not just 'run program XXX' if or then?
macjeff Posted April 1, 2022 Author Posted April 1, 2022 It seems like ANY of the programs for Garage door 1, 2, 3 or even motion dont run after a long wait. Then they all run. like the propgrams need to be woken up. I will try the run other program idea but there are no other programs that do it.
Recommended Posts