Closed 2rs closed 5 years ago
trigger:
- at: 08:00:00
platform: time
This should not be able to work. 08:00:00
without quotation marks will be interpreted as 28800
, e..g. 8 60 60 seconds. It is not valid for at
field which requires a time
value.
Well, I have tried several times to correct it by manually encapsulating all occurences that was missing apostrophes, but as soon as I do something in the automations editor and save the changes then the yaml will look like it used to - that is, broken like my example.
I have also observed this issue. I wonder if https://github.com/home-assistant/home-assistant/issues/20976 is related to this issue also, as I see the same happening in their config
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Home Assistant release with the issue:
homeassistant: 0.86.4
Last working Home Assistant release (if known): Only noticed inconsistent formating recently
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io raspberry pi
Component/platform:
Description of problem:
Automation Editor behaves inconsistent when encapsulating time values with apostrophes. Sometimes with and sometimes not. I've noticed this with time values. If I clean up my automations.yaml manually the editor wil remove my clean up and back to inconsistent encapsulation the next time the editor is started.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: I placed this by error in the home-assistant-polymer, but closed it and reposted here.