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 sensor is reported OPEN in Homebridge but CLOSED in ADT Pulse App. The door is CLOSED. #116

Closed
sptv1 opened this issue Nov 19, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@sptv1
Copy link

sptv1 commented Nov 19, 2023

This just started today.

Inside Homebridge, one door sensor is showing as OPEN. But the door itself is closed, and the sensor on ADT Pulse app is showing as CLOSED. I've tried resetting the ADT bridge several times. I have changed settings to "remove obsolete zones" = TRUE. I have also restarted Homebridge. None of these has solved the problem. Weird.

@sptv1 sptv1 added the bug Something isn't working label Nov 19, 2023
@mrjackyliang
Copy link
Owner

Yes, it happened for me last night. I will be working on a remake of the entire plugin soon, as of now, I believe the plugin would be unstable.

@mrjackyliang
Copy link
Owner

mrjackyliang commented Nov 19, 2023

My logs are constantly spammed with removeObsoleteZone logs as well

@sptv1
Copy link
Author

sptv1 commented Nov 19, 2023

Further examination - now the BASEMENT DOOR (which is the one causing problems) is no longer a problem. However, now my KITCHEN DOOR is showing up twice in the accessories panel, with two different sensor numbers. When I unblock "remove obsolete zones" most of the sensors no longer show up in Homebridge (or HomeKit). I am also getting an "unknown error occurred" in my logs, regardless of whether "obsolete zones" is true or false.

@mrjackyliang
Copy link
Owner

This is because of the website constantly changing available sensors. From my side, I would see random sensors being taken offline and online.

@mrjackyliang
Copy link
Owner

This issue will be worked on soon. Follow #98

Copy link

github-actions bot commented Feb 2, 2024

This issue is now locked and considered resolved due to inactivity.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants