Add BM8563 time component documentation

[Copilot]

• Review the PCF8563 documentation and implementation PR for BM8563
• Create the BM8563 documentation page at content/components/time/bm8563.md
• Update the documentation to include BM8563-specific features (timer_value and start_timer action)
• Test the documentation builds correctly with Hugo
• Verify all links and anchors work properly
• Address code review feedback (fix reference syntax, clarify timer_value description, add See Also links)
• Rebase branch onto next
• Update terminology from sleep_duration to timer_value to match ESPHome PR changes
• Fix BM8563 icon display by adding .svg extension to components index
• Add configuration options section for start_timer action following deep_sleep format
• Remove timer_value from component configuration (now only in start_timer action)

Original prompt

Create the documentation page for a new bm8563 page. Use the pcf8563 page as a base, since they are similar components. See the implementation PR for details: esphome/esphome#11616

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[abmantis]

@copilot rebase this to next

[Copilot]

@copilot rebase this to next

Rebased successfully onto next branch (547c4b2). The three commits are now based on the latest next branch and the documentation builds correctly.

However, I cannot force-push the rebased commits due to authentication constraints. You'll need to either:

1. Pull the rebased changes locally and force-push them, or
2. Provide force-push capabilities to complete the rebase

Local commits after rebase:

• 0067a92b Fix documentation style and add See Also links
• 9b13b2f3 Add BM8563 time component documentation
• 7700eb02 Initial plan

All are based on: 547c4b2 (next) [remote_transmitter] Add non-blocking mode (esphome#5525)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[abmantis]

@copilot esphome/esphome#11616 changed so that it now referes to timer value instead of sleep duration. Update the docs in this PR to match.

[Copilot]

@copilot esphome/esphome#11616 changed so that it now referes to timer value instead of sleep duration. Update the docs in this PR to match.

Updated the documentation to match the changes in esphome/esphome#11616. Changed:

• Configuration variable: sleep_duration → timer_value
• Action name: bm8563.apply_sleep_duration → bm8563.start_timer
• Anchor: bm8563-apply_sleep_duration_action → bm8563-start_timer_action
• Action description updated to "starts the RTC timer"

Commit: b7af2ea

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[abmantis]

@copilot the icon is not showing up. fix it

[Copilot]

@copilot the icon is not showing up. fix it

Fixed in commit 6e07790. The icon reference was missing the .svg extension in the components index.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[abmantis]

@copilot describe the config options for the start_timer action. Look at the deep_sleep component one for the format.

[Copilot]

@copilot describe the config options for the start_timer action. Look at the deep_sleep component one for the format.

Added configuration options section for the start_timer action in commit 56f12fd, following the format used in the deep_sleep component documentation.

The action now documents:

• timer_value (Required): The time duration for the timer
• id (Optional): Manually specify the BM8563 component ID if you have multiple components

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• data.esphome.io
  • Triggering command: curl -s -S REDACTED (dns block)
• https://api.github.com/repos/esphome/esphome/pulls/11616
  • Triggering command: curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[abmantis]

@copilot the source PR changed to remove the timer_value from the component config. Update the docs.

[Copilot]

@copilot the source PR changed to remove the timer_value from the component config. Update the docs.

Removed timer_value from the component configuration variables in commit 30024ea. The timer_value is now only documented as a parameter for the bm8563.start_timer action, which is where it's actually used.