And you have this page on your installation and you’ve restarted AppDeamon?
To confirm that the folder in your editor is actually the one used by Appdaemon, please delete the app from hacs, which also needs to lead in the files deleted in the file editor (except for apps yaml) and restart Appdaemon, the panel needs to stop working then.
yes restart appdaemon
Testing the statusIcon features with Esphome, I have verified the color change based on sensor values (Wifi signal sensor). Also the display of the values themselves, but stucked with icons. I don’t know if I missed something. Is possible changing the statusIcons based on states or would it be a new feature?
Thanks.
statusIcon1:
entity: sensor.wifi_signal_percent_2
altFont: True
# icon: 'ha:{{states("sensor.wifi_signal_percent_2")}}' # valor en lugar de icono
icon: mdi:wifi
color: >
{%if int(states("sensor.wifi_signal_percent_2")) < 40%}
[255,0,0]
{%else%}
[0,255,0]
{%endif%}
in my case the same, everything is fine but it does not work
import hassapi as hass
from luibackend.config import LuiBackendConfig
from luibackend.controller import LuiController
from luibackend.mqtt import LuiMqttListener, LuiMqttSender
from luibackend.updater import Updater
import apis
class NsPanelLovelaceUIManager(hass.Hass):
def initialize(self):
self.log('Starting')
apis.ha_api = self
apis.mqtt_api = self.get_plugin_api("MQTT")
cfg = self._cfg = LuiBackendConfig(self, self.args["config"])
topic_send = cfg.get("panelSendTopic")
topic_recv = cfg.get("panelRecvTopic")
mqttsend = LuiMqttSender(self, topic_send)
# Request Tasmota Driver Version
apis.mqtt_api.mqtt_publish(topic_send.replace("CustomSend", "GetDriverVersion"), "x")
controller = LuiController(cfg, mqttsend.send_mqtt_msg)
desired_tasmota_driver_version = 8
desired_display_firmware_version = 49
version = "v3.9.4"
model = cfg.get("model")
if model == "us-l":
desired_display_firmware_url = f"http://nspanel.pky.eu/lovelace-ui/github/nspanel-us-l-{version}.tft"
elif model == "us-p":
desired_display_firmware_url = f"http://nspanel.pky.eu/lovelace-ui/github/nspanel-us-p-{version}.tft"
else:
desired_display_firmware_url = f"http://nspanel.pky.eu/lovelace-ui/github/nspanel-{version}.tft"
desired_tasmota_driver_url = "https://raw.githubusercontent.com/joBr99/nspanel-lovelace-ui/main/tasmota/autoexec.be"
mode = cfg.get("updateMode")
updater = Updater(self.log, mqttsend.send_mqtt_msg, topic_send, mode, desired_display_firmware_version, model, desired_display_firmware_url, desired_tasmota_driver_version, desired_tasmota_driver_url)
LuiMqttListener(topic_recv, controller, updater)
self.log('Started')
I’ve read this entire thread and before I go jumping in the deep end, could anyone quickly advise if this works for the US panel in Portrait mode, and if so point me to a page/screenshot where this is configured ?… thank you.
There are multiple different solutions in this thread. I use the @jobraun lovelace-ui and it works perfectly in portrait.: Prepare NsPanel - NsPanel Lovelace UI Docs (pky.eu)
I am not sure whether the NSPanel blueprint by @Blackymas is available in portrait, but I would imagine it is.
if you are using ha templates for the icons you will need to use the acuall chars that you can get by clicking U in the cheatsheet
alternativly there is a new type ‘ha-i:’ instead of ‘ha:’ that is translating the icon name after the template is evaluated, but I think this is only part of the dev version
Can you confirm that you are using the HomeAssistant Operating System and not your own docker containers? (docker compose; unraid whatever)
In case you are using docker contains, please send me your config of homeassistant and appdaemon.
yes with the new release 3.1.0
Is there a setting in the guide that calls it out on 3.1.0?
you find all information in the release notes
Yes, I am using docker, config of appdeamon:
home assistant configuration refers to configuration.yaml?
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
logger:
default: info
homeassistant:
time_zone: Europe/Madrid
external_url: "https://argentona.duckdns.org:8123"
internal_url: "http://homeassistant.local:8123"
customize: !include customize.yaml
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
climate: !include termostatos.yaml
sensor: !include sensor.yaml
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
device_tracker:
- platform: xiaomi_miio
host: XXXXXXXXXX
token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
camera:
- platform: xiaomi_cloud_map_extractor
host: xxxxxxxxxxxxx
token: !secret xiaomi_cloud_map_extractor_token
username: !secret xiaomi_cloud_map_extractor_user
password: !secret xiaomi_cloud_map_extractor_psw
draw: ['all']
attributes:
- calibration_points
map_transformation:
scale: 2
binary_sensor:
- platform: meteoalarm
country: "spain"
province: "barcelona"
no the configuration of your docker containers
most likely you missed that the appdaemon volume mount needs to be within the HA one to access file from HACS
see the volume paths in this example:
version: "3.5"
services:
homeassistant:
image: ghcr.io/home-assistant/home-assistant:stable
container_name: homeassistant
network_mode: host
volumes:
- ./docker-data/homeassistant/:/config
- /etc/localtime:/etc/localtime:ro
environment:
- TZ=Europe/Berlin
privileged: true
restart: unless-stopped
appdaemon:
container_name: appdaemon
image: acockburn/appdaemon:latest
environment:
- HA_URL=http://your-homeassistant-url:8123
- TOKEN="xxxxxx"
volumes:
- /etc/localtime:/etc/localtime:ro
- ./docker-data/homeassistant/appdaemon:/conf
depends_on:
- homeassistant
restart: unless-stopped
I can’t find the configuration file, can you help me?
It is installed on a PC with debian
Well, how do you start your docker containers?
It starts automatically when the PC boots.
Follow these instructions to install home assistant supervised;
No clue about supervised installations; it should work just fine, but apparently appdaemon doesn’t recognize the changes made by hacs or the editor, however I cannot help you debug this.
I’m personally running HA OS in a virtual machine and never used a supervised installation on debian.
If you are not familar enough with docker/linux stuff to debug this I would recommend you to use a HA OS or HA Containers instead.
Well, I’ve been trying things and I tell you:
Bearing in mind that the NSPanel Lovelace UI version is always the latest: 3.9.4, and that appdeamon is restarted after every tft installation
If the tft version is 43: everything works correctly
If the tft version is 48: screensaver works, but navigation through the screens does not work
If the tft version is 49: nothing works
I don’t think it is a home assistant configuration error, because if it were like that, nothing would work with the tft 43 version.
Is that correct? Does it give you any clue as to what could happen?
HACS might show 3.9.4, however they apparently do not get updated correctly within the Appdaemon folder.
I’m not sure how this is possible with a supervised Installation if you are able to edit the apps.yaml and see the correct files.
Maybe try to reinstall AppDeamon 
