From bd8b8b580bf6041a5f1f4bbceec2947c2a1f073e Mon Sep 17 00:00:00 2001
From: joBr99 <29555657+joBr99@users.noreply.github.com>
Date: Sun, 12 Jun 2022 14:12:52 +0200
Subject: [PATCH] upd docs
---
README.md | 764 +--------------------------------------
doc-pics/card-alarm.png | Bin 0 -> 8142 bytes
doc-pics/card-media.png | Bin 0 -> 23280 bytes
docs/card-alarm.md | 20 +
docs/card-climate.md | 24 ++
docs/card-entities.md | 5 +-
docs/card-grid.md | 6 +-
docs/card-media.md | 19 +
docs/card-qr.md | 46 +++
docs/faq.md | 25 ++
docs/img/card-thermo.png | Bin 0 -> 15523 bytes
docs/notifications.md | 85 +++++
docs/phys-btn.md | 29 ++
docs/subpages.md | 18 +
mkdocs.yml | 2 +
15 files changed, 276 insertions(+), 767 deletions(-)
create mode 100644 doc-pics/card-alarm.png
create mode 100644 doc-pics/card-media.png
create mode 100644 docs/img/card-thermo.png
create mode 100644 docs/notifications.md
create mode 100644 docs/subpages.md
diff --git a/README.md b/README.md
index c3275e1f..f91b14eb 100644
--- a/README.md
+++ b/README.md
@@ -42,766 +42,6 @@ Some (not all) screenshots from the US Portrait Version:

-## TLDR
-1. Install Tasmota to NSPanel
-2. Install Berry Driver in Tasmota and setup MQTT
-3. Flash Nextion Firmware
-4. Install AppDaemon, setup MQTT and install Backend Application
+## Documentation
-For more detailed Instructions see the following Sections:
-
-- [Requirements](#requirements)
-
-- [Installation - Home Automation Part (Home Assistant)](#installation---home-automation-part-home-assistant)
-
-- [Installation - Home Automation Part (IoBroker)](#installation---home-automation-part-iobroker)
-
-- [Installation - NSPanel Part (Firmware)](#installation---nspanel-part)
-
-- [Configuration](#configuration)
- - [Configuring the MQTT integration in AppDaemon](#configuring-the-mqtt-integration-in-appdaemon)
- - [Configure your NSPanel in AppDaemon](#configure-your-nspanel-in-appdaemon)
-- [How to update](#how-to-update)
-- [FAQ](#faq---frequently-asked-questions)
-
-
-## Requirements
-
- - NSPanel
- - USB to Serial TTL Adapter
- - Running Instance of the Home Automation Platform of your Choise
- - Running [Home Assistant Instance](https://www.home-assistant.io/installation/)
- - with installed [MQTT Broker](https://www.home-assistant.io/docs/mqtt/broker)
- - Running [ioBroker Instance](https://www.iobroker.net/#en/documentation)
- - with installed MQTT Broker
-
-## Installation - Home Automation Part (Home Assistant)
-
-This section describes the Installation Steps for HomeAssistant, follow each step.
-
-
-
-### Installing AppDaemon
-
-
-The backend application for HomeAssistant is written in a python for [AppDaemon](https://github.com/AppDaemon/appdaemon).
-This means it requires a working and running installation of AppDaemon.
-
-The easiest way to install it is through Home Assistant's Supervisor Add-on Store, it will be automaticly connected to your Home Assistant Instance.
-
-
-
-#### Add babel package to AppDaemon Container (Optional)
-
-For localisation (date in your local language) you need to add the python package babel to your AppDaemon Installation.
-
-
-
-
-### Installing Studio Code Server (optional, recommended)
-
-You will need a way to edit the `apps.yaml` config file in the Appdaemon folder.
-Install Studio Code Server from Home Assistant's Supervisor Add-on Store to easily edit configuration Files on your HomeAssistant Instance.
-
-
-
-### Installing HACS
-
-HACS is the Home Assistant Community Store and allows for community integrations and
-automations to be updated cleanly and easily from the Home Assistant web user interface.
-It's simple to install the AppDaemon app without HACS, but keeping up to date requires
-manual steps that HACS will handle for you: you will be notified of updates, and they
-can be installed by a click on a button.
-
-If you want to use HACS, you will have to follow [their documentation on how to install HACS](https://hacs.xyz/docs/setup/download).
-
-
-
-### Installing AppDaemon Backend Application
-
-To install Lovelace UI Backend App with HACS, you will need to make sure that you enabled
-AppDaemon automations in HACS, as these are not enabled by default:
-
-1. Click on `Configuration` on the left menu bar in Home Assistant Web UI
-2. Select `Devices & Services`
-3. Select `Integrations`
-4. Find `HACS` and click on `Configure`
-5. In the window that opens, make sure that `Enable AppDaemon apps discovery & tracking`
- is checked, or check it and click `Submit`
-6. If you just enabled this (or just installed HACS), you might have to wait a few minutes
- as all repositories are being fetched; you might hit a GitHub rate limit, which might
- then require you to wait a few hours for HACS to be fully configured. In this case,
- you won't be able to proceed to the next steps until HACS is ready.
-
-Now, to install NSPanel Lovelace UI Backend with HACS, follow these steps:
-
-1. Click on `HACS` on the left menu bar in Home Assistant Web UI
-2. Click on `Automations` in the right panel
-3. Click on `Explore & download repositories` in the bottom right corner
-4. Search for `NSPanel`, and click on `NSPanel Lovelace UI Backend` in the list that appears
-5. In the bottom right corner of the panel that appears, click on
- `Download this repository with HACS`
-6. A confirmation panel will appear, click on `Download`, and wait for HACS to
- proceed with the download
-7. The Backend Application is now installed, and HACS will inform you when updates are available
-
-
-
-### Flash Tasmota to your NSPanel
-
-You need to connect to your nspanel via serial and flash tasmtoa [tasmota32-nspanel.factory.bin](https://tasmota.github.io/install/firmware/development/tasmota32-nspanel.factory.bin) to your NSPanel. You can use the Tasmota Web Installer to do so. [Tasmota Web Installer](https://tasmota.github.io/install/)
-Make sure to come back to this guide, before uploading the nspanel.be/autoexec.be files.
-For more deatils see the [NSPanel Page of the Tasmota Template Repository](https://templates.blakadder.com/sonoff_NSPanel.html).
-
-### Configure Tasmota Template for NSPanel
-
-Configure the NSPanel template for Tasmota. (Go to Configuration and Configure Other and paste the template there, make sure to tick the activate checkbox)
-
-
-
-You can use the following template or copy the one on the [Tasmota Template Repo Site](https://templates.blakadder.com/sonoff_NSPanel.html).
-
-`{"NAME":"NSPanel","GPIO":[0,0,0,0,3872,0,0,0,0,0,32,0,0,0,0,225,0,480,224,1,0,0,0,33,0,0,0,0,0,0,0,0,0,0,4736,0],"FLAG":0,"BASE":1,"CMND":"ADCParam 2,11200,10000,3950 | Sleep 0 | BuzzerPWM 1"}`
-
-After a reboot of tasmota your screen will light up with the stock display firmware.
-
-### Setup your MQTT Server in Tasmota
-
-Configure your MQTT Server in Tasmota.
-See Tasmota [MQTT Documentation](https://tasmota.github.io/docs/MQTT/) for more details.
-
-
-
-### Upload Berry Driver to Tasmota
-
-1. Download the autoexec.be from the repository: [Berry Driver](tasmota/autoexec.be)
-
-2. Go to `Consoles` > `Manage File System` in Tasmota and upload the previously downloaded file.
-
-3. Restart your NSPanel
-
-### Flash Firmware to Nextion Screen
-
-Note for ioBroker Users: Check the Release Notes, if the ioBroker Backend is not up to date with the current release there will be a note and you have to flash the latest compatible version from there.
-
-#### Use your own Webserver
-
-Upload the nspanel.tft from the lastest release to a Webserver (for example www folder of Home Assistant) and execute the following command in Tasmota Console. (Development Version: [tft file from HMI folder](HMI/nspanel.tft))
-
-**Webserver must be HTTP, HTTPS is not supported, due to limitations of berry lang on tasmota**
-
-`FlashNextion http://ip-address-of-your-homeassistant:8123/local/nspanel.tft`
-
-#### Use my webserver
-
-Due the limitations of Berry, it's not possible to download the tft file directly from github, so I'm also renting a small server where you can download the file via HTTP.
-
-Use the one following commands to flash the latest release from this repository, just execute the following Command in Tasmota:
-
-EU Version: `FlashNextion http://nspanel.pky.eu/lui-release.tft`
-
-US Version Portrait: `FlashNextion http://nspanel.pky.eu/lui-us-p-release.tft`
-
-US Version Landscape: `FlashNextion http://nspanel.pky.eu/lui-us-l-release.tft`
-
-
-
-Support for ESPHome is WIP, see this third-party [ESPHome component](https://github.com/sairon/esphome-nspanel-lovelace-ui) which allows using ESPHome instead of Tasmota.
-
-1. Installing HomeAssistant Add-Ons
-2. Installing HomeAssistant Community Store
-3. Installing Lovelace AppDaemon Backend Application
-Installation Instructions for Tasmota (Recommended)
-Installation Instructions for ESPHome
-
`"%I:%M ?%p"`-`dateAdditonalTemplate` | True | string | `""` | Addional Text dispayed after Date, can contain a Homeassistant Template Example `" - {{ states('sun.sun') }}"` -`timeAdditonalTemplate` | True | string | `""` | Addional Text dispayed below Time, can contain a Homeassistant Template -`dateFormat` | True | string | `%A, %d. %B %Y` | date format used if babel is not installed -`cards` | False | complex | | configuration for cards that are displayed on panel -`screensaver` | True | complex | | configuration for screensaver -`hiddenCards` | True | complex | | configuration for cards that can be accessed though navigate items - - - -
- - - `af_xx` - Afrikaans - - `ar_xx` - Arabic - - `bg_xx` - Bulgarian - - `ca_xx` - Catalan - - `cs_xx` - Czech - - `da_xx` - Danish - - `de_xx` - German - - `el_xx` - Greek - - `en_xx` - English - - `es_xx` - Spanish - - `et_xx` - Estonian - - `fa_xx` - Persian - - `fi_xx` - Finnish - - `fr_xx` - French - - `he_xx` - Hebrew - - `hr_xx` - Croatian - - `hu_xx` - Hungarian - - `hy_xx` - Armenian - - `id_xx` - Indonesian - - `is_xx` - Icelandic - - `it_xx` - Italian - - `lb_xx` - Luxembourgish - - `lt_xx` - Lithuanian - - `lv_xx` - Latvian - - `nb_xx` - Norwegian - - `nl_xx` - Dutch - - `nn_xx` - Norwegian - - `pl_xx` - Polish - - `pt_xx` - Portuguese - - `ro_xx` - Romanian - - `ru_xx` - Russian - - `sk_xx` - Slovak - - `sl_xx` - Slovenian - - `sv_xx` - Swedish - - `th_xx` - Thai - - `tr_xx` - Turkish - - `uk_xx` - Ukrainian - - `vi_xx` - Vietnamese - -
-Rl;v`p
z1iSU}HyC7s_>*+Y&xoHB{{CgWytO;)5JX5oJm43w&UCG wHO*IB6zZ-_vMx-r|rdWG75^+1xNgDWFhRJ
z }RM-aWU%IW2K!?
zCh$J$Yx?an)jI2M_J(S0|L>Ttk9hPDOf=;lJ>AZnY|w*uFBWeVw`W;PJ1!(`bB*s3
zglC1-Hh!nyZh7aI`OP>aQ)ykz(Ayjc09;Rz6AlkvmkAzp1|6=SK8mDq^#Y&OtARZ|
z-)~i|WnxOy!V~I-Bx4gY&**6xV|gqCe*LA57i-OG$z>l!B2jpaAPKe!nNic$;Gh*k
zWBR!SP c{-
z6_1`pt);Tg=-ynlealEG- 4x6y`QUmDLe0oJDoP$d@=xD6gDNRXI@xqBG+MVYSSJM2F@Vs_hrzvhyBS
zBOG1ipA@OuKNC7lsMn8Ylual?gZ7~-mJW}^Xc}s~#nxtlADVp1j<)CddJsmM696^W
zeaU)wSJ%(OC~pD0Qc?RNWT8oBAd7I`>l8@&bIM6I+2pqlwq>#PR<2KlGdSdB}k{3%zkLl-SD=5e|a_<-l0On!J&Hde%mW}6!H_!
z*Y641b1@1gE(GigVSsktTx5B5bwx(UD+3e(qkscKX<-(*tP1@HKosep4Fx+Rpvwj!
z;S3w`ODaqst18H%ny#*{I>Oz4q>59)l2TnrKpy>!h)8!YkM1WeEgha;RFvicWZQ;|
zi;GElKWFgMz_73|Hwk@U8%Y`<^3w9Y9jqGVeFT7T0V%?}=VKNcKECDIn9cUZCy?MP
zGy+#ptWHO$eW<`pz8(7EOl#Eq_&==D(yt-CTA?3hf`i=B&fd<^DL^`em}jwDEf1o1
zcnf_bf `;m~D^n~sSsk!**}O@8M1R$qRj*%0IL
zZD8}ZV`~WSeperate Page
+
+
+ This is the notification used by the backend for updates, opening it requires to the following commands to the CustomSend Topic:
+
+ `pageType popupNotify`
+
+ `entityUpdateDetail~internalName~heading~headingColor~button1text~button1color~button2text~tB2Color~notificationText~textColor~sleepTimeout`
+
+ It is possible to exit from the page by sending `exitPopup`
+
+Send Message to the Panel combined with a buzzer sound:
+
+ ```yaml
+nspanel_popup_notification:
+ alias: Popup Notification
+ sequence:
+ - service: mqtt.publish
+ data:
+ topic: cmnd/tasmota_NsPanelTerrasse/Backlog
+ payload: CustomSend pageType~popupNotify; CustomSend entityUpdateDetail~id~{{
+ title }}~65535~~~~~{{ message }}~65535~{{ timeout }}; Buzzer 2,2,2
+ mode: single
+ icon: mdi:message-badge
+ ```
+
+Send Message to the Panel:
+
+ ```yaml
+nspanel_popup_notification:
+ alias: Popup Notification
+ sequence:
+ - service: mqtt.publish
+ data:
+ topic: cmnd/tasmota_NsPanelTerrasse/Backlog
+ payload: CustomSend pageType~popupNotify; CustomSend entityUpdateDetail~id~{{
+ title }}~65535~~~~~{{ message }}~65535~{{ timeout }}
+ mode: single
+ icon: mdi:message-badge
+ ```
+Notification on screensaver
+
+
+ The screensaver can display Notifications by sending this command to the CustomSend topic: `notify~heading~text`
+
+
+Send Message to the Screensaver combined with a buzzer sound:
+
+ ```yaml
+nspanel_screensaver_notification:
+ alias: Screensaver Notification
+ sequence:
+ - service: mqtt.publish
+ data:
+ topic: cmnd/tasmota_NsPanelTerrasse/Backlog
+ payload: CustomSend notify~{{ heading }}~{{ message }}; Buzzer 2,2,2
+ mode: single
+ icon: mdi:message-badge
+ ```
+
+Send Message to the Screensaver:
+
+ ```yaml
+nspanel_screensaver_notification:
+ alias: Screensaver Notification
+ sequence:
+ - service: mqtt.publish
+ data:
+ topic: cmnd/tasmota_NsPanelTerrasse/Backlog
+ payload: CustomSend notify~{{ heading }}~{{ message }}
+ mode: single
+ icon: mdi:message-badge
+ ```
+
+