Windows 10 has increased the security between Services and the interactive user session. It may not be possible for a service to ‘see’ activity of the interactive user.
I'm tempted to update my driver / application to kick off at startup, include a loop inside the code to handle a polling period and shift most of the config across to a HE device driver, rather than requiring manual updates to config files. The PC-based part could read in the config from a HE device each time it polls, including things like the polling period, thresholds and whether to turn the motion detection off.
The best I could find re having the PC part running regularly was to place it in the startup folder for the user. Like I mentioned above, I would then handle the scheduling of it with a loop inside the code and a polling period config setting in the HE device.
I really want to try and achieve reliable presence detection in my kitchen. I have two Aeotec Multisensor 6s running cSteele's drivers in the kitchen. They detect motion just fine and turn the lights on when I enter, but their "occupancy" detection is complete crap. If I am at the counter chopping veggies or at the hob cooking, they will lose track of me and turn everything off. It's such a pain and sometimes, even a bit risky.
This is how I have set the rule up. Anyone have any suggestions to improve this?