added a feature request for this
going to Main via HACS, solved the problem, many thanks
Awsome thanks
Nope. When I plug in, appdaemon does see the device and sends commands, but nothing when i press the screen to exit ‘screensaver’.
2022-05-21 20:52:01.540217 INFO nspanel-1: MQTT callback for: {'topic': 'tele/NSPanelTheatre/RESULT', 'wildcard': None, 'payload': '{"nextion":"bytes(\'1A\')"}'}
2022-05-21 20:52:01.040546 INFO nspanel-1: Sending MQTT Message: time~20:52
2022-05-21 20:51:18.936376 INFO nspanel-1: Update Pre-Check sucessful Tasmota Driver Version: 4 Panel Version: 34
2022-05-21 20:51:18.923765 INFO nspanel-1: MQTT callback for: {'topic': 'tele/NSPanelTheatre/RESULT', 'wildcard': None, 'payload': '{"nlui_driver_version":"4"}'}
2022-05-21 20:51:18.744251 INFO nspanel-1: Sending MQTT Message: pageType~screensaver
2022-05-21 20:51:18.716036 INFO nspanel-1: Started rendering of page None with type screensaver
2022-05-21 20:51:18.701073 INFO nspanel-1: Sending MQTT Message: dimmode~10
2022-05-21 20:51:18.691988 INFO nspanel-1: Sending MQTT Message: timeout~20
2022-05-21 20:51:18.683251 INFO nspanel-1: Sending MQTT Message: date~Saturday, 21. May 2022
2022-05-21 20:51:18.672069 INFO nspanel-1: Sending MQTT Message: time~20:51
2022-05-21 20:51:18.653656 INFO nspanel-1: Startup Event
2022-05-21 20:51:18.648348 INFO nspanel-1: Update Pre-Check failed Tasmota Driver Version: None Panel Version: 34
2022-05-21 20:51:18.632312 INFO nspanel-1: Sending MQTT Message: X
2022-05-21 20:51:18.626670 INFO nspanel-1: Received Message from Screen: event,startup,34,us-l
2022-05-21 20:51:18.621660 INFO nspanel-1: MQTT callback for: {'topic': 'tele/NSPanelTheatre/RESULT', 'wildcard': None, 'payload': '{"CustomRecv":"event,startup,34,us-l"}'}
2022-05-21 20:51:01.088282 INFO nspanel-1: Sending MQTT Message: time~20:51
2022-05-21 20:50:01.042570 INFO nspanel-1: Sending MQTT Message: time~20:50
hmm, is the birghtness of the display changing? it should wake up from the sleep brightness without any answer from the backend
another way to test if your touch is working, flash a different firmware / a test file
you could use this one: FlashNextion http://nspanel.pky.eu/test.tft
Ok, so ive got it working finally.
The flash you sent me came up, but still not able to command any touch interface. As a last ditch effort, i disconnected the front panel from the base and checked the pins, put it back and its now working.
I can only suspect something wasnt seated correctly because ive disconnected from power many times (its sitting on the desk next to me, not mounted in wall yet).
Thanks for the help, seems to be self inflicted on this end somehow. Good to note if others have same issue though…
@jobraun , Thanks for the excellent work, shot you some pizza change yesterday after I got your Lovelace UI up and operational. US user here so REALLY appreciate the adaptation.
1 Like
try out current development version
Will do when I am back home.
Thanks
@jobraun - Thanks so much, the best solution I have tried so far 
And the fact that the display is updated whenever you save the apps.yaml file is really neat.
Is there a way to set a background colour or wallpaper image ?
I can’t seem to get the cardQR to work, what exactly is iText ?
it would be great if you could release your ‘sandbox’ configs that you created the screen sample images from, that would make getting started easier with the ability to copy out snippets from the sandbox without having to start from scratch.
background color or wallpaper images are not possible with nextion, you have to modify the firmware in the nextion editor for that
cardQR is upcoming in the next release, you have to update to the current development version for this
The config example in the documentation should cover a lot of the stuff in the sample config. I would like to have some more real world config examples in the appdaemon folder of the repo.
Thanks so much.
Would it be possible to also release the app.yaml code for your test pages 1 - 6
Same as in the README, but since you don’t have the items in your homeassistant it will display them as config errors on your panel.
If you are replacing all of the entity items with items that are existent in your homeassistant you should get all of the screens in that picture.
1 Like
Ahh, ok understood.
I have just updated and now running the “main” development version.
Hi, I’m using nspanel-lovelace-ui interface and I’m having trouble with the time in the screensaver.
Ns panel tasmota time = 20:04
Appdeamon time = 20:04
Home assistant time = 20:04
Ns display time in the screensaver = 18:04
Does anyone know how to fix this.
Who is recreating this 1980’s home automation system GUI??
sounds like your timezone in homeassistant general config isn’t correct (you need to restart the HA host after the chage)
Using nspanel-lovelace-ui interface and having trouble getting time in am/pm.
I have looked at the theme settings and tried a few things my apps.yaml looks like this
nspanel-1:
module: nspanel-lovelace-ui
class: NsPanelLovelaceUIManager
config:
panelRecvTopic: "tele/nspanel/RESULT"
panelSendTopic: "cmnd/nspanel/CustomSend"
updateMode: "auto-notify"
sleepTimeout: 30
#sleepBrightness: 10
sleepBrightness:
- time: "6:00:00"
value: 10
- time: "23:00:00"
value: 2
locale: "en_CA" # used for translations in translations.py and for localized date if babel python package is installed
model: "us-p"
screensaver:
entity: weather.nanaimo
defaultCard: cardThermo_thermostat
theme: !include /config/appdaemon/apps/screensaver-theme.yaml
I downloaded the screensaver-theme.yaml and uncommented the am/pm
#Uncomment by deleting the '#' and configure as you see fit.
#Colors are in the format [Red, Green, Blue] and can be numbers from 0-255
#The items shoud be self-explanatory but tMRIcon affects the humidity icon and tMR affects the humidity text.
#background: [220, 0, 0]
#time: [220, 0, 255]
timeAMPM: [220, 0, 255]
#date: [220, 0, 255]
#tMainIcon: [220, 0, 255]
#tMainText: [220, 0, 255]
#tForecast1: [220, 0, 255]
#tForecast2: [220, 0, 255]
#tForecast3: [220, 0, 255]
#tForecast4: [220, 0, 255]
#tF1Icon: [220, 0, 255]
#tF2Icon: [220, 0, 255]
#tF3Icon: [220, 0, 255]
#tF4Icon: [220, 0, 255]
#tForecast1Val: [220, 0, 255]
#tForecast2Val: [220, 0, 255]
#tForecast3Val: [220, 0, 255]
#tForecast4Val: [220, 0, 255]
#bar: [220, 0, 255]
#tMRIcon: [220, 0, 255]
#tMR: [220, 0, 255]
#autoWeather automatically colors the screensaver weather icons based upon weather. Uncomment the following line to enable.
#autoWeather: true
Tried adding true after it no go. tried uncommenting autoweather and did not see color changes either.
screensaver-theme.yaml is in the same folder as app.yaml
Any help appreciated.
Craig
Figured it out for any one else who may have trouble here is what I did.
nspanel-1:
module: nspanel-lovelace-ui
class: NsPanelLovelaceUIManager
config:
panelRecvTopic: "tele/nspanel/RESULT"
panelSendTopic: "cmnd/nspanel/CustomSend"
updateMode: "auto-notify"
timeFormat: "%I:%M ?%p"
sleepTimeout: 30
#sleepBrightness: 10
sleepBrightness:
- time: "6:00:00"
value: 10
- time: "23:00:00"
value: 2
locale: "en_CA" # used for translations in translations.py and for localized date if babel python package is installed
model: "us-p"
You only need to configure the time format
timeFormat: "%I:%M ?%p"