NEWS
System & Admin Upgrade "exited with code 25" Start-Schleife?
ioBroker Allgemein
75
Beiträge
3
Kommentatoren
4.1k
Aufrufe
3
Watching
-
Joooooh....
Von dem anderen Chaos abgesehen: Setz den ham.0 auf ein gescheites Log-Level. Dann ist auch das Log kürzer... -
@thomas-braun Geht das per CommandoZeile? Die UI schmiert ab bevor ich das hinbekomme
-
hmersch@RoofServer:/opt/iobroker$ iob logs 2025-05-27 19:01:56.981 - info: sql.0 (129913) enabled logging of hm-rega.0.44417, Alias=false, 88 points now activated 2025-05-27 19:01:56.981 - info: sql.0 (129913) enabled logging of hm-rega.0.51326, Alias=false, 89 points now activated 2025-05-27 19:01:56.981 - info: sql.0 (129913) enabled logging of hm-rega.0.51327, Alias=false, 90 points now activated 2025-05-27 19:01:56.981 - info: sql.0 (129913) enabled logging of tr-064.0.states.wps, Alias=false, 91 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlan, Alias=false, 92 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlan24, Alias=false, 93 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlan50, Alias=false, 94 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlanGuest, Alias=false, 95 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlan24Password, Alias=false, 96 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlan50Password, Alias=false, 97 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.wlanGuestPassword, Alias=false, 98 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.abIndex, Alias=false, 99 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.ab, Alias=false, 100 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.ring, Alias=false, 101 points now activated 2025-05-27 19:01:56.982 - info: sql.0 (129913) enabled logging of tr-064.0.states.reconnectInternet, Alias=false, 102 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of tr-064.0.states.command, Alias=false, 103 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of tr-064.0.states.commandResult, Alias=false, 104 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of tr-064.0.states.externalIP, Alias=false, 105 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of tr-064.0.states.reboot, Alias=false, 106 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of tr-064.0.calllists.htmlTemplate.htmlTemplate, Alias=false, 107 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of tr-064.0.callmonitor.toPauseState, Alias=false, 108 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of hm-rpc.1.OEQ0431543.1.STATE, Alias=false, 109 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of hm-rpc.1.OEQ0431360.1.STATE, Alias=false, 110 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of hm-rpc.1.OEQ0433923.1.STATE, Alias=false, 111 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of javascript.0.Klima.rel_Feuchte, Alias=false, 112 points now activated 2025-05-27 19:01:56.983 - info: sql.0 (129913) enabled logging of javascript.0.Klima.Temperatur, Alias=false, 113 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.adopt_state, Alias=false, 114 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.license_state, Alias=false, 115 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.na-state, Alias=false, 116 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.ng-state, Alias=false, 117 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.port_table.Main.stp_state, Alias=false, 118 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.port_table.Secondary.stp_state, Alias=false, 119 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.state, Alias=false, 120 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath0.state, Alias=false, 121 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath1.state, Alias=false, 122 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath3.state, Alias=false, 123 points now activated 2025-05-27 19:01:56.984 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath4.state, Alias=false, 124 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.license_state, Alias=false, 125 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.na-state, Alias=false, 126 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.ng-state, Alias=false, 127 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.state, Alias=false, 128 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath0.state, Alias=false, 129 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath1.state, Alias=false, 130 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath3.state, Alias=false, 131 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath4.state, Alias=false, 132 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.state_expire, Alias=false, 133 points now activated 2025-05-27 19:01:56.985 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.state_expire, Alias=false, 134 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath2.state, Alias=false, 135 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath5.state, Alias=false, 136 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath6.state, Alias=false, 137 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath2.state, Alias=false, 138 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath5.state, Alias=false, 139 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath6.state, Alias=false, 140 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of hm-rpc.1.OEQ0473422.1.STATE, Alias=false, 141 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of hm-rpc.1.OEQ0212930.1.STATE, Alias=false, 142 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of hm-rpc.1.OEQ0212930.2.STATE, Alias=false, 143 points now activated 2025-05-27 19:01:56.986 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath7.state, Alias=false, 144 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.vap_table.ath8.state, Alias=false, 145 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath7.state, Alias=false, 146 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.vap_table.ath8.state, Alias=false, 147 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of hm-rega.0.57688, Alias=false, 148 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of javascript.0.localLoggerMailStripped, Alias=false, 149 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of hm-rega.0.64620, Alias=false, 150 points now activated 2025-05-27 19:01:56.987 - info: sql.0 (129913) enabled logging of hm-rega.0.1851, Alias=false, 151 points now activated 2025-05-27 19:01:56.988 - info: sql.0 (129913) enabled logging of hm-rpc.2.0001D3C99C72E0.2.STATE, Alias=false, 152 points now activated 2025-05-27 19:01:56.988 - info: sql.0 (129913) enabled logging of hm-rpc.2.0001D3C99C72E0.6.POWER, Alias=false, 153 points now activated 2025-05-27 19:01:56.988 - info: sql.0 (129913) enabled logging of ping.0.RoofServer.172_16_100_1.alive, Alias=false, 154 points now activated 2025-05-27 19:01:56.988 - info: sql.0 (129913) enabled logging of ping.0.RoofServer.wg_mersch_it.alive, Alias=false, 155 points now activated 2025-05-27 19:01:56.988 - info: sql.0 (129913) enabled logging of 0_userdata.0.RegensensorPRGDetectedRain, Alias=false, 156 points now activated 2025-05-27 19:01:56.988 - info: sql.0 (129913) enabled logging of ping.0.RoofServer.google_de.alive, Alias=false, 157 points now activated 2025-05-27 19:01:56.989 - info: sql.0 (129913) enabled logging of 0_userdata.0.RegensensorPRGDiffWertHistory, Alias=false, 158 points now activated 2025-05-27 19:01:56.989 - info: sql.0 (129913) enabled logging of sonoff.0.gosuna-1.ENERGY_Power, Alias=false, 159 points now activated 2025-05-27 19:01:56.989 - info: sql.0 (129913) enabled logging of sonoff.0.gosuna-2.ENERGY_Power, Alias=false, 160 points now activated 2025-05-27 19:01:56.989 - info: sql.0 (129913) enabled logging of hm-rpc.2.000D5BE9A4DC9A.1.AVERAGE_ILLUMINATION, Alias=false, 161 points now activated 2025-05-27 19:01:56.989 - info: sql.0 (129913) enabled logging of hm-rpc.2.000D5BE9A4DC9A.1.CURRENT_ILLUMINATION, Alias=false, 162 points now activated 2025-05-27 19:01:56.990 - info: sql.0 (129913) enabled logging of mielecloudservice.0.000175975877.Status, Alias=false, 163 points now activated 2025-05-27 19:01:56.990 - info: sql.0 (129913) enabled logging of easee.1.EH3ZHB6M.status.chargerOpMode, Alias=false, 164 points now activated 2025-05-27 19:01:56.990 - info: sql.0 (129913) enabled logging of easee.1.EH3ZHB6M.status.totalPower, Alias=false, 165 points now activated 2025-05-27 19:01:56.990 - info: sql.0 (129913) enabled logging of easee.1.EH3ZHB6M.status.outputCurrent, Alias=false, 166 points now activated 2025-05-27 19:01:56.990 - info: sql.0 (129913) enabled logging of easee.1.EH3ZHB6M.status.lifetimeEnergy, Alias=false, 167 points now activated 2025-05-27 19:01:56.991 - info: sql.0 (129913) enabled logging of wiegand-tcpip.0.controllers.125042571.1.unlocked, Alias=false, 168 points now activated 2025-05-27 19:01:56.991 - info: sql.0 (129913) enabled logging of nut.0.battery.charge, Alias=false, 169 points now activated 2025-05-27 19:01:56.991 - info: sql.0 (129913) enabled logging of hm-rpc.2.002A1D89B50332.1.LOCK_TARGET_LEVEL, Alias=false, 170 points now activated 2025-05-27 19:01:56.991 - info: sql.0 (129913) enabled logging of hm-rpc.2.002A1D89B50332.1.PROCESS, Alias=false, 171 points now activated 2025-05-27 19:01:56.991 - info: sql.0 (129913) enabled logging of hm-rpc.2.002A1D89B50332.1.LOCK_STATE, Alias=false, 172 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of hm-rpc.2.002A1D89B50332.1.ACTIVITY_STATE, Alias=false, 173 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of hm-rpc.2.000EDF29922C40.1.HUMIDITY, Alias=false, 174 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of hm-rpc.2.000EDF29922C40.1.ACTUAL_TEMPERATURE, Alias=false, 175 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of hm-rega.0.2198, Alias=false, 176 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of modbus.0.inputRegisters.30775_Wirkleistung_Gesamt, Alias=false, 177 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of parser.0.RelaisWP-1, Alias=false, 178 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of evcc.0.loadpoint.1.status.chargePower, Alias=false, 179 points now activated 2025-05-27 19:01:56.992 - info: sql.0 (129913) enabled logging of evcc.0.loadpoint.1.status.charging, Alias=false, 180 points now activated 2025-05-27 19:01:56.993 - info: sql.0 (129913) enabled logging of opendtu.0.total.yieldday, Alias=false, 181 points now activated 2025-05-27 19:01:56.993 - info: sql.0 (129913) enabled logging of opendtu.0.total.yieldtotal, Alias=false, 182 points now activated 2025-05-27 19:01:56.993 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1068_soc, Alias=false, 183 points now activated 2025-05-27 19:01:56.993 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1069_energy_counter_ac_to_dc, Alias=false, 184 points now activated 2025-05-27 19:01:56.993 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1078_grid_power, Alias=false, 185 points now activated 2025-05-27 19:01:56.994 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1088_PV-sensor_power, Alias=false, 186 points now activated 2025-05-27 19:01:56.994 - info: sql.0 (129913) enabled logging of 0_userdata.0.PowerMgtLoensweg.Varta-PowerConsumed, Alias=false, 187 points now activated 2025-05-27 19:01:56.994 - info: sql.0 (129913) enabled logging of 0_userdata.0.PowerMgtLoensweg.Varta-PowerProvided, Alias=false, 188 points now activated 2025-05-27 19:01:56.994 - info: sql.0 (129913) enabled logging of modbus.0.inputRegisters.30513_Gesamtertrag, Alias=false, 189 points now activated 2025-05-27 19:01:56.994 - info: sql.0 (129913) enabled logging of modbus.0.inputRegisters.30517_Tag_Energie, Alias=false, 190 points now activated 2025-05-27 19:01:58.614 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 129928 2025-05-27 19:02:00.955 - info: telegram.0 (129928) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:01.365 - error: telegram.0 (129928) Failed sending [chatId - 1173210274]: Error: ETELEGRAM: 403 Forbidden: bot was blocked by the user 2025-05-27 19:02:02.694 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 129955 2025-05-27 19:02:05.045 - info: tr-064.0 (129955) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.tr-064, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:06.683 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130003 2025-05-27 19:02:08.628 - info: hm-rpc.0 (130003) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:08.943 - info: hm-rpc.0 (130003) binrpc server is trying to listen on 0.0.0.0:18701 2025-05-27 19:02:08.944 - info: hm-rpc.0 (130003) binrpc client is trying to connect to 192.168.66.111:8701/ with ["xmlrpc_bin://192.168.66.75:18701","RoofServer:hm-rpc.0:c7b8c8d0ec070239c073f823598ca100"] 2025-05-27 19:02:09.122 - info: hm-rpc.0 (130003) binrpc -> listDevices 144 2025-05-27 19:02:09.249 - info: hm-rpc.0 (130003) new CUxD devices/channels after filter: 0 2025-05-27 19:02:09.250 - info: hm-rpc.0 (130003) Connected 2025-05-27 19:02:10.687 - info: host.RoofServer instance system.adapter.hm-rpc.1 in version "2.0.2" started with pid 130018 2025-05-27 19:02:12.522 - info: hm-rpc.1 (130018) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:12.833 - info: hm-rpc.1 (130018) binrpc server is trying to listen on 0.0.0.0:12001 2025-05-27 19:02:12.834 - info: hm-rpc.1 (130018) binrpc client is trying to connect to 192.168.66.111:2001/ with ["xmlrpc_bin://192.168.66.75:12001","RoofServer:hm-rpc.1:ebead5b50e21151ad739f1104db88c62"] 2025-05-27 19:02:12.850 - info: hm-rpc.1 (130018) binrpc <- system.listMethods ["RoofServer:hm-rpc.1:ebead5b50e21151ad739f1104db88c62"] 2025-05-27 19:02:12.871 - info: hm-rpc.1 (130018) binrpc <- listDevices ["RoofServer:hm-rpc.1:ebead5b50e21151ad739f1104db88c62"] 2025-05-27 19:02:13.045 - info: hm-rpc.1 (130018) binrpc -> 344 devices 2025-05-27 19:02:13.536 - info: hm-rpc.1 (130018) Connected 2025-05-27 19:02:14.615 - info: host.RoofServer instance system.adapter.hm-rega.0 in version "5.1.0" started with pid 130033 2025-05-27 19:02:14.884 - info: sql.0 (129913) changed history configuration to pin detected datatype for modbus.1.holdingRegisters.1078_grid_power 2025-05-27 19:02:16.417 - info: hm-rega.0 (130033) starting. Version 5.1.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:16.617 - info: hm-rega.0 (130033) subscribe hm-rpc.1.BidCoS-RF.50.PRESS_SHORT 2025-05-27 19:02:16.781 - info: hm-rega.0 (130033) ReGaHSS 192.168.66.111 up 2025-05-27 19:02:16.817 - info: hm-rega.0 (130033) time difference local-ccu 1s 2025-05-27 19:02:18.710 - info: host.RoofServer instance scheduled system.adapter.ical.0 2,32 * * * * 2025-05-27 19:02:18.717 - info: host.RoofServer instance system.adapter.ical.0 in version "1.16.1" started with pid 130048 2025-05-27 19:02:21.471 - info: hm-rega.0 (130033) request state values 2025-05-27 19:02:21.642 - info: ical.0 (130048) starting. Version 1.16.1 in /opt/iobroker/node_modules/iobroker.ical, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:22.443 - info: ical.0 (130048) processing URL: MH https://calendar.google.com/calendar/ical/c294fa6864d2%40group.calendar.google.com/private-063afafa12704b6d953907c2d98a219d/basic.ics 2025-05-27 19:02:22.913 - info: host.RoofServer instance system.adapter.unifi.0 in version "0.7.0" started with pid 130063 2025-05-27 19:02:25.815 - info: hm-rega.0 (130033) Updated all datapoints 2025-05-27 19:02:25.911 - info: hm-rega.0 (130033) got 95 variables 2025-05-27 19:02:26.567 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130078 2025-05-27 19:02:26.619 - info: sql.0 (129913) enabled logging of hm-rega.0.1851, Alias=false, WriteNulls=false 2025-05-27 19:02:26.640 - info: sql.0 (129913) enabled logging of hm-rega.0.2198, Alias=false, WriteNulls=false 2025-05-27 19:02:26.666 - info: sql.0 (129913) enabled logging of hm-rega.0.3307, Alias=false, WriteNulls=false 2025-05-27 19:02:26.679 - info: sql.0 (129913) enabled logging of hm-rega.0.3817, Alias=false, WriteNulls=false 2025-05-27 19:02:26.780 - info: sql.0 (129913) enabled logging of hm-rega.0.9138, Alias=false, WriteNulls=false 2025-05-27 19:02:26.832 - info: sql.0 (129913) enabled logging of hm-rega.0.14141, Alias=false, WriteNulls=false 2025-05-27 19:02:26.860 - info: sql.0 (129913) enabled logging of hm-rega.0.16479, Alias=false, WriteNulls=false 2025-05-27 19:02:26.869 - info: sql.0 (129913) enabled logging of hm-rega.0.16480, Alias=false, WriteNulls=false 2025-05-27 19:02:26.912 - info: sql.0 (129913) enabled logging of hm-rega.0.25695, Alias=false, WriteNulls=false 2025-05-27 19:02:26.983 - info: sql.0 (129913) enabled logging of hm-rega.0.29630, Alias=false, WriteNulls=false 2025-05-27 19:02:26.991 - info: sql.0 (129913) enabled logging of hm-rega.0.32282, Alias=false, WriteNulls=false 2025-05-27 19:02:27.004 - info: sql.0 (129913) enabled logging of hm-rega.0.33022, Alias=false, WriteNulls=false 2025-05-27 19:02:27.029 - info: sql.0 (129913) enabled logging of hm-rega.0.36060, Alias=false, WriteNulls=false 2025-05-27 19:02:27.034 - info: sql.0 (129913) enabled logging of hm-rega.0.36061, Alias=false, WriteNulls=false 2025-05-27 19:02:27.039 - info: sql.0 (129913) enabled logging of hm-rega.0.36062, Alias=false, WriteNulls=false 2025-05-27 19:02:27.045 - info: sql.0 (129913) enabled logging of hm-rega.0.36063, Alias=false, WriteNulls=false 2025-05-27 19:02:27.089 - info: sql.0 (129913) enabled logging of hm-rega.0.41371, Alias=false, WriteNulls=false 2025-05-27 19:02:27.117 - info: sql.0 (129913) enabled logging of hm-rega.0.44417, Alias=false, WriteNulls=false 2025-05-27 19:02:27.144 - info: sql.0 (129913) enabled logging of hm-rega.0.51326, Alias=false, WriteNulls=false 2025-05-27 19:02:27.145 - warn: hm-rega.0 (130033) State value to set for "hm-rega.0.51326" has value "-40" less than min "0" 2025-05-27 19:02:27.198 - info: sql.0 (129913) enabled logging of hm-rega.0.51327, Alias=false, WriteNulls=false 2025-05-27 19:02:27.218 - info: sql.0 (129913) enabled logging of hm-rega.0.57688, Alias=false, WriteNulls=false 2025-05-27 19:02:27.271 - info: sql.0 (129913) enabled logging of hm-rega.0.64620, Alias=false, WriteNulls=false 2025-05-27 19:02:27.284 - info: hm-rega.0 (130033) added/updated 95 variables 2025-05-27 19:02:27.285 - info: hm-rega.0 (130033) deleted 0 variables 2025-05-27 19:02:27.407 - info: hm-rega.0 (130033) got 123 programs 2025-05-27 19:02:27.934 - info: ical.0 (130048) Terminated (NO_ERROR): Without reason 2025-05-27 19:02:28.532 - warn: ical.0 (130048) get state error: Connection is closed. 2025-05-27 19:02:28.792 - info: host.RoofServer instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) 2025-05-27 19:02:29.277 - info: backitup.0 (130078) starting. Version 3.0.31 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:29.413 - info: backitup.0 (130078) [iobroker] backup will be activated at 02:00 every 1 day(s) 2025-05-27 19:02:29.512 - info: sql.0 (129913) enabled logging of hm-rega.0.29631.ProgramExecute, Alias=false, WriteNulls=false 2025-05-27 19:02:29.527 - info: sql.0 (129913) enabled logging of hm-rega.0.29631.Active, Alias=false, WriteNulls=false 2025-05-27 19:02:29.863 - info: sql.0 (129913) enabled logging of hm-rega.0.42002.ProgramExecute, Alias=false, WriteNulls=false 2025-05-27 19:02:29.869 - info: sql.0 (129913) enabled logging of hm-rega.0.42002.Active, Alias=false, WriteNulls=false 2025-05-27 19:02:29.421 - info: backitup.0 (130078) [ccu] backup will be activated at 01:30 every 3 day(s) 2025-05-27 19:02:30.663 - info: host.RoofServer instance system.adapter.sonoff.0 in version "3.1.2" started with pid 130093 2025-05-27 19:02:31.036 - info: hm-rega.0 (130033) added/updated 123 programs 2025-05-27 19:02:31.036 - info: hm-rega.0 (130033) deleted 0 programs 2025-05-27 19:02:31.142 - info: hm-rega.0 (130033) update rooms to enum.rooms 2025-05-27 19:02:31.292 - info: hm-rega.0 (130033) update functions to enum.functions 2025-05-27 19:02:31.331 - info: hm-rega.0 (130033) update favorites to enum.favorites 2025-05-27 19:02:33.005 - info: sonoff.0 (130093) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.sonoff, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:33.027 - info: sonoff.0 (130093) Starting MQTT authenticated server on port 1883 2025-05-27 19:02:34.649 - info: host.RoofServer instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 130119 2025-05-27 19:02:35.128 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.f0:9f:c2:a6:46:94.state, Alias=false, WriteNulls=false 2025-05-27 19:02:37.394 - info: hm-rpc.2 (130119) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:37.803 - info: hm-rpc.2 (130119) xmlrpc server is trying to listen on 0.0.0.0:2010 2025-05-27 19:02:37.804 - info: hm-rpc.2 (130119) xmlrpc client is trying to connect to 192.168.66.111:2010/ with ["http://192.168.66.75:2010","RoofServer:hm-rpc.2:b5897e342b96a2cdeef8e9f77d2c0b6c"] 2025-05-27 19:02:37.918 - info: hm-rpc.2 (130119) Connected 2025-05-27 19:02:37.983 - info: sql.0 (129913) enabled logging of unifi.0.default.devices.78:8a:20:53:92:d9.state, Alias=false, WriteNulls=false 2025-05-27 19:02:38.151 - info: hm-rpc.2 (130119) xmlrpc <- listDevices ["RoofServer:hm-rpc.2:b5897e342b96a2cdeef8e9f77d2c0b6c"] 2025-05-27 19:02:38.602 - info: hm-rpc.2 (130119) xmlrpc -> 0 devices 2025-05-27 19:02:39.086 - info: host.RoofServer instance system.adapter.ping.0 in version "1.6.2" started with pid 130135 2025-05-27 19:02:40.055 - info: hm-rpc.2 (130119) xmlrpc <- newDevices 218 2025-05-27 19:02:40.273 - info: hm-rpc.2 (130119) new HMIP devices/channels after filter: 0 2025-05-27 19:02:43.065 - info: host.RoofServer instance system.adapter.homeconnect.0 in version "1.4.3" started with pid 130169 2025-05-27 19:02:43.494 - info: ping.0 (130135) starting. Version 1.6.2 in /opt/iobroker/node_modules/iobroker.ping, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:45.706 - info: homeconnect.0 (130169) starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.homeconnect, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:46.025 - error: homeconnect.0 (130169) AxiosError: Request failed with status code 429 2025-05-27 19:02:46.026 - error: homeconnect.0 (130169) {"error":{"description":"The rate limit \"1000 calls in 1 day\" was reached. Requests are blocked during the remaining period of 86027 seconds.","key":"429"}} 2025-05-27 19:02:46.115 - error: homeconnect.0 (130169) 429 Too Many Requests 2025-05-27 19:02:46.115 - error: homeconnect.0 (130169) Start Event Stream Error: {"type":"error","status":429,"message":"Too Many Requests"} 2025-05-27 19:02:46.116 - info: homeconnect.0 (130169) Too many requests. Please wait 24h. 2025-05-27 19:02:46.656 - info: host.RoofServer instance system.adapter.mielecloudservice.0 in version "6.5.10" started with pid 130191 2025-05-27 19:02:48.371 - info: mielecloudservice.0 (130191) starting. Version 6.5.10 in /opt/iobroker/node_modules/iobroker.mielecloudservice, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:48.397 - info: mielecloudservice.0 (130191) Login attempt #1 @Miele-API 2025-05-27 19:02:49.096 - info: mielecloudservice.0 (130191) Access token expires on: 26.6.2025, 19:02:00 2025-05-27 19:02:49.097 - info: mielecloudservice.0 (130191) Registering for all appliance events at Miele API. 2025-05-27 19:02:49.109 - info: mielecloudservice.0 (130191) Initializing SSE watchdog. 2025-05-27 19:02:49.172 - info: mielecloudservice.0 (130191) Server Sent Events-Connection has been established @Miele-API. 2025-05-27 19:02:50.738 - info: host.RoofServer instance system.adapter.wiegand-tcpip.0 in version "0.4.7" started with pid 130206 2025-05-27 19:02:52.429 - info: wiegand-tcpip.0 (130206) starting. Version 0.4.7 in /opt/iobroker/node_modules/iobroker.wiegand-tcpip, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:52.451 - info: wiegand-tcpip.0 (130206) Create controller 125042571 for Model 1-Door Objects 2025-05-27 19:02:52.526 - warn: wiegand-tcpip.0 (130206) Incorrect controller-setup for non/broadcast: 125042571 2025-05-27 19:02:52.526 - info: wiegand-tcpip.0 (130206) Create controller 123224600 for Model 1-Door Objects 2025-05-27 19:02:52.828 - warn: wiegand-tcpip.0 (130206) Incorrect controller-setup for non/broadcast: 123224600 2025-05-27 19:02:52.847 - info: wiegand-tcpip.0 (130206) Connect to controller: 125042571 2025-05-27 19:02:53.116 - info: wiegand-tcpip.0 (130206) Reset the device clock: 125042571 2025-05-27 19:02:53.128 - info: wiegand-tcpip.0 (130206) Connect to controller: 123224600 2025-05-27 19:02:53.253 - info: wiegand-tcpip.0 (130206) Reset the device clock: 123224600 2025-05-27 19:02:54.576 - info: host.RoofServer instance system.adapter.nut.0 in version "1.6.0" started with pid 130221 2025-05-27 19:02:56.374 - info: nut.0 (130221) starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.nut, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:02:58.726 - info: host.RoofServer instance system.adapter.alexa2.0 in version "3.26.5" started with pid 130236 2025-05-27 19:03:00.587 - info: alexa2.0 (130236) starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:00.612 - info: alexa2.0 (130236) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. 2025-05-27 19:03:00.614 - error: alexa2.0 (130236) Adapter seems to have issues and crashed three times in a row. Disabling!! Please start again and check logs. 2025-05-27 19:03:01.617 - info: alexa2.0 (130236) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-05-27 19:03:02.774 - info: host.RoofServer instance system.adapter.alexa2.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2025-05-27 19:03:02.774 - info: host.RoofServer Do not restart adapter system.adapter.alexa2.0 because desired by instance 2025-05-27 19:03:02.826 - info: host.RoofServer instance system.adapter.modbus.0 in version "6.3.2" started with pid 130253 2025-05-27 19:03:04.756 - info: modbus.0 (130253) starting. Version 6.3.2 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:05.180 - info: sql.0 (129913) enabled logging of modbus.0.inputRegisters.30513_Gesamtertrag, Alias=false, WriteNulls=false 2025-05-27 19:03:05.184 - info: sql.0 (129913) enabled logging of modbus.0.inputRegisters.30517_Tag_Energie, Alias=false, WriteNulls=false 2025-05-27 19:03:05.187 - info: sql.0 (129913) enabled logging of modbus.0.inputRegisters.30775_Wirkleistung_Gesamt, Alias=false, WriteNulls=false 2025-05-27 19:03:05.240 - info: modbus.0 (130253) Connected to slave 192.168.66.239 2025-05-27 19:03:06.688 - info: host.RoofServer instance system.adapter.modbus.1 in version "6.3.2" started with pid 130268 2025-05-27 19:03:08.582 - info: modbus.1 (130268) starting. Version 6.3.2 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:09.121 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1068_soc, Alias=false, WriteNulls=false 2025-05-27 19:03:09.125 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1069_energy_counter_ac_to_dc, Alias=false, WriteNulls=false 2025-05-27 19:03:09.134 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1078_grid_power, Alias=false, WriteNulls=false 2025-05-27 19:03:09.162 - info: sql.0 (129913) enabled logging of modbus.1.holdingRegisters.1088_PV-sensor_power, Alias=false, WriteNulls=false 2025-05-27 19:03:09.220 - info: modbus.1 (130268) Connected to slave 192.168.66.250 2025-05-27 19:03:10.770 - info: host.RoofServer instance system.adapter.tuya.0 in version "3.16.0" started with pid 130283 2025-05-27 19:03:13.341 - info: tuya.0 (130283) starting. Version 3.16.0 in /opt/iobroker/node_modules/iobroker.tuya, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:13.829 - info: tuya.0 (130283) bf56359fa1429b7be6qybg: Connect locally to device 2025-05-27 19:03:13.831 - info: tuya.0 (130283) bf1356ecf61e8155832ho7: Connect locally to device 2025-05-27 19:03:13.833 - info: tuya.0 (130283) bf7474eac2fbdf758dalff: Connect locally to device 2025-05-27 19:03:13.834 - info: tuya.0 (130283) bf7474eac2fbdf758dalff Init with IP=192.168.66.99, Key=yW;(kK[_V-]c?;Tk, Version=3.3 2025-05-27 19:03:13.839 - info: tuya.0 (130283) bf8e6ee7031f77b746a45q: Connect locally to device 2025-05-27 19:03:13.839 - info: tuya.0 (130283) bf8e6ee7031f77b746a45q Init with IP=192.168.66.134, Key=.aKZByop=a7!n*1?, Version=3.4 2025-05-27 19:03:13.919 - info: tuya.0 (130283) bf918b83061a3f9b54rm6b: Connect locally to device 2025-05-27 19:03:13.919 - info: tuya.0 (130283) bf918b83061a3f9b54rm6b Init with IP=192.168.66.149, Key=r~A.@|Cnbd7sJq5c, Version=3.3 2025-05-27 19:03:13.920 - info: tuya.0 (130283) Existing devices initialized 2025-05-27 19:03:13.922 - info: tuya.0 (130283) Try to sync devices from Cloud using stored cloud credentials 2025-05-27 19:03:14.091 - info: tuya.0 (130283) Listen for local Tuya devices on port 6666 2025-05-27 19:03:14.091 - info: tuya.0 (130283) Listen for encrypted local Tuya devices on port 6667 2025-05-27 19:03:14.553 - info: tuya.0 (130283) IOT Cloud ID/Secret not configured, disabling real time State updates from Cloud MQTT 2025-05-27 19:03:14.790 - info: host.RoofServer instance system.adapter.evcc.0 in version "0.2.2" started with pid 130298 2025-05-27 19:03:15.746 - info: tuya.0 (130283) bf8e6ee7031f77b746a45q: Connect locally to device 2025-05-27 19:03:15.746 - info: tuya.0 (130283) bf8e6ee7031f77b746a45q Init with IP=192.168.66.134, Key=.aKZByop=a7!n*1?, Version=3.4 2025-05-27 19:03:16.685 - info: evcc.0 (130298) starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.evcc, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:16.746 - info: evcc.0 (130298) Lege neuen Ladepunkt an mit Index: 1 2025-05-27 19:03:16.890 - info: tuya.0 (130283) bf7474eac2fbdf758dalff: Error on Reconnect (1): connect EHOSTUNREACH 192.168.66.99:6668 2025-05-27 19:03:16.906 - info: tuya.0 (130283) bf7474eac2fbdf758dalff: Connect locally to device 2025-05-27 19:03:16.906 - info: tuya.0 (130283) bf7474eac2fbdf758dalff Init with IP=192.168.66.99, Key=yW;(kK[_V-]c?;Tk, Version=3.3 2025-05-27 19:03:16.940 - info: sql.0 (129913) enabled logging of evcc.0.loadpoint.1.status.chargePower, Alias=false, WriteNulls=false 2025-05-27 19:03:16.942 - info: sql.0 (129913) enabled logging of evcc.0.loadpoint.1.status.charging, Alias=false, WriteNulls=false 2025-05-27 19:03:17.072 - info: tuya.0 (130283) bf1356ecf61e8155832ho7: Connect locally to device 2025-05-27 19:03:18.609 - info: host.RoofServer instance system.adapter.lg-thinq.0 in version "1.1.0" started with pid 130313 2025-05-27 19:03:18.645 - info: tuya.0 (130283) bf918b83061a3f9b54rm6b: Connect locally to device 2025-05-27 19:03:18.646 - info: tuya.0 (130283) bf918b83061a3f9b54rm6b Init with IP=192.168.66.149, Key=r~A.@|Cnbd7sJq5c, Version=3.3 2025-05-27 19:03:19.959 - info: tuya.0 (130283) bf7474eac2fbdf758dalff: Error on Reconnect (3): connect EHOSTUNREACH 192.168.66.99:6668 2025-05-27 19:03:20.682 - info: lg-thinq.0 (130313) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.lg-thinq, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:21.558 - info: lg-thinq.0 (130313) Login successful 2025-05-27 19:03:22.741 - info: host.RoofServer instance system.adapter.opendtu.0 in version "3.1.0" started with pid 130328 2025-05-27 19:03:23.786 - info: lg-thinq.0 (130313) Found: 1 devices 2025-05-27 19:03:23.787 - info: lg-thinq.0 (130313) Create or update datapoints for e8b5a49a-a144-1b85-a916-d8e35e8028de 2025-05-27 19:03:24.592 - info: opendtu.0 (130328) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.opendtu, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:24.825 - info: opendtu.0 (130328) Connect to OpenDTU over websocket connection. 2025-05-27 19:03:26.703 - info: host.RoofServer instance system.adapter.device-watcher.0 in version "2.12.1" started with pid 130343 2025-05-27 19:03:28.642 - info: device-watcher.0 (130343) starting. Version 2.12.1 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:28.654 - info: device-watcher.0 (130343) Number of selected adapters to monitor devices: 5. Loading data from: HmiP, Hmrpc, Homeconnect, Sonoff, Unifi ... 2025-05-27 19:03:28.655 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER 2025-05-27 19:03:28.655 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER 2025-05-27 19:03:28.656 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER 2025-05-27 19:03:28.656 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER 2025-05-27 19:03:28.656 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER 2025-05-27 19:03:28.656 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER 2025-05-27 19:03:28.657 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER 2025-05-27 19:03:28.657 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER 2025-05-27 19:03:28.657 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive 2025-05-27 19:03:28.657 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive 2025-05-27 19:03:28.658 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive,sonoff.0.gosuna-2.alive 2025-05-27 19:03:28.658 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive,sonoff.0.gosuna-2.alive 2025-05-27 19:03:28.658 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive,sonoff.0.gosuna-2.alive,sonoff.0.gosuna-usb-1.alive 2025-05-27 19:03:28.658 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive,sonoff.0.gosuna-2.alive,sonoff.0.gosuna-usb-1.alive 2025-05-27 19:03:28.658 - info: device-watcher.0 (130343) Found devices/services on blacklist for lists: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive,sonoff.0.gosuna-2.alive,sonoff.0.gosuna-usb-1.alive,sonoff.0.kuecheledband.alive 2025-05-27 19:03:28.658 - info: device-watcher.0 (130343) Found devices/services on blacklist for notifications: hm-rpc.1.OEQ0433923.0.RSSI_PEER,hm-rpc.1.KEQ0944083.0.RSSI_PEER,hm-rpc.1.MEQ0271319.0.RSSI_PEER,hm-rpc.1.NEQ0387355.0.RSSI_PEER,sonoff.0.gosuna-1.alive,sonoff.0.gosuna-2.alive,sonoff.0.gosuna-usb-1.alive,sonoff.0.kuecheledband.alive 2025-05-27 19:03:30.909 - info: host.RoofServer instance system.adapter.discovery.0 in version "5.0.0" started with pid 130358 2025-05-27 19:03:35.355 - info: host.RoofServer instance system.adapter.web.0 in version "7.0.8" started with pid 130369 2025-05-27 19:03:35.774 - info: sonoff.0 (130093) Client [gosuna-usb-1] connected with secret 1748365415770_2790 2025-05-27 19:03:36.045 - info: sonoff.0 (130093) Client [gosuna-usb-2] connected with secret 1748365416044_6316 2025-05-27 19:03:37.702 - info: discovery.0 (130358) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:37.943 - info: lg-thinq.0 (130313) Update raw datapoints for e8b5a49a-a144-1b85-a916-d8e35e8028de 2025-05-27 19:03:43.983 - info: host.RoofServer instance scheduled system.adapter.dwd.0 */5 * * * * 2025-05-27 19:03:43.990 - info: host.RoofServer instance system.adapter.dwd.0 in version "2.8.5" started with pid 130400 2025-05-27 19:03:44.651 - info: web.0 (130369) starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:44.655 - info: vis.0 (130388) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:03:44.751 - info: lg-thinq.0 (130313) Found MQTT Host 2025-05-27 19:03:44.808 - info: lg-thinq.0 (130313) Found AWS CER 2025-05-27 19:03:45.354 - info: lg-thinq.0 (130313) Create certification done 2025-05-27 19:03:45.416 - warn: web.0 (130369) Could not find any certificate collections - check ACME installation or consider installing 2025-05-27 19:03:45.417 - warn: web.0 (130369) Falling back to self-signed certificates or to custom certificates 2025-05-27 19:03:45.559 - info: web.0 (130369) https server listening on port 8082 2025-05-27 19:03:45.631 - info: web.0 (130369) Secure socket.io server listening on port 8082 2025-05-27 19:03:45.682 - info: lg-thinq.0 (130313) Start MQTT Connection 2025-05-27 19:03:46.021 - info: lg-thinq.0 (130313) MQTT connected to: t20/op/2333271ebb2eff127ec1822fde9a6f5b39220a8b13f00676225d5afb273a12de/inbox 2025-05-27 19:03:47.287 - info: vis.0 (130388) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:47.364 - error: dwd.0 (130400) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4' 2025-05-27 19:03:47.371 - error: host.RoofServer uncaught exception: Could not determine controller directory 2025-05-27 19:03:47.371 - error: host.RoofServer Error: Could not determine controller directory at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11) at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1306:37) at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3219:30) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) 2025-05-27 19:03:47.372 - info: host.RoofServer stopInstance system.adapter.admin.0 (force=false, process=true) 2025-05-27 19:03:47.373 - info: host.RoofServer stopInstance system.adapter.history.0 (force=false, process=true) 2025-05-27 19:03:47.373 - info: host.RoofServer stopInstance system.adapter.javascript.0 (force=false, process=true) 2025-05-27 19:03:47.374 - info: host.RoofServer stopInstance system.adapter.email.0 (force=false, process=true) 2025-05-27 19:03:47.374 - info: host.RoofServer stopInstance system.adapter.sql.0 (force=false, process=true) 2025-05-27 19:03:47.374 - info: host.RoofServer stopInstance system.adapter.telegram.0 (force=false, process=true) 2025-05-27 19:03:47.374 - info: host.RoofServer stopInstance system.adapter.tr-064.0 (force=false, process=true) 2025-05-27 19:03:47.374 - info: host.RoofServer stopInstance system.adapter.hm-rpc.0 (force=false, process=true) 2025-05-27 19:03:47.375 - info: host.RoofServer stopInstance system.adapter.hm-rpc.1 (force=false, process=true) 2025-05-27 19:03:47.375 - info: host.RoofServer stopInstance system.adapter.hm-rega.0 (force=false, process=true) 2025-05-27 19:03:47.375 - info: host.RoofServer stopInstance system.adapter.ical.0 (force=false, process=false) 2025-05-27 19:03:47.375 - info: host.RoofServer stopInstance canceled schedule system.adapter.ical.0 2025-05-27 19:03:47.376 - info: host.RoofServer stopInstance system.adapter.unifi.0 (force=false, process=true) 2025-05-27 19:03:47.376 - info: host.RoofServer stopInstance system.adapter.backitup.0 (force=false, process=true) 2025-05-27 19:03:47.376 - info: host.RoofServer stopInstance system.adapter.sonoff.0 (force=false, process=true) 2025-05-27 19:03:47.376 - info: host.RoofServer stopInstance system.adapter.hm-rpc.2 (force=false, process=true) 2025-05-27 19:03:47.376 - info: host.RoofServer stopInstance system.adapter.ping.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.homeconnect.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.mielecloudservice.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.ham.0 (force=false, process=false) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.wiegand-tcpip.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.nut.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.alexa2.0 (force=false, process=false) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.modbus.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.modbus.1 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.tuya.0 (force=false, process=true) 2025-05-27 19:03:47.377 - info: host.RoofServer stopInstance system.adapter.evcc.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.lg-thinq.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.opendtu.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.device-watcher.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.discovery.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.web.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.mobile.0 (force=false, process=false) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.vis.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.dwd.0 (force=false, process=true) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance canceled schedule system.adapter.dwd.0 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.vis-fancyswitch.0 (force=false, process=false) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false) 2025-05-27 19:03:47.378 - info: host.RoofServer stopInstance system.adapter.vis-metro.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.vis-colorpicker.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.vis-history.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.vis-bars.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.text2command.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.daswetter.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.material.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.nina.0 (force=false, process=false) 2025-05-27 19:03:47.379 - info: host.RoofServer stopInstance system.adapter.klf200.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.vis-rgraph.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.simple-api.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.govee.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.easee.1 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.parser.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.vw-connect.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.statistics.0 (force=false, process=false) 2025-05-27 19:03:47.380 - info: host.RoofServer stopInstance system.adapter.waterkotte-easycon.0 (force=false, process=false) 2025-05-27 19:03:47.506 - error: device-watcher.0 (130343) Objects database error: read ECONNRESET 2025-05-27 19:03:47.544 - error: unifi.0 (130063) States database error: read ECONNRESET 2025-05-27 19:03:47.563 - info: hm-rpc.2 (130119) xmlrpc -> 192.168.66.111:2010/ init ["http://192.168.66.75:2010",""] 2025-05-27 19:03:47.567 - warn: web.0 (130369) setTimeout called, but adapter is shutting down 2025-05-27 19:03:47.565 - info: device-watcher.0 (130343) cleaned everything up... 2025-05-27 19:03:47.576 - info: backitup.0 (130078) cleaned everything up... 2025-05-27 19:03:47.580 - info: hm-rpc.1 (130018) binrpc -> 192.168.66.111:2001/ init ["xmlrpc_bin://192.168.66.75:12001",""] 2025-05-27 19:03:47.588 - info: admin.0 (129805) terminating http server on port 8081 2025-05-27 19:03:47.587 - info: hm-rpc.0 (130003) binrpc -> 192.168.66.111:8701/ init ["xmlrpc_bin://192.168.66.75:18701",""] 2025-05-27 19:03:47.592 - info: admin.0 (129805) <== Disconnect system.user.admin from ::ffff:192.168.66.108 admin 2025-05-27 19:03:47.592 - info: hm-rpc.1 (130018) Disconnected 2025-05-27 19:03:47.607 - info: hm-rpc.0 (130003) Disconnected 2025-05-27 19:03:47.612 - error: telegram.0 (129928) Failed sending [chatId - 1173210274]: Error: ETELEGRAM: 403 Forbidden: bot was blocked by the user 2025-05-27 19:03:47.648 - info: hm-rpc.2 (130119) Disconnected 2025-05-27 19:03:48.070 - info: dwd.0 (130400) terminating 2025-05-27 19:03:48.071 - info: dwd.0 (130400) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:48.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.619 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.620 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.620 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.620 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.623 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.623 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.624 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.624 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.624 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.625 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.625 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.627 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.627 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.627 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.627 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.628 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.628 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.628 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.628 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.628 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.628 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.629 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.629 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.629 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.629 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.651 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.651 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.652 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.652 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.652 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.653 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.653 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.653 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.653 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.654 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.655 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.662 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.662 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.662 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.669 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.669 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.669 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.670 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.670 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.670 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.671 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.671 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.671 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.671 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.672 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.672 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.672 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database -
@wendy2702 Eben die Zeilen 1-500, hier der Rest. Das merkwürdige Runterfahren ist hier eher am Anfang
2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.675 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.675 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.063 - info: sonoff.0 (130093) terminating with timeout 2025-05-27 19:03:49.064 - info: sonoff.0 (130093) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.064 - info: mielecloudservice.0 (130191) terminating with timeout 2025-05-27 19:03:49.065 - info: mielecloudservice.0 (130191) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.065 - info: lg-thinq.0 (130313) terminating with timeout 2025-05-27 19:03:49.066 - info: evcc.0 (130298) terminating with timeout 2025-05-27 19:03:49.066 - info: lg-thinq.0 (130313) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.067 - info: device-watcher.0 (130343) terminating with timeout 2025-05-27 19:03:49.069 - info: nut.0 (130221) terminating with timeout 2025-05-27 19:03:49.068 - info: device-watcher.0 (130343) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.069 - info: web.0 (130369) terminating with timeout 2025-05-27 19:03:49.071 - info: wiegand-tcpip.0 (130206) terminating with timeout 2025-05-27 19:03:49.071 - info: nut.0 (130221) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.072 - info: wiegand-tcpip.0 (130206) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.073 - info: modbus.0 (130253) terminating with timeout 2025-05-27 19:03:49.075 - info: homeconnect.0 (130169) terminating with timeout 2025-05-27 19:03:49.076 - info: homeconnect.0 (130169) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.077 - info: opendtu.0 (130328) terminating with timeout 2025-05-27 19:03:49.078 - info: opendtu.0 (130328) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.076 - info: modbus.1 (130268) terminating with timeout 2025-05-27 19:03:49.077 - info: modbus.1 (130268) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.079 - info: ping.0 (130135) terminating with timeout 2025-05-27 19:03:49.080 - info: backitup.0 (130078) terminating with timeout 2025-05-27 19:03:49.081 - info: backitup.0 (130078) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.070 - info: web.0 (130369) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.082 - info: discovery.0 (130358) terminating with timeout 2025-05-27 19:03:49.067 - info: evcc.0 (130298) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.074 - info: modbus.0 (130253) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.081 - info: ping.0 (130135) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.084 - info: tr-064.0 (129955) terminating with timeout 2025-05-27 19:03:49.084 - info: discovery.0 (130358) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.085 - info: tr-064.0 (129955) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.088 - info: telegram.0 (129928) terminating with timeout 2025-05-27 19:03:49.089 - info: telegram.0 (129928) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.089 - info: email.0 (129879) terminating with timeout 2025-05-27 19:03:49.091 - info: email.0 (129879) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.092 - info: hm-rega.0 (130033) terminating with timeout 2025-05-27 19:03:49.093 - info: hm-rega.0 (130033) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.095 - info: admin.0 (129805) terminating with timeout 2025-05-27 19:03:49.096 - info: admin.0 (129805) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.566 - info: hm-rpc.2 (130119) terminating with timeout 2025-05-27 19:03:49.567 - info: hm-rpc.2 (130119) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.583 - info: hm-rpc.1 (130018) terminating with timeout 2025-05-27 19:03:49.584 - info: hm-rpc.1 (130018) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.592 - info: hm-rpc.0 (130003) terminating with timeout 2025-05-27 19:03:49.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.593 - info: hm-rpc.0 (130003) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.508 - error: web.0 (130369) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.529 - error: wiegand-tcpip.0 (130206) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.534 - error: tuya.0 (130283) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.541 - error: mielecloudservice.0 (130191) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.546 - error: modbus.0 (130253) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.549 - error: backitup.0 (130078) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.551 - warn: discovery.0 (130358) get state error: Connection is closed. 2025-05-27 19:03:52.552 - warn: unifi.0 (130063) get state error: DB closed 2025-05-27 19:03:52.536 - error: tuya.0 (130283) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.558 - warn: hm-rega.0 (130033) get state error: Connection is closed. 2025-05-27 19:03:52.561 - error: hm-rpc.1 (130018) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.561 - info: hm-rega.0 (130033) terminating 2025-05-27 19:03:52.562 - error: telegram.0 (129928) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.549 - error: nut.0 (130221) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.566 - error: evcc.0 (130298) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.569 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.570 - error: admin.0 (129805) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.575 - error: opendtu.0 (130328) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.575 - error: hm-rpc.2 (130119) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.579 - warn: ping.0 (130135) get state error: Connection is closed. 2025-05-27 19:03:52.577 - warn: admin.0 (129805) get state error: Connection is closed. 2025-05-27 19:03:52.577 - warn: admin.0 (129805) get state error: DB closed 2025-05-27 19:03:52.578 - info: admin.0 (129805) terminating 2025-05-27 19:03:52.578 - info: admin.0 (129805) terminating 2025-05-27 19:03:52.581 - error: homeconnect.0 (130169) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.583 - error: lg-thinq.0 (130313) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.587 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.591 - warn: sonoff.0 (130093) get state error: Connection is closed. 2025-05-27 19:03:52.593 - error: modbus.1 (130268) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.591 - error: tr-064.0 (129955) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.596 - warn: backitup.0 (130078) get state error: Connection is closed. 2025-05-27 19:03:52.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.553 - error: device-watcher.0 (130343) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.606 - warn: hm-rpc.1 (130018) get state error: DB closed 2025-05-27 19:03:52.595 - error: hm-rpc.0 (130003) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.589 - error: history.0 (129834) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.592 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.alive, error - DB closed 2025-05-27 19:03:52.592 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.modeReadColors, error - DB closed 2025-05-27 19:03:52.593 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.alive, error - DB closed 2025-05-27 19:03:52.593 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.modeReadColors, error - DB closed 2025-05-27 19:03:52.593 - info: sonoff.0 (130093) terminating 2025-05-27 19:03:52.609 - error: email.0 (129879) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.564 - warn: nut.0 (130221) get state error: Connection is closed. 2025-05-27 19:03:52.565 - warn: nut.0 (130221) get state error: DB closed 2025-05-27 19:03:52.611 - info: nut.0 (130221) terminating 2025-05-27 19:03:52.612 - info: nut.0 (130221) terminating 2025-05-27 19:03:52.573 - warn: mielecloudservice.0 (130191) get state error: Connection is closed. 2025-05-27 19:03:52.574 - info: mielecloudservice.0 (130191) terminating 2025-05-27 19:03:52.577 - warn: hm-rpc.2 (130119) get state error: DB closed 2025-05-27 19:03:52.578 - warn: hm-rpc.2 (130119) get state error: DB closed 2025-05-27 19:03:52.625 - info: hm-rpc.2 (130119) terminating 2025-05-27 19:03:52.625 - info: hm-rpc.2 (130119) terminating 2025-05-27 19:03:52.578 - warn: opendtu.0 (130328) get state error: Connection is closed. 2025-05-27 19:03:52.578 - warn: opendtu.0 (130328) get state error: DB closed 2025-05-27 19:03:52.632 - info: opendtu.0 (130328) terminating 2025-05-27 19:03:52.633 - info: opendtu.0 (130328) terminating 2025-05-27 19:03:52.606 - warn: hm-rpc.1 (130018) get state error: DB closed 2025-05-27 19:03:52.637 - info: hm-rpc.1 (130018) terminating 2025-05-27 19:03:52.638 - info: hm-rpc.1 (130018) terminating 2025-05-27 19:03:52.583 - warn: homeconnect.0 (130169) get state error: Connection is closed. 2025-05-27 19:03:52.584 - warn: homeconnect.0 (130169) get state error: DB closed 2025-05-27 19:03:52.585 - info: homeconnect.0 (130169) terminating 2025-05-27 19:03:52.586 - info: homeconnect.0 (130169) terminating 2025-05-27 19:03:52.639 - warn: modbus.1 (130268) get state error: Connection is closed. 2025-05-27 19:03:52.643 - info: modbus.1 (130268) terminating 2025-05-27 19:03:52.620 - error: sql.0 (129913) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.662 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.663 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.663 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:53.563 - info: tuya.0 (130283) terminating with timeout 2025-05-27 19:03:53.564 - info: tuya.0 (130283) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:56.031 - info: homeconnect.0 (130169) Keep Alive failed Reconnect EventStream 2025-05-27 19:03:56.106 - error: homeconnect.0 (130169) 429 Too Many Requests 2025-05-27 19:03:56.106 - error: homeconnect.0 (130169) Start Event Stream Error: {"type":"error","status":429,"message":"Too Many Requests"} 2025-05-27 19:03:56.107 - info: homeconnect.0 (130169) Too many requests. Please wait 24h. 2025-05-27 19:03:57.552 - error: tuya.0 (130283) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.554 - warn: tuya.0 (130283) get state error: Connection is closed. 2025-05-27 19:03:57.555 - warn: tuya.0 (130283) get state error: DB closed 2025-05-27 19:03:57.556 - info: tuya.0 (130283) terminating 2025-05-27 19:03:57.557 - info: tuya.0 (130283) terminating 2025-05-27 19:03:57.567 - error: nut.0 (130221) Cannot check object existence of "nut.0.battery.charge": DB closed 2025-05-27 19:03:57.571 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.581 - error: opendtu.0 (130328) Cannot find view "system" for search "folder" : Connection is closed. 2025-05-27 19:03:57.592 - error: history.0 (129834) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:57.594 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.601 - error: modbus.1 (130268) Cannot find view "system" for search "state" : DB closed 2025-05-27 19:03:57.667 - error: sql.0 (129913) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:58.588 - info: history.0 (129834) terminating with timeout 2025-05-27 19:03:58.588 - info: history.0 (129834) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:58.594 - info: sql.0 (129913) terminating with timeout 2025-05-27 19:03:58.594 - info: sql.0 (129913) Terminated (NO_ERROR): Without reason 2025-05-27 19:04:02.574 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:04:02.596 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:04:02.597 - warn: history.0 (129834) get state error: Connection is closed. 2025-05-27 19:04:02.671 - warn: sql.0 (129913) get state error: Connection is closed. 2025-05-27 19:04:02.673 - warn: sql.0 (129913) get state error: DB closed 2025-05-27 19:04:02.673 - info: sql.0 (129913) terminating 2025-05-27 19:04:02.673 - info: sql.0 (129913) terminating 2025-05-27 19:04:31.403 - info: host.RoofServer iobroker.js-controller version 7.0.7 js-controller starting 2025-05-27 19:04:31.406 - info: host.RoofServer Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2025-05-27 19:04:31.407 - info: host.RoofServer hostname: RoofServer, node: v20.19.2 2025-05-27 19:04:31.407 - info: host.RoofServer ip addresses: 192.168.66.75 fe80::ee2c:259e:69f8:4bec fe80::bee1:cabf:72ba:3764 172.16.100.9 2025-05-27 19:04:33.422 - info: host.RoofServer connected to Objects and States 2025-05-27 19:04:33.439 - info: host.RoofServer added notifications configuration of host 2025-05-27 19:04:34.220 - info: host.RoofServer 62 instances found 2025-05-27 19:04:34.253 - info: host.RoofServer starting 54 instances 2025-05-27 19:04:34.839 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeCurrent" 2025-05-27 19:04:35.009 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeNewest" 2025-05-27 19:04:35.014 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeNewestNext" 2025-05-27 19:04:35.065 - info: host.RoofServer instance system.adapter.admin.0 in version "7.6.3" started with pid 130519 2025-05-27 19:04:35.068 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmCurrent" 2025-05-27 19:04:35.112 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmNewest" 2025-05-27 19:04:35.157 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmNewestNext" 2025-05-27 19:04:35.200 - info: host.RoofServer Some obsolete host states deleted. 2025-05-27 19:04:36.911 - error: admin.0 (130519) admin.0 already running 2025-05-27 19:04:36.913 - warn: admin.0 (130519) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:37.661 - error: host.RoofServer instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:37.662 - info: host.RoofServer Restart adapter system.adapter.admin.0 because enabled 2025-05-27 19:04:38.967 - info: host.RoofServer instance system.adapter.history.0 in version "3.0.1" started with pid 130530 2025-05-27 19:04:40.486 - error: history.0 (130530) history.0 already running 2025-05-27 19:04:40.488 - warn: history.0 (130530) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:41.203 - error: host.RoofServer instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:41.204 - info: host.RoofServer Restart adapter system.adapter.history.0 because enabled 2025-05-27 19:04:42.894 - info: host.RoofServer instance system.adapter.javascript.0 in version "8.8.3" started with pid 130541 2025-05-27 19:04:44.936 - error: javascript.0 (130541) javascript.0 already running 2025-05-27 19:04:44.938 - warn: javascript.0 (130541) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:45.667 - error: host.RoofServer instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:45.667 - info: host.RoofServer Restart adapter system.adapter.javascript.0 because enabled 2025-05-27 19:04:46.968 - info: host.RoofServer instance system.adapter.email.0 in version "2.0.3" started with pid 130584 2025-05-27 19:04:48.495 - error: email.0 (130584) email.0 already running 2025-05-27 19:04:48.497 - warn: email.0 (130584) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:49.205 - error: host.RoofServer instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:49.205 - info: host.RoofServer Restart adapter system.adapter.email.0 because enabled 2025-05-27 19:04:50.876 - info: host.RoofServer instance system.adapter.sql.0 in version "3.0.1" started with pid 130595 2025-05-27 19:04:52.427 - error: sql.0 (130595) sql.0 already running 2025-05-27 19:04:52.429 - warn: sql.0 (130595) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:53.139 - error: host.RoofServer instance system.adapter.sql.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:53.139 - info: host.RoofServer Restart adapter system.adapter.sql.0 because enabled 2025-05-27 19:04:54.991 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 130606 2025-05-27 19:04:56.917 - error: telegram.0 (130606) telegram.0 already running 2025-05-27 19:04:56.919 - warn: telegram.0 (130606) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:57.637 - error: host.RoofServer instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:57.637 - info: host.RoofServer Restart adapter system.adapter.telegram.0 because enabled 2025-05-27 19:04:59.570 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 130617 2025-05-27 19:04:59.582 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 130623 2025-05-27 19:05:02.151 - error: tr-064.0 (130617) tr-064.0 already running 2025-05-27 19:05:02.152 - warn: tr-064.0 (130617) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:02.878 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130641 2025-05-27 19:05:03.054 - error: host.RoofServer instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:03.054 - info: host.RoofServer Restart adapter system.adapter.tr-064.0 because enabled 2025-05-27 19:05:03.181 - info: telegram.0 (130623) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:03.771 - error: telegram.0 (130623) Failed sending [chatId - 1173210274]: Error: ETELEGRAM: 403 Forbidden: bot was blocked by the user 2025-05-27 19:05:04.551 - error: hm-rpc.0 (130641) hm-rpc.0 already running 2025-05-27 19:05:04.553 - warn: hm-rpc.0 (130641) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:05.258 - error: host.RoofServer instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:05.258 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.0 because enabled 2025-05-27 19:05:07.007 - info: host.RoofServer instance system.adapter.hm-rpc.1 in version "2.0.2" started with pid 130656 2025-05-27 19:05:08.693 - info: host.RoofServer instance system.adapter.admin.0 in version "7.6.3" started with pid 130667 2025-05-27 19:05:09.067 - error: hm-rpc.1 (130656) hm-rpc.1 already running 2025-05-27 19:05:09.069 - warn: hm-rpc.1 (130656) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:09.778 - error: host.RoofServer instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:09.779 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.1 because enabled 2025-05-27 19:05:10.967 - info: host.RoofServer instance system.adapter.hm-rega.0 in version "5.1.0" started with pid 130678 2025-05-27 19:05:12.195 - info: host.RoofServer instance system.adapter.history.0 in version "3.0.1" started with pid 130689 2025-05-27 19:05:12.860 - error: hm-rega.0 (130678) hm-rega.0 already running 2025-05-27 19:05:12.863 - warn: hm-rega.0 (130678) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:12.871 - info: admin.0 (130667) starting. Version 7.6.3 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:12.903 - info: admin.0 (130667) requesting all objects 2025-05-27 19:05:16.332 - error: host.RoofServer instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:16.333 - info: host.RoofServer Restart adapter system.adapter.hm-rega.0 because enabled 2025-05-27 19:05:16.536 - info: admin.0 (130667) received all objects 2025-05-27 19:05:17.243 - info: admin.0 (130667) socket.io server listening on port 8081 2025-05-27 19:05:17.244 - info: admin.0 (130667) http server listening on port 8081 2025-05-27 19:05:17.245 - info: admin.0 (130667) Use link "http://127.0.0.1:8081" to configure. 2025-05-27 19:05:18.279 - info: host.RoofServer instance scheduled system.adapter.ical.0 2,32 * * * * 2025-05-27 19:05:18.287 - info: host.RoofServer instance system.adapter.ical.0 in version "1.16.1" started with pid 130720 2025-05-27 19:05:19.921 - info: host.RoofServer instance system.adapter.javascript.0 in version "8.8.3" started with pid 130737 2025-05-27 19:05:21.039 - info: host.RoofServer instance system.adapter.unifi.0 in version "0.7.0" started with pid 130744 2025-05-27 19:05:21.268 - info: host.RoofServer instance system.adapter.email.0 in version "2.0.3" started with pid 130755 2025-05-27 19:05:21.904 - info: admin.0 (130667) ==> Connected system.user.admin from ::ffff:192.168.66.108 2025-05-27 19:05:28.629 - error: unifi.0 (130744) unifi.0 already running 2025-05-27 19:05:28.632 - warn: unifi.0 (130744) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:28.700 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130784 2025-05-27 19:05:28.889 - info: host.RoofServer instance system.adapter.sql.0 in version "3.0.1" started with pid 130791 2025-05-27 19:05:29.032 - info: host.RoofServer instance system.adapter.sonoff.0 in version "3.1.2" started with pid 130798 2025-05-27 19:05:29.048 - info: history.0 (130689) starting. Version 3.0.1 in /opt/iobroker/node_modules/iobroker.history, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:29.861 - error: host.RoofServer instance system.adapter.unifi.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:29.862 - info: host.RoofServer Restart adapter system.adapter.unifi.0 because enabled 2025-05-27 19:05:30.067 - info: ical.0 (130720) starting. Version 1.16.1 in /opt/iobroker/node_modules/iobroker.ical, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:30.298 - info: email.0 (130755) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.email, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:31.496 - info: ical.0 (130720) processing URL: MH https://calendar.google.com/calendar/ical/c530e1fa7a07a45ab04e116a7f389806477602687d99c31f461cc294fa6864d2%40group.calendar.google.com/private-063afafa12704b6d953907c2d98a219d/basic.ics 2025-05-27 19:05:32.834 - info: host.RoofServer instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 130829 2025-05-27 19:05:33.290 - error: backitup.0 (130784) backitup.0 already running 2025-05-27 19:05:33.292 - warn: backitup.0 (130784) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:33.696 - error: sonoff.0 (130798) sonoff.0 already running 2025-05-27 19:05:33.699 - warn: sonoff.0 (130798) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:34.351 - error: host.RoofServer instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:34.351 - info: host.RoofServer Restart adapter system.adapter.backitup.0 because enabled 2025-05-27 19:05:34.934 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 130840 2025-05-27 19:05:35.375 - error: host.RoofServer instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:35.376 - info: host.RoofServer Restart adapter system.adapter.sonoff.0 because enabled 2025-05-27 19:05:35.563 - info: javascript.0 (130737) starting. Version 8.8.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:37.971 - error: hm-rpc.2 (130829) hm-rpc.2 already running 2025-05-27 19:05:37.974 - warn: hm-rpc.2 (130829) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:38.202 - info: host.RoofServer instance system.adapter.ping.0 in version "1.6.2" started with pid 130866 2025-05-27 19:05:39.339 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130885 2025-05-27 19:05:39.795 - info: ical.0 (130720) Terminated (NO_ERROR): Without reason 2025-05-27 19:05:39.820 - error: host.RoofServer instance system.adapter.hm-rpc.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:39.820 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.2 because enabled 2025-05-27 19:05:39.833 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130894 -
@wendy2702 Eben die Zeilen 1-500, hier der Rest. Das merkwürdige Runterfahren ist hier eher am Anfang
2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.675 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.675 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.063 - info: sonoff.0 (130093) terminating with timeout 2025-05-27 19:03:49.064 - info: sonoff.0 (130093) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.064 - info: mielecloudservice.0 (130191) terminating with timeout 2025-05-27 19:03:49.065 - info: mielecloudservice.0 (130191) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.065 - info: lg-thinq.0 (130313) terminating with timeout 2025-05-27 19:03:49.066 - info: evcc.0 (130298) terminating with timeout 2025-05-27 19:03:49.066 - info: lg-thinq.0 (130313) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.067 - info: device-watcher.0 (130343) terminating with timeout 2025-05-27 19:03:49.069 - info: nut.0 (130221) terminating with timeout 2025-05-27 19:03:49.068 - info: device-watcher.0 (130343) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.069 - info: web.0 (130369) terminating with timeout 2025-05-27 19:03:49.071 - info: wiegand-tcpip.0 (130206) terminating with timeout 2025-05-27 19:03:49.071 - info: nut.0 (130221) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.072 - info: wiegand-tcpip.0 (130206) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.073 - info: modbus.0 (130253) terminating with timeout 2025-05-27 19:03:49.075 - info: homeconnect.0 (130169) terminating with timeout 2025-05-27 19:03:49.076 - info: homeconnect.0 (130169) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.077 - info: opendtu.0 (130328) terminating with timeout 2025-05-27 19:03:49.078 - info: opendtu.0 (130328) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.076 - info: modbus.1 (130268) terminating with timeout 2025-05-27 19:03:49.077 - info: modbus.1 (130268) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.079 - info: ping.0 (130135) terminating with timeout 2025-05-27 19:03:49.080 - info: backitup.0 (130078) terminating with timeout 2025-05-27 19:03:49.081 - info: backitup.0 (130078) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.070 - info: web.0 (130369) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.082 - info: discovery.0 (130358) terminating with timeout 2025-05-27 19:03:49.067 - info: evcc.0 (130298) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.074 - info: modbus.0 (130253) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.081 - info: ping.0 (130135) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.084 - info: tr-064.0 (129955) terminating with timeout 2025-05-27 19:03:49.084 - info: discovery.0 (130358) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.085 - info: tr-064.0 (129955) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.088 - info: telegram.0 (129928) terminating with timeout 2025-05-27 19:03:49.089 - info: telegram.0 (129928) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.089 - info: email.0 (129879) terminating with timeout 2025-05-27 19:03:49.091 - info: email.0 (129879) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.092 - info: hm-rega.0 (130033) terminating with timeout 2025-05-27 19:03:49.093 - info: hm-rega.0 (130033) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.095 - info: admin.0 (129805) terminating with timeout 2025-05-27 19:03:49.096 - info: admin.0 (129805) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.566 - info: hm-rpc.2 (130119) terminating with timeout 2025-05-27 19:03:49.567 - info: hm-rpc.2 (130119) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.583 - info: hm-rpc.1 (130018) terminating with timeout 2025-05-27 19:03:49.584 - info: hm-rpc.1 (130018) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.592 - info: hm-rpc.0 (130003) terminating with timeout 2025-05-27 19:03:49.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.593 - info: hm-rpc.0 (130003) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.508 - error: web.0 (130369) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.529 - error: wiegand-tcpip.0 (130206) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.534 - error: tuya.0 (130283) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.541 - error: mielecloudservice.0 (130191) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.546 - error: modbus.0 (130253) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.549 - error: backitup.0 (130078) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.551 - warn: discovery.0 (130358) get state error: Connection is closed. 2025-05-27 19:03:52.552 - warn: unifi.0 (130063) get state error: DB closed 2025-05-27 19:03:52.536 - error: tuya.0 (130283) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.558 - warn: hm-rega.0 (130033) get state error: Connection is closed. 2025-05-27 19:03:52.561 - error: hm-rpc.1 (130018) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.561 - info: hm-rega.0 (130033) terminating 2025-05-27 19:03:52.562 - error: telegram.0 (129928) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.549 - error: nut.0 (130221) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.566 - error: evcc.0 (130298) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.569 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.570 - error: admin.0 (129805) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.575 - error: opendtu.0 (130328) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.575 - error: hm-rpc.2 (130119) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.579 - warn: ping.0 (130135) get state error: Connection is closed. 2025-05-27 19:03:52.577 - warn: admin.0 (129805) get state error: Connection is closed. 2025-05-27 19:03:52.577 - warn: admin.0 (129805) get state error: DB closed 2025-05-27 19:03:52.578 - info: admin.0 (129805) terminating 2025-05-27 19:03:52.578 - info: admin.0 (129805) terminating 2025-05-27 19:03:52.581 - error: homeconnect.0 (130169) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.583 - error: lg-thinq.0 (130313) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.587 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.591 - warn: sonoff.0 (130093) get state error: Connection is closed. 2025-05-27 19:03:52.593 - error: modbus.1 (130268) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.591 - error: tr-064.0 (129955) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.596 - warn: backitup.0 (130078) get state error: Connection is closed. 2025-05-27 19:03:52.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.553 - error: device-watcher.0 (130343) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.606 - warn: hm-rpc.1 (130018) get state error: DB closed 2025-05-27 19:03:52.595 - error: hm-rpc.0 (130003) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.589 - error: history.0 (129834) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.592 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.alive, error - DB closed 2025-05-27 19:03:52.592 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.modeReadColors, error - DB closed 2025-05-27 19:03:52.593 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.alive, error - DB closed 2025-05-27 19:03:52.593 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.modeReadColors, error - DB closed 2025-05-27 19:03:52.593 - info: sonoff.0 (130093) terminating 2025-05-27 19:03:52.609 - error: email.0 (129879) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.564 - warn: nut.0 (130221) get state error: Connection is closed. 2025-05-27 19:03:52.565 - warn: nut.0 (130221) get state error: DB closed 2025-05-27 19:03:52.611 - info: nut.0 (130221) terminating 2025-05-27 19:03:52.612 - info: nut.0 (130221) terminating 2025-05-27 19:03:52.573 - warn: mielecloudservice.0 (130191) get state error: Connection is closed. 2025-05-27 19:03:52.574 - info: mielecloudservice.0 (130191) terminating 2025-05-27 19:03:52.577 - warn: hm-rpc.2 (130119) get state error: DB closed 2025-05-27 19:03:52.578 - warn: hm-rpc.2 (130119) get state error: DB closed 2025-05-27 19:03:52.625 - info: hm-rpc.2 (130119) terminating 2025-05-27 19:03:52.625 - info: hm-rpc.2 (130119) terminating 2025-05-27 19:03:52.578 - warn: opendtu.0 (130328) get state error: Connection is closed. 2025-05-27 19:03:52.578 - warn: opendtu.0 (130328) get state error: DB closed 2025-05-27 19:03:52.632 - info: opendtu.0 (130328) terminating 2025-05-27 19:03:52.633 - info: opendtu.0 (130328) terminating 2025-05-27 19:03:52.606 - warn: hm-rpc.1 (130018) get state error: DB closed 2025-05-27 19:03:52.637 - info: hm-rpc.1 (130018) terminating 2025-05-27 19:03:52.638 - info: hm-rpc.1 (130018) terminating 2025-05-27 19:03:52.583 - warn: homeconnect.0 (130169) get state error: Connection is closed. 2025-05-27 19:03:52.584 - warn: homeconnect.0 (130169) get state error: DB closed 2025-05-27 19:03:52.585 - info: homeconnect.0 (130169) terminating 2025-05-27 19:03:52.586 - info: homeconnect.0 (130169) terminating 2025-05-27 19:03:52.639 - warn: modbus.1 (130268) get state error: Connection is closed. 2025-05-27 19:03:52.643 - info: modbus.1 (130268) terminating 2025-05-27 19:03:52.620 - error: sql.0 (129913) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.662 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.663 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.663 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:53.563 - info: tuya.0 (130283) terminating with timeout 2025-05-27 19:03:53.564 - info: tuya.0 (130283) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:56.031 - info: homeconnect.0 (130169) Keep Alive failed Reconnect EventStream 2025-05-27 19:03:56.106 - error: homeconnect.0 (130169) 429 Too Many Requests 2025-05-27 19:03:56.106 - error: homeconnect.0 (130169) Start Event Stream Error: {"type":"error","status":429,"message":"Too Many Requests"} 2025-05-27 19:03:56.107 - info: homeconnect.0 (130169) Too many requests. Please wait 24h. 2025-05-27 19:03:57.552 - error: tuya.0 (130283) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.554 - warn: tuya.0 (130283) get state error: Connection is closed. 2025-05-27 19:03:57.555 - warn: tuya.0 (130283) get state error: DB closed 2025-05-27 19:03:57.556 - info: tuya.0 (130283) terminating 2025-05-27 19:03:57.557 - info: tuya.0 (130283) terminating 2025-05-27 19:03:57.567 - error: nut.0 (130221) Cannot check object existence of "nut.0.battery.charge": DB closed 2025-05-27 19:03:57.571 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.581 - error: opendtu.0 (130328) Cannot find view "system" for search "folder" : Connection is closed. 2025-05-27 19:03:57.592 - error: history.0 (129834) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:57.594 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.601 - error: modbus.1 (130268) Cannot find view "system" for search "state" : DB closed 2025-05-27 19:03:57.667 - error: sql.0 (129913) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:58.588 - info: history.0 (129834) terminating with timeout 2025-05-27 19:03:58.588 - info: history.0 (129834) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:58.594 - info: sql.0 (129913) terminating with timeout 2025-05-27 19:03:58.594 - info: sql.0 (129913) Terminated (NO_ERROR): Without reason 2025-05-27 19:04:02.574 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:04:02.596 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:04:02.597 - warn: history.0 (129834) get state error: Connection is closed. 2025-05-27 19:04:02.671 - warn: sql.0 (129913) get state error: Connection is closed. 2025-05-27 19:04:02.673 - warn: sql.0 (129913) get state error: DB closed 2025-05-27 19:04:02.673 - info: sql.0 (129913) terminating 2025-05-27 19:04:02.673 - info: sql.0 (129913) terminating 2025-05-27 19:04:31.403 - info: host.RoofServer iobroker.js-controller version 7.0.7 js-controller starting 2025-05-27 19:04:31.406 - info: host.RoofServer Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2025-05-27 19:04:31.407 - info: host.RoofServer hostname: RoofServer, node: v20.19.2 2025-05-27 19:04:31.407 - info: host.RoofServer ip addresses: 192.168.66.75 fe80::ee2c:259e:69f8:4bec fe80::bee1:cabf:72ba:3764 172.16.100.9 2025-05-27 19:04:33.422 - info: host.RoofServer connected to Objects and States 2025-05-27 19:04:33.439 - info: host.RoofServer added notifications configuration of host 2025-05-27 19:04:34.220 - info: host.RoofServer 62 instances found 2025-05-27 19:04:34.253 - info: host.RoofServer starting 54 instances 2025-05-27 19:04:34.839 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeCurrent" 2025-05-27 19:04:35.009 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeNewest" 2025-05-27 19:04:35.014 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeNewestNext" 2025-05-27 19:04:35.065 - info: host.RoofServer instance system.adapter.admin.0 in version "7.6.3" started with pid 130519 2025-05-27 19:04:35.068 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmCurrent" 2025-05-27 19:04:35.112 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmNewest" 2025-05-27 19:04:35.157 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmNewestNext" 2025-05-27 19:04:35.200 - info: host.RoofServer Some obsolete host states deleted. 2025-05-27 19:04:36.911 - error: admin.0 (130519) admin.0 already running 2025-05-27 19:04:36.913 - warn: admin.0 (130519) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:37.661 - error: host.RoofServer instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:37.662 - info: host.RoofServer Restart adapter system.adapter.admin.0 because enabled 2025-05-27 19:04:38.967 - info: host.RoofServer instance system.adapter.history.0 in version "3.0.1" started with pid 130530 2025-05-27 19:04:40.486 - error: history.0 (130530) history.0 already running 2025-05-27 19:04:40.488 - warn: history.0 (130530) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:41.203 - error: host.RoofServer instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:41.204 - info: host.RoofServer Restart adapter system.adapter.history.0 because enabled 2025-05-27 19:04:42.894 - info: host.RoofServer instance system.adapter.javascript.0 in version "8.8.3" started with pid 130541 2025-05-27 19:04:44.936 - error: javascript.0 (130541) javascript.0 already running 2025-05-27 19:04:44.938 - warn: javascript.0 (130541) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:45.667 - error: host.RoofServer instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:45.667 - info: host.RoofServer Restart adapter system.adapter.javascript.0 because enabled 2025-05-27 19:04:46.968 - info: host.RoofServer instance system.adapter.email.0 in version "2.0.3" started with pid 130584 2025-05-27 19:04:48.495 - error: email.0 (130584) email.0 already running 2025-05-27 19:04:48.497 - warn: email.0 (130584) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:49.205 - error: host.RoofServer instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:49.205 - info: host.RoofServer Restart adapter system.adapter.email.0 because enabled 2025-05-27 19:04:50.876 - info: host.RoofServer instance system.adapter.sql.0 in version "3.0.1" started with pid 130595 2025-05-27 19:04:52.427 - error: sql.0 (130595) sql.0 already running 2025-05-27 19:04:52.429 - warn: sql.0 (130595) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:53.139 - error: host.RoofServer instance system.adapter.sql.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:53.139 - info: host.RoofServer Restart adapter system.adapter.sql.0 because enabled 2025-05-27 19:04:54.991 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 130606 2025-05-27 19:04:56.917 - error: telegram.0 (130606) telegram.0 already running 2025-05-27 19:04:56.919 - warn: telegram.0 (130606) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:57.637 - error: host.RoofServer instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:57.637 - info: host.RoofServer Restart adapter system.adapter.telegram.0 because enabled 2025-05-27 19:04:59.570 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 130617 2025-05-27 19:04:59.582 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 130623 2025-05-27 19:05:02.151 - error: tr-064.0 (130617) tr-064.0 already running 2025-05-27 19:05:02.152 - warn: tr-064.0 (130617) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:02.878 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130641 2025-05-27 19:05:03.054 - error: host.RoofServer instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:03.054 - info: host.RoofServer Restart adapter system.adapter.tr-064.0 because enabled 2025-05-27 19:05:03.181 - info: telegram.0 (130623) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:03.771 - error: telegram.0 (130623) Failed sending [chatId - 1173210274]: Error: ETELEGRAM: 403 Forbidden: bot was blocked by the user 2025-05-27 19:05:04.551 - error: hm-rpc.0 (130641) hm-rpc.0 already running 2025-05-27 19:05:04.553 - warn: hm-rpc.0 (130641) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:05.258 - error: host.RoofServer instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:05.258 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.0 because enabled 2025-05-27 19:05:07.007 - info: host.RoofServer instance system.adapter.hm-rpc.1 in version "2.0.2" started with pid 130656 2025-05-27 19:05:08.693 - info: host.RoofServer instance system.adapter.admin.0 in version "7.6.3" started with pid 130667 2025-05-27 19:05:09.067 - error: hm-rpc.1 (130656) hm-rpc.1 already running 2025-05-27 19:05:09.069 - warn: hm-rpc.1 (130656) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:09.778 - error: host.RoofServer instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:09.779 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.1 because enabled 2025-05-27 19:05:10.967 - info: host.RoofServer instance system.adapter.hm-rega.0 in version "5.1.0" started with pid 130678 2025-05-27 19:05:12.195 - info: host.RoofServer instance system.adapter.history.0 in version "3.0.1" started with pid 130689 2025-05-27 19:05:12.860 - error: hm-rega.0 (130678) hm-rega.0 already running 2025-05-27 19:05:12.863 - warn: hm-rega.0 (130678) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:12.871 - info: admin.0 (130667) starting. Version 7.6.3 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:12.903 - info: admin.0 (130667) requesting all objects 2025-05-27 19:05:16.332 - error: host.RoofServer instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:16.333 - info: host.RoofServer Restart adapter system.adapter.hm-rega.0 because enabled 2025-05-27 19:05:16.536 - info: admin.0 (130667) received all objects 2025-05-27 19:05:17.243 - info: admin.0 (130667) socket.io server listening on port 8081 2025-05-27 19:05:17.244 - info: admin.0 (130667) http server listening on port 8081 2025-05-27 19:05:17.245 - info: admin.0 (130667) Use link "http://127.0.0.1:8081" to configure. 2025-05-27 19:05:18.279 - info: host.RoofServer instance scheduled system.adapter.ical.0 2,32 * * * * 2025-05-27 19:05:18.287 - info: host.RoofServer instance system.adapter.ical.0 in version "1.16.1" started with pid 130720 2025-05-27 19:05:19.921 - info: host.RoofServer instance system.adapter.javascript.0 in version "8.8.3" started with pid 130737 2025-05-27 19:05:21.039 - info: host.RoofServer instance system.adapter.unifi.0 in version "0.7.0" started with pid 130744 2025-05-27 19:05:21.268 - info: host.RoofServer instance system.adapter.email.0 in version "2.0.3" started with pid 130755 2025-05-27 19:05:21.904 - info: admin.0 (130667) ==> Connected system.user.admin from ::ffff:192.168.66.108 2025-05-27 19:05:28.629 - error: unifi.0 (130744) unifi.0 already running 2025-05-27 19:05:28.632 - warn: unifi.0 (130744) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:28.700 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130784 2025-05-27 19:05:28.889 - info: host.RoofServer instance system.adapter.sql.0 in version "3.0.1" started with pid 130791 2025-05-27 19:05:29.032 - info: host.RoofServer instance system.adapter.sonoff.0 in version "3.1.2" started with pid 130798 2025-05-27 19:05:29.048 - info: history.0 (130689) starting. Version 3.0.1 in /opt/iobroker/node_modules/iobroker.history, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:29.861 - error: host.RoofServer instance system.adapter.unifi.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:29.862 - info: host.RoofServer Restart adapter system.adapter.unifi.0 because enabled 2025-05-27 19:05:30.067 - info: ical.0 (130720) starting. Version 1.16.1 in /opt/iobroker/node_modules/iobroker.ical, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:30.298 - info: email.0 (130755) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.email, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:31.496 - info: ical.0 (130720) processing URL: MH https://calendar.google.com/calendar/ical/c530e1fa7a07a45ab04e116a7f389806477602687d99c31f461cc294fa6864d2%40group.calendar.google.com/private-063afafa12704b6d953907c2d98a219d/basic.ics 2025-05-27 19:05:32.834 - info: host.RoofServer instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 130829 2025-05-27 19:05:33.290 - error: backitup.0 (130784) backitup.0 already running 2025-05-27 19:05:33.292 - warn: backitup.0 (130784) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:33.696 - error: sonoff.0 (130798) sonoff.0 already running 2025-05-27 19:05:33.699 - warn: sonoff.0 (130798) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:34.351 - error: host.RoofServer instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:34.351 - info: host.RoofServer Restart adapter system.adapter.backitup.0 because enabled 2025-05-27 19:05:34.934 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 130840 2025-05-27 19:05:35.375 - error: host.RoofServer instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:35.376 - info: host.RoofServer Restart adapter system.adapter.sonoff.0 because enabled 2025-05-27 19:05:35.563 - info: javascript.0 (130737) starting. Version 8.8.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:37.971 - error: hm-rpc.2 (130829) hm-rpc.2 already running 2025-05-27 19:05:37.974 - warn: hm-rpc.2 (130829) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:38.202 - info: host.RoofServer instance system.adapter.ping.0 in version "1.6.2" started with pid 130866 2025-05-27 19:05:39.339 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130885 2025-05-27 19:05:39.795 - info: ical.0 (130720) Terminated (NO_ERROR): Without reason 2025-05-27 19:05:39.820 - error: host.RoofServer instance system.adapter.hm-rpc.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:39.820 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.2 because enabled 2025-05-27 19:05:39.833 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130894@wendy2702 Ist dwd.0 das Problem?
(Im 1. Logfile-Teil, ca Zeile 320)
2025-05-27 19:03:47.364 - error: dwd.0 (130400) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4' 2025-05-27 19:03:47.371 - error: host.RoofServer uncaught exception: Could not determine controller directory 2025-05-27 19:03:47.371 - error: host.RoofServer Error: Could not determine controller directory at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11) at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1306:37) at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3219:30) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) -
@wendy2702 Ist dwd.0 das Problem?
(Im 1. Logfile-Teil, ca Zeile 320)
2025-05-27 19:03:47.364 - error: dwd.0 (130400) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4' 2025-05-27 19:03:47.371 - error: host.RoofServer uncaught exception: Could not determine controller directory 2025-05-27 19:03:47.371 - error: host.RoofServer Error: Could not determine controller directory at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11) at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1306:37) at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3219:30) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9)Stoppen von dwd.0 hilft auch nicht
Nun finde ich sowas hier:
2025-05-27 19:21:38.759 - error: host.RoofServer startInstance statistics.0: cannot find start file! 2025-05-27 19:21:38.780 - error: web.0 (135592) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4'...passt da im hintergrund was mit dem Nod(JS) nicht? Kann ich das Node_modules vielleicht neu bauen lassen oder so?
Gruss -
-
Stoppen von dwd.0 hilft auch nicht
Nun finde ich sowas hier:
2025-05-27 19:21:38.759 - error: host.RoofServer startInstance statistics.0: cannot find start file! 2025-05-27 19:21:38.780 - error: web.0 (135592) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4'...passt da im hintergrund was mit dem Nod(JS) nicht? Kann ich das Node_modules vielleicht neu bauen lassen oder so?
Gruss -
-
@adarof sieht eher so aus als ob was mit deiner database nicht passt für mich.
Wenn das nach dem Admin Update angefangen hat würde ich mal nach dem Error 25 im Forum suchen.
Oder kam das nach dem Ubuntu Upgrade?
@wendy2702
Würde tippen dass es nach dem UbuntuUpgrade kam, da das Admin Upgrade nun auch immernoch ansteht könnte es auch einfach nicht durchgeführt worden sein.
Kann ich die Datenbank checken irgendwie? -
@wendy2702
Würde tippen dass es nach dem UbuntuUpgrade kam, da das Admin Upgrade nun auch immernoch ansteht könnte es auch einfach nicht durchgeführt worden sein.
Kann ich die Datenbank checken irgendwie?Sehe gerade:
Wenn ich "schnell" nach dem "Absturz" ein "iob logs" mache, bekomme ich sowas hier:hmersch@RoofServer:/opt/iobroker$ iob logs node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }....wenn ich dann 10 sek warte, tut es wieder.
Hat das vielleicht auch was damit zu tun?
-
@wendy2702
Würde tippen dass es nach dem UbuntuUpgrade kam, da das Admin Upgrade nun auch immernoch ansteht könnte es auch einfach nicht durchgeführt worden sein.
Kann ich die Datenbank checken irgendwie?@adarof Check ist mir erstmal nicht bekannt.
Was kam den bei der Ausführung von iob fix zurück?
Und ich würde trotzdem mal im Forum nach dem Error 25 suchen.
Edit: kann auch gut sein das der JS-Controller zerschossen ist. Installiere den doch mal neu
-
@adarof Check ist mir erstmal nicht bekannt.
Was kam den bei der Ausführung von iob fix zurück?
Und ich würde trotzdem mal im Forum nach dem Error 25 suchen.
Edit: kann auch gut sein das der JS-Controller zerschossen ist. Installiere den doch mal neu
@wendy2702
Geht das so?iob stop cd /opt/iobroker sudo -H -u iobroker npm reinstall iobroker.js-controllerergibt:
hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller npm warn skipping integrity check for git dependency ssh://git@github.com/theknut/ioBroker.waterkotte-easycon.git npm warn skipping integrity check for git dependency ssh://git@github.com/eifel-tech/ioBroker.syrconnect.git npm warn skipping integrity check for git dependency ssh://git@github.com/nbuenger/ioBroker.govee.git npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated q@1.1.2: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated multer@1.4.5-lts.2: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version. npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated sinon@15.2.0: 16.1.1 ⠦ removed 40 packages, and changed 1483 packages in 2m... aber nach "iob start" gleiches Verhalten :-(
"iob fix" sagt nun das hier:
hmersch@RoofServer:/opt/iobroker$ iob fix library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 205-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease OK:2 https://deb.nodesource.com/node_20.x nodistro InRelease Holen:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB] Holen:4 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal InRelease [4.418 B] OK:5 https://gcups-static.greencell.global/deb stable InRelease Holen:6 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB] Holen:7 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal/main amd64 Packages [36,7 kB] Holen:8 http://de.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [420 kB] Holen:9 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [114 kB] Holen:10 http://de.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 DEP-11 Metadata [212 B] Holen:11 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [359 kB] Holen:12 http://de.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B] Holen:13 http://de.archive.ubuntu.com/ubuntu jammy-backports/main amd64 DEP-11 Metadata [7.096 B] Holen:14 http://de.archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 DEP-11 Metadata [212 B] Holen:15 http://de.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [24,1 kB] Holen:16 http://de.archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 DEP-11 Metadata [212 B] OK:17 http://security.ubuntu.com/ubuntu jammy-security InRelease Es wurden 260 kB in 2 s geholt (126 kB/s). Paketlisten werden gelesen… Fertig N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot »https://deb.nodesource.com/node_20.x nodistro InRelease« die Architektur »i386« nicht unterstützt. ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Stoppen von »iobroker.service« notwendig. Multiple identities can be used for authentication: 1. user,,, (user) 2. hmersch 4. iobroker Choose identity to authenticate as (1-4): 2 Password: ==== AUTHENTICATION COMPLETE === Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Ich hatte schon nach Error-25 gesucht; meist scheint ein "iob fix" geholfen zu haben.
Meinst Du ich sollte "rm -rf node_modules" versuchen, wie hier beschrieben?
https://forum.iobroker.net/topic/56543/nach-nodejs-update-kein-adapter-mehr-updatebar/46 -
Keine Ahnung ob das hilft.
Kommt denn noch immer der Eintrag bezüglich JS Controller im log?
@wendy2702 Das ist doch mysteriös. Nun hatte ich bei "iob logs" (und auch iob status) permanent das hier:
node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }Also hab ich nochmal
"sudo -H -u iobroker npm reinstall iobroker.js-controller" gemacht
Nun tut das wieder. laut Logs ausgabe war nun ein anderer Adapter unglücklich:2025-05-27 19:59:11.436 - error: unifi.0 (144596) [updateUnifiData site default] error: Cannot find module './admin/lib/objects_wlans.json' Require stack: - /opt/iobroker/node_modules/iobroker.unifi/main.js, stack: Error: Cannot find module './admin/lib/objects_wlans.json'Alsob da im Hintergrund noch was passiert, was da Dateien löscht / kompiliert / generiert.
Noch eine Idee?
-
@wendy2702 Das ist doch mysteriös. Nun hatte ich bei "iob logs" (und auch iob status) permanent das hier:
node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }Also hab ich nochmal
"sudo -H -u iobroker npm reinstall iobroker.js-controller" gemacht
Nun tut das wieder. laut Logs ausgabe war nun ein anderer Adapter unglücklich:2025-05-27 19:59:11.436 - error: unifi.0 (144596) [updateUnifiData site default] error: Cannot find module './admin/lib/objects_wlans.json' Require stack: - /opt/iobroker/node_modules/iobroker.unifi/main.js, stack: Error: Cannot find module './admin/lib/objects_wlans.json'Alsob da im Hintergrund noch was passiert, was da Dateien löscht / kompiliert / generiert.
Noch eine Idee?
Beim nächsten start doch wieder js-controller:
2025-05-27 20:22:15.697 - info: web.0 (150845) starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v20.19.2, js-controller: 7.0.7 2025-05-27 20:22:15.733 - error: web.0 (150845) 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(). 2025-05-27 20:22:15.741 - info: vis.0 (150856) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.19.2, js-controller: 7.0.7 2025-05-27 20:22:15.734 - error: web.0 (150845) unhandled promise rejection: Cannot find i18n directory 2025-05-27 20:22:15.738 - error: web.0 (150845) Error: Cannot find i18n directory at Module.init (file:///opt/iobroker/node_modules/@iobroker/i18n/build/esm/index.js:45:15) at WebAdapter.onReady (/opt/iobroker/node_modules/iobroker.web/dist/main.js:561:26) 2025-05-27 20:22:15.739 - error: web.0 (150845) Cannot find i18n directory 2025-05-27 20:22:15.760 - warn: web.0 (150845) setTimeout called, but adapter is shutting down 2025-05-27 20:22:15.860 - error: vis.0 (150856) 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(). 2025-05-27 20:22:15.860 - error: vis.0 (150856) unhandled promise rejection: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/lib/../www/js/config.js' 2025-05-27 20:22:15.862 - error: vis.0 (150856) Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/lib/../www/js/config.js' at Object.openSync (node:fs:574:18) at Object.readFileSync (node:fs:453:35) at syncWidgetSets (/opt/iobroker/node_modules/iobroker.vis/lib/install.js:192:24) at generatePages (/opt/iobroker/node_modules/iobroker.vis/main.js:157:21) at main (/opt/iobroker/node_modules/iobroker.vis/main.js:235:32)Es scheinen immer Verzeichnisse nicht auffindbar zu sein. Wenn ich dann aber z.B. nach "/opt/iobroker/node_modules/iobroker.vis/lib/../www/widgets/" ist es vorhanden
-
@adarof kannst du den installations Befehl mal so ausführen
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob stop iob fix iob start iob updateAlso nicht mit „reinstall“
@wendy2702
iob stop war vorher, dann das hier:hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller npm warn skipping integrity check for git dependency ssh://git@github.com/theknut/ioBroker.waterkotte-easycon.git npm warn skipping integrity check for git dependency ssh://git@github.com/nbuenger/ioBroker.govee.git npm warn skipping integrity check for git dependency ssh://git@github.com/eifel-tech/ioBroker.syrconnect.git npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated q@1.1.2: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated multer@1.4.5-lts.2: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version. npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated sinon@15.2.0: 16.1.1 added 1 package, and changed 1484 packages in 2m 180 packages are looking for funding run `npm fund` for details hmersch@RoofServer:/opt/iobroker$ iob fix library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 205-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://security.ubuntu.com/ubuntu jammy-security InRelease OK:2 http://de.archive.ubuntu.com/ubuntu jammy InRelease OK:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease OK:4 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease OK:5 https://deb.nodesource.com/node_20.x nodistro InRelease OK:6 https://gcups-static.greencell.global/deb stable InRelease Holen:7 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal InRelease [4.418 B] Es wurden 4.418 B in 1 s geholt (5.136 B/s). Paketlisten werden gelesen… Fertig N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot »https://deb.nodesource.com/node_20.x nodistro InRelease« die Architektur »i386« nicht unterstützt. ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Stoppen von »iobroker.service« notwendig. Multiple identities can be used for authentication: 1. user,,, (user) 2. hmersch 4. iobroker Choose identity to authenticate as (1-4): 2 Password: ==== AUTHENTICATION COMPLETE === Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller^C hmersch@RoofServer:/opt/iobroker$ iob start hmersch@RoofServer:/opt/iobroker$ iob update Used repository: stable Adapter "admin" : 7.6.17 , installed 7.6.3 [Updatable] Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "amazon-dash" : 1.2.0 , installed 1.2.0 Adapter "backitup" : 3.2.2 , installed 3.0.31 [Updatable] Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "device-watcher": 2.12.1 , installed 2.12.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "easee" : 1.0.10 , installed 1.0.10 Adapter "email" : 2.0.4 , installed 2.0.3 [Updatable] Adapter "evcc" : 0.1.1 , installed 0.2.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.7 Adapter "klf200" : 1.3.5 , installed 1.3.5 Adapter "lg-thinq" : 1.1.0 , installed 1.1.0 Adapter "material" : 1.3.1 , installed 1.3.1 Adapter "mielecloudservice": 6.5.10, installed 6.5.10 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "nut" : 1.6.0 , installed 1.6.0 Adapter "opendtu" : 3.1.0 , installed 3.1.0 Adapter "parser" : 2.2.4 , installed 2.2.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "rickshaw" : 1.0.0 , installed 1.0.0 Adapter "sbfspot" : 4.4.2 , installed 4.4.2 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "wiegand-tcpip": 0.4.6 , installed 0.4.7 Adapter "ws" : 2.6.2 , installed 2.6.2 hmersch@RoofServer:/opt/iobroker$ -
@wendy2702
iob stop war vorher, dann das hier:hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller npm warn skipping integrity check for git dependency ssh://git@github.com/theknut/ioBroker.waterkotte-easycon.git npm warn skipping integrity check for git dependency ssh://git@github.com/nbuenger/ioBroker.govee.git npm warn skipping integrity check for git dependency ssh://git@github.com/eifel-tech/ioBroker.syrconnect.git npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated q@1.1.2: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated multer@1.4.5-lts.2: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version. npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated sinon@15.2.0: 16.1.1 added 1 package, and changed 1484 packages in 2m 180 packages are looking for funding run `npm fund` for details hmersch@RoofServer:/opt/iobroker$ iob fix library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 205-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://security.ubuntu.com/ubuntu jammy-security InRelease OK:2 http://de.archive.ubuntu.com/ubuntu jammy InRelease OK:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease OK:4 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease OK:5 https://deb.nodesource.com/node_20.x nodistro InRelease OK:6 https://gcups-static.greencell.global/deb stable InRelease Holen:7 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal InRelease [4.418 B] Es wurden 4.418 B in 1 s geholt (5.136 B/s). Paketlisten werden gelesen… Fertig N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot »https://deb.nodesource.com/node_20.x nodistro InRelease« die Architektur »i386« nicht unterstützt. ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Stoppen von »iobroker.service« notwendig. Multiple identities can be used for authentication: 1. user,,, (user) 2. hmersch 4. iobroker Choose identity to authenticate as (1-4): 2 Password: ==== AUTHENTICATION COMPLETE === Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller^C hmersch@RoofServer:/opt/iobroker$ iob start hmersch@RoofServer:/opt/iobroker$ iob update Used repository: stable Adapter "admin" : 7.6.17 , installed 7.6.3 [Updatable] Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "amazon-dash" : 1.2.0 , installed 1.2.0 Adapter "backitup" : 3.2.2 , installed 3.0.31 [Updatable] Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "device-watcher": 2.12.1 , installed 2.12.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "easee" : 1.0.10 , installed 1.0.10 Adapter "email" : 2.0.4 , installed 2.0.3 [Updatable] Adapter "evcc" : 0.1.1 , installed 0.2.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.7 Adapter "klf200" : 1.3.5 , installed 1.3.5 Adapter "lg-thinq" : 1.1.0 , installed 1.1.0 Adapter "material" : 1.3.1 , installed 1.3.1 Adapter "mielecloudservice": 6.5.10, installed 6.5.10 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "nut" : 1.6.0 , installed 1.6.0 Adapter "opendtu" : 3.1.0 , installed 3.1.0 Adapter "parser" : 2.2.4 , installed 2.2.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "rickshaw" : 1.0.0 , installed 1.0.0 Adapter "sbfspot" : 4.4.2 , installed 4.4.2 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "wiegand-tcpip": 0.4.6 , installed 0.4.7 Adapter "ws" : 2.6.2 , installed 2.6.2 hmersch@RoofServer:/opt/iobroker$Ich sehe da auch immer viele "error instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)" von unterschiedlichsten Adaptern.
Als ob iobroker alle Adapter mehrfach startet - was dann ja zu den Zugriffsproblemen führen könnteJedenfalls hat das npm install & fix & start & update keine Änderung gebracht
-
Ich sehe da auch immer viele "error instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)" von unterschiedlichsten Adaptern.
Als ob iobroker alle Adapter mehrfach startet - was dann ja zu den Zugriffsproblemen führen könnteJedenfalls hat das npm install & fix & start & update keine Änderung gebracht
-
Ich sehe da auch immer viele "error instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)" von unterschiedlichsten Adaptern.
Als ob iobroker alle Adapter mehrfach startet - was dann ja zu den Zugriffsproblemen führen könnteJedenfalls hat das npm install & fix & start & update keine Änderung gebracht
371
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge