Skip to content

Document zabbix publish_string_states config #36734

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 5 commits into from
Jun 30, 2025

Conversation

rusitschka
Copy link
Contributor

@rusitschka rusitschka commented Jan 5, 2025

Proposed change

This PR documents the new Zabbix config value publish_string_states introduced in PR 134773.

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

  • New Features
    • Added a new configuration option publish_string_states for Zabbix integration.
    • Enables publishing of string states that cannot be converted to numeric values.
    • Default setting is disabled (false).

@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Jan 5, 2025
Copy link

netlify bot commented Jan 5, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 7ace52f
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/685d8637cef74b000813c854
😎 Deploy Preview https://deploy-preview-36734--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 project configuration.

Copy link
Contributor

coderabbitai bot commented Jan 5, 2025

📝 Walkthrough

Walkthrough

The pull request adds a new configuration option publish_string_states to the Zabbix integration documentation. This boolean option, defaulting to false and marked as optional, enables publishing of string states that cannot be cast to numeric values. The change updates the configuration example and documentation without altering logic or control flow.

Changes

File Change Summary
source/_integrations/zabbix.markdown Added new configuration option publish_string_states
- Boolean, default false, optional
- Enables publishing of string states that cannot be cast to numeric values
- Updated example configuration to include publish_string_states: true

Sequence Diagram

sequenceDiagram
    participant User
    participant Zabbix Integration
    User->>Zabbix Integration: Configure with publish_string_states
    alt publish_string_states is true
        Zabbix Integration->>Zabbix Integration: Publish string states
    else publish_string_states is false (default)
        Zabbix Integration->>Zabbix Integration: Skip string states
    end
Loading

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 2020a7e and 7ace52f.

📒 Files selected for processing (1)
  • source/_integrations/zabbix.markdown (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_integrations/zabbix.markdown
⏰ 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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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: 0

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

65-69: Enhance documentation clarity for the include_strings option.

While the documentation follows the correct format, it could be more helpful by:

  1. Clarifying what happens to string states when include_strings is false (are they ignored, filtered out, etc?)
  2. Adding an example configuration showing its usage

Consider adding this example to the "Full configuration" section:

  zabbix:
    host: ZABBIX_HOST
    path: ZABBIX_PATH
    ssl: false
    username: USERNAME
    password: PASSWORD
    publish_states_host: homeassistant
+   include_strings: true
    exclude:
      domains:
        - device_tracker

65-69: Add reference to the parent PR.

To help with tracking changes and providing additional context, consider adding a comment referencing the parent PR where this feature was introduced (PR 134773).

Add a small note in the description:

  include_strings:
    description: >-
      Also publish string states, i.e. states which cannot be cast to a numeric value.
+     Introduced in Home Assistant Core PR #134773.
    required: false
    type: boolean
    default: false
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 29d08bd and bc0b5ac.

📒 Files selected for processing (1)
  • source/_integrations/zabbix.markdown (1 hunks)

@rusitschka rusitschka changed the title Document zabbix include_strings config Document zabbix publish_string_states config Jun 26, 2025
@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Jun 30, 2025
@frenck frenck merged commit 77e19ab into home-assistant:next Jun 30, 2025
7 checks passed
@home-assistant home-assistant bot removed the parent-merged The parent PR has been merged already label Jun 30, 2025
@@ -62,6 +62,11 @@ publish_states_host:
description: The host that will receive the state changes from Home Assistant. It needs to be manually created in Zabbix first and have the template associated with it (see above).
required: false
type: string
publish_string_states:
description: Also publish string states, i.e. states which cannot be cast to a numeric value.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
description: Also publish string states, i.e. states which cannot be cast to a numeric value.
description: Also publish string states. That is, states that cannot be cast to a numeric value.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was already merged - @c0ffeeca7 should I re-open the PR?

@c0ffeeca7
Copy link
Contributor

haha, yes, Frenck was quick 🚀 . Nah, it's fine. It's a nitpick. We avoid e.g. and i.e., as per Style Guide. Keep an eye out for it next time.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has-parent This PR has a parent PR in a other repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants