Venetian Blind support #205
Open
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
`speed` was removed in Home Assistant 2022.04. This fixes control of fans.
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. - [Release notes](https://github.com/substack/minimist/releases) - [Commits](https://github.com/substack/minimist/compare/1.2.5...1.2.6) --- updated-dependencies: - dependency-name: minimist dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [ansi-regex](https://github.com/chalk/ansi-regex) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/chalk/ansi-regex/releases) - [Commits](chalk/ansi-regex@v4.1.0...v4.1.1) --- updated-dependencies: - dependency-name: ansi-regex dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Switch to using `percentage` instead of `speed` for fans
…regex-4.1.1 chore(deps): bump ansi-regex from 4.1.0 to 4.1.1
…ist-1.2.6 chore(deps): bump minimist from 1.2.5 to 1.2.6
…ream Correctly handle single speed fans
Since we use Github Actions for releases, we don't need to keep a potentially outdated dist file checked in.
rollup-plugin-uglify has been replaced with rollup-plugin-terser but the dependency wasn't cleaned up. Removing will allow for resolving https://github.com/custom-cards/slider-button-card/security/dependabot/1
Remove rollup-plugin-uglify
Mostly for the releases badge to work, but fixed all links in this file to point to the new fork instead of the original repo. Might want to update the 'buy me a coffee' link? Also added credit to mattieha so licensing is happier.
Update README.md
Remove /dist/ directory and add to .gitignore
Bumps [terser](https://github.com/terser/terser) from 4.8.0 to 4.8.1. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…er-4.8.1 chore(deps): bump terser from 4.8.0 to 4.8.1
Fix scrolling on touchscreens
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.0.4 to 3.1.2. - [Release notes](https://github.com/isaacs/minimatch/releases) - [Commits](isaacs/minimatch@v3.0.4...v3.1.2) --- updated-dependencies: - dependency-name: minimatch dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…match-3.1.2 chore(deps): bump minimatch from 3.0.4 to 3.1.2
Bumps [json5](https://github.com/json5/json5) and [tsconfig-paths](https://github.com/dividab/tsconfig-paths). These dependencies needed to be updated together. Updates `json5` from 2.2.0 to 2.2.3 - [Release notes](https://github.com/json5/json5/releases) - [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md) - [Commits](json5/json5@v2.2.0...v2.2.3) Updates `tsconfig-paths` from 3.9.0 to 3.10.1 - [Release notes](https://github.com/dividab/tsconfig-paths/releases) - [Changelog](https://github.com/dividab/tsconfig-paths/blob/master/CHANGELOG.md) - [Commits](dividab/tsconfig-paths@v3.9.0...v3.10.1) --- updated-dependencies: - dependency-name: json5 dependency-type: indirect - dependency-name: tsconfig-paths dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [json5](https://github.com/json5/json5) from 1.0.1 to 1.0.2. - [Release notes](https://github.com/json5/json5/releases) - [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md) - [Commits](json5/json5@v1.0.1...v1.0.2) --- updated-dependencies: - dependency-name: json5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Restore editor UI
…t-mode Fix vertical alignment of attribute in compact mode (fixes #58)
Upgrade to Node 18
Outstanding bug: Rounding error when input_number step is set to certain values (observed easily with step set to 2 or 3)
the step and the max of an input_number entity. Appears that at this time applyStep() is unnecessary, and was in fact causing the problem I have tested stepped sliders of both input_number entities as well as light and climate entities, and stepping still works as expected when applyStep() is not called at all. This does not resolve the issue where step count results in "illegal" values on certain input_number entities.
[feat] Add Support for input_number domain
Add docs for input_number
2 tasks
[feat] Add Support for number domain
Update sk.json
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.
Description:
I would like to see the correct visual representation for my venetian blinds tilt position.
Solution:
This would require another option to the background: slider option (currently solid, gradient, triangle, striped, custom) whereby the visual would be extremely thin lines at 50% tilt and changing to increasing thicker lines as the percentage increases or decreases away from 50% becoming completely opaque at 0% and 100%. The thickness of the lines would come from the percentage of tilt with 50% being 1px and increase to whatever px is required to fill the window at 0 and 100. A formula like abs( 50 - state(cover.blind) ) would give you 0px to 50px. The action of the slider opening/closing would come from another HA entity responsible for raising/lowering the blind.
So in essence the slider portion would come from 1 entity that raises/lowers the blind, which needs to be optional since in my case I do not have that feature automated, only tilt. The tilt entity would then only control the background image...thin lines becoming thicker and thicker as they tilt up/down.