Motion sensor fallback to default

[mattnewham]

I have set the 5 second timeout in the config, however once a file is placed in the path the sensor stays active forever, even if the file is subsequently deleted.

This effectively makes the plugin useless but I can't see what is wrong with it!

[yaudouin]

I have the same problem under windows 7. Did you find a solution ?

[purplespider]

This is annoying. Other than this issue, the module seems to work great. Been trying to fix it myself, but not having much luck.

[mattnewham]

I never did solve the problem. I've now moved on to use Home Assistant as my main hub and I just use homebridge as a plugin there. I suggest to check it out as it is way more powerful.

[purplespider]

@mattnewham Thanks, Home Assistant does look ace, especially if it works well with Homebridge for HomeKit support. Can I ask what "component" you used to achieve the functionality of this module?

[mabrodeur]

I know this is an old thread but for those joining in 2018, it just works fine but you need to set your config correctly! The inverse parameter should be a boolean and not a string or the condition will not work.

{
      "accessory": "homebridge-filesensor.FileSensor",
      "name": "Motion sensor",
      "path": "path/to/folder",
      "window_seconds": 10,
      "inverse": false,  <== HERE, this needs to be a boolean and DO NOT wrap it like this "false"
      "sensor_type": "m"
}

If we set the inverse param as "false", what happens is that when the plugin detects a file change, it sets the motion to false immediately (instead of true) and then, after the window_seconds it sets it to true and this is where you see the state change in Homekit. Which is the reversed behavior.