Skip to content

Improve troubleshooting links in FRITZ!Tools #42367

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.

Sign up for GitHub

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
c0ffeeca7 merged 1 commit into from
Dec 9, 2025
Merged

Improve troubleshooting links in FRITZ!Tools #42367

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/_integrations/fritz.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ automation:

## Troubleshooting

In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue re-occurs stop the debug logging again (_download of debug log file will start automatically_). Further _if still possible_, please also download the {% term diagnostics %} data. If you have collected the debug log and the diagnostics data, provide them with the issue report.
In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#enabling-debug-logging), restart the integration, and as soon as the issue re-occurs stop the debug logging again (_download of debug log file will start automatically_). Further _if still possible_, please also download the [diagnostics data](/docs/configuration/troubleshooting/#download-diagnostics). If you have collected the debug log and the diagnostics data, provide them with the issue report.
Copy link

Copilot AI Dec 7, 2025

Choose a reason for hiding this comment

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

The change removes the use of the glossary term {% term diagnostics %} and replaces it with a regular link [diagnostics data](/docs/configuration/troubleshooting/#download-diagnostics). According to the documentation guidelines, glossary term references should be used when appropriate as they provide tooltips with term definitions for better user experience.

Additionally, most other integration files use a more common pattern:

  • For debug logging: /docs/configuration/troubleshooting/#debug-logs-and-diagnostics
  • For diagnostics: either [diagnostics](/integrations/diagnostics) or {% term diagnostics %}

Consider using one of these established patterns for consistency with the rest of the documentation. For example:

In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue re-occurs stop the debug logging again (_download of debug log file will start automatically_). Further _if still possible_, please also download the {% term diagnostics %} data. If you have collected the debug log and the diagnostics data, provide them with the issue report.

Copilot generated this review using guidance from repository custom instructions.

### Device presence detection is not working as expected

Expand Down