Instanz wird neu gegestartet sobald ein Gerät "fertig" ist.

[Krys91]

Hi, bei mir wird unter der 3.0.0 die Instanz gekillt, sobald ein Gerät fertig ist. Die Ansage / Meldung über Alexa / Google Home / Telegram kommt, bspw. "Spülmaschinenist fertig." und anschließend startet die Instanz neu. Der Timer für das automatische Ausschalten läuft dann nicht mehr und das Gerät bleibt dauerhaft an.

System ist auf dem neusten Stand.

`device-reminder.0
2023-10-28 12:35:29.920 warn State "device-reminder.0.info.connection" has no existing object, this might lead to an error in future versions

device-reminder.0
2023-10-28 12:35:29.025 info starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.device-reminder, node: v18.18.2, js-controller: 5.0.12

device-reminder.0
2023-10-28 12:34:56.562 info terminating

device-reminder.0
2023-10-28 12:34:56.061 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

device-reminder.0
2023-10-28 12:34:56.060 info terminating

device-reminder.0
2023-10-28 12:34:56.056 error Converting circular structure to JSON --> starting at object with constructor 'Timeout' | property '_idlePrev' -> object with constructor 'TimersList' --- property '_idleNext' closes the circle

device-reminder.0
2023-10-28 12:34:56.056 error TypeError: Converting circular structure to JSON --> starting at object with constructor 'Timeout' | property '_idlePrev' -> object with constructor 'TimersList' --- property '_idleNext' closes the circle at JSON.stringify () at sendMsg (/opt/iobroker/node_modules/iobroker.device-reminder/main.js:1144:47)

device-reminder.0
2023-10-28 12:34:56.056 error unhandled promise rejection: Converting circular structure to JSON --> starting at object with constructor 'Timeout' | property '_idlePrev' -> object with constructor 'TimersList' --- property '_idleNext' closes the circle

device-reminder.0
2023-10-28 12:34:56.055 error 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().`

[Xenon-s]

fixed in 3.0.1