camera domain not showing up

[msavazzi]

Checks

• I have searched the existing issues and no issue is describing my issue
• I have checked the FAQ
• I have checked the documentation
• I have installed the latest version

The problem

I've installed the extension and followed the sample UI but the camera. domain does not exist so it does not show the map.

My robot is an ECOVACS DEEBOT OZMO T8 so it shows the map in the app. I cannot understand why is not visible

Diagnostics information

Anything in the logs that might be useful for us?

2022-05-19 22:06:25 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration deebot which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
account and will be unable to retrieve HEOS favorites: Use the 'heos.sign_in' service to sign-in to a HEOS account
2022-05-19 22:06:57 WARNING (MainThread) [deebot_client.commands.common] Command "getPos" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:06:57 WARNING (MainThread) [deebot_client.commands.common] Command "getStats" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:06:57 WARNING (MainThread) [deebot_client.commands.common] Command "getChargeState" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:12 WARNING (MainThread) [deebot_client.commands.common] Command "getCleanInfo" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:12 WARNING (MainThread) [deebot_client.commands.common] Command "getBattery" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:12 WARNING (MainThread) [deebot_client.commands.common] Command "getError" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:27 WARNING (MainThread) [deebot_client.commands.common] Command "getSpeed" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:27 WARNING (MainThread) [deebot_client.commands.common] Command "getCachedMapInfo" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}

Additional information

No response

[edenhaus]

Please provide the required diagnostic information.
Download the diagnostic data for the device you are having issues with (found on the device page) and append it here.

[msavazzi]

Please provide the required diagnostic information. Download the diagnostic data for the device you are having issues with (found on the device page) and append it here.

happy to do it but I do not know how. What you mean diagnostic data? device page where? I have no device page in homeassistant.

[xrh0905]

Logs?

[msavazzi]

Logs?

I've enabled the debug as instructed here:
https://deebot.readthedocs.io/integrations/home-assistant/issues/

with

logger:
  logs:
    homeassistant.components.vacuum: debug
    custom_components.deebot: debug
    deebot_client: debug

in the config.yaml

and posted the outcome in the initial post. Is there anything else I should do?

here is again

`2022-05-19 22:06:25 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration deebot which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-05-19 22:06:57 WARNING (MainThread) [deebot_client.commands.common] Command "getPos" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:06:57 WARNING (MainThread) [deebot_client.commands.common] Command "getStats" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:06:57 WARNING (MainThread) [deebot_client.commands.common] Command "getChargeState" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:12 WARNING (MainThread) [deebot_client.commands.common] Command "getCleanInfo" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:12 WARNING (MainThread) [deebot_client.commands.common] Command "getBattery" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:12 WARNING (MainThread) [deebot_client.commands.common] Command "getError" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:27 WARNING (MainThread) [deebot_client.commands.common] Command "getSpeed" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:07:27 WARNING (MainThread) [deebot_client.commands.common] Command "getCachedMapInfo" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:33:50 WARNING (MainThread) [deebot_client.commands.common] Command "playSound" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
2022-05-19 22:34:05 WARNING (MainThread) [deebot_client.commands.common] Command "clean" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}

[edenhaus]

Please provide the required diagnostic information. Download the diagnostic data for the device you are having issues with (found on the device page) and append it here.

happy to do it but I do not know how. What you mean diagnostic data? device page where? I have no device page in homeassistant.

Settings -> Devices & Services -> Click on the device under the "Deebot 4 Home Assistant" integration -> (select the affected deebot) -> click "Download diagnostics" below the device info

@msavazzi You are posting here only the warnings not the complete log. Please open the log-file and filter for the above loggers and afterwards post here all logs

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.