8000 Bump Intellifire to 4.1.9 by jeeftor · Pull Request #121091 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bump Intellifire to 4.1.9 #121091

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

Merged
merged 50 commits into from
Sep 1, 2024
Merged

Conversation

jeeftor
Copy link
Contributor
@jeeftor jeeftor commented Jul 3, 2024

Proposed change

I had a previous PR #107479 that was closed due to inactivity. The hold up with that PR was trying to figure out if I should do a migration / minor-migration or no migration. Based on reading through the docs I'm going to use a proper migration - as the new configuration is no longer going to be backwards compatible.

This means a minor version bump is backwards compatible unlike a major version bump which causes the integration to fail setup if the user downgrades Home Assistant Core without restoring their configuration from backup.

As for the contents of the PR

Reason

In preparation for ultimately adding Cloud support to this integration I need to bump the backing library. I've been in touch with the manufacture and they've given me updated guidance on how to fix the backing library. As such this backing library comes with some additional code changes as well.

Update backing lib

The new backing library uses a UnifiedFireplace which has access to both Cloud and Local functions. This PR is only using the local functions but in order to support the new backing-lib we there was some code refactoring that needed to occur.

Update to config-flow

Based on discussion with HTT (Home and Hearth technologies) - previous backing library was handling the "login flow" a little wonky. By changing how thats handled - it also gave me the opportunity to simply the config flow.

Sensor updates

Some of the sensors also had to be updated to support the backing-lib changes...

jeeftor/intellifire4py@2.2.2...v4.1.9

  • Changes to backing lib have been discussed with manufactuer
  • Adding a new user-agent to tag our traffic as coming from python
  • Fixed the login-flow to be more performant

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, 10000 web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

@home-assistant home-assistant bot marked this pull request as draft August 17, 2024 16:49
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@jeeftor jeeftor force-pushed the intellifire_bump_migrate branch 4 times, most recently from c9f22d6 to 84f5bce Compare August 19, 2024 19:22
@jeeftor jeeftor marked this pull request as ready for review August 26, 2024 14:33
@home-assistant home-assistant bot requested a review from joostlek August 26, 2024 14:33
@crayolakranz
Copy link

Hi, my name is Garrett Kranz and I work for Hearth & Home Technologies. We manufacture the fireplaces and control systems that this integration leverages. We had requested these changes from @jeeftor awhile back to reduce stress on our devices and servers. Is there any way you can help expedite the request? @joostlek

@home-assistant home-assistant bot marked this pull request as draft August 29, 2024 17:57
@jeeftor jeeftor requested a review from joostlek August 29, 2024 19:01
@jeeftor jeeftor marked this pull request as ready for review August 29, 2024 19:45
@home-assistant home-assistant bot marked this pull request as draft August 30, 2024 09:35
@jeeftor jeeftor force-pushed the intellifire_bump_migrate branch from 28837c2 to ab1427d Compare August 30, 2024 11:23
@jeeftor jeeftor marked this pull request as ready for review August 30, 2024 11:52
@home-assistant home-assistant bot requested a review from joostlek August 30, 2024 11:52
@joostlek joostlek changed the title Bump Intellifire - Backing library - with minor refactor Bump Intellifire to 4.1.9 Aug 30, 2024
@joostlek joostlek added this to the 2024.9.0 milestone Sep 1, 2024
@joostlek joostlek merged commit 12336f5 into home-assistant:dev Sep 1, 2024
40 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Sep 2, 2024
except LoginException:
errors["base"] = "api_error"
LOGGER.error("Invalid credentials for iftapi.net")
Local control of IntelliFire devices requires that the user download the correct API KEY which is only available on the cloud. Cloud control of the devices requires the user has at least once authenticated against the cloud and a set of cookie variables have been stored locally.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please follow PEP8 for docstrings. Lines should be shorter than 72 characters.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0