Announcement

Collapse
No announcement yet.

DoorBird Beta Plugin Release

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    I have the D101. I have the plugin installed and connected. I see the image from the doorbell in the plugin seutp window. When I view my devices list, I do see my doorbird "Not Ringing" device. I'm trying to set it to trigger an event when the doorbell rings. I have an event setup to turn on a light when the device "not ringing" changes and becomes ringing. But nothing happens.

    I pulled up my device list and watched as I rang the doorbell, and that device never changed from not ringing.

    What else can I try. I'm using the "app" user credentials.

    Comment


      Have you setup the schedules? See my comment in post#390

      Comment


        I just read it. I don't really care to have motion sensors, but will enable 3d motion sensor. when I activate that I can go into settings and schedule all the "push notifications" are light blue. If I look under the Favorites area HTTP(s) calls, I have nothing listed in HTTPS calls, not sure if that is normal.

        Under expert schedule for doorbell push notifications are all light blue too.

        I just tested again after enabling the 3d motion push and still nothing

        Comment


          OH, I saw in one of the other posts that the plugin is supposed to make a favorite HTTP call and I didn't see anything in there, so I created one http://192.168.1.20:8080/doorbird?triggertype=1 but it still didn't seem to work. Below is my log enteries.

          Dec-01 7:44:05 AM DoorBird DoorBird Web Exception: The remote server returned an error: (401) Unauthorized.
          Dec-01 7:44:05 AM DoorBird DoorBird Web Exception: The remote server returned an error: (401) Unauthorized.
          Dec-01 7:44:05 AM DoorBird DoorBird Relays: 1
          Dec-01 7:44:05 AM DoorBird DoorBird Device Type: DoorBird D101S
          Dec-01 7:44:05 AM DoorBird DoorBird WiFi MAC Address: 1C.......
          Dec-01 7:44:05 AM DoorBird DoorBird Build Number: 15961006
          Dec-01 7:44:05 AM DoorBird DoorBird Firmware: 000128
          Dec-01 7:44:04 AM Plug-In Finished initializing plug-in DoorBird
          Dec-01 7:44:04 AM Starting Plug-In DoorBird loaded in 433 milliseconds
          Dec-01 7:44:04 AM DoorBird HomeSeer IP Address Found: 192.168.1.20:80
          Dec-01 7:44:04 AM DoorBird DoorBird Password: .....
          Dec-01 7:44:04 AM DoorBird DoorBird Username: .....
          Dec-01 7:44:04 AM DoorBird DoorBird IP Address: 192.168.1.25
          Dec-01 7:44:04 AM Starting Plug-In Plugin DoorBird started successfully in 100 milliseconds
          Dec-01 7:44:04 AM DoorBird Plugin Starting - Checking if HS4/HS3
          Dec-01 7:44:04 AM DoorBird DoorBird Plugin Starting Interface:
          Dec-01 7:44:04 AM Starting Plug-In Initializing plugin DoorBird ...
          Dec-01 7:44:04 AM Info Plugin DoorBird has connected. IP:127.0.0.1:62897

          Not sure why I'm getting unauthorized, I'm using the username and password used for the app. I tried the admin credentials, and that didn't work at all lol.

          Comment


            Click image for larger version

Name:	Screenshot_20201201-151125_DoorBird.png
Views:	470
Size:	220.4 KB
ID:	1437378 Here are mine favorites

            Comment


              Originally posted by Cor View Post
              Click image for larger version

Name:	Screenshot_20201201-151125_DoorBird.png
Views:	470
Size:	220.4 KB
ID:	1437378 Here are mine favorites
              Thanks! did those auto populate in your app or did you need to type them in? and when you go into the doorbell schedule, which of those three are highlighted as scheduled? My app only allows me to schedule one of my favorites at a time, the other gets grayed out.

              Comment


                Well, I am not sure about that. It is years ago that I installed DoorBird (on HS3 in that time). As far as I understyand it should be auto populate with installation. Are you using HS3?

                Comment


                  OH! I found in the app there is a user setting where I can give a user access to the API. I granted the user permission to the API. I'll test in a few minutes and see if that did anything. Once I granted that permission the plugin auto populated the favorites to the app... one step closer, hopefully the test works!

                  Comment


                    AH!! it works!! Thanks everyone for your help! it turns out it was Operator Error. below is what I had to do incase anyone else runs into it.

                    My symptoms were,
                    the plugin would connect, and all device would show up in my device list with no errors. But I could not get the doorbell to trigger anything
                    I looked at my logs in HS and saw a 401 not authorized error

                    my fix
                    In the app, under administration click on the user you linked to Homeseer
                    at the bottom of the app press permissions
                    Ensure you add a checkmark next to API-Operator
                    save the settings

                    Comment


                      I am missing the communication between the button in the doorbird app and the "Default Doorbird Relay 1" in homeseer and homeseer will not update the status when pressing the button in the app. The doorbell and motion sensor works as expected. I am suspecting this is a missing setting in the app. Maybe one of the scheduels or the HTTP(S) Calls. Anyone care to share their setup?

                      This is a D101 and I have attached a image of my HTTP(S) Calls.

                      Click image for larger version

Name:	IMG_1120.PNG
Views:	561
Size:	79.5 KB
ID:	1446184

                      Comment


                        I have a D101 doorbell, working fine with the plugin. I am trying to add a second instance for a new one on HS3, but motion / ring events are not coming through. I can switch on the IR LED without problem. I tried:
                        • removing / recreating devices
                        • removing / recreating plugin instance
                        • also checked both 'push' schedules and http schedules in Doorbird app, they are active
                        • also checked both http calls in Doorbird app, they seem OK
                        Any suggestions what I could try?

                        Some additional info after testing:

                        I have found what might be the problem: http calls are not created correctly in the Doorbird app.

                        In the first instance (which is working) syntax is (like in post #400 above) http://:IPaddress: port/Doorbird?triggertype=2 for the HSCall_Motion
                        But for the second instance called 'Gang' (which is not working) syntax generated by the plugin is: http://:IPaddress: port/Doorbird?instance=Gang for the HSCall_Motion. So the 'triggertype' part seems to be missing. I tried to change it to http://:IPaddress: port/Doorbird?instance=Gang?triggertype=2 but that also is not working.

                        @mrhappy or someone else knowing what the correct syntax is for multiple instances for the HTTP call??

                        After extra testing and searching, found on a Norvegian site that syntax should be something like this?
                        http://:IPaddress: port/Doorbird?instance=Gang&triggertype=2. This changes something in the command prompt window of the plugin, but still not working. In the working instance, it gives:
                        [15/01/2021 20:06:26] - > GetPagePlugin Called: DoorBird User: *******@******* Rights: 6 QueryString: triggertype=2
                        [15/01/2021 20:06:26] - -> HTTP Notification From DoorBird - Starting Thread
                        [15/01/2021 20:06:26] - > StartDeviceThread Entered
                        [15/01/2021 20:06:26] - > Thread Entered For 3
                        [15/01/2021 20:06:26] - AddToTable : 1
                        [15/01/2021 20:06:29] - -> Thread Exit

                        In the plugin that does not work:
                        [15/01/2021 20:03:17] - > GetPagePlugin Called: DoorBird User: ******@****** Rights: 6 QueryString: instance=Gang&triggertype=2
                        [15/01/2021 20:03:17] - -> HTTP Notification From DoorBird - Starting Thread

                        But then it stops, the rest of the treatment does not seem to be triggered?
                        Last edited by backkri; January 15, 2021, 02:15 PM. Reason: Extra information

                        Comment


                          Originally posted by backkri View Post
                          I have a D101 doorbell, working fine with the plugin. I am trying to add a second instance for a new one on HS3, but motion / ring events are not coming through. I can switch on the IR LED without problem. I tried:
                          I am just going through the same . I have multiple Doorbird installed, and I originally had a D101 doorbell installed which was fully functional in HS4 however encountered the same described above when I added the additional D2101.

                          I removed the D101 and added the new D2101 as the default and it create the default two motion and ring http calls in Doorbird but it did not create additional http calls for the D2101 additional two relays. I added the D101 but did not create additional http calls for the second Doordird.


                          @mrhappy
                          Originally posted by mrhappy View Post
                          WHAT DOES NOT WORK
                          Any of the RFID/fingerprint functionality - let me know if this is needed as I will need someone to test things with
                          The use case for the RFID is external access control through Homeseer. At the moment it can be configured to uses other Homeseer services, such as MQTT but it would be nice if this was embedded at some point into the Doorbird application.

                          As far as I can see the RFID trigger is not exposed through the API however it can be configured internally in the Doorbird app to trigger a relay or call a http call which can be used in Homeseer. So for giggles I created additional http calls for the relays i.e. trigger=3, 4 etc and configured Doorbird RFID sensor to trigger the Relay 1 and relays to fire the http call and this were recorded in Homeseer (with Developer Mode enable) but not written to logs. This was an inert action as Homeseer Doorbird is not configurable to respond to user configured triggers.




                          Comment


                            Has there been any more ideas on what the proper calls are for the second / third instancesof the plugin?

                            Comment


                              Originally posted by NotFu View Post
                              Has there been any more ideas on what the proper calls are for the second / third instancesof the plugin?
                              Unfortunately not. Connected a Fibaro universal bnary sensor to the dry cotnact output of the doorbird as a workaround for the moment.

                              Comment


                                Struggling to get door bird to work with HS4 and register a ring event....

                                Comment

                                Working...
                                X