Skip to content
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

Feature 2.0.0/routing cooldown fixes #1196

Merged
merged 26 commits into from
Aug 1, 2024

Conversation

ndorin
Copy link
Contributor

@ndorin ndorin commented Aug 1, 2024

  • Adds fixes to clear routes and prevent displays from powering back on when displays are in cooldown phase

ndorin and others added 26 commits June 25, 2024 16:08
Added `FireUpdate` calls for feedback on mode change in order to get correct values when changing modes.
As part of the Essentials startup process, ALL rooms are activated, meaning there are unnecessary rooms activated. Deactiving them all prior to determining a combination scenario helps keep unecessary activity from happening.
Most devices that implement IRouting will now need to handle the possiblity of a null as the input selector, with the idea being that a null input selector should clear the route to whatever device is selected as the input selector. This may change to a typed value in the future.
The routerequest is being removed if the route is successfully made after the display has cooled down. This was an extraneous removal
@andrew-welker andrew-welker merged commit 941e537 into development-2.0.0 Aug 1, 2024
1 check passed
@andrew-welker andrew-welker deleted the feature-2.0.0/routing-cooldown-fixes branch August 1, 2024 19:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants