Update Wiki and First Steps
hollabee
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082420725.png
Normal file
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082420725.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082450296.png
Normal file
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082450296.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082520575.png
Normal file
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082520575.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082614749.png
Normal file
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082614749.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 138 KiB |
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082638657.png
Normal file
BIN
(DE)-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082638657.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 92 KiB |
@@ -5,69 +5,93 @@ Im Prinzip ist die Einrichtung der Automatisierung selbsterklärend. Nachfolgend
|
||||
|
||||
|
||||
# Parameter
|
||||
### 1. ESPhome Node Name
|
||||
#### ESPhome Node Name
|
||||
Bezieht sich auf den ESPhome-Gerätenamen. **Zulässig sind die Zeichen "__",a-z, 0-9, jedoch keine Sonder- und Leerzeichen**. Dies ist eine Einschränkung seitens HA, da aus dem Device-Name des Blueprints die jeweiligen Entity_IDs generiert werden.
|
||||
|
||||
### 2. Language for NSPanel
|
||||
#### Language for NSPanel
|
||||
Über das Dropdown Menü kann die Sprache ausgewählt werden. Unterstützt werden derzeit 26 Sprachen.
|
||||
|
||||
### 3. Nextion TFT File Folder
|
||||
#### Nextion TFT File Folder
|
||||
Kann freigelassen werden. Wird aber benötigt, wenn eine eigene TFT Konfiguration verwendet werden soll.
|
||||
|
||||
### 4. Delay
|
||||
#### Delay to avoid synchronization problems
|
||||
Es kann bei schlechtem WLAN Signal vorkommen, dass Menüs nicht komplett geladen werden. Sollte dies vorkommen, kann hier ein Delay in 5ms Schritten eingestellt werden, um dies zu kompensieren.
|
||||
|
||||
### 5 . Synchronisation of all all values
|
||||
#### Synchronization of all all values (Optional)
|
||||
Light und Cover Seiten (Werte) werden kontinuierlich upgedatet (kann zu Flackern führen).
|
||||
|
||||
### 6. Synchronisation of all all Sliders
|
||||
#### Synchronization of all all Sliders (Optional)
|
||||
Light und Cover Seiten (Position der Cover) werden kontinuierlich upgedatet (kann zu Flackern führen).
|
||||
|
||||
### 7. Weather Integration
|
||||
#### Weather Integration
|
||||
Auswahl zwischen der HA Weather Integration oder dem genaueren Accuweather.
|
||||
|
||||
### 8. Name Weather
|
||||
#### Weather entity from HA
|
||||
Dropdown Menü zur Auswahl der zu verwendenden Weather Entität. Beispiel: Wenn in Punkt 7 "Accuweather" ausgewählt wird, so muss hier die Entität für Accuweather ausgewählt werden.
|
||||
|
||||
### 9. Outdoor Temperature
|
||||
#### Outdoor Temperature Sensor (Optional)
|
||||
Optional kann hier der Wert eines Aussentemperatur Sensor verwendet werden. Falls kein separater Sensor verwendet wird, wird der Wert der Wetter-Integration verwendet.
|
||||
|
||||
### 10. Humidity Sensor
|
||||
#### Indoor Temperature Sensor (Optional)
|
||||
|
||||
Optional kann hier der Wert eines InnentemperaturSensor verwendet werden. Wird das Feld leer gelassen, wird der Temperatursensor des NSPanels verwendet. Zusätzlich ist unter HA Devices eine Temperaturkorrektur für den NSPanel-Sensor möglich.
|
||||
|
||||
#### Humidity Sensor (Optional)
|
||||
Optionaler Innen-Feuchte Sensor.
|
||||
|
||||
### 11. Hot Water Temperatur Sensor
|
||||
#### Hot Water Temperatur Sensor (Optional)
|
||||
Optionaler Heiß Wasser Sensor.
|
||||
|
||||
### 12. Hot Water Switch
|
||||
Optionaler Warm Wasser Schalter, bspw. für einen Boiler.
|
||||
#### Hot Water Charge (Optional)
|
||||
Optionaler Schalter um bspw. einen Boiler an- bzw. aus zu schalten.
|
||||
|
||||
### 13. Top 04 Flame
|
||||
#### Top 04 Flame
|
||||
Zeigt ein Flammen-Symbol auf dem Home Screen an, bspw. wenn eine Therme angeschaltet (On) ist.
|
||||
|
||||
### 14. Climate to Control
|
||||
#### Climate to Control (Optional)
|
||||
Wenn eine Climate Integration gesteuert werden soll, muss diese hier eingegeben werden. Erreichbar ist diese dann über die Temperatur auf dem Home Screen des NSPanels.
|
||||
|
||||
### 15. Climate Control optimistic Mode
|
||||
#### Climate Control optimistic Mode (Optional)
|
||||
Abhängig von der Klima Steuerung, kann für ein besseres Ansprechverhalten der Optimistic Mode verwendet werden. Die vorgenommenen Änderungen werden erst bei verlassen des Screens auf das Device übertragen.
|
||||
|
||||
### 16. Left Button Switch
|
||||
Linker Hardware Button des NSPanel.
|
||||
#### Activate QR Code (Optional)
|
||||
|
||||
### 17. Name Left Button Switch
|
||||
Aktiviert die QR Code Page sowie den Button auf dem Home Screen.
|
||||
|
||||
#### Name "QR Code Page" (Optional)
|
||||
|
||||
Bezeichnung des QR Screens, wenn diese aufgerufen wird.
|
||||
|
||||
#### QR Code content (Optional)
|
||||
|
||||
String, der als QR Code dargestellt werden soll. Dies kann ein Text sein, eine URL oder beispielsweise auch für einen vereinfachten Login ins WiFi verwendet werden (hier einfach SSID und Password ersetzen sowie entweder "WPA" oder "WEP" verwenden):
|
||||
|
||||
```WIFI:S:SSID;T:WPA/WEP;P:PASSWORD;;```
|
||||
|
||||
#### Left Button (Optional)
|
||||
Hier kann die Entitiy ausgewählt werden, welche mit dem linken Hardware Button geschaltet werden soll.
|
||||
|
||||
#### Name Left Button (Optional)
|
||||
Text auf dem Screen über dem linken Hardware Button (Home Screen)
|
||||
|
||||
### 18. Right Button Switch
|
||||
Rechter Hardware Button des NSPanel.
|
||||
#### Activate Relay 1 local Fallback (Optional)
|
||||
|
||||
### 19. Name Right Button Switch
|
||||
Normalerweise werden die internen Relays über HA getriggert. Ist dieser Menüpunkt aktiviert, so wird das Relay 1 bei betätigen des Linken Hardware Buttons geschaltet, sollte HA offline sein.
|
||||
|
||||
#### Right Button (Optional)
|
||||
Hier kann die Entitiy ausgewählt werden, welche mit dem rechten Hardware Button geschaltet werden soll.
|
||||
|
||||
#### Name "Right Button" (Optional)
|
||||
Text auf dem Screen über dem rechten Hardware Button (Home Screen)
|
||||
|
||||
### 20. Name Button Page 1- 4
|
||||
#### Activate Relay 2 local Fallback (Optional)
|
||||
|
||||
Normalerweise werden die internen Relays über HA getriggert. Ist dieser Menüpunkt aktiviert, so wird das Relay 2 bei betätigen des Linken Hardware Buttons geschaltet, sollte HA offline sein.
|
||||
|
||||
#### Name Button Page 1- 4
|
||||
Text auf den jeweiligen Button Screens.
|
||||
|
||||
|
||||
|
||||
### Buttons 01 - 32
|
||||
#### Buttons 01 - 32 (Optional)
|
||||
Die Buttons sind durch Wischen auf dem Home Screen zu erreichen und in ihrer Funktion völlig identisch.
|
||||
Entweder können nacheinander die einzelnen Button Pages durch Wischen nach links erreicht werden, oder direkt auf die Button Pages durch Wischen nach oben, unten oder rechts angesprungen werden.
|
||||
|
||||
@@ -96,13 +120,43 @@ Wenn der jeweilige Button gedrückt wird, wird automatisch die korrespondierende
|
||||
Für jeden Button kann optional ein eigener Name angegeben werden.
|
||||
Alle Buttons bieten die Möglichkeit, die Ausführung der Aktion optional bestätigen zu lassen. Dies kann separat für jeden Button über *"Confirm execution of the button press"* aktiviert bzw. deaktiviert werden.
|
||||
|
||||
#### Activate Entity Pages (Optional)
|
||||
|
||||
Hiermit können die Entity Pages auf dem Home Screen aktiviert werden. Diese können verwendet werden, um bspw. Werte oder Status von Entitäten auf den einzelnen Pages darzustellen.
|
||||
|
||||
#### Entity 01 - 32 (Optional)
|
||||
|
||||
Die Entity Pages sind durch drücken auf das Entity Symbol auf dem Home Screen zu erreichen und in ihrer Funktion völlig identisch.
|
||||
|
||||
Die Entities sind wie folgt nummeriert:
|
||||
|
||||
| | Entity Page 1 | Entity Page 2 | Entity Page 3 | Entity Page 4 |
|
||||
| ------- | ------------- | ------------- | ------------- | ------------- |
|
||||
| Zeile 1 | 01 02 03 04 | 09 10 11 12 | 17 18 19 20 | 25 26 27 28 |
|
||||
| Zeile 2 | 05 06 07 08 | 13 14 15 16 | 21 22 23 24 | 29 30 31 32 |
|
||||
|
||||
Zusätzlich besteht die Möglichkeit, ein Icon für jede Entität aus derzeit 6896 Icons auszuwählen.
|
||||
Natürlich gibt es auch die Möglichkeit, eine eigene Entitätsbezeichnung einzugeben und eine Bezeichnung für die 4 Seiten zu vergeben. Wenn kein Entity-Label gesetzt ist, wird der Friendly Name von HA übernommen.
|
||||
|
||||
Die derzeit verfügbaren Icons finden sich hier: https://htmlpreview.github.io/?https://github.com/jobr99/Generate-HASP-Fonts/blob/master/cheatsheet.html
|
||||
|
||||
Zum Einfügen des ausgewählten Icons auf das "U" des Icons klicken und in das jeweilige Feld im Blueprint einfügen. Es wird danach ein "komisches" Symbol im Blueprint angezeigt, dies ist jedoch korrekt.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
***
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082420725.png)
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082450296.png)
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082520575.png)
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082614749.png)
|
||||
|
||||
...
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082638657.png)
|
||||
|
||||
@@ -38,12 +38,12 @@ In diesem Beitrag geht es um die erst Konfiguration. Hier werden alle wichtigen
|
||||
> Es ist auch möglich den Code aus der Datei _**"nspnael_blueprint.yaml"**_ zu kopieren und in HA einzufügen.
|
||||
> Hinweise dazu findest du unter [Using Automation Blueprints](https://www.home-assistant.io/docs/automation/using_blueprints/) und [Automation blueprint tutorial](https://www.home-assistant.io/docs/blueprint/tutorial/#create-the-blueprint-file)
|
||||
|
||||
#### 2. Nun muss von Github das File **_"nspanel.tft"_** herunter geladen werden
|
||||
#### 2. Nun muss von Github das File **_"nspanel_eu.tft"_** oder **_"nspanel_us.tft"_**heruntergeladen werden
|
||||
|
||||
|
||||
|
||||
|
||||
#### 3. Das File **_"nspanel.tft"_** muss nun auf deinen Home Assistant Server in den Ordner **_"www"_** hochgeladen werden. Siehe dazu auch hier [Home Assistant HTTP](https://www.home-assistant.io/integrations/http/#hosting-files) 'Hosting Files' Bereich für weiter Informationen.
|
||||
#### 3. Das File muss nun auf deinen Home Assistant Server in den Ordner **_"www"_** hochgeladen werden. Siehe dazu auch hier [Home Assistant HTTP](https://www.home-assistant.io/integrations/http/#hosting-files) 'Hosting Files' Bereich für weiter Informationen.
|
||||
|
||||
|
||||
|
||||
@@ -71,8 +71,8 @@ substitutions:
|
||||
wifi_ssid: "YOUR WIFI SSID"
|
||||
wifi_password: "YOUR WIFI PASSWORD"
|
||||
|
||||
nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel.tft" # URL to local tft File
|
||||
# nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft" # URL to Github
|
||||
nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel_eu.tft" # URL to local tft File
|
||||
# nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_eu.tft" # URL to Github
|
||||
|
||||
##### CHANGE ME END #####
|
||||
|
||||
@@ -92,18 +92,20 @@ packages:
|
||||
```
|
||||
|
||||
|
||||
> Im Pfad **_http://HOME-ASSISTANT-IP:8123/local/nspanel.tft_** muss nun die IP Adresse von deinem _**Home Assistant Server**_ eingetragen werden. (_**/local/**_ ist das selbe Verzeichnis wie **_"www"_**
|
||||
> Im Pfad **_http://HOME-ASSISTANT-IP:8123/local/nspanel_eu.tft_** muss nun die IP Adresse von deinem _**Home Assistant Server**_ eingetragen werden. (_**/local/**_ ist das selbe Verzeichnis wie **_"www"_**
|
||||
>
|
||||
>
|
||||
|
||||
> Das kann dann wie folgt aussehen **_http://192.168.1.1:8123/local/nspanel.tft_**
|
||||
> Das kann dann wie folgt aussehen **_http://192.168.1.1:8123/local/nspanel_eu.tft_**
|
||||
|
||||
> ⚠️ **_ACHTUNG_** Du kannst auch den Pfad zu Github verwenden **_https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft_** und das TFT direkt von Github herunter laden. Aber dabei kann es zu Problemen mit dem Upload zum NSPanel kommen. Das hängt von deinem Internet und WLAN ab. Für mehr Informationen zu diesem Thema schauen auf der **_Issue_** Seite im Github. Das ganze sollte dann so aussehen
|
||||
> ⚠️ **_ACHTUNG_** Du kannst auch den Pfad zu Github verwenden **_https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_eu.tft_** und das TFT direkt von Github herunter laden. Aber dabei kann es zu Problemen mit dem Upload zum NSPanel kommen. Das hängt von deinem Internet und WLAN ab. Für mehr Informationen zu diesem Thema schauen auf der **_Issue_** Seite im Github. Das ganze sollte dann so aussehen
|
||||
|
||||
```
|
||||
# nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel.tft" # URL to local tft File
|
||||
nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft" # URL to Github
|
||||
# nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel_eu.tft" # URL to local tft File
|
||||
nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_eu.tft" # URL to Github
|
||||
```
|
||||
|
||||
|
||||
> ⚠️ **_ACHTUNG_** soll das US Layout des Panels verwendet werden, dann muss anstelle von "nspanel_eu.tft" in der nextion_update_url "nspanel_us.tft" verwendet werden!
|
||||
|
||||
#### 6. Jetzt kann das NSPanel mit dem neuen ESPHome Code geflasht werden
|
||||
> wie das NSPanel geflasht wird kannst du dir hier ansehen [Anleitung - Flash Sonoff NSPanel mit ESPHome](https://www.youtube.com/watch?v=3afPFg6kUdc)
|
||||
@@ -163,8 +165,8 @@ _**"ESPHome: DEVICE_NAME_upload_tft"**_ --> (esphome.device_name_upload_tft)
|
||||
|
||||
* Blueprint Datei _**"nspnael_blueprint.yaml"**_ kann auch manuell installiert werden
|
||||
* ESPHome Datei_**"nspanel_esphome.yaml"**_ kann auch manuell installiert werden. Dadurch können weitere _**"Advanced"**_ Konfigurationen aktiviert oder hinzugefügt werden.
|
||||
* Außerdem besteht die Möglichkeit das TFT File _**"nspanel.tft"**_ manuell hochzuladen. Das Ganze kann auch mit einem _**"Folder Watcher"**_ kombiniert werden
|
||||
* zusätzlich stellen wir die HMI Datei _**"nspanel.HMI"**_ für den Nextion Editor zur Verfügung, um Grafiken und Programmierung bei bedarf anpassen zu können
|
||||
* Außerdem besteht die Möglichkeit das TFT File _**"nspanel_eu.tft"**_ manuell hochzuladen. Das Ganze kann auch mit einem _**"Folder Watcher"**_ kombiniert werden
|
||||
* zusätzlich stellen wir die HMI Datei _**"nspanel_eu.HMI"**_ für den Nextion Editor zur Verfügung, um Grafiken und Programmierung bei bedarf anpassen zu können
|
||||
|
||||
> _**ACHTUNG!**_ Wer diesen Modus benutzt, sollte wissen was er tut. Wir geben hier keinen Support!
|
||||
|
||||
|
||||
@@ -7,99 +7,123 @@ In principle, the setup of the automation is self-explanatory. The individual el
|
||||
|
||||
# Parameters
|
||||
|
||||
### 1. ESPhome Node Name
|
||||
#### ESPhome Node Name
|
||||
|
||||
Refers to the ESPhome device name. **Allowed characters are "__",a-z, 0-9, but no special characters or spaces**. This is a restriction on the side of HA, since the respective entity_IDs are generated from the device name of the blueprint.
|
||||
|
||||
### 2. Language of NSPanel
|
||||
#### Language of NSPanel
|
||||
|
||||
The language can be selected via the drop-down menu. Currently 26 languages are supported.
|
||||
|
||||
### 3. Nextion TFT File Folder
|
||||
#### Nextion TFT File Folder
|
||||
|
||||
Can be left blank. However, it is required if a custom TFT configuration is to be used.
|
||||
|
||||
### 4. Delay
|
||||
#### Delay
|
||||
|
||||
If the WiFi signal is poor, menus may not be loaded completely. If this happens, a delay in 5ms increments can be set here to compensate for this.
|
||||
|
||||
### 5. Synchronization of all values
|
||||
#### Synchronization of all values (Optional)
|
||||
|
||||
Light and cover pages (values) are updated continuously (may cause flickering).
|
||||
|
||||
### 6. Synchronization of all all sliders
|
||||
#### Synchronization of all all sliders (Optional)
|
||||
|
||||
Light and cover pages (cover position) are updated continuously (may cause flickering).
|
||||
|
||||
### 7. Weather integration
|
||||
#### Weather integration
|
||||
|
||||
Choose between HA own weather integration or the more accurate Accuweather.
|
||||
|
||||
### 8. Name Weather
|
||||
#### Weather entity from HA
|
||||
|
||||
Dropdown menu to select the Weather entity to use. Example: If "Accuweather" is selected in item 7, then the entity for Accuweather must be selected here.
|
||||
|
||||
### 9. Outdoor temperature
|
||||
#### Outdoor temperature Sensor (Optional)
|
||||
|
||||
Optionally, the value of an outdoor temperature sensor can be used here. If no separate sensor is used, the value of the weather integration will be used._
|
||||
Optionally, the value of an outdoor temperature sensor can be used here. If no separate sensor is used, the value of the weather integration will be used.
|
||||
|
||||
### 10. Humidity Sensor
|
||||
#### Indoor Temperature Sensor (Optional)
|
||||
|
||||
An indoor temperature sensor is not necessary. Leave the field empty if you want to use the temperature sensor of the NSPanel. If the value of the sensor needs to be corrected, this can be done via the temperature correction for the NSPanel under HA Devices.
|
||||
|
||||
#### Humidity Sensor (Optional)
|
||||
|
||||
Optional indoor humidity sensor.
|
||||
|
||||
### 11. Hot Water Temperature Sensor
|
||||
#### Hot Water Temperature Sensor (Optional)
|
||||
|
||||
Optional Hot Water Sensor.
|
||||
Optional Hot Water Sensor.
|
||||
|
||||
### 12. Hot Water Switch
|
||||
#### Hot Water Charge (Optional)
|
||||
|
||||
Optional hot water switch, e.g. for a boiler.
|
||||
|
||||
### 13. Top 04 Flame
|
||||
#### Top 04 Flame
|
||||
|
||||
Displays a flame symbol on the home screen, e.g. when a boiler is switched on.
|
||||
|
||||
### 14. Climate to Control
|
||||
#### Climate to Control (Optional)
|
||||
|
||||
If a Climate Integration is to be controlled, it must be entered here. This can then be accessed via the temperature on the home screen of the NSPanel.
|
||||
|
||||
### 15. Climate control optimistic mode
|
||||
#### Climate Control optimistic Mode (Optional)
|
||||
|
||||
Depending on the climate control, the optimistic mode can be used for better response. The changes made are only transferred to the device when the screen is exited.
|
||||
|
||||
### 16. Left button switch
|
||||
#### Activate QR Code (Optional)
|
||||
|
||||
Activates the QR Code Page and the QR Code Button on the home page
|
||||
|
||||
#### Name "QR Code Page" (Optional)
|
||||
|
||||
Naming of the QR Code Page, displayed on the top left of the page.
|
||||
|
||||
#### QR Code content (Optional)
|
||||
|
||||
String, which is shown as a QR Code on the NSPanel. This can be a simple text, a URL or could also be used for a simplified login to the WiFi. Here is an example (simply change SSID and password to your credentials and either use "WPA" or "WEP"):
|
||||
|
||||
```WIFI:S:SSID;T:WPA/WEP;P:PASSWORD;;```
|
||||
|
||||
#### Left Button (Optional)
|
||||
|
||||
Left hardware button of the NSPanel.
|
||||
|
||||
### 17. Name left button switch
|
||||
#### Name Left Button (Optional)
|
||||
|
||||
Text on the screen above the left hardware button (home screen).
|
||||
|
||||
### 18. Right Button Switch
|
||||
#### Activate Relay 1 local Fallback (Optional)
|
||||
|
||||
Normally, the internal relays of the NSPanels are triggered via HA. If the NSPanel loses WiFi connection or HA is down, the left hardware button can then switch relay 1 directly.
|
||||
|
||||
#### Right Button (Optional)
|
||||
|
||||
Right Hardware Button of the NSPanel.
|
||||
|
||||
### 19. Name Right Button Switch
|
||||
#### Name "Right Button" (Optional)
|
||||
|
||||
Text on the screen above the right hardware button (home screen).
|
||||
|
||||
### 20. Name Button Page 1- 4
|
||||
#### Activate Relay 2 local Fallback (Optional)
|
||||
|
||||
Normally, the internal relays of the NSPanels are triggered via HA. If the NSPanel loses WiFi connection or HA is down, the right hardware button can then switch relay 2 directly.
|
||||
|
||||
#### Name Button Page 1- 4
|
||||
|
||||
Text on the respective button screens.
|
||||
|
||||
|
||||
|
||||
### Buttons 01 - 32
|
||||
#### Buttons 01 - 32 (Optional)
|
||||
|
||||
The buttons can be accessed by swiping on the Home Screen and their functions are completely identical.
|
||||
Either the individual button pages can be accessed one after the other by swiping to the left, or the button pages can be accessed directly by swiping up, down or to the right.
|
||||
|
||||
The buttons are numbered as follows:
|
||||
|
||||
| | Button Page 1 | Button Page 2 | Button Page 3 | Button Page 4 |
|
||||
| ------ | ------------- | ------------- | ------------- | ------------- |
|
||||
| Line 1 | 01 02 03 04 | 09 10 11 12 | 17 18 19 20 | 25 26 27 28 |
|
||||
| line 2 | 05 06 07 08 | 13 14 15 16 | 21 22 23 24 | 29 30 31 32 |
|
||||
| | Button Page 1 | Button Page 2 | Button Page 3 | Button Page 4 |
|
||||
| ----- | ------------- | ------------- | ------------- | ------------- |
|
||||
| Row 1 | 01 02 03 04 | 09 10 11 12 | 17 18 19 20 | 25 26 27 28 |
|
||||
| Row 2 | 05 06 07 08 | 13 14 15 16 | 21 22 23 24 | 29 30 31 32 |
|
||||
|
||||
The following entities can be stored:
|
||||
|
||||
@@ -120,92 +144,42 @@ When the respective button is pressed, the corresponding page is automatically o
|
||||
For each button an own name can be specified optionally.
|
||||
All buttons offer the possibility to optionally confirm the execution of the action. This can be activated or deactivated separately for each button via *"Confirm execution of the button press"*.
|
||||
|
||||
#### Activate Entity Pages (Optional)
|
||||
|
||||
***
|
||||
This option activates the entity pages on the Home Screen. The entity pages can be used for example to display values or statuses of entities on the individual pages.
|
||||
|
||||
-Blueprint---Setup-and-Description-of-the-Blueprint.assets/configuration_1.png)
|
||||
#### Entity 01 - 32 (Optional)
|
||||
|
||||
-Blueprint---Setup-and-Description-of-the-Blueprint.assets/configuration_2.png)
|
||||
The entity pages can be accessed by pressing the symbol on the Home Screen and their functions are completely identical.
|
||||
|
||||
-Blueprint---Setup-and-Description-of-the-Blueprint.assets/configuration_3.png)
|
||||
The entities are numbered as follows:
|
||||
|
||||
-Blueprint---Setup-and-Description-of-the-Blueprint.assets/configuration_4.png)
|
||||
|
||||
|
||||
|
||||
This section is covering the settings in the Blueprint Automation.
|
||||
The Blueprint Automation is the central configuration piece of this solution for the NSPanel.
|
||||
|
||||
In principal, setting up the automation is self explaining. Below you will find an explanation of each configuration point of the Blueprint.
|
||||
|
||||
|
||||
# Parameter
|
||||
1. **ESPhome Node Name:** Refers to the ESPhome device name. Allowed characters are a-z, 0-9, but no special characters or spaces. This is a restriction by HA, since the respective Entity_IDs are generated from the device name of the blueprint.
|
||||
|
||||
2. **Language for NSPanel:** The language can be selected via dropdown menu. Currently 26 languages are supported.
|
||||
3. **Nextion TFT File Folder:** Can be left blank. But it is needed if you want to use your own TFT configuration.
|
||||
4. **Delay**: Weak WiFi signal can lead to screens not being loaded completely. If this happens, a delay in 5ms steps can be set here to compensate for this.
|
||||
5. **Synchronization of all all values:** Light and cover pages (values) are updated continuously (can lead to flickering).
|
||||
6. **Synchronization of all sliders:** light and cover pages (cover position) are updated continuously (can cause flickering).
|
||||
7. **Weather Integration:** Choose between HA Weather Integration or the more accurate Accuweather.
|
||||
8. **Name Weather:** Dropdown menu to select the weather entity to use. Example: If "Accuweather" is selected in option 7, the entity for Accuweather must be selected here.
|
||||
9. **Outdoor Temperature:** Optionally the value of an outdoor temperature sensor can be used here. If no separate sensor is used, the value of the weather integration is used.
|
||||
10. **Humidity Sensor:** Optional indoor humidity sensor.
|
||||
11. **Hot Water Temperature Sensor:** Optional hot water sensor.
|
||||
12. **Hot Water Switch:** Optional hot water switch, e.g. for a boiler.
|
||||
13. **Top 04 Flame:** Displays a flame symbol on the home screen, e.g. when a therme is switched on (On).
|
||||
14. **Climate to Control:** If a Climate Integration is to be controlled, it must be entered here. This can then be accessed via the temperature on the home screen of the NSPanel.
|
||||
15. **Climate Control optimistic Mode:** Depending on the climate control, the optimistic mode can be used for a better response. The value is being transmitted after leaving the screen.
|
||||
16. **Left Button Switch:** Left Hardware Button of the NSPanel.
|
||||
17. **Name Left Button Switch:** Text on the screen above the left hardware button (Home Screen).
|
||||
18. **Right Button Switch:** Right Hardware Button of the NSPanel.
|
||||
19. **Name Right Button Switch:** Text on the screen above the right hardware button (Home Screen).
|
||||
20. **Name Button Page 1- 4:** Text on the respective Button Screens.
|
||||
|
||||
|
||||
|
||||
**Buttons 01-32**
|
||||
The buttons can be reached by swiping on the home screen and are identical in their function.
|
||||
|
||||
You can either swipe through all 4 button pages by going to the left, or directly access the pages by swiping up, down, or right.
|
||||
|
||||
|
||||
|
||||
The buttons are numbered as follows:
|
||||
|
||||
| | Button Page 1 | Button Page 2 | Button Page 3 | Button Page 4 |
|
||||
| | Entity Page 1 | Entity Page 2 | Entity Page 3 | Entity Page 4 |
|
||||
| ----- | ------------- | ------------- | ------------- | ------------- |
|
||||
| Row 1 | 01 02 03 04 | 09 10 11 12 | 17 18 19 20 | 25 26 27 28 |
|
||||
| Row 2 | 05 06 07 08 | 13 14 15 16 | 21 22 23 24 | 29 30 31 32 |
|
||||
|
||||
The following entities can be stored:
|
||||
Additionally there is the possibility to choose an icon of your choice from 6896 icons.
|
||||
|
||||
- Light
|
||||
- Switch
|
||||
- Cover
|
||||
- Input Boolean
|
||||
- Automation
|
||||
- Button
|
||||
- Input Button
|
||||
- Scene
|
||||
- Person
|
||||
- Script
|
||||
- Binary Sensor
|
||||
- Fan
|
||||
Of course there is also the possibility to enter your own entity label and to assign a label for the 4 pages. If no entity label is set, the friendly name is taken from HA.
|
||||
|
||||
If the respective button is pressed, the corresponding page is automatically opened, e.g. the cover control for covers, etc.
|
||||
A name can be set optionally for each button.
|
||||
The currently implemented symbols can be found here: https://htmlpreview.github.io/?https://github.com/jobr99/Generate-HASP-Fonts/blob/master/cheatsheet.html
|
||||
|
||||
All buttons offer the possibility to optionally confirm the execution of the action. This can be activated or deactivated separately for each button via "Confirm execution of the button press".
|
||||
**To use the icons in the Blueprint you would have to click on the "U" on the website to copy the icon and then paste it in the Blueprint** *(Attention: Only a "strange" character is displayed, but that is correct).*
|
||||
|
||||
|
||||
|
||||
|
||||
***
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082420725.png)
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082450296.png)
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082520575.png)
|
||||
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082614749.png)
|
||||
|
||||
...
|
||||
|
||||
-Blueprint---Einrichtung-und-Erklärung-vom-Blueprint.assets/image-20230210082638657.png)
|
||||
@@ -39,12 +39,12 @@ This section covers the initial configuration. All important steps for installat
|
||||
> It is also possible to copy the code from the file _**"nspnael_blueprint.yaml "**_ and paste it into HA.
|
||||
> You can find instructions for this under [Using Automation Blueprints](https://www.home-assistant.io/docs/automation/using_blueprints/) and [Automation blueprint tutorial](https://www.home-assistant.io/docs/blueprint/tutorial/#create-the-blueprint-file)
|
||||
|
||||
#### 2. You have to download the file **_nspanel.tft_** from Github
|
||||
#### 2. You have to download the file **_nspanel_us.tft_** or **_"nspanel_eu.tft"_** from Github
|
||||
|
||||
|
||||
|
||||
|
||||
#### 3. Upload the **_nspnael.tft_** file to your **_Home Assistant Server_** in the **_www_** folder, see [Home Assistant HTTP](https://www.home-assistant.io/integrations/http/#hosting-files) 'Hosting Files' section for details.
|
||||
#### 3. Upload the file to your **_Home Assistant Server_** in the **_www_** folder, see [Home Assistant HTTP](https://www.home-assistant.io/integrations/http/#hosting-files) 'Hosting Files' section for details.
|
||||
|
||||
|
||||
|
||||
@@ -60,7 +60,7 @@ This section covers the initial configuration. All important steps for installat
|
||||
|
||||
> ⚠️ _**ATTENTION!**_ for _**"device_name"**_ max. 15 characters _**[a-z], [0-9] and [\_]**_ may be used and all must be _**"lowercase"**_. Furthermore, characters like _**[-], [SPECIAL CHARACTARS] and [SPACES]**_ are forbidden and will cause problems with the blueprint.
|
||||
|
||||
**Example:** _**nspanel_kitchen**_
|
||||
**Example:** _**nspanel_blackymas**_
|
||||
|
||||
|
||||
### CODE:
|
||||
@@ -73,8 +73,8 @@ substitutions:
|
||||
wifi_ssid: "YOUR WIFI SSID"
|
||||
wifi_password: "YOUR WIFI PASSWORD"
|
||||
|
||||
nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel.tft" # URL to local tft File
|
||||
# nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft" # URL to Github
|
||||
nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel_us.tft" # URL to local tft File
|
||||
# nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_us.tft" # URL to Github
|
||||
|
||||
##### CHANGE ME END #####
|
||||
|
||||
@@ -95,15 +95,17 @@ packages:
|
||||
|
||||
> At **_http://HOME-ASSISTANT-IP:8123/local/nspanel.tft_** you have to enter your _**IP from Home Assistant**_.
|
||||
|
||||
> This could look like this **_http://192.168.1.1:8123/local/nspanel.tft_**
|
||||
> This could look like this **_http://192.168.1.1:8123/local/nspanel_us.tft_**
|
||||
|
||||
> ⚠️ _**ATTENTION!**_ You can also comment out the path nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft" and load the TFT directly from Github. But it can happen that there are problems with the upload to the NSPanel. This depends on your internet and wifi. For more information on this issue, see the issue page on Github. It should then look like this
|
||||
> ⚠️ _**ATTENTION!**_ You can also comment out the path nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_us.tft" and load the TFT directly from Github. But it can happen that there are problems with the upload to the NSPanel. This depends on your internet and wifi. For more information on this issue, see the issue page on Github. It should then look like this
|
||||
|
||||
```
|
||||
# nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel.tft" # URL to local tft File
|
||||
nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft"
|
||||
# nextion_update_url: "http://HOME-ASSISTANT-IP:8123/local/nspanel_us.tft" # URL to local tft File
|
||||
nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel_us.tft"
|
||||
```
|
||||
|
||||
> _⚠️ **Attention**_if you want to use the European Layout of the NSPanel, you must use "nspanel_eu.tft" instead of "nspanel_us.tft"!
|
||||
|
||||
|
||||
|
||||
#### 6. Now the NSPanel can be flashed with the new ESPHome code.
|
||||
@@ -119,7 +121,7 @@ packages:
|
||||
|
||||
> _**NOTE!**_ In the blueprint, in the _**"ESPHOME Node Name"**_ field, enter exactly the same name that you assigned in the _**"ESPHome File"**_.
|
||||
|
||||
> **Example:** _**nspanel_kitchen**_
|
||||
> **Example:** _**nspanel_blackymas**_
|
||||
|
||||
|
||||
|
||||
@@ -142,8 +144,8 @@ See [(EN) Common Issues | TFT Upload When nspanel lovelace ui has been installed
|
||||
|
||||
* Blueprint file _**"nspnael_blueprint.yaml "**_ can also be installed manually.
|
||||
* ESPHome file_**"nspanel_esphome.yaml "**_ can also be installed manually. This allows to activate or add more _**"Advanced "**_ configurations.
|
||||
* There is also the possibility to upload the TFT file _**"nspanel.tft "**_ manually. The whole thing can also be combined with a _**"Folder Watcher "**_.
|
||||
* additionally we provide the HMI file _**"nspanel.HMI "**_ for the Nextion Editor to customize graphics and programming if needed
|
||||
* There is also the possibility to upload the TFT file _**"nspanel_us.tft "**_ manually. The whole thing can also be combined with a _**"Folder Watcher "**_.
|
||||
* additionally we provide the HMI file _**"nspanel_us.HMI "**_ for the Nextion Editor to customize graphics and programming if needed
|
||||
|
||||
> _**ATTENTION!**_ If you use this mode, you should know what you are doing. We do not give support here!
|
||||
|
||||
|
||||
Reference in New Issue
Block a user