Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. [WLED] LED streifen (WS2812B,WS2811,SK6812,APA102) bedienen

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    [WLED] LED streifen (WS2812B,WS2811,SK6812,APA102) bedienen

    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jkalver @Dutchman last edited by

      @dutchman
      Hi,

      ich habe meine Logs die Tage mal näher beobachtet, um die Fehlerursache weiter einzuschränken.
      Dabei bin ich auf folgendes gestossen. Irgendwann am Nachmittag erzeugt mein iobroker einen Fehler : read ECONNRESET
      Während die anderen Adapter damit umgehen können (siehe beiliegendes log) hat der WLED Adapter ein Problem, sich davon zu erholen.
      Vielleicht hilft das ja bei der Fehlersuche.

      2021-04-21 20:04:16.595  - error: fronius.0 (775) States database error: read ECONNRESET
2021-04-21 20:04:16.677  - error: email.0 (1960) States database error: read ECONNRESET
2021-04-21 20:04:16.573  - error: wled.0 (2140) States database error: read ECONNRESET
2021-04-21 20:04:16.746  - error: tr-064.0 (1599) States database error: read ECONNRESET
2021-04-21 20:04:16.784  - error: javascript.0 (1801) States database error: read ECONNRESET
2021-04-21 20:04:16.845  - error: backitup.0 (844) States database error: read ECONNRESET
2021-04-21 20:04:16.906  - error: discovery.0 (756) States database error: read ECONNRESET
2021-04-21 20:04:16.913  - error: robonect.0 (1562) States database error: read ECONNRESET
2021-04-21 20:04:16.875  - info: wled.0 (2140) cleaned everything up...
2021-04-21 20:04:16.918  - error: sql.0 (1327) States database error: write ECONNRESET
2021-04-21 20:04:16.876  - info: javascript.0 (1801) Stop script script.js.PV_Leistung_nach_KNX
2021-04-21 20:04:16.878  - info: javascript.0 (1801) Stop script script.js.Batterie_Ladezustand_nach_KNX
2021-04-21 20:04:16.880  - info: javascript.0 (1801) Stop script script.js.Batterie_Leistung
2021-04-21 20:04:16.880  - info: javascript.0 (1801) Stop script script.js.Netz_Leistung
2021-04-21 20:04:16.881  - info: javascript.0 (1801) Stop script script.js.FehlerEmail
2021-04-21 20:04:16.882  - info: javascript.0 (1801) Stop script script.js.Hausverbrauch_Wh
2021-04-21 20:04:16.883  - info: javascript.0 (1801) Stop script script.js.Garagentor_Licht_Steuerung.PRESET_von_KNX_nach_WLED
2021-04-21 20:04:16.883  - info: javascript.0 (1801) Stop script script.js.Wled_Terasse.Preset_vonKNX_nach_WLED
2021-04-21 20:04:16.884  - info: javascript.0 (1801) Stop script script.js.Wled_Terasse.Ein_Aus_Schalten
2021-04-21 20:04:16.884  - info: javascript.0 (1801) Stop script script.js.Wled_Terasse.Dimmer
2021-04-21 20:04:16.885  - info: javascript.0 (1801) Stop script script.js.Wled_Terasse.Ausschalten_wenn_Steckdose_ausschaltet
2021-04-21 20:04:16.959  - error: ping.0 (1341) States database error: read ECONNRESET
2021-04-21 20:04:16.963  - error: admin.0 (745) States database error: read ECONNRESET
2021-04-21 20:04:16.963  - error: modbus.0 (1762) States database error: write ECONNRESET
2021-04-21 20:04:17.052  - error: web.0 (791) States database error: read ECONNRESET
2021-04-21 20:04:16.998  - error: modbus.0 (1762) Objects database error: read ECONNRESET
2021-04-21 20:04:17.115  - info: backitup.0 (844) cleaned everything up...
2021-04-21 20:04:17.113  - error: info.0 (810) States database error: write ECONNRESET
2021-04-21 20:04:17.002  - error: admin.0 (745) Objects database error: read ECONNRESET
2021-04-21 20:04:17.159  - info: robonect.0 (1562) cleaned everything up...
2021-04-21 20:04:17.197  - info: admin.0 (745) terminating http server on port 8081
2021-04-21 20:04:17.257  - info: info.0 (810) cleaned everything up...
2021-04-21 20:04:17.176  - error: knx.0 (1376) States database error: write EPIPE
2021-04-21 20:04:17.334  - info: web.0 (791) terminated http server on port 8082
2021-04-21 20:04:17.296  - error: info.0 (810) Objects database error: write EPIPE
2021-04-21 20:04:17.453  - error: knx.0 (1376) Objects database error: read ECONNRESET
2021-04-21 20:04:18.379  - debug: wled.0 (2140) Plugin sentry destroyed
2021-04-21 20:04:18.380  - info: wled.0 (2140) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.389  - info: javascript.0 (1801) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.416  - info: fronius.0 (775) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.592  - info: email.0 (1960) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.625  - info: backitup.0 (844) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.671  - info: robonect.0 (1562) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.672  - info: discovery.0 (756) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.685  - info: sql.0 (1327) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.730  - info: admin.0 (745) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.732  - info: ping.0 (1341) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.767  - info: info.0 (810) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:18.846  - info: web.0 (791) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2021-04-21 20:04:20.085  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:21.754  - error: wled.0 (2140) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:21.783  - error: fronius.0 (775) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:21.821  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.835  - error: email.0 (1960) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:21.838  - error: javascript.0 (1801) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:21.846  - error: tr-064.0 (1599) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:21.842  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.842  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.843  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.844  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.845  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.846  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.847  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.848  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.849  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.849  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.850  - warn: fronius.0 (775) get state error: DB closed
2021-04-21 20:04:21.920  - error: backitup.0 (844) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:21.982  - warn: backitup.0 (844) get state error: DB closed
2021-04-21 20:04:22.003  - error: robonect.0 (1562) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.087  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.097  - warn: robonect.0 (1562) get state error: DB closed
2021-04-21 20:04:22.099  - error: discovery.0 (756) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.098  - error: ping.0 (1341) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.096  - error: admin.0 (745) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.105  - warn: email.0 (1960) get state error: DB closed
2021-04-21 20:04:22.104  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.105  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.106  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.108  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.109  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.111  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.112  - warn: sql.0 (1327) No Connection to database
2021-04-21 20:04:22.129  - error: web.0 (791) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.143  - warn: discovery.0 (756) get state error: DB closed
2021-04-21 20:04:22.147  - warn: admin.0 (745) get state error: Connection is closed.
2021-04-21 20:04:22.149  - warn: web.0 (791) get state error: DB closed
2021-04-21 20:04:22.189  - error: modbus.0 (1762) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.194  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.213  - error: sql.0 (1327) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.196  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.198  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.201  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.203  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.209  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.210  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.213  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.215  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.216  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.218  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.219  - warn: ping.0 (1341) get state error: DB closed
2021-04-21 20:04:22.305  - error: info.0 (810) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:22.434  - warn: info.0 (810) get state error: Connection is closed.
2021-04-21 20:04:22.436  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.437  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.437  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.437  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.438  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.438  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.438  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.439  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.439  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.439  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.440  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.440  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.440  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.441  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.441  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.442  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.442  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.449  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.449  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.450  - warn: info.0 (810) get state error: DB closed
2021-04-21 20:04:22.576  - error: knx.0 (1376) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
2021-04-21 20:04:26.789  - error: fronius.0 (775) Cannot check object existence of "fronius.0.info.lastsync": Connection is closed.
2021-04-21 20:04:27.106  - error: ping.0 (1341) Cannot check object existence of "ping.0.192_168_1_1.alive": Connection is closed.
2021-04-21 20:04:27.312  - error: info.0 (810) Cannot check object existence of "info.0.sysinfo.cpu.currentspeed.maxSpeed": Connection is closed.
2021-04-21 20:04:31.183  - info: host.ioBroker-RasPi4 iobroker.js-controller version 3.2.16 js-controller starting
2021-04-21 20:04:31.193  - info: host.ioBroker-RasPi4 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-04-21 20:04:31.194  - info: host.ioBroker-RasPi4 hostname: ioBroker-RasPi4, node: v10.23.0
2021-04-21 20:04:31.195  - info: host.ioBroker-RasPi4 ip addresses: 192.168.1.8 2003:cd:5735:8200:3252:103f:8920:f841 fe80::d70c:377c:4d1e:edc2
2021-04-21 20:04:32.951  - info: host.ioBroker-RasPi4 connected to Objects and States
2021-04-21 20:04:33.054  - info: host.ioBroker-RasPi4 added notifications configuration of host
2021-04-21 20:04:33.999  - info: host.ioBroker-RasPi4 17 instances found
2021-04-21 20:04:34.061  - info: host.ioBroker-RasPi4 starting 15 instances
2021-04-21 20:04:34.244  - info: host.ioBroker-RasPi4 instance system.adapter.admin.0 started with pid 7446
2021-04-21 20:04:37.540  - error: admin.0 (7446) admin.0 already running
2021-04-21 20:04:37.545  - warn: admin.0 (7446) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:04:38.196  - info: host.ioBroker-RasPi4 instance system.adapter.discovery.0 started with pid 7459
2021-04-21 20:04:38.321  - error: host.ioBroker-RasPi4 instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:04:38.323  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.admin.0 because enabled
2021-04-21 20:04:40.370  - error: discovery.0 (7459) discovery.0 already running
2021-04-21 20:04:40.374  - warn: discovery.0 (7459) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:04:41.070  - error: host.ioBroker-RasPi4 instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:04:41.072  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.discovery.0 because enabled
2021-04-21 20:04:42.141  - info: host.ioBroker-RasPi4 instance system.adapter.fronius.0 started with pid 7472
2021-04-21 20:04:44.870  - error: fronius.0 (7472) fronius.0 already running
2021-04-21 20:04:44.874  - warn: fronius.0 (7472) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:04:45.515  - error: host.ioBroker-RasPi4 instance system.adapter.fronius.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:04:45.516  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.fronius.0 because enabled
2021-04-21 20:04:46.250  - info: host.ioBroker-RasPi4 instance system.adapter.web.0 started with pid 7485
2021-04-21 20:04:48.480  - error: web.0 (7485) web.0 already running
2021-04-21 20:04:48.484  - warn: web.0 (7485) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:04:49.163  - error: host.ioBroker-RasPi4 instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:04:49.164  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.web.0 because enabled
2021-04-21 20:04:50.232  - info: host.ioBroker-RasPi4 instance system.adapter.info.0 started with pid 7498
2021-04-21 20:04:53.806  - error: info.0 (7498) info.0 already running
2021-04-21 20:04:53.811  - warn: info.0 (7498) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:04:54.115  - info: host.ioBroker-RasPi4 instance system.adapter.backitup.0 started with pid 7519
2021-04-21 20:04:54.488  - error: host.ioBroker-RasPi4 instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:04:54.489  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.info.0 because enabled
2021-04-21 20:04:58.201  - info: host.ioBroker-RasPi4 instance system.adapter.sql.0 started with pid 7528
2021-04-21 20:05:01.151  - error: sql.0 (7528) sql.0 already running
2021-04-21 20:05:01.157  - warn: sql.0 (7528) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:01.811  - error: host.ioBroker-RasPi4 instance system.adapter.sql.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:01.813  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.sql.0 because enabled
2021-04-21 20:05:01.930  - error: backitup.0 (7519) backitup.0 already running
2021-04-21 20:05:01.934  - warn: backitup.0 (7519) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:02.201  - info: host.ioBroker-RasPi4 instance system.adapter.ping.0 started with pid 7551
2021-04-21 20:05:02.592  - error: host.ioBroker-RasPi4 instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:02.594  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.backitup.0 because enabled
2021-04-21 20:05:04.276  - error: ping.0 (7551) ping.0 already running
2021-04-21 20:05:04.281  - warn: ping.0 (7551) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:04.962  - error: host.ioBroker-RasPi4 instance system.adapter.ping.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:04.963  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.ping.0 because enabled
2021-04-21 20:05:06.124  - info: host.ioBroker-RasPi4 instance system.adapter.knx.0 started with pid 7564
2021-04-21 20:05:08.354  - info: host.ioBroker-RasPi4 instance system.adapter.admin.0 started with pid 7576
2021-04-21 20:05:08.482  - error: knx.0 (7564) knx.0 already running
2021-04-21 20:05:09.149  - error: host.ioBroker-RasPi4 instance system.adapter.knx.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:09.151  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.knx.0 because enabled
2021-04-21 20:05:10.106  - info: host.ioBroker-RasPi4 instance system.adapter.robonect.0 started with pid 7584
2021-04-21 20:05:11.114  - info: host.ioBroker-RasPi4 instance system.adapter.discovery.0 started with pid 7595
2021-04-21 20:05:12.098  - info: admin.0 (7576) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.admin, node: v10.23.0, js-controller: 3.2.16
2021-04-21 20:05:12.209  - info: admin.0 (7576) requesting all states
2021-04-21 20:05:12.211  - info: admin.0 (7576) requesting all objects
2021-04-21 20:05:13.736  - info: admin.0 (7576) Request actual repository...
2021-04-21 20:05:14.802  - info: admin.0 (7576) received all objects
2021-04-21 20:05:15.131  - info: admin.0 (7576) http server listening on port 8081
2021-04-21 20:05:15.132  - info: admin.0 (7576) Use link "http://localhost:8081" to configure.
2021-04-21 20:05:15.739  - info: host.ioBroker-RasPi4 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
2021-04-21 20:05:15.917  - info: host.ioBroker-RasPi4 instance system.adapter.fronius.0 started with pid 7616
2021-04-21 20:05:15.981  - info: host.ioBroker-RasPi4 instance system.adapter.tr-064.0 started with pid 7623
2021-04-21 20:05:16.054  - error: robonect.0 (7584) robonect.0 already running
2021-04-21 20:05:16.060  - warn: robonect.0 (7584) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:17.164  - error: host.ioBroker-RasPi4 instance system.adapter.robonect.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:17.167  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.robonect.0 because enabled
2021-04-21 20:05:17.657  - info: discovery.0 (7595) starting. Version 2.5.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.23.0, js-controller: 3.2.16
2021-04-21 20:05:18.223  - info: host.ioBroker-RasPi4 instance system.adapter.modbus.0 started with pid 7636
2021-04-21 20:05:19.220  - info: host.ioBroker-RasPi4 instance system.adapter.web.0 started with pid 7651
2021-04-21 20:05:19.759  - error: tr-064.0 (7623) tr-064.0 already running
2021-04-21 20:05:19.873  - info: fronius.0 (7616) starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.fronius, node: v10.23.0, js-controller: 3.2.16
2021-04-21 20:05:20.461  - error: host.ioBroker-RasPi4 instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:20.463  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.tr-064.0 because enabled
2021-04-21 20:05:21.253  - error: modbus.0 (7636) modbus.0 already running
2021-04-21 20:05:22.131  - error: host.ioBroker-RasPi4 instance system.adapter.modbus.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:22.133  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.modbus.0 because enabled
2021-04-21 20:05:23.400  - info: admin.0 (7576) Repository received successfully.
2021-04-21 20:05:24.757  - warn: web.0 (7651) slow connection to states DB. Still waiting ...
2021-04-21 20:05:25.028  - info: host.ioBroker-RasPi4 instance system.adapter.javascript.0 started with pid 7675
2021-04-21 20:05:26.255  - info: host.ioBroker-RasPi4 instance system.adapter.info.0 started with pid 7683
2021-04-21 20:05:26.305  - info: host.ioBroker-RasPi4 instance system.adapter.email.0 started with pid 7684
2021-04-21 20:05:27.532  - info: web.0 (7651) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v10.23.0, js-controller: 3.2.16
2021-04-21 20:05:28.350  - info: web.0 (7651) socket.io server listening on port 8082
2021-04-21 20:05:28.384  - info: web.0 (7651) simpleAPI server listening on port 8082
2021-04-21 20:05:28.386  - info: web.0 (7651) Allow states only when user is owner: false
2021-04-21 20:05:28.407  - info: web.0 (7651) http server listening on port 8082
2021-04-21 20:05:29.598  - error: email.0 (7684) email.0 already running
2021-04-21 20:05:29.606  - warn: email.0 (7684) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:32.147  - info: host.ioBroker-RasPi4 instance system.adapter.wled.0 started with pid 7724
2021-04-21 20:05:32.196  - info: host.ioBroker-RasPi4 instance system.adapter.sql.0 started with pid 7730
2021-04-21 20:05:32.474  - error: host.ioBroker-RasPi4 instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:32.475  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.email.0 because enabled
2021-04-21 20:05:32.668  - info: host.ioBroker-RasPi4 instance system.adapter.backitup.0 started with pid 7738
2021-04-21 20:05:33.155  - error: javascript.0 (7675) javascript.0 already running
2021-04-21 20:05:33.166  - warn: javascript.0 (7675) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:33.966  - error: host.ioBroker-RasPi4 instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-04-21 20:05:33.968  - info: host.ioBroker-RasPi4 Restart adapter system.adapter.javascript.0 because enabled
2021-04-21 20:05:35.056  - info: host.ioBroker-RasPi4 instance system.adapter.ping.0 started with pid 7747
2021-04-21 20:05:35.576  - info: info.0 (7683) starting. Version 1.7.14 in /opt/iobroker/node_modules/iobroker.info, node: v10.23.0, js-controller: 3.2.16
2021-04-21 20:05:36.488  - debug: wled.0 (7724) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-04-21 20:05:36.786  - debug: wled.0 (7724) Objects client ready ... initialize now
2021-04-21 20:05:36.812  - debug: wled.0 (7724) Objects create System PubSub Client
2021-04-21 20:05:36.816  - debug: wled.0 (7724) Objects create User PubSub Client
2021-04-21 20:05:36.819  - debug: wled.0 (7724) Objects client initialize lua scripts
2021-04-21 20:05:36.939  - debug: wled.0 (7724) Objects connected to redis: 127.0.0.1:9001
2021-04-21 20:05:37.019  - debug: wled.0 (7724) objectDB connected
2021-04-21 20:05:37.037  - debug: wled.0 (7724) Redis States: Use Redis connection: 127.0.0.1:9000
2021-04-21 20:05:37.085  - debug: wled.0 (7724) States create System PubSub Client
2021-04-21 20:05:37.093  - debug: wled.0 (7724) States create User PubSub Client
2021-04-21 20:05:37.150  - debug: wled.0 (7724) States connected to redis: 127.0.0.1:9000
2021-04-21 20:05:37.153  - debug: wled.0 (7724) statesDB connected
2021-04-21 20:05:37.194  - error: wled.0 (7724) wled.0 already running
2021-04-21 20:05:37.213  - debug: wled.0 (7724) Plugin sentry destroyed
2021-04-21 20:05:37.214  - warn: wled.0 (7724) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-04-21 20:05:37.618  - info: sql.0 (7730) starting. Version 1.15.5 in /opt/iobroker/node_modules/iobroker.sql, node: v10.23.0, js-controller: 3.2.16
2021-04-21 20:05:38.410  - error: wled.0 (7724) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-04-21 20:05:38.415  - error: wled.0 (7724) unhandled promise rejection: Cannot read property 'error' of undefined
2021-04-21 20:05:38.429  - error: wled.0 (7724) TypeError: Cannot read property 'error' of undefined
    at Wled.onUnload (/opt/iobroker/node_modules/iobroker.wled/main.js:97:13)
    at Wled.emit (events.js:198:13)
    at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8620:22)
    at Object.onceWrapper (events.js:286:20)
    at process.emit (events.js:198:13)
    at process.exit (internal/process/per_thread.js:168:15)
    at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:352:25)
    at process._tickCallback (internal/process/next_tick.js:68:7)
2021-04-21 20:05:38.430  - error: wled.0 (7724) Cannot read property 'error' of undefined
      Dutchman 1 Reply Last reply Reply Quote 0
      • Dutchman
        Dutchman Developer Most Active Administrators @jkalver last edited by

        @jkalver sagte in [WLED] LED streifen (WS2812B,WS2811,SK6812,APA102) bedienen:

        Während die anderen Adapter damit umgehen können (siehe beiliegendes log) hat der WLED Adapter ein Problem, sich davon zu erholen.
        Vielleicht hilft das ja bei der Fehlersuche.

        danke, ja das hilft zur estaetigung das diese Innovation das problem loesen wird :
        https://github.com/DrozmotiX/ioBroker.wled/issues/145

        DutchmanNL created this issue in DrozmotiX/ioBroker.wled

        closed Change complete communication logic to WebSocket #145

        1 Reply Last reply Reply Quote 1
        • V
          Vocaris last edited by

          Hallo Gemeinde,
          ich möchte gerne das sicherlich bekannte "Garagen Projekt" umsetze.
          Dafür habe ich jetzt WS2821 und das passende Netzteil bestellt. Dem WEMOS D1 habe ich schon hier und habe diesen mit WLED_0.12.0_ESP8266.bin bespielt. Die Umsetzung am Tor (Start und Stopp des Effektes) möchte ich mit 2 Xiaomi Fensterkontakten realisieren, die ich am Torlauf entsprechend befestige.

          Nun wollte ich dem WEMOS mal testen, ob ds soweit klappt. HAbe hier aber nur einen 10 LED langen WS2801 Streifen. Aber diese Streifen werden ja mittlerweile auch unterstützt. Leider bekomme ich da Ergebnis nicht hin.
          Im WebInterface gibt man den LED Streifen 2801 ein und muss dann die Pin Belegung für Date und Clock angeben. Was kommen dort nun an Werten rein? Das da Pin steht wäre ich vom den physischen Pins ausgegangen.
          Wenn ich also Date an D3 und CLK an D4 des WEMONS hängen möchte, hätte ich jetzt für DATA = 18 und für CLK=17 eingegeben. Aber diese Werte speichert er nicht. Hm OK. Ggf. sind die GPIOS gemeint. Das wäre dann für DATA=0 und für CLK=2. Das speichert er. Aber an meinen LEDs tut sich nix, wenn ich am Farbrad drehe.. Weiß einer was hier zu tun ist.
          Zudem sagt mir der Browser im WI immer 093c2489-971a-4c4d-a90c-1209a888f0c7-image.png
          Weiß auch nicht was das ist.

          Zuletzt bin ich noch Lost was den gesamten Effekt angeht. Wie bekomme ich denn diese ganzen Farbabläufe etc. in den WEMOS rein? Wenn die o.g. Schalter je einen bestimmten Wert annehmen, dann soll ja die "Kirmes" laufen.
          Sind das Werte im WEMOS, die dann je einen Effekt darstellen und diese werden dann z.B. via MQTT durch den ioB angetriggert. Oder muss per MQTT imemr der ganzen "Code" übermittelt werden. Ich bin da leider aktuell komplett aufgeschmissen.

          vorab Danke

          J 1 Reply Last reply Reply Quote 0
          • J
            jkalver @Vocaris last edited by

            @vocaris
            Hi,

            habe das Projekt gerade umgesetzt mit NodeMCU. Welchen Pin Du bei dem WEMOS besetzen musst, kann ich dir nicht sagen.
            Ich habe 2 Endschalter für das Tor installiert, die gehen auf freie Eingänge von meinem KNX Binäreingang. Die Logik für das Schalten der Farben habe ich im X1 drin. Kann man aber bestimmt auch im iobroker mit den Skripten machen.
            Die Farben und Effekte stellst du in der WebOberfläche vom WLED ein und speicherst die als Preset. Über den IOBROKER kannst du dann den Preset setzen.

            Viel Spass
            Jens

            V 1 Reply Last reply Reply Quote 0
            • V
              Vocaris @jkalver last edited by

              @jkalver OK. Ich habe es mir WEMOS und ioB.
              Habe zwar die LEDs noch nicht dran aber habe mal mit den Presets gespeilt. Keine Ahnung was ich da mach aber habe mal drei angelegt.

              9f27e85e-61cc-41df-9a18-9128bf3371a7-image.png

              Aber im MQTT Adapter im ioB sehe ich die nicht

              d00eaf96-f64e-4492-84e2-2a7874118e9d-image.png

              Habe aber immer diese Anzeige untern im Browser "TypeError: Die Eigenschaft 'chcekced' von null kann nicht festgelegt werden"

              J 1 Reply Last reply Reply Quote 0
              • J
                jkalver @Vocaris last edited by jkalver

                @vocaris
                Das sieht bei mir auch ein wenig anders aus.

                7c055ede-fd13-45a8-896d-6ab978c80c42-image.png

                Du musst die gewünschten Farben/Effekte einstellen und dann als Preset speichern. Die kannst Du dann über den iobroker ganz einfach aufrufen
                0b764888-e588-411a-b59d-bccfd81634b9-image.png

                1 Reply Last reply Reply Quote 0
                • M
                  Muchul last edited by

                  Der Wled adapter braucht doch kein mqtt.
                  Die Datenpunkte sind doch alle in wled drin.
                  Screenshot_2021-04-23-15-53-50-715_com.android.chrome.jpg

                  V 1 Reply Last reply Reply Quote 0
                  • V
                    Vocaris @Muchul last edited by

                    @muchul OK fairer Punkt. Danach habe ich gar nicht gesucht. Da bei dem Projekt alles von MQTT gesprochen hat. Habe ich jetzt drin.
                    Jetzt besteht nur noch das Problem warum dER Kl. LED Streifen nicht klappt. Und wie man das Preset richtig konfiguriert

                    J M 2 Replies Last reply Reply Quote 0
                    • J
                      jkalver @Vocaris last edited by

                      @vocaris
                      Ich gehe mal davon aus, dass du die Datenleitung an der richtigen Seite am LED Streifen angeschlossen hast.
                      Nur mal so ein Gedanke...

                      V 1 Reply Last reply Reply Quote 0
                      • M
                        Muchul @Vocaris last edited by

                        @vocaris
                        Wenn du das kabel richtig herum angeschlossen hast und es immer noch nicht geht, setzten d1 mal auf Werkseinstellungen zurück, über die wled Oberfläche.
                        Der sollte direkt laufen.
                        Du hast doch ws2812 leds, oder?

                        V 1 Reply Last reply Reply Quote 0
                        • V
                          Vocaris @Muchul last edited by

                          @muchul nein 2801
                          Und die habe ich im Webinterface auch ausgewählt...

                          M 1 Reply Last reply Reply Quote 0
                          • V
                            Vocaris @jkalver last edited by

                            @jkalver sagte in [WLED] LED streifen (WS2812B,WS2811,SK6812,APA102) bedienen:

                            @vocaris
                            Ich gehe mal davon aus, dass du die Datenleitung an der richtigen Seite am LED Streifen angeschlossen hast.
                            Nur mal so ein Gedanke...

                            Yes habe ich natürlich Pfeil zeigt nach links, also habe ich rechts gelötet..

                            1 Reply Last reply Reply Quote 0
                            • M
                              Muchul @Vocaris last edited by Muchul

                              @vocaris
                              Kennst du das hier schon?
                              https://github.com/Aircoookie/WLED/issues/711

                              @Aircoookie Aircoookie kommentiert am 24. Februar 2020
                              Es werden gpio0 und 2 verwendet, also die Pins D3 und D4.

                              CaptainDario created this issue in Aircoookie/WLED

                              closed Using ws2801 leds #711

                              V 1 Reply Last reply Reply Quote 0
                              • V
                                Vocaris @Muchul last edited by

                                @muchul hei. Ja kenne ich. Wie ich geschrieben habe, habe ich auch dieses beiden Pins am Wemos genutzt. Im WI stehen 2 und 0. Aber dennoch nix zu sehen. Ich gehe davon aus, dass im WI die GPIO Werte eingegeben werden. Also 2 und 0 und nicht 17 und 18. Aber 17 und 18 kann man auch nicht speichern.

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  Muchul @Vocaris last edited by

                                  @vocaris
                                  Sorry, da kann ich leider nicht mehr helfen,
                                  aber du hast ja bei wled dein Problem geschrieben.
                                  Da kommt bestimmt eine Lösung.

                                  V 1 Reply Last reply Reply Quote 0
                                  • V
                                    Vocaris @Muchul last edited by

                                    @muchul Dank dir. Ich habe heute morgen mal das erste St. von dem LED Streifen abgeschnitte. Habe jetzt nur noch 9 LEDs. Neu angelötet und wieder verbunden. Und Zack es geht.
                                    Habe dann 4 Presets erstellt:
                                    rot - SM=0&SS=0&SV=2&S=0&S2=174&GP=1&SP=0&RV=0&SB=255&A=255&R=255&G=0&B=0&W=0&R2=0&G2=0&B2=0&W2=&FX=60&SX=203&IX=246&T=1
                                    grün - SM=0&SS=0&SV=2&S=0&S2=174&GP=1&SP=0&RV=0&SB=255&A=255&R=0&G=255&B=0&W=0&R2=0&G2=0&B2=0&W2=&FX=0&T=1
                                    weiss - SM=0&SS=0&SV=2&S=0&S2=174&GP=1&SP=0&RV=0&SB=255&A=255&R=0&G=0&B=0&W=255&R2=0&G2=0&B2=0&W2=&FX=60&SX=64&IX=113&T=1
                                    spots - SM=0&SS=0&SV=2&S=13&S2=174&GP=7&SP=20&RV=0&SB=255&A=255&W=255&R2=0&G2=0&B2=0&W2=&FX=0&T=1
                                    aus - T=0

                                    Und auch das geht. Bis auf WEISS und SPOTS. Das sehe ich nix. Ggf. liegt es am kurzen Streifen.
                                    Die 2801 habe ich als GRB eingestellt.

                                    M 1 Reply Last reply Reply Quote 0
                                    • J
                                      jkalver @crunchip last edited by

                                      @crunchip
                                      Hi,

                                      Habe vorgestern die Nodejs von v10 auf die letzte v14 upgedated. Seitdem habe ich das Problem mit dem reset der Adapter nicht mehr und Wled läuft auch durch.

                                      crunchip 1 Reply Last reply Reply Quote 1
                                      • crunchip
                                        crunchip Forum Testing Most Active @jkalver last edited by

                                        @jkalver soll heissen, mit node14 läuft es? seltsam🤔

                                        J 1 Reply Last reply Reply Quote 0
                                        • J
                                          jkalver @crunchip last edited by jkalver

                                          @crunchip so sieht es aus😊

                                          crunchip 1 Reply Last reply Reply Quote 0
                                          • M
                                            Muchul @Vocaris last edited by

                                            @vocaris
                                            Die LED s versorgst du aber auch mit zusätzlichem Strom, oder?
                                            Grd von esp und Netzteil auf Stripes aufgelegt?
                                            Plus von esp nicht verbinden.
                                            Reagiert der Stripe auf die einzelnen farben richtig?
                                            Ist das ein rgbw Stripe?
                                            Ich kenne deine Stripes nich, daher die dummen fragen.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.0k
                                            Online

                                            30.4k
                                            Users

                                            76.7k
                                            Topics

                                            1.2m
                                            Posts

                                            adapater adapter neu hier test testen tester wled
                                            73
                                            655
                                            86211
                                            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