Hey @Phuturist, sure thing, it shows as:
RELAYS":[“1”,“2”],“DEVICE-TYPE”: “DoorBird D2101V”}]}}
v3.0.2 - 2021-xx-xx
- Update to SDK3 (requires Homey firmware 5.x).
- Changed the relay functionality from a button to a slider under the device to avoid accidentally opening the door.
- Moved the functionality for adding the HTTP notifications from the app settings to the individual device settings for a more robust configuration. This requires you to re-configure your notifications in the DoorBird smartphone app though. See the support forum for more information.
- Added manual pairing fo those situations where mDNS is not working
- Added a second relay slider under the device for the DoorBird D2101V
This new version is available in the test channel in the app store. You can only install this if you are running Homey firmware 5.x which is currently rolling out. Next week this version of my app will be published to the stable channel but if you want to use it now you can already.
Here are the new instructions for (re-)configuring the HTTP notifications.
Setting up notifications
For the doorbell alarm, motion alarm, doorbell rang, motion detected and door open trigger flow cards to work in Homey the DoorBird needs to be configured to send HTTP notifications for these events to Homey. Follow the instructions below to set this up.
- When adding your DoorBird device to Homey it will add HTTP calls to your DoorBird which the DoorBird can use to communicate with Homey.
- Open the DoorBird smartphone app, go to the administration area and select the ‘3D or 4D motion sensor settings’ option
- Set the pause between alarm option to your preference (during the period no new events will be send to Homey)
- After that select the the ‘Schedule for actions’ option
- On this page select ‘HTTP calls’ from the top left icon pull down menu and select ‘Homey Motion Trigger’ from the top middle menu and click op the top left menu to fill the schedule (or configure it to your preference, this determines when the DoorBird will send motion events to Homey)
- Go back twice and select the option ‘Relays’ and then the option ‘Schedule’
- On this page select ‘HTTP calls’ from the top left icon pull down and select ‘Homey Relay Trigger’ from the top middle menu and click op the top left menu to fill the schedule (or configure it to your preference, this determines when the DoorBird will send door open events to Homey)
- Go back twice and select the option ‘Schedule for doorbell’
- On this page select ‘HTTP calls’ from the top left icon pull down and select ‘Homey Doorbell Trigger’ from the top middle menu and click op the top left menu to fill the schedule (or configure it to your preference, this determines when the DoorBird will send doorbell events to Homey)
- Test your settings, everything should be setup now to receive events from your DoorBird within Homey
- If needed you can remove and/or re-add the HTTP notifications from the device maintenance settings in Homey.
2 Likes
Hi @Phuturist Thanks for your update and ongoing development. Have you tested the D1101v with Homey (including v5.X)? Currently looking at replacing Ring Pro with Doorbird. Also curious if this will support single gate management? Thanks.
I have that unit myself. I have no clue what single gate management means.
Thanks @Phuturist . WRT “gate management” (sorry) Can you use Homey app to control a Doorbird-supported Electric Strike to open/close lock on a gate?
Asumming you would connect it to a relay of the D1101V than yes. The app supports switching the relay(s) of connected DoorBird devices.
1 Like
v3.0.4 - 2021-03-04
- Update to SDK3 (requires Homey firmware 5.x).
- Changed the relay functionality from a button to a slider under the device to avoid accidentally opening the door.
- Moved the functionality for adding the HTTP notifications from the app settings to the individual device settings for a more robust configuration. This requires you to re-configure your notifications in the DoorBird smartphone app though. See the support forum for more information. See [APP] DoorBird
- Added manual pairing fo those situations where mDNS is not working
- Added a extra relay sliders for devices that support multiple relays
- Updated the branding with the new logo and brandcolor
1 Like
The relay doesn’t work… Only making a flow triggering the relay 1.
Sliding doesn’t work.
Could you give some more details on what is not working. Perhaps an example of your flow.
And with sliding doesnt work you mean the slider to trigger the relay from the device settings? And do you have a device with multiple relays and do none of them work or only the second / third relay?
When i open the Doorbird, i get the option to trigger the standard relay. Then i have to slide it, but it doesn’t work when i slide it manually.
Did you do this?
This requires you to re-configure your notifications in the DoorBird smartphone app though. See the support forum for more information.
I deleted the Doorbird and added it again, now it works! Thanks.
Hi, since the update of yesterday 23 feb, 09:26 the relay button on the doorbird App is not working any more… On the homey / doorbird I can view both the live view snap shot and the last door bell snap shot. Is something changed with regards to receiving the relay API call from the doorbird? The flow it self works, the input/ trigger seems not OK.
Hello Phuturist.
Is there a way to install the v.2.4.5 instead of v3.0.2?
I have a homey on v4, and I cannot upgrade to v5 yet since there still is a problem with Osram zigbee ledspots.
I just ordered a doorbird D1101V and I can’t install the app 
You would need to install it through the command line. If this is easy depends on your technical skills. You can use the guide and link below.
- Install apps through command line: [HOW TO] CLI install method
- Version 2.4.5: Release 2.4.5 · jghaanstra/com.doorbird · GitHub
That’s ok, shouldn’t be a problem.
Thanks
@Phuturist It has been two weeks since I was able to upgrade Homey to v5. So I removed the cli installed package I got from github and I installed the latest version from the appstore.
I have two DV1101-S doorstations and three indoor stations. All are operating within a seperate vlan (vlan 4 - 192.168.4.0/24) with ip address reservations in DHCP.
Traffic from vlan 4 to vlan 1 is limited to a couple ip adresses (1/ HOMEY, 2/smartphone, 3/smartphone wife, 4/ pc) By allowing traffic from vlan 4 to these ip addresses in vlan 1 I am able to:
- view lan quality video feed in the doorbird app on our smartphone instead of cloud only
- make the doorstations succesfully connect to Homey for API calls
- Grab camera snapshot and latest doorbell/motion snapshots from the doorstation in Homey
I do admit I had to bring the doorstations online in vlan 1 to be detected by Homey when paring them, then change the vlan to 4 and edit the ip address in the homey device settings.
To be short: all is working perfectly… But although all is working fine, once the app is restarted (or homey restarted) the device tile get a warning icon, and homey says the device is offline. It is not, and Homey still works perfectly fine except for that device offline message.
So my question is: how does the app determine the availability/connectivity of/to the doorstations? And why is it saying offline while it can communicate with the doorstations?
I guess I know the answer (mdns? broadcast?)
Second question is: can this be fixed in a next release of your app? (check TCP ip connection to determine the on/offline status in addition to mdns/broadcast…?
Third question is: what is the extra value to use mdns/broadcast instead of tcp ip?
Thank you in advance for your answer.
Allow me to add my greatest appriciation for maintaining this great app!
Not a clue what is going on, I do not set the device as offline from my app. mDNS is only used during device discovery, all commands from Homey are sent over HTTP REST and the DoorBird reports any events to Homey over HTTP REST as well through the HTTP notifications that have been set up in the DoorBird app. Send me a crash report from the app settings, perhaps that gives me clues on what is going on.
Not as long as I dont know what is causing this.
Auto discovery of DoorBirds within the network during pairing.
v3.0.5 - 2021-03-31
- Added an opt-out option for scheduling notification events during pairing to make setup more user friendly.