TTLock has stopped reporting lock status

[Nick-Sills]

Describe the bug

My Simpled Smart Lock has stopped reporting any lock statuses. It can be unlocked from Home Assistant, but no-longer reports locked or last operator. Similarly, no lock actions are reported if the lock is manually used.

This was working fine until a couple of days ago.

Thanks!

To Reproduce

See above

Expected behavior

Lock reports locked/unlocked and last operator statuses

Required information

Please provide:

• Debug logs reproducing the issue. For most issues, it is required to enable debug logging, and reload the extension so we capture the required information.
• The diagnostic info for ttlock.

I'm not sure if this log snippet is relevant to the problem or not.

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 15 January 2025 at 21:26:40 (2 occurrences)
Last logged: 15 January 2025 at 21:27:04

[139964157915728] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
hass, entity, func, data, call.context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/lock/init.py", line 226, in async_handle_lock_service
await self.async_lock(**self.add_default_code(kwargs))
File "/config/custom_components/ttlock/lock.py", line 44, in async_lock
await self.coordinator.lock()
File "/config/custom_components/ttlock/coordinator.py", line 247, in lock
res = await self.api.lock(self.lock_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ttlock/api.py", line 173, in lock
res = await self.get("lock/lock", lockId=lock_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ttlock/api.py", line 126, in get
return await self._parse_resp(resp, log_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ttlock/api.py", line 111, in _parse_resp
raise RequestFailed(f"API returned: {res}")
custom_components.ttlock.api.RequestFailed: API returned: {'errcode': 1, 'errmsg': 'failed or means no', 'description': '表示失败或否'}

[jbergler]

This feels like a duplicate of #182 - could you check if you're receiving webhook events for your lock?

[jbergler]

In terms of the error you posted, that's a failure from the API - which indicates something else is up but unfortunately we don't have any insight into what's going on there.

If you use the ttlock mobile app with bluetooth disabled, does it work?

[Nick-Sills]

@jbergler Thanks for the very quick response. It's appreciated.

Sincere apologies, it appears that my call-back url is failing so this issue is totally at my end. I'll close the issue.