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

Add option to allow to use setpoint instead of override for legacy incomfort RF gateway #135143

Open
wants to merge 8 commits into
base: dev
Choose a base branch
from

Conversation

jbouwh
Copy link
Contributor

@jbouwh jbouwh commented Jan 8, 2025

Proposed change

Some older InComfort RF Gateways do not reset the override setting after the setpoint of a climate has changed manually. In that case the changed setpoint is not updated in Home Assistant. To work-a-round this issue this PR adds an option that allows to return the setpoint instead of the override. As side effect is though that when the setpoint is changed using the override, it will take some time for the climate to show the correct setpoint as the override attribute will be ignored.

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, 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.

To help with the load of incoming pull requests:

@jbouwh jbouwh changed the title Add option to allow to use setpoint in stead of override for legacy incomfort RF gateway Add option to allow to use setpoint instead of override for legacy incomfort RF gateway Jan 8, 2025
@joostlek
Copy link
Member

joostlek commented Jan 9, 2025

Some older InComfort RF Gateways

Is it possible to detect this?

@jbouwh
Copy link
Contributor Author

jbouwh commented Jan 9, 2025

Some older InComfort RF Gateways

Is it possible to detect this?

We can detect a serial number but cannot decide on the software version at the moment.
Also it is not clear what software version works, and which one does not.

@jbouwh jbouwh requested a review from joostlek January 9, 2025 22:25
@@ -63,9 +78,60 @@ async def async_try_connect_gateway(
return None


class InComfortOptionsFlowHandler(OptionsFlow):
Copy link
Member

Choose a reason for hiding this comment

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

Let's put this one below the ConfigFlow

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The config flow holds a reference to the options flow, so it is easier to define the OptionFlowHandler first

homeassistant/components/incomfort/config_flow.py Outdated Show resolved Hide resolved
Comment on lines 105 to 112
self.hass.config_entries.async_update_entry(
self.config_entry, options=new_options
)
self.hass.async_create_task(
self.hass.config_entries.async_reload(self.config_entry.entry_id),
eager_start=False,
)
return self.async_create_entry(data=new_options)
Copy link
Member

Choose a reason for hiding this comment

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

I know we have this helper for reauth, does it work for options flow as well?

Copy link
Contributor Author

@jbouwh jbouwh Jan 10, 2025

Choose a reason for hiding this comment

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

Reauth is for configflow, not for the option flow, but a helper would be a good idea for a new PR

Copy link
Member

Choose a reason for hiding this comment

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

Oh I didn't mean the reload helper, I meant the update data and reload integration one

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I know, but this was another improvement

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As we want to class create entry, we do not want to reload and abort, as we do with reauth in the config flow.

homeassistant/components/incomfort/strings.json Outdated Show resolved Hide resolved
homeassistant/components/incomfort/strings.json Outdated Show resolved Hide resolved
homeassistant/components/incomfort/config_flow.py Outdated Show resolved Hide resolved
@home-assistant home-assistant bot marked this pull request as draft January 10, 2025 11:48
@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.

@jbouwh jbouwh marked this pull request as ready for review January 10, 2025 16:11
@home-assistant home-assistant bot requested a review from joostlek January 10, 2025 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants