Parkside lawn mower PMRDA 20-Li A1

[tkrynicki]

Hi,
any ideas for Parkside lawn mower PMRDA 20-Li A1 support ?
https://www.lidl.de/p/parkside-20-v-smart-maehroboter-pmrda-20-li-a1/p100325200
I found isssue added but already deleted:

[make-all]

The was deleted at the request of the submitter. I assume they would submit a new request without whatever information they were concerned about, but it seems they didn't.

[tkrynicki]

How can I support you to make this device integrated? If it's possible?

[make-all]

Based on the previous information given, it is very similar to the Moebot S that is already supported, and a minor tweak to that config should make it compatible.
Commit bf67175 should be enough to get it working.

[make-all]

Please include the log message from when you attempt to add the device if you still cannot add it using the "main" development version (which you can install through HACS using the Redownload option)

[TadFocus]

Hello, here is it.
"6" is battery sensor in %
"101" is state (STANDBY, MOWING, PARK, ERROR, etc.)
"106" is PIN code
another I don´t know.

`{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.5.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.11",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Prague",
"os_name": "Linux",
"os_version": "6.1.29",
"supervisor": "2023.04.1",
"host_os": "Home Assistant OS 10.2",
"docker_version": "23.0.6",
"chassis": "embedded",
"run_as_root": true
},

"localtuya": {
  "version": "5.2.0",
  "requirements": []
},

"integration_manifest": {
"domain": "localtuya",
"name": "LocalTuya integration",
"codeowners": [
"@rospogrigio",
"@postlund"
],
"config_flow": true,
"dependencies": [],
"documentation": "https://github.com/rospogrigio/localtuya/",
"iot_class": "local_push",
"issue_tracker": "https://github.com/rospogrigio/localtuya/issues",
"requirements": [],
"version": "5.2.0",
"is_built_in": false
},
"data": {
"device_config": {
"friendly_name": "Robotick\u00e1 seka\u010dka na tr\u00e1vu PMRDA 20-Li A1",
"host": "192.168.1.197",
"device_id": "bf7adXXXXXXXXXXXXX5j6pd",
"local_key": ")z7b]-;oUXXXXXXXXX",
"protocol_version": "3.3",
"enable_debug": false,
"model": "Robot lawn mower PMRDA 20-Li A1",
"dps_strings": [
"6 (value: 100)",
"101 (value: STANDBY)",
"102 (value: 0)",
"103 (value: MOWER_LEAN)",
"104 (value: True)",
"105 (value: 3)",
"106 (value: 4444)",
"116 (value: False)"
],
"entities": [
{
"id": 101,
"friendly_name": "PMRDA stav",
"platform": "sensor"
},
{
"id": 6,
"friendly_name": "PMRDA stav baterie",
"device_class": "battery",
"platform": "sensor"
}
],
"product_key": "XXXXXXXXXXXXXXXX"
},
"device_cloud_info": {
"active_time": 1684157417,
"biz_type": 0,
"category": "gcj",
"create_time": 1684156377,
"icon": "smart/icon/ay1559701439060fw6BY/cd5d1eb275462c33b3ea5f52672fe535.png",
"id": "XXXXXXXXXXXXXXXXXXXXXX",
"ip": "XX.XX.XX.XX",
"lat": "57.0300",
"local_key": "XXXXXXXXXXXXXXXX",
"lon": "19.2600",
"model": "",
"name": "Robotick\u00e1 seka\u010dka na tr\u00e1vu PMRDA 20-Li A1",
"online": true,
"owner_id": "XXXXXXXX",
"product_id": "icw5XXXXfcevsve",
"product_name": "Robot lawn mower PMRDA 20-Li A1",
"status": [
{
"code": "battery_percentage",
"value": 100
}
],
"sub": false,
"time_zone": "+02:00",
"uid": "euXXXXXXXXXXXXXrrAwA",
"update_time": 1685876820,
"uuid": "7724dfba1f012984"
}
}
}`

[tkrynicki]

Is possible to decode ex. "112" - Work log: ZH7jNAAABEkBZH4zQwAACHIBZH4KWwAAGEcBZHtxhgAAAJ4BZHs2GQAAKSYBZHsyZAAAADwBZHdxUwAAB0oBZHYggAAAGSEBZHTOyQAALSsBZHS+DgAAB7gB ?
"111" Error log:
ZH7rFxZkfju1FmR+I/kUZH4jzhZke3IkFGR7MpEVZHsyiBhkd3imFWR3eKMCZHd4nhQ=

I see also not supported option: "116" i have value: false

And in smart app Error log can have states ex. Tapperd, lifted, upside down

[tkrynicki]

I'm wonder if error log: ZH7rFxZkfju1FmR+I/kUZH4jzhZke3IkFGR7MpEVZHsyiBhkd3imFWR3eKMCZHd4nhQ=
Is hashed time stamp with error text messages.
It should be 2023/06/05 19:47:01 trapped
If I correctly investigated.

[make-all]

It looks base64 encoded. There are online base64 decoders to test this theory.
But in general, base64 encoded fields can be binary data, so are only decoded when there is a specific use case where they are handled. Using them to encode text is a bit strange, because it just makes the text hard to read and increases the size overhead.

[make-all]

It appears to be valid base64, but decodes to binary, so I think it is not a text log but some sort of binary log (perhaps compressed)

[Peck07]

I know it's an old thread, but maybe helps:
error log
ZH7rFxZkfju1FmR+I/kUZH4jzhZke3IkFGR7MpEVZHsyiBhkd3imFWR3eKMCZHd4nhQ= decodes to:
64 7e eb 17 16
64 7e 3b b5 16
64 7e 23 f9 14
64 7e 23 ce 16
64 7b 72 24 14
64 7b 32 91 15
64 7b 32 88 18
64 77 78 a6 15
64 77 78 a3 02
64 77 78 9e 14
divided to 10 segments, because mower stores apparently the last 10 errors.
647EEB17 in decimal is 1,686,039,319 epoch, which is GMT: 2023. June 6., Tuesday 8:15:19,
16, 14, 18, 02 are probably the error codes.

Similarly, if you base64 decode ZH7jNAAABEkBZH4zQwAACHIBZH4KWwAAGEcBZHtxhgAAAJ4BZHs2GQAAKSYBZHsyZAAAADwBZHdxUwAAB0oBZHYggAAAGSEBZHTOyQAALSsBZHS+DgAAB7gB worklog, you get 10 records, the first:
64 7e e3 34 00 00 04 49 01 - first 4 bytes are again the epoch, 00 00 is probably a filler (or used for longer mow times, didn't do the math), 0449 in decimal is 1097, that's how many seconds it mowed, 01 is probably an indicator for automatic mowing.

[stefangries]

I just tried the main-branch of this integration with my Parkside Mower. Seems to be working quite well, only the status seems wrong:

The correct status is charging, but the main status of the mower is "Fehler" which translates to "Error":

By the way: To let the robot return to the dock, you first have to pause, then stop and then press return to dock. Otherwise it won't work.

[stefangries]

Seems like the current changes break something. The vacuum.* entity is now missing. Readding the device does not help.

This is the error on the console:

[make-all]

Sorry, I did not remove the mapping completely, I left an invalid empty mapping statement in there.

[stefangries]

Seems to be working now, thanks a lot!

[stefangries]

I found another small error. The integration seems not to be able to handle the "RAIN_PARK" state:

To make sure there are no other states the integration cannot handle, here are the states I have experiened so far.
Fot the device state: CHARGING/CHARGING_WITH_TASK_SUSPEND/MOWING/PAUSED/STANDBY/PARK/EMERGENCY/LOCKED/ERROR
For the problem state: MOWER_LEAN/RAIN_PARK/MOWER_UI_LOCKED/MOWER_EMERGENCY

[stefangries]

@make-all Thanks for fixing this 👍

[TadFocus]

You can use mower commands (mowing, pause, park etc?)

[TadFocus]

Note that the support for this device is not yet released, as it required a tweak to the Moebot config. If installing from HACS, you need to select Redownload, select "main" as the version, and wait for that version field to reactivate before pressing the Download button.

This was a problem, thank you

[Biegnik]

Hi, I used this tweak for a month and I was satisfied with results, but after last HS core update (2024.05.3) all mower entities became unavailable. Is there a chance for support?

[make-all]

Did you also update tuya-local?

[Biegnik]

No, I didn't. I followed your instructions from the post above.

[Biegnik]

I downgrade to HS 2024.4.4. and mower entities are available again... What can cause the problem with this update?

[adriaanos]

Does this work in the Smart Life/Tuya app for you? I get an error when I try to add it to the app and the mower factory resets

[stefangries]

For me the Tuya Smart App ist working.

[adriaanos]

I can connect with Bluetooth but cannot activate with WiFi

[cociweb]

Can anybody be so kind to share a snapshot of the config flow, please? I do not have sensors (on the latest version). The same behavior on 3.3 and 3.4 protocol versions.
I have these attributes, but I don't really know what are these and which one goes to which on the config flow.

[make-all]

The config flow for this integration does not look like that, most likely you are using localtuya, which is a different integration.

[cociweb]

The config flow for this integration does not look like that, most likely you are using localtuya, which is a different integration.

Yes, You are right! Thanks for the hints! With your custom component it is perfectly working!

[cociweb]

The config flow for this integration does not look like that, most likely you are using localtuya, which is a different integration.

Yes, You are right! Thanks for the hints! With your custom component it is perfectly working!

um there are some mismatch with the state reporting, and error reposrting, but for control puproses with some hack it can work. - maybe we can open a separate issue thread where we can work it out. Problem Riport is opened:
#1983

[rucanunes]

Could someone please tell me if you are using LocalTuya or the Tuya integration?
How do you add the Lawn Robot? I don't know how to do it because it asks for a blinking light...

Thank you.

[cociweb]

https://github.com/make-all/tuya-local?tab=readme-ov-file#installation

[rucanunes]

Thank you. Didn't know about this one. I was using Local Tuya.
What are the advantages of this integration compared to Local Tuya?

[make-all]

They have a different history, localtuya started with support for simple devices like switches and lights first, and adopted a DIY approach where the end user had to set up their device at dps level themselves. tuya-local forked from a goldair-climate integration, expanding to support other brands of climate devices at first, and keeping the approach that user should not need to know details at the protocol level, so all devices are supported by pre-defined config files. This distinction has become less important, as I think localtuya supports auto-generating all that user config based on the cloud data for the device. Both now support most kinds of entity available in Home Assistant.

Originally both were based on the pytuya library, which has been unmaintained now for years. localtuya chose to fork the library themselves, and maintain a copy inside their source tree. tuya-local chose to switch to tinytuya, which is maintained by a separate team. Because of the workload of maintaining both the HA side and the tuya side of the interface, localtuya can be a bit behind tinytuya when it comes to supporting new Tuya protocol versions, but I think the developers are co-operating so this may be less of a factor now. localtuya's fork of pytuya has been made fully async to fit in with Home Assistant, while tinytuya has remained synchronous, so tuya-local has to use worker threads to fit in with the async expectations of HA, which may make it a little less responsive and heavier.

[rucanunes]

Thank you very much for your detailed reply!! 👍

[cociweb]

I was asking how to add the Parkside Lawn Robot to Tuya so I can add it to HA. But I figured out.

Do you know if we can use both HA and the Parkside app?

you can use HA either with Tuya app or Parkside (lidl home) app too - but not with both. Tuya or lidl are exclusive.

[rucanunes]

If someone finds this post and doesn't know how to to add the Lawn Robot to the Tuya app, just go to "Config -> Activate wifi" on your Parkside Lawn Robot and use the Tuya app to add it.

[jonferreira]

I was literally looking at this now. That Lidl APP SUCKS.

PS: I guess I wasn't the only one buying this robot at 50% discount last week lol

[rucanunes]

Portugal?

This one's not so bad.

[jonferreira]

Yeah :) I was using Lidl Home. Anyway uninstalled that, paired it with the "Smart Live" app I was already using, installed and configured tuya-local and setup it on HA. 15min job and it's done!

Deffo easier than to layout all the perimeter wire and make it so that it find it's dock lol

[Fmoedas91]

hi anyone can help me? i'm stuck in here.

i don't know what is the values that i need to configure to have all control in vacumm mode (play, pause, dock etc). anyone can share this configuration? thanks

[make-all]

This is not the config dialog of this integration.

Please see this discussion instead: https://community.home-assistant.io/t/local-tuya-setup-for-mower/533487