This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official
[APP] DoorBird for Homey
This discussion has been closed.
Comments
I even went further, because I noticed that sometimes flows vanishes. I did a factory reset and then installed only doorbird. Same result. Again I runned the test: {"BHA": { "RETURNCODE": "1", "NOTIFICATIONS": []}}. Even I can see that the JSON array returned only an error.
I did notice that something in the DoorBird notification API has changed. It seems that they are in the progress of moving these notifications it over to the DoorBird smartphone app (under Administration > HTTP calls). You can only set a doorbell notification here however and the API documentation is not updated yet. I'll email them to get more info.
http://192.168.1.44/bha-api/image.cgi?http-user=ghbfei0001&http-password=w5DYFxbLgC
Success
http://192.168.1.44/bha-api/image.cgi?http-user=ghbfei0001&http-password=w5DYFxbLgC&index=1&event=doorbell
Success
http://192.168.1.44/bha-api/monitor.cgi?http-user=ghbfei0001&http-password=w5DYFxbLgC&check=doorbell
Returned empty page
http://192.168.1.44/bha-api/monitor.cgi?http-user=ghbfei0001&http-password=w5DYFxbLgC&ring=doorbell
Browser request keeps polling for a minute, then empty page
So could you provide me a script or something so I can help find the problem?
When trying to write some manual instructions for you I may have found the issue. It looks like a certain API call is not working since DoorBird firmware 1.0.9. I use this API call to get some info on the DoorBird. Could you tell me the outcome of this URL: http://192.168.1.44/bha-api/info.cgi
Second: The json output is {"BHA": { "RETURNCODE": "1", "VERSION": [{"FIRMWARE": "000109","BUILD_NUMBER": "15120529","WIFI_MAC_ADDR": "1CCAE370E77C","RELAYS":["1"],"DEVICE-TYPE": "DoorBird D101"}]}}
Third: Keep up the good work, thanx
Now you need to access the following URL's in your browser replacing the parameters with your own and the mentioned notification URL's from above.
Set doorbell notification: http://192.168.1.44/bha-api/notification.cgi?url=<<doorbellurl>>&user=&password=&event=doorbell&subscribe=1&relaxation=10
Set motion notification: http://192.168.1.44/bha-api/notification.cgi?url=<<motionurl>>&user=&password=&event=motionsensor&subscribe=1&relaxation=60
Set door relay notification: http://192.168.1.44/bha-api/notification.cgi?url=<<dooropenurl>>&user=&password=&event=dooropen&subscribe=1&relaxation=60
response: {"status":200,"result":"Not authorised, incoming IP address (192.168.1.33) does not match DoorBird IP address (192.168.1.35) or MAC address of incoming request does not match DoorBird MAC address."}
192.168.1.33 = my laptop
Next I saved it and entered this in the browser
http://192.168.1.35/bha-api/notification.cgi?url=http://192.168.1.34/api/app/com.doorbird/doorbell/1CCAE370E77C/&event=doorbell&subscribe=1&relaxation=10
Got a 400 Bad Request: The request had bad syntax or was inherently impossible to be satisfied.
Typo?
The IP's changed. Has to do with my ancient installation. I live in Spain and have to deal with an ancient adsl router. Every time the power drops (and that happens a lot), the dhcp ip table is lost and the devices don't always get their former ip addresses. That's why I did a factory reset and connected only my pc, the homey and the doorbird to exclude errors and to make sure the ip's are right.
The syntax from your notification URL is correct. I just tested it myself again with my own DoorBird IP, Homey IP and DoorBird MAC address. Works fine for me. If this does not work for you something is going on with your DoorBird and I wont be able to help you any further as it's beyond my Homey app. One thing I can suggest is to reboot the DoorBird (either cut the power or use the restart option from the administration settings) and then try again. If it still not works I suggest you contact the DoorBird company about this.
Is this a known problem?
You can either disable the api notification through the settings area of my DoorBird app or change / remove the new HTTP calls (which or copied from the old api notifications) or it's schedule in the DoorBird smartphone app to avoid double notifications being send to Homey.
I have an doorbird question, nog realy an Homey question i hope someone can help me.
This is not working but i can ping the device.
Just go to http://xxx/bha-api/view.html (where xxx is the current IP address of the Video Door Station in your LAN) with your favourite web browser and enjoy a new way of door communication. Alternatively log in at http://www.doorbird.com/checkonline and follow the html5 widget link. For the html5 widget to work in your browser window, your PC must be connected in the same Local Area Network (LAN) […] as the DoorBird IP Video Door Station. Enter the same user name and password that you are using to add the Video Door Station to the DoorBird iOS or Android App.
yep, got it.
But you can only use this login once.
i wrote an email to doorbird for support
THX!
Afther entering it says:
Latest version - 2018-04-08 -- v2.2.0
@hansje, this should fix your issues. Please read the instructions in the app store or the opening post.
I stil cant connect, ip and login are ok.
Can i do something else to check teh connection?
THX!
Do you mean Windows commandline or homey commandline?
Thx!
Use 'athom app run' and try to pair your DoorBird. It should spit out extra info onto the console the should give more insights on what is going on.
I wil dive into this.
THX!!!
I had some issues to get my Doorbird talking to the com.doorbird app.
Diving into the issue, I found the problem in the sourcecode for the app.
I created an issue in github for this (with a solution).
Basically the handling of the MAC of the Doorbird in the app is incorrect.
After solving this, communication between Doorbird and Homey works perfectly, flows are triggered,
everything ok.
Still very happy with this app. Thanks for all the hard work creating it :-)