I wasn’t happy with continuous stream from doorbird. If I included Synology video station in the story after few days of use doorbird would become extremely slow to reach, like it’s overloading the network interface. The second I disable Synology video camera bum, all fine. Never got to the bottom of it, neither the support. They prepared few firmware that were directly related to nic stability, it helped to some extent but I just gave up. I’m mentioning this in case someone notice similar symptoms, just disable it in Synology and have a look.
v2.3.4 - 2019-08-05
FIX: fixed setting the notification URLs from the app settings page
It’s getting worse and worse… As mentioned before the app had issues getting the API calls to the controller when the app was closed. Now after upgrade to 2.4.0 the device was offline. So I deleted the device, but unfortunately it does not discover it anymore. Then I removed the whole app, removed the HTTP url’s in Doorbird, re-installed the app, but still, it does not discover the doorbird device anymore.
Bottom line, getting frustrated after 5 weeks of fiddling around with this app without satisfying results. Can you get me on track to get things fixed…?
Thnx
Update…I downgraded to rel. 2.3.3 and then I was able to add the doorbird device again. Then I installed 2.3.4 to get the notification url fix in place and the device is still online. I will do some testing, but won’t be able to get this done today. Depending on the results I might get to 2.4.x again.
On what Homey firmware are you?
I have now the problem that with Doorbird app 2.4.0 and Homey 2.5.1 my doorbird device gives me error: device currently unavailable.
Doorbird has version 119
Without modifing anything, i tried restart the doorbird app and tried to restart teh doorbird, still device unavailable.
Seems that http pushes from doorbird are still processed.
Not sure why it’s unavailable but I just pushed a new version to the app store that will probably fix that. It’s pending approval now.
v2.4.2 - 2019-08-11
- FIX: small fix for devices being unavailable
- FIX: small fix for quirky pairing wizard template
@Phuturist Thanks, this solves the unavailable issue.
App is updated 4 hours ago on my homey, doorbird has been pushed less than 1 hour ago.
I do notice that these are working: Live Snapshot and Last movement snapshot. Last doorbel snapshot gives an error: invalid_content_type (Something went wrong, please try later).
The add button for adding the http calls is working, but there is now a problem to set the Schedule for all three calls.
They are now occupied?
Doorbird has version 119
Floorboard app has version v2.4.2
read the instruction carefully!
Go back twice and then in an other menu (not this, you can only select a schedule once).
(have had the same mistake)
Thanks for your reply, I have done that only the relay schedule is working.
- try to set the motion http call in the motion schedule that’s occupied.
- set the relay http call in the relay schedule that’s working.
- Try to set doorbell http calls in the doorbell schedule that’s occupied.
I can not reproduce this. The error suggests the no valid image has been returned by the DoorBird. This could perhaps be the case when the request times out. Have you tried reloading the snapshot a couple of times to see if it’s just a hick-up related to slow network (the DoorBird is not a fast loading device).
You need to select the correct trigger for the right schedule (as described in the instructions). If it’s greyed out it means you have assigned the doorbell trigger to another schedule (the relay or the motion). Go back there and make sure you select the correct trigger for each schedule.
I’m having the same persistent issue…same error, but exactly opposite.
Last doorbell snapshot is working and Live Snapshot and Last Movement gives the invalid_content_type error.
Retrying does not resolve this issue; gives same error code. I can check debug logs tomorrow evening.
With the help of @TedTolboom we where able to reproduce this. It appears the be an issue with incorrect permission of the DoorBird user which has been added in Homey to connect with the DoorBird. Make sure you have “watch always”, “history” and “motion” permission enabled.
2 Likes
History was off for my homey user on doorbird. After switching it on all three snapshots do work. Thanks!
v2.4.3 - 2019-08-13
- FIX: fix for motion snapshot token (it displayed the live snapshot)
- IMPROVEMENT: better error handling when permissions have not been configured correcty
1 Like
@Phuturist, I have try that but it is still not working, can I send you a PM with a screen record that I make?
Sure, could you also post a screenshot of all the HTTP calls that have been added in the DoorBird app.
How to register Sip User in doorbird
I am tried to register a sip User in doorbird. but it has not to work. this way I have been trying. http://192.168.0.12/bha-api/sip.cgi?action=registration&user=ggzvvx0002&password=n7KqC&url=192.168.0.149?http-user=ggzvvx0002&http-password=n7KqC
