feat: doorbell button-press (visitor) events over Baichuan → MQTT - #418
Open
josh-stephens wants to merge 1 commit into
Open
feat: doorbell button-press (visitor) events over Baichuan → MQTT#418josh-stephens wants to merge 1 commit into
josh-stephens wants to merge 1 commit into
Conversation
Doorbells report a button press on the live Baichuan connection as an AlarmEvent with status="visitor" (verified on Battery Video Doorbell 2nd Gen, fw v3.0.0.6304, standalone via UID discovery) - no Reolink cloud or FCM push registration needed, sidestepping the PHONE_REGISTRATION_ERROR path entirely (QuantumEntangledAndy#288). - MotionStatus::Visitor + MdState::Visitor thread the event from the alarm parser to consumers - MQTT publishes status/visitor as a momentary on/off (gated on enable_motion, same alarm subscription) - motion-gated streams treat a press as activity (wakes the stream) - motion_detected() treats a visitor at the door as motion present
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Doorbells announce a button press on the live Baichuan connection as an
AlarmEventwithstatus="visitor"(theAItypestays e.g.people; the sequence isnone → visitor → noneover ~5s). This PR threads that through to MQTT as a momentarystatus/visitoron/off topic.This gives working doorbell ring events without Reolink cloud or FCM — sidestepping the push-registration path that currently fails with
PHONE_REGISTRATION_ERROR(#288). It appears to be the same mechanism Reolink's own NVRs/Home Hub use.Verified on real hardware
Reolink Battery Video Doorbell 2nd Gen (hw
DBB_NT19DNO34MPW6DBB3, fwv3.0.0.6304_26041428), standalone via UID/local UDP discovery,mqtt-rtspmode:→
neolink/doorbell/status/visitorpublisheson, thenoffwhen the camera returnsstatus=nonea few seconds later. Home Assistant (MQTT binary_sensor on that topic) shows a clean ~4s pulse per press. Running in production since 2026-08-23.Changes
MotionStatus::Visitor/MdState::Visitorcarry the event from the alarm parser to consumersstatus/visitormomentary topic (gated onenable_motion— same alarm subscription, no new config)motion_detected()counts a visitor at the door as motion presentai_type/statusof non-none alarm events is logged at debug for future mappingHappy to adjust naming/shape (e.g. an HA discovery entity for it) if you'd prefer.