The weather integration is now automatically detected by the Blueprint, based on the attributes provided by the integration itself, so an user selection is not needed anymore.
* Code refactoring - Nextion constants - Colors
No changes in functionalities. Just renaming variables related to colors in order to improve readability.
* Code refactoring - Nextion constants - Icons
* Adding aliases on the first level actions
This will make easier troubleshooting as aliases are shown in the logs.
* Nextion constants - Pages
* Nextion constants - Commands
* Nextion constants - Other pics
* Fixed typo in nextion.pics.hardware.button
* Fixed " 'mui_weekday_today' is undefined"
* Code refactoring/standardization
Refactoring:
- Weather pages
- It might support any weather integration now, including OpenWeather)
- New string for translation (when weather info is not available for a certain day)
- Home page (partial)
* Fix bug "'home_page_values' is undefined"
* Code refactoring - Button pages
Rebuilt button pages in order to improve readability and maintainability.
No changes on functionalities,
* Changed blueprint version to v3.2.2
* Refactoring entities pages
* Reorganizing inputs to improve readability
* Bug fixes: qrcode icon & weather provider
- Fixed bug preventing to detect that QR Code was enabled in order to display the QR code icon on Home page
- Fixed weather integration detection
* Review states(entity_id) to make it more resilient
Reduce the chances of crash if a `states(entity_id)` returns an error.
* Make state_attr(entity_id, attr) more resilitent
To avoid crashes with an invalid return.
* Perf improv: Don't load weather vars unless needed
Performance improvement - don't load weather vars when those are not needed.
* Using alias for delay_value
To make easier to maintain the code.
* Code refactoring: Button press/status
Optimizing code in order to improve readability & maintainability.
* Reorganizing pages variables
As it is now, using `minutes: "/1"`, the time will update every minute, but that could happen when lots of seconds has passed on that minute, making possible the displayed time to be up to 59s late.
By changing that to `seconds: 0` if forces the update in the same rate, but always in the first second of a minute, keeping the displayed time always updated.