renash2me
commented
10 months ago same problem here mate, but im using a different vacuum
Open Bonfra04 opened 10 months ago
renash2me
commented
10 months ago same problem here mate, but im using a different vacuum
Bonfra04
commented
10 months ago @renash2me I managed to work around the problem by editing the entity JSON in the .storage directory: There the config of the vacuum is hardcoded programmatically and should not be modified by hand. If you manage to corrupt this file your home assistant configuration would be reset. That being said in the JSON file there is a part regarding the localtuya vacuum entity. There you can add DPs to the list (following the general format of the already present ones) and then pick this new DP for the UI.
File is at: /config/.storage/core.config_entities
this is an example:
{
"entry_id": "REDACTED",
"version": 2,
"domain": "localtuya",
"title": "localtuya",
"data": {
"region": "eu",
"username": "localtuya",
"no_cloud": true,
"client_id": "",
"client_secret": "",
"user_id": "",
"devices": {
"REDACTED": {
"friendly_name": "Spazzino",
"host": "REDACTED",
"local_key": "REDACTED",
"protocol_version": "3.3",
"enable_debug": true,
"entities": [
{
"friendly_name": "Spazzino",
"idle_status_value": "idle",
"powergo_dp": 2,
"docked_status_value": "chargring,fullcharge",
"returning_status_value": "tocharge",
"battery_dp": 106,
"mode_dp": 104,
"modes": "smart,pose,zone,backcharge,curpointing,selectroom",
"return_mode": "backcharge",
"fan_speed_dp": 109,
"fan_speeds": "quiet,auto,strong,max",
"fault_dp": 122,
"paused_state": "pause",
"stop_status": "pause",
"id": 105,
"platform": "vacuum"
}
],
"add_entities": false,
"device_id": "REDACTED",
"dps_strings": [
"2 (power_go)",
"3 (mode)",
"101 (value: False)",
"102 (value: False)",
"103 (value: True)",
"104 (clean_mode)",
"105 (robot_state)",
"106 (battery)",
"107 (value: 0)",
"108 (value: 0)",
"109 (fan_mode)",
"113 (value: False)",
"116 (value: 22549)",
"117 (value: 436)",
"118 (value: 18)",
"119 (value: 22549)",
"120 (value: 22549)",
"121 (value: 22549)",
"122 (robot_fault)",
"137 (value: True)",
"144 (value: False)"
],
"product_key": "REDACTED"
}
},
"updated_at": "1700991489139"
},
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"unique_id": "",
"disabled_by": null
}As you can see the list of DPs is not standard as I added some. Then I can use the numerical value in the dropdowns in the UI. Beware that the ID DP that you choose at the start and cannot later change shall not be altered here as it will render the device unusable.
As for how I found which DP did what it was just a trial and error trying to guess which current value read from the IoT platform could better satisfy the name in the JSON file (which IMHO is more descriptive than the UI names).
I'm not closing this Issue since anyway even if its all correct somehow the status of the device is only available if HAOS and the vacuum are connected to the internet. If any of the two is offline the status is always set to unknown. Which doesn't make sense since all the other commands work fine
renash2me
commented
10 months ago Thanks!!
guilhermelirio
commented
6 months ago Same problem here, with a Vacum Kabum Smart 900.
Any solution?
Kipjr
commented
3 months ago Same issue for for the Blaupunkt Bluebot XBOOST , status either in Error or in Cleaning
"model": "BLUEBOT XBOOST",
"device_id": "redacted",
"dps_strings": [
"1 (value: False)",
"11 (value: 0)",
"14 (value: 33)",
"25 (value: True)",
"26 (value: turn_left)",
"27 (value: standby)",
"28 (value: sleep)",
"30 (value: high)",
"31 (value: False)",
"32 (value: 23)",
"33 (value: 19)",
"34 (value: 01902300299)"
]
The problem
While trying to configure my Rowenta X-Plorer S75 I need to compile the various DPs into the provided fields. Fetching from the Tuya IoT Platform I can see that the DP for Power is "1"
But in the dropdown selector in the HA UI this dp is not visible
Also, the "Mode" DP is not shown and, I think, this is the reason why the Dashboard shows the device to be always "Cleaning"
In general, some features are just not available since there is no DP to put in the field that requires it. I don't know if fixing this will also fix all of the other bugs I have such as wrong states displayed and wrong commands sent, but I hope so.
Environment
Steps to reproduce
DP dump
Additional information
Here is the full json of the Query Properties from the IoT Platform