Hub connection
**Describe the bug**
I can't get Bluetooth device readings directly from the gateway itself. I've configured the device ID of the BT devices to match the original ones, I'm using the gateway's IP and token and I've specified the BT device's own model.

**Expected behavior**
I'd really like for direct fetch of readings to work.

**Debug log**
Similar errors happen with both `lumi.sensor_smoke.mcn02` and `cgllc.clock.dove`. The token and IP seem to work for the gateway connection itself.

I've enabled detailed debug log for the `cgllc.clock.dove` and "user ack timeout" seems to be the bane of all BT devices.
```
[4/3/2024, 2:40:25 AM] [homebridge-miot] [Mi Alarm Clock] (Protocol) Start handshake x.y.z.q
[4/3/2024, 2:40:25 AM] [homebridge-miot] [Mi Alarm Clock] (Protocol)  x.y.z.q <- (0) {"method":"get_properties","params":[{"did":"blt.4.xxxxxxxxxxx","siid":2,"piid":1},{"did":"blt.4.xxxxxxxxxxx","siid":2,"piid":2}],"id":3622}
[4/3/2024, 2:40:25 AM] [homebridge-miot] [Mi Alarm Clock] (Protocol)  x.y.z.q<- !1�Z✂️s\f�
[4/3/2024, 2:40:25 AM] [homebridge-miot] [Mi Alarm Clock] (Protocol)  x.y.z.q -> Data: {"id":3522,"error":{"code":-9999,"message":"user ack timeout"},"exe_time":4000}
[4/3/2024, 2:40:25 AM] [homebridge-miot] [Mi Alarm Clock] (Protocol)  x.y.z.q -> Message: {"id":3522,"error":{"code":-9999,"message":"user ack timeout"},"exe_time":4000}
```

**Additional context**
I've tried adding the hub (`lumi.gateway.mgl03`) to both DE and CN location alongside the Bluetooth devices, but all I end up with are still ACK errors if the hub is used. Forced connection through Mi Cloud does work, but that has been too unreliable (I'd really like to get rid of those pesky zero readings) so I'd really like to use a local direct connection.
