- All the weather pages now shares the same code, increasing standardization
- Support for other forecast parameters when supported by the integration
- Removed empty rows between the forecast parameters
This fix the following error which happens when an entity with a non-numeric value ('unknown', 'unavailable', some text, etc.) is sent to the device:
```
Error: Error rendering data template: ValueError: Template error: round got invalid input 'Geen' when rendering template '{{ states(repeat.item.entity) |round(1) }}{{ state_attr(repeat.item.entity, "unit_of_measurement") }}' but no default was specified
```
This may also implement the feature requested in #490
This add the support to user selected date and time formats.
The following formats are supported now:
- Date formats:
- EU: 22.03
- UK: 22/03
- US: 3/22
- Time formats:
- EU/UK: 13:30
- US: 1:30 AM/PM (the AM7PM info will be depending on updates on TFT file)
- Fix the error where a missing/invalid entity causes the panel to slow down when opening a new page or keeps with "Loading..." on the screen until it timeouts.
This will probably fix#493
- Optimizing MUI (Multilingual User Interface) code in order to make easier add new languages and to read the code. It will probably consume a bit less resources by reducing the number of `if..elif...` and by removing a bunch of `string.replace`.
- Language selection list sorted alphabetically in order to make easier to find
Used YAML alias to simplify the code in the `input:` area. This will make easier to maintain as it creates single points of changes, promoting consistence.
Fix warning message:
Template variable warning: list object has no element 3 when rendering '{%- if settings_entity_value != "unknown" -%} {{ settings_entity_value.split(',')[3] }} {%- else -%} unknown {%- endif -%}'
