errors after upgrade to 0.6

Posted on
Sun Oct 07, 2018 3:19 pm
agame offline
Posts: 178
Joined: Jul 13, 2017
Location: Melbourne, Australia

errors after upgrade to 0.6

I upgraded the plugin to version 0.6 a couple of days ago and have since been seeing experiencing some odd problems.

The two master devices invariably show themselves as offline after a period (state binding is set to 'device status', so I assume these should still be showing green indefinitely?). They will come back green after reloading the plugin. The door birds are operating correctly in other respects (visible in Security Spy, and on the Doorbird App), and are actually still reporting motion and button presses, so I assume this is just a UI issue (?). A status request generates this:

Code: Select all
8 Oct 2018 at 8:08:19 am
   DoorBird                        sent "DoorBird Front (master device status)" status request
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird                        DoorBird Front (master device status): Connected
   DoorBird                            Firmware    : 000112
   DoorBird                            Build Number: 15337269
   DoorBird                            MAC Address : 1CCAE37xxxx
   DoorBird                            Model       : DoorBird D2101BV


There are also bursts of dense error messages in the logs: a slab of which looks like this:

Code: Select all
DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   Schedule                        update old humidity variables ensuite
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Online
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Online
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.check_status() called           



The above log extract was from last night and I haven't been able to replicate this morning, so can't be certain this wasn't transitory. But the status is still drifting from green to grey after a few hours. [assume the inconsistent spelling of 'Dorbird' up there is just a feature of the code...].

Posted on
Mon Oct 08, 2018 5:26 am
kwijibo007 offline
Posts: 238
Joined: Sep 27, 2013
Location: Melbourne, Australia

Re: errors after upgrade to 0.6

Strange. My DoorBird shows green (on) as expected. After how long do they show as off? Do they both turn off at the same time?

Posted on
Tue Oct 09, 2018 4:51 am
agame offline
Posts: 178
Joined: Jul 13, 2017
Location: Melbourne, Australia

Re: errors after upgrade to 0.6

they both seem to be thrashing themselves on/off tens of times per minute (but show as continually grey on the UI once entering that mode). I just tested movement and it was detected successfully but with a longer than expected lag (presumably waiting for one of the brief 'connected' periods. This didn't occur in the previous versions - and given its affecting both devices similarly seems likely to be the plugin rather than a device glitch.

I wonder if I should try rolling back?

here's about a minute's worth of my log just now

Code: Select all
DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   Schedule                        update old humidity variables ensuite
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Online
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Online
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Front (master device status): Online
   DoorBird                        DoorBird Laneway (master device status): Offline
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird Debug                  Doorbird.check_status() called
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird                        DoorBird Laneway (master device status): Online
   DoorBird Debug                  Doorbird.primary_device_state_update() called
   DoorBird Debug                  Dorbird.update_status_fields() called
   DoorBird                        DoorBird Front (master device status): Offline
   DoorBird Debug                  Doorbird.check_status() called
   Error             



every few minutes there's a red 'DoorBird Error' stating 'Unable to update Doorbird details'.

Posted on
Tue Oct 09, 2018 5:11 am
agame offline
Posts: 178
Joined: Jul 13, 2017
Location: Melbourne, Australia

Re: errors after upgrade to 0.6

UPDATE:

looking for a version to try rolling back to, I came across your note on release 0.4.1 on re-saving the master device settings. I was travelling so had skipped from 0.4 to 0.6 and therefore hadn't done that since installing 4.0. So I tried doing that anyhow (still on 0.6) and my log is now clear and status is a nice green - at least it has been for 10 mins.

So fingers crossed problem is solved!

Posted on
Tue Oct 09, 2018 5:20 am
kwijibo007 offline
Posts: 238
Joined: Sep 27, 2013
Location: Melbourne, Australia

Re: errors after upgrade to 0.6

Great news. Let me know if anything weird shoes up again. There were some fairly substantial changes made between 0.5 and 0.6... I was surprised at the lack of issues raised :D

Posted on
Tue Oct 09, 2018 5:21 am
kwijibo007 offline
Posts: 238
Joined: Sep 27, 2013
Location: Melbourne, Australia

Re: errors after upgrade to 0.6

Oh... and I'll fix those "Dorbird" typos in the next update.

Pete

Posted on
Tue Oct 09, 2018 4:25 pm
agame offline
Posts: 178
Joined: Jul 13, 2017
Location: Melbourne, Australia

Re: errors after upgrade to 0.6

ha! thanks. still stable overnight so clearly that was it.

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest