- Fix: MQTTt not being ready at startup. by @xNUTx in #149
- Support for HA 2024.9 by @dgomes
- fix: Reuse of the same image with different sized displays causes a random resize. by @xNUTx in #143
- fix: Dynamic reloading broken on recently added displays. by @xNUTx in #140
- feat: Added optional setting http_proxy to push_image by @xNUTx in #144
- Fixes 'str' object has no attribute 'read' by @illuzn in #132
- Replace deprecated async_forward_entry_setup call by @TNTLarsn in #137
- fix: properly split jsonl upload at lineends by @akloeckner in #138
- Support for 2024.6.0
- Fixed height & width were being transposed when fitscreen=true by @FreeBear-nc in #121
- Move file open() to executor job by @dgomes in #123
- feat: allow full script syntax in event section by @akloeckner in #112
- Support discovery through mDNS (0.7.0-rc11 or higher)
- Support for HA 2024.1
- Replace version popup for legacy 0.6.x plates with log warning
- Fix error as
ANTIALIAS
was removed in Pillow 10.0.0. Now usingLANCZOS
instead. - Updated Manifest.json
- Better handling of discovery for 0.7.0-dev firmware
- Support for 2022.7.0
- Code improvements
- Support for 2022.4.0
- Adds page number entity
- Adds restart button
- Code improvements
- Support for 2021.12.0
- Change startup message from warning to info (@fvanroie)
- Adds configuration URL
- Antiburn configuration switch
- Minor bug fixes
- Accepts .json files which contain an array
- JSON files undergo schema validation
- JSONL batching improves performance
- Add new service that serves images directly to OpenHASP
- Fixes to work with HA 2021.8.1
- Improves UX
- Entity names have changed
- Configuration is now handled through the UI (Config-flow)
- Plates are discovered
- Component checks firmware version on discovery
- GPIO's are exposed as Light's and Switches as configured in the plate
- Sync with all the changes in firmware version 0.6.0
- Cleans all subscriptions and updates on device removal
It is recommended that you erase configuration from your yaml file (except for objects) and follow the instructions on the log file about the slug to be used in the yaml file.