Skip to content
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

input_datetime always triggers at the earliest setup time #116294

Open
crazyfacka opened this issue Apr 27, 2024 · 1 comment
Open

input_datetime always triggers at the earliest setup time #116294

crazyfacka opened this issue Apr 27, 2024 · 1 comment

Comments

@crazyfacka
Copy link

crazyfacka commented Apr 27, 2024

The problem

I use an input_datetime helper with only has_time: true to trigger an automation. The automation is successfully triggered, but always to the earliest time that the input_datetime was set.

Try (1):

  1. Set input_datetime to 8:00
  2. Automation triggers at 8:00

Try (2):

  1. Set input_datetime to 7:30
  2. Automation triggers at 7:30

Try (3):

  1. Set input_datetime to 8:00
  2. Automation triggers at 7:30

image

image

What version of Home Assistant Core has the issue?

core-2024.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

input_datetime

Link to integration documentation on our website

https://www.home-assistant.io/integrations/input_datetime/

Diagnostics information

No response

Example YAML snippet

alias: Office
description: ""
trigger:
  - platform: time
    at: input_datetime.alarm_trigger
condition:
  - condition: state
    entity_id: cover.sonoff_1001436ec2
    state: closed
    enabled: true
action:
  - service: automation.turn_off
    data:
      stop_actions: false
    target:
      entity_id:
        - automation.alarm_office_light
  - device_id: ae46f496b8fae2259607945b87c165e7
    domain: cover
    entity_id: cover.sonoff_1001436ec2
    type: set_position
    position: 70
  - if:
      - condition: state
        entity_id: sun.sun
        state: below_horizon
    then:
      - type: turn_on
        device_id: 7ad2f00102d55da8a94aa3621253544b
        entity_id: 9e7ec3253b5acfb37a49e4dc78656c51
        domain: switch
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

The value for the input_datetime is set in the UI using an Entity Card. Looking into the Developer Tools, the timestamp is updated accordingly.

@home-assistant
Copy link

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

Code owner commands

Code owners of input_datetime 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 input_datetime Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


input_datetime documentation
input_datetime source
(message by IssueLinks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant