Add config option and update flow for pressure sensors - #459
Open
da-sa-li wants to merge 24 commits into
Open
Conversation
…tion-in-integration Propagate source unknown/unavailable states to derived sensors
da-sa-li
marked this pull request as ready for review
June 16, 2026 19:41
Home Assistant deprecated `FlowHandler.show_advanced_options` in Core 2026.6: it now always returns True, logs a deprecation warning on every access, and is removed in 2027.6. User profile advanced mode is going away, so a data entry flow can no longer tell advanced users apart. Show the poll, scan interval, custom icons and enabled sensors options to everyone, and always offer the wider entity list in the temperature and humidity pickers, keeping entities with a matching device class first. Without it, sensors that carry no device class could not be selected by anyone. The `no_sensors_advanced` abort reason is therefore unreachable and is merged into `no_sensors`, which takes over its wording in every translation. Raise the minimum supported Home Assistant to 2026.6.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QYoDyQh9qU1KcnSohNSpex
Home Assistant Core 2026.7 introduced the `UnitOfDensity` and `UnitOfRatio` enumerators, which replace the `CONCENTRATION_*` constants. Declare the absolute humidity unit through `UnitOfDensity.GRAMS_PER_CUBIC_METER` instead of a bare string. The value is unchanged, so no entity is affected. The enumerators spell the micro prefix as U+03BC while the constants they replace used U+00B5, so the config flow now excludes both spellings of the microgram concentration units. Without it, a sensor reporting the new spelling would show up among the selectable source entities. This requires Home Assistant 2026.7, so raise the minimum and move the pytest matrix to Python 3.14, which the supported Home Assistant versions require. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QYoDyQh9qU1KcnSohNSpex
Use the unit enumerators for density and ratio units
|
I'd like to apply your PR to my fork. Can you submit the PR to https://github.com/dewi-ny-je/thermal_comfort ? thanks |
This reverts commit d89724c.
Local brand images
Add a release workflow that works out the next version from the commits since the most recent release tag, following Conventional Commits: a `!` marker or a `BREAKING CHANGE:` footer bumps the major, `feat` bumps the minor and everything else bumps the patch. Merge commits are ignored. It publishes the tag, the release and the notes, and can be started by hand to override the bump or to do a dry run. The archive workflow becomes reusable so the release workflow can attach the zip itself. A release created with GITHUB_TOKEN does not trigger the `release` event, so relying on that trigger alone would leave the release without the archive HACS expects. It keeps the `release` trigger for releases published by hand, and now resolves the package directory without tripping over `__pycache__` and uploads through the gh CLI, so the tag is correct on both paths. The other workflows gain `workflow_dispatch`, `concurrency` groups and an empty top level `permissions` with the minimum granted per job, and move to the current action versions. `no-commit-to-branch` is skipped in CI, where it has no local branch to guard. Dependabot keeps the actions and the test requirements up to date. Also fix the two checks that were already failing on master: three unused imports in the config flow tests, a comment black wanted to reformat and the formatting of the inlang settings. The gitignore grows the usual Python, pytest, coverage and editor entries, and `.github/scripts` is allowed to write to stdout. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QYoDyQh9qU1KcnSohNSpex
…mpatibility-45ia3h ci: automate releases and tighten the workflows
Update manifest.json with new codeowners and links
Delete custom_components/__init__.py
Remove unnecessary fields from hacs.json
`hacs.json` no longer sets `zip_release`, so HACS takes the other download path: `download_repository_zip()` fetches the source archive of the tagged commit and extracts the integration directory as committed. The zip asset it used to read, the only place the release workflow wrote the version, is no longer looked at. The version the integration reports to Home Assistant is therefore whatever `manifest.json` holds at the tagged commit, which would stay at 2.3.0 for every future release. Write the version into the manifest, commit it and tag that commit instead. The push uses GITHUB_TOKEN, which does not start another workflow run, so this cannot loop. Since the manifest now tracks the released version, it also serves as the baseline when the repository has no release tag yet, which removes the need to seed one by hand. A tag still wins when there is one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QYoDyQh9qU1KcnSohNSpex
…ompatibility-45ia3h fix(ci): commit the release version to the manifest
Author
Sure, no problem! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The pressure is hardcoded at 101325 Pa. This PR adds the option to add a pressure sensor in the config flow and use actual measurements for the calculations.
If no pressure sensor is configured, there is a fallback using the barometric formula and the elevation above sea level.
Resolves Issue #2