Closed cicero200272 closed 2 months ago
same here. Got: ` Logger: pyNukiBT.nuki Source: runner.py:188 First occurred: 13:36:44 (25 occurrences) Last logged: 13:38:32
parse error Error in path (parsing) -> crc wrong checksum, read 36355, computed 18825 Got unexpected message length for command 49960. got length:132 expecting length:8 Got 124 unknown bytes with value: b'x\xc0\x81\xbe_\x83\x862\x95C\xd1\xcd\x88\xa5\x93\x94\x0c\x92\xff\x1b\x01\x00f\x00h f\x02\x99\x13\xd6wz\x15~\xbb\x92\x99\xf0\x94W\x00\x9fx5\xed\xab \xb4\xb9\xf4\x10\xa6\x05\\xc9\xcb\xc2[TO%\xe6\xd1\x95\xce\xd8\x07\x83"\x1d\xa5\xb9\x85h]\xc6\xef\xf2B\xfc\x81\xcf\xa7\'\xe1j\x99\xe4"\x10D#\xf5+\x04=\xc8[\xca<\x9efR]\xc8{\xc3\xad!D<\xae\xb7<\x0edzW\x18f[\x8c\x0f' HomeAssistant: Received unsolicited notification: Container: auth_id = b'\x15Ga7' (total 4) command = (enum) (unknown) 49960 payload = None crc = 49272 was expecting CONFIG `
Same Problem with nuki 2.0
0026bb765291 (Handle: 50): Unknown', '00000023-0000-1000-8000-0026bb765291 (Handle: 178): Unknown', '00000068-0000-1000-8000-0026bb765291 (Handle: 160): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 158): Unknown', '00000079-0000-1000-8000-0026bb765291 (Handle: 172): Unknown', '0000008f-0000-1000-8000-0026bb765291 (Handle: 166): Unknown', 'a92ee101-5501-11e4-916c-0800200c9a66 (Handle: 138): Unknown', '0000001d-0000-1000-8000-0026bb765291 (Handle: 101): Unknown', '00000023-0000-1000-8000-0026bb765291 (Handle: 119): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 93): Unknown', '0000001e-0000-1000-8000-0026bb765291 (Handle: 110): MCAP Control Channel', '000000a5-0000-1000-8000-0026bb765291 (Handle: 95): Unknown', '00000019-0000-1000-8000-0026bb765291 (Handle: 127): AVDTP', '00000037-0000-1000-8000-0026bb765291 (Handle: 132): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 125): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 70): Unknown', '00000050-0000-1000-8000-0026bb765291 (Handle: 87): Unknown', '0000004e-0000-1000-8000-0026bb765291 (Handle: 77): Unknown', '0000004f-0000-1000-8000-0026bb765291 (Handle: 82): Unknown', '0000004c-0000-1000-8000-0026bb765291 (Handle: 72): Unknown', 'a92ee203-5501-11e4-916c-0800200c9a66 (Handle: 148): Unknown', 'a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 145): Unknown', 'a92ee201-5501-11e4-916c-0800200c9a66 (Handle: 142): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 9): Unknown', '000000a5-0000-1000-8000-0026bb765291 (Handle: 16): Unknown', '00000037-0000-1000-8000-0026bb765291 (Handle: 11): Unknown', '00002a26-0000-1000-8000-00805f9b34fb (Handle: 155): Firmware Revision String', '00002a27-0000-1000-8000-00805f9b34fb (Handle: 153): Hardware Revision String', '00002a25-0000-1000-8000-00805f9b34fb (Handle: 151): Serial Number String'] 2024-02-25 22:32:14.493 INFO (MainThread) [pyNukiBT.nuki] Connected 2024-02-25 22:32:14.493 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki 2024-02-25 22:32:14.523 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1 2024-02-25 22:32:14.525 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 145): Unknown, data: bytearray(b'\x10\xd3%\xf3J\xa2\xf2\xd1,\xa4\xbf4h\xd7\x9e\x84\xfe_P\x98\xcfs\x0c\x1b\xe6\\4\x008\x00=\xa7X\xd5-;u\xcc\xe8\xfa%\xc0\xf0\x0c\\:\xd3*\x1e\rm\x90\x8d\r\xdd\xf2\xab\xb7\x93\xcd\x03K!\xad0f\x8c\xc5\xd6L\xa8\x8b\x16\x0bz\xee\x17d\x9c\x0c\x1d^\x8d
Kd')
2024-02-25 22:32:14.527 INFO (MainThread) [pyNukiBT.nuki] sending encrypted command REQUEST_LOG_ENTRIES
2024-02-25 22:32:14.528 INFO (MainThread) [pyNukiBT.nuki] Trying to send data. Attempt 1
2024-02-25 22:32:14.528 INFO (MainThread) [pyNukiBT.nuki] Connected
2024-02-25 22:32:14.528 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki
2024-02-25 22:32:14.552 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1
2024-02-25 22:32:14.555 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 145): Unknown, data: bytearray(b'\xef!J\x92W\x0c@\xca%\x95=\x1b\x94\xec\xec\xbeYyyj~\x8f\xcb\xa9\xe6\4\x00M\x00f\x05"\xbb\xdf\x85\xe9\xb0\xd1\xd2it\x19\x8f\x87\x82\x1b\xca\xc6\x8d\xd1\xb7\x11,~\xfe\xcb\x97\xd8K\xed\xe1\xa0\xc2\x07i\x01\xd6\xe8=\xef\x13a\xfb+rTp\x01\x7fTXs\xf2\x88\x9f\xd0\xb9k\x93\xd7\r8\xa4\xe0\xd0b\xe1\xf5\x0c\xa4\xcd\x8aR\xb8')
2024-02-25 22:32:14.583 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 145): Unknown, data: bytearray(b'dz\xfdA$d\xa8\x83(\x1e\xfb\x06CZ\xa9\xe4\xfd\x1d\x92\x1f-\x16_D\xe6\4\x00\x19\x00WQ)x\xb7\x95\x99]\xf2\xa8\xa2g\x81\xcb\x8d\x17\x18K\xb8KF\xcc\x92^\x17')
2024-02-25 22:32:14.584 DEBUG (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-02-25 22:32:14.584 DEBUG (MainThread) [pyNukiBT.nuki] Container:
status = (enum) COMPLETED 0
2024-02-25 22:32:14.584 DEBUG (MainThread) [pyNukiBT.nuki] [Container(index=47, timestamp=Container(year=2024, month=2, day=25, hour=20, minute=27, second=54), auth_id=4294967295, name=u'', type=uEnumIntegerString.new(2, 'LOCK_ACTION'), data=Container(lock_action=uEnumIntegerString.new(2, 'LOCK'), trigger=uEnumIntegerString.new(2, 'BUTTON'), flags=0, completion_status=uEnumIntegerString.new(0, 'SUCCESS'), padding=None))]`
@cicero200272 could it be that the new nuki4 has a different communication protocol? I see that the pairing was successful and that we got the lock status correctly, but for some reason we got an unexpected message when we asked the lock for config.
i don't have a nuki4, so i don't really have a way to debug this myself so i may need your help. is there any log after what you sent me? basically if we get an unexpected message we ignore it and continue to wait for the correct one. so you should either get the config info and continue or get a timeout error if the config message is not received
@Marcus27-03 from your logs i don't see any issue with the nuki2
Last action: COMPLETED and completion_status=uEnumIntegerString.new(0, 'SUCCESS')
so from the logs it seems everything is ok
@cicero200272 @fjfricke @Marcus27-03 please try the latest version (0.0.12). i've fixed some issues related to nuki 4
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4391 Installed Version | 1.34.0 Stage | running Available Repositories | 1398 Downloaded Repositories | 34Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 21. September 2024 um 02:00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | false remote_server | eu-central-1-7.ui.nabu.casa certificate_status | ready instance_id | 35c5ebd370f5454f90f48a8a563ac01f can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okDashboards
dashboards | 4 -- | -- resources | 19 views | 8 mode | yamlRecorder
oldest_recorder_run | 14. Februar 2024 um 09:58 -- | -- current_recorder_run | 20. Februar 2024 um 16:45 estimated_db_size | 233.30 MiB database_engine | mysql database_version | 10.6.11Spotify
api_endpoint_reachable | ok -- | --Checklist
Describe the issue
My Nuki lock (4th generation) non-pro cannot be initialized. It is automatically discovered and paired, but then the initialization process runs of the integration over and over again.
HA runs in a docker container on my Raspberry Pi 4, for bluetooth I use an ESP32 BT proxy.
Seems closely related to https://github.com/ronengr/hass_nuki_bt/issues/34#issuecomment-1872500072 and https://github.com/ronengr/hass_nuki_bt/issues/35
Reproduction steps
Debug logs
Diagnostics dump
No response