Closed w1llf0rd closed 4 years ago
Try setting removeObsoleteZones
to false
Got it thank you! Great job on the plug-in it’s amazing. One more question, some glass break and smoke detectors show as contact sensors instead... is there anyway to fix that?
Yes, someone reported the issue but didn't come through with sending me a picture of the device names.
Log on to ADT Pulse > System, and then take a screenshot of all your devices. Then comment below on which zones are displaying incorrectly. I need to add the names to the plugin for them to recognize it correctly.
And, in the meantime, try not to re-organize the accessories until the plugin is updated! Don't want you to do the whole organization again.
Glass break detectors will show as occupancy sensors for now. HomeKit doesn't have glass break support yet (afaik).
Just documenting this:
Z7 Bedroom 's Hallway Smoke Detector
detected as contact sensor because Bedroom
has a dr
in it.Z41 Nook Glass Detector
detected as contact sensor because "Nook" is part of the doorWindow
detection.Z2 Master Bedroom Glass Detector
detected as contact sensor because Bedroom
has a dr
in it.The fix would be flipping the tag detection in function getZoneStatus
. Also tagging issues #22 and #25.
@w1llf0rd I am assuming that the sensors with names Service
are not being added to Homebridge also? They don't seem to be in the list of detectable accessories in the plug-in.
Yes the service sensors are not in homebridge... thanks!
Guys,
My system shows Glass Detectors in HomeKit. See attached.
Kevin
From: Jacky Liang notifications@github.com Sent: Tuesday, July 21, 2020 6:29 PM To: mrjackyliang/homebridge-adt-pulse homebridge-adt-pulse@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [mrjackyliang/homebridge-adt-pulse] Sensors Reset to Default Name and Room at Random Times (#33)
Glass break detectors will show as occupancy sensors for now. HomeKit doesn't have glass break support yet (afaik).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mrjackyliang/homebridge-adt-pulse/issues/33#issuecomment-662139453 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2BNPV4NWZEMLQGEG2B7MTR4YJEJANCNFSM4PDXVIBA . https://github.com/notifications/beacon/AI2BNPTQJJVH3ST4DQHWHC3R4YJEJA5CNFSM4PDXVIBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE53XEPI.gif
@knedd Hi, can you upload the screenshot directly to GitHub? The image attached is not shown here for some reason.
My system shows glass breakage detectors .
@knedd Oh. Glass detectors are supported in this plugin. They will just be shown as an occupancy sensor. HomeKit doesn't officially support glass break sensors. Once it does, I will convert it and give instructions on how to upgrade.
@w1llf0rd v1.8.11 is now available. Before you update to this version, please follow the directions below to prevent your Homebridge from crashing:
resetAll
to true
v1.8.11
resetAll
to false
These instructions only apply to you. Anyone else should proceed with the update normally unless their sensors were also wrongly detected in the first place. Let me know if the update is a success, thanks!
Sorry for the late response... got busy yesterday. I updated to 1.8.11 and now it continuously says ADT Pulse - An unknown error occurred. Also the same sensors as before still show as contact sensors.
Did you reset all the devices before the upgrade was performed?
Configure the logLevel
to 40
, clear all the Homebridge logs and then send the logs here.
I tried but couldn’t find where to set resetAll so I just unadded and readded the bridge... I’m a homebridge noob!
You would have to set the resetAll
using the configuration in Homebridge. The README.md
file in the repository should give you examples on how to do so.
Homebridge configuration example
If you do need help, let me know so I can start a Google Meet screenshare!
Done! Thank you for all your work!
Not a problem! Let me know if the unknown error continues to exist!
This issue is now locked and considered resolved due to inactivity.
Describe the bug:
What do you think the problem relates to? It might have to do with being on the new iOS beta but I am unsure.
Steps to reproduce the bug:
Expected behavior:
The room and name of the sensors should stay the way I set them.
The Apple device you are using: