Fix command_line binary sensor examples with correct payload values

[Copilot]

Proposed change

The binary sensor examples return "1" or "0" but omit payload_on/payload_off configuration. Since these default to "ON" and "OFF", the examples fail silently.

# Before - broken
command_line:
  - binary_sensor:
      command: "cat /proc/sys/net/ipv4/ip_forward"

# After - working
command_line:
  - binary_sensor:
      command: "cat /proc/sys/net/ipv4/ip_forward"
      payload_on: "1"
      payload_off: "0"

Type of change

• Adjusted missing or incorrect information in the current documentation (current branch).

Additional information

• This PR fixes or closes issue: fixes #

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.
• The documentation follows the Home Assistant documentation standards.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Binary sensor suggested command</issue_title>
<issue_description>### Feedback

The suggested commands for binary sensor in the template yaml are "cat /proc/sys/net/ipv4/ip_forward" and "echo 1". None of these work, as binary_sensor seems to only accept "ON" & "OFF" (case sensitive). It might be better to update these commands to [[ "$(cat /proc/sys/net/ipv4/ip_forward)" = 1 ]] && echo "ON" || echo "OFF" and "Echo ON", respectively.

URL

https://www.home-assistant.io/integrations/command_line/

Version

2025.11.2

Additional information

No response</issue_description>

<agent_instructions>The reporter is right, these examples:

Binary sensor
To use your Command binary sensor in your installation, add the following to your configuration.yaml file:

Example configuration.yaml entry

command_line:

• binary_sensor:
  command: "cat /proc/sys/net/ipv4/ip_forward"
• binary_sensor:
  command: "echo 1"

are not retuning NO or YES (which are the default payloads). These examples thus need to be extended with other payload settings (unlike the reporter suggest, he is suggesting adjusting the command line, which shouldn't be needed)
</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Binary sensor suggested command #41817

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[home-assistant]

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.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	db9dd96
🔍 Latest deploy log	https://app.netlify.com/projects/home-assistant-docs/deploys/691acade1e1de60008183e33
😎 Deploy Preview	https://deploy-preview-41820--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[Copilot]

Pull Request Overview

This PR fixes broken binary sensor examples in the command_line integration documentation. The examples were returning "1" or "0" but relied on the default payload_on/payload_off values of "ON"/"OFF", causing them to fail silently.

Key changes:

• Added explicit payload_on: "1" and payload_off: "0" configuration to both binary sensor examples

[c0ffeeca7]

Thank you, @frenck 👍