Update #3:
For some reason, after deleting MQTT & TTLOCK integrations, my lock was successfully integrated with HA, but no entities are showing and no control of locking/unlocking as prr image below:
Update #4
[bfd…8aq] Failed to connect to 192.168.86.33: [Errno 111] Connect call failed (‘192.168.86.33’, 6668)
12:54:40 PM – (WARNING) LocalTuya (custom integration) - message first occurred at 6:32:44 AM and shows up 370 times
[bfd…rjv] Disconnected - waiting for discovery broadcast
12:54:37 PM – (WARNING) LocalTuya (custom integration) - message first occurred at 6:32:44 AM and shows up 383 times
[bfd…rjv] Initial state update failed, giving up: DecodeError(‘could not decrypt data: wrong local_key? (exception %s)’, JSONDecodeError(‘Expecting value: line 1 column 1 (char 0)’))
12:54:37 PM – (ERROR) LocalTuya (custom integration) - message first occurred at 6:32:44 AM and shows up 383 times
Ping fails, no response from peer
7:35:53 AM – (ERROR) runner.py
Fetched https://alexa-api.nabucasa.com/access_token (400)
7:35:10 AM – (WARNING) components/cloud/alexa_config.py - message first occurred at 6:32:30 AM and shows up 2 times
Setup timed out for stage 2 - moving forward
6:37:36 AM – (WARNING) bootstrap.py
Error setting up entry Lock 3C8797 for tuya_ble
6:37:36 AM – (ERROR) Tuya BLE (custom integration)
Waiting on integrations to complete setup: tuya_ble
6:37:28 AM – (WARNING) bootstrap.py - message first occurred at 6:33:28 AM and shows up 5 times
DC:23:4D:3C:87:97: Device unexpectedly disconnected; RSSI: None
6:37:17 AM – (WARNING) Tuya BLE (custom integration) - message first occurred at 6:33:07 AM and shows up 4 times
DC:23:4D:3C:87:97: timeout receiving response, RSSI: None
6:34:16 AM – (ERROR) Tuya BLE (custom integration) - message first occurred at 6:34:16 AM and shows up 2 times
Zigbee channel 15 utilization is 98.22%!
6:32:51 AM – (WARNING) components/zha/core/gateway.py - message first occurred at 6:32:51 AM and shows up 2 times
Config entry ‘Mono5 0x18409d6e’ for yeelight integration not ready yet: Failed to read from the socket at 192.168.86.250:55443: [Errno 113] Connect call failed (‘192.168.86.250’, 55443).; Retrying in background
6:32:45 AM – (WARNING) config_entries.py - message first occurred at 6:32:44 AM and shows up 2 times