0.2.0

There are now eight levels instead of five, and every one of them can be renamed from the integration's Configure dialog, under Level names. Levels 1 to 4 are unchanged; the new levels sit between Automatic and Default as 5 Occupancy, 6 Peak Demand Limit and 7 Scheduled, and Default moves from 5 to 8. Every level above Default survives a restart.

Upgrading from 0.1.x: your saved default-priority options are migrated for you. However, a priority: 5 written by hand into an automation or script now means Occupancy, which holds and survives a restart, so delete it to get Default back. A priority-control-card with default_priority: 5 should become 8, and templates comparing effective_priority against 5 should compare against 8. Rolling back to 0.1.9 works, as long as you haven't set a default priority of 5 to 7.

If you're already on 0.2.0b1, the only change is the brightness label in item 6.

Fixes in this release:

1. Devices that come up as unavailable or unknown before reporting their real state now get that state recorded at Default once it arrives, so releasing an override returns them to it instead of leaving them where the override put them. Zigbee, Z-Wave and Thread devices all start this way, as does anything Home Assistant restores as unavailable at startup.
2. The setup and options forms show proper labels; the translations file was never shipped before.
3. Opening the picker in more-info scrolls the dialog down to the end of the list.
4. Picking a level on a group's more-info now applies to the members' own toggles in that dialog.
5. The tile card feature fits its tile again, as one status line with a Release button, instead of a per-level list that spilled out the bottom.
6. A light command sent with raw brightness (0 to 255) now shows its level as a percentage instead of a bare ON. Adaptive Lighting and most integrations send it that way. Thanks to Bluhb_ on Reddit for the report and the fix.

Hard-refresh your browser after updating.