v0.6.1

What's Changed

• Added Brand Images.
• Updated Readme to contain verbiage required to be in compliance with YNAB's API Terms of Service

Full Changelog: v0.6.0...v0.6.1

v0.6.0

What's Changed

• Changes to coordinator flow to keep in line with Home Assistant changes.

Bug Fixes

• Fixes bug where all entities would become unavailable.
• Fixes error about ConfigEntryError in forwarded platform sensor.

Full Changelog: v0.5.1...v0.6.0

v0.5.1

What's Changed

• Home Assistant removed the async_forward_entry_setup method. So switched to the new async_forward_entry_setups method instead.

Full Changelog: v0.5.0...v0.5.1

v0.5.0

What's Changed

• Sync all categories by @birdwing in #5

Full Changelog: v0.4.1...v0.5.0

v0.4.1

Bug Fixes

• Update sensors to use enumeration for State Class since the constant STATE_CLASS_TOTAL was removed.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

🚨Breaking Change 🚨

Version 0.4.0 and onward now sets budgets up as individual "devices", with each account and category selected becoming it's own sensor.
If you were previously using template sensors in order to create sensors for individual categories, this will break those template sensors.
Any automations, templates or cards pulling category data from the old single sensor attributes will break!
It is the hope that these individual sensors will make maintaining your YNAB data easier.

What's Changed

• Switch API to use a Data coordinatory by @birdwing
• Split entity into multiple sensors by @birdwing
  • Budget sensor: for storing budget "device" data
  • Balance sensor - split into 2 child sensors
    • Account sensor: for storing account data
    • Category Sensor: for storing category data
• Switch to using ID's instead of names for selecting categories and accounts by @birdwing
• Separate Icons for different sensors by @birdwing
• Update Readme to reflect changes, and remove old YAML configuration instructions

Full Changelog: v0.3.1...v0.4.0

v0.4.0-beta.1

🚨Breaking Change 🚨

Version 0.4.0 and onward now sets budgets up as individual "devices", with each account and category selected becoming it's own sensor.
If you were previously using template sensors in order to create sensors for individual categories, this will break those template sensors.
Any automations, templates or cards pulling category data from the old single sensor attributes will break!
It is the hope that these individual sensors will make maintaining your YNAB data easier.

What's Changed

• Switch to using ID's instead of names for selecting categories and accounts by @birdwing
• Separate Icons for different sensors by @birdwing

Full Changelog: v0.4.0-beta...v0.4.0-beta.1

v0.4.0-beta

🚨Breaking Change 🚨

Version 0.4.0 and onward now sets budgets up as individual "devices", with each account and category selected becoming it's own sensor.
If you were previously using template sensors in order to create sensors for individual categories, this will break those template sensors.
Any automations, templates or cards pulling category data from the old single sensor attributes will break!
It is the hope that these individual sensors will make maintaining your YNAB data easier.

What's Changed

• Switch API to use a Data coordinatory by @birdwing
• Split entity into multiple sensors
  • Budget sensor: for storing budget "device" data
  • Balance sensor - split into 2 child sensors
    • Account sensor: for storing account data
    • Category Sensor: for storing category data

Full Changelog: v0.3.1...v0.4.0-beta

v0.3.1

What's Changed

• Standardize attribute names using HA's provided slugify util - Thanks @eabruzzese
• Set currency type by iso code instead of symbol by @birdwing

v0.3.0

What's Changed

• Update YNAB with Base integration by @birdwing in #1
• Add Config flow from tomreay's ynab fork by @birdwing in #2

Full Changelog: v0.1.11...v0.3.0