Fix periodic reporting status for lock series

[zerzhang]

• suggest remove the lock periodic reporting status when perfoming an action lock or unlock, which contains error status and sometimes causes the status to be overwritten immediately
• Normally, when we perform a locking or unlocking action, we will actively query the lock status once. At this time, the locking or unlocking action may not have been completed. Then, when the BLE scan detects a change in the device broadcast, we will also actively update the status once. Through these two methods, we can ensure that the final state of the lock is correct.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
switchbot/devices/lock.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bdraco]

How does this work if the user only has passive scans on?

[zerzhang]

If the user only has passive scanning, the user should not be able to add this device.

[bdraco]

Historically users turn on active scanning to add the device and than turn it back off once it's discovered. When active scans are on the connection times are much much longer

[zerzhang]

If this is the case, there should be no problem. When the device is added, self.model is already determined. In subsequent scans, we only use the manufacturer_data in the advertisement. We don't need to know the service_data because we already know the type when the device is added.

    @callback
    def _async_handle_bluetooth_event(
        self,
        service_info: bluetooth.BluetoothServiceInfoBleak,
        change: bluetooth.BluetoothChange,
    ) -> None:
        """Handle a Bluetooth event."""
        self.ble_device = service_info.device
        if not (
            adv := switchbot.parse_advertisement_data(
                service_info.device, service_info.advertisement, self.model
            )
        ):
            return
        if "modelName" in adv.data:
            self._ready_event.set()
        _LOGGER.debug(
            "%s: Switchbot data: %s", self.ble_device.address, self.device.data
        )
        if not self.device.advertisement_changed(adv) and not self._was_unavailable:
            return

[zerzhang]

@bdraco I have discussed this with our internal team and was told that different devices have different instructions for periodically reporting device status, so I made the following changes.

• Correct COMMAND_ENABLE_NOTIFICATIONS command for differenct lock device
• Each time an action is executed, the device status is reported periodically until Bluetooth is disconnected

[zerzhang]

@bdraco Could you help to review this?

[bdraco]

Thanks for your patience! I'm currently awaiting battery delivery for proper testing of the lock functionality. Due to shipping restrictions on lithium-ion batteries to my location, delivery has been delayed, but tracking indicates arrival within 1-2 days.

Once received, I'll thoroughly test the periodic reporting changes with actual hardware and merge if everything works as expected.

I'll update this PR as soon as testing is complete.

[zerzhang]

ok

[bdraco]

Batteries arrived, tested, everything seems ok with this change