BUG] (Memory allocation issue -> Homebridge fails to start due to memory allocation failure with homebridge-magichome-dynamic-platform plugin)

[kilianp07]

Logs

Debug mode enabled in Homebridge.
Reproduced the issue, resulting in the error message mentioned above.
When attempting to start Homebridge with the "homebridge-magichome-dynamic-platform" plugin enabled, the following error is displayed:

<--- Last few GCs --->
[21326:0x5cb3c50]    31593 ms: Scavenge 219.7 (237.7) -> 219.6 (238.2) MB, 14.7 / 0.0 ms  (average mu = 0.901, current mu = 0.782) allocation failure; 
[21326:0x5cb3c50]    31619 ms: Scavenge 220.1 (238.2) -> 220.0 (239.7) MB, 16.3 / 0.0 ms  (average mu = 0.901, current mu = 0.782) allocation failure; 
[21326:0x5cb3c50]    32579 ms: Mark-sweep 336.3 (355.4) -> 219.3 (289.6) MB, 448.3 / 0.0 ms  (average mu = 0.854, current mu = 0.737) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

This error prevents Homebridge from starting successfully.

To Reproduce

Steps to reproduce the behavior:

1. Install and enable the "homebridge-magichome-dynamic-platform" plugin in Homebridge.
2. Attempt to start Homebridge.
3. Observe the error message mentioned above.

Expected behavior

Homebridge should start successfully with the "homebridge-magichome-dynamic-platform" plugin enabled.

Additional context

Context

I've already set the max-old-space-size option to 256 after the first occurrence of the error.
I've disabled all plugins except for Homebridge UI, and have determined that the issue is related to the "homebridge-magichome-dynamic-platform" plugin.

Host Hardware

Hardware: Raspberry Pi 3B+
OS: Raspbian Buster
Homebridge and MagicHome

Homebridge version: 8.19.3
Homebridge-magichome-dynamic-platform version: 1.9.7
Link to the MagicHome Device on the seller's website: N/A.