jhansche/ha-birdbuddy v0.1.0

on GitHub

What's Changed

This is a massive release thousands of lines of code improved and many bugs fixed, thanks to @parrot-tailor, across both the integration and the python library.

• Modernize the integration's tooling, CI, and docs by @parrot-tailor in #108
• Migrate to pybirdbuddy v0.1.0 and its server-side postcard flow by @parrot-tailor in #109

🚨 Breaking changes!

Adopting [pybirdbuddy] v0.1.0 moves the integration to Bird Buddy's
server-side postcardCollect flow. Entities keep their IDs and history,
and automations built on the "A new postcard is ready" Device Trigger carry
over untouched, since the trigger resolves the event internally. Automations
that reference the event or the service directly need updating:

• birdbuddy_new_postcard_sighting — renamed to
  birdbuddy_new_postcard. The payload carries
  postcard_id, feeder_id, species, and media in place of the
  postcard and sighting report objects.
• birdbuddy.collect_postcard — takes postcard_id, plus optional
  feeder_id and share, in place of the postcard and sighting
  objects. Bird Buddy identifies species server-side, so the schema now
  rejects strategy and best_guess_confidence; share_media becomes
  share.
• The bundled Blueprint — re-import it and re-create any
  automation built from it, since it now uses the renamed event and the new
  service inputs.

Re-importing the Blueprint covers everything if you use it without
customizing the payload.

Home Assistant raises a Repairs notice while an automation or script still
triggers on birdbuddy_new_postcard_sighting. Editing that trigger clears
the notice on a following update poll.

New Contributors

• @parrot-tailor made their first contribution in #108

Full Changelog: v0.0.24...v0.1.0
pybirdbuddy 0.1.0 release: https://github.com/jhansche/pybirdbuddy/releases#release-v0.1.0