<![CDATA[Fehlermeldung "setState not processed"]]>Hallo zusammen,

die Meldung "setState not processed because States database not connected" bekomme ich derzeit für ein paar Minuten von einem Adapter. Dann ist wieder eine Weile Ruhe, dann tauchen die Meldungen wieder im Log auf.

Die Meldungen kommen von verschiedenen Adaptern wie backitup oder kecontact.

Weitere Meldungen, die ich da noch sehe:

  • getForeignState not processed because States database not connected
  • [iobroker] history json could not be created: TypeError: Cannot read properties of null (reading 'setState')

Backitup meldet außerdem einen Fehler beim Sichern:
Letzte iobroker Sicherung:
error: 07. August 2022 um 02:43 Uhr

Die Sicherung liegt aber wie gewohnt in Verzeichnis meines NAS.

Node-js v16.16
NPM 8.11
Admin 5.3.8
Nutzung von compact mode

Zur Meldung finde ich bei Google nur drei Treffer, die mich nicht weiterbringen.

]]>https://forum.iobroker.net/topic/56984/fehlermeldung-setstate-not-processedRSS for NodeMon, 11 May 2026 21:16:24 GMTSun, 07 Aug 2022 13:59:34 GMT60<![CDATA[Reply to Fehlermeldung "setState not processed" on Fri, 24 Feb 2023 14:03:15 GMT]]>@DJMarc75 leider geht es wieder los mit den Meldungen.

kecontact.0	2023-02-24 14:50:11.019	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:11.016	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:11.018	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:11.014	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.905	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.905	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.903	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.901	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.900	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.898	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.902	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:10.893	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:08.640	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:08.638	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:08.639	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:08.637	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:00.020	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:00.017	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:00.019	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:50:00.015	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:49:51.513	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:49:51.511	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:49:51.512	info	(COMPACT) setState not processed because States database not connected
kecontact.0	2023-02-24 14:49:51.510	info	(COMPACT) setState not processed because States database not connected

hier mal die Outputs wie beim letzten Mal:

sudo ln -s /usr/bin/node /usr/bin/nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

ln: failed to create symbolic link '/usr/bin/nodejs': File exists
armv7l
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.16.0
v16.16.0
8.11.0
pi
/home/pi
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
111 packages can be upgraded. Run 'apt list --upgradable' to see them.
nodejs:
  Installed: 16.16.0-deb-1nodesource1
  Candidate: 16.19.1-deb-1nodesource1
  Version table:
     16.19.1-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
 *** 16.16.0-deb-1nodesource1 100
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u3 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages

und

iobroker update -i

Used repository: stable
Adapter    "admin"        : 6.3.5    , installed 6.3.5
Adapter    "backitup"     : 2.5.12   , installed 2.5.12
Adapter    "discovery"    : 3.1.0    , installed 3.1.0
Adapter    "email"        : 1.1.4    , installed 1.1.4
Adapter    "feiertage"    : 1.1.0    , installed 1.1.0
Adapter    "flot"         : 1.11.0   , installed 1.11.0
Adapter    "history"      : 2.2.4    , installed 2.2.4
Adapter    "hm-rega"      : 3.0.43   , installed 3.0.43
Adapter    "hm-rpc"       : 1.15.16  , installed 1.15.16
Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
Adapter    "info"         : 1.9.19   , installed 1.9.19
Adapter    "javascript"   : 6.1.4    , installed 6.1.4
Controller "js-controller": 4.0.24   , installed 4.0.24
Adapter    "kecontact"    : 1.5.2    , installed 1.5.2
Adapter    "mobile"       : 1.0.1    , installed 1.0.1
Adapter    "modbus"       : 5.0.11   , installed 5.0.11
Adapter    "musiccast"    : 0.1.5    , installed 0.1.5
Adapter    "netatmo"      : 2.0.5    , installed 2.0.5
Adapter    "ping"         : 1.5.3    , installed 1.5.3
Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "socketio"     : 4.2.0    , installed 4.2.0
Adapter    "sonos"        : 2.2.3    , installed 2.2.3
Adapter    "sql"          : 2.2.0    , installed 2.2.0
Adapter    "tr-064"       : 4.2.17   , installed 4.2.17
Adapter    "vis"          : 1.4.15   , installed 1.4.15
Adapter    "vis-icontwo"  : 0.90.0   , installed 0.90.0
Adapter    "vis-inventwo" : 3.3.1    , installed 3.3.1
Adapter    "vw-connect"   : 0.0.56   , installed 0.0.60
Adapter    "web"          : 4.3.0    , installed 4.3.0
Adapter    "whatsapp-cmb" : 0.2.3    , installed 0.2.3
Adapter    "ws"           : 1.3.0    , installed 1.3.0
Adapter    "yamaha"       : 0.5.3    , installed 0.5.3

Kann das ein Programierfehler im Adapter sein? Oder irgendein Timing-Problem?

]]>https://forum.iobroker.net/post/952816https://forum.iobroker.net/post/952816Fri, 24 Feb 2023 14:03:15 GMT<![CDATA[Reply to Fehlermeldung "setState not processed" on Sun, 07 Aug 2022 20:40:26 GMT]]>@djmarc75

pi@raspberrypi:~ $ iobroker update -i
Used repository: stable
Adapter    "admin"        : 5.3.8    , installed 5.3.8
Adapter    "backitup"     : 2.4.10   , installed 2.4.10
Adapter    "discovery"    : 3.0.5    , installed 3.0.5
Adapter    "email"        : 1.1.3    , installed 1.1.3
Adapter    "feiertage"    : 1.1.0    , installed 1.1.0
Adapter    "flot"         : 1.11.0   , installed 1.11.0
Adapter    "history"      : 2.2.0    , installed 2.2.0
Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
Adapter    "info"         : 1.9.19   , installed 1.9.19
Adapter    "javascript"   : 5.7.0    , installed 5.7.0
Controller "js-controller": 4.0.23   , installed 4.0.23
Adapter    "kecontact"    : 1.4.1    , installed 1.4.1
Adapter    "mobile"       : 1.0.1    , installed 1.0.1
Adapter    "modbus"       : 5.0.4    , installed 5.0.4
Adapter    "musiccast"    : 0.1.5    , installed 0.1.5
Adapter    "netatmo"      : 1.7.1    , installed 1.7.1
Adapter    "ping"         : 1.5.3    , installed 1.5.3
Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
Adapter    "simple-api"   : 2.7.0    , installed 2.7.0
Adapter    "socketio"     : 4.2.0    , installed 4.2.0
Adapter    "sonos"        : 2.2.3    , installed 2.2.3
Adapter    "sql"          : 2.1.7    , installed 2.1.7
Adapter    "tr-064"       : 4.2.16   , installed 4.2.16
Adapter    "vis"          : 1.4.15   , installed 1.4.15
Adapter    "vis-icontwo"  : 0.89.0   , installed 0.89.0
Adapter    "vis-inventwo" : 3.3.1    , installed 3.3.1
Adapter    "vw-connect"   : 0.0.51   , installed 0.0.51
Adapter    "web"          : 4.3.0    , installed 4.3.0
Adapter    "ws"           : 1.3.0    , installed 1.3.0
Adapter    "yamaha"       : 0.5.3    , installed 0.5.3
]]>https://forum.iobroker.net/post/839517https://forum.iobroker.net/post/839517Sun, 07 Aug 2022 20:40:26 GMT<![CDATA[Reply to Fehlermeldung "setState not processed" on Sun, 07 Aug 2022 19:36:31 GMT]]>@sneak-l8

und mal bitte noch

iobroker update -i
]]>https://forum.iobroker.net/post/839501https://forum.iobroker.net/post/839501Sun, 07 Aug 2022 19:36:31 GMT<![CDATA[Reply to Fehlermeldung "setState not processed" on Sun, 07 Aug 2022 19:12:57 GMT]]>@djmarc75 Gerne:

pi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs

uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
armv7l
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.16.0
v16.16.0
8.11.0
pi
/home/pi
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
nodejs:
  Installed: 16.16.0-deb-1nodesource1
  Candidate: 16.16.0-deb-1nodesource1
  Version table:
 *** 16.16.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
]]>https://forum.iobroker.net/post/839488https://forum.iobroker.net/post/839488Sun, 07 Aug 2022 19:12:57 GMT<![CDATA[Reply to Fehlermeldung "setState not processed" on Sun, 07 Aug 2022 18:29:41 GMT]]>@sneak-l8 sagte in Fehlermeldung "setState not processed":

weder die Ursache klar noch ob es wieder vorkommen wird

Na dann fangen wir mal einfach damit an dass Du von Folgendem die komplette Ein- und Ausgabe hier in Codetags postest...

sudo ln -s /usr/bin/node /usr/bin/nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

dann wissen wir schonmal wie Du wo unterwegs bist.

]]>https://forum.iobroker.net/post/839471https://forum.iobroker.net/post/839471Sun, 07 Aug 2022 18:29:41 GMT<![CDATA[Reply to Fehlermeldung "setState not processed" on Sun, 07 Aug 2022 18:17:57 GMT]]>@djmarc75 Ne, noch nicht. Wollte erst mal hören, ob ich in den Zustand etwas testen soll oder so.
Ist ja schön, wenn es nach einem Reboot weg ist, aber dann ist weder die Ursache klar noch ob es wieder vorkommen wird.

]]>https://forum.iobroker.net/post/839468https://forum.iobroker.net/post/839468Sun, 07 Aug 2022 18:17:57 GMT<![CDATA[Reply to Fehlermeldung "setState not processed" on Sun, 07 Aug 2022 14:09:49 GMT]]>@sneak-l8 sagte in Fehlermeldung "setState not processed":

setState not processed because States database not connected

System schonmal rebootet?

]]>https://forum.iobroker.net/post/839389https://forum.iobroker.net/post/839389Sun, 07 Aug 2022 14:09:49 GMT