Broadlink RM4 Mini - Temperature sensor causes the plugin to stop working

[MrAsterisco]

Describe the bug
I have 3 Broadlink RM4 Mini and I'm using this plugin to control three A/Cs (using the air-conditioner accessory type). Every once in a while (it ranges from anything from twice a day to once a week), the plugin stops working and I need to restart Homebridge.

When this happens, the following is logged to the Homebridge console and attempting to interact with the accessories via the Home app fails:

[homebridge-broadlink-rm-pro] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

or, in other cases:

[homebridge-broadlink-rm-pro] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

To Reproduce
Steps to reproduce the behavior:

1. Configure the plugin with a few Broadlink RM4 Mini.
2. Use the default settings, including reading the temperature from the device.
3. Wait.

Expected behavior
The plugin continues to work for longer periods of time.

Desktop (please complete the following information):

• OS: macOS
• Browser: Arc (Chromium-based)
• Version: Version 1.69.0 (55816), Chromium Engine Version 131.0.6778.70

Smartphone (please complete the following information):

• Device: iPhone 16 Pro Max
• OS: iOS 18.1
• Browser: Safari
• Version: 18.1

Additional context
I tried to turn off reading from the temperature sensor and this does help in solving the situation, however it's not ideal. It also doesn't always solve the problem, as I still need to manually restart Homebridge once every month or so. I believe this is caused by the fact that it's not always the same characteristics that fails to respond.

I'm wondering if the plugin isn't hiding another problem behind the scenes: it seems it fails to connect to the Broadlinks and instead of retrying, it just crashes the entire Homebridge instance. Perhaps, it would be worth failing silently and try again a few times before crashing? I'd be happy to contribute to the codebase with some guidance.

[ChristianPorsche]

Same problem, tried everything...nothing works