-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
Fix for time_date sensor #10694
Fix for time_date sensor #10694
Conversation
Thanks! |
* fix to time_date sensor * cleaned up the code and added unit tests * fixed lint errors
* fix to time_date sensor * cleaned up the code and added unit tests * fixed lint errors
is this a fix for the time date picker or is this picker still not available? |
The datetime_input should be "available". What bug are you experiencing? |
Not necessarily a bug, but the current method of entering a time is nearly impossible. A 0 gets added automatically at times, the field jumps from the hour to minute when you don’t want it to, and all of this is worse using the iOS app. I don’t know if there’s a better way to select a time that’s less frustrating, but it’s currently very difficult. Also, the calendar doesn’t display correctly with the iOS app. Only one week appears in the monthly popup and it’s difficult to scroll and pick the correct date. Maybe this is an iOS app bug?? |
Don't discuss unrelated topics in a PR |
Description:
This is a fix to
date
option oftime_date
sensor.Related issue (if applicable): fixes #10477
Example entry for
configuration.yaml
(if applicable): N/AChecklist:
If the code does not interact with devices:
tox
run successfully. Your PR cannot be merged unless tests pass