Navigation

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

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    UNSOLVED HS100 Adapter Fehlermeldungen

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

      Einen guten Abende Alle, ich habe mir den Adapter auch installiert, bei mir tauchen im log folgende Fehlermeldungen auf:

      hs100.0	2020-05-04 18:28:01.490	warn	(2373) Got terminate signal. Checking desired PID: 3676 vs own PID 2373
hs100.0	2020-05-04 18:28:01.483	info	(2373) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
hs100.0	2020-05-04 18:28:01.481	info	(2373) terminating
hs100.0	2020-05-04 18:28:01.479	warn	(2373) Got terminate signal. Checking desired PID: 0 vs own PID 2373
host.vm1-VirtualBox	2020-05-04 18:28:01.474	info	instance system.adapter.hs100.0 started with pid 3676
hs100.0	2020-05-04 18:27:32.580	info	(2373) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.2
host.vm1-VirtualBox	2020-05-04 18:27:31.442	info	Restart adapter system.adapter.hs100.0 because enabled
host.vm1-VirtualBox	2020-05-04 18:27:31.441	error	instance system.adapter.hs100.0 terminated with code 156 (156)

      Aber ich kann ein und aus schalten und die Werte im Objekten sind auch ok.

      current
state
HS110
	state	value			15	
hw_ver	state
HS110
	state	value			2.0	
last_update	state
HS110
	state	value			2020.5.4 18:35:13	
mac	state
HS110
	state	value			98:DA:C4:4F:D0:3D	
model	state
HS110
	state	value			HS110(EU)	
power	state
HS110
	state	value			0	
state	state
HS110
	state	switch			false	
sw_ver	state
HS110
	state	value			1.5.6 Build 191125 Rel.083657
      1 Reply Last reply Reply Quote 0
      • arteck
        arteck Developer Most Active last edited by arteck

        scheisse sry Leute.. hab die dependency nicht aktualiert...

        also .. bitte jetzt nochmal vom GIT installeiren...ohhh man.. sollte die Version 1.1.3 ercheinen

        https://github.com/arteck/ioBroker.hs100

        Winni S B 3 Replies Last reply Reply Quote 1
        • Winni
          Winni @arteck last edited by

          @arteck Schaut gut aus, Fehlermeldungen sind weg, danke vielmals und einen schönen Abend.

          1 Reply Last reply Reply Quote 0
          • S
            skokarl @arteck last edited by

            @arteck sagte in HS100 Adapter Fehlermeldungen:

            scheisse sry Leute.. hab die dependency nicht aktualiert...

            also .. bitte jetzt nochmal vom GIT installeiren...ohhh man.. sollte die Version 1.1.3 ercheinen

            https://github.com/arteck/ioBroker.hs100

            erledigt. Test läuft.

            1 Reply Last reply Reply Quote 0
            • arteck
              arteck Developer Most Active last edited by

              nicht zu früh freuen.. ich bin auch noch am testen..

              M 1 Reply Last reply Reply Quote 0
              • B
                Berchemer @arteck last edited by

                @arteck sagte in HS100 Adapter Fehlermeldungen:

                https://github.com/arteck/ioBroker.hs100

                Test läuft auch hier 🙂

                B 1 Reply Last reply Reply Quote 0
                • M
                  muckel @arteck last edited by

                  @arteck

                  Test läuft seit Mittags
                  Uuups; war das jetzt ein Ausrutscher?
                  Hatte ich mit der .../error Version nicht mehr

                  host.SmartHome	2020-05-05 16:55:43.422	info	Restart adapter system.adapter.hs100.0 because enabled
host.SmartHome	2020-05-05 16:55:43.422	info	instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[3]: at TCP.<anonymous> (net.js:672:12)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[3]: at Socket.emit (events.js:310:20)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[3]: at Object.onceWrapper (events.js:417:26)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[3]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[3]: TCP 192.168.0.44:9999 Error: TCP Socket Closed. segment:0 hadError:false
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[2]: at TCP.<anonymous> (net.js:672:12)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[2]: at Socket.emit (events.js:310:20)
host.SmartHome	2020-05-05 16:55:43.422	error	Caught by controller[2]: at Object.onceWrapper (events.js:417:26)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[2]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[2]: TCP 192.168.0.44:9999 Error: TCP Socket Closed. segment:0 hadError:false
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[1]: at TCP.<anonymous> (net.js:672:12)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[1]: at Socket.emit (events.js:310:20)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[1]: at Object.onceWrapper (events.js:417:26)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[1]: TCP 192.168.0.39:9999 Error: TCP Socket Closed. segment:0 hadError:false
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[0]: at TCP.<anonymous> (net.js:672:12)
host.SmartHome	2020-05-05 16:55:43.421	error	Caught by controller[0]: at Socket.emit (events.js:310:20)
host.SmartHome	2020-05-05 16:55:43.420	error	Caught by controller[0]: at Object.onceWrapper (events.js:417:26)
host.SmartHome	2020-05-05 16:55:43.420	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
host.SmartHome	2020-05-05 16:55:43.418	error	Caught by controller[0]: TCP 192.168.0.45:9999 Error: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 16:55:42.983	error	at TCP.<anonymous> (net.js:672:12)
hs100.0	2020-05-05 16:55:42.983	error	at Socket.emit (events.js:310:20)
hs100.0	2020-05-05 16:55:42.983	error	at Object.onceWrapper (events.js:417:26)
hs100.0	2020-05-05 16:55:42.983	error	at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
hs100.0	2020-05-05 16:55:42.983	error	(28099) Error: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 16:55:42.982	error	(28099) uncaught exception: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 16:55:42.950	error	at TCP.<anonymous> (net.js:672:12)
hs100.0	2020-05-05 16:55:42.950	error	at Socket.emit (events.js:310:20)
hs100.0	2020-05-05 16:55:42.950	error	at Object.onceWrapper (events.js:417:26)
hs100.0	2020-05-05 16:55:42.950	error	at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
hs100.0	2020-05-05 16:55:42.950	error	(28099) Error: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 16:55:42.950	error	(28099) uncaught exception: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 16:55:42.881	info	(28099) Terminated (NO_ERROR): Without reason
hs100.0	2020-05-05 16:55:42.880	info	(28099) terminating
hs100.0	2020-05-05 16:55:42.877	error	at TCP.<anonymous> (net.js:672:12)
hs100.0	2020-05-05 16:55:42.877	error	at Socket.emit (events.js:310:20)
hs100.0	2020-05-05 16:55:42.877	error	at Object.onceWrapper (events.js:417:26)
hs100.0	2020-05-05 16:55:42.877	error	at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
hs100.0	2020-05-05 16:55:42.877	error	(28099) Error: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 16:55:42.875	error	(28099) uncaught exception: TCP Socket Closed. segment:0 hadError:false
                  1 Reply Last reply Reply Quote 0
                  • S
                    skokarl last edited by skokarl

                    so,
                    vor 17 Stunden Adapter aktualisiert.

                    Test bist jetzt :

                    NICHTS, KEIN ERROR

                    @muckel....den Upload hattest Du gemacht ?

                    M 1 Reply Last reply Reply Quote 0
                    • B
                      Berchemer @Berchemer last edited by Berchemer

                      @Berchemer sagte in HS100 Adapter Fehlermeldungen:

                      @arteck sagte in HS100 Adapter Fehlermeldungen:

                      https://github.com/arteck/ioBroker.hs100

                      Test läuft auch hier 🙂

                      Sorry... Hatte vor 9 Stunden von Github installiert, Upload durchgeführt, dann lief es sorgenfrei... Bis vor Kurzem:

                      2020-05-05 17:31:42.282 - debug: hs100.0 (32448) HS Plug 192.1.1.132
2020-05-05 17:31:42.282 - debug: hs100.0 (32448) HS Plug 192.1.1.131
2020-05-05 17:31:42.467 - debug: hs100.0 (32448) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.5 17:31:42
2020-05-05 17:31:42.548 - debug: hs100.0 (32448) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.5 17:31:42
2020-05-05 17:31:43.720 - debug: hs100.0 (32448) Refresh Data HS110 192.1.1.132
2020-05-05 17:31:44.581 - debug: hs100.0 (32448) Month value HS110(EU) 192.1.1.132
2020-05-05 17:31:45.017 - debug: hs100.0 (32448) Day value HS110(EU) 0.32 192.1.1.132
2020-05-05 17:31:52.469 - error: hs100.0 (32448) uncaught exception: TCP Timeout
2020-05-05 17:31:52.469 - error: hs100.0 (32448) Error: TCP Timeout
at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
2020-05-05 17:31:52.470 - debug: hs100.0 (32448) Send error setDevState : Error: TCP Timeout
2020-05-05 17:31:52.470 - debug: hs100.0 (32448) Send error setDevState : Error: TCP Timeout
2020-05-05 17:31:52.470 - debug: hs100.0 (32448) Send error setDevState : Error: TCP Timeout
2020-05-05 17:31:52.472 - info: hs100.0 (32448) terminating
2020-05-05 17:31:52.472 - info: hs100.0 (32448) Terminated (NO_ERROR): Without reason
2020-05-05 17:31:52.983 - error: host.SERVER Caught by controller[1]: TCP 192.1.1.131:9999 Error: TCP Timeout
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[1]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[1]: at listOnTimeout (internal/timers.js:549:17)
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[1]: at processTimers (internal/timers.js:492:7)
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[2]: TCP 192.1.1.131:9999 Error: TCP Timeout
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[2]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[2]: at listOnTimeout (internal/timers.js:549:17)
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[2]: at processTimers (internal/timers.js:492:7)
2020-05-05 17:31:52.984 - error: host.SERVER Caught by controller[2]: TCP 192.1.1.131:9999 Error: TCP Timeout
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: at listOnTimeout (internal/timers.js:549:17)
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: at processTimers (internal/timers.js:492:7)
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: TCP 192.1.1.131:9999 Error: TCP Timeout
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: at listOnTimeout (internal/timers.js:549:17)
2020-05-05 17:31:52.985 - error: host.SERVER Caught by controller[2]: at processTimers (internal/timers.js:492:7)
2020-05-05 17:31:52.985 - info: host.SERVER instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
2020-05-05 17:31:52.985 - info: host.SERVER Restart adapter system.adapter.hs100.0 because enabled
2020-05-05 17:32:23.031 - info: host.SERVER instance system.adapter.hs100.0 started with pid 28913
2020-05-05 17:32:23.223 - debug: hs100.0 (28913) Redis Objects: Use Redis connection: 0.0.0.0:9001
2020-05-05 17:32:23.232 - debug: hs100.0 (28913) Objects client ready ... initialize now
2020-05-05 17:32:23.233 - debug: hs100.0 (28913) Objects create System PubSub Client
2020-05-05 17:32:23.234 - debug: hs100.0 (28913) Objects create User PubSub Client
2020-05-05 17:32:23.234 - debug: hs100.0 (28913) Objects client initialize lua scripts
2020-05-05 17:32:23.241 - debug: hs100.0 (28913) Objects connected to redis: 0.0.0.0:9001
2020-05-05 17:32:23.242 - debug: hs100.0 (28913) objectDB connected
2020-05-05 17:32:23.243 - debug: hs100.0 (28913) Redis States: Use Redis connection: 0.0.0.0:9000
2020-05-05 17:32:23.247 - debug: hs100.0 (28913) States create User PubSub Client
2020-05-05 17:32:23.248 - debug: hs100.0 (28913) States create System PubSub Client
2020-05-05 17:32:23.254 - debug: hs100.0 (28913) States connected to redis: 0.0.0.0:9000
2020-05-05 17:32:23.254 - debug: hs100.0 (28913) statesDB connected
2020-05-05 17:32:23.412 - info: hs100.0 (28913) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.3, js-controller: 3.0.20
2020-05-05 17:32:23.424 - debug: hs100.0 (28913) Host = SERVER
2020-05-05 17:32:23.446 - debug: hs100.0 (28913) undefined generated 192.1.1.131
2020-05-05 17:32:23.447 - debug: hs100.0 (28913) undefined generated 192.1.1.132

2020-05-05 17:32:23.700 - debug: hs100.0 (28913) HS Plug 192.1.1.132
2020-05-05 17:32:23.701 - debug: hs100.0 (28913) HS Plug 192.1.1.131
2020-05-05 17:32:25.700 - debug: hs100.0 (28913) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.5 17:32:25
2020-05-05 17:32:26.862 - debug: hs100.0 (28913) Refresh Data HS110 192.1.1.132
2020-05-05 17:32:27.735 - debug: hs100.0 (28913) Month value HS110(EU) 192.1.1.132
2020-05-05 17:32:28.169 - debug: hs100.0 (28913) Day value HS110(EU) 0.32 192.1.1.132
2020-05-05 17:32:30.162 - debug: hs100.0 (28913) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.5 17:32:30
2020-05-05 17:32:30.453 - debug: hs100.0 (28913) Refresh Data HS110 192.1.1.131
2020-05-05 17:32:30.744 - debug: hs100.0 (28913) Month value HS110(EU) 192.1.1.131
2020-05-05 17:32:31.034 - debug: hs100.0 (28913) Day value HS110(EU) 0.438 192.1.1.131

2020-05-05 17:34:23.703 - debug: hs100.0 (28913) HS Plug 192.1.1.132
2020-05-05 17:34:23.705 - debug: hs100.0 (28913) HS Plug 192.1.1.131
2020-05-05 17:34:23.920 - debug: hs100.0 (28913) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.5 17:34:23
2020-05-05 17:34:25.080 - debug: hs100.0 (28913) Refresh Data HS110 192.1.1.132
2020-05-05 17:34:25.952 - debug: hs100.0 (28913) Month value HS110(EU) 192.1.1.132
2020-05-05 17:34:26.182 - debug: hs100.0 (28913) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.5 17:34:26
2020-05-05 17:34:26.390 - debug: hs100.0 (28913) Day value HS110(EU) 0.32 192.1.1.132
2020-05-05 17:34:32.058 - error: hs100.0 (28913) uncaught exception: TCP Socket Closed. segment:0 hadError:false
2020-05-05 17:34:32.058 - error: hs100.0 (28913) Error: TCP Socket Closed. segment:0 hadError:false
at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
at Object.onceWrapper (events.js:417:26)
at Socket.emit (events.js:310:20)
at TCP. (net.js:672:12)
2020-05-05 17:34:32.059 - debug: hs100.0 (28913) Send error setDevState : Error: TCP Socket Closed. segment:0 hadError:false
2020-05-05 17:34:32.061 - info: hs100.0 (28913) terminating
2020-05-05 17:34:32.061 - info: hs100.0 (28913) Terminated (NO_ERROR): Without reason
2020-05-05 17:34:32.304 - debug: hs100.0 (28913) Month value HS110(EU) 192.1.1.131
2020-05-05 17:34:32.576 - error: host.SERVER Caught by controller[0]: TCP 192.1.1.131:9999 Error: TCP Socket Closed. segment:0 hadError:false
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[0]: at Object.onceWrapper (events.js:417:26)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[0]: at Socket.emit (events.js:310:20)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[0]: at TCP. (net.js:672:12)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[1]: TCP 192.1.1.131:9999 Error: TCP Socket Closed. segment:0 hadError:false
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[1]: at Object.onceWrapper (events.js:417:26)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[1]: at Socket.emit (events.js:310:20)
2020-05-05 17:34:32.578 - error: host.SERVER Caught by controller[1]: at TCP. (net.js:672:12)
2020-05-05 17:34:32.578 - info: host.SERVER instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
2020-05-05 17:34:32.579 - info: host.SERVER Restart adapter system.adapter.hs100.0 because enabled
2020-05-05 17:35:00.052 - info: host.SERVER instance system.adapter.dwd.0 started with pid 31169
2020-05-05 17:35:02.620 - info: host.SERVER instance system.adapter.hs100.0 started with pid 31227
2020-05-05 17:35:02.811 - debug: hs100.0 (31227) Redis Objects: Use Redis connection: 0.0.0.0:9001
2020-05-05 17:35:02.822 - debug: hs100.0 (31227) Objects client ready ... initialize now
2020-05-05 17:35:02.823 - debug: hs100.0 (31227) Objects create System PubSub Client
2020-05-05 17:35:02.823 - debug: hs100.0 (31227) Objects create User PubSub Client
2020-05-05 17:35:02.824 - debug: hs100.0 (31227) Objects client initialize lua scripts
2020-05-05 17:35:02.834 - debug: hs100.0 (31227) Objects connected to redis: 0.0.0.0:9001
2020-05-05 17:35:02.836 - debug: hs100.0 (31227) objectDB connected
2020-05-05 17:35:02.837 - debug: hs100.0 (31227) Redis States: Use Redis connection: 0.0.0.0:9000
2020-05-05 17:35:02.842 - debug: hs100.0 (31227) States create User PubSub Client
2020-05-05 17:35:02.842 - debug: hs100.0 (31227) States create System PubSub Client
2020-05-05 17:35:02.851 - debug: hs100.0 (31227) States connected to redis: 0.0.0.0:9000
2020-05-05 17:35:02.851 - debug: hs100.0 (31227) statesDB connected
2020-05-05 17:35:03.034 - info: hs100.0 (31227) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.3, js-controller: 3.0.20
2020-05-05 17:35:03.044 - debug: hs100.0 (31227) Host = SERVER
2020-05-05 17:35:03.070 - debug: hs100.0 (31227) undefined generated 192.1.1.131
2020-05-05 17:35:03.114 - debug: hs100.0 (31227) undefined generated 192.1.1.132

2020-05-05 17:35:03.413 - debug: hs100.0 (31227) HS Plug 192.1.1.132
2020-05-05 17:35:03.415 - debug: hs100.0 (31227) HS Plug 192.1.1.131
2020-05-05 17:35:05.443 - debug: hs100.0 (31227) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.5 17:35:05
2020-05-05 17:35:06.605 - debug: hs100.0 (31227) Refresh Data HS110 192.1.1.132
2020-05-05 17:35:07.476 - debug: hs100.0 (31227) Month value HS110(EU) 192.1.1.132
2020-05-05 17:35:07.912 - debug: hs100.0 (31227) Day value HS110(EU) 0.32 192.1.1.132
2020-05-05 17:35:10.191 - debug: hs100.0 (31227) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.5 17:35:10
2020-05-05 17:35:12.684 - debug: hs100.0 (31227) Refresh Data HS110 192.1.1.131
2020-05-05 17:35:13.529 - debug: hs100.0 (31227) Month value HS110(EU) 192.1.1.131
2020-05-05 17:35:13.965 - debug: hs100.0 (31227) Day value HS110(EU) 0.44 192.1.1.131
                      S 1 Reply Last reply Reply Quote 0
                      • S
                        skokarl @Berchemer last edited by

                        @Berchemer

                        bei mir seit 17 Std. sauber

                        1 Reply Last reply Reply Quote 0
                        • M
                          muckel @skokarl last edited by

                          @skokarl

                          @muckel....den Upload hattest Du gemacht ?

                          natürlich, hab ja dazugelernt 🙂
                          Bis jetzt kam es nicht mehr.

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            skokarl @muckel last edited by

                            @muckel sagte in HS100 Adapter Fehlermeldungen:

                            @skokarl

                            @muckel....den Upload hattest Du gemacht ?

                            natürlich, hab ja dazugelernt 🙂
                            Bis jetzt kam es nicht mehr.

                            Du hattest doch eben noch von Fehler gesprochen ?

                            M 2 Replies Last reply Reply Quote 0
                            • M
                              muckel @skokarl last edited by

                              @skokarl

                              Siehe Logfile. Das kam einmalig. Seither nichts mehr. Seltsam

                              1 Reply Last reply Reply Quote 0
                              • M
                                muckel @skokarl last edited by

                                @skokarl

                                wieder

                                host.SmartHome	2020-05-05 20:04:43.615	error	Caught by controller[0]: at TCP.<anonymous> (net.js:672:12)
host.SmartHome	2020-05-05 20:04:43.615	error	Caught by controller[0]: at Socket.emit (events.js:310:20)
host.SmartHome	2020-05-05 20:04:43.614	error	Caught by controller[0]: at Object.onceWrapper (events.js:417:26)
host.SmartHome	2020-05-05 20:04:43.614	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
host.SmartHome	2020-05-05 20:04:43.612	error	Caught by controller[0]: TCP 192.168.0.42:9999 Error: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 20:04:43.076	info	(24753) Terminated (NO_ERROR): Without reason
hs100.0	2020-05-05 20:04:43.075	info	(24753) terminating
hs100.0	2020-05-05 20:04:43.023	error	at TCP.<anonymous> (net.js:672:12)
hs100.0	2020-05-05 20:04:43.023	error	at Socket.emit (events.js:310:20)
hs100.0	2020-05-05 20:04:43.023	error	at Object.onceWrapper (events.js:417:26)
hs100.0	2020-05-05 20:04:43.023	error	at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
hs100.0	2020-05-05 20:04:43.023	error	(24753) Error: TCP Socket Closed. segment:0 hadError:false
hs100.0	2020-05-05 20:04:43.019	error	(24753) uncaught exception: TCP Socket Closed. segment:0 hadError:false
                                1 Reply Last reply Reply Quote 0
                                • Winni
                                  Winni last edited by Winni

                                  Sorry, falscher Thread

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    skokarl last edited by

                                    seit 26 Stunden sauber !!!!
                                    scheint als wäre ich raus ...😀

                                    @arteck sieht gut aus.

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      Berchemer last edited by

                                      Nachdem es bei mir über 12 Stunden ohne Fehler lief, habe ich auch mal sicherheitshalber den Adapter gestoppt, den Objekte-Ordner gelöscht und neu gestartet. Mal sehen, wie es jetzt weitergeht 🙂

                                      S 1 Reply Last reply Reply Quote 0
                                      • S
                                        skokarl @Berchemer last edited by

                                        @Berchemer sagte in HS100 Adapter Fehlermeldungen:

                                        Nachdem es bei mir über 12 Stunden ohne Fehler lief, habe ich auch mal sicherheitshalber den Adapter gestoppt, den Objekte-Ordner gelöscht und neu gestartet. Mal sehen, wie es jetzt weitergeht 🙂

                                        gute Idee, mach ich auch noch

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          Berchemer last edited by

                                          Btw. Nachdem ich wegen des Neuanlegens des Objektebaums die Protokollierung durch den SQL-Adapter wieder eingeschaltet habe, wollte ich die Monatscounter als Zähler im sql-Reiter definieren. Der sql-Adapter meckerte daraufhin, dass man string-Datenpunkte nicht als Counter definieren könne und ich stellte fest, dass die Datenpunkte mit Stromstärke, Leistung, Gesamtmenge usw. nicht als number, sondern als string definiert sind.

                                          Ich gehe nicht davon aus, dass das das Problem ist, dem wir hier seit Tagen hinterherjagen. Aber sollte man die bei Neuanlage nicht als number statt string definieren? In dem Zusammenhang könnt eman ggf. auch die Unit der Datenpunkte bei Neuanlage mit angeben. Könnte u.a. der automatischen Erkennung durch den Adapter SourceAnalytics helfen, wenn bei den Werte auch Watt oder kwh oder V usw. als Unit stehen würde. Ist sicherlich nichts Dringliches, nur eine Verschönerung 🙂

                                          Wer weiß, ob es auch damit zusammenhängen könnte aber ganz nebenbei habe ich auch mal die Firmware der beiden Steckdosen angehoben von

                                          1.5.4 Build 180815 Rel 121440

                                          auf

                                          1.5.6 Build 191125 Rel 083657

                                          Vielleicht hilft es ja.
                                          Jetzt lasse ich aber den Adapter und die Steckdosen mal wieder in Ruhe damit sie ordentlich weiter laufen und sperre den Steckdosen nach dem Update wieder den Internetzugang 🙂

                                          1 Reply Last reply Reply Quote 0
                                          • B
                                            Berchemer last edited by

                                            Lief so schön durch... Über 12 Stunden... Und dann 😖

                                            2020-05-07 09:20:18.669 - debug: hs100.0 (5004) HS Plug 192.1.1.132
2020-05-07 09:20:18.671 - debug: hs100.0 (5004) HS Plug 192.1.1.131
2020-05-07 09:20:18.869 - debug: hs100.0 (5004) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.7 09:20:18
2020-05-07 09:20:18.875 - debug: hs100.0 (5004) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.7 09:20:18
2020-05-07 09:20:20.037 - debug: hs100.0 (5004) Refresh Data HS110 192.1.1.131
2020-05-07 09:20:20.045 - debug: hs100.0 (5004) Refresh Data HS110 192.1.1.132
2020-05-07 09:20:20.902 - debug: hs100.0 (5004) Month value HS110(EU) 192.1.1.132
2020-05-07 09:20:20.909 - debug: hs100.0 (5004) Month value HS110(EU) 192.1.1.131
2020-05-07 09:20:21.338 - debug: hs100.0 (5004) Day value HS110(EU) 0.166 192.1.1.132
2020-05-07 09:20:21.352 - debug: hs100.0 (5004) Day value HS110(EU) 0.169 192.1.1.131

2020-05-07 09:22:18.673 - debug: hs100.0 (5004) HS Plug 192.1.1.132
2020-05-07 09:22:18.675 - debug: hs100.0 (5004) HS Plug 192.1.1.131
2020-05-07 09:22:18.833 - debug: hs100.0 (5004) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.7 09:22:18
2020-05-07 09:22:19.995 - debug: hs100.0 (5004) Refresh Data HS110 192.1.1.132
2020-05-07 09:22:20.867 - debug: hs100.0 (5004) Month value HS110(EU) 192.1.1.132
2020-05-07 09:22:21.302 - debug: hs100.0 (5004) Day value HS110(EU) 0.166 192.1.1.132
2020-05-07 09:22:21.604 - debug: hs100.0 (5004) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.7 09:22:21
2020-05-07 09:22:27.668 - error: hs100.0 (5004) uncaught exception: TCP Socket Closed. segment:0 hadError:false
2020-05-07 09:22:27.669 - error: hs100.0 (5004) Error: TCP Socket Closed. segment:0 hadError:false
at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
at Object.onceWrapper (events.js:417:26)
at Socket.emit (events.js:310:20)
at TCP. (net.js:672:12)
2020-05-07 09:22:27.672 - info: hs100.0 (5004) terminating
2020-05-07 09:22:27.672 - info: hs100.0 (5004) Terminated (NO_ERROR): Without reason
2020-05-07 09:22:27.747 - error: hs100.0 (5004) uncaught exception: TCP Socket Closed. segment:0 hadError:false
2020-05-07 09:22:27.748 - error: hs100.0 (5004) Error: TCP Socket Closed. segment:0 hadError:false
at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
at Object.onceWrapper (events.js:417:26)
at Socket.emit (events.js:310:20)
at TCP. (net.js:672:12)
2020-05-07 09:22:28.034 - debug: hs100.0 (5004) Day value HS110(EU) 0.169 192.1.1.131
2020-05-07 09:22:28.188 - error: host.SERVER Caught by controller[0]: TCP 192.1.1.131:9999 Error: TCP Socket Closed. segment:0 hadError:false
2020-05-07 09:22:28.190 - error: host.SERVER Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
2020-05-07 09:22:28.190 - error: host.SERVER Caught by controller[0]: at Object.onceWrapper (events.js:417:26)
2020-05-07 09:22:28.190 - error: host.SERVER Caught by controller[0]: at Socket.emit (events.js:310:20)
2020-05-07 09:22:28.190 - error: host.SERVER Caught by controller[0]: at TCP. (net.js:672:12)
2020-05-07 09:22:28.191 - error: host.SERVER Caught by controller[1]: TCP 192.1.1.131:9999 Error: TCP Socket Closed. segment:0 hadError:false
2020-05-07 09:22:28.191 - error: host.SERVER Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19)
2020-05-07 09:22:28.191 - error: host.SERVER Caught by controller[1]: at Object.onceWrapper (events.js:417:26)
2020-05-07 09:22:28.191 - error: host.SERVER Caught by controller[1]: at Socket.emit (events.js:310:20)
2020-05-07 09:22:28.191 - error: host.SERVER Caught by controller[1]: at TCP. (net.js:672:12)
2020-05-07 09:22:28.191 - info: host.SERVER instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
2020-05-07 09:22:28.191 - info: host.SERVER Restart adapter system.adapter.hs100.0 because enabled
2020-05-07 09:22:58.208 - info: host.SERVER instance system.adapter.hs100.0 started with pid 7002
2020-05-07 09:22:58.527 - debug: hs100.0 (7002) Redis Objects: Use Redis connection: 0.0.0.0:9001
2020-05-07 09:22:58.538 - debug: hs100.0 (7002) Objects client ready ... initialize now
2020-05-07 09:22:58.539 - debug: hs100.0 (7002) Objects create System PubSub Client
2020-05-07 09:22:58.539 - debug: hs100.0 (7002) Objects create User PubSub Client
2020-05-07 09:22:58.540 - debug: hs100.0 (7002) Objects client initialize lua scripts
2020-05-07 09:22:58.548 - debug: hs100.0 (7002) Objects connected to redis: 0.0.0.0:9001
2020-05-07 09:22:58.549 - debug: hs100.0 (7002) objectDB connected
2020-05-07 09:22:58.550 - debug: hs100.0 (7002) Redis States: Use Redis connection: 0.0.0.0:9000
2020-05-07 09:22:58.555 - debug: hs100.0 (7002) States create User PubSub Client
2020-05-07 09:22:58.555 - debug: hs100.0 (7002) States create System PubSub Client
2020-05-07 09:22:58.563 - debug: hs100.0 (7002) States connected to redis: 0.0.0.0:9000
2020-05-07 09:22:58.564 - debug: hs100.0 (7002) statesDB connected
2020-05-07 09:22:58.786 - info: hs100.0 (7002) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.hs100, node: v12.16.3, js-controller: 3.0.20
2020-05-07 09:22:58.794 - debug: hs100.0 (7002) Host = SERVER
2020-05-07 09:22:58.815 - debug: hs100.0 (7002) undefined generated 192.1.1.131
2020-05-07 09:22:58.817 - debug: hs100.0 (7002) undefined generated 192.1.1.132

2020-05-07 09:22:59.100 - debug: hs100.0 (7002) HS Plug 192.1.1.132
2020-05-07 09:22:59.101 - debug: hs100.0 (7002) HS Plug 192.1.1.131
2020-05-07 09:23:00.692 - debug: hs100.0 (7002) Refresh 192.1.1.131 Model = HS110(EU) state = true update = 2020.5.7 09:23:00
2020-05-07 09:23:01.128 - debug: hs100.0 (7002) Refresh 192.1.1.132 Model = HS110(EU) state = true update = 2020.5.7 09:23:01
2020-05-07 09:23:02.290 - debug: hs100.0 (7002) Refresh Data HS110 192.1.1.132
2020-05-07 09:23:03.162 - debug: hs100.0 (7002) Month value HS110(EU) 192.1.1.132
2020-05-07 09:23:03.173 - debug: hs100.0 (7002) Refresh Data HS110 192.1.1.131
2020-05-07 09:23:03.599 - debug: hs100.0 (7002) Day value HS110(EU) 0.167 192.1.1.132
2020-05-07 09:23:04.480 - debug: hs100.0 (7002) Month value HS110(EU) 192.1.1.131
2020-05-07 09:23:04.916 - debug: hs100.0 (7002) Day value HS110(EU) 0.169 192.1.1.131
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            810
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            fehler im log hs100 adapter
                                            23
                                            190
                                            17635
                                            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