Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 2.0 ab sofort im Latest Repo

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 2.0 ab sofort im Latest Repo

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

      So soll es auch sein. Danke

      J 1 Reply Last reply Reply Quote 0
      • J
        Jan1 @apollon77 last edited by

        @apollon77
        So hab die 41er drauf und stoppen geht wieder zügig, allerdings habe ich eben den Email Adapter deinstalliert und dabei hat sich IOBroker erst mal neu gestartet.
        Dazu steht dann nur davon reichlich im LOG:

        host.Beelink.compactgroup1	2019-11-10 09:33:15.051	warn	get state Error: Connection is closed.
        host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
        host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
        host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
        
        apollon77 1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @Jan1 last edited by

          @Jan1 wenn sich iobroker neu gestartet hat muss da aber noch mehr stehen.

          Bitte zeig mal mehr log.

          J 2 Replies Last reply Reply Quote 0
          • J
            Jan1 @apollon77 last edited by

            @apollon77
            Da steht schon mehr, allerdings keine Errors, sondern nur die Neustarts der Adapter:

            sonoff.0	2019-11-10 09:35:12.105	info	(18888) Client [Shelly-Spiegelschrank] connected with secret 1573374912103_8989
            sonoff.0	2019-11-10 09:35:11.895	info	(18888) Client [Sonoff-Flur_1] connected with secret 1573374911890_977
            sonoff.0	2019-11-10 09:35:11.878	info	(18888) Client [Rollladen1-Wohnzimmer] connected with secret 1573374911877_4664
            sonoff.0	2019-11-10 09:35:11.835	info	(18888) Client [Rollladen2-Schlafzimmer] connected with secret 1573374911831_1020
            sonoff.0	2019-11-10 09:35:11.832	info	(18888) Client [SP111-Schrankwand] connected with secret 1573374911831_8089
            sonoff.0	2019-11-10 09:35:11.817	info	(18888) Client [SP111-Vitrine] connected with secret 1573374911813_4773
            sonoff.0	2019-11-10 09:35:11.792	info	(18888) Client [Sonoff-Flur_2] connected with secret 1573374911790_2146
            sonoff.0	2019-11-10 09:35:11.742	info	(18888) Client [Sonoff-Esszimmer-Lampe] connected with secret 1573374911741_7654
            sonoff.0	2019-11-10 09:35:11.723	info	(18888) Client [Sonoff-Bad_Umschalter] connected with secret 1573374911722_2374
            sonoff.0	2019-11-10 09:35:11.709	info	(18888) Client [Rollladen1-Schlafzimmer] connected with secret 1573374911708_4601
            sonoff.0	2019-11-10 09:35:11.621	info	(18888) Client [Rollladen-Bad] connected with secret 1573374911620_5687
            sonoff.0	2019-11-10 09:35:11.468	info	(18888) Client [Shelly-Balkon] connected with secret 1573374911467_5208
            sonoff.0	2019-11-10 09:35:11.393	info	(18888) Client [Shelly-Wäschezimmer] connected with secret 1573374911390_5248
            sonoff.0	2019-11-10 09:35:11.347	info	(18888) Client [Shelly-Küche] connected with secret 1573374911346_4132
            sonoff.0	2019-11-10 09:35:11.300	info	(18888) Client [Sonoff-RF-Bridge] connected with secret 1573374911298_2024
            sonoff.0	2019-11-10 09:35:11.270	info	(18888) Client [Sonoff-Ventilator_Wohnzimmer] connected with secret 1573374911270_3625
            sonoff.0	2019-11-10 09:35:11.230	info	(18888) Client [Shelly-Bad] connected with secret 1573374911228_8964
            sonoff.0	2019-11-10 09:35:11.166	info	(18888) Client [Test-Rollladen] connected with secret 1573374911136_3647
            sonoff.0	2019-11-10 09:35:11.164	info	(18888) Client [Rollladen2-Wohnzimmer] connected with secret 1573374911135_8804
            sonoff.0	2019-11-10 09:35:11.046	info	(18888) Client [Tuya-Theke] connected with secret 1573374911039_2585
            sonoff.0	2019-11-10 09:35:03.357	info	(18888) Starting MQTT authenticated server on port 1883
            sonoff.0	2019-11-10 09:35:03.316	info	(18888) starting. Version 2.3.2 in /opt/iobroker/node_modules/iobroker.sonoff, node: v10.17.0
            host.Beelink	2019-11-10 09:35:01.639	info	instance system.adapter.sonoff.0 started with pid 18888
            host.Beelink	2019-11-10 09:34:57.625	info	instance system.adapter.fritzdect.0 is handled by compact group controller pid 16942
            host.Beelink	2019-11-10 09:34:53.626	info	instance system.adapter.telegram.0 is handled by compact group controller pid 16942
            host.Beelink	2019-11-10 09:34:49.626	info	instance system.adapter.web.0 is handled by compact group controller pid 16942
            wifilight.0	2019-11-10 09:34:47.162	info	(18569) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.wifilight, node: v10.17.0
            host.Beelink	2019-11-10 09:34:45.638	info	instance system.adapter.wifilight.0 started with pid 18569
            host.Beelink	2019-11-10 09:34:41.643	info	instance system.adapter.zigbee.0 started with pid 18409
            vr200.0	2019-11-10 09:34:40.215	info	(18388) devices found: 1
            vr200.0	2019-11-10 09:34:39.365	info	(18388) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.vr200, node: v10.17.0
            host.Beelink	2019-11-10 09:34:37.670	info	instance system.adapter.vr200.0 started with pid 18388
            tr-064-community.0	2019-11-10 09:34:35.460	info	(18228) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.tr-064-community, node: v10.17.0
            host.Beelink	2019-11-10 09:34:33.643	info	instance system.adapter.tr-064-community.0 started with pid 18228
            host.Beelink	2019-11-10 09:34:29.626	info	instance system.adapter.tankerkoenig.0 is handled by compact group controller pid 16942
            host.Beelink	2019-11-10 09:34:29.331	info	instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
            openweathermap.0	2019-11-10 09:34:28.806	info	(18043) Terminated (NO_ERROR): Without reason
            scenes.0	2019-11-10 09:34:27.646	info	(18059) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v10.17.0
            openweathermap.0	2019-11-10 09:34:25.701	info	(18043) starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v10.17.0
            host.Beelink	2019-11-10 09:34:25.691	info	instance system.adapter.scenes.0 started with pid 18059
            iqontrol.0	2019-11-10 09:34:25.452	info	(COMPACT) Deleting unused Objects...
            iqontrol.0	2019-11-10 09:34:25.446	info	(COMPACT) Creating Options...
            node-red.0	2019-11-10 09:34:24.695	warn	10 Nov 09:34:24 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false
            node-red.0	2019-11-10 09:34:24.695	warn	(17869) 10 Nov 09:34:24 - [info] Benutzerverzeichnis: /opt/iobroker/iobroker-data/node-red/
            host.Beelink	2019-11-10 09:34:21.797	info	instance system.adapter.openweathermap.0 started with pid 18043
            host.Beelink	2019-11-10 09:34:21.767	info	instance scheduled system.adapter.openweathermap.0 14 * * * *
            node-red.0	2019-11-10 09:34:19.779	info	(17869) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
            node-red.0	2019-11-10 09:34:19.190	info	(17869) starting. Version 1.13.0 in /opt/iobroker/node_modules/iobroker.node-red, node: v10.17.0
            milight-smart-light.0	2019-11-10 09:34:17.920	info	(17846) main->::milight-smart-light adapter was started successfully!
            milight-smart-light.0	2019-11-10 09:34:17.919	info	(17846) main->::all states were subscribed!
            milight-smart-light.0	2019-11-10 09:34:17.917	info	(17846) main->::all MiLight zones and states were created!
            host.Beelink	2019-11-10 09:34:17.638	info	instance system.adapter.node-red.0 started with pid 17869
            milight-smart-light.0	2019-11-10 09:34:15.315	info	(17846) starting. Version 0.2.7 in /opt/iobroker/node_modules/iobroker.milight-smart-light, node: v10.17.0
            host.Beelink	2019-11-10 09:34:13.641	info	instance system.adapter.milight-smart-light.0 started with pid 17846
            host.Beelink.compactgroup1	2019-11-10 09:34:10.840	info	instance system.adapter.fritzdect.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:34:09.625	info	instance system.adapter.javascript.0 is handled by compact group controller pid 16942
            telegram.0	2019-11-10 09:34:07.536	info	(COMPACT) starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.telegram, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:34:07.107	info	instance system.adapter.telegram.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:34:05.625	info	instance system.adapter.iqontrol.0 is handled by compact group controller pid 16942
            web.0	2019-11-10 09:34:03.193	info	(COMPACT) https server listening on port 8082
            web.0	2019-11-10 09:34:03.192	info	(COMPACT) Allow states only when user is owner: false
            web.0	2019-11-10 09:34:03.191	info	(COMPACT) Secure simpleAPI server listening on port 8082
            web.0	2019-11-10 09:34:03.186	info	(COMPACT) Secure socket.io server listening on port 8082
            web.0	2019-11-10 09:34:03.005	info	(COMPACT) starting. Version 2.4.9 in /opt/iobroker/node_modules/iobroker.web, node: v10.17.0
            host.Beelink	2019-11-10 09:34:02.924	info	instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
            host.Beelink.compactgroup1	2019-11-10 09:34:02.654	info	instance system.adapter.web.0 started in COMPACT mode
            tankerkoenig.0	2019-11-10 09:34:02.603	info	(COMPACT) Reading data from tankerkoenig ...
            tankerkoenig.0	2019-11-10 09:34:02.584	info	(COMPACT) Sync time set to 9 minutes or 540000 ms
            tankerkoenig.0	2019-11-10 09:34:02.582	info	(COMPACT) starting. Version 2.0.6 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v10.17.0
            ical.0	2019-11-10 09:34:02.405	info	(17395) Terminated (NO_ERROR): Without reason
            host.Beelink	2019-11-10 09:34:01.629	info	instance system.adapter.iot.0 is handled by compact group controller pid 16942
            host.Beelink.compactgroup1	2019-11-10 09:33:58.655	info	instance system.adapter.tankerkoenig.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:57.625	info	instance system.adapter.info.0 is handled by compact group controller pid 16942
            ical.0	2019-11-10 09:33:56.464	info	(17395) processing URL: Schichtplan https://calendar.google.com/calendar/ical/q1c63lrjub78ejlmol28r399tk%40group.calendar.google.com/private-93d5d08eac1c8f5bfd5205f4984b0d93/basic.ics
            ical.0	2019-11-10 09:33:55.907	info	(17395) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:55.550	info	instance system.adapter.javascript.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:53.639	info	instance system.adapter.ical.0 started with pid 17395
            host.Beelink	2019-11-10 09:33:53.626	info	instance scheduled system.adapter.ical.0 1 0,6,12,18 * * *
            enigma2.0	2019-11-10 09:33:51.867	info	(16960) enigma2 Verbunden!
            iqontrol.0	2019-11-10 09:33:51.240	info	(COMPACT) Creating Views...
            iqontrol.0	2019-11-10 09:33:50.816	info	(COMPACT) Creating Toolbar...
            iqontrol.0	2019-11-10 09:33:50.815	info	(COMPACT) starting. Version 0.2.13 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:50.651	info	instance system.adapter.iqontrol.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:49.627	info	instance system.adapter.history.0 is handled by compact group controller pid 16942
            iot.0	2019-11-10 09:33:48.060	info	(COMPACT) Connection changed: connect
            iot.0	2019-11-10 09:33:47.234	info	(COMPACT) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
            iot.0	2019-11-10 09:33:47.228	info	(COMPACT) starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:46.873	info	instance system.adapter.iot.0 started in COMPACT mode
            info.0	2019-11-10 09:33:46.415	info	(COMPACT) Popup news was read...
            info.0	2019-11-10 09:33:46.314	info	(COMPACT) Reading process data every 8 seconds.
            info.0	2019-11-10 09:33:46.198	info	(COMPACT) Reading user data every 8 seconds.
            info.0	2019-11-10 09:33:46.070	info	(COMPACT) Reading CPU temp data every 3 seconds.
            info.0	2019-11-10 09:33:46.067	info	(COMPACT) Reading memory data every 3 seconds.
            info.0	2019-11-10 09:33:45.957	info	(COMPACT) Reading disk data every 8 seconds.
            info.0	2019-11-10 09:33:45.952	info	(COMPACT) Reading battery data every 8 seconds.
            info.0	2019-11-10 09:33:45.908	info	(COMPACT) Reading CPU data every 3 seconds.
            info.0	2019-11-10 09:33:45.899	info	(COMPACT) Reading CPU current speed every 3 seconds.
            host.Beelink	2019-11-10 09:33:45.625	info	instance system.adapter.harmony.0 is handled by compact group controller pid 16942
            info.0	2019-11-10 09:33:44.937	info	(COMPACT) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.info, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:43.231	info	instance system.adapter.info.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:41.649	info	instance system.adapter.google-sharedlocations.0 started with pid 16990
            host.Beelink	2019-11-10 09:33:41.367	info	instance system.adapter.feiertage.0 terminated with code 0 (NO_ERROR)
            feiertage.0	2019-11-10 09:33:40.842	info	(16975) Terminated (NO_ERROR): Without reason
            feiertage.0	2019-11-10 09:33:40.299	info	(16975) adapter feiertage objects written
            feiertage.0	2019-11-10 09:33:40.294	info	(16975) Next holiday: 1. Weihnachtstag is in 45 days on 25.12.2019
            feiertage.0	2019-11-10 09:33:40.246	info	(16975) starting. Version 1.0.13 in /opt/iobroker/node_modules/iobroker.feiertage, node: v10.17.0
            history.0	2019-11-10 09:33:39.215	info	(COMPACT) starting. Version 1.8.7 in /opt/iobroker/node_modules/iobroker.history, node: v10.17.0
            harmony.0	2019-11-10 09:33:38.847	info	(COMPACT) [PROCESS] Synced hub config for Harmony Hub (192.168.100.44)
            host.Beelink.compactgroup1	2019-11-10 09:33:38.661	info	instance system.adapter.history.0 started in COMPACT mode
            harmony.0	2019-11-10 09:33:37.897	info	(COMPACT) [CONNECT] Connected to Harmony Hub (192.168.100.44)
            host.Beelink	2019-11-10 09:33:37.653	info	instance system.adapter.feiertage.0 started with pid 16975
            host.Beelink	2019-11-10 09:33:37.639	info	instance scheduled system.adapter.feiertage.0 0 0 * * *
            harmony.0	2019-11-10 09:33:36.759	info	(COMPACT) [CONNECT] Connecting to Harmony Hub (192.168.100.44)
            harmony.0	2019-11-10 09:33:36.676	info	(COMPACT) [DISCOVER] Discovered Harmony Hub (192.168.100.44) and will try to connect
            enigma2.0	2019-11-10 09:33:36.619	info	(16960) starting Polling every 15000 ms
            enigma2.0	2019-11-10 09:33:36.582	info	(16960) starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.enigma2, node: v10.17.0
            harmony.0	2019-11-10 09:33:35.424	info	(COMPACT) [DISCOVER] Searching for Harmony Hubs on 255.255.255.255
            harmony.0	2019-11-10 09:33:35.417	info	(COMPACT) starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.harmony, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:34.876	info	instance system.adapter.harmony.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:33.637	info	instance system.adapter.enigma2.0 started with pid 16960
            ble.0	2019-11-10 09:33:31.480	info	(COMPACT) starting scan for services ["fe95"]
            ble.0	2019-11-10 09:33:31.197	info	(COMPACT) monitored services: fe95
            ble.0	2019-11-10 09:33:31.194	info	(COMPACT) enabled plugins: Xiaomi, mi-flora, _default
            ble.0	2019-11-10 09:33:31.192	info	(COMPACT) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
            ble.0	2019-11-10 09:33:31.130	info	(COMPACT) starting. Version 0.10.1 in /opt/iobroker/node_modules/iobroker.ble, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:30.672	info	instance system.adapter.ble.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:29.625	info	instance system.adapter.ble.0 is handled by compact group controller pid 16942
            alexa2.0	2019-11-10 09:33:28.880	info	(COMPACT) Alexa-Push-Connection established. Disable Polling
            alexa2.0	2019-11-10 09:33:28.611	info	(COMPACT) Device-type:A1RABVCI4QCIKC (TIMERS_AND_ALARMS,FAR_FIELD_WAKE_WORD,AUDIO_PLAYER,CHANGE_NAME,LEMUR_ALPHA,AUDIBLE,KINDLE_BOOKS,DEREGISTER_DEVICE,EARCONS,SLEEP,FLASH_BRIEFING,SUPPORT_CALEND
            alexa2.0	2019-11-10 09:33:28.611	info	(COMPACT) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
            alexa2.0	2019-11-10 09:33:28.610	info	(COMPACT) Unknown Device, but enabling commands, Try it and report back if commands work.
            alexa2.0	2019-11-10 09:33:28.606	info	(COMPACT) Device-type:A2XPGY5LRKB9BE (VOLUME_SETTING,TIMERS_AND_ALARMS,AUDIO_PLAYER,CHANGE_NAME,AUDIBLE,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,KINDLE_BOOKS,DEREGISTER_DEVICE,SLEEP,AMAZON_MUSIC,PERSIS
            alexa2.0	2019-11-10 09:33:28.606	info	(COMPACT) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
            alexa2.0	2019-11-10 09:33:28.606	info	(COMPACT) Unknown Device, but enabling commands, Try it and report back if commands work.
            backitup.0	2019-11-10 09:33:28.316	info	(COMPACT) [total] backup was activated at 03:00 every 7 day(s)
            backitup.0	2019-11-10 09:33:28.304	info	(COMPACT) [minimal] backup was activated at 02:00 every 3 day(s)
            backitup.0	2019-11-10 09:33:28.292	info	(COMPACT) starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:27.593	info	instance system.adapter.backitup.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:25.626	info	instance system.adapter.backitup.0 is handled by compact group controller pid 16942
            alexa2.0	2019-11-10 09:33:23.423	info	(COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:22.712	info	instance system.adapter.alexa2.0 started in COMPACT mode
            host.Beelink	2019-11-10 09:33:21.628	info	instance system.adapter.alexa2.0 is handled by compact group controller pid 16942
            admin.0	2019-11-10 09:33:21.204	info	(COMPACT) Use link "https://localhost:8081" to configure.
            admin.0	2019-11-10 09:33:21.203	info	(COMPACT) https server listening on port 8081
            admin.0	2019-11-10 09:33:21.101	info	(COMPACT) received all objects
            admin.0	2019-11-10 09:33:20.143	info	(COMPACT) requesting all objects
            admin.0	2019-11-10 09:33:20.142	info	(COMPACT) requesting all states
            admin.0	2019-11-10 09:33:20.126	info	(COMPACT) starting. Version 3.6.12 in /opt/iobroker/node_modules/iobroker.admin, node: v10.17.0
            host.Beelink.compactgroup1	2019-11-10 09:33:19.210	info	instance system.adapter.admin.0 started in COMPACT mode
            host.Beelink.compactgroup1	2019-11-10 09:33:18.635	info	starting 14 instances
            host.Beelink.compactgroup1	2019-11-10 09:33:18.419	info	connected to Objects and States
            host.Beelink.compactgroup1	2019-11-10 09:33:18.301	info	iobroker.js-controller version 2.0.41 js-controller starting
            host.Beelink	2019-11-10 09:33:17.649	info	instance system.adapter.admin.0 is handled by compact group controller pid 16942
            host.Beelink	2019-11-10 09:33:17.637	info	start controller for compactgroup 1
            host.Beelink	2019-11-10 09:33:17.621	info	starting 27 instances
            host.Beelink	2019-11-10 09:33:17.556	info	28 instances found
            host.Beelink	2019-11-10 09:33:17.385	info	connected to Objects and States
            host.Beelink	2019-11-10 09:33:16.826	info	ip addresses: 192.168.100.10 2a01:c23:7850:7c00:2054:a3b9:66c1:57ec 2a01:c23:7850:7c00:8639:beff:fe16:3b2 fe80::8639:beff:fe16:3b2 fe80::8d8:9fff:fe12:db29
            host.Beelink	2019-11-10 09:33:16.824	info	hostname: Beelink, node: v10.17.0
            host.Beelink	2019-11-10 09:33:16.823	info	Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
            host.Beelink	2019-11-10 09:33:16.818	info	iobroker.js-controller version 2.0.41 js-controller starting
            host.Beelink.compactgroup1	2019-11-10 09:33:15.059	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.059	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.059	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.059	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.058	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.057	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.057	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.057	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.057	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.057	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.057	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.056	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.055	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.054	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.053	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.053	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.053	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.053	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.053	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.053	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.052	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.052	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.052	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.052	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.052	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.051	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.051	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.051	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.051	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.051	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.050	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.049	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.049	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.049	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.049	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.049	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.049	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.048	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.047	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.046	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.046	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.046	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.046	warn	get state Error: Connection is closed.
            host.Beelink.compactgroup1	2019-11-10 09:33:15.046	warn	get state Error: Connection is closed.
            
            
            apollon77 1 Reply Last reply Reply Quote 0
            • J
              Jan1 @apollon77 last edited by

              @apollon77
              nächstes Problem wenn ich iQontrol im IOBroker aufrufe:
              c8d6c498-e4fa-4aa2-995b-f4161201be79-grafik.png

              BBTown 1 Reply Last reply Reply Quote 0
              • BBTown
                BBTown @Jan1 last edited by

                @Jan1 sagte in js-controller 2.0 ab sofort im Latest Repo:

                wenn ich iQontrol im IOBroker aufrufe

                hast Du ggf. etwas von http auf https umgestellt?
                Es wird ein Zertifikat erwartet
                Über "erweitert" kommst Du in den Dialog die Seite dennoch aufrufen zu können

                J 1 Reply Last reply Reply Quote 0
                • J
                  Jan1 @BBTown last edited by

                  @BBTown
                  Es steht die ganze Zeit schon auf HTTPS und damit hatte ich das Problem noch nicht.
                  Die Seite lässt sich im IOBroker auch nicht mit "erweitert" öffnen, da hier nur "zurück" möglich ist. Wenn ich sie normal im Firefox öffne, kommt diese Meldung auch, kann aber mit erweitert geöffnet werden. Im Anschluss geht es auch im IOBroker wieder.
                  Somit nicht tragisch, aber seltsam, weil es die ganze Zeit eigentlich auch ohne diese Meldung funktioniert hatte und außer JS Update wurde nicht wirklich was geändert.

                  BBTown 1 Reply Last reply Reply Quote 0
                  • BBTown
                    BBTown @Jan1 last edited by

                    @Jan1
                    ist ggf. ein Zertifikat abgelaufen?
                    Wenn es viele Aktualisierungen gibt (upates) kann es auch sein, dass ein Zertifikat bzw. eine Nachfrage erenut kommt.

                    Bei mir ist es bspw. so wenn ich ein Update bei Proxmox durchführe, dass beim ersten nächsten Start auch dieser Dialog kommt und dann erst einmal wieder Ruhe ist (sorry, ich kann das nicht besser/fundierter erkläutern).

                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @Jan1 last edited by

                      @Jan1 mehr bitte. Das starten nach dem Crash ist irrelevant. Brauche logs von BEVOR das connection close kam. Das ist nur die Auswirkung weil Controller weg war.

                      J 1 Reply Last reply Reply Quote 0
                      • apollon77
                        apollon77 last edited by

                        Die 2.0.41 hat tiefere Zertifikat Checks drin und generiert wenn nötig ein neues ssl Zertifikat.

                        Es wird die key länge geprüft, die Gültigkeit - also ob abgelaufen - und auch das es nicht länger gültig ist als 825 Tage (iOS 13 Anforderung). Die 1.5.x hat schon alte Zertifikate ersetzt aber mit einem was 5 Jahre gültig ist. Das ist für die neuen Apple Vorgaben zu lang.

                        Daher musst du denke nur das neue Zertifikat akzeptieren (so wie irgendwann früher mal)

                        1 Reply Last reply Reply Quote 0
                        • J
                          Jan1 @apollon77 last edited by Jan1

                          @apollon77
                          Da steht nicht mehr drin.
                          Ich installiere jetzt noch mal den Mail Adapter und schau ob mir das System beim Deinstallieren wieder abschmiert.
                          Hier das komplette Log nach dem IOBroker beim Deinstallieren wieder abgeschmiert ist:
                          iobroker.2019-11-10.log
                          restart.log

                          Ich denke, dass der Email Adpter ein Problem hat, da er selbst wenn ich den compact modus aktiviere, zwar die Meldung in der Konsole kommt, dass der Modus geändert wurde, aber immer noch auf disabled steht:

                          root@Beelink:/opt/iobroker# iobroker compact email.0 enable 2
                          This adapter does not support compact mode. The below settings will have no effect!
                          
                          Compact mode enabled for instance: true
                          Compact group:                     --> 2
                          Instance settings for "email.0" are changed.
                          root@Beelink:/opt/iobroker# iobroker list instances
                          + system.adapter.admin.0                 : admin                 -  enabled, compact enabled (group 1), port: 8081, bind: 0.0.0.0 (SSL), run as: admin
                          + system.adapter.alexa2.0                : alexa2                -  enabled, compact enabled (group 1)
                          + system.adapter.backitup.0              : backitup              -  enabled, compact enabled (group 1)
                          + system.adapter.ble.0                   : ble                   -  enabled, compact enabled (group 1)
                          + system.adapter.email.0                 : email                 -  enabled, compact disabled
                          
                          
                          apollon77 1 Reply Last reply Reply Quote 0
                          • apollon77
                            apollon77 @Jan1 last edited by

                            @Jan1 sagte in js-controller 2.0 ab sofort im Latest Repo:

                            This adapter does not support compact mode. The below settings will have no effect!

                            Das sagt an sich schonmal das email bisher compact mode nicht unterstützt. Von daher kann der auch nicht im compact mode laufen.

                            Sonst gratuliere, hast noch nen Bug gefunden 🙂 Der passiert wenn man eine Instanz löscht und der Adapter da noch läuft. Würde aber erstmal keine extra neue Version machen sondern warten was noch kommt.

                            J 1 Reply Last reply Reply Quote 0
                            • J
                              Jan1 @apollon77 last edited by

                              @apollon77
                              Ja jetzt sehe ich es auch, voll überlesen😁
                              Der Bug scheint aber neu zu sein, da ich bis jetzt noch nie eine Instanz gestoppt hatte, bevor ich deinstalliert habe. Was solls, so oft deinstalliere ich eigentlich auch nicht und wenn man es weiß kann man auch damit leben.

                              sigi234 apollon77 2 Replies Last reply Reply Quote 0
                              • sigi234
                                sigi234 Forum Testing Most Active @Jan1 last edited by

                                @Jan1 sagte in js-controller 2.0 ab sofort im Latest Repo:

                                Der Bug scheint aber neu zu sein, da ich bis jetzt noch nie eine Instanz gestoppt hatte, bevor ich deinstalliert habe

                                Da mache ich immer , vorher stoppen. 😀

                                1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 @Jan1 last edited by

                                  @Jan1 ja er ist neu. Hat sich bei den Compact Modus Umbauarbeiten eingeschlichen. Aber ist ok. Fixen wir (bzw GitHub ist schon gefixt)

                                  1 Reply Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 last edited by

                                    So, und weil es so schön ist (und doch noch ein paar Kleinigkeiten aufgekommen sind):

                                    2.0.42 ist verfügbar im latest ab gleich:

                                    • (Apollon77) Correct error message if certificate can not be parsed
                                    • (bluefox) Fix upload of material adapter
                                    • (Apollon77) prevent crash when adapter instance is deleted which is also running currently and if stopped by deletion
                                    • (bluefox) make sure getForeignStates do not modify the input ids list
                                    • (Apollon77) enhance list instances and only show compact infos if adapter supports it
                                    1 Reply Last reply Reply Quote 0
                                    • MathiasJ
                                      MathiasJ last edited by

                                      2.0.42 ist bei mir jetzt on.
                                      War nur ein kleines Gezehter.
                                      Erst beim Slave den Update gemacht.
                                      dann beim Master. da hat er mir dann Fehlermeldungen gebracht.
                                      Nach dem Fix alles nochmal, da hat er aber kein Update mehr gemacht weil iobroker "up to date".
                                      Komisch, komisch...... naja, die neue Version ist drauf.

                                      apollon77 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @MathiasJ last edited by

                                        @MathiasJ in solchen Fällen sind die genauen Fehlermeldungen halt extrem interessant. Waren vllt ja auch nur Warnungen.

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

                                          hi...nach dem ich einige Files unter 0_userdata.0 abgelegt hatte, bekomme ich nun einen Fehler im BackupIt

                                          ERROR] [minimal] - /opt/iobroker/node_modules/standard-as-callback/built/index.js:6
                                                  throw e;
                                                  ^
                                          
                                          Error: EISDIR: illegal operation on a directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/files/0_userdata.0/files/icons/thermo/'
                                              at Object.openSync (fs.js:443:3)
                                              at Object.writeFileSync (fs.js:1194:35)
                                              at objects.readFile (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:57:24)
                                              at _getBinaryState (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInRedis.js:520:13)
                                              at client.getBuffer (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInRedis.js:329:17)
                                              at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
                                              at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                                              at process._tickCallback (internal/process/next_tick.js:68:7)
                                          
                                          [DEBUG] [minimal] - done
                                          

                                          Damit ich auch mal prüfen kann welches Files überhaupt da liegen, würde ich gerne auch darauf mit WSCP zugreifen wollen. Aber ich finde kein Folder mit 0_userdata.0 ... Was kann ich tun, um das zu prüfen?

                                          apollon77 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @msauer last edited by

                                            @msauer Ich tippe eher das eine deiner obigen Versuche wo du einen Verzeichnisnamen angegeben hast dazu geführt haben das der Index kaputt ist. Er denkt das ein File da liegt wo eigentlich ein verzeichnis ist.

                                            Ich schaue das ich das noch abfange.
                                            Für dich: Bitte 2.0.42 installieren, ioBroker stoppen! Dann dort in /op/iobroker/iobroker-data/files/0_userdata.0 das _data.json löschen.
                                            Dann 'iobroker file sync" aufrufen - damit sollte der Index neu erstellt werden.

                                            Dann neu versuchen bitte

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            489
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            89
                                            1052
                                            262426
                                            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