Supports hidden ssid with the use of substitutions `wifi_hidden: "true"`.
This can be breaking change for users with custom/advanced wifi settings.
Solves #906
Moving service calls back to the blueprint as latest HA requires user's permissions to call HA services from ESPHome.
This still have to be used for Alarm calls due to security concerns.
* Performance improvements
The main focus here was to reduce the number of calls between Home Assistant and ESPHome, moving logic as much as possible to TFT and ESPHome.
- Service calls moved to ESPHome (in preparation for Alarm Control Panel)
- Page change informed via event call instead of `nspanel_event` sensor (which still in use by other calls, but might be possible to remove in the future)
* Draft embedded climate
This adds an initial version of an embedded climate/thermostat (heating only for now) with support for local control even with Wi-Fi out.
Solves #646
Solves #263
* Update ReleaseNotes.md
* Fix climate slider
Fix for climate slider opening in an incorrect position and sending only the integer part of the new target temperature
* Moving home page to ESPHome
In progress...
* Fix translations - Dutch
* Embedded chip 3
Home page - Chip 3 will be controlled locally when embedded climate is enable.
* Fixed buttons bar
Fixed buttons bar managed on ESPHome when embedded climate is visible.
We are trying to make your panel as autonomous as possible by moving some of the controls from the Blueprint to ESPHome. This will reduce the load in your network and Home Assistant, but also will make a more reliable system capable to do it's core functionality even when the network is unavailable or Home Assistant is restarting.
With this version, the following engines have been moved to your panel (local control):
- Physical relay control (when hardware left button is connected to relay 1 or right button to relay 2)
Solves #910
* Panel offline mode
Introduces "offline mode" for the panel, which will be used later with a fallback climate.
Pages that are depending on the blueprint (buttons pages, entity pages, settings pages, etc) won't be shown when the API is disconnected.
* Panel offline mode
* Panel offline mode
* Panel offline mode
* Panel offline mode
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
* 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`
* 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 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
* 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`
* Changes to nextion_inited
Changed from `switch` named `Nextion inited` (with entity_id like `switch.xxxx_nextion_inited`) to a `binary_sensor` named `Nextion display` (`binary_sensor.xxxx_nextion_display`).
The idea is to avoid users trying to change it's state from Home Assistant (with unknown consequences) and make this entity more clear, improving usability.
* Change `nextion_inited` to a sensor
* Rename 'Sleep mode' switch
Renamed from `Sleep Modus` to `Sleep mode`.
Breaking change: This will rename the entity_id of that switch and this can affect existing automations created by users and also will require changes in the blueprint if #698 is merged.
Note: Variable names in HMI/TFT not renamed.
* Align with other PR
