Merge branch 'main' of https://github.com/joBr99/nspanel-lovelace-ui

README.md

@@ -10,9 +10,9 @@ NsPanel Lovelace UI is a Firmware for the nextion screen inside of NSPanel in th
 
 **EU Model and US Model supported (in portrait and landscape orientation)**
 
-Content of the screen is controlled by a AppDaemon Python Script installed on your HomeAssistant Instance.
+The content of the screen is controlled by an AppDaemon Python Script installed on your HomeAssistant Instance.
 
-Or an TypeScript on your ioBroker Instance in case you are an ioBroker User.
+Or a TypeScript on your ioBroker Instance in case you are an ioBroker User.
 
 NsPanel needs to be flashed with Tasmota (or upcoming with ESPHome)
 
@@ -22,7 +22,7 @@ NsPanel needs to be flashed with Tasmota (or upcoming with ESPHome)
 
 - Entities Page with support for cover, switch, input_boolean, binary_sensor, sensor, button, number, scenes, script, input_button and light, input_text (read-only), lock, fan and automation
 - Grid Page with support for cover, switch, input_boolean, button, scenes, light, lock and automation
-- Detail Pages for Lights (Brightness, Temperature and Color of the Light) and for Covers (Position)
+- Detail Pages for Lights (Brightness, Temperature and Color of the Light) and Covers (Position)
 - Thermostat Page 
 - Media Player Card
 - Alarm Control Card
@@ -32,7 +32,7 @@ NsPanel needs to be flashed with Tasmota (or upcoming with ESPHome)
 - **Everything is dynamically configurable by a yaml config, no need to code or touch Nextion Editor**
 
 It works with [Tasmota](https://tasmota.github.io/docs/) and MQTT. 
-To control the panel and update it with content from HomeAssistant there is an [AppDaemon](https://github.com/AppDaemon/appdaemon) App.
+To control the panel and update it with content from HomeAssistant, there is an [AppDaemon](https://github.com/AppDaemon/appdaemon) App.
 
 See the following picture to get an idea of the look of this firmware for NSPanel.
 

docs/entities.md

@@ -36,6 +36,14 @@ It is also possible to configure different icon overwrites per state:
                 "off": mdi:lightbulb
 ```
 
+It is also possible to use text instead of icons with `text:X`
+
+```yaml
+            icon:
+                "on": mdi:lightbulb
+                "off": "text:"
+```
+
 ## Hide item based on state
 
 This sensor will only be shown on the card if it's state is equal to `off`

docs/faq.md

@@ -6,17 +6,17 @@ You have most likely an error in your MQTT configuration somewhere. To find the
 
 1. Check your appdaemon log. (Settings > Add-ons > AppDaemon > Log)
 You should see something like this:
-`INFO MQTT: MQTT Plugin initialization complete`
+`INFO MQTT: MQTT Plugin initialization complete`  
-If you are seeing Messages like this:
+If you are seeing Messages like this:  
-`CRITICAL MQTT: Could not complete MQTT Plugin initialization, for Connection was refused due to Not Authorised`
+`CRITICAL MQTT: Could not complete MQTT Plugin initialization, for Connection was refused due to Not Authorised`  
-Your appdaemon mqtt config is wrong, check your appdaemon.yaml. 
+Your appdaemon mqtt config is wrong, check your appdaemon.yaml.  
-The log of your mqtt broker might give you additional information.
+The log of your mqtt broker might give you additional information.  
 
-2. Check MQTT Configuration of Tasmota. 
+2. Check MQTT Configuration of Tasmota.
 Your Tasmota device needs to connect sucessfully to your MQTT Broker, if you are in the waiting for content screen, the panel will send periodic messages to it's mqtt topic.
 
 3. Make sure that you are using the same topic in apps.yaml and in your tasmota configuration. 
-The examples in the docs ([MQTT Config](https://docs.nspanel.pky.eu/configure_mqtt/)) are an valid (tasmota<>apps.yaml).
+The examples in the docs ([MQTT Config](https://docs.nspanel.pky.eu/configure_mqtt/)) are an valid example (tasmota<>apps.yaml).  
 Please don't modify the Full Topic in your Tasmota Config, unless you know the implications, changing the Full Topic will result in diffent Send and Receive Channels, that have to be correct in your apps.yaml.
 
 4. If you are still in the waiting for content screen please share the following items, with the Waiting for Content Issue type on the [Github Issues Page](https://github.com/joBr99/nspanel-lovelace-ui/issues/new/choose)

docs/prepare_nspanel.md

@@ -42,6 +42,11 @@ 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`
 
+
+
+Note: For the US Version Users - keepin mind that you need to add the model config option to your apps.yaml later, more details on config overview page
+
+
 <details>
 <summary>Alternatively you can use your own webserver or the one build into HomeAssistant:</summary>
 <br>