NEWS
IoBroker - Neustart, Javascript keine Funktion
ioBroker Allgemein
22
Beiträge
2
Kommentatoren
1.6k
Aufrufe
2
Watching
-
@paul53 kannte ich so auch noch nicht, das Script startet und aufgrund der Fehler im Script kommt ein gelbes Pause Zeichen.
Hier der neue LOG:20:29:39.540 info javascript.1 Stop script script.js.Allgemein.Servicemeldungen 20:29:43.034 info javascript.1 Start javascript script.js.Allgemein.Servicemeldungen 20:29:43.034 info javascript.1 script.js.Allgemein.Servicemeldungen: hm-rpc.0.MEQ0214836.0.UNREACH: Badezimmer Fenster:0.UNREACH 20:29:43.034 info javascript.1 script.js.Allgemein.Servicemeldungen: iqontrol.0.Views.Tanel.0000__Tanel Licht.UNREACH: UNREACH 20:29:43.034 error javascript.1 script.js.Allgemein.Servicemeldungen: script.js.Allgemein.Servicemeldungen:50 20:29:43.034 error javascript.1 at count (script.js.Allgemein.Servicemeldungen:50:31) 20:29:43.034 error javascript.1 at script.js.Allgemein.Servicemeldungen:57:9 20:29:43.034 error javascript.1 at countService (script.js.Allgemein.Servicemeldungen:56:21) 20:29:43.034 error javascript.1 at script.js.Allgemein.Servicemeldungen:111:1ioBroker im Docker auf Qnap TS-453A 16GB Ram 4-Bay
-
@paul53 kannte ich so auch noch nicht, das Script startet und aufgrund der Fehler im Script kommt ein gelbes Pause Zeichen.
Hier der neue LOG:20:29:39.540 info javascript.1 Stop script script.js.Allgemein.Servicemeldungen 20:29:43.034 info javascript.1 Start javascript script.js.Allgemein.Servicemeldungen 20:29:43.034 info javascript.1 script.js.Allgemein.Servicemeldungen: hm-rpc.0.MEQ0214836.0.UNREACH: Badezimmer Fenster:0.UNREACH 20:29:43.034 info javascript.1 script.js.Allgemein.Servicemeldungen: iqontrol.0.Views.Tanel.0000__Tanel Licht.UNREACH: UNREACH 20:29:43.034 error javascript.1 script.js.Allgemein.Servicemeldungen: script.js.Allgemein.Servicemeldungen:50 20:29:43.034 error javascript.1 at count (script.js.Allgemein.Servicemeldungen:50:31) 20:29:43.034 error javascript.1 at script.js.Allgemein.Servicemeldungen:57:9 20:29:43.034 error javascript.1 at countService (script.js.Allgemein.Servicemeldungen:56:21) 20:29:43.034 error javascript.1 at script.js.Allgemein.Servicemeldungen:111:1 -
@mike2712: Dieser Datenpunkt erzeugt den Fehler:
iqontrol.0.Views.Tanel.0000__Tanel Licht.UNREACH
Ändere den UNREACH-Selektor (s.u.).
-
@paul53 Das sind die Datenpunkte aus Qontrol, richtig ?
die sind aber an jedem Qontrol so angebunden, warum macht nur der eine Fehler, wo kann ich den ändern?
-
@paul53 Das sind die Datenpunkte aus Qontrol, richtig ?
die sind aber an jedem Qontrol so angebunden, warum macht nur der eine Fehler, wo kann ich den ändern?
-
@paul53 Jetzt habe ich den rausgelöscht, wie vermutet kommt jetzt der nächste, nicht Licht, sondern Jalousie.
20:42:07.108 info javascript.1 Stop script script.js.Allgemein.Servicemeldungen 20:42:11.398 info javascript.1 Start javascript script.js.Allgemein.Servicemeldungen 20:42:11.398 info javascript.1 script.js.Allgemein.Servicemeldungen: hm-rpc.0.MEQ0214836.0.UNREACH: Badezimmer Fenster:0.UNREACH 20:42:11.398 info javascript.1 script.js.Allgemein.Servicemeldungen: iqontrol.0.Views.Tanel.0001__Tanel Jalousie.UNREACH: UNREACH 20:42:11.413 error javascript.1 script.js.Allgemein.Servicemeldungen: script.js.Allgemein.Servicemeldungen:50 20:42:11.413 error javascript.1 at count (script.js.Allgemein.Servicemeldungen:50:31) 20:42:11.413 error javascript.1 at script.js.Allgemein.Servicemeldungen:57:9 20:42:11.413 error javascript.1 at countService (script.js.Allgemein.Servicemeldungen:56:21) 20:42:11.413 error javascript.1 at script.js.Allgemein.Servicemeldungen:111:1Sorry iQontrol
https://forum.iobroker.net/topic/22039/neuer-adapter-visualisierung-iqontrol -
@mike2712 sagte:
wo kann ich den ändern?
Du solltest die Selektoren ändern:
var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');@paul53
Da habe ich was falsch verstanden? Habe den hier bei unreach den Wert rausgenommen.
Das Script kommt doch sogar von Dir, ist mein Script noch aktuell, ich kann leider nichts anderes finden.
ioBroker im Docker auf Qnap TS-453A 16GB Ram 4-Bay
-
@paul53
Da habe ich was falsch verstanden? Habe den hier bei unreach den Wert rausgenommen.Das Script kommt doch sogar von Dir, ist mein Script noch aktuell, ich kann leider nichts anderes finden.
@mike2712 sagte:
Das Script kommt doch sogar von Dir
Das ist eines meiner ersten Skripte gewesen. Damals gab es noch kein iQontrol. Nur HomeMatic hatte Datenpunkte mit UNREACH am Ende. Deshalb erweitere den Selektor um hm-rpc. vor dem Sternchen:
var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]'); -
@mike2712 sagte:
Das Script kommt doch sogar von Dir
Das ist eines meiner ersten Skripte gewesen. Damals gab es noch kein iQontrol. Nur HomeMatic hatte Datenpunkte mit UNREACH am Ende. Deshalb erweitere den Selektor um hm-rpc. vor dem Sternchen:
var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');@paul53 ok, ist das weiter entwickelt worden, scheinbar nicht, schade finde das sehr gut und nützlich.
Was genau muss ich den in dieser Zeile ändern ?
var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');
Ich kann leider kein Java, dann würden die Homematic Unreach auch nicht mehr funktionieren? Das wäre auch blöd.
ioBroker im Docker auf Qnap TS-453A 16GB Ram 4-Bay
-
@paul53 ok, ist das weiter entwickelt worden, scheinbar nicht, schade finde das sehr gut und nützlich.
Was genau muss ich den in dieser Zeile ändern ?
var SelectorUNREACH = $('channel[state.id=hm-rpc.*.UNREACH]');
Ich kann leider kein Java, dann würden die Homematic Unreach auch nicht mehr funktionieren? Das wäre auch blöd.
-
@mike2712 sagte:
dann würden die Homematic Unreach auch nicht mehr funktionieren?
Der Zusatz hm-rpc. begrenzt die Gültigkeit auf HomeMatic.
@paul53 super, vielen Dank, das läuft jetzt ohne Probleme durch.
Aber nochmal, kann das meine Probleme verursacht haben da dieses Script ja auf Pause stand?
Obwohl was dafür spricht, ist ja das ich das Gefühl hatte das es mit testen von iQontrol zusammenhängt. Aber verstehe es nicht, da das Script ja pausiert. Was passiert den durch diesen Fehler, die wichtigen Funktionen waren ja eigentlich im Javascript 0.ioBroker im Docker auf Qnap TS-453A 16GB Ram 4-Bay
-
@paul53 super, vielen Dank, das läuft jetzt ohne Probleme durch.
Aber nochmal, kann das meine Probleme verursacht haben da dieses Script ja auf Pause stand?
Obwohl was dafür spricht, ist ja das ich das Gefühl hatte das es mit testen von iQontrol zusammenhängt. Aber verstehe es nicht, da das Script ja pausiert. Was passiert den durch diesen Fehler, die wichtigen Funktionen waren ja eigentlich im Javascript 0. -
@mike2712 sagte:
kann das meine Probleme verursacht haben da dieses Script ja auf Pause stand?
Wirklich ? Wenn das Skript nicht aktiviert ist, kann es auch keine Logeinträge erzeugen.
-
Ich habe weiterhin Probleme das Javascript mit der Instanz 0 nicht ausgeführt wird, ich habe weiterhin sehr viele Warnungen und Fehler im LOG.
Wie kann ich den den Fehler finden, Fehlermeldungen zum Javascript fallen mir nicht auf.
Das System läuft total instabil.Javascript scheint einfach nicht zu laufen, obwohl im Adapter alles grün ist, die Funktionen funktionieren nach einem Neustart ohne Probleme, wie kann ich den Fehler eingrenzen?
2019-05-26 00:00:00.156 - warn: javascript.0 Cannot calculate "night" for 52.133751464629825, 7.540483474731443 2019-05-26 00:00:01.186 - warn: javascript.0 Cannot calculate "nightEnd" for 52.133751464629825, 7.540483474731443 2019-05-26 00:10:20.881 - warn: sonoff.0 Old client Sonoff-Steckdose-14 with secret 1558822182333_9671 sends publish. Ignore! Actual secret is 1558822217589_8185 2019-05-26 00:10:20.881 - warn: sonoff.0 Old client Sonoff-Steckdose-14 with secret 1558822182333_9671 sends pingreq. Ignore! Actual secret is 1558822217589_8185 2019-05-26 00:10:24.750 - warn: sonoff.0 Old client Sonoff-Steckdose-17 with secret 1558822048485_8304 sends pingreq. Ignore! Actual secret is 1558822213034_9291 2019-05-26 01:01:35.126 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:01:35.126 - error: fritzdect.0 no response part in returned message 2019-05-26 01:01:42.895 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:01:42.895 - error: fritzdect.0 no response part in returned message 2019-05-26 01:01:42.895 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:01:42.895 - error: fritzdect.0 no response part in returned message 2019-05-26 01:01:52.894 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:01:52.894 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:00.023 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:02:00.023 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:02.893 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:02.893 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:02.893 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:02.893 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:12.721 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:12.721 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:12.721 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:12.721 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:22.923 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:22.923 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:22.923 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:22.923 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:32.782 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:32.782 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:32.923 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:32.923 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:42.782 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:42.782 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:42.782 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:42.782 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:49.833 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:02:49.833 - error: fritzdect.0 no response part in returned message 2019-05-26 01:02:52.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:02:52.922 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:02.781 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:02.781 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:02.781 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:02.781 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:09.693 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:03:09.693 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:12.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:12.922 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:12.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:12.922 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:19.693 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:03:19.693 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:22.781 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:22.781 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:32.984 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:32.984 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:39.988 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:03:39.988 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:42.983 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:42.983 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:42.983 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:42.983 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:52.921 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:52.921 - error: fritzdect.0 no response part in returned message 2019-05-26 01:03:52.921 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:03:52.921 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:02.889 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:02.889 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:02.983 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:02.983 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:09.924 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:09.924 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:09.924 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:04:09.924 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:12.919 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:12.919 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:20.032 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:04:20.032 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:22.778 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:22.778 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:30.032 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:04:30.032 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:32.934 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:32.934 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:42.980 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:42.980 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:50.328 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:04:50.328 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:52.980 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:52.980 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:52.980 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:04:52.980 - error: fritzdect.0 no response part in returned message 2019-05-26 01:04:59.922 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:04:59.922 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:02.839 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:05:02.839 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:02.839 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:05:02.839 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:10.031 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:05:10.031 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:12.824 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:05:12.824 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:12.824 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:05:12.824 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:20.125 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:05:20.125 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:22.823 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:05:22.823 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:22.823 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/webservices/homeautoswitch.lua?0=0&sid=e5d517fc26e675b2&switchcmd=getdevicelistinfos"}} 2019-05-26 01:05:22.823 - error: fritzdect.0 no response part in returned message 2019-05-26 01:05:30.031 - error: fritzdect.0 fritzbox returned this {"error":{"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"},"options":{"url":"http://172.16.10.10/wlan/guest_access.lua?0=0&sid=e5d517fc26e675b2"}} 2019-05-26 01:05:30.031 - error: fritzdect.0 no response part in returned message 2019-05-26 01:30:46.927 - info: javascript.0 script.js.Steckdosen.PV-Leistung: 209 2019-05-26 01:31:46.768 - error: cloud.0 Socket error: Error: websocket error 2019-05-26 01:31:46.768 - info: cloud.0 Connection changed: transport error 2019-05-26 01:31:46.768 - info: cloud.0 Connection lost 2019-05-26 01:31:57.346 - error: host.Home-ioBroker instance system.adapter.cloud.0 terminated with code 4294967196 () 2019-05-26 01:31:57.346 - info: host.Home-ioBroker Restart adapter system.adapter.cloud.0 because enabled 2019-05-26 01:31:58.375 - info: host.Home-ioBroker instance system.adapter.cloud.0 started with pid 20996 2019-05-26 01:32:18.187 - info: alexa2.0 Alexa-Push-Connection disconnected - retry: Retry Connection in 5s 2019-05-26 01:32:23.132 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2019-05-26 01:32:23.132 - warn: alexa2.0 Device-type:AKPGW064GI9HE (MICROPHONE,PERSISTENT_CONNECTION,FLASH_BRIEFING,ACTIVE_AFTER_FRO,CHANGE_NAME,VOLUME_SETTING,SUPPORTS_SOFTWARE_VERSION,ARTHUR_TARGET,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,ALLOW_LOG_UPLOAD) 2019-05-26 01:32:24.973 - info: alexa2.0 Alexa-Push-Connection established. Disable Polling 2019-05-26 01:32:28.686 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2019-05-26 01:32:28.686 - warn: alexa2.0 Device-type:AKPGW064GI9HE (MICROPHONE,FLASH_BRIEFING,ARTHUR_TARGET,ACTIVE_AFTER_FRO,SUPPORTS_SOFTWARE_VERSION,VOLUME_SETTING,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,CHANGE_NAME,PERSISTENT_CONNECTION,ALLOW_LOG_UPLOAD) 2019-05-26 01:32:53.147 - info: cloud.0 starting. Version 2.6.2 in C:/iobroker/node_modules/iobroker.cloud, node: v10.15.1 2019-05-26 01:32:53.381 - info: cloud.0 Connecting with https://iobroker.pro:10555 with "@pro_mike@mike-holtgrefe.de_b621e8a0-23d2-11e8-8035-a92015b605a4" 2019-05-26 01:32:58.841 - info: cloud.0 Trying to connect as system.user.admin 2019-05-26 01:33:40.228 - error: iot.0 read ECONNRESET 2019-05-26 01:33:40.244 - info: iot.0 Connection changed: disconnect 2019-05-26 01:33:40.244 - info: iot.0 Connection lost 2019-05-26 01:33:41.352 - error: host.Home-ioBroker instance system.adapter.sonoff.0 terminated with code 7 (Adapter already running) 2019-05-26 01:33:41.352 - info: host.Home-ioBroker Restart adapter system.adapter.sonoff.0 because enabled 2019-05-26 01:33:45.657 - info: iot.0 Connection changed: connect 2019-05-26 01:33:55.874 - warn: alexa2.0 Reconnection to DB. 2019-05-26 01:33:55.890 - warn: alexa2.0 Reconnection to DB. 2019-05-26 01:33:55.907 - warn: hm-rpc.0 Reconnection to DB. 2019-05-26 01:33:55.922 - warn: hm-rpc.0 Reconnection to DB. 2019-05-26 01:33:55.984 - warn: tradfri.0 Reconnection to DB. 2019-05-26 01:33:56.000 - warn: tradfri.0 Reconnection to DB. 2019-05-26 01:34:01.443 - warn: pushover.0 Reconnection to DB. 2019-05-26 01:34:01.443 - warn: pushover.0 Reconnection to DB. 2019-05-26 01:34:11.725 - info: host.Home-ioBroker instance system.adapter.sonoff.0 started with pid 26720 2019-05-26 01:34:12.941 - warn: hm-rega.0 Reconnection to DB. 2019-05-26 01:34:12.957 - warn: hm-rega.0 Reconnection to DB. 2019-05-26 01:34:13.174 - warn: web.0 Reconnection to DB. 2019-05-26 01:34:13.174 - warn: web.0 Reconnection to DB. 2019-05-26 01:34:13.721 - warn: hm-rpc.2 Reconnection to DB. 2019-05-26 01:34:13.737 - warn: hm-rpc.2 Reconnection to DB. 2019-05-26 01:34:13.689 - warn: admin.0 Reconnection to DB. 2019-05-26 01:34:13.705 - warn: admin.0 Reconnection to DB. 2019-05-26 01:34:16.528 - warn: fritzdect.0 Reconnection to DB. 2019-05-26 01:34:16.528 - warn: fritzdect.0 Reconnection to DB. 2019-05-26 01:34:19.696 - info: cloud.0 Trying to connect as system.user.admin 2019-05-26 01:34:26.778 - warn: tr-064.0 Reconnection to DB. 2019-05-26 01:34:26.794 - warn: tr-064.0 Reconnection to DB. 2019-05-26 01:34:27.590 - warn: hm-rpc.0 Reconnection to DB. 2019-05-26 01:34:27.590 - warn: hm-rpc.0 Reconnection to DB. 2019-05-26 01:34:27.620 - warn: alexa2.0 Reconnection to DB. 2019-05-26 01:34:27.620 - warn: alexa2.0 Reconnection to DB. 2019-05-26 01:34:28.230 - warn: tradfri.0 Reconnection to DB. 2019-05-26 01:34:28.230 - warn: tradfri.0 Reconnection to DB. 2019-05-26 01:34:28.729 - warn: iot.0 Reconnection to DB. 2019-05-26 01:34:28.729 - warn: iot.0 Reconnection to DB. 2019-05-26 01:34:29.289 - warn: fritzdect.0 Reconnection to DB. 2019-05-26 01:34:29.289 - warn: fritzdect.0 Reconnection to DB. 2019-05-26 01:34:29.492 - error: pushover.0 already running 2019-05-26 01:34:29.727 - error: host.Home-ioBroker instance system.adapter.pushover.0 terminated with code 7 (Adapter already running) 2019-05-26 01:34:29.727 - info: host.Home-ioBroker Restart adapter system.adapter.pushover.0 because enabled 2019-05-26 01:34:30.804 - error: host.Home-ioBroker instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-05-26 01:34:30.804 - info: host.Home-ioBroker Restart adapter system.adapter.sayit.0 because enabled 2019-05-26 01:34:32.628 - warn: text2command.0 Reconnection to DB. 2019-05-26 01:34:32.628 - warn: text2command.0 Reconnection to DB. 2019-05-26 01:34:33.112 - warn: fullcalendar.0 Reconnection to DB. 2019-05-26 01:34:33.127 - warn: fullcalendar.0 Reconnection to DB. 2019-05-26 01:34:33.299 - warn: sql.0 Reconnection to DB. 2019-05-26 01:34:33.299 - warn: sql.0 Reconnection to DB. 2019-05-26 01:34:33.658 - warn: backitup.0 Reconnection to DB. 2019-05-26 01:34:33.658 - warn: backitup.0 Reconnection to DB. 2019-05-26 01:34:39.087 - error: backitup.0 already running 2019-05-26 01:34:39.587 - error: host.Home-ioBroker instance system.adapter.backitup.0 terminated with code 7 (Adapter already running) 2019-05-26 01:34:39.587 - info: host.Home-ioBroker Restart adapter system.adapter.backitup.0 because enabled 2019-05-26 01:34:47.105 - error: fullcalendar.0 already running 2019-05-26 01:34:39.617 - info: sonoff.0 starting. Version 2.2.2 in C:/iobroker/node_modules/iobroker.sonoff, node: v10.15.1 2019-05-26 01:34:52.129 - error: host.Home-ioBroker instance system.adapter.fullcalendar.0 terminated with code 7 (Adapter already running) 2019-05-26 01:34:52.409 - info: sonoff.0 Starting MQTT server on port 1883 2019-05-26 01:34:52.425 - error: text2command.0 already running 2019-05-26 01:34:52.580 - info: sonoff.0 Client [Sonoff-Steckdose-51] connected with secret 1558827292565_1702 2019-05-26 01:34:52.814 - info: sonoff.0 Client [Sonoff-Steckdose-14] connected with secret 1558827292799_4363 2019-05-26 01:34:52.814 - info: sonoff.0 Client [Sonoff-Steckdose-13] connected with secret 1558827292814_6594 2019-05-26 01:34:52.129 - info: host.Home-ioBroker Restart adapter system.adapter.fullcalendar.0 because enabled 2019-05-26 01:34:53.173 - info: sonoff.0 Client [Sonoff-Steckdose-17] connected with secret 1558827293173_3992 2019-05-26 01:34:53.173 - info: sonoff.0 Client [Sonoff-Steckdose-11] connected with secret 1558827293173_2187 2019-05-26 01:34:53.189 - info: sonoff.0 Client [Sonoff-Steckdose-15] connected with secret 1558827293173_4843 2019-05-26 01:34:53.190 - error: host.Home-ioBroker instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-05-26 01:34:53.190 - info: host.Home-ioBroker Restart adapter system.adapter.text2command.0 because enabled 2019-05-26 01:34:53.204 - error: cloud.0 already running 2019-05-26 01:34:53.251 - info: sonoff.0 Client [Sonoff-Steckdose-53] connected with secret 1558827293251_9534 2019-05-26 01:34:53.314 - info: sonoff.0 Client [Sonoff-Steckdose-12] connected with secret 1558827293298_9981 2019-05-26 01:34:53.345 - info: sonoff.0 Client [Sonoff-Steckdose-16] connected with secret 1558827293345_3055 2019-05-26 01:34:53.439 - error: host.Home-ioBroker instance system.adapter.cloud.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:51.160 - warn: iqontrol.0 Reconnection to DB. 2019-05-26 01:41:51.441 - error: fritzdect.0 already running 2019-05-26 01:41:51.472 - error: text2command.0 already running 2019-05-26 01:41:51.487 - error: tradfri.0 already running 2019-05-26 01:41:51.503 - error: backitup.0 already running 2019-05-26 01:41:51.784 - warn: sql.0 Reconnection to DB. 2019-05-26 01:41:51.784 - warn: sql.0 Reconnection to DB. 2019-05-26 01:41:52.237 - error: pushover.0 already running 2019-05-26 01:41:52.267 - error: tr-064.0 already running 2019-05-26 01:41:52.283 - error: alexa2.0 already running 2019-05-26 01:41:52.283 - error: hm-rpc.0 already running 2019-05-26 01:41:52.314 - error: iqontrol.0 already running 2019-05-26 01:41:52.704 - error: host.Home-ioBroker instance system.adapter.fullcalendar.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:52.704 - info: host.Home-ioBroker Restart adapter system.adapter.fullcalendar.0 because enabled 2019-05-26 01:41:52.720 - error: host.Home-ioBroker instance system.adapter.backitup.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:52.720 - info: host.Home-ioBroker Restart adapter system.adapter.backitup.0 because enabled 2019-05-26 01:41:52.766 - error: host.Home-ioBroker instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:52.766 - info: host.Home-ioBroker Restart adapter system.adapter.text2command.0 because enabled 2019-05-26 01:41:53.079 - warn: javascript.0 Reconnection to DB. 2019-05-26 01:41:53.484 - error: host.Home-ioBroker instance system.adapter.tr-064.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:53.781 - warn: javascript.0 Reconnection to DB. 2019-05-26 01:41:53.484 - info: host.Home-ioBroker Restart adapter system.adapter.tr-064.0 because enabled 2019-05-26 01:41:53.546 - error: host.Home-ioBroker instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:53.546 - info: host.Home-ioBroker Restart adapter system.adapter.sayit.0 because enabled 2019-05-26 01:41:53.593 - error: host.Home-ioBroker instance system.adapter.fritzdect.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:53.593 - info: host.Home-ioBroker Restart adapter system.adapter.fritzdect.0 because enabled 2019-05-26 01:41:53.702 - error: host.Home-ioBroker instance system.adapter.pushover.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:53.702 - info: host.Home-ioBroker Restart adapter system.adapter.pushover.0 because enabled 2019-05-26 01:41:53.718 - error: host.Home-ioBroker instance system.adapter.tradfri.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:53.718 - info: host.Home-ioBroker Restart adapter system.adapter.tradfri.0 because enabled 2019-05-26 01:41:54.498 - info: host.Home-ioBroker instance system.adapter.tr-064.0 started with pid 6832 2019-05-26 01:41:55.684 - error: host.Home-ioBroker instance system.adapter.iqontrol.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:55.684 - info: host.Home-ioBroker Restart adapter system.adapter.iqontrol.0 because enabled 2019-05-26 01:41:55.699 - error: host.Home-ioBroker instance system.adapter.javascript.1 terminated with code 7 (Adapter already running) 2019-05-26 01:41:55.699 - info: host.Home-ioBroker Restart adapter system.adapter.javascript.1 because enabled 2019-05-26 01:41:55.793 - error: host.Home-ioBroker instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-05-26 01:41:55.793 - info: host.Home-ioBroker Restart adapter system.adapter.hm-rpc.0 because enabled 2019-05-26 01:41:55.808 - error: host.Home-ioBroker instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running)
766
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge