Skip to content

Docs for TIS Control integration #37071

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

Draft
wants to merge 27 commits into
base: next
Choose a base branch
from
Draft

Conversation

KarimTIS
Copy link

@KarimTIS KarimTIS commented Jan 23, 2025

Proposed change

Added documentaion for TIS Control integration

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Introduced the TIS Control integration, allowing users to control TIS Control devices within Home Assistant.
    • Enhanced discoverability with detailed metadata for the TIS Control integration.
  • Documentation

    • Added a new markdown file with integration details, configuration instructions, and UDP communication settings for improved user guidance.

KarimTIS and others added 12 commits January 18, 2025 18:11
* Update network_storage.md

* Update network_storage.md

* tiny tweak

---------

Co-authored-by: c0ffeeca7 <[email protected]>
* aquacell.markdown: Tweak docs

* aquacell.markdown: Add TwinTec too

* aquacell.markdown: Mention Culligan
* Add debugging steps for nest integration.

Google can delete your pub/sub subscription. This adds troubleshooting steps to
address that issue for the nest integration.

* tiny tweak

* Update source/_integrations/nest.markdown

* Apply suggestions from coderabbitai code review

* Update source/_integrations/nest.markdown

* tweak to kick the CI

---------

Co-authored-by: c0ffeeca7 <[email protected]>
…e-assistant#37067)

Bumps [sorbet-runtime](https://github.com/sorbet/sorbet) from 0.5.11766 to 0.5.11778.
- [Release notes](https://github.com/sorbet/sorbet/releases)
- [Commits](https://github.com/sorbet/sorbet/commits)

---
updated-dependencies:
- dependency-name: sorbet-runtime
  dependency-type: indirect
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…7068)

Bumps [rubocop](https://github.com/rubocop/rubocop) from 1.70.0 to 1.71.0.
- [Release notes](https://github.com/rubocop/rubocop/releases)
- [Changelog](https://github.com/rubocop/rubocop/blob/master/CHANGELOG.md)
- [Commits](rubocop/rubocop@v1.70.0...v1.71.0)

---
updated-dependencies:
- dependency-name: rubocop
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Correct "lighting" to "lightning"
…sistant#37030)

* Update squeezebox.markdown

Clarify the integration connects to an exiting instance and doesn't provide the LMS control directly itself as this has come up a couple of times in the HA LMS add-no thread.

* Update source/_integrations/squeezebox.markdown

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update source/_integrations/squeezebox.markdown

Co-authored-by: c0ffeeca7 <[email protected]>

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: c0ffeeca7 <[email protected]>
@home-assistant home-assistant bot added the current This PR goes into the current branch label Jan 23, 2025
Copy link

netlify bot commented Jan 23, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 6de8c0b
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/6797c5774283cd0008e49431
😎 Deploy Preview https://deploy-preview-37071--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

coderabbitai bot commented Jan 23, 2025

📝 Walkthrough

Walkthrough

The pull request introduces a new markdown documentation file for the TIS Control integration in Home Assistant. This file contains metadata, configuration instructions, and guidance on integrating TIS Control devices, specifically switch devices like RCU and RELAY. It outlines the requirement for devices to be on the same local network and details the configuration process through the Home Assistant integrations page, including the specification of the UDP port.

Changes

File Change Summary
source/_integrations/tis_control.markdown New documentation file created with integration metadata, configuration instructions, and setup details for TIS Control devices

Sequence Diagram

sequenceDiagram
    participant User
    participant HomeAssistant
    participant TISDeviceManager
    participant TISControlDevice

    User->>HomeAssistant: Configure TIS Control Integration
    HomeAssistant->>User: Request UDP Port (default 6000)
    User->>HomeAssistant: Provide UDP Port
    HomeAssistant->>TISDeviceManager: Initialize Communication
    TISDeviceManager->>TISControlDevice: Discover and Add Devices
    HomeAssistant->>TISControlDevice: Enable Control and Monitoring
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🧹 Nitpick comments (2)
source/_integrations/tis_control.markdown (2)

3-4: Fix grammatical issues in the description.

The description should capitalize "Home Assistant" consistently.

-description: Instructions on how to integrate your TIS Control devices with home assistant.
+description: Instructions on how to integrate your TIS Control devices with Home Assistant.

22-22: Add missing newline at end of file.

Add a newline character at the end of the file to comply with markdown formatting standards.

🧰 Tools
🪛 Markdownlint (0.37.0)

22-22: null
Files should end with a single newline character

(MD047, single-trailing-newline)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7bd4ed0 and 734875d.

📒 Files selected for processing (1)
  • source/_integrations/tis_control.markdown (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
source/_integrations/tis_control.markdown

22-22: null
Files should end with a single newline character

(MD047, single-trailing-newline)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (1)
source/_integrations/tis_control.markdown (1)

4-4: Verify the version number format.

The version number 0.1.4 doesn't follow Home Assistant's typical versioning scheme (YYYY.M.X). Please verify if this is the correct version format for this integration.

Comment on lines 17 to 18
The TIS Control integration makes it possible to integrate and control TIS Control devices within Home Assistant.

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Enhance the integration description.

The current description lacks essential information. Consider adding:

  • What TIS Control devices are and their typical use cases
  • Prerequisites or requirements for using this integration
  • Supported device types or models
  • Network requirements or limitations

@home-assistant home-assistant bot added the has-parent This PR has a parent PR in a other repo label Jan 23, 2025
klaasnicolaas and others added 11 commits January 23, 2025 14:39
)

Update the TP-Link troubleshooting section with additional steps and guidelines.
…e-assistant#37135)

Bumps [sorbet-runtime](https://github.com/sorbet/sorbet) from 0.5.11778 to 0.5.11781.
- [Release notes](https://github.com/sorbet/sorbet/releases)
- [Commits](https://github.com/sorbet/sorbet/commits)

---
updated-dependencies:
- dependency-name: sorbet-runtime
  dependency-type: indirect
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ant#37136)

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4.1.0 to 4.2.0.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4.1.0...v4.2.0)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Add basic configuration

* Give the supported devices info its own header

* Remove `intergas` term

* Update source/_integrations/incomfort.markdown

* Add troubleshooing section
@KarimTIS KarimTIS marked this pull request as ready for review January 27, 2025 17:42
@home-assistant home-assistant bot added in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Jan 27, 2025
@home-assistant
Copy link

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.

@KarimTIS KarimTIS changed the base branch from current to next January 27, 2025 17:45
@home-assistant home-assistant bot removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch current This PR goes into the current branch labels Jan 27, 2025
@home-assistant home-assistant bot added the next This PR goes into the next branch label Jan 27, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

♻️ Duplicate comments (2)
source/_integrations/tis_control.markdown (2)

19-22: 🛠️ Refactor suggestion

Enhance the integration description.

The current description lacks essential information about TIS Control devices, prerequisites, and supported features.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

20-20: Bare URL used
null

(MD034, no-bare-urls)


24-27: 🛠️ Refactor suggestion

Add standard Home Assistant documentation sections.

The documentation is missing several standard sections typically included in Home Assistant integration documentation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~27-~27: A comma might be missing here.
Context: ...ation. The default port is 6000.
After this the integration will scan the network a...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🪛 markdownlint-cli2 (0.17.2)

27-27: Files should end with a single newline character
null

(MD047, single-trailing-newline)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 734875d and 6de8c0b.

📒 Files selected for processing (1)
  • source/_integrations/tis_control.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/tis_control.markdown

[uncategorized] ~27-~27: A comma might be missing here.
Context: ...ation. The default port is 6000.
After this the integration will scan the network a...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🪛 markdownlint-cli2 (0.17.2)
source/_integrations/tis_control.markdown

20-20: Bare URL used
null

(MD034, no-bare-urls)


27-27: Files should end with a single newline character
null

(MD047, single-trailing-newline)

Comment on lines +1 to +17
---
title: TIS Control
description: Instructions on how to integrate your TIS Control devices with home assistant.
ha_release: 0.1.4
ha_category:
- Network
- Notifications
ha_iot_class: Local Polling
ha_domain: tis_control
ha_platforms:
- switch
ha_codeowners:
- '@karimtis'
- '@Mustafa744'

ha_integration_type: integration
---
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Revise metadata section for accuracy.

Several metadata fields need attention:

  1. The description should capitalize "Home Assistant"
  2. The version number format should follow Home Assistant's YYYY.M.0 pattern
  3. The "Notifications" category seems incorrect for a switch control integration

Apply these changes:

 ---
 title: TIS Control
-description: Instructions on how to integrate your TIS Control devices with home assistant.
+description: Instructions on how to integrate your TIS Control devices with Home Assistant.
-ha_release: 0.1.4
+ha_release: 2024.2.0
 ha_category:
   - Network
-  - Notifications
+  - Switch
 ha_iot_class: Local Polling
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
title: TIS Control
description: Instructions on how to integrate your TIS Control devices with home assistant.
ha_release: 0.1.4
ha_category:
- Network
- Notifications
ha_iot_class: Local Polling
ha_domain: tis_control
ha_platforms:
- switch
ha_codeowners:
- '@karimtis'
- '@Mustafa744'
ha_integration_type: integration
---
---
title: TIS Control
description: Instructions on how to integrate your TIS Control devices with Home Assistant.
ha_release: 2024.2.0
ha_category:
- Network
- Switch
ha_iot_class: Local Polling
ha_domain: tis_control
ha_platforms:
- switch
ha_codeowners:
- '@karimtis'
- '@Mustafa744'
ha_integration_type: integration
---

Comment on lines +24 to +27
## Configuration

To enable the integration, go to the integrations page inside the configuration panel and add the TIS Control integration. You will be asked to enter the port number for the UDP communication. The default port is 6000.
After this the integration will scan the network and add the devices automatically to your Home Assistant device list under the TIS Control Integration.
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix formatting and grammar in configuration section.

The configuration section needs formatting and grammar improvements.

Apply these changes:

 ## Configuration
 
 To enable the integration, go to the integrations page inside the configuration panel and add the TIS Control integration. You will be asked to enter the port number for the UDP communication. The default port is 6000.
-After this the integration will scan the network and add the devices automatically to your Home Assistant device list under the TIS Control Integration.
+After this, the integration will scan the network and add the devices automatically to your Home Assistant device list under the TIS Control Integration.
+
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Configuration
To enable the integration, go to the integrations page inside the configuration panel and add the TIS Control integration. You will be asked to enter the port number for the UDP communication. The default port is 6000.
After this the integration will scan the network and add the devices automatically to your Home Assistant device list under the TIS Control Integration.
## Configuration
To enable the integration, go to the integrations page inside the configuration panel and add the TIS Control integration. You will be asked to enter the port number for the UDP communication. The default port is 6000.
After this, the integration will scan the network and add the devices automatically to your Home Assistant device list under the TIS Control Integration.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~27-~27: A comma might be missing here.
Context: ...ation. The default port is 6000.
After this the integration will scan the network a...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🪛 markdownlint-cli2 (0.17.2)

27-27: Files should end with a single newline character
null

(MD047, single-trailing-newline)

Comment on lines +19 to +22
The TIS Control integration makes it possible to integrate and control TIS Control devices within Home Assistant.
For full list of the products visit https://www.tiscontrol.com/.
currently the integration only supports switch devices aka (RCU, RELAY) devices.
To use the integration you need to have one or more supported device connected to the same local network and know which communication port they are using (default for TIS Control devices is udp 6000).
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix formatting and style issues.

The description section needs formatting improvements:

  1. Format the URL as a proper markdown link
  2. Capitalize sentence beginnings
  3. Format technical terms using backticks
  4. Fix grammatical issues

Apply these changes:

 The TIS Control integration makes it possible to integrate and control TIS Control devices within Home Assistant.
-For full list of the products visit https://www.tiscontrol.com/.
-currently the integration only supports switch devices aka (RCU, RELAY) devices.
-To use the integration you need to have one or more supported device connected to the same local network and know which communication port they are using (default for TIS Control devices is udp 6000).
+For a full list of the products, visit [TIS Control's website](https://www.tiscontrol.com/).
+Currently, the integration only supports switch devices (also known as `RCU` and `RELAY` devices).
+To use the integration, you need to have one or more supported devices connected to the same local network and know which communication port they are using (default for TIS Control devices is UDP port `6000`).
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The TIS Control integration makes it possible to integrate and control TIS Control devices within Home Assistant.
For full list of the products visit https://www.tiscontrol.com/.
currently the integration only supports switch devices aka (RCU, RELAY) devices.
To use the integration you need to have one or more supported device connected to the same local network and know which communication port they are using (default for TIS Control devices is udp 6000).
The TIS Control integration makes it possible to integrate and control TIS Control devices within Home Assistant.
For a full list of the products, visit [TIS Control's website](https://www.tiscontrol.com/).
Currently, the integration only supports switch devices (also known as `RCU` and `RELAY` devices).
To use the integration, you need to have one or more supported devices connected to the same local network and know which communication port they are using (default for TIS Control devices is UDP port `6000`).
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

20-20: Bare URL used
null

(MD034, no-bare-urls)

@KarimTIS KarimTIS marked this pull request as draft January 27, 2025 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-parent This PR has a parent PR in a other repo in-progress This PR/Issue is currently being worked on new-integration This PR adds documentation for a new Home Assistant integration next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.