-
Notifications
You must be signed in to change notification settings - Fork 100
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
feat: Sch departure and charging binary sensor #441
Conversation
…into sch-binary
#164 I don't think this fully closes the issue. We really need an input_time entity made available to integrations or the dedicated service calls. |
I'll merge this for now. We're limited by what HA exposes to us and I'm reluctant to try to hack other items like a text input to get that functionality. |
I think these binary sensors would still be helpful even if we had the full solution available. I'm on the fence with a number input being the "minutes after midnight". That's doesn't feel very intuitive. |
In the Tesla app, we can only set the minutes in 15 minute increments. If I add an Entity card with the |
Huh, I did not know this. Guess I have never tired to set it to odd minutes in the hour.
HA integrations cannot make an input_datetime automatically. That entity type can only be added by individual users. My recommendation here is to use templates to convert an input_datetime into the equivalent minutes after midnight the API expects to receive. Then use that template in the custom_api call found in the Wiki here. If and when integrations can add a Time entity I'd like to build out switches for scheduling. |
No description provided.