Closed ambanmba closed 3 years ago
Nothing's changed from a code perspective...so that leads me to ask: what might have changed in your environment? Did you update plugin versions, Protect firmware, or anything else of consequence?
I'll take a closer look this week, but would appreciate if you'd think through the above. Thanks!
The last successful doorbell trigger occurred at 17:54 AEDT on 21 Jan. The first unsuccessful doorbell trigger occurred at 15:39 AEDT on 22 Jan. --- All doorbell presses from this point onwards fail to trigger The last Ubiquiti firmware update occurred on 6 Jan. The last Ubiquiti config change occurred on 14 Jan (password change due to well publicised UI hack) There was no Homebridge change in the days prior to 21 Jan There was no Homebridge update/change done after 21 Jan other than to debug this problem. Have rebooted Homebridge, have unset/set notification settings in Protect I don't think the problem is on the Apple/Homekit side since the Homebridge Accessories screen doesn't show activity when the button is pressed Pressing the doorbell button operates the physical bell it's attached to The video stream from the doorbell works as normal
Something changed more recently than that given Protect firmware 1.17.1 was released ~four days ago...and you're running it.
Wow, good pickup! I just went through the logs and it looks like the auto-update feature got enabled. It shows that on 21 Jan at 20:27 AEDT the controller and all the cameras (including the doorbell) got upgraded. This timing coincides perfectly with the loss of doorbell trigger functionality! Prior to the update the trigger worked, then it stopped after the upgrade.
There’s a bug in 1.17.1 that is supposedly fixed in 1.17.2 where doorbell rings occasionally don’t get acknowledged on doorbells. You can read more in the Ubiquiti forums. I’d suggest you upgrade to 1.17.2, and be watchful over Ubiquiti updates in the future. :smile: I would not recommend autoupdating any Ubiquiti firmware without checking out what issues early adopters have run into. I would generally recommend waiting 1-2 weeks before doing so.
Best of luck.
Upgraded to 2.0.26 (CK2+ Firmware) and 1.17.2 (Protect) and restarted the Homebridge service. That didn't solve the problem, but doing a full reboot of the Homebridge server (it's on an rPi) did the trick.
Incidentally, why do all the cameras have a doorbell automation trigger, not just the Doorbell itself?
I misread your question: the answer is to replicate certain behavior that is specific to doorbells in the HomeKit ecosystem. For example, you may want to have a camera pop up on an Apple TV in the same way it would when a doorbell rings. This allows cameras to emulate doorbells in those scenarios.
@hjdhjd , I hate to be "that guy" but there is still a problem. The HB-UI-Protect integration seems to break after a few hours. The problem doesn't appear to be Homebridge as the other plugins all seem to work (even Homebridge Camera FFmpeg on another direct link to a HikVision camera). The symptom is that after a full system reboot, the HB-UI-Protect plugin works for some period of time then silently stops working without any logs or error messages. When the HB-UI-Protect plugin stops working it can no longer stream video or respond to triggers such as the Doorbell. All normal UI features as accessed from UI apps work normally. The doorbell rings normally and sends a UI notification on the phone.
CK is at 2.0.26 and Protect is at 1.17.2.
I am actually having this issue as well. I have now upgraded to 1.17.3 and the issue still occurs. I am happy to share information/logs if that makes this easier to debug, just let me know.
I totally understand your sentiment to wait a couple weeks on upgrading firmware, but let me know if there is anything I can do to help get to the bottom of this.
This issue is locked to prevent necroposting on closed issues. Please create a new issue for related support requests, bug reports, or feature suggestions.
Describe The Problem: Doorbell button no longer triggers Doorbell switch. Other functions continue to work. Nothing was touched in the config from the day when things were working to the day that things suddenly stopped working.
To Reproduce: Ring doorbell. Nothing happens in Homebridge. All other Homebridge / Homebridge-Unifi plugin features continue to work (e.g. visibility of camera streams in Homekit, motion detection triggers, etc.)
Logs: Nothing appears in the logs when the button is pressed.
Homebridge Configuration:
Screenshots: None
Environment: