We should not send api calls for doorSensor if there is none configured

[samuellazea]

Hello,

Based on last PR's and latest release I notice in the logs that there are api calls done for door sensors while I only have locks configured.
Would be good if we can check if there are any door sensors configured before running the calls in order to minimize the call numbers

`2025-01-15 19:51:19.729 DEBUG (MainThread) [custom_components.ttlock.api] [cc6a] Sending request to https://euapi.ttlock.com/v3/doorSensor/query with args={'lockId': 12345678}

2025-01-15 19:51:19.732 INFO (SyncWorker_4) [homeconnect.sseclient] Connecting ...

2025-01-15 19:51:19.765 DEBUG (MainThread) [custom_components.ttlock.api] [cc6a] Received response: status=200: body={'errcode': 1, 'errmsg': 'failed or means no', 'description': '表示失败或否'}

2025-01-15 19:51:19.765 DEBUG (MainThread) [custom_components.ttlock.api] [cc6a] API returned: {'errcode': 1, 'errmsg': 'failed or means no', 'description': '表示失败或否'}
`

[github-actions]

@samuellazea: hello! 👋

This issue is being automatically closed because it does not follow the issue template.

[jbergler]

Thanks @github-actions for that excellent contribution...

I agree in theory, I think the problem is the lockDetails endpoint doesn't actually tell you if a sensor is attached or not.
The featureValue seems to set the sensor bit whenever the lock supports a sensor, regardless of its presence.

I didn't have a ton of time to dig into that, so if you have ideas on how to make better decisions before firing the next api call off I'm all ears!