Fix value for multi_touch event publishing

[edwardtfn]

fixes #74
Value was "OFF" instead of "ON"

Summary by CodeRabbit

• New Features
  • Enhanced touch panel responsiveness
  • Updated multi-touch and swipe event handling
• Documentation
  • Added comments about hardware button and vibration integration for touch events

[coderabbitai]

Walkthrough

The pull request modifies the ESPHome configuration file for touch events, specifically updating the state publishing for multi-touch and swipe events. The changes involve switching the state of various binary sensors from OFF to ON when touch events occur, including multi-touch releases and different swipe directions. Comments have been added to provide context about hardware button and vibration extensions for these touch events.

Changes

File	Change Summary
ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_touch.yaml	- Updated state publishing for multi-touch release events from OFF to ON - Modified states for swipe events (bs_swipe_left, bs_swipe_down, bs_swipe_right, bs_swipe_up) to ON - Added comments about hardware button and vibration extensions

Assessment against linked issues

Objective	Addressed	Explanation
Multitouch event update [#74]	✅

The changes directly address the issue reported in #74, where the multitouch event was not updating. By changing the state to ON for multi-touch events, the configuration now ensures that the touch events are properly reflected in the system's state.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_touch.yaml (1)

319-322: Consider documenting the event state behavior.

While the implementation is correct, it would be helpful to add a brief comment explaining that the ON state indicates event occurrence, especially since this behavior was previously incorrect.

Add a comment like this:

  - id: touch_on_multi_touch_release
    mode: restart
    then:
      # Extended by:
      #   - HW Buttons
      #   - HW Vibration
+     # Publishes ON state to indicate multi-touch release event occurrence
      - binary_sensor.template.publish:
          id: bs_multi_touch
          state: ON  # yamllint disable-line rule:truthy

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2e43160 and 48ddfbf.

📒 Files selected for processing (1)

• ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_touch.yaml (1 hunks)

🔇 Additional comments (1)

ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_touch.yaml (1)

321-321: LGTM! This fixes the multi-touch event state.

The change from OFF to ON correctly fixes the state publishing for multi-touch release events, ensuring proper event signaling. This aligns with the expected behavior where touch events should trigger an "ON" state to indicate the event occurred.