sh00t2kill
Service vacuum.turn_on not found
Hey Guys,
Great integration and all went well with installation, however, when accessing the controls via the integration or via the dashboard for my pool cleaner, I simply get the messages Service vacuum.turn_on not found and vacuum.turn_off not found. A search of services indicates that this is the case that there are no services called vacuum.turn_on or vacuum.turn_off.
Can you advise how this can be remedied, e.g. code your code be tweaked to allow the vacuum.start, vacuum.stop service calls instead of ones above in the first paragraph.
"Technically" you can't turn a dolphin pool robot on or off. You can only start and stop.
We did used to have turn_on be equal to start, will need to put this back I think.
For now you can use start
Turn on was supposed to run same action of start while turn off is stop, I also noticed it's not working and will get to it
Thanks so much guys. Yes, I thought it was strange that you would be 'turning on' or 'turning off'. I will wait for you to release an update. Thanks again for jumping this so quickly. Cheers.
There seem to be a bunch of other custom vacuum in the same state. Looks like the idea was to move from turn_on -> start, but the UI still shows the turn_on and turn_off actions.
Im not convinced this is actually something we can fix. turn on and turn off are not supported by the vacuum entity, and you cant (at least not that i can see anywhere) add custom services at the entity level, only at the base domain level (eg mydolphin_plus.turn_on as opposed to vacuum.turn_on)
We can, once the vacuum is on, there will be turn off button, will fix it locally and check
We have a fix for this, will be part of the next release.
HA does some black magic when it detects the off state. If anyone is using automations detecting the vacuum changing TO off, this will break.,
This is fantastic!! Really appreciate all your effort on this. Look forward to the next release
in v1.0.16 the unsupported actions will be removed - turn on, turn off, toggle, issue is that although it will be removed the UI component still presents the turn on, which I guess once it will fully deprecated (for now marked deprecated in future HA version)
Hey Guys, I have since installed v1.0.16 and .17 and the Service vacuum.turn_on not found action is still the error message when there is an attempt to start the pool cleaner via the vacuum card as well as the custom vacuum card suggested by the documentation.
Hey Guys, I have since installed v1.0.16 and .17 and the Service vacuum.turn_on not found action is still the error message when there is an attempt to start the pool cleaner via the vacuum card as well as the custom vacuum card suggested by the documentation.
https://github.com/sh00t2kill/dolphin-robot/issues/209#issuecomment-2213133471
@amicus1268 the play icon is to start not turn on, the turn on button is something that comes from HA not the integration - integration doesn't support turn/off
Then why does the play icon not start the device?
It should. This is technically a bug in HA core but we will need to work around it.
For the moment use a custom card where you can edit the start service call? Or just call the start service.
No need to share logs.
If it helps, I start the robot daily using the custom card by changing the drop-down from "Pickup" to "Floor Only" ... within a few seconds it will show "Scanning".
