Removed all inputs related to customization of chip03 (Climate entity) and instead will follow the same icons and colors used by page climate, with a thermometer replacing the fire icon for heating.
* Fix `hvac_action` indication icons
Fix for pages home and climate.
This should remove the need for all the 25~30 instances of hot water in the code.
* Update nspanel_esphome.yaml
* Climate - Custom buttons - Long press
This add long press functionality to Custom buttons and also fix a bug on short press.
I believe the new custom page is ready for get user's feedback with this.
* Climate - Custom buttons - Long press
* Climate - Custom buttons - Long press
* Climate - Custom buttons - Long press
* Climate page - Performance & bug fix
Performance improvement:
- Moved icon definition to TFT, so only buttons related to supported hvac modes will be updated and just icon color and link enabling is sent.
Bug fixing:
- Removed incorrect button name on buttons update
Others:
- Merged `set_climate_target_temp` into `set_climate` services
- Update current temperature when target temperature is updated
* Removed reference to `set_climate_target_temp`
Removed unused entry from blueprint.
* Removed service `set_climate_target_temp`
* Update `nspanel_eu`
- Set climate buttons on the TFT.
- Bump version to 3.3.2 (temporarily, to align with ESPHome and Blueprint)
* Update `nspanel_eu_code`
* Climate: support to `target_temp_step`
Adding support to attribute `target_temp_step` to define the step of changing temperature.
`0.5` will be used if this attribute is not available on the climate entity.
* Update nspanel_esphome.yaml
* Update nspanel_eu files
* Update nspanel_eu_code files
* 2sec hold for sending target_temp
Added 2sec hold of `target_temp` value before sending it to ESPHome and Blueprint, so the climate service is not called at every click on the slider or +/-.
* Update nspanel_eu_code
* Fix buttons on climate page
Fix icon for dry and auto.
Move Off for last position.
Fix TFT sending incorrect id for buttons.
* Update TFT
* Update nspanel_eu_code
* Move target_temp set to TFT
Use TFT to set target temp from slider and +/-.
Using decimals for slider.
* Update nspanel_esphome.yaml
* Update nspanel_eu files
* update nspanel_eu_code folder
* New climate page - basic support
Basic support to the new climate page.
Still pending values and buttons.
* Support to new climate services
* New climate page - basic
* Enable users select alignment for entity values
Users will be able to select the alignment for the column with values on the entity pages.
The options are:
- Right (default)
- Center
- Left
solves #732
* Add support to `xcen` on `set_entity`
* More flexible `date_format` engine
This is not changing anything for normal users other than minor UI on the blueprint setting, however will start using the `date_format` in a python standard string, but translating `%A` with existing weekdays in MUI.
Advanced users will be able to edit they automation yaml (either in `automations.yaml` file or editing the automation in yaml mode) in order to use any format they want.
=> This is not adding new translations to short week days or months, so if users add this in advanced mode, it will be shown in English.
* Added support for translation of date strings
Support translations to all date related strings.
=> Pending the translations - to ask support from the community.
* Support for custom date formats
* Fixed translation PRT
* Update nspanel_blueprint.yaml
This is a simplified version of #728 which is easier to maintain, as only conditions for entities pages have being added.
So the scope is limited to:
- Auto-update entity pages without compromising overall performance. (Entities page values not updating unless re-opened #410)
Takes advantage of new global vars implemented by eee2bb7295
This will improve drastically the speed on displaying the Home page.
This push removes the update of date & time from the Home page and moved it to the time minute trigger (every minute), regardless the page shown (including when sleeping).
The time is also update after a boot (to ensure there's a time value when the Home page is displayed for the first time) and with an automation reload (just to cover the case when time format changes).
This prevents message `Nextion reported variable name invalid!` when the button have a state other than `on` or `off`, like when it is connected to a stateless entity (scene, automation, etc.).
