macjeff

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.

Even with 3.08 it still said 3.06. This is a VERY easy Node server to setup. No API keys or anything so I went ahead and deleted and added back. Now it says 3.08.

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.

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.

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.

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?

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')

I am out for the day so I will post it this evening

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.

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 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.

I dont know but I was testing a lot of versions for Michel like 5.4.0_1, 5.4.0_2, 5.4.0_3. Those worked fine. but every time it was a upgrade like 5.4.0, 5.4.1, 5.4.2, I had to do this and it fixed it every time. Did it work for you?

This has probably been answered but this is normal now. Clear JAVA cache (And apps) and it should work. The start java app will download the proper version after doing this.

Got it. Not using the "issues" on Github much anymore since the forums are better!!! So did not even look there.

It may be API or ISY limitation but I had a device named Drives/Monitor and it would not add to ISY So I changed name to Drive & Monitor in KASA app and still nothing changes to Drives and Monitor and it came right into ISY

This seems fixed also in 3.0.54. Only issue left for me is the Harmony Hub 3.07 wont upgrade. Jimbo confirmed issue and reported to you.

I hope the power strip uses one ip addres and not multiple ip for each outlet.

So I kind of like KASA but I have like 100 switches in my house so if I replaced them all I would have to have 100 IP addresses. So I was thinking of putting KASA on a different subnet just for the switches. BUT can the Node server support that? It seems to scan your LAN for switches so thinking this wont work.

verified mine actually works also Just activated some things. But it still says 3.06 and if it really installed 3.06 on the next restart it should not try and download it again but it is.

It shows connected but whats strange is ZERO log entries even in DEBUG mode since I did the update to PG3 3.0.54 and I have it on debug and yes I tried to change and restart but still no log entries. Each time i restart it takes forever so its trying to grab stuff from the server but then it comes back on connected at 3.06 not 3.07. Poor @bpwwer Been a busy couple days for him. I assume he will see this and if you need my logs let me know.

3.0.54 should fix these issues. Its pushed now sudo pkg update then sudo pkg upgrade

I restart Node server and I still get 3.06.

try 3.0.54. May fix issues

3.0.54 seems to fix all the issues including wireless tags

Great!! Its not the perfect fix. I think the next version will fix Wireless Tag, Harmony, and Kasa for you. I sent in my logs but you may want to download a log file and send it (PM) to bpwwr At this point dont try the erase and install at this time because what you have working now is better than nothing.