home-assistant[bot]
commented
2 months ago Hey there @fabaff, mind taking a look at this issue as it has been labeled with an integration (worldclock) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `worldclock` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign worldclock` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
worldclock documentation worldclock source (message by IssueLinks)
ebonzl
pfeerick
The problem
This seems unecessary, as this clogs up the logbook with entries especially if you have many world clock time zones configured - I guess a workaround is to create an entry can be manually added to the configuration.yaml to exclude these entities. but would be good if they did not log time changes by default
What version of Home Assistant Core has the issue?
core-2024.8.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Worldclock
Link to integration documentation on our website
https://www.home-assistant.io/integrations/worldclock
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response