Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Admin Adapter 4.0.8

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    UNSOLVED Admin Adapter 4.0.8

    This topic has been deleted. Only users with topic management privileges can see it.
    • JB_Sullivan
      JB_Sullivan last edited by JB_Sullivan

      Auch auf die Gefahr hin, das ich völlig falsch liege, aber seit dem Update auf Admin 4.0.8 scheint der Innogy Adapter verrückt zu spielen.

      Den Entwickler des Innogy Adapter hatte ich in der Vergangeheit schon wegen anderen Dingen mal angeschrieben und auch auf GIT entsprechende Fehler Reports aufgemacht, aber der Entwickler ist scheinbar nicht mehr Aktiv, denn an dem Adapter tut sich gar nichts mehr.

      Um so interessanter das heute nach dem Update des Admin Adapter plötzlich der Innogy Adapter anfängt "Zicken" zu machen.

      Hier einmal das LOG daszu. Wie gesagt, vielleicht liege ich auch völlig falsch und das ganze steht in keinem Zusammenhang.

      innogy-smarthome.0	2020-04-19 13:47:22.201	warn	(848) Unknown state (please report to dev):isOn {"name":"isOn","value":false,"lastchanged":"2020-04-17T17:15:17.543Z"}
      innogy-smarthome.0	2020-04-19 13:47:22.201	warn	(848) Unknown state (please report to dev):activeChannel {"name":"activeChannel","value":"None","lastchanged":"2020-04-17T17:15:18.394Z"}
      innogy-smarthome.0	2020-04-19 13:47:22.151	info	(848) Initialization sequence completed: found 41 devices
      innogy-smarthome.0	2020-04-19 13:47:16.523	info	(848) starting. Version 0.3.4 in C:/iobroker/GLT/node_modules/iobroker.innogy-smarthome, node: v10.17.0
      innogy-smarthome.0	2020-04-19 13:47:16.282	debug	(848) statesDB connected
      innogy-smarthome.0	2020-04-19 13:47:16.281	debug	(848) States connected to redis: 127.0.0.1:9000
      innogy-smarthome.0	2020-04-19 13:47:16.268	debug	(848) States create System PubSub Client
      innogy-smarthome.0	2020-04-19 13:47:16.265	debug	(848) States create User PubSub Client
      innogy-smarthome.0	2020-04-19 13:47:16.256	debug	(848) Redis States: Use Redis connection: 127.0.0.1:9000
      innogy-smarthome.0	2020-04-19 13:47:16.254	debug	(848) objectDB connected
      innogy-smarthome.0	2020-04-19 13:47:16.247	debug	(848) Objects connected to redis: 127.0.0.1:9001
      innogy-smarthome.0	2020-04-19 13:47:16.226	debug	(848) Objects client initialize lua scripts
      innogy-smarthome.0	2020-04-19 13:47:16.225	debug	(848) Objects create User PubSub Client
      innogy-smarthome.0	2020-04-19 13:47:16.224	debug	(848) Objects create System PubSub Client
      innogy-smarthome.0	2020-04-19 13:47:16.219	debug	(848) Objects client ready ... initialize now
      innogy-smarthome.0	2020-04-19 13:47:15.443	debug	(848) Redis Objects: Use Redis connection: 127.0.0.1:9001
      host.GLT	2020-04-19 13:47:14.594	info	instance system.adapter.innogy-smarthome.0 started with pid 848
      host.GLT	2020-04-19 13:46:44.570	info	Restart adapter system.adapter.innogy-smarthome.0 because enabled
      host.GLT	2020-04-19 13:46:44.570	info	instance system.adapter.innogy-smarthome.0 terminated with code 0 (NO_ERROR)
      host.GLT	2020-04-19 13:46:44.570	error	Caught by controller[0]: at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
      host.GLT	2020-04-19 13:46:44.569	error	Caught by controller[0]: { Error: read ECONNRESET
      innogy-smarthome.0	2020-04-19 13:46:44.100	debug	(10732) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
      innogy-smarthome.0	2020-04-19 13:46:44.009	info	(10732) Terminated (NO_ERROR): Without reason
      innogy-smarthome.0	2020-04-19 13:46:44.009	info	(10732) terminating
      innogy-smarthome.0	2020-04-19 13:46:44.003	debug	(10732) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
      innogy-smarthome.0	2020-04-19 13:46:44.001	error	at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
      innogy-smarthome.0	2020-04-19 13:46:44.001	error	(10732) Error: read ECONNRESET
      innogy-smarthome.0	2020-04-19 13:46:44.001	error	(10732) uncaught exception: read ECONNRESET
      info.0	2020-04-19 13:46:19.855	info	(8540) Popup news was read...
      
      1 Reply Last reply Reply Quote 0
      • Winni
        Winni last edited by

        Die Innogy-Server haben wohl heute immer wieder Probleme. Vielleicht ist das der Grund.
        Bei mir wird der Adapter auch immer gelb und rot im log schaut das so aus

        nnogy-smarthome.0	2020-04-19 21:51:55.061	error	(12313) Error: read ECONNRESET at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
        innogy-smarthome.0	2020-04-19 21:51:55.060	error	(12313) uncaught exception: read ECONNRESET
        

        Ich hab noch den ioBroker.admin 3.7.8

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        Support us

        ioBroker
        Community Adapters
        Donate

        952
        Online

        31.9k
        Users

        80.1k
        Topics

        1.3m
        Posts

        admin 4.0.8 innogy
        2
        2
        198
        Loading More Posts
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes
        Reply
        • Reply as topic
        Log in to reply
        Community
        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
        The ioBroker Community 2014-2023
        logo