Error in Parsing Schedules: RangeError: Maximum call stack size exceeded #73

OberfragGER · 2023-08-22T08:28:41Z

Hi,

i own a new Doorbird D201x since 06/2023. So i have installed 2 instances of the Door-Adapter.

After a while, the Doorbird.1 (the new one) gives me a warning evey 3 Minutes:

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded

The adapter ist still green and everything seems to work fine.
After a restart of the adapter, everthing works good for 2-4 weeks an the the warning happens again.

Any hints?

The text was updated successfully, but these errors were encountered:

Schmakus · 2023-08-22T09:22:13Z

Which Adapter Version?

OberfragGER · 2023-08-22T09:27:07Z

Which Adapter Version?

Sorry. My specs:

iobroker Plattform linux Betriebssystem linux Architektur x64 CPUs 2 Geschwindigkeit 1596 MHz Modell Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz RAM 5 GB System-Betriebszeit 23 T. 11:30:56 Node.js v18.16.0 (Es gibt eine neuere Version: v18.17.1) time 1692696320386 timeOffset -120 Anzahl der Adapter 491 NPM 9.5.1 Datenträgergröße 7.78 GB freier Festplattenspeicher 4.29 GB Betriebszeit 7 T. 10:51:05 Aktive Instanzen 43 Weg /opt/iobroker/

Doorbird Adapter: v1.0.5

Schmakus · 2023-08-22T09:35:37Z

Please check the latest version 1.2.3.
If the error message appears again after a longer period of time, please report again. Thanks!

OberfragGER · 2023-08-22T09:50:19Z

Please check the latest version 1.2.3. If the error message appears again after a longer period of time, please report again. Thanks!

Done!

OberfragGER · 2023-08-31T08:58:02Z

Please check the latest version 1.2.3. If the error message appears again after a longer period of time, please report again. Thanks!

Ist happens today again.

Im on version 1.2.3

OberfragGER · 2023-08-31T09:02:19Z

Please check the latest version 1.2.3. If the error message appears again after a longer period of time, please report again. Thanks!

I set the adapter on debug (without restart). Look- i have a lot entry about the PIN code!
On the doorbird is a keypad attached and for testing things i setup a PIN-Code (240477).
So for me this could be a hint or?

- (Schmakus) tryed to fixed [#73] Maximum call stack size exceeded - (Stefan592) fixed 'listen on all interfaces'

Schmakus · 2023-08-31T15:37:22Z

Bitte prüfen mit v1.2.4

OberfragGER · 2023-09-01T06:32:02Z

Bitte prüfen mit v1.2.4

01.09.2023, 8:30 Uhr: Ist installiert. Ich melde mich falls es wieder kommt.

Klaus-Lucas · 2023-09-08T15:22:47Z

auch ich habe heute viele dieser Fehlermeldungen erhalten.

Admin version: 6.9.2
Adapter version: 1.2.4
JS-Controller version: 5.0.2
Node version: 18.17.1
Operating system: Ubuntu 22.04.3 LTS

2023-09-08 16:40:24.552 - warn: doorbird.0 (144859) Error in Parsing Schedules: RangeError: Maximum call stack size exceeded

2023-09-08 16:43:24.767 - warn: doorbird.0 (144859) Error in Parsing Schedules: RangeError: Maximum call stack size exceeded

OberfragGER · 2023-09-08T16:35:45Z

Ich bin mir unsicher, ob sich der Fehler von allein löst.

Hast du die Instanz seitdem neu gestartet? Bei mir scheint sich das zu fangen.

hast du irgendein „offizielles Zubehör“ dran? Also Keypad, Fingersensor o.ä.? Welche Doorbird? Ich habe die 210x

Klaus-Lucas · 2023-09-08T17:35:13Z

Ich habe jetzt die Instanz neu gestartet und momentan ist Ruhe. Aber der Fehler weißt ja drarauf hin, dass irgendwann der Stack überläuft, heißt es dauert eine Zeit nach einem Neustart des Adapters, bis der Fehler wieder auftritt. Schätze so 1 W. Meine Doorbird ist eine 2100.

Schmakus · 2023-09-09T06:00:18Z

Guten Morgen.
Der Fehler sagt, dass es zu einem Überlauf kommt. Meist, bzw. hauptsächlich in schleifen oder rekursiven Aufrufen.
Ich konnte den Fehler noch nicht identifizieren. Ich werde ein paar debug logs einbauen müssen.
Ich selbst habe merkwürdigerweise keine Fehler. Der Adapter läuft seit Wochen ohne Neustart.
Ein Neustart der Adapter schaft kurzfristig Abhilfe, bei betroffenen Systemen.

OberfragGER · 2023-09-09T07:16:06Z

Guten Morgen.
Der Fehler sagt, dass es zu einem Überlauf kommt. Meist, bzw. hauptsächlich in schleifen oder rekursiven Aufrufen.
Ich konnte den Fehler noch nicht identifizieren. Ich werde ein paar debug logs einbauen müssen.
Ich selbst habe merkwürdigerweise keine Fehler. Der Adapter läuft seit Wochen ohne Neustart.
Ein Neustart der Adapter schaft kurzfristig Abhilfe, bei betroffenen Systemen.

Wie gesagt. Ich habe 2 Doorbird 2100 und der Fehler tritt nur bei der Doorbird mit Keypad auf. Deshalb die Nachfrage an Klaus-Lucas da du ja meines Wissens auch kein weiteres Zubehör daran hst. Ich vermute einen Zusammenhang mit dem Keypad.

Auch bei mir läuft das immer ca. 1W.

Klaus-Lucas · 2023-09-09T11:05:26Z

Also meine Station besteht nur aus Kamera und 2 Klingeltastern. Fingerabdruckscanner hatte meine Tür schon gehabt.

Schmakus · 2023-09-09T12:26:13Z

Guten Morgen.

Der Fehler sagt, dass es zu einem Überlauf kommt. Meist, bzw. hauptsächlich in schleifen oder rekursiven Aufrufen.

Ich konnte den Fehler noch nicht identifizieren. Ich werde ein paar debug logs einbauen müssen.

Ich selbst habe merkwürdigerweise keine Fehler. Der Adapter läuft seit Wochen ohne Neustart.

Ein Neustart der Adapter schaft kurzfristig Abhilfe, bei betroffenen Systemen.

Wie gesagt. Ich habe 2 Doorbird 2100 und der Fehler tritt nur bei der Doorbird mit Keypad auf. Deshalb die Nachfrage an Klaus-Lucas da du ja meines Wissens auch kein weiteres Zubehör daran hst. Ich vermute einen Zusammenhang mit dem Keypad.

Kannst du bitte mal einen debug log hier Posten. Ich benötige den log nach Adapter Neustart.
Evtl. versucht der Adapter immer wieder Zeitpläne zu erstellen, obwohl nicht nötig.
Wird dir in den Objekten irgendwas im Zusammenhang mit dem Keypad angezeigt?

Klaus-Lucas · 2023-09-09T13:51:57Z

Also hier wäre dann meines, wobei bei:
"Cheking if Favorite for Doorbell ID 102 exists."
das fehlende "c" noch eingebaut werden sollte.

`

2023-09-09 15:47:09.419 - info: host.iobroker "system.adapter.doorbird.0" enabled
2023-09-09 15:47:09.477 - info: host.iobroker instance system.adapter.doorbird.0 started with pid 1411538
2023-09-09 15:47:09.684 - debug: doorbird.0 (1411538) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-09-09 15:47:09.699 - debug: doorbird.0 (1411538) Objects client ready ... initialize now
2023-09-09 15:47:09.699 - debug: doorbird.0 (1411538) Objects create System PubSub Client
2023-09-09 15:47:09.700 - debug: doorbird.0 (1411538) Objects create User PubSub Client
2023-09-09 15:47:09.714 - debug: doorbird.0 (1411538) Objects client initialize lua scripts
2023-09-09 15:47:09.716 - debug: doorbird.0 (1411538) Objects connected to redis: 127.0.0.1:9001
2023-09-09 15:47:09.728 - debug: doorbird.0 (1411538) Redis States: Use Redis connection: 127.0.0.1:9000
2023-09-09 15:47:09.733 - debug: doorbird.0 (1411538) States create System PubSub Client
2023-09-09 15:47:09.733 - debug: doorbird.0 (1411538) States create User PubSub Client
2023-09-09 15:47:09.783 - debug: doorbird.0 (1411538) States connected to redis: 127.0.0.1:9000
2023-09-09 15:47:09.836 - info: doorbird.0 (1411538) starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.doorbird, node: v18.17.1, js-controller: 5.0.12
2023-09-09 15:47:09.857 - debug: doorbird.0 (1411538) Server gestartet auf Port 8100 und IP 192.168.178.41
2023-09-09 15:47:09.910 - debug: doorbird.0 (1411538) Authorization with User ghhnoo0001 successful!
2023-09-09 15:47:09.938 - debug: doorbird.0 (1411538) Checking favorites on DoorBird Device..
2023-09-09 15:47:09.959 - debug: doorbird.0 (1411538) Found a Favorite that belongs to me.. (ID: '0') ('ioBroker doorbird.0 Motion': 'http://192.168.178.41:8100/motion')
2023-09-09 15:47:09.959 - debug: doorbird.0 (1411538) Found a Favorite that belongs to me.. (ID: '1') ('ioBroker doorbird.0 102 Ring': 'http://192.168.178.41:8100/ring?102')
2023-09-09 15:47:09.959 - debug: doorbird.0 (1411538) Found a Favorite that belongs to me.. (ID: '2') ('ioBroker doorbird.0 101 Ring': 'http://192.168.178.41:8100/ring?101')
2023-09-09 15:47:09.959 - debug: doorbird.0 (1411538) Result of Favorites: {"101":{"ID":"2","URL":"http://192.168.178.41:8100/ring?101"},"102":{"ID":"1","URL":"http://192.168.178.41:8100/ring?102"},"Motion":{"ID":"0","URL":"http://192.168.178.41:8100/motion"}}
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Following schedules found: [{"input":"doorbell","param":"102","output":[{"event":"http","param":"1","enabled":"1","schedule":{"weekdays":[{"from":"75600","to":"75599"}]}},{"event":"notify","param":"","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}]},{"input":"doorbell","param":"101","output":[{"event":"notify","param":"","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}},{"event":"http","param":"2","enabled":"1","schedule":{"weekdays":[{"from":"75600","to":"75599"}]}},{"event":"relay","param":"1","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}]},{"input":"motion","param":"","output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"","event":"notify"},{"event":"http","param":"0","enabled":"1","schedule":{"weekdays":[{"from":"75600","to":"75599"}]}}]},{"input":"relay","param":"1","output":[{"event":"relay","param":"ghlcty:2","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}]},{"input":"relay","param":"2","output":[]}]
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Looping through the Schedules..
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Detected a Doorbell Schedule!
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) The Param of the actual Schedule is: 102
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) The Output contains 2 entries!
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Entry "0" is: {"event":"http","param":"1","enabled":"1","schedule":{"weekdays":[{"from":"75600","to":"75599"}]}}
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Entry "1" is: {"event":"notify","param":"","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Counted 1 Doorbells.
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) Detected a Doorbell Schedule!
2023-09-09 15:47:10.006 - debug: doorbird.0 (1411538) The Param of the actual Schedule is: 101
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) The Output contains 3 entries!
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Entry "0" is: {"event":"notify","param":"","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Entry "1" is: {"event":"http","param":"2","enabled":"1","schedule":{"weekdays":[{"from":"75600","to":"75599"}]}}
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Entry "2" is: {"event":"relay","param":"1","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Counted 2 Doorbells.
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Detected Motion Schedule!
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) The Output contains 2 entries!
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Entry "0" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"","event":"notify"}
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Entry "1" is: {"event":"http","param":"0","enabled":"1","schedule":{"weekdays":[{"from":"75600","to":"75599"}]}}
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Checking if we need to create any favorites..
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Cheking if Favorite for Doorbell ID 102 exists.
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Favorite for Doorbell ID 102 exists!
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Checking if we need to create any favorites..
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Cheking if Favorite for Doorbell ID 101 exists.
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Favorite for Doorbell ID 101 exists!
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Checking if we need to create any favorites..
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Favorites checked successfully. No actions needed!
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Checking if we need to create Schedules on DoorBird Device..
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Okay we dont need to create any Doorbell-Schedules..
2023-09-09 15:47:10.007 - debug: doorbird.0 (1411538) Okay we dont need to create any Doorbell-Schedules..
`

Schmakus · 2023-09-11T12:22:38Z

@OberfragGER Kannst du mir bitte einen debug-log posten? Danke!

OberfragGER · 2023-09-11T12:38:08Z

@OberfragGER Kannst du mir bitte einen debug-log posten? Danke!

Klar. Ich bin auf 1.2.4

`

doorbird.1	2023-09-11 14:39:13.418	debug	Okay we dont need to create any Doorbell-Schedules..
doorbird.1	2023-09-11 14:39:13.418	debug	Okay we dont need to create any Doorbell-Schedules..
doorbird.1	2023-09-11 14:39:13.417	debug	Checking if we need to create Schedules on DoorBird Device..
doorbird.1	2023-09-11 14:39:13.417	debug	Favorites checked successfully. No actions needed!
doorbird.1	2023-09-11 14:39:13.417	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:39:13.416	debug	Favorite for Doorbell ID 240477 exists!
doorbird.1	2023-09-11 14:39:13.416	debug	Cheking if Favorite for Doorbell ID 240477 exists.
doorbird.1	2023-09-11 14:39:13.416	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:39:13.416	debug	Favorite for Doorbell ID 1 exists!
doorbird.1	2023-09-11 14:39:13.416	debug	Cheking if Favorite for Doorbell ID 1 exists.
doorbird.1	2023-09-11 14:39:13.416	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:39:13.415	debug	Favorite for Doorbell ID 240477 exists!
doorbird.1	2023-09-11 14:39:13.415	debug	Cheking if Favorite for Doorbell ID 240477 exists.
doorbird.1	2023-09-11 14:39:13.415	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:39:13.414	debug	Favorite for Doorbell ID 1 exists!
doorbird.1	2023-09-11 14:39:13.414	debug	Cheking if Favorite for Doorbell ID 1 exists.
doorbird.1	2023-09-11 14:39:13.414	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:39:13.414	debug	Counted 2 Doorbells.
doorbird.1	2023-09-11 14:39:13.414	debug	Entry "1" is: {"event":"http","param":"1","enabled":"1","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}
doorbird.1	2023-09-11 14:39:13.414	debug	Entry "0" is: {"event":"relay","param":"1","schedule":{"weekdays":[{"to":"79199","from":"79200"}]}}
doorbird.1	2023-09-11 14:39:13.414	debug	The Output contains 2 entries!
doorbird.1	2023-09-11 14:39:13.414	debug	The Param of the actual Schedule is: 240477
doorbird.1	2023-09-11 14:39:13.413	debug	Detected a Doorbell Schedule!
doorbird.1	2023-09-11 14:39:13.413	debug	Counted 1 Doorbells.
doorbird.1	2023-09-11 14:39:13.413	debug	Entry "4" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"2","event":"relay"}
doorbird.1	2023-09-11 14:39:13.413	debug	Entry "3" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"1","event":"relay"}
doorbird.1	2023-09-11 14:39:13.412	debug	Entry "2" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"0","event":"sip"}
doorbird.1	2023-09-11 14:39:13.412	debug	Entry "1" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"4","event":"http"}
doorbird.1	2023-09-11 14:39:13.412	debug	Entry "0" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"","event":"notify"}
doorbird.1	2023-09-11 14:39:13.412	debug	The Output contains 5 entries!
doorbird.1	2023-09-11 14:39:13.412	debug	The Param of the actual Schedule is: 1
doorbird.1	2023-09-11 14:39:13.412	debug	Detected a Doorbell Schedule!
doorbird.1	2023-09-11 14:39:13.412	debug	Looping through the Schedules..
doorbird.1	2023-09-11 14:39:13.411	debug	Following schedules found: [{"output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"","event":"notify"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"4","event":"http"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"0","event":"sip"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"1","event":"relay"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"2","event":"relay"}],"input":"doorbell","param":"1"},{"input":"doorbell","param":"240477","output":[{"event":"relay","param":"1","schedule":{"weekdays":[{"to":"79199","from":"79200"}]}},{"event":"http","param":"1","enabled":"1","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}]},{"output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"3","event":"http"}],"input":"relay","param":"2"},{"output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"2","event":"http"}],"input":"relay","param":"1"}]
doorbird.1	2023-09-11 14:39:13.210	debug	Result of Favorites: {"1":{"ID":"4","URL":"http://192.168.178.15:8101/ring?1"},"240477":{"ID":"1","URL":"http://192.168.178.15:8101/ring?240477"},"Motion":{"ID":"0","URL":"http://192.168.178.15:8101/motion"}}
doorbird.1	2023-09-11 14:39:13.210	debug	Found a Favorite that belongs to me.. (ID: '4') ('ioBroker doorbird.1 1 Ring': 'http://192.168.178.15:8101/ring?1')
doorbird.1	2023-09-11 14:39:13.209	debug	Found a Favorite that belongs to me.. (ID: '1') ('ioBroker doorbird.1 240477 Ring': 'http://192.168.178.15:8101/ring?240477')
doorbird.1	2023-09-11 14:39:13.209	debug	Found a Favorite that belongs to me.. (ID: '0') ('ioBroker doorbird.1 Motion': 'http://192.168.178.15:8101/motion')
doorbird.1	2023-09-11 14:39:13.177	debug	Checking favorites on DoorBird Device..
doorbird.1	2023-09-11 14:39:13.110	debug	Authorization with User XXX successful!
doorbird.1	2023-09-11 14:39:12.968	debug	Refresh connection check...
doorbird.1	2023-09-11 14:36:12.942	debug	Okay we dont need to create any Doorbell-Schedules..
doorbird.1	2023-09-11 14:36:12.942	debug	Okay we dont need to create any Doorbell-Schedules..
doorbird.1	2023-09-11 14:36:12.942	debug	Checking if we need to create Schedules on DoorBird Device..
doorbird.1	2023-09-11 14:36:12.941	debug	Favorites checked successfully. No actions needed!
doorbird.1	2023-09-11 14:36:12.941	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:36:12.941	debug	Favorite for Doorbell ID 240477 exists!
doorbird.1	2023-09-11 14:36:12.941	debug	Cheking if Favorite for Doorbell ID 240477 exists.
doorbird.1	2023-09-11 14:36:12.941	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:36:12.941	debug	Favorite for Doorbell ID 1 exists!
doorbird.1	2023-09-11 14:36:12.940	debug	Cheking if Favorite for Doorbell ID 1 exists.
doorbird.1	2023-09-11 14:36:12.940	debug	Checking if we need to create any favorites..
doorbird.1	2023-09-11 14:36:12.940	debug	Counted 2 Doorbells.
doorbird.1	2023-09-11 14:36:12.940	debug	Entry "1" is: {"event":"http","param":"1","enabled":"1","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}
doorbird.1	2023-09-11 14:36:12.940	debug	Entry "0" is: {"event":"relay","param":"1","schedule":{"weekdays":[{"to":"79199","from":"79200"}]}}
doorbird.1	2023-09-11 14:36:12.939	debug	The Output contains 2 entries!
doorbird.1	2023-09-11 14:36:12.939	debug	The Param of the actual Schedule is: 240477
doorbird.1	2023-09-11 14:36:12.939	debug	Detected a Doorbell Schedule!
doorbird.1	2023-09-11 14:36:12.939	debug	Counted 1 Doorbells.
doorbird.1	2023-09-11 14:36:12.939	debug	Entry "4" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"2","event":"relay"}
doorbird.1	2023-09-11 14:36:12.939	debug	Entry "3" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"1","event":"relay"}
doorbird.1	2023-09-11 14:36:12.939	debug	Entry "2" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"0","event":"sip"}
doorbird.1	2023-09-11 14:36:12.938	debug	Entry "1" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"4","event":"http"}
doorbird.1	2023-09-11 14:36:12.938	debug	Entry "0" is: {"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"","event":"notify"}
doorbird.1	2023-09-11 14:36:12.938	debug	The Output contains 5 entries!
doorbird.1	2023-09-11 14:36:12.938	debug	The Param of the actual Schedule is: 1
doorbird.1	2023-09-11 14:36:12.938	debug	Detected a Doorbell Schedule!
doorbird.1	2023-09-11 14:36:12.937	debug	Looping through the Schedules..
doorbird.1	2023-09-11 14:36:12.937	debug	Following schedules found: [{"output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"","event":"notify"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"4","event":"http"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"0","event":"sip"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"1","event":"relay"},{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"2","event":"relay"}],"input":"doorbell","param":"1"},{"input":"doorbell","param":"240477","output":[{"event":"relay","param":"1","schedule":{"weekdays":[{"to":"79199","from":"79200"}]}},{"event":"http","param":"1","enabled":"1","schedule":{"weekdays":[{"from":"79200","to":"79199"}]}}]},{"output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"3","event":"http"}],"input":"relay","param":"2"},{"output":[{"schedule":{"weekdays":[{"from":"79200","to":"79199"}]},"param":"2","event":"http"}],"input":"relay","param":"1"}]
doorbird.1	2023-09-11 14:36:12.900	debug	Result of Favorites: {"1":{"ID":"4","URL":"http://192.168.178.15:8101/ring?1"},"240477":{"ID":"1","URL":"http://192.168.178.15:8101/ring?240477"},"Motion":{"ID":"0","URL":"http://192.168.178.15:8101/motion"}}
doorbird.1	2023-09-11 14:36:12.900	debug	Found a Favorite that belongs to me.. (ID: '4') ('ioBroker doorbird.1 1 Ring': 'http://192.168.178.15:8101/ring?1')
doorbird.1	2023-09-11 14:36:12.899	debug	Found a Favorite that belongs to me.. (ID: '1') ('ioBroker doorbird.1 240477 Ring': 'http://192.168.178.15:8101/ring?240477')
doorbird.1	2023-09-11 14:36:12.899	debug	Found a Favorite that belongs to me.. (ID: '0') ('ioBroker doorbird.1 Motion': 'http://192.168.178.15:8101/motion')
doorbird.1	2023-09-11 14:36:12.863	debug	Checking favorites on DoorBird Device..
doorbird.1	2023-09-11 14:36:12.723	debug	Authorization with User XXX successful!
doorbird.1	2023-09-11 14:36:12.645	debug	Server gestartet auf Port 8101 und IP 192.168.178.15
doorbird.1	2023-09-11 14:36:12.528	info	starting. Version 1.2.4 (non-npm: iobroker-community-adapters/ioBroker.doorbird#38add291a78a3ba5f5206c67e0398da2ea025c84) in /opt/iobroker/node_modules/iobroker.doorbird, node: v18.17.1, js-controller: 4.0.24
doorbird.1	2023-09-11 14:36:12.039	debug	States connected to redis: 127.0.0.1:9000
doorbird.1	2023-09-11 14:36:11.907	debug	States create User PubSub Client
doorbird.1	2023-09-11 14:36:11.906	debug	States create System PubSub Client
doorbird.1	2023-09-11 14:36:11.853	debug	Redis States: Use Redis connection: 127.0.0.1:9000
doorbird.1	2023-09-11 14:36:11.798	debug	Objects connected to redis: 127.0.0.1:9001
doorbird.1	2023-09-11 14:36:11.791	debug	Objects client initialize lua scripts
doorbird.1	2023-09-11 14:36:11.627	debug	Objects create User PubSub Client
doorbird.1	2023-09-11 14:36:11.625	debug	Objects create System PubSub Client
doorbird.1	2023-09-11 14:36:11.620	debug	Objects client ready ... initialize now
doorbird.1	2023-09-11 14:36:11.521	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
doorbird.1	2023-09-11 14:36:03.948	debug	Server closed

`

Alle 3 Minuten wiederholt sich ein Großteil von dem. Da kommt dann immer:
Looping through the Schedules..

Negalein · 2023-10-11T17:58:04Z

heute wieder Warn-Meldungen

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded. Error-Stack: RangeError: Maximum call stack size exceeded at strEscape (/opt/iobroker/node_modules/safe-stable-stringify/index.js:29:54) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:188:16) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:256:23) at stringify (/opt/iobroker/node_modules/safe-stable-stringify/index.js:598:18) at Format.transform (/opt/iobroker/node_modules/logform/json.js:28:19) at Format.transform (/opt/iobroker/node_modules/logform/combine.js:20:24) at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:313:29) at Transform._read (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:166:10) at Transform._write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:155:83) at doWrite (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:390:139)

Schmakus · 2023-10-11T18:34:04Z

heute wieder Warn-Meldungen


Error in Parsing Schedules: RangeError: Maximum call stack size exceeded. Error-Stack: RangeError: Maximum call stack size exceeded at strEscape (/opt/iobroker/node_modules/safe-stable-stringify/index.js:29:54) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:188:16) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:256:23) at stringify (/opt/iobroker/node_modules/safe-stable-stringify/index.js:598:18) at Format.transform (/opt/iobroker/node_modules/logform/json.js:28:19) at Format.transform (/opt/iobroker/node_modules/logform/combine.js:20:24) at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:313:29) at Transform._read (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:166:10) at Transform._write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:155:83) at doWrite (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:390:139)

Hi. Du hast auch ein Keypad?
Ich werde mal ne Beta machen mit anderer Logik. Den Link werde ich dann hier posten zum Testen.

Negalein · 2023-10-11T18:42:34Z

Hi. Du hast auch ein Keypad?

Nein, kein Keypad!
Ich hab die D2102V

Ich hab damals schon ein Issue eröffnet.
#66

OberfragGER · 2023-10-11T18:58:14Z

@Schmakus Da ich sowieso den Logparser verwende, habe ich nun einmal "RangeError" in die Überwachung genommen (ich bekomm dann eine Telegram-Nachricht).

Bisher aber alles ruhig die letzte Zeit.

OberfragGER · 2023-10-16T11:29:04Z

Also der Fehler ist bei mir immer noch da. Allerdings hat sich das System anscheinend von selbst wieder erholt.

Stefan592 · 2023-11-28T19:05:55Z

Ich habe den Fehler heute mit der aktuellen Version V1.3.0 bekommen.

System: Docker
Doorbird: 1 Station

Der Fehler kommt alle ~3 Minuten:

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded. Error-Stack: RangeError: Maximum call stack size exceeded at strEscape (/opt/iobroker/node_modules/safe-stable-stringify/index.js:29:54) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:188:16) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:256:23) at stringify (/opt/iobroker/node_modules/safe-stable-stringify/index.js:598:18) at Format.transform (/opt/iobroker/node_modules/logform/json.js:28:19) at Format.transform (/opt/iobroker/node_modules/logform/combine.js:20:24) at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:313:29) at Transform._read (/opt/iobroker/node_modules/readable-stream/lib/_stream_transform.js:177:10) at Transform._write (/opt/iobroker/node_modules/readable-stream/lib/_stream_transform.js:164:83) at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:409:139)

OberfragGER · 2023-12-20T20:25:50Z

Jupp. Fehler ist bei mir auch wieder da. Version 1.3.0.
Dieses mal bei Instanz 0. Eine Normale D21xx ohne Keypad etc.

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded. Error-Stack: RangeError: Maximum call stack size exceeded at strEscape (/opt/iobroker/node_modules/safe-stable-stringify/index.js:29:54) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:188:16) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:256:23) at stringify (/opt/iobroker/node_modules/safe-stable-stringify/index.js:598:18) at Format.transform (/opt/iobroker/node_modules/logform/json.js:28:19) at Format.transform (/opt/iobroker/node_modules/logform/combine.js:20:24) at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:313:29) at Transform._read (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:166:10) at Transform._write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:155:83) at doWrite (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:390:139)

Interessant... auch hier der Fehler recht konstant alle 3 Minuten.

Nach Adapter-Neustart erstmal Ruhe.

PeterMarkl · 2024-01-17T07:29:11Z

Ich bekomme den Fehler leider auch alle 3 Minuten:
2024-01-17 06:55:57.814 - warn: doorbird.1 (1747) Error in Parsing Schedules: RangeError: Maximum call stack size exceeded. Error-Stack: RangeError: Maximum call stack size exceeded at strEscape (/opt/iobroker/node_modules/safe-stable-stringify/index.js:29:54) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:188:16) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:256:23) at stringify (/opt/iobroker/node_modules/safe-stable-stringify/index.js:598:18) at Format.transform (/opt/iobroker/node_modules/logform/json.js:28:19) at Format.transform (/opt/iobroker/node_modules/logform/combine.js:20:24) at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:313:29) at Transform._read (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:166:10) at Transform._write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:155:83) at doWrite (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:390:139)

PEPITO82 · 2024-01-25T11:53:20Z

Ich bekomme den Fehler bei meiner D1101V auch alle drei Minuten:

doorbird.0 | 2024-01-25 12:48:50.885 | warn | Error in Parsing Schedules: RangeError: Maximum call stack size exceeded. Error-Stack: RangeError: Maximum call stack size exceeded at strEscape (/opt/iobroker/node_modules/safe-stable-stringify/index.js:58:54) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:240:20) at stringifyFnReplacer (/opt/iobroker/node_modules/safe-stable-stringify/index.js:314:23) at stringify (/opt/iobroker/node_modules/safe-stable-stringify/index.js:659:18) at Format.transform (/opt/iobroker/node_modules/logform/json.js:28:19) at Format.transform (/opt/iobroker/node_modules/logform/combine.js:20:24) at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:313:29) at Transform._read (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:177:10) at Transform._write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:164:83) at doWrite (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:409:139)

Schmakus · 2024-02-22T08:38:10Z

please check v.1.4.1 in beta repo.

OberfragGER · 2024-02-23T20:46:11Z

please check v.1.4.1 in beta repo.

Ok. Is installed now. Lets see...
Thanks a lot in advance.

Schmakus added a commit that referenced this issue Aug 31, 2023

chore: release v1.2.4

1e515cf

- (Schmakus) tryed to fixed [#73] Maximum call stack size exceeded - (Stefan592) fixed 'listen on all interfaces'

Schmakus added the bug Something isn't working label Sep 1, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded #73

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded #73

OberfragGER commented Aug 22, 2023 •

edited

Loading

Schmakus commented Aug 22, 2023

OberfragGER commented Aug 22, 2023

Schmakus commented Aug 22, 2023

OberfragGER commented Aug 22, 2023

OberfragGER commented Aug 31, 2023

OberfragGER commented Aug 31, 2023 •

edited

Loading

Schmakus commented Aug 31, 2023

OberfragGER commented Sep 1, 2023

Klaus-Lucas commented Sep 8, 2023 •

edited

Loading

OberfragGER commented Sep 8, 2023

Klaus-Lucas commented Sep 8, 2023

Schmakus commented Sep 9, 2023

OberfragGER commented Sep 9, 2023

Klaus-Lucas commented Sep 9, 2023 •

edited

Loading

Schmakus commented Sep 9, 2023

Klaus-Lucas commented Sep 9, 2023

Schmakus commented Sep 11, 2023

OberfragGER commented Sep 11, 2023 •

edited

Loading

Negalein commented Oct 11, 2023

Schmakus commented Oct 11, 2023

Negalein commented Oct 11, 2023 •

edited

Loading

OberfragGER commented Oct 11, 2023

OberfragGER commented Oct 16, 2023

Stefan592 commented Nov 28, 2023 •

edited

Loading

OberfragGER commented Dec 20, 2023 •

edited

Loading

PeterMarkl commented Jan 17, 2024

PEPITO82 commented Jan 25, 2024

Schmakus commented Feb 22, 2024

OberfragGER commented Feb 23, 2024

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded #73

Error in Parsing Schedules: RangeError: Maximum call stack size exceeded #73

Comments

OberfragGER commented Aug 22, 2023 • edited Loading

Schmakus commented Aug 22, 2023

OberfragGER commented Aug 22, 2023

Schmakus commented Aug 22, 2023

OberfragGER commented Aug 22, 2023

OberfragGER commented Aug 31, 2023

OberfragGER commented Aug 31, 2023 • edited Loading

Schmakus commented Aug 31, 2023

OberfragGER commented Sep 1, 2023

Klaus-Lucas commented Sep 8, 2023 • edited Loading

OberfragGER commented Sep 8, 2023

Klaus-Lucas commented Sep 8, 2023

Schmakus commented Sep 9, 2023

OberfragGER commented Sep 9, 2023

Klaus-Lucas commented Sep 9, 2023 • edited Loading

Schmakus commented Sep 9, 2023

Klaus-Lucas commented Sep 9, 2023

`

Schmakus commented Sep 11, 2023

OberfragGER commented Sep 11, 2023 • edited Loading

Negalein commented Oct 11, 2023

Schmakus commented Oct 11, 2023

Negalein commented Oct 11, 2023 • edited Loading

OberfragGER commented Oct 11, 2023

OberfragGER commented Oct 16, 2023

Stefan592 commented Nov 28, 2023 • edited Loading

OberfragGER commented Dec 20, 2023 • edited Loading

PeterMarkl commented Jan 17, 2024

PEPITO82 commented Jan 25, 2024

Schmakus commented Feb 22, 2024

OberfragGER commented Feb 23, 2024

OberfragGER commented Aug 22, 2023 •

edited

Loading

OberfragGER commented Aug 31, 2023 •

edited

Loading

Klaus-Lucas commented Sep 8, 2023 •

edited

Loading

Klaus-Lucas commented Sep 9, 2023 •

edited

Loading

OberfragGER commented Sep 11, 2023 •

edited

Loading

Negalein commented Oct 11, 2023 •

edited

Loading

Stefan592 commented Nov 28, 2023 •

edited

Loading

OberfragGER commented Dec 20, 2023 •

edited

Loading