v1.5.1

• furbo.get_events did not work at all in 1.5.0. Every call came back as
  Furbo API error 400 (code 12001). The cloud requires the list of cameras
  and 1.5.0 treated it as optional, so a call that did not name one was
  refused. It now defaults to every camera on the account, and naming one
  still narrows it. Found by the reporter in #6 testing it the day it shipped.
• Event names are checked before the call. Furbo answers a name it does
  not recognise with the same bare 12001 it gives for a missing field, so a
  typo was indistinguishable from a bug. The field is now a dropdown of the
  names Furbo accepts.
• furbo.get_events read a plain time in the wrong timezone. A window
  written without an offset, which is how most people write one, was read in
  the timezone of the machine Home Assistant runs on rather than the timezone
  Home Assistant is set to. On a container those differ: asking for 19:00 from
  a London install fetched the clips from 20:00. Both ends of the window are
  now read as the local time the automation was written in.
• A window with an offset on one end and not the other no longer fails.
  Mixing the two raised an unhandled error instead of returning clips.
• The repair notice about the add-on waiting for a verification code is now
  cleared when the account is deleted. It was registered against the
  integration rather than the entry, so removing the account left a permanent
  warning about an add-on nothing was waiting on, with nothing to press.