core icon indicating copy to clipboard operation
core copied to clipboard

Vacuum docked state event is not triggered/listened correctly

Open MacrosorcH opened this issue 2 years ago • 2 comments

The problem

I have a few automations triggered by status of vacuum changing to 'docked' that, for some reason, don't trigger anymore ,although the status of the vacuum is indeed docked.

What version of Home Assistant Core has the issue?

2023.5.5

What was the last working version of Home Assistant Core?

2023.4.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

MacrosorcH avatar Jun 02 '23 23:06 MacrosorcH

It looks like it's actually the wait_for_trigger that is not working anymore, as the 'docked' event is triggered correctly but the wait_for_trigger keeps waiting forever.

wait_for_trigger:
  - platform: device
    device_id: 1e7d3d52c721764780968e1e76d095743
    domain: vacuum
    entity_id: vacuum.robot
    type: docked
continue_on_timeout: false
timeout:
  hours: 0
  minutes: 0
  seconds: 0
  milliseconds: 0

MacrosorcH avatar Jun 03 '23 08:06 MacrosorcH

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (automation) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of automation can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign automation Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


automation documentation automation source (message by IssueLinks)

home-assistant[bot] avatar Jun 05 '23 07:06 home-assistant[bot]

I rewrote from scratch the automation that was using the problematic wait_for_trigger and it is working now, so... not sure what happened, but I'm closing this issue! Thanks anyway and sorry for the noise!

MacrosorcH avatar Jun 07 '23 21:06 MacrosorcH