Closed Klaus-Lucas closed 1 year ago
Nein, denke du hast das richtig gemacht. Die Station reagiert nur auf die Komandos anders als ich es erwarte. Leider habe ich keine DP1500 zum Testen und bis jetzt konnte mir keiner sagen wie genau die funktioniert.
Wenn es dazu irgendwo eine Anleitung gibt kann ich den Scheduler noch einpflegen. Bis dahin musst Du wohl mit dem Listener Modus agieren.
"Bis dahin musst Du wohl mit dem Listener Modus agieren." OK, das läuft
Das ist doch schonmal gut. Nein, das Gerät zu haben hilft nur bedingt. Ich bräuchte infos wie ich die Daten von der Station zerlegen muss. Da kommt eben sowas wie
ffff50120e475731303030415f56312e372e36bf
Das sieht ja ähnlich aus wie das was meine Station liefert. Aber eben nicht gleich. Vermutlich ist es nicht schwierig, wenn man weiss wie. Für die ELV gibt es eben ne schöne Doku.
Wenn Du mal mutig sein willst :D Im Order Lib gibt es eine Datei constants.js, hier müssten ein paar Zeilen getauscht werden, und dann sollte ich zumindest die Softwareversion auslesen können. Hab ich gerade mal mit dem Log von Dir probiert-
Etwa auf Zeile 1579 wir ein Array COMMANS definiert. Schau da mal rein, es gibt ein block 'Get Firmware'. Hier muss das subcommand_init und die length geändert werden. Es sollte so aussehen:
{
name: 'Get Firmware (DP1000)(',
configurable: true,
config_variable: 'ws_getfirmware',
channel: 'info',
command: [0xFF, 0xFF, 0x50, 0x03, 0x53],
command_int: 80,
subcommand_int: 71,
parser: new BinaryParser()
.endianess('big').seek(5)
.string('softwaretype', {
encoding: 'utf8',
length: 14
})
},
Dann aktiviere mal im Zeitplan nur die 'Firmware abrufen' und starte den Scheduler. Vielleicht können wir uns ja so der Sache nähern...
Klar, mach ich. Parallel habe ich mal bei ecowitt wegen Doku. nachgefragt.
-------- Ursprüngliche Nachricht -------- Von: "Daniel Dräs" @.> Gesendet: 25. Juli 2023 14:20:42 MESZ An: "phifogg/ioBroker.sainlogic" @.> CC: Klaus Lucas @.>, Author @.> Betreff: Re: [phifogg/ioBroker.sainlogic] Scheduler received data for unkown command XX subcommand YY (Issue #174)
Wenn Du mal mutig sein willst :D Im Order Lib gibt es eine Datei constants.js, hier müssten ein paar Zeilen getauscht werden, und dann sollte ich zumindest die Softwareversion auslesen können. Hab ich gerade mal mit dem Log von Dir probiert-
Etwa auf Zeile 1579 wir ein Array COMMANS definiert. Schau da mal rein, es gibt ein block 'Get Firmware'. Hier muss das subcommand_init und die length geändert werden. Es sollte so aussehen:
{ name: 'Get Firmware (DP1000)(', configurable: true, config_variable: 'ws_getfirmware', channel: 'info', command: [0xFF, 0xFF, 0x50, 0x03, 0x53], command_int: 80, subcommand_int: 71, parser: new BinaryParser() .endianess('big').seek(5) .string('softwaretype', { encoding: 'utf8', length: 14 }) },
Dann aktiviere mal im Zeitplan nur die 'Firmware abrufen' und starte den Scheduler. Vielleicht können wir uns ja so der Sache nähern...
-- Reply to this email directly or view it on GitHub: https://github.com/phifogg/ioBroker.sainlogic/issues/174#issuecomment-1649733123 You are receiving this because you authored the thread.
Message ID: @.***>
da bist du wohl auf dem richtigem Wege:
2023-07-25 16:58:48.510 - info: sainlogic.0 (8516) starting. Version 0.10.5 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.17.0, js-controller: 5.0.8
2023-07-25 16:58:48.555 - info: sainlogic.0 (8516) Starting Scheduler
2023-07-25 16:58:48.556 - info: sainlogic.0 (8516) Scheduler call ws_getfirmware activated
2023-07-25 16:58:48.557 - debug: sainlogic.0 (8516) Weatherstation IP: 192.168.178.45
2023-07-25 16:58:48.558 - debug: sainlogic.0 (8516) Weatherstation port: 45000
2023-07-25 16:58:48.559 - debug: sainlogic.0 (8516) Scheduler Interval: 15
2023-07-25 16:59:03.560 - info: sainlogic.0 (8516) Scheduler pulling for new data
2023-07-25 16:59:03.656 - debug: sainlogic.0 (8516) Scheduler connected to weather station run 255,255,80,3,83
2023-07-25 16:59:03.676 - debug: sainlogic.0 (8516) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf
2023-07-25 16:59:03.679 - debug: sainlogic.0 (8516) Data Command received: 80 subcommand 71
2023-07-25 16:59:03.682 - debug: sainlogic.0 (8516) Data object: {"softwaretype":"GW1000A_V1.7.6"}
2023-07-25 16:59:03.683 - info: sainlogic.0 (8516) Scheduler updating IOBroker states
2023-07-25 16:59:03.686 - debug: sainlogic.0 (8516) Setting value from data for info.softwaretype to GW1000A_V1.7.6
2023-07-25 16:59:03.689 - debug: sainlogic.0 (8516) FW Scheduler Connection closed
2023-07-25 16:59:18.559 - info: sainlogic.0 (8516) Scheduler pulling for new data
2023-07-25 16:59:18.567 - debug: sainlogic.0 (8516) Scheduler connected to weather station run 255,255,80,3,83
2023-07-25 16:59:18.586 - debug: sainlogic.0 (8516) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf
2023-07-25 16:59:18.587 - debug: sainlogic.0 (8516) Data Command received: 80 subcommand 71
2023-07-25 16:59:18.587 - debug: sainlogic.0 (8516) Data object: {"softwaretype":"GW1000A_V1.7.6"}
2023-07-25 16:59:18.588 - info: sainlogic.0 (8516) Scheduler updating IOBroker states
2023-07-25 16:59:18.590 - debug: sainlogic.0 (8516) Setting value from data for info.softwaretype to GW1000A_V1.7.6
2023-07-25 16:59:18.598 - debug: sainlogic.0 (8516) FW Scheduler Connection closed
Wird aber nicht in Objekte/Model angezeigt/übernommen.
Wunderground Listener klappte auch nicht:
2023-07-25 17:22:29.911 - info: sainlogic.0 (25387) starting. Version 0.10.5 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.17.0, js-controller: 5.0.8 2023-07-25 17:22:29.960 - debug: sainlogic.0 (25387) Listener IP: 192.168.178.41 2023-07-25 17:22:29.961 - debug: sainlogic.0 (25387) Listener port: 45000 2023-07-25 17:22:29.962 - debug: sainlogic.0 (25387) Listener path: /weatherstation/updateweatherstation.php? 2023-07-25 17:22:29.963 - debug: sainlogic.0 (25387) Listener protocol: wunderground 2023-07-25 17:22:29.963 - debug: sainlogic.0 (25387) Forward URL: 2023-07-25 17:22:29.965 - info: sainlogic.0 (25387) Starting Listener
2023-07-25 17:23:14.849 - warn: sainlogic.0 (25387) Listener received illegal request: /weatherstation/updateweatherstation.php?ID=IMOERS179&PASSWORD=UNcqivm3&tempf=-9999&humidity=-9999&dewptf=-9999&windchillf=-9999&winddir=-9999&windspeedmph=-9999&windgustmph=-9999&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.445&monthlyrainin=1.535&yearlyrainin=16.815&solarradiation=-9999&UV=-9999&indoortempf=-9999&indoorhumidity=-9999&baromin=29.790&soilmoisture=42&soilmoisture2=40&soilmoisture3=35&soilmoisture4=31&dateutc=now&softwaretype=GW1000A_V1.7.6&action=updateraw&realtime=1&rtfreq=5
2023-07-25 17:24:15.830 - warn: sainlogic.0 (25387) Listener received illegal request: /weatherstation/updateweatherstation.php?ID=IMOERS179&PASSWORD=UNcqivm3&tempf=-9999&humidity=-9999&dewptf=-9999&windchillf=-9999&winddir=-9999&windspeedmph=-9999&windgustmph=-9999&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.445&monthlyrainin=1.535&yearlyrainin=16.815&solarradiation=-9999&UV=-9999&indoortempf=-9999&indoorhumidity=-9999&baromin=29.793&soilmoisture=42&soilmoisture2=40&soilmoisture3=35&soilmoisture4=31&dateutc=now&softwaretype=GW1000A_V1.7.6&action=updateraw&realtime=1&rtfreq=5
Ja, das WU-Protokoll geht irgendwie nicht bei der Station. Das hatte ich schonmal mit jemand. Haben wir nicht rausbekommen warum. Sorry. Könnte natürlich an noch mehr von den schrägen -9999 werten liegen. Ich kann mal was einbauen um die abzufangen.
Gut dass der Scheduler mal den Versionsstring rauskriegt. Das ist doch mal was. Er sagt doch 'Setting value from data for info.softwaretype to GW1000A_V1.7.6'
Kommt das nicht an?
Für den Listener würde ich empfehlen das '?' in ioB zu entfernen. Dann probiere mal in der Konfiguration der Station mit und ohne.
Habe weiter getestet. Ergebnis musst du vor deiner obigen Antwort einordnen.
Will dich nicht verwirren, aber ich habe auf meinem iobroker2, der dem Repo "Stable" folgt, die gleichen Einstellungen gemacht, wie beim iobroker1 mit Repo "Beta". Jeweils die IP natürlich in der App unter Customized geändert. Debug Mode bei den Adapter ist eingeschaltet. Das Feld "last_update" hat den korrekten Zeitstempel jede Minute.
Problem: Die Info-Felder werden beim iobroker1 nicht gefüllt.
iobroker2 (Stable) ok:
Beim Stable bekomme ich mit Listener Daten:
2023-07-25 17:41:38.072 - info: host.iobroker2 "system.adapter.sainlogic.0" enabled 2023-07-25 17:41:38.111 - info: host.iobroker2 instance system.adapter.sainlogic.0 started with pid 1147 2023-07-25 17:41:40.360 - info: sainlogic.0 (1147) starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.17.0, js-controller: 4.0.24 2023-07-25 17:41:40.398 - info: sainlogic.0 (1147) Starting Listener 2023-07-25 17:41:40.498 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.UVraw" has to be type "number" but received type "string" 2023-07-25 17:41:40.499 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.UVraw" has to be type "number" but received type "string" 2023-07-25 17:41:40.501 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.UVraw" has to be type "number" but received type "string" 2023-07-25 17:41:40.502 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.dailyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.504 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.dailyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.505 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.dailyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.506 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.dailyrain_piezo" has to be type "number" but received type "string" 2023-07-25 17:41:40.507 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.dewpointtemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.508 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.dewpointtemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.510 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.dewpointtemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.511 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.dewpointtemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.512 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.dewpointtemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.513 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.indoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.514 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.514 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.indoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.516 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.indoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.516 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.indoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.518 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.indoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.519 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.519 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.indoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.520 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.indoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.521 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.indoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.522 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.monthlyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.523 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.monthlyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.524 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.monthlyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.525 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.monthlyrain_piezo" has to be type "number" but received type "string" 2023-07-25 17:41:40.526 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.outdoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.527 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.527 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.528 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.529 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.outdoorhumidity" has to be type "number" but received type "string" 2023-07-25 17:41:40.530 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.outdoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.531 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.532 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.533 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.534 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.outdoortemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.535 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.pressureabs" has to be type "number" but received type "string" 2023-07-25 17:41:40.536 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressureabs" has to be type "number" but received type "string" 2023-07-25 17:41:40.536 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.pressureabs" has to be type "number" but received type "string" 2023-07-25 17:41:40.537 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.pressureabs" has to be type "number" but received type "string" 2023-07-25 17:41:40.538 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.pressureabs" has to be type "number" but received type "string" 2023-07-25 17:41:40.539 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.pressurerel" has to be type "number" but received type "string" 2023-07-25 17:41:40.540 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressurerel" has to be type "number" but received type "string" 2023-07-25 17:41:40.541 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.pressurerel" has to be type "number" but received type "string" 2023-07-25 17:41:40.542 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.pressurerel" has to be type "number" but received type "string" 2023-07-25 17:41:40.542 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.pressurerel" has to be type "number" but received type "string" 2023-07-25 17:41:40.544 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.rain" has to be type "number" but received type "string" 2023-07-25 17:41:40.544 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.rain" has to be type "number" but received type "string" 2023-07-25 17:41:40.545 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.rain_piezo" has to be type "number" but received type "string" 2023-07-25 17:41:40.546 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.solarradiation" has to be type "number" but received type "string" 2023-07-25 17:41:40.546 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.solarradiation" has to be type "number" but received type "string" 2023-07-25 17:41:40.547 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.solarradiation" has to be type "number" but received type "string" 2023-07-25 17:41:40.548 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.uvi" has to be type "number" but received type "string" 2023-07-25 17:41:40.549 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.uvi" has to be type "number" but received type "string" 2023-07-25 17:41:40.550 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.uvi" has to be type "number" but received type "string" 2023-07-25 17:41:40.551 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.weeklyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.551 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.weeklyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.552 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.weeklyrain_piezo" has to be type "number" but received type "string" 2023-07-25 17:41:40.553 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.windchilltemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.554 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.absolut.windchilltemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.554 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.minvalues.daily.windchilltemp" has to be type "number" but received type "string" 2023-07-25 17:41:40.555 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.winddir" has to be type "number" but received type "string" 2023-07-25 17:41:40.556 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.windgustspeed" has to be type "number" but received type "string" 2023-07-25 17:41:40.557 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.windgustspeed" has to be type "number" but received type "string" 2023-07-25 17:41:40.558 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.windgustspeed" has to be type "number" but received type "string" 2023-07-25 17:41:40.558 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.maxdailygust" has to be type "number" but received type "string" 2023-07-25 17:41:40.559 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.windspeed" has to be type "number" but received type "string" 2023-07-25 17:41:40.560 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.windspeed" has to be type "number" but received type "string" 2023-07-25 17:41:40.561 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.daily.windspeed" has to be type "number" but received type "string" 2023-07-25 17:41:40.562 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.yearlyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.562 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.yearlyrain" has to be type "number" but received type "string" 2023-07-25 17:41:40.563 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.totalrainin" has to be type "number" but received type "string" 2023-07-25 17:41:40.564 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.maxvalues.absolut.totalrainin" has to be type "number" but received type "string" 2023-07-25 17:41:40.565 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.yearlyrain_piezo" has to be type "number" but received type "string" 2023-07-25 17:41:40.565 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.soilmoisture" has to be type "number" but received type "string" 2023-07-25 17:41:40.566 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.info.soilbatt" has to be type "number" but received type "string" 2023-07-25 17:41:40.567 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.info.wh80batt" has to be type "number" but received type "string" 2023-07-25 17:41:40.567 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.info.wh40batt" has to be type "number" but received type "string" 2023-07-25 17:41:40.568 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.info.wh25batt" has to be type "number" but received type "string" 2023-07-25 17:41:40.569 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.tf_ch" has to be type "number" but received type "string" 2023-07-25 17:41:40.570 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.info.tf_batt" has to be type "number" but received type "string" 2023-07-25 17:41:40.570 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.tf_co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.571 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.humi_co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.572 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.pm25_co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.612 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.daily.pm25_24h_co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.612 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.pm10_co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.613 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.daily.pm10_24h_co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.614 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.co2" has to be type "number" but received type "string" 2023-07-25 17:41:40.615 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.daily.co2_24h" has to be type "number" but received type "string" 2023-07-25 17:41:40.616 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.info.co2_batt" has to be type "number" but received type "string" 2023-07-25 17:41:40.617 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.lightning_time" has to be type "number" but received type "string" 2023-07-25 17:41:40.618 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.lightning" has to be type "number" but received type "string" 2023-07-25 17:41:40.619 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.daily.lightning_num" has to be type "number" but received type "string" 2023-07-25 17:41:40.620 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.eventrain_piezo" has to be type "number" but received type "string" 2023-07-25 17:41:40.621 - info: sainlogic.0 (1147) State value to set for "sainlogic.0.weather.current.hourlyrain_piezo" has to be type "number" but received type "string"
iobroker1 (Beta) nicht ok.
023-07-25 17:50:22.973 - info: sainlogic.0 (12854) starting. Version 0.10.5 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.17.0, js-controller: 5.0.8 2023-07-25 17:50:23.024 - debug: sainlogic.0 (12854) Listener IP: 192.168.178.41 2023-07-25 17:50:23.025 - debug: sainlogic.0 (12854) Listener port: 45000 2023-07-25 17:50:23.026 - debug: sainlogic.0 (12854) Listener path: / 2023-07-25 17:50:23.027 - debug: sainlogic.0 (12854) Listener protocol: ecowitt 2023-07-25 17:50:23.028 - debug: sainlogic.0 (12854) Forward URL: 2023-07-25 17:50:23.030 - info: sainlogic.0 (12854) Starting Listener 2023-07-25 17:50:41.919 - debug: sainlogic.0 (12854) Listener body is PASSKEY=0142670A6020B1CD65C1B1E0504B3301&stationtype=GW1000A_V1.7.6&runtime=431406&dateutc=2023-07-25+15:50:41&baromrelin=29.796&baromabsin=29.624&rainratein=0.000&eventrainin=0.441&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.445&monthlyrainin=1.535&yearlyrainin=16.815&totalrainin=16.815&soilmoisture1=42&soilmoisture2=40&soilmoisture3=35&soilmoisture4=31&lightning_num=7&lightning=17&lightning_time=1690275265&soilbatt1=1.6&soilbatt2=1.6&soilbatt3=1.6&soilbatt4=1.6&wh57batt=5&freq=868M&model=GW1000A_Pro 2023-07-25 17:50:41.921 - debug: sainlogic.0 (12854) Listener received EW update: {"PASSKEY":"0142670A6020B1CD65C1B1E0504B3301","stationtype":"GW1000A_V1.7.6","runtime":"431406","dateutc":"2023-07-25 15:50:41","baromrelin":"29.796","baromabsin":"29.624","rainratein":"0.000","eventrainin":"0.441","hourlyrainin":"0.000","dailyrainin":"0.000","weeklyrainin":"0.445","monthlyrainin":"1.535","yearlyrainin":"16.815","totalrainin":"16.815","soilmoisture1":"42","soilmoisture2":"40","soilmoisture3":"35","soilmoisture4":"31","lightning_num":"7","lightning":"17","lightning_time":"1690275265","soilbatt1":"1.6","soilbatt2":"1.6","soilbatt3":"1.6","soilbatt4":"1.6","wh57batt":"5","freq":"868M","model":"GW1000A_Pro"} 2023-07-25 17:50:41.930 - debug: sainlogic.0 (12854) No mapping found for dataelement: PASSKEY 2023-07-25 17:50:41.934 - debug: sainlogic.0 (12854) Extracting value for info.softwaretype(stationtype) 2023-07-25 17:50:41.935 - debug: sainlogic.0 (12854) No mapping found for dataelement: runtime 2023-07-25 17:50:41.936 - debug: sainlogic.0 (12854) No mapping found for dataelement: dateutc 2023-07-25 17:50:41.936 - debug: sainlogic.0 (12854) Extracting value for weather.current.pressurerel(baromrelin) 2023-07-25 17:50:41.946 - debug: sainlogic.0 (12854) Extracting value for weather.current.pressureabs(baromabsin) 2023-07-25 17:50:41.948 - debug: sainlogic.0 (12854) Extracting value for weather.current.rain(rainratein) 2023-07-25 17:50:41.950 - debug: sainlogic.0 (12854) No mapping found for dataelement: eventrainin 2023-07-25 17:50:41.950 - debug: sainlogic.0 (12854) No mapping found for dataelement: hourlyrainin 2023-07-25 17:50:41.951 - debug: sainlogic.0 (12854) Extracting value for weather.current.dailyrain(dailyrainin) 2023-07-25 17:50:41.952 - debug: sainlogic.0 (12854) Extracting value for weather.current.weeklyrain(weeklyrainin) 2023-07-25 17:50:41.954 - debug: sainlogic.0 (12854) Extracting value for weather.current.monthlyrain(monthlyrainin) 2023-07-25 17:50:41.955 - debug: sainlogic.0 (12854) Extracting value for weather.current.yearlyrain(yearlyrainin) 2023-07-25 17:50:41.956 - debug: sainlogic.0 (12854) Extracting value for weather.current.totalrainin(totalrainin) 2023-07-25 17:50:41.957 - debug: sainlogic.0 (12854) Extracting value for weather.current.1.soilmoisture(soilmoisture1) 2023-07-25 17:50:41.958 - debug: sainlogic.0 (12854) Extracting value for weather.current.2.soilmoisture(soilmoisture2) 2023-07-25 17:50:41.959 - debug: sainlogic.0 (12854) Extracting value for weather.current.3.soilmoisture(soilmoisture3) 2023-07-25 17:50:41.959 - debug: sainlogic.0 (12854) Extracting value for weather.current.4.soilmoisture(soilmoisture4) 2023-07-25 17:50:41.960 - debug: sainlogic.0 (12854) Extracting value for weather.daily.lightning_num(lightning_num) 2023-07-25 17:50:41.960 - debug: sainlogic.0 (12854) Extracting value for weather.current.lightning(lightning) 2023-07-25 17:50:41.961 - debug: sainlogic.0 (12854) Extracting value for weather.current.lightning_time(lightning_time) 2023-07-25 17:50:41.961 - debug: sainlogic.0 (12854) Extracting value for weather.info.1.soilbatt(soilbatt1) 2023-07-25 17:50:41.962 - debug: sainlogic.0 (12854) Extracting value for weather.info.2.soilbatt(soilbatt2) 2023-07-25 17:50:41.962 - debug: sainlogic.0 (12854) Extracting value for weather.info.3.soilbatt(soilbatt3) 2023-07-25 17:50:41.963 - debug: sainlogic.0 (12854) Extracting value for weather.info.4.soilbatt(soilbatt4) 2023-07-25 17:50:41.963 - debug: sainlogic.0 (12854) No mapping found for dataelement: wh57batt 2023-07-25 17:50:41.964 - debug: sainlogic.0 (12854) Extracting value for info.freq(freq) 2023-07-25 17:50:41.964 - debug: sainlogic.0 (12854) Extracting value for info.model(model) 2023-07-25 17:50:41.965 - debug: sainlogic.0 (12854) Extracting value for info.last_listener_update(last_listener_update) 2023-07-25 17:50:41.966 - debug: sainlogic.0 (12854) Setting value from data for info.softwaretype to GW1000A_V1.7.6 2023-07-25 17:50:41.967 - debug: sainlogic.0 (12854) Setting value from data for weather.current.pressurerel to 1008.9 2023-07-25 17:50:41.968 - debug: sainlogic.0 (12854) Target for pressurerel unit is set: hPa, using conversion: null 2023-07-25 17:50:41.968 - debug: sainlogic.0 (12854) Setting value from data for weather.current.pressureabs to 1003.1 2023-07-25 17:50:41.969 - debug: sainlogic.0 (12854) Target for pressureabs unit is set: hPa, using conversion: null 2023-07-25 17:50:41.969 - debug: sainlogic.0 (12854) Setting value from data for weather.current.rain to 0 2023-07-25 17:50:41.970 - debug: sainlogic.0 (12854) Target for rain unit is set: mm, using conversion: null 2023-07-25 17:50:41.970 - debug: sainlogic.0 (12854) Setting value from data for weather.current.dailyrain to 0 2023-07-25 17:50:41.970 - debug: sainlogic.0 (12854) Target for dailyrain unit is set: mm, using conversion: null 2023-07-25 17:50:41.971 - debug: sainlogic.0 (12854) Setting value from data for weather.current.weeklyrain to 11.3 2023-07-25 17:50:41.971 - debug: sainlogic.0 (12854) Target for weeklyrain unit is set: mm, using conversion: null 2023-07-25 17:50:41.972 - debug: sainlogic.0 (12854) Setting value from data for weather.current.monthlyrain to 39 2023-07-25 17:50:41.972 - debug: sainlogic.0 (12854) Target for monthlyrain unit is set: mm, using conversion: null 2023-07-25 17:50:41.972 - debug: sainlogic.0 (12854) Setting value from data for weather.current.yearlyrain to 427.1 2023-07-25 17:50:41.973 - debug: sainlogic.0 (12854) Target for yearlyrain unit is set: mm, using conversion: null 2023-07-25 17:50:41.974 - debug: sainlogic.0 (12854) Setting value from data for weather.current.totalrainin to 427.1 2023-07-25 17:50:41.974 - debug: sainlogic.0 (12854) Target for totalrainin unit is set: mm, using conversion: null 2023-07-25 17:50:41.975 - debug: sainlogic.0 (12854) Setting value from data for weather.current.1.soilmoisture to 42 2023-07-25 17:50:41.975 - debug: sainlogic.0 (12854) Setting value from data for weather.current.2.soilmoisture to 40 2023-07-25 17:50:41.975 - debug: sainlogic.0 (12854) Setting value from data for weather.current.3.soilmoisture to 35 2023-07-25 17:50:41.976 - debug: sainlogic.0 (12854) Setting value from data for weather.current.4.soilmoisture to 31 2023-07-25 17:50:41.976 - debug: sainlogic.0 (12854) Setting value from data for weather.daily.lightning_num to 7 2023-07-25 17:50:41.977 - debug: sainlogic.0 (12854) Setting value from data for weather.current.lightning to 17 2023-07-25 17:50:41.977 - debug: sainlogic.0 (12854) Setting value from data for weather.current.lightning_time to 1690275265 2023-07-25 17:50:41.977 - debug: sainlogic.0 (12854) Setting value from data for weather.info.1.soilbatt to 1.6 2023-07-25 17:50:41.978 - debug: sainlogic.0 (12854) Setting value from data for weather.info.2.soilbatt to 1.6 2023-07-25 17:50:41.978 - debug: sainlogic.0 (12854) Setting value from data for weather.info.3.soilbatt to 1.6 2023-07-25 17:50:41.978 - debug: sainlogic.0 (12854) Setting value from data for weather.info.4.soilbatt to 1.6 2023-07-25 17:50:41.979 - debug: sainlogic.0 (12854) Setting value from data for info.freq to 868M 2023-07-25 17:50:41.979 - debug: sainlogic.0 (12854) Setting value from data for info.model to GW1000A_Pro 2023-07-25 17:50:41.979 - debug: sainlogic.0 (12854) Setting value from data for info.last_listener_update to {"PASSKEY":"0142670A6020B1CD65C1B1E0504B3301","stationtype":"GW1000A_V1.7.6","runtime":"431406","dateutc":"2023-07-25 15:50:41","baromrelin":"29.796","baromabsin":"29.624","rainratein":"0.000","eventrainin":"0.441","hourlyrainin":"0.000","dailyrainin":"0.000","weeklyrainin":"0.445","monthlyrainin":"1.535","yearlyrainin":"16.815","totalrainin":"16.815","soilmoisture1":"42","soilmoisture2":"40","soilmoisture3":"35","soilmoisture4":"31","lightning_num":"7","lightning":"17","lightning_time":"1690275265","soilbatt1":"1.6","soilbatt2":"1.6","soilbatt3":"1.6","soilbatt4":"1.6","wh57batt":"5","freq":"868M","model":"GW1000A_Pro"}
Ja, das WU-Protokoll geht irgendwie nicht bei der Station. Das hatte ich schonmal mit jemand. Haben wir nicht rausbekommen warum. Sorry. Könnte natürlich an noch mehr von den schrägen -9999 werten liegen. Ich kann mal was einbauen um die abzufangen.
Die schrägen Werte liegen ggf. daran, dass das Hypersonic-Aerometer momentan wegen Defekt nicht online ist, aber definiert ist.
Gut dass der Scheduler mal den Versionsstring rauskriegt. Das ist doch mal was. Er sagt doch 'Setting value from data for info.softwaretype to GW1000A_V1.7.6'
Kommt das nicht an?
Schrieb oben schon: Wird aber nicht in Objekte/Model angezeigt/übernommen. Getestet mit iobroker1 (Beta)
Für den Listener würde ich empfehlen das '?' in ioB zu entfernen. Dann probiere mal in der Konfiguration der Station mit und ohne.
Habe den Pfad auf "/weatherstation/updateweatherstation.php" und Protokoll "Wunderground" gesetzt:
Listener received illegal request: /weatherstation/updateweatherstation.phpID=IMOERS179&PASSWORD=UNcqivm3&tempf=-9999&humidity=-9999&dewptf=-9999&windchillf=-9999&winddir=-9999&windspeedmph=-9999&windgustmph=-9999&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.445&monthlyrainin=1.535&yearlyrainin=16.815&solarradiation=-9999&UV=-9999&indoortempf=-9999&indoorhumidity=-9999&baromin=29.802&soilmoisture=42&soilmoisture2=39&soilmoisture3=35&soilmoisture4=31&dateutc=now&softwaretype=GW1000A_V1.7.6&action=updateraw&realtime=1&rtfreq=5
Ist die Dokumentation hier vielleicht hilfreich: https://github.com/merbanan/rtl_433/blob/master/src/devices/fineoffset_wh1050.c Fine Offset ist der Original-Hersteller der von vielen Händlern (Ecowitt, Froggit....) vertrieben wird. Siehe auch: https://github.com/merbanan/rtl_433/blob/master/src/devices/ecowitt.c
Das Repo ist mal super spannend, der hat ja für einige Stationen was gefunden. Muss ich mir genauer anschauen.
Mit deinen beiden IOB's hast mich etwas verwirrt. Versteh ich richtig, der stable (2) geht alles, mit dem (1) nicht? Und was ist bei 1 nun installiert?
Mit deinen beiden IOB's hast mich etwas verwirrt.
Das hatte ich ja angekündigt :-)
Versteh ich richtig, der stable (2) geht alles, mit dem (1) nicht? Und was ist bei 1 nun installiert?
Also: Beide iob1 & 2 nutzen den Listener um an die Daten zu kommen. Es geht nur um die Info-Felder. iob2 (stable) füllt es korrekt. iob1 (beta) bekommt laut Log auch die Daten: Setting value from data for info.last_listener_update to {"PASSKEY":"0142670A6020B1CD65C1B1E0504B3301","stationtype":"GW1000A_V1.7.6","runtime":"511743","dateutc":"2023-07-26 14:09:41","baromrelin":"29.935","baromabsin":"29.763","rainratein":"0.000","eventrainin":"0.118","hourlyrainin":"0.000","dailyrainin":"0.118","weeklyrainin":"0.563","monthlyrainin":"1.654","yearlyrainin":"16.933","totalrainin":"16.933","soilmoisture1":"40","soilmoisture2":"36","soilmoisture3":"39","soilmoisture4":"29","lightning_num":"17","lightning":"24","lightning_time":"1690366913","soilbatt1":"1.6","soilbatt2":"1.6","soilbatt3":"1.6","soilbatt4":"1.6","wh57batt":"5","freq":"868M","model":"GW1000A_Pro"}
sind aber nicht in den Info-Felder (Freq., Model, Softwaretype) unter Objekte zu sehen.
Und was ist bei 1 nun installiert?
Welche Versionen benutzt werden steht doch im Log: iob1: 2023-07-25 17:50:22.973 - info: sainlogic.0 (12854) starting. Version 0.10.5 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.17.0, js-controller: 5.0.8
iob2: 2023-07-25 17:41:40.360 - info: sainlogic.0 (1147) starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.17.0, js-controller: 4.0.24
iob1: Admin 6.6.1 NPM 9.6.7
iob2: Admin 6.3.5 NPM 9.6.7
Schreib, was du sonst noch brauchst.
Kennst du übrigens diese Seite: https://github.com/SBorg2014/WLAN-Wetterstation
Man kann im WSview/Custom ja nur einen Adressaten für die Wetterdaten einrichten. Eine Lösung dafür ist hier: https://loxwiki.atlassian.net/wiki/spaces/LOXBERRY/pages/1240959272/FOSHKplugin
Ja, das SBorg Ding kenne ich, ist ja quasi 'nur' der Listenerteil aus meinem Adapter - oder umgekehrt. Wie Du magst, das Skript gab es zuerst.
Einen Forwarder habe ich auch drin, wobei ich 'einfach' die Daten genau gleich wie ich sie krieg weiterreiche.
Das foshkplugin ist da aber bei den Weiterleitungen nicht begrenzt. Man kann also:
Ah.. die Anforderung hat noch niemand gebracht :D Das wäre jetzt nicht sooo kompliziert umzusetzen.
Ist ja kein K.O Kriterium. Nicht jeder will ja seine Wetterdaten auf mehreren Geräten verteilen. Wenn du das richtig machen wolltest, müsste dein Adapter eine weitere Registrierkarte anbieten, wo man mit Hinzufügen von Zeilen die einzelnen Weiterleitungen definieren könnte. So was wie hier:
Vor der Inst. deines Adapters hatte ich im WSview dazu das eingetragen:
wo "Private Weather Tablet" läuft. Wie müsste ich bei dir das Weiterleitungsfeld bestücken?
Dann müsstest du einfach als weiterleitungs-URL das hier eintragen:
Das müsste reichen.
Ok, danke für die Hilfe
Hallo, nutze deinen Adapter mit einer DP1500 Wetterstation in folgernder Umgebung: admin: 6.6.1 Node.js: v18.16.1 NPM: v9.5.1 js-controller: 5.0.8
Nachdem der Adapter gestartet wurde, kommt obige Meldung nach "Scheduler connected to weather station":
2023-07-24 21:58:29.198 - info: sainlogic.0 (5416) starting. Version 0.10.5 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.16.1, js-controller: 5.0.8 2023-07-24 21:58:29.243 - info: sainlogic.0 (5416) Starting Scheduler 2023-07-24 21:58:29.245 - info: sainlogic.0 (5416) Scheduler call ws_getfirmware activated 2023-07-24 21:58:29.246 - info: sainlogic.0 (5416) Scheduler call ws_getcurrent activated 2023-07-24 21:58:29.247 - debug: sainlogic.0 (5416) Weatherstation IP: 192.168.178.45 2023-07-24 21:58:29.248 - debug: sainlogic.0 (5416) Weatherstation port: 45000 2023-07-24 21:58:29.249 - debug: sainlogic.0 (5416) Scheduler Interval: 5 2023-07-24 21:58:29.250 - debug: sainlogic.0 (5416) Listener IP: 192.168.178.41 2023-07-24 21:58:29.251 - debug: sainlogic.0 (5416) Listener port: 45000 2023-07-24 21:58:29.251 - debug: sainlogic.0 (5416) Listener path: /weatherstation/updateweatherstation.php 2023-07-24 21:58:29.252 - debug: sainlogic.0 (5416) Listener protocol: ecowitt 2023-07-24 21:58:29.253 - debug: sainlogic.0 (5416) Forward URL: 2023-07-24 21:58:29.254 - info: sainlogic.0 (5416) Starting Listener 2023-07-24 21:58:34.250 - info: sainlogic.0 (5416) Scheduler pulling for new data 2023-07-24 21:58:34.420 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,80,3,83 2023-07-24 21:58:34.435 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf 2023-07-24 21:58:34.438 - debug: sainlogic.0 (5416) Data Command received: 80 subcommand 71 2023-07-24 21:58:34.439 - error: sainlogic.0 (5416) Scheduler received data for unkown command 80 subcommand 71 2023-07-24 21:58:34.439 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,11,0,6,4,4,25 2023-07-24 21:58:34.448 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff5b040261 2023-07-24 21:58:34.449 - debug: sainlogic.0 (5416) Data Command received: 91 subcommand 97 2023-07-24 21:58:34.449 - error: sainlogic.0 (5416) Scheduler received data for unkown command 91 subcommand 97 2023-07-24 21:58:34.451 - debug: sainlogic.0 (5416) FW Scheduler Connection closed 2023-07-24 21:58:39.251 - info: sainlogic.0 (5416) Scheduler pulling for new data 2023-07-24 21:58:39.257 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,80,3,83 2023-07-24 21:58:39.274 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf 2023-07-24 21:58:39.274 - debug: sainlogic.0 (5416) Data Command received: 80 subcommand 71 2023-07-24 21:58:39.275 - error: sainlogic.0 (5416) Scheduler received data for unkown command 80 subcommand 71 2023-07-24 21:58:39.275 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,11,0,6,4,4,25 2023-07-24 21:58:39.284 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff5b040261 2023-07-24 21:58:39.285 - debug: sainlogic.0 (5416) Data Command received: 91 subcommand 97 2023-07-24 21:58:39.286 - error: sainlogic.0 (5416) Scheduler received data for unkown command 91 subcommand 97 2023-07-24 21:58:39.289 - debug: sainlogic.0 (5416) FW Scheduler Connection closed 2023-07-24 21:58:44.251 - info: sainlogic.0 (5416) Scheduler pulling for new data 2023-07-24 21:58:44.257 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,80,3,83 2023-07-24 21:58:44.274 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf 2023-07-24 21:58:44.275 - debug: sainlogic.0 (5416) Data Command received: 80 subcommand 71 2023-07-24 21:58:44.275 - error: sainlogic.0 (5416) Scheduler received data for unkown command 80 subcommand 71 2023-07-24 21:58:44.276 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,11,0,6,4,4,25 2023-07-24 21:58:44.285 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff5b040261 2023-07-24 21:58:44.286 - debug: sainlogic.0 (5416) Data Command received: 91 subcommand 97 2023-07-24 21:58:44.286 - error: sainlogic.0 (5416) Scheduler received data for unkown command 91 subcommand 97 2023-07-24 21:58:44.289 - debug: sainlogic.0 (5416) FW Scheduler Connection closed 2023-07-24 21:58:49.251 - info: sainlogic.0 (5416) Scheduler pulling for new data 2023-07-24 21:58:49.264 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,80,3,83 2023-07-24 21:58:49.284 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf 2023-07-24 21:58:49.285 - debug: sainlogic.0 (5416) Data Command received: 80 subcommand 71 2023-07-24 21:58:49.285 - error: sainlogic.0 (5416) Scheduler received data for unkown command 80 subcommand 71 2023-07-24 21:58:49.286 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,11,0,6,4,4,25 2023-07-24 21:58:49.295 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff5b040261 2023-07-24 21:58:49.296 - debug: sainlogic.0 (5416) Data Command received: 91 subcommand 97 2023-07-24 21:58:49.296 - error: sainlogic.0 (5416) Scheduler received data for unkown command 91 subcommand 97 2023-07-24 21:58:49.299 - debug: sainlogic.0 (5416) FW Scheduler Connection closed 2023-07-24 21:58:54.251 - info: sainlogic.0 (5416) Scheduler pulling for new data 2023-07-24 21:58:54.257 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,80,3,83 2023-07-24 21:58:54.274 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff50120e475731303030415f56312e372e36bf 2023-07-24 21:58:54.275 - debug: sainlogic.0 (5416) Data Command received: 80 subcommand 71 2023-07-24 21:58:54.275 - error: sainlogic.0 (5416) Scheduler received data for unkown command 80 subcommand 71 2023-07-24 21:58:54.276 - debug: sainlogic.0 (5416) Scheduler connected to weather station run 255,255,11,0,6,4,4,25 2023-07-24 21:58:54.286 - debug: sainlogic.0 (5416) FW Scheduler Received data string: ffff5b040261 2023-07-24 21:58:54.287 - debug: sainlogic.0 (5416) Data Command received: 91 subcommand 97 2023-07-24 21:58:54.288 - error: sainlogic.0 (5416) Scheduler received data for unkown command 91 subcommand 97 2023-07-24 21:58:54.290 - debug: sainlogic.0 (5416) FW Scheduler Connection closed 2023-07-24 21:58:54.958 - info: host.iobroker "system.adapter.sainlogic.0" disabled 2023-07-24 21:58:54.960 - info: host.iobroker stopInstance system.adapter.sainlogic.0 (force=false, process=true) 2023-07-24 21:58:54.974 - info: sainlogic.0 (5416) Got terminate signal TERMINATE_YOURSELF 2023-07-24 21:58:54.976 - info: sainlogic.0 (5416) Sainlogic Adapter gracefully shut down... 2023-07-24 21:58:54.977 - info: sainlogic.0 (5416) terminating 2023-07-24 21:58:54.978 - info: sainlogic.0 (5416) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-07-24 21:58:54.979 - info: sainlogic.0 (5416) Listener closed. 2023-07-24 21:58:55.235 - info: host.iobroker stopInstance system.adapter.sainlogic.0 send kill signal 2023-07-24 21:58:55.480 - info: sainlogic.0 (5416) terminating 2023-07-24 21:58:55.713 - info: host.iobroker instance system.adapter.sainlogic.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
Daten werden in der WSView-Plus App angezeigt. Hab ich irgendwo was verbastelt?