* Limit light to supported settings
When showing light settings, only the supported features will be shown for each light.
* Limit light to supported settings
* Limit light to supported settings
* Limit light to supported settings
* Limit light to supported settings
* Limit light to supported settings
This partially solves #635
* Limits covers to supported settings
Only show cover settings when `set_position` is supported.
This solves #635
* Limits covers to supported settings
This changes the behavior of Wifi icon:
How it was before:
- Wifi icon was visible only when the wifi was connected, nothing was shown when wifi was not connected.
How it is now:
- Wifi icon will have 3 states:
- Wifi & API connected: Gray wifi icon
- Wifi disconnected: Red wifi-off icon
- Wifi connected, but API disconnected (HA is out?): Red api-off icon
This adds support to weather integrations where the `datetime` field under `forecast` attribute is provided as a `datetime` type.
This was seen on Météo-France, while all other weather integrations tested so far used a `text` field for `datetime`.
This solves #893
* Create `nspanel_us_land.tft'
Add `nspanel_us_land.tft' for US panel on landscape mode, fixing the offset on the touch screen when using `nspanel_eu.tft` into a US panel.
Hides the hardware buttons labels, as Nextion cannot support rotated text.
* Created `nspanel_us_land.tft`
* Created `nspanel_us_land.tft`
solves #390
solves #432
solves https://github.com/Blackymas/NSPanel_HA_Blueprint/discussions/299#discussioncomment-4933716
* Created `nspanel_us_land.tft`
* Created `nspanel_us_land.tft`
* Use `en` as fallback language
Uses English if a non valid language is selected (like when using legacy language selection).
* Use `en` as fallback language
* Move `entity` variable to home page
This will enable future development of a fallback climate
* Move `entity` variable to home page
* Move `entity` variable to home page
* Move `entity` variable to home page
* Move `entity` variable to home page
* Remove `settings_entity`
- Bump version to 3.5_dev
- Removed references to pictures removed from TFT
- Removed code related to closing settings pages
- Removed trigger `settings_entity`
* Removed `set_settings_entity` service
- Bump version to 3.5_dev
- Removed `set_settings_entity` service - BREAKING CHANGE
- Removed `settings_entity` text-sensor - BREAKING CHANGE
- Added service `open_entity_settings_page` - BREAKING CHANGE
* Removed `settings_entity`
- Bump version to 3.5_dev
- Removed old climate page (climate_backup)
- Removed pics related to old climate page (ids 16-47, 80-83, 95-96 and 125(US only))
- Enforces brightness on any page change (this allows wake-up on settings page with long press on physical buttons) - Pending removing code from Blueprint
- Added `entity` variable on pages `climate`, `lightsettings` and `coversettings`
- Added `entity` info to `nspanelevent` on pages `climate`, `lightsettings` and `coversettings`
- Added `back_page` variable on pages `climate`, `lightsettings` and `coversettings` (default: home)
- Moving to TFT close page logic on pages `climate`, `lightsettings` and `coversettings` - Pending changes on Blueprint and ESPHome
- Standardized name for `page_label` on pages `climate`, `lightsettings` and `coversettings`
- Standardized settings page names: `climate`, `cover` and `light` (Removed `settings` from page name)
* Removed `settings_entity`
* Removed `settings_entity`
* Removed `settings_entity`
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
