WIP - introduce an API that waits for events #570
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A crazy idea to keep things future-proof with an infinite amount of customization options.
the basic problem with the integration is allowing users to customize anything and everything like home assistant users love to do 😄
This WIP intends to fire events with the currently attempted data (e.g. values from
calc_brightness_pct
), fire those in an event to HASS, wait for hass automation to see the trigger and fire an event with the replacement data, and simply use that in our functions instead.A full API. Why create features users ask for when instead we can implement ways for them to do it themselves to decrease the overall todo list (i.e.
change_switch_settings
)Probably nothing good here. Had fun learning about async timers & tasks though. Another idea is loading custom python functions from the config which users can set with
change_switch_settings
or the config flow.