NEWS
[gelöst] Brauche Hilfe beim NSPanel mit Tasmota
-
Wie sehen die Config Parameter bei dir aus?
export const config = <Config> { panelRecvTopic: 'mqtt.1.SmartHome.NSPanel_1.tele.RESULT', // Bitte anpassen panelSendTopic: 'mqtt.1.SmartHome.NSPanel_1.cmnd.CustomSend', // Bitte anpassen -
@armilar
Habe beide Befehle nacheinander ausgeführt, Panel hat neu gebootet und das flashen wurde auch ausgeführt.21:01:43.911 MQT: SmartHome/NSPanel_1/tele/STATE = {"Time":"2023-02-16T21:01:43","Uptime":"0T00:01:40","UptimeSec":100,"Heap":152,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":999,"MqttCount":1,"Berry":{"HeapUsed":16,"Objects":240},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"GS-Net","BSSId":"CC:CE:1E:AD:6B:A8","Channel":10,"Mode":"11n","RSSI":100,"Signal":-43,"LinkCount":1,"Downtime":"0T00:00:04"}} 21:01:43.957 MQT: SmartHome/NSPanel_1/tele/SENSOR = {"Time":"2023-02-16T21:01:43","ANALOG":{"Temperature1":19.8},"ESP32":{"Temperature":48.1},"TempUnit":"C"} 21:01:48.685 MQT: SmartHome/NSPanel_1/tele/RESULT = {"CustomRecv":"event,startup,49,eu"} -
Sende mal die Config Paramater aus dem Post darüber.
-
export const config: Config = { panelRecvTopic: 'mqtt.1.SmartHome.NSPanel_1.tele.RESULT', // Bitte anpassen panelSendTopic: 'mqtt.1.SmartHome.NSPanel_1.cmnd.CustomSend', // Bitte anpassenHatte ich lt. dem Video angepasst
-
@armilar
Welche Config Parameter meinst du? -
okay, das Panel hat einen Pfad mit Datenpunkte in 0_userdata angelegt. Den mal löschen. Dann das TypeScript nochmal starten...

komplett löschen
-
Welche Config Parameter meinst du?
die
export const config: Config = { panelRecvTopic: 'mqtt.1.SmartHome.NSPanel_1.tele.RESULT', // Bitte anpassen panelSendTopic: 'mqtt.1.SmartHome.NSPanel_1.cmnd.CustomSend', // Bitte anpassenDie aus dem Script aus deinem Post davor
-
Die Datenpunkte hat das Script neu angelegt.
Aber die Struktur ist jetzt anders.

Hier die alte Struktur

-
Das was du alte Struktur nennst ist der Screenshot aus den MQTT Objekten, nicht 0_userdata
-
Jup, hab ich gerade auch gesehen

-
Wie sehen denn die tele Datenpunkte im mqtt.1. aus?
EDIT: Du hast da aber keinen Mosquitto oder eine andere Fehlerquelle dazwischen, oder?
Port 1886 jetzt auch in Tasmota?
-
Info1
{"Info1":{"Module":"NSPanel","Version":"12.3.1.3(tasmota32-SONOFF_NSPANEL_DE)","FallbackTopic":"cmnd/NSPanel_01_fb/","GroupTopic":"SmartHome/tasmotas/cmnd/"}}Info2
{"Info2":{"WebServerMode":"Admin","Hostname":"NSPanel-1-3720","IPAddress":"192.168.10.130","IP6Global":"","IP6Local":"fe80::c6dd:57ff:fee7:ee88"}}Info3
{"Info3":{"RestartReason":"Software reset CPU","BootCount":53}}Result
{"CustomRecv":"event,startup,49,eu"}State
{"Time":"2023-02-16T21:22:53","Uptime":"0T00:22:50","UptimeSec":1370,"Heap":151,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":999,"MqttCount":1,"Berry":{"HeapUsed":16,"Objects":240},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"GS-Net","BSSId":"CC:CE:1E:AD:6B:A8","Channel":10,"Mode":"11n","RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:04"}}EDIT: Du hast da aber keinen Mosquitto oder eine andere Fehlerquelle dazwischen, oder?
Nein, alles dirket. NSPanel -> ioBroker
Port 1886 jetzt auch in Tasmota?
NSPanel hat jetzt ebenfalls 1886 in den mqtt-Einstellungen -
Die Empfangsrichtung ist perfekt. Verstehe im Moment nur nicht, warum der CustomSend da nichts sendet. Das Script befeuert den ja schon mit Daten
Gib mal einfach nur folgendes in die Tasmota-Console
CustomSend time~21:30 -
@armilar said in Brauche Hilfe beim NSPanel mit Tasmota:
CustomSend time~21:30
21:30:09.186 MQT: SmartHome/NSPanel_1/stat/RESULT = {"CustomSend":"Done"} 21:30:12.958 MQT: SmartHome/NSPanel_1/tele/STATE = {"Time":"2023-02-16T21:30:12","Uptime":"0T00:01:28","UptimeSec":88,"Heap":145,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":595,"MqttCount":1,"Berry":{"HeapUsed":16,"Objects":239},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"GS-Net","BSSId":"CC:CE:1E:AD:6B:A8","Channel":10,"Mode":"11n","RSSI":100,"Signal":-45,"LinkCount":1,"Downtime":"0T00:00:03"}} 21:30:13.004 MQT: SmartHome/NSPanel_1/tele/SENSOR = {"Time":"2023-02-16T21:30:12","ANALOG":{"Temperature1":20.4},"ESP32":{"Temperature":49.2},"TempUnit":"C"} 21:30:14.770 MQT: SmartHome/NSPanel_1/tele/RESULT = {"CustomRecv":"event,startup,49,eu"} 21:30:20.770 MQT: SmartHome/NSPanel_1/tele/RESULT = {"CustomRecv":"event,startup,49,eu"} 21:30:22.959 MQT: SmartHome/NSPanel_1/tele/STATE = {"Time":"2023-02-16T21:30:22","Uptime":"0T00:01:38","UptimeSec":98,"Heap":147,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":634,"MqttCount":1,"Berry":{"HeapUsed":16,"Objects":240},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"GS-Net","BSSId":"CC:CE:1E:AD:6B:A8","Channel":10,"Mode":"11n","RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:03"}} 21:30:22.999 MQT: SmartHome/NSPanel_1/tele/SENSOR = {"Time":"2023-02-16T21:30:22","ANALOG":{"Temperature1":20.4},"ESP32":{"Temperature":49.8},"TempUnit":"C"} 21:30:26.671 MQT: SmartHome/NSPanel_1/tele/RESULT = {"CustomRecv":"event,startup,49,eu"} 21:30:32.672 MQT: SmartHome/NSPanel_1/tele/RESULT = {"CustomRecv":"event,startup,49,eu"} 21:30:32.958 MQT: SmartHome/NSPanel_1/tele/STATE = {"Time":"2023-02-16T21:30:32","Uptime":"0T00:01:48","UptimeSec":108,"Heap":147,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":670,"MqttCount":1,"Berry":{"HeapUsed":16,"Objects":240},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"GS-Net","BSSId":"CC:CE:1E:AD:6B:A8","Channel":10,"Mode":"11n","RSSI":100,"Signal":-43,"LinkCount":1,"Downtime":"0T00:00:03"}} 21:30:33.003 MQT: SmartHome/NSPanel_1/tele/SENSOR = {"Time":"2023-02-16T21:30:32","ANALOG":{"Temperature1":20.4},"ESP32":{"Temperature":49.8},"TempUnit":"C"} -
und das Ding dreht sich immer noch?
-
@armilar
Hat bald einen Drehwurm.
Keine Änderung -
ioBroker mal durchgestartet?
-
@armilar
iobroker neu gestartet, NSPanel KaltstartUnd es dreht sich immer noch

-
-
Zeige bitte nochmal deine aktuellen Einstellungen aus dem Tasmota MQTT