"Unknown data protocol" messages being logged periodically

[rccoleman]

I've been seeing logs like this in my HA log on a semi-regular basis lately:

2025-02-05 13:03:50.939 WARNING (Thread-5 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-05 13:03:50.939 INFO (Thread-5 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] RoborockMessage(protocol=102, payload=b'{"t":1738789428,"dps":{"128":0}}', seq=8792, version=b'1.0', random=18692, timestamp=1738789428, message_retry=None)
2025-02-05 13:03:54.008 WARNING (Thread-5 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-05 13:03:54.008 INFO (Thread-5 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] RoborockMessage(protocol=102, payload=b'{"t":1738789431,"dps":{"128":0}}', seq=8798, version=b'1.0', random=18703, timestamp=1738789431, message_retry=None)
2025-02-05 13:04:24.542 WARNING (Thread-5 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-05 13:04:24.542 INFO (Thread-5 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] RoborockMessage(protocol=102, payload=b'{"t":1738789462,"dps":{"128":0}}', seq=8805, version=b'1.0', random=18715, timestamp=1738789462, message_retry=None)
2025-02-05 13:31:05.872 WARNING (Thread-4 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Living Room] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-05 13:31:05.872 INFO (Thread-4 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Living Room] RoborockMessage(protocol=102, payload=b'{"t":1738791064,"dps":{"128":1}}', seq=8714, version=b'1.0', random=18516, timestamp=1738791064, message_retry=None)
2025-02-05 13:34:58.164 WARNING (Thread-4 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Living Room] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-05 13:34:58.164 INFO (Thread-4 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Living Room] RoborockMessage(protocol=102, payload=b'{"t":1738791296,"dps":{"128":0}}', seq=8780, version=b'1.0', random=18646, timestamp=1738791296, message_retry=None)

Sometimes it reports a different number:

2025-02-05 16:34:56.585 WARNING (Thread-4 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Living Room] Unknown data protocol 134, please create an issue on the python-roborock repository
2025-02-05 16:34:56.585 INFO (Thread-4 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Living Room] RoborockMessage(protocol=102, payload=b'{"t":1738802094,"dps":{"134":0}}', seq=11496, version=b'1.0', random=24416, timestamp=1738802094, message_retry=None)

I don't think it's causing any functional issues, but I wanted to report it.

I have three QRevo Master robots and it looks like they all cause these warnings every so often.

[Thorn-hill]

+1, getting
[Roborock S7 MaxV] Unknown data protocol 128, please create an issue on the python-roborock repository

[Lash-L]

Hi yes - it is not a functional problem, but it will help us better support the device. I need the response of the get_home_data call -parituclarily the schema section of it. (can be seen with debug logging on)

[northern-pit]

I have same issue with my new QREVO CURV
Core 2025.2.1

Logger: roborock.version_1_apis.roborock_mqtt_client_v1
Source: /usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py:434
First occurred: 9 February 2025 at 21:08:10 (16 occurrences)
Last logged: 9 February 2025 at 22:30:39

[Robert] Unknown data protocol 128, please create an issue on the python-roborock repository
[Robert] Unknown data protocol 134, please create an issue on the python-roborock repository

I need the response of the get_home_data call

I would glad to post it, someone will share where or how to get this response.

[rccoleman]

I grabbed this by using the example on the home page for this package and pulling out the "schema" bit from home_data:

schema=[HomeDataProductSchema(id=101, name='rpc_request', code='rpc_request', mode='rw', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=102, name='rpc_response', code='rpc_response', mode='rw', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=120, name='错误代码', code='error_code', mode='ro', type='ENUM', product_property=None, property='{"range": [""]}', desc=None), HomeDataProductSchema(id=121, name='设备状态', code='state', mode='ro', type='ENUM', product_property=None, property='{"range": [""]}', desc=None), HomeDataProductSchema(id=122, name='设备电量', code='battery', mode='ro', type='ENUM', product_property=None, property='{"range": [""]}', desc=None), HomeDataProductSchema(id=123, name='清扫模式', code='fan_power', mode='rw', type='ENUM', product_property=None, property='{"range": [""]}', desc=None), HomeDataProductSchema(id=124, name='拖地模式', code='water_box_mode', mode='rw', type='ENUM', product_property=None, property='{"range": [""]}', desc=None), HomeDataProductSchema(id=125, name='主刷寿命', code='main_brush_life', mode='rw', type='VALUE', product_property=None, property='{"max": 100, "min": 0, "step": 1, "unit": "null", "scale": 1}', desc=None), HomeDataProductSchema(id=126, name='边刷寿命', code='side_brush_life', mode='rw', type='VALUE', product_property=None, property='{"max": 100, "min": 0, "step": 1, "unit": "null", "scale": 1}', desc=None), HomeDataProductSchema(id=127, name='滤网寿命', code='filter_life', mode='rw', type='VALUE', product_property=None, property='{"max": 100, "min": 0, "step": 1, "unit": "null", "scale": 1}', desc=None), HomeDataProductSchema(id=128, name='额外状态', code='additional_props', mode='ro', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=130, name='完成事件', code='task_complete', mode='ro', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=131, name='电量不足任务取消', code='task_cancel_low_power', mode='ro', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=132, name='运动中任务取消', code='task_cancel_in_motion', mode='ro', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=133, name='充电状态', code='charge_status', mode='ro', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=134, name='烘干状态', code='drying_status', mode='ro', type='RAW', product_property=None, property=None, desc=None), HomeDataProductSchema(id=135, name='离线原因细分', code='offline_status', mode='ro', type='RAW', product_property=None, property=None, desc=None)]

128 appears to be extra status and 134 is Drying State

[Lash-L]

Hey @rccoleman - Any idea what 128 seems to be representing? It changed to 1 once in your original post, but it is difficult to tell what that actually means without having a device myself or knowing more context.

[rccoleman]

I'll see if I can correlate it to something with the robot.

Well, I just got three of them, but all are 0. The robot had finished vacuuming, docked itself, and emptied the bin. The first two came when it docked and started emptying and the third when it finished emptying.

2025-02-10 19:38:52.553 WARNING (Thread-7 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-10 19:38:52.554 INFO (Thread-7 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] RoborockMessage(protocol=102, payload=b'{"t":1739245129,"dps":{"128":0}}', seq=14889, version=b'1.0', random=31591, timestamp=1739245129, message_retry=None)
2025-02-10 19:38:55.695 WARNING (Thread-7 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-10 19:38:55.696 INFO (Thread-7 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] RoborockMessage(protocol=102, payload=b'{"t":1739245132,"dps":{"128":0}}', seq=14891, version=b'1.0', random=31593, timestamp=1739245132, message_retry=None)
2025-02-10 19:39:27.070 WARNING (Thread-7 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-10 19:39:27.070 INFO (Thread-7 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [Second Floor] RoborockMessage(protocol=102, payload=b'{"t":1739245163,"dps":{"128":0}}', seq=14903, version=b'1.0', random=31614, timestamp=1739245163, message_retry=None)

My guess is that '1' is related to mopping somehow, but I'll need to experiment.

Exciting, I got a "4":

2025-02-11 04:49:14.697 WARNING (Thread-3 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [First Floor] Unknown data protocol 128, please create an issue on the python-roborock repository
2025-02-11 04:49:14.697 INFO (Thread-3 (_thread_main)) [roborock.version_1_apis.roborock_mqtt_client_v1] [First Floor] RoborockMessage(protocol=102, payload=b'{"t":1739278154,"dps":{"128":4}}', seq=781, version=b'1.0', random=1649, timestamp=1739278154, message_retry=None)

But mostly 0s, and I have no idea what caused that 4. And no idea why it repeats the same "0" entries over and over.

[mm98]

I can confirm. Same warning here:

Logger: roborock.version_1_apis.roborock_mqtt_client_v1
Source: /usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py:434
First occurred: 09:20:00 (22 occurrences)
Last logged: 14:07:03

[Roborock S8 Pro Ultra] Unknown data protocol 128, please create an issue on the python-roborock repository
[Roborock S8 Pro Ultra] Unknown data protocol 134, please create an issue on the python-roborock repository

[elcajon]

I did some tests related to these unknown protocols with my Roborock S8 Pro Ultra today.

• 134

  • 1 = drying state on
  • 0 = drying state off

• 128

  • 0 = idle at station (while charging / mop cleaning)
  • 2 = idle away from station
  • 4 = start charging or mop cleaning
  • 6 = paused while away from station

home-assistant_roborock_2025-03-04T14-20-37.514Z.log

[Lash-L]

We have done a complete refactor of most of our codebase since this issue first existed. Protocol updates are being added back in via #731 and the original issue here will no longer be a problem.