fix: Update uptime endpoint paths after breaking change migration on portal - #8
Merged
Merged
Conversation
…tive-uptime/ Resolves 404 errors after flowerhub portal breaking change in July 2026.
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
1 participant
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.
This pull request updates the Flowerhub portal API client and documentation to match a breaking change in the Flowerhub backend API, where all uptime-related endpoints have been renamed from
/asset-uptime/to/asset-effective-uptime/. This resolves 404 errors reported by Home Assistant integration users after a breaking change on flowerhub portal API in July 2026 and ensures continued compatibility with the Flowerhub API.API Endpoint Migration:
flowerhub_portal_api_client/async_client.pyto use/asset-effective-uptime/paths instead of/asset-uptime/for available months, bar chart history, and pie chart endpoints. [1] [2] [3]docs/REST_API_specification.mdto reflect the new endpoint paths for uptime-related resources. [1] [2] [3]Tests and Versioning:
tests/test_client.pyto use the new/asset-effective-uptime/endpoint paths, ensuring tests remain valid. [1] [2] [3] [4] [5] [6] [7]1.0.1inpyproject.tomland added a changelog entry describing the migration and its impact. [1] [2]