homebridge-camera-ffmpeg: How do you use http to trigger doorbell button? Nothing in the Wiki/Readme

Describe The Problem: The description states: doorbell: Exposes the doorbell device for this camera. This can be triggered with the dummy switches, MQTT messages, or via HTTP, depending on what features are enabled in the config. (Default: false)

I would like to use a http command to activate the doorbell trigger button, but I see no instructions on how to do so

Homebridge Config:

    {
                    "name": "Front Door FFMPEG",
                    "manufacturer": "xxxx",
                    "model": "xxxx",
                    "serialNumber": "1234",
                    "firmwareRevision": "1.0",
                    "motion": true,
                    "motionTimeout": 1,
                    "doorbell": true,
                    "doorbellSwitch": true,
                    "switches": true,
                    "videoConfig": {
                        "source": "-re -ignore_loop 0 -i file:///home/pi/Public/fuo.gif",
                        "maxStreams": 2,
                        "maxWidth": 1280,
                        "maxHeight": 720,
                        "maxFPS": 10,
                        "maxBitrate": 300,
                        "vcodec": "libx264",
                        "audio": false,
                        "packetSize": 1316,
                        "vflip": false,
                        "hflip": false,
                        "debug": false
                    }
                }

Environment:

  • Node.js Version: v12.18.3
  • NPM Version: v6.14.7
  • Homebridge Version: 1.2.0-beta.31
  • Homebridge Camera FFmpeg Version: homebridge-camera-ffmpeg v2.4.2
  • Homebridge Config UI X Plugin Version: homebridge-config-ui-x v4.24.0
  • Operating System: Raspbian GNU/Linux Buster (10)

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 30 (17 by maintainers)

Most upvoted comments

Awesome, thanks for testing guys. I’ll likely push this to release later today.

So, fun fact. Apparently I had broken HTTP/MQTT automation at some point. I found the error while adding in some HTTP responses, and will be publishing a new version with fixes later tonight, once I’ve had some time to do a bit more testing to make sure I got it all.