fix: Removed status indicator, ensure display is ready before updating #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* `display.yaml`: Ensure display is ready before updating, on recent ESPHome versions the lambdas performing diplay updates might get called before display component is ready, leading to creash * `indicator.yaml`: Removed status indicator, seemingly leading to crash on newer ESPHome versions since it is handled by WiFi controller. It is suspected the processing might now have some concurrency issues or race condition * `schedule.yaml`: Allowed to be optional * `rtc.yaml`, `time.yaml`, `display.yaml`: Updated to allow excluding those (using dereference operator instead of `id`, otherwise ESPHome will claim it can't resolve referenced symbol)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
display.yaml: Ensure display is ready before updating, on recent ESPHome versions the lambdas performing diplay updates might get called before display component is ready, leading to creashindicator.yaml: Removed status indicator, seemingly leading to crash on newer ESPHome versions since it is handled by WiFi controller. It is suspected the processing might now have some concurrency issues or race conditionschedule.yaml: Allowed to be optionalrtc.yaml,time.yaml,display.yaml: Updated to allow excluding those (using dereference operator instead ofid, otherwise ESPHome will claim it can't resolve referenced symbol)