-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TTEC vacuum #1545
Comments
if the voice assistant works without errors, maybe there is another command to start cleaning? |
An activate dp is required to start/pause the vacuum if there is no start and pause command in the command dp. We had followed the tuya naming of this as "pause" to integrate the pause command into the command dp, but there is still no "start" command. It is better to separate it back out and reverse the logic to make it an "activate" dp. Issue #1545
Logger: custom_components.tuya_local.device Пылесос receive loop has terminated does not start( |
Remain with the original assumption that pause missing means not paused. Issue #1545
it does not start (the voice assistant does not work either, although it worked before)
|
"the same error when adding" It seems like you are maybe adding multiple copies of the integration? You should only need to add each device once. Even if the config changes, you do not need to add it again. |
Yes, you're right, the mistake is because of this |
- dp 1 labelled switch_go in Tuya docs. Seems this should be activate, not power. - dp 2 labelled pause in Tuya docs. Assume this works in combination with dp 1 as push buttons doing the opposite thing - combine into activate attribute. - dp 3 since dp 1 is no longer marked as the power dp, this can become the power dp (it is marked as charge_go, which implies it controls power to the charging) Issue #1545
Maybe I misunderstood the function of those first three dps. I have made another attempt with another combination. This time, the logic should set switch_go to true when start is pressed, and pause to true when pause is pressed. These two dps are assumed to work together now. |
does not work |
I don't understand this. There is no start button in the screenshots in #1491, according to the history of the config, the start button would not have started appearing until the first fix on this issue yesterday. |
if there are no more ideas, then return this yaml, at least the voice assistant works here |
I think a comment on #1393 has helped to understand how the switch_go, pause and switch_charge dps operate. I have separated them out as buttons in case the vacuum is still not working correctly with them. |
now it says "the device is not supported"Device matches None with quality of 0%. DPS: {"updated_at": 1706343412.8754532, "4": "chargego", "5": "charge_done", "6": 0, "7": 0, "8": 100, "9": "strong", "10": "closed", "17": 189, "19": 289, "21": 139, "23": 149, "26": 8, "28": 0} |
maybe I should run it through the cloud in tuya? is there anything useful to learn there? Everything works there |
An activate dp is required to start/pause the vacuum if there is no start and pause command in the command dp. We had followed the tuya naming of this as "pause" to integrate the pause command into the command dp, but there is still no "start" command. It is better to separate it back out and reverse the logic to make it an "activate" dp. Issue make-all#1545
Remain with the original assumption that pause missing means not paused. Issue make-all#1545
- dp 1 labelled switch_go in Tuya docs. Seems this should be activate, not power. - dp 2 labelled pause in Tuya docs. Assume this works in combination with dp 1 as push buttons doing the opposite thing - combine into activate attribute. - dp 3 since dp 1 is no longer marked as the power dp, this can become the power dp (it is marked as charge_go, which implies it controls power to the charging) Issue make-all#1545
I do not know what to do with this vacuum cleaner, it is already boring...
after the previous fix, the cleaning start button is no longer pressed (while everything works through the voice assistant) and outputs a bunch of errors
previous fix - #1509
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:238
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:19:18 (1 occurrences)
Last logged: 11:19:18
[281472147770816] Entity vacuum.pylesos does not support this service.
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 864, in entity_service_call
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity vacuum.pylesos does not support this service.
The text was updated successfully, but these errors were encountered: