Monatsrückblick Januar/Februar 2026 ist online!

[ticaki]

Danke, ist kein Problem mit dem Adapter. Schätze mal wie TT-Tom ist das Berry Skript und du warst auf dem falschen Tab unterwegs

Da auf den Stift klicken, dann wird oben alles ausgefüllt und anschließend auf nspanel-aktualisieren klicken. (der name ändert sich)

Tasmotatools hab ich schon länger nicht mehr getestet btw. angepasst - vielleicht funktioniert da der berry teil nicht korrekt.

[TT-Tom]

@muuulle

klick mal auf "Dateisystem verwalten" da, siehst du die Datei.

@ticaki habe Tasmotatools getestet funktioniert noch.

[ticaki]

Kann aber sein das der "leere" Datei bugfix da nicht drin ist. Aber einen Blick ins Dateisystem des NSPanels sollte das klären.

[muuulle]

@TT-Tom
Moin,
es ist tatsächlich leer:

Kann ich die Daten händisch anlegen?

[TT-Tom]

@muuulle sagte in Betatest Adapter NSPanel-lovelace-ui v0.13.x:

Kann ich die Daten händisch anlegen?

Ja könnte man, ist aber nicht die Lösung. Bitte versuche den Schritt über die NSPanel Einstellungen, da sollte dein Panel zu sehen sein. Schau dir das Bild von @ticaki Beitrag an, damit du im richtigen Tab bist. https://forum.iobroker.net/post/1330165. Lass den Adapter auf Debug stehen und schicke uns das Log, damit wir den Fehler finden können zu deinem Problem.

[muuulle]

@TT-Tom
Hallo TT-Tom,

vielen Dank für den Hinweis, ich war wirklich im falschen Tab. Eine autoexec wird weiterhin nicht im Tasmota angezeigt. Hier der zugehörige Log vom ioBroker:

2026-03-17 20:02:46.202 - info: host.pi-slave "system.adapter.nspanel-lovelace-ui.0" enabled
2026-03-17 20:02:46.959 - info: host.pi-slave instance system.adapter.nspanel-lovelace-ui.0 in version "0.14.0" started with pid 55160
2026-03-17 20:02:49.468 - debug: nspanel-lovelace-ui.0 (55160) Redis Objects: Use Redis connection: 192.168.178.116:9001
2026-03-17 20:02:49.541 - debug: nspanel-lovelace-ui.0 (55160) Objects client ready ... initialize now
2026-03-17 20:02:49.544 - debug: nspanel-lovelace-ui.0 (55160) Objects create System PubSub Client
2026-03-17 20:02:49.547 - debug: nspanel-lovelace-ui.0 (55160) Objects create User PubSub Client
2026-03-17 20:02:49.662 - debug: nspanel-lovelace-ui.0 (55160) Objects client initialize lua scripts
2026-03-17 20:02:49.671 - debug: nspanel-lovelace-ui.0 (55160) Objects connected to redis: 192.168.178.116:9001
2026-03-17 20:02:49.747 - debug: nspanel-lovelace-ui.0 (55160) Redis States: Use Redis connection: 192.168.178.116:9000
2026-03-17 20:02:49.793 - debug: nspanel-lovelace-ui.0 (55160) States create System PubSub Client
2026-03-17 20:02:49.795 - debug: nspanel-lovelace-ui.0 (55160) States create User PubSub Client
2026-03-17 20:02:49.920 - debug: nspanel-lovelace-ui.0 (55160) States connected to redis: 192.168.178.116:9000
2026-03-17 20:02:50.853 - info: nspanel-lovelace-ui.0 (55160) starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.nspanel-lovelace-ui, node: v22.22.1, js-controller: 7.0.7
2026-03-17 20:02:50.916 - info: nspanel-lovelace-ui.0 (55160) Configured panels: name#topic -> [Panel_1#Panel_1]
2026-03-17 20:02:50.917 - info: nspanel-lovelace-ui.0 (55160) Found 1 script configs for topics: Panel_1
2026-03-17 20:02:50.918 - info: nspanel-lovelace-ui.0 (55160) Detailed configuration checks are suppressed here. Full validation output is only shown when the configuration script is sent to the adapter.
2026-03-17 20:02:50.923 - debug: nspanel-lovelace-ui.0 (55160) [config-manager] Start converting configuration for Panel_1
2026-03-17 20:02:51.018 - debug: nspanel-lovelace-ui.0 (55160) [config-manager] Screensaver pageItems count: 28
2026-03-17 20:02:51.040 - debug: nspanel-lovelace-ui.0 (55160) Config for Panel_1: raw
2026-03-17 20:02:51.183 - debug: nspanel-lovelace-ui.0 (55160) [library] Load language de
2026-03-17 20:02:51.191 - debug: nspanel-lovelace-ui.0 (55160) [library] Load language de from custom
2026-03-17 20:02:51.196 - info: nspanel-lovelace-ui.0 (55160) [mqttServer] MQTT server started and listening on port 8883
2026-03-17 20:02:51.429 - debug: nspanel-lovelace-ui.0 (55160) Force an MQTT reconnect from the Nspanel with the ip 192.168.178.57 in 10 seconds!
2026-03-17 20:02:52.655 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client "iobroker_35fd1b6d-1538-4195-ba6e-619fb7091747" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:02:52.704 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] MQTT connected.
2026-03-17 20:02:52.803 - debug: nspanel-lovelace-ui.0 (55160) Check configuration!
2026-03-17 20:02:52.809 - debug: nspanel-lovelace-ui.0 (55160) 44467.40625k
2026-03-17 20:02:52.817 - debug: nspanel-lovelace-ui.0 (55160) [controller] controller created
2026-03-17 20:02:53.031 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] subscribe to: Panel_1/stat/RESULT
2026-03-17 20:02:53.047 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1] Panel E0_E2_E6_0B_F3_E8 is initialised!
2026-03-17 20:02:53.048 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] subscribe to: Panel_1/tele/#
2026-03-17 20:02:53.078 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] subscribe to: Panel_1/stat/#
2026-03-17 20:02:53.092 - info: nspanel-lovelace-ui.0 (55160) [Panel_1] Setting panel to offline until first message!
2026-03-17 20:02:53.113 - debug: nspanel-lovelace-ui.0 (55160) [system-notifications] Request notifications from "system.host.iobroker-iobroker"
2026-03-17 20:02:53.131 - debug: nspanel-lovelace-ui.0 (55160) [system-notifications] Received notifications from "system.host.iobroker-iobroker": {}
2026-03-17 20:02:53.131 - debug: nspanel-lovelace-ui.0 (55160) [system-notifications] Request notifications from "system.host.pi-slave"
2026-03-17 20:02:53.136 - debug: nspanel-lovelace-ui.0 (55160) [system-notifications] Received notifications from "system.host.pi-slave": {"system":{"categories":{"packageUpdates":{"instances":{"system.host.pi-slave":{"messages":[{"message":"libcamera-ipa/stable 0.7.0+rpt20260205-1 arm64 [upgradable from: 0.6.0+rpt20251202-1]\nlibrpicam-app1/stable 1.11.1-1 arm64 [upgradable from: 1.10.1-1]\nlinux-headers-rpi-2712/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nlinux-headers-rpi-v8/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nlinux-image-rpi-2712/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nlinux-image-rpi-v8/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nrpicam-apps-core/stable 1.11.1-1 arm64 [upgradable from: 1.10.1-1]","ts":1773774161746}]}},"description":{"en":"Some OS packages can be updated.","de":"Einige Betriebssystempakete können aktualisiert werden.","ru":"Некоторые пакеты ОС могут быть обновлены.","pt":"Alguns pacotes do sistema operativo podem ser actualizados.","nl":"Sommige OS-pakketten kunnen worden bijgewerkt.","fr":"Certains paquets du système d'exploitation peuvent être mis à jour.","it":"Alcuni pacchetti del sistema operativo possono essere aggiornati.","es":"Algunos paquetes del sistema operativo pueden actualizarse.","pl":"Niektóre pakiety systemu operacyjnego mogą zostać zaktualizowane.","uk":"Деякі пакунки ОС можна оновити.","zh-cn":"某些操作系统软件包可以更新。"},"name":{"en":"OS package updates available","de":"Betriebssystem-Paket-Updates verfügbar","ru":"Доступны обновления пакетов ОС","pt":"Actualizações de pacotes do SO disponíveis","nl":"OS-pakketupdates beschikbaar","fr":"Mises à jour du système d'exploitation disponibles","it":"Aggiornamenti del pacchetto OS disponibili","es":"Actualizaciones de paquetes del SO disponibles","pl":"Dostępne aktualizacje pakietów systemu operacyjnego","uk":"Доступні оновлення пакетів ОС","zh-cn":"提供操作系统软件包更新"},"severity":"notify"}},"description":{"en":"These notifications are collected by the ioBroker system and point to issues you should check and fix.","de":"Diese Benachrichtigungen werden vom ioBroker-System erfasst und weisen auf Probleme hin, die überprüft und behoben werden sollten.","ru":"Эти уведомления собираются системой ioBroker и указывают на проблемы, которые вы должны проверить и исправить.","pt":"Essas notificações são coletadas pelo sistema ioBroker e apontam para problemas que você deve verificar e corrigir.","nl":"Deze meldingen worden verzameld door het ioBroker-systeem en wijzen op problemen die u moet controleren en oplossen.","fr":"Ces notifications sont collectées par le système ioBroker et indiquent des problèmes que vous devez vérifier et résoudre.","it":"Queste notifiche vengono raccolte dal sistema ioBroker e indicano problemi che dovresti controllare e correggere.","es":"Estas notificaciones son recopiladas por el sistema ioBroker y señalan problemas que debe verificar y solucionar.","pl":"Te powiadomienia są zbierane przez system ioBroker i wskazują problemy, które należy sprawdzić i naprawić.","uk":"Ці сповіщення збираються системою ioBroker і вказують на проблеми, які ви повинні перевірити та виправити.","zh-cn":"这些通知由ioBroker系统收集，并指出您应检查并修复的问题"},"name":{"en":"System Notifications","de":"System-Benachrichtigungen","ru":"Системные уведомления","pt":"Notificações do sistema","nl":"Systeemmeldingen","fr":"Notifications système","it":"Notifiche di sistema","es":"Notificaciones del sistema","pl":"Powiadomienia systemowe","uk":"Системні сповіщення","zh-cn":"系统通知"}}}
2026-03-17 20:02:53.662 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client iobroker_35fd1b6d-1538-4195-ba6e-619fb7091747 connected.
2026-03-17 20:02:57.388 - debug: nspanel-lovelace-ui.0 (55160) [controller] Panel E0_E2_E6_0B_F3_E8 created
2026-03-17 20:02:57.605 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:02:58.763 - debug: nspanel-lovelace-ui.0 (55160) [controller] No pageConfig available, skipping trash data update.
2026-03-17 20:02:58.764 - info: nspanel-lovelace-ui.0 (55160) [controller] 1 Panels initialized
2026-03-17 20:03:00.604 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:01.746 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client "Panel_1-0BF3E8" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:03:02.026 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:02.668 - debug: nspanel-lovelace-ui.0 (55160) {"command":"refreshMaintainTable","message":{"internalServerIp":"192.168.178.2"},"from":"system.adapter.admin.0","callback":{"message":{"internalServerIp":"192.168.178.2"},"id":1105,"ack":false,"time":1773774182749},"_id":60922982}
2026-03-17 20:03:02.751 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client Panel_1-0BF3E8 connected.
2026-03-17 20:03:02.952 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:05.952 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:10.952 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:17.952 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:26.953 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:37.953 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:03:49.947 - debug: nspanel-lovelace-ui.0 (55160) {"command":"getAllPages","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":1106,"ack":false,"time":1773774230029},"_id":60922983}
2026-03-17 20:03:50.965 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:04:05.975 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:04:22.985 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:04:41.993 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:03.003 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:04.902 - debug: nspanel-lovelace-ui.0 (55160) {"command":"nsPanelInit","message":{"tasmotaName":"Panel_1","tasmotaIP":"192.168.178.57","tasmotaTopic":"Panel_1","mqttServer":true,"mqttIp":"","mqttPort":8883,"mqttUsername":"WNsOXNbpSLDZjgX","mqttPassword":"WGH2BZtuEcI:.ek9p3aI_:p1eJZDEjhkyrvAaW=oyw1O2yxMgm","internalServerIp":"192.168.178.2","useBetaTFT":false,"model":"eu"},"from":"system.adapter.admin.0","callback":{"message":{"tasmotaName":"Panel_1","tasmotaIP":"192.168.178.57","tasmotaTopic":"Panel_1","mqttServer":true,"mqttIp":"","mqttPort":8883,"mqttUsername":"WNsOXNbpSLDZjgX","mqttPassword":"WGH2BZtuEcI:.ek9p3aI_:p1eJZDEjhkyrvAaW=oyw1O2yxMgm","internalServerIp":"192.168.178.2","useBetaTFT":false,"model":"eu"},"id":1107,"ack":false,"time":1773774304989},"_id":60922984}
2026-03-17 20:05:04.903 - info: nspanel-lovelace-ui.0 (55160) Sending mqtt config & base config to tasmota: 192.168.178.57 with user WNsOXNbpSLDZjgX && ***
2026-03-17 20:05:04.904 - debug: nspanel-lovelace-ui.0 (55160) Requesting tasmota status 5 with url: http://192.168.178.57/cm?&cmnd=status%205
2026-03-17 20:05:05.056 - debug: nspanel-lovelace-ui.0 (55160) Response from tasmota status 5: {"StatusNET":{"Hostname":"Panel-1","IPAddress":"192.168.178.57","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.178.1","DNSServer2":"0.0.0.0","Mac":"E0:E2:E6:0B:F3:E8","IP6Global":"fd9a:b998:ff69:481f:e2e2:e6ff:fe0b:f3e8","IP6Local":"fe80::e2e2:e6ff:fe0b:f3e8%st1","Ethernet":{"Hostname":"","IPAddress":"0.0.0.0","Gateway":"0.0.0.0","Subnetmask":"0.0.0.0","DNSServer1":"192.168.178.1","DNSServer2":"0.0.0.0","Mac":"00:00:00:00:00:00","IP6Global":"","IP6Local":""},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":16}}
2026-03-17 20:05:05.057 - debug: nspanel-lovelace-ui.0 (55160) Sending mqtt config & base config to tasmota with IP 192.168.178.57 and name Panel_1.
2026-03-17 20:05:05.138 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] Wait for panel connect on: Panel_1/tele/INFO1
2026-03-17 20:05:05.139 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] subscribe to: Panel_1/tele/INFO1
2026-03-17 20:05:17.653 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client "Panel_1-0BF3E8" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:05:17.713 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] Panel connect detected: Panel_1/tele/INFO1
2026-03-17 20:05:17.790 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] Wait for panel connect on: Panel_1/tele/INFO1
2026-03-17 20:05:17.791 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] subscribe to: Panel_1/tele/INFO1
2026-03-17 20:05:17.913 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:18.655 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client Panel_1-0BF3E8 connected.
2026-03-17 20:05:18.856 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:21.857 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:26.858 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:28.467 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client "Panel_1-0BF3E8" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:05:28.525 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] Panel connect detected: Panel_1/tele/INFO1
2026-03-17 20:05:28.726 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:29.470 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client Panel_1-0BF3E8 connected.
2026-03-17 20:05:29.670 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:30.812 - info: nspanel-lovelace-ui.0 (55160) Installing berry on tasmota with IP 192.168.178.57, name Panel_1.
2026-03-17 20:05:30.813 - debug: nspanel-lovelace-ui.0 (55160) URL: http://192.168.178.57/cm?&cmnd=Backlog UfsRename autoexec.be,autoexec.old; UrlFetch https://raw.githubusercontent.com/ticaki/ioBroker.nspanel-lovelace-ui/main/tasmota/berry/10/autoexec.be; Restart 1
2026-03-17 20:05:30.917 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] Wait for panel connect on: Panel_1/tele/INFO1
2026-03-17 20:05:30.917 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] subscribe to: Panel_1/tele/INFO1
2026-03-17 20:05:30.919 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1] Received STATUS10 with sensor data, updated info and states!
2026-03-17 20:05:32.670 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:37.672 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:40.999 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client "Panel_1-0BF3E8" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:05:41.061 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] Panel connect detected: Panel_1/tele/INFO1
2026-03-17 20:05:41.261 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:42.002 - debug: nspanel-lovelace-ui.0 (55160) [mqttServer] Client Panel_1-0BF3E8 connected.
2026-03-17 20:05:42.202 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:44.063 - debug: nspanel-lovelace-ui.0 (55160) FlashNextionAdv0 http://nspanel.de/nspanel-v5.1.1.tft
2026-03-17 20:05:44.164 - info: nspanel-lovelace-ui.0 (55160) Installing tft on tasmota with IP 192.168.178.57 and name Panel_1.
2026-03-17 20:05:44.170 - debug: nspanel-lovelace-ui.0 (55160) Create/Update script script.js.nspanel-lovelace-ui_0.globalPageConfig
2026-03-17 20:05:44.189 - info: nspanel-lovelace-ui.0 (55160) Update script script.js.nspanel-lovelace-ui_0.globalPageConfig
2026-03-17 20:05:44.190 - info: nspanel-lovelace-ui.0 (55160) Update global script script.js.nspanel-lovelace-ui_0.globalPageConfig
2026-03-17 20:05:44.276 - debug: nspanel-lovelace-ui.0 (55160) Create script script.js.nspanel-lovelace-ui_0.Panel_1
2026-03-17 20:05:44.306 - info: nspanel-lovelace-ui.0 (55160) Update script script.js.nspanel-lovelace-ui_0.Panel_1
2026-03-17 20:05:45.203 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:48.025 - info: host.pi-slave instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 55180
2026-03-17 20:05:48.975 - info: host.pi-slave stopInstance system.adapter.nspanel-lovelace-ui.0 (force=false, process=true)
2026-03-17 20:05:48.979 - info: nspanel-lovelace-ui.0 (55160) Got terminate signal TERMINATE_YOURSELF
2026-03-17 20:05:49.162 - info: host.pi-slave stopInstance system.adapter.nspanel-lovelace-ui.0 send kill signal
2026-03-17 20:05:49.178 - debug: nspanel-lovelace-ui.0 (55160) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:05:49.179 - info: nspanel-lovelace-ui.0 (55160) [Panel_1] Goint offline because delete panel!
2026-03-17 20:05:49.269 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] unsubscribe from: Panel_1/stat/RESULT
2026-03-17 20:05:49.271 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] unsubscribe from: Panel_1/tele/#
2026-03-17 20:05:49.272 - debug: nspanel-lovelace-ui.0 (55160) [mqttClient] unsubscribe from: Panel_1/stat/#
2026-03-17 20:05:49.323 - info: nspanel-lovelace-ui.0 (55160) [mqttClient] MQTT connection closed.
2026-03-17 20:05:49.327 - info: nspanel-lovelace-ui.0 (55160) terminating
2026-03-17 20:05:49.329 - info: nspanel-lovelace-ui.0 (55160) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-17 20:05:49.482 - info: nspanel-lovelace-ui.0 (55160) terminating
2026-03-17 20:05:50.100 - info: host.pi-slave instance system.adapter.nspanel-lovelace-ui.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-17 20:05:53.661 - info: host.pi-slave instance system.adapter.nspanel-lovelace-ui.0 in version "0.14.0" started with pid 55196
2026-03-17 20:05:56.149 - debug: nspanel-lovelace-ui.0 (55196) Redis Objects: Use Redis connection: 192.168.178.116:9001
2026-03-17 20:05:56.222 - debug: nspanel-lovelace-ui.0 (55196) Objects client ready ... initialize now
2026-03-17 20:05:56.225 - debug: nspanel-lovelace-ui.0 (55196) Objects create System PubSub Client
2026-03-17 20:05:56.228 - debug: nspanel-lovelace-ui.0 (55196) Objects create User PubSub Client
2026-03-17 20:05:56.362 - debug: nspanel-lovelace-ui.0 (55196) Objects client initialize lua scripts
2026-03-17 20:05:56.371 - debug: nspanel-lovelace-ui.0 (55196) Objects connected to redis: 192.168.178.116:9001
2026-03-17 20:05:56.444 - debug: nspanel-lovelace-ui.0 (55196) Redis States: Use Redis connection: 192.168.178.116:9000
2026-03-17 20:05:56.490 - debug: nspanel-lovelace-ui.0 (55196) States create System PubSub Client
2026-03-17 20:05:56.492 - debug: nspanel-lovelace-ui.0 (55196) States create User PubSub Client
2026-03-17 20:05:56.620 - debug: nspanel-lovelace-ui.0 (55196) States connected to redis: 192.168.178.116:9000
2026-03-17 20:05:56.779 - info: nspanel-lovelace-ui.0 (55196) starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.nspanel-lovelace-ui, node: v22.22.1, js-controller: 7.0.7
2026-03-17 20:05:56.842 - info: nspanel-lovelace-ui.0 (55196) Configured panels: name#topic -> [Panel_1#Panel_1]
2026-03-17 20:05:56.843 - info: nspanel-lovelace-ui.0 (55196) Found 1 script configs for topics: Panel_1
2026-03-17 20:05:56.843 - info: nspanel-lovelace-ui.0 (55196) Detailed configuration checks are suppressed here. Full validation output is only shown when the configuration script is sent to the adapter.
2026-03-17 20:05:56.848 - debug: nspanel-lovelace-ui.0 (55196) [config-manager] Start converting configuration for Panel_1
2026-03-17 20:05:56.942 - debug: nspanel-lovelace-ui.0 (55196) [config-manager] Screensaver pageItems count: 28
2026-03-17 20:05:56.951 - debug: nspanel-lovelace-ui.0 (55196) Config for Panel_1: raw
2026-03-17 20:05:57.093 - debug: nspanel-lovelace-ui.0 (55196) [library] Load language de
2026-03-17 20:05:57.103 - debug: nspanel-lovelace-ui.0 (55196) [library] Load language de from custom
2026-03-17 20:05:57.108 - info: nspanel-lovelace-ui.0 (55196) [mqttServer] MQTT server started and listening on port 8883
2026-03-17 20:05:57.307 - debug: nspanel-lovelace-ui.0 (55196) Force an MQTT reconnect from the Nspanel with the ip 192.168.178.57 in 10 seconds!
2026-03-17 20:05:58.533 - debug: nspanel-lovelace-ui.0 (55196) [mqttServer] Client "iobroker_77ce8a31-fb9e-457e-9fd5-17780e3856c2" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:05:58.580 - debug: nspanel-lovelace-ui.0 (55196) [mqttClient] MQTT connected.
2026-03-17 20:05:58.682 - debug: nspanel-lovelace-ui.0 (55196) Check configuration!
2026-03-17 20:05:58.690 - debug: nspanel-lovelace-ui.0 (55196) 44414.515625k
2026-03-17 20:05:58.697 - debug: nspanel-lovelace-ui.0 (55196) [controller] controller created
2026-03-17 20:05:58.902 - debug: nspanel-lovelace-ui.0 (55196) [mqttClient] subscribe to: Panel_1/stat/RESULT
2026-03-17 20:05:58.918 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1] Panel E0_E2_E6_0B_F3_E8 is initialised!
2026-03-17 20:05:58.919 - debug: nspanel-lovelace-ui.0 (55196) [mqttClient] subscribe to: Panel_1/tele/#
2026-03-17 20:05:58.948 - debug: nspanel-lovelace-ui.0 (55196) [mqttClient] subscribe to: Panel_1/stat/#
2026-03-17 20:05:58.963 - info: nspanel-lovelace-ui.0 (55196) [Panel_1] Setting panel to offline until first message!
2026-03-17 20:05:58.983 - debug: nspanel-lovelace-ui.0 (55196) [system-notifications] Request notifications from "system.host.iobroker-iobroker"
2026-03-17 20:05:58.998 - debug: nspanel-lovelace-ui.0 (55196) [system-notifications] Received notifications from "system.host.iobroker-iobroker": {}
2026-03-17 20:05:58.999 - debug: nspanel-lovelace-ui.0 (55196) [system-notifications] Request notifications from "system.host.pi-slave"
2026-03-17 20:05:59.004 - debug: nspanel-lovelace-ui.0 (55196) [system-notifications] Received notifications from "system.host.pi-slave": {"system":{"categories":{"packageUpdates":{"instances":{"system.host.pi-slave":{"messages":[{"message":"libcamera-ipa/stable 0.7.0+rpt20260205-1 arm64 [upgradable from: 0.6.0+rpt20251202-1]\nlibrpicam-app1/stable 1.11.1-1 arm64 [upgradable from: 1.10.1-1]\nlinux-headers-rpi-2712/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nlinux-headers-rpi-v8/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nlinux-image-rpi-2712/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nlinux-image-rpi-v8/stable 1:6.12.75-1+rpt1 arm64 [upgradable from: 1:6.12.62-1+rpt1]\nrpicam-apps-core/stable 1.11.1-1 arm64 [upgradable from: 1.10.1-1]","ts":1773774161746}]}},"description":{"en":"Some OS packages can be updated.","de":"Einige Betriebssystempakete können aktualisiert werden.","ru":"Некоторые пакеты ОС могут быть обновлены.","pt":"Alguns pacotes do sistema operativo podem ser actualizados.","nl":"Sommige OS-pakketten kunnen worden bijgewerkt.","fr":"Certains paquets du système d'exploitation peuvent être mis à jour.","it":"Alcuni pacchetti del sistema operativo possono essere aggiornati.","es":"Algunos paquetes del sistema operativo pueden actualizarse.","pl":"Niektóre pakiety systemu operacyjnego mogą zostać zaktualizowane.","uk":"Деякі пакунки ОС можна оновити.","zh-cn":"某些操作系统软件包可以更新。"},"name":{"en":"OS package updates available","de":"Betriebssystem-Paket-Updates verfügbar","ru":"Доступны обновления пакетов ОС","pt":"Actualizações de pacotes do SO disponíveis","nl":"OS-pakketupdates beschikbaar","fr":"Mises à jour du système d'exploitation disponibles","it":"Aggiornamenti del pacchetto OS disponibili","es":"Actualizaciones de paquetes del SO disponibles","pl":"Dostępne aktualizacje pakietów systemu operacyjnego","uk":"Доступні оновлення пакетів ОС","zh-cn":"提供操作系统软件包更新"},"severity":"notify"}},"description":{"en":"These notifications are collected by the ioBroker system and point to issues you should check and fix.","de":"Diese Benachrichtigungen werden vom ioBroker-System erfasst und weisen auf Probleme hin, die überprüft und behoben werden sollten.","ru":"Эти уведомления собираются системой ioBroker и указывают на проблемы, которые вы должны проверить и исправить.","pt":"Essas notificações são coletadas pelo sistema ioBroker e apontam para problemas que você deve verificar e corrigir.","nl":"Deze meldingen worden verzameld door het ioBroker-systeem en wijzen op problemen die u moet controleren en oplossen.","fr":"Ces notifications sont collectées par le système ioBroker et indiquent des problèmes que vous devez vérifier et résoudre.","it":"Queste notifiche vengono raccolte dal sistema ioBroker e indicano problemi che dovresti controllare e correggere.","es":"Estas notificaciones son recopiladas por el sistema ioBroker y señalan problemas que debe verificar y solucionar.","pl":"Te powiadomienia są zbierane przez system ioBroker i wskazują problemy, które należy sprawdzić i naprawić.","uk":"Ці сповіщення збираються системою ioBroker і вказують на проблеми, які ви повинні перевірити та виправити.","zh-cn":"这些通知由ioBroker系统收集，并指出您应检查并修复的问题"},"name":{"en":"System Notifications","de":"System-Benachrichtigungen","ru":"Системные уведомления","pt":"Notificações do sistema","nl":"Systeemmeldingen","fr":"Notifications système","it":"Notifiche di sistema","es":"Notificaciones del sistema","pl":"Powiadomienia systemowe","uk":"Системні сповіщення","zh-cn":"系统通知"}}}
2026-03-17 20:05:59.552 - debug: nspanel-lovelace-ui.0 (55196) [mqttServer] Client iobroker_77ce8a31-fb9e-457e-9fd5-17780e3856c2 connected.
2026-03-17 20:06:04.163 - debug: nspanel-lovelace-ui.0 (55196) [controller] Panel E0_E2_E6_0B_F3_E8 created
2026-03-17 20:06:04.165 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/STATUS0","payload":""} to panel.
2026-03-17 20:06:04.493 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:05.681 - debug: nspanel-lovelace-ui.0 (55196) [controller] No pageConfig available, skipping trash data update.
2026-03-17 20:06:05.681 - info: nspanel-lovelace-ui.0 (55196) [controller] 1 Panels initialized
2026-03-17 20:06:06.400 - info: host.pi-slave instance system.adapter.weatherunderground.0 having pid 55180 terminated with code 0 (NO_ERROR)
2026-03-17 20:06:06.966 - debug: nspanel-lovelace-ui.0 (55196) [mqttServer] Client "Panel_1-0BF3E8" login successful (user="WNsOXNbpSLDZjgX").
2026-03-17 20:06:07.230 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:07.970 - debug: nspanel-lovelace-ui.0 (55196) [mqttServer] Client Panel_1-0BF3E8 connected.
2026-03-17 20:06:08.170 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:11.170 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:16.172 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:23.172 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:32.172 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:43.172 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.
2026-03-17 20:06:56.184 - debug: nspanel-lovelace-ui.0 (55196) [Panel_1-SendClass] send payload: {"topic":"Panel_1/cmnd/CustomSend","payload":"pageType~pageStartup","opt":{"retain":true}} to panel.

[ticaki]

Kann es sein das das NSPanel keinen Internetzugang hat?

Wenn du

UrlFetch https://raw.githubusercontent.com/ticaki/ioBroker.nspanel-lovelace-ui/main/tasmota/berry/10/autoexec.be

in die Tasmota Konsole eingibst sollte das Berryscript installiert werden - wenn das Panel internet hat.

[ticaki]

0.15.1 (2026-03-18)

• (ticaki) added: internet access check for Tasmota device before berry installation
• (ticaki) Möglichkeit die urls auf eigene lokale umzustellen - nicht empfohlen - finger weg wenn ihr die arbeit die das bringt scheut.

Der Tasmota check geht auf raw.githubusercontent.com und wird beim aktualisieren/initialisieren durchgeführt

Das Umbiegen der Adressen auf einen eigenen Server ist für Leute gedacht die alles Lokal haben möchten und wird nur minimal supportet - keiner der Entwickler nutzt das. In dem Fall geht der check auf den hostname.

Man findet es unter:

Expert an -> Tab Developer

Wer das verwendet bitte die Verzeichnisstruktur unter Berry beachten .../10/autoexec.be - Die Dateibezeichner bei berry und tft müssen identisch sein.

[muuulle]

Perfekt. Jetzt klappt’s. Das Panel hatte ebenfalls keinen Zugang zum Internet.. Tausend Dank für eure Unterstützung. Jetzt muss ich nur noch die alten Einstellungen wieder herstellen 🙂

[13patrick37]

@ticaki was ich letztens mit Tom schon besprochen hatte: ist es möglich im Spotify/Sonos Player die Lautstärke Regelung zu ändern? Der Schieberegler erhöht ja +/-1. Allerdings ist das teilweise schwierig zu bedienen.

Kann man das irgendwie ändern, dass auf den seitlichen+/- Buttons auch nur die Lautstärke um einen Punkt erhöht/gesenkt wird?

[ticaki]

Hm hab ich nicht mit bekommen oder ... em dachte das wäre ein Skriptänderungswunsch :D
Ich gucke mal

[ticaki]

@13patrick37
@armilar
Da könnte ich zwar was rum hacken - was dann komisch funktioniert. Jedoch um das ordentlich zu machen muß das tft angepasst werden.

das +/- vom TFT sendet aktuelles Volumen +/-1 zurück und bewegt den Slider um eine Position - der Adapter schreibst in den State nach min/max anpassungen und return dann die Antwort vom entsprechenden Adapter wieder ans panel - dadurch springt der slider dann ab und an. Wenn ich da rumhacke springt der nicht nur ab und an und auch nicht nur selten :D. Um das zu lösen mußte der +/- Wert im Panel einstellbar sein.

{"topic":"nspanel/ns_panel2/cmnd/CustomSend","payload":"entityUpd~ Mmm Mmm Mmm Mmm ~button~bUp~~17299~~~~~~~~~media~ Mmm Mmm Mmm Mmm | 1:50-3:50~65535~ 50 Jahre - Die internation~53247~43~~1374~~number~3?logo~logo-sonos~63519~Wiedergabeposition~49|0|100~button~3?1~~1374~~1~input_sel~3?2~~2047~Favoritenliste~PRESS~text~3?4~11:01¬1~53247~~11:01~input_sel~3?5~~2047~Titelübersicht~PRESS~button~3?0-NextPageArrow~~2047~mehr~1"}

z.B. wenn da die 43 eine optionalen Anhang vom Typ Zahl bekommt - also 43?5

Keine Ahnung wann und ob Armilar da zeit für hat.

Ich empfehle dir ein Issue aufzumachen und @armilar + Beschreibung deines Wunsches rein zu schreiben

@tt-tom fyi

[ticaki]

@13patrick37
Abgesehen davon wieviele sonos hast du? Wenn mehr als 1 - wie gut findest du die Einbindung. Da ich mir damit viel Arbeit gemacht habe und du es vielleicht falsch konfiguriert haben kannst - will ich das mal checken. Bei mir sieht das so aus:

Ich hab 3 die meist mittels Nspanel in eine Gruppe zusammengefasst werden - und kann sie in jedem raum steuern ohne fummeln.

Panel 1

    const SonosWohnzimmer: PageType = {
        type: 'cardMedia',
        heading: 'main',
        alwaysOnDisplay: true,
        media: {
            id: 'sonos.0.root.192_168_178_209',
            speakerList: [],
            minValue: 0,
            maxValue: 30,
        },
        parent: 'main',
        uniqueName: 'SonosWohnzimmer',
        items: [],
        scrollPresentation: 'arrow'
    };

Panel 2

const SonosSchlafzimmer: PageType = {
        type: 'cardMedia',
        heading: 'main',
        alwaysOnDisplay: true,
        media: {
            id: 'sonos.0.root.192_168_178_57',
            speakerList: [],
            minValue: 0,
            maxValue: 50,
        },
        uniqueName: 'SonosSchlafzimmer',
        parent: 'main',
        items: [],
        scrollPresentation: 'arrow'
    };

usw.

EDIT:
1 Sache ist doch fummelig - aber das geht nicht besser :D

Wenn ich was anderes im Schlafzimmer hören will und mich dann umentscheide muß ich entweder im schlafzimmer kurz was anspielen und dann alle lautsprecher im Schlafzimmer hinzufügen oder aber woanders hin gehen und das Schlafzimmer dort zur größeren Gruppe wieder hinzufügen - das ist aber verschmerzbar ^^

[muuulle]

Moin zusammen,
bisher hatte ich den advanced Screensaver. Nach Nachbau der bisherigen Ansichten, wird mir nun der Standard-Screensaver angezeigt. Wo konnte man noch den advanced Screensaver auswählen?

Vielen Dank für einen kurzen Anschub :)

[TT-Tom]

@muuulle

Es gibt mehrere Stellen das zu ändern.
Serviceseite
Objekte-> Screensaver
Admin-Tab (links) einfach anklicken und dann auswählen