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

Door Sensors Slow #9

Closed
BlackWaterSeal opened this issue Oct 12, 2018 · 4 comments
Closed

Door Sensors Slow #9

BlackWaterSeal opened this issue Oct 12, 2018 · 4 comments
Labels
stale OP hasn't responded unreproducible Maybe a glitch or specific environment issue wontfix This will not be worked on

Comments

@BlackWaterSeal
Copy link

BlackWaterSeal commented Oct 12, 2018

Hello,

Thank-you for making this plugin. It has been great. I just wanted to let you know that my sensors seems to be slow, sometimes too slow to even appear in the Home app. The motion detector appears fine and fairly instant. Windows are ok but slow. I’d have to leave the window open for 30 secs or so for it to register in Home. The door sensor is by far the slowest. I can open and close my front door and it will appear in my Alarm.com app history but never in Home. I haven’t tried leaving the door open for longer than a few minutes. I know there were earlier reports of not having the required Alarm.com subscription that did not include sensor monitoring. However, I’m sure I have this on my account as the motion and windows work (or one window, I didn’t open anymore more to test it). The door sensor is really what I’m hoping for to be speedier. Not sure if this is an plugin thing, my setup (RP3) or the Alarm.com side.

Thanks again for this plugin.

@mkormendy mkormendy added wontfix This will not be worked on unreproducible Maybe a glitch or specific environment issue labels Oct 12, 2018
@mkormendy
Copy link
Collaborator

I'm amazed that your motion sensors seem fine and fairly instant.
In my house, the door contact sensors and changing the state of the alarm is what's pretty immediate, within 5-30 seconds. But my motion sensors don't even register any motion whatsoever, and that's in either the home app OR the alarm.com iOS app.

Now, I have Fiber internet at my location and I've done some extensive testing to see what the internet speeds are, which are more than fast enough and I get push notifications all the time.

I'm guessing this is highly dependent on whether the alarm system box has a fast connection to the alarm.com servers. I don't have any tools to test this or check this. My installation uses a cellular service, although this may be improved with a physical telephone line connection or maybe some sort of WiFi module for connecting the box to the internet to improve the speeds (if there is one).

As it is, I can't reproduce everyone's setup, so I'm at a loss.
The plugin has been coded based on receiving the payload of data I receive from the service - it's rather simple in its operation.

@BlackWaterSeal
Copy link
Author

BlackWaterSeal commented Oct 12, 2018

My system is on cellular as well. Home internet gets 150 Mpbs down, 15 Mbps up. I get my door sensors front and back instantly in the Alarm.com app even when checking on the home WiFi. So connectivity speed should be ok. Checking the RP3/Homebridge log the door sensor doesn’t even appear when opens or closes. But motion and windows do appear in the log. Panel status also appears instantly in both the Home and Alarm.com app. Just something about the door sensors that just doesn’t even make it to Homebridge.

Oh well, better than nothing.

Thanks for you replying so quickly.

@BlackWaterSeal
Copy link
Author

I know this won’t be fixed as it is hard to reproduce. Just wanted to add some info in case it helps in anyway.

I just spoke to my alarm company. Seems like the all windows/sliding doors/glass break are marked as “perimeter” sensors in their system and the doors are marked as “entry way” sensors. I was hoping they could change the doors sensors to a “perimeter” sensor instead. I was thinking maybe the “entry way” sensors send a different data header that is not being parsed properly by Homebridge hence it doesn’t even show in the Homebridge log.

It’s a wild goose chase for me, I know.

@mkormendy
Copy link
Collaborator

mkormendy commented Nov 5, 2018

That's an interesting note. I've been busy with launching an international project for my current job amongst my regular weekend commitments. I'd like to see the payload that ends up returning from your setup to see what the different accessories report as.

Would you be interested in scheduling a troubleshooting session?

@mkormendy mkormendy added the stale OP hasn't responded label Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale OP hasn't responded unreproducible Maybe a glitch or specific environment issue wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants