v1.0.2

Changelog

1.0.2

• Reply-then-push fallback: reply_token now attempts the free Reply API for the first target and automatically falls back to the Push API on failure. Remaining targets always use Push.
• Pending user cap: Webhook capture is now capped at 20 pending accounts (FIFO). Oldest entry is evicted when the cap is reached.
• Entity IDs from recipient_name: Notify entity IDs are now derived from the ASCII recipient_name field (notify.line_bot_<recipient_name>), not the display name.
• Confirm checkbox in setup: The webhook setup step now requires ticking a confirmation checkbox before proceeding.
• Event-driven options flow: The "waiting for message" spinner now wakes immediately when a new account is captured, instead of polling on a fixed interval.
• Two-step add-recipient flow: Account selection and name entry are now separate steps, making multi-account adds clearer.
• single_config_entry: true added to manifest, preventing duplicate integration entries.
• iot_class corrected to cloud_push (webhook is the primary data path).
• Service registered once at integration level instead of per config entry.
• Shared API helpers extracted to api.py, eliminating duplicated HTTP logic across __init__.py and notify.py.
• Sensor improvements: Quota coordinator now passes config_entry= to DataUpdateCoordinator; quota and consumption fetched in parallel; both sensors marked EntityCategory.DIAGNOSTIC; unlimited plans correctly report None for limit instead of 0.
• Webhook robustness: Validates payload structure before processing; room events are explicitly skipped; one config entry write per request instead of per event; LINE_TEST_REPLY_TOKEN constant used to filter LINE's internal test events.
• CONFIG_SCHEMA set to cv.config_entry_only_config_schema(DOMAIN) per HA standards.
• hacs.json cleaned up (removed invalid domains and category keys).
• Various bug fixes and code quality improvements throughout.