0.4.0 no problems, 1 note

[berkinet]

Just installed 0.4.0 and it works fine. Thanks!

One small note. After upgrading I started getting the following errors:

• DoorBird Debug Doorbird.primary_device_state_update() called
  DoorBird Error DoorBird Status: Unable to read keep alive time

I just had to open the former "Status" device, enter Edit Device Settings, then Save and Close.

[berkinet]

Just installed 0.4.0 and it works fine....

I wrote too soon. When creating a trigger, the states list is broken. Here is what it shows:

Screen Shot 2018-08-05 at 15.27.58.png (38.65 KiB) Viewed 3668 times

If I select Motion On/Off State or Doorbell On/Off State I do not get the options Has Any Change", Becomes On, or Becomes Off.
If I select the On or Off below each of the states noted above, then I get the Any, True or False choices.

Having a single state, with Any, On or Off is more common. But, having specific states with True, etc is Ok. I guess not offers flexibility as -is, though it should be one way or the other. But, in either case, the separate states, should be labeled for clarity. I.e. Doorbell On, Doorbell Off, etc.

[kwijibo007]

Thanks for testing.

One small note. After upgrading I started getting the following errors:

• DoorBird Debug Doorbird.primary_device_state_update() called
  DoorBird Error DoorBird Status: Unable to read keep alive time

I just had to open the former "Status" device, enter Edit Device Settings, then Save and Close.

I'll try to replicate and sort this out

Just installed 0.4.0 and it works fine....
I wrote too soon. When creating a trigger, the states list is broken.

Wow, that's a bug. There should only be On/Off State actions. Not sure how this has happened. I'll investigate

Pete

[kwijibo007]

When creating a trigger, the states list is broken

Just uploaded 0.4.1 which fixes the state list.

One small note. After upgrading I started getting the following errors:
DoorBird Debug Doorbird.primary_device_state_update() called
DoorBird Error DoorBird Status: Unable to read keep alive time
I just had to open the former "Status" device, enter Edit Device Settings, then Save and Close.

This one's got me stumped. I'm pretty sure the error is because the new "State Binding" field was not set until you saved the Device Settings. I don't understand why because it's assigned a default value. It's only an issue the first time you update but it's really not ideal. I'm using the stateListOrDisplayStateIdChanged() method within deviceStartComm but that's for states, not properties. Any thoughts?

Pete

[berkinet]

...Just uploaded 0.4.1 which fixes the state list.

Actually, the update fixed the states list issue as well. Seems to be working fine. But, I will keep testing.

Thanks!

[neilk]

Upgraded and all good for me. I did get the keep alive error but the edit/save cleared it straight away.

[kwijibo007]

Upgraded and all good for me. I did get the keep alive error but the edit/save cleared it straight away.

Thanks for testing. I would love to fix it but I can’t replicate it as it’s a one-off update error. New installs should be fine.

[agame]

Also got a flood of keep alive errors on upgrade but after re-saving the master devices appears to be working fine.