errors after upgrade to 0.6

Thanks Adam,

Have you deleted both devices?

Pete

I've now deleted both devices, and recreated both devices (in that order).

on creation, there were a number of errors, and the devices didn't come online:

Code: Select all

2 Nov 2018 at 4:52:55 pm
   DoorBird Debug                  validateDeviceConfigUi() called
   DoorBird Debug                  closedDeviceConfigUI() called
   DoorBird Debug                  New Doorbird device
   DoorBird Error                  Error in plugin execution UiClosed2:

Traceback (most recent call last):
  File "plugin.py", line 275, in closedDeviceConfigUi
NameError: global name 'Dorbird' is not defined

   Schedule                        update old humidity variables ensuite

2 Nov 2018 at 4:53:57 pm
   DoorBird Debug                  deviceCreated() called

2 Nov 2018 at 4:55:45 pm
   DoorBird Debug                  validateDeviceConfigUi() called
   DoorBird Debug                  closedDeviceConfigUI() called
   DoorBird Debug                  New Doorbird device
   DoorBird Error                  Error in plugin execution UiClosed2:

Traceback (most recent call last):
  File "plugin.py", line 275, in closedDeviceConfigUi
NameError: global name 'Dorbird' is not defined

I've subsequently reloaded the plugin, they are both online, and the logs are quiet - too early to tell if that's permanent given the previous behaviour - will continue watching tonight.

thanks for your help
Adam.

Edit: logs still quiet after an hour - I think they would have been playing up by now previously, so fingers crossed.

Code: Select all

Traceback (most recent call last):
  File "plugin.py", line 275, in closedDeviceConfigUi
NameError: global name 'Dorbird' is not defined



Ahh, now this is a silly typo on my part. I'll get it sorted in the next update. It won't affect the plugin once it's re-started after the device is created.

Let's hope it's stable now. I'm keen to get this bug nutted out. Thanks for your paitience.

Pete

no worries. confirming logs are still clear after several hours.

[I repointed the orphaned bell and motion devices at the new master devices. These are the devices that trigger anything signifiant, so not too much was permanently.broken by the exercise.]

...With this issue I think the only way to understand what's happening is to print the decrypted UDP packet to the log so we can see if your Doorbird is really sending the bell press event or if the plugin is triggering by mistake.

Give me a couple of days and I'll get a new version out that allows printing of the decrypted UDP packet...

I hate to push ion this, but I am only her until Monday, and then gone until February. I can do some work remotely, but it would be better if I can do it while I am still here... and anyway, DoorBird is incredibly slow to respond, so I'd like to get any more data I can find to them ASAP.

Thanks.

...With this issue I think the only way to understand what's happening is to print the decrypted UDP packet to the log so we can see if your Doorbird is really sending the bell press event or if the plugin is triggering by mistake.

Give me a couple of days and I'll get a new version out that allows printing of the decrypted UDP packet...

I hate to push ion this, but I am only her until Monday, and then gone until February. I can do some work remotely, but it would be better if I can do it while I am still here... and anyway, DoorBird is incredibly slow to respond, so I'd like to get any more data I can find to them ASAP.

Thanks.

I just banged together a quick update. It prints raw details from the decrypted UDP packet. You'll likely notice 4 identicle log entries per event. This is expected. The Doorbird sends two packets per port you're listening on (the default is both 6524 & 35344).

https://github.com/kwijibo007/DoorBird.git

Hope this helps,

Pete

...I just banged together a quick update....

Almost. It loads, but there is an error when the request is received, and no packet data prints. It's late where you are. I'll look at the code and see if I can find the problem.

Thanks.

Code: Select all

2 Nov 2018 at 13:11:07
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Status: Online
   DoorBird Debug                  Doorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Error                  DoorBird Status: Unable to update Doorbird details

2 Nov 2018 at 13:15:55
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  Doorbird.doorbell_event() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   Trigger                         DoorBird Ring
   Action Group                    DoorBirdRing
   DoorBird Plugin                 Ring detected
   DoorBird                        Doorbell has rung
   DoorBird                        DoorBird Doorbell: On
   Script Error                    Error in plugin execution compileExecuteSource:

Traceback (most recent call last):
  File "plugin.py", line 209, in compileExecuteSource
  File "plugin.py", line 189, in _compileExecuteSource
  File "<string>", line 4, in _dynamicFunc
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 360, in __call__
SystemExit: None

   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  Doorbird.doorbell_off() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Doorbell: Off
   DoorBird Debug                  ------------------------------
   DoorBird Debug                  DoorBird Status: Decrypted UDP packet details
   DoorBird Debug                      Intercom_ID: ghbeez
   DoorBird Debug                      Event: 1       
   DoorBird Debug                      Timestamp: 1541160954

...I'll look at the code and see if I can find the problem...]

Hmmm. Maybe there isn't a problem. I was expecting an octal dump or something, and thought the dashes were unxecoded data. Now I see that are just formatting. As to the error that was in a script I run, well used to run, on ring.

Thanks to the most recent version of the plugin I now know more. It seems that when the DoorBird (D2101KV) is restarted, it rings the app and sends a ring event via the API. But, it does not ring the physical local doorbell attached to the 2-pin connector on the soft-call button. (see image below). This seems obvious since the 2-pin contacts (and probably the contacts on the 4-pin connector as well) are probably closed by operation of the button and not by a relay. But, in both cases (phantom and real button press) the plugin receives the same event: 1

Screenshot 2018-11-02 at 15.17.36.png (45.92 KiB) Viewed 3727 times

I also have a 2101 (2101V) and the nightly reboot does not send me an alert nor ring the doorbell via the IP Chime. I do not use any of the other contacts, relays, etc.

It is interesting to note the phantom ring problem cleared for a week or so after I replaced the "soft-touch call button." Perhaps the main unit tries to read something from the button (via the 4-wire pin). I have the old button, time to open it up and see if there are any electronics inside, or just a switch.

... I have the old button, time to open it up and see if there are any electronics inside, or just a switch.

Definitely more than just a switch. The photo below is actually the back side of the board. When the button is pressed, the two onboard-switches are pushed against two matching plastic posts inside the case.

doorBird-Soft-Touch_button.png (315.89 KiB) Viewed 3994 times

Now about 12 hours later and the cycle of errors has returned to both devices

I also have a 2101 (2101V) and the nightly reboot does not send me an alert nor ring the doorbell via the IP Chime. I do not use any of the other contacts, relays, etc.

I also have, with the soft-touch button (the backlight on the original button pad failed so they sent me the soft-touch), and I have no phantom rings. I have the IP chime device.

I've upgraded to 0.7.
As per usual, the logs were quiet for a few hours but became noisy again overnight with the usual cycle of error messages.

I've upgraded to 0.7.
As per usual, the logs were quiet for a few hours but became noisy again overnight with the usual cycle of error messages.

Hi Adam,

Would you mind running a custom version of the plugin so we can do some troubleshooting? You can download it here: https://www.dropbox.com/s/wb9vritf782lcfz/DoorBird.indigoPlugin.zip?dl=0

To determine if the Doorbrid device is "off" the plugin detects that the Doorbird has not sent a UDP "keep alive packet" in x seconds. X being the amount set in your plugin devices preferences "Keep Alive Timeout". The default is 30 seconds. The theory being that if your Doorbird does not send a keep alive packet within 30 seconds it must be offline. If the Doorbird is offline and a packet is recived, it turns back on. I think for some reason the variable that holds the timestamp of the last time your Doorbirds checked in is not updating or is invalid. And therefore the device gets caught in a toggle loop.

This version of the plugin prints the values of the current time (as reported by the plugin), the variable holding the value of the perceived last check in and the difference between the two in seconds. The times are printed in unix time (not human readable). This is going to cause a lot logs to be written. When the Doorbirds start toggling on / off in a loop could you please post a few of the log entires so I can see what's happening?

Pete

Thanks for that!
the explanation makes sense [except why does it take a few hours to commence? ]

I had some difficulty forcing this update: I'm guessing because the dropbox version has the same version number as the existing 0.7 [is dropbox pointing at the intended version?] So have since deleted the existing plugin file and manually replaced the file rather than using the 'double-click' process.
The plugin reload of course has stopped the noisy logs for now so lets see what is happening tomorrow morning!