Add touchlinesl integration

[jnsgruk]

Breaking change

This PR introduces a new integration for the Roth Touchline SL underfloor heating system.

It supports reading temperature, humidity and preset, based on the pytouchlinesl library which I published earlier this week.

The system supports a constant target temperature per zone, and also has a number of "global schedules". In this integration, the "Presets" for the climate zone represent the configured global schedules.

See below some screenshots of the integration when connected to my TouchlineSL module:

Documentation PR to follow for the integration.

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

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add docs for new Touchline SL integration home-assistant.io#34441

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:

• Documentation added/updated for www.home-assistant.io

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:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @jnsgruk

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

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.

[joostlek]

There already is an integration for touchline, what's the difference?

[jnsgruk]

There already is an integration for touchline, what's the difference?

Touchline SL is essentially a completely different product - the original Touchline module speaks to the old controller over the LAN, whereas Touchline SL is controlled through an internet facing public API and has more features - the two are unfortunately not compatible 🙂

[joostlek]

Check. If it's ready for review, please mark it so

Stale

[jnsgruk]

Check. If it's ready for review, please mark it so

Done - I was just waiting until I'd got the docs and brands PRs together, which are now at:

• Add docs for new Touchline SL integration home-assistant.io#34441
• Add Touchline SL icons brands#5797

[jnsgruk]

@joostlek I think I've addressed all of your feedback, thanks for the tips!

I've made changes in two separate commits - let me know if you'd like me to squash down into a single commit again - I wanted to leave them separate so it was easy to see the changes I was making in response to our conversation.

[joostlek]

You can just leave your commits like that, in the end we squash them and merge them in one go. Squashing and force pushing only messes up the GitHub diff

[joostlek]

What are your future plans with the integration? Do you want to add more platforms? Based on that I might actually want to recommend using a coordinator. Using a coordinator centralizes the polling mechanism to a single component and it could help you clean up the updating part

[joostlek]

Oh and also please checkout fujitsu_fglair on how they added a brand. touchline already is an integration, so we can group them by manufacturer

[jnsgruk]

@joostlek I think I've addressed all bar one piece of feedback 🙂

[joostlek]

I'll have another pass after I've done my groceries. Feel free to send me a message on discord :)

[joostlek]

Do you have a link to the one piece? (That saves me going through everything, and you already know which one :) )

[jnsgruk]

Do you have a link to the one piece? (That saves me going through everything, and you already know which one :) )

#124557 (comment)

Thank you!

[joostlek]

I'm missing a test where we add a config entry with the same unique_id and test we abort if we set up again