Hi ! just merged your PR and push a new version for HACS 
Thank you for your fast resolution about that problem 
Hi
2 things
I have map management section only option to reset map, no rooms to define by design. So my robot only draws one big “room” and has options to add restricted rects and define one zone rect to clean.
Currently the weback app bug still does not show map in app but the request to the *_map_list_get
gives:
{
"msg": "ServiceErrorException",
"code": 0,
"data": {}
}
The user_thing_list_get is success and gives back data
Hi there
Using the Tesvor x500 here. I updated and it works again without problems. However not with Maps. I took a look into the app and do not see the option for saved maps. I guess, since the robot is too old, it always spontaneously creates the map and never saves it anywhere.
If you have any recommendations how to fix this, I am happy to try it out. 
1 Like
Version 1.1.2 works now, sort of, map still not available, but all initializes
Might still be the weback app bug not showing the map in app, if they manage to fix this, I will provide an update.
Oh and API currently gives for reuse_map_list_get, I guess no data is available for map_data:
{
"msg": "success",
"code": 1,
"data": {
"realtime_map_id": "0",
"map_list": []
}
}
In my app they seemed to have fixed the map issue - showing maps again after cleaning. As I do not have any saved maps in my app, I wanted to ask you how it looks at your place?
Actually, the map issue is till not fixed (at least in my case) . They managed to render last known map to app as static data, so zones could be applied (API showed newly added restricted data after adding zone to rendered map). It is not updating the map and vacuum pos. API still cannot get map data for me. Some promice was to be fixed in the middle of nex month. We will wait and see.
With the latest version, I frequently get the following error:
[custom_components.weback_vacuum.WebackApi] WebackApi (WSS) Error during on_message (map_data) (details='MapData')
It seems to come up every 5 seconds. Supposedly because I do not have maps available. @Jezza34000 any idea what is wrong in the code?
I get a similar error:
2023-03-24 01:19:25.163 ERROR (Thread-2565 (run_forever)) [websocket] error from callback <bound method WebackWssCtrl.on_message of <custom_components.homeassistant_weback_component-main.VacDevice.VacDevice object at 0x7f9def59f0>>: ‘working_status’
Ideas?
Hello,
Yes
Is it possible to put integration into debug mode and send more log before and after error ?
Thank you
1 Like
How do I do it?
in configuration.yaml, add this:
logger:
default: error
logs:
custom_components.weback_vacuum: debug
and then restart HomeAssistant.
Logs are found in System - > Settings - > Logs and hit “LOAD FULL LOGS”
1 Like
Invalid config for [logger]: [customize] is an invalid option for [logger]. Check: logger->logger->customize. (See /config/configuration.yaml, line 10).
I have the same code in my configuration.yaml and it works fine, are you sure you don’t have a typo and the correct amounts of space?
Check your YAML indentation
I finally got around to this, sorry guys, busy week…
Here’s what I see:
Logger: homeassistant.components.vacuum
Source: custom_components/homeassistant_weback_component-main/VacDevice.py:105
Integration: Aspiradora (documentation, issues)
First occurred: March 30, 2023, 00:45:42 (2 occurrences)
Last logged: March 30, 2023, 00:45:54
- Error adding entities for domain vacuum with platform weback_vacuum
- Error while setting up weback_vacuum platform for vacuum
Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 442, in async_add_entities await asyncio.gather(*tasks) File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 629, in _async_add_entity capabilities=entity.capability_attributes, File “/usr/src/homeassistant/homeassistant/components/vacuum/init.py”, line 214, in capability_attributes return {ATTR_FAN_SPEED_LIST: self.fan_speed_list} File “/config/custom_components/homeassistant_weback_component-main/vacuum.py”, line 171, in fan_speed_list if self.device.vacuum_or_mop == 1: File “/config/custom_components/homeassistant_weback_component-main/VacDevice.py”, line 105, in vacuum_or_mop if self.robot_status[‘fan_status’] == self.FAN_DISABLED and self.robot_status[‘water_level’] != self.MOP_DISABLED: KeyError: ‘fan_status’
Logger: homeassistant.helpers.integration_platform
Source: loader.py:796
First occurred: March 30, 2023, 00:45:39 (9 occurrences)
Last logged: March 30, 2023, 01:00:28Unexpected error importing weback_vacuum/group.py
Unexpected error importing weback_vacuum/media_source.py
Unexpected error importing weback_vacuum/cast.py
Unexpected error importing weback_vacuum/significant_change.py
Unexpected error importing weback_vacuum/hardware.py
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/integration_platform.py”, line 40, in _async_process_single_integration_platform_component
platform = integration.get_platform(platform_name)
File “/usr/src/homeassistant/homeassistant/loader.py”, line 779, in get_platform
cache[full_name] = self._import_platform(platform_name)
File “/usr/src/homeassistant/homeassistant/loader.py”, line 796, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File “/usr/local/lib/python3.10/importlib/init.py”, line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File “”, line 1050, in _gcd_import
File “”, line 1027, in _find_and_load
File “”, line 1004, in _find_and_load_unlocked
ModuleNotFoundError: No module named ‘custom_components.homeassistant_weback_component-main.diagnostics’
Logger: custom_components.homeassistant_weback_component-main.WebackApi
Source: custom_components/homeassistant_weback_component-main/WebackApi.py:585
Integration: homeassistant_weback_component-main
First occurred: March 30, 2023, 00:46:37 (3402 occurrences)
Last logged: 11:12:34WebackApi (WSS) Failed to puslish message after 8 retry
Logger: websocket
Source: /usr/local/lib/python3.10/site-packages/websocket/_logging.py:62
First occurred: March 30, 2023, 00:45:54 (75995 occurrences)
Last logged: 11:12:39
- error from callback <bound method WebackWssCtrl.on_message of <custom_components.homeassistant_weback_component-main.VacDevice.VacDevice object at 0x7f7f71b520>>: ‘working_status’
- Connection to remote host was lost. - goodbye
- error from callback <bound method WebackWssCtrl.on_message of <custom_components.homeassistant_weback_component-main.VacDevice.VacDevice object at 0x7f7f6b7c10>>: ‘working_status’
- Handshake status 500 Internal Server Error - goodbye
- Handshake status 403 Forbidden - goodbye
Hi !
Good job I got everything i need to fix it.
I will push an update as soon as possible 
1 Like
Glad I could help!
I had installed the integration manually… I’m trying to install it thru HACS but I get this message:
Ideas?
Hi,
first, good job, guys!
Really amazed with the effort.
But, this week, I hit with WAF (Wife Approval Factor) in the Vacuum App side and decided to abandon Mamibot from Weback.
Issue was, Weback did not handle map data (still not fixed for Mamibot) and used some old random map, that caused Vacuum to act stupid (like trying to go trough a wall as map shows empty place there).
I re-flashed Vacuum with Tuya based firmware and started using Tuya Smart and integrated to Home Assistant via Local Tuya. 80% works, the main functionality is there and this is okay for Minimum Viable Functionality for me (Was a lot of debugging and mapping of DP points but so far I managed). And WAF is good as Tuya app has more functions available, like floors, rooms, map saving etc.
I hope you shall succeed in the long run and keep up the good work!
My journey will not end here, I shall find another mountain to climb and during the climbing, hope to meet same great guys as you when solving yet another problem of integrating things to HA!
Regards,
Kenno