Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V1 motion sensors don't show motion #51

Closed
2 tasks done
BewhiskeredBard opened this issue Jan 8, 2020 · 4 comments
Closed
2 tasks done

V1 motion sensors don't show motion #51

BewhiskeredBard opened this issue Jan 8, 2020 · 4 comments
Labels
bug Something isn't working v1 Applies only to V1 Scout hardware
Milestone

Comments

@BewhiskeredBard
Copy link
Owner

BewhiskeredBard commented Jan 8, 2020

Description

V1 motion sensors don't update their status unless the security system is armed.

Reproduction Steps

Steps to reproduce the behavior:

  1. Setup a Scout system with a motion sensor.
  2. Disarm the system.
  3. Trigger the motion sensor.
  4. Note that Home app doesn't update and the logs do not have an event for the motion.

Expected Behavior

The device should show motion in the Home app.

To Do

  • Log a warning and prevent creating an accessory for any V1 motion sensors.
  • Update README.md to mention the lack of support.
@BewhiskeredBard BewhiskeredBard added bug Something isn't working v1 Applies only to V1 Scout hardware labels Jan 8, 2020
@BewhiskeredBard
Copy link
Owner Author

V2 hardware always sends a trigger event immediately upon motion starting. What varies is how it behaves when motion stops.

  • If the system is disarmed, it won't send a trigger for motion stopping until there has been 30 seconds without motion.
  • If the device is in test mode (can be triggered in the device details in the app/dashboard), a trigger is sent immediately after motion is no longer detected.
  • I haven't yet tested when a mode is triggered/alarming, but I'm less concerned here since it's likely one of the other two behaviors.

@BewhiskeredBard
Copy link
Owner Author

It's possible if the v1 motion sensor was put into test mode it could work (it's just an API call), but it would also prevent triggering the security system's alarm. Something fancy could be done to automatically put the device in test mode when the system is disarmed, and then take it out of test mode when a mode is armed, but I'm hesitant to do anything that could impact the behavior of how the system protects someone's home.

@BewhiskeredBard
Copy link
Owner Author

I’m leaning towards just blocking v1 motion sensors from being supported by this plugin.

@BewhiskeredBard
Copy link
Owner Author

Here’s the data returned by the API for a v1 motion sensor (from #40):

  {
    "version": "01D02D02",
    "reported": {
      "mesh_address": 2,
      "timedout": false,
      "channel": 0,
      "trigger": {
        "state": "motion_stop"
      },
      "battery": {
        "low": null
      },
      "fw_version": "1.2.2",
      "uptime": 20412
    },
    "mode_ids": [
      "5688fc4da1cb3442eb000338"
    ],
    "created": "2015-01-29T15:50:23.475Z",
    "name": "Motion Sensor",
    "updated": "2017-12-14T18:44:06.996Z",
    "desired": {},
    "pro_monitoring_label": "003",
    "heartbeat": 1577805270609,
    "location_id": "54ca3b40935b88c780000006",
    "hub_id": "0a70080064100452904ba000a0000100",
    "id": "0a70080064100450d80fa000a0000100",
    "type": "motion_sensor"
  }

@BewhiskeredBard BewhiskeredBard added this to the v1.0 milestone Feb 4, 2020
@BewhiskeredBard BewhiskeredBard pinned this issue Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v1 Applies only to V1 Scout hardware
Projects
Archived in project
Development

No branches or pull requests

1 participant