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.

Sign up for GitHub

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

Jump to bottom

Incorrect flag for valid use of 'not' condition #340

Closed
grantalewis opened this issue May 23, 2020 · 5 comments · Fixed by #374 or #375
Closed

Incorrect flag for valid use of 'not' condition #340

grantalewis opened this issue May 23, 2020 · 5 comments · Fixed by #374 or #375
Labels
yaml

Comments

@grantalewis
Copy link 

  - alias: Trigger Son Asleep When No Alarm Set
    initial_state: 'on'
    trigger:
      - platform: time_pattern
        minutes: '/5'
        seconds: 00
    condition:
      condition: and
      conditions:
        - condition: template
          value_template: >
            {{ is_state('light.son_bedroom_son_bedroom_fan_light','off') and is_state('light.son_bedroom_son_bedroom_fan','on') }}
        - condition: state
          entity_id: input_boolean.son_awake
          state: 'on'
        - condition: not
          conditions:
            - condition: time
              after: '07:00:00'
            - condition: time
              before: '22:00:00'
    action:
      - service: input_boolean.turn_off
        entity_id: input_boolean.son_awake

Screen Shot 2020-05-23 at 8 31 46 AM
@grantalewis grantalewis changed the title VSC add-on incorrectly flags valid use of new 'not' condition VSC incorrectly flags valid use of new 'not' condition May 23, 2020
@grantalewis grantalewis changed the title VSC incorrectly flags valid use of new 'not' condition Incorrect flag for valid use of 'not' condition May 23, 2020
@denniswham
Copy link

denniswham commented May 25, 2020 •
edited
Loading

Solved by PR #337

@grantalewis
Copy link
Author

grantalewis commented May 31, 2020 •
edited
Loading

FYI applied the update to version: 2.3.0 but am still seeing "Value not accepted."

Screen Shot 2020-05-30 at 8 59 40 PM

@denniswham
Copy link

denniswham commented May 31, 2020 via email

@grantalewis
Copy link
Author

Just checking: any progress on this? I'm still seeing the issue.

@frenck frenck mentioned this issue Jul 11, 2020
Merged
@keesschollaart81 keesschollaart81 mentioned this issue Jul 12, 2020
Merged
@frenck
Copy link
Collaborator

frenck commented Jul 12, 2020

Fixed in 1.7.0

@frenck frenck closed this as completed Jul 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
yaml
Projects
None yet
Milestone
No milestone
3 participants
@frenck @grantalewis @denniswham