Open ebonzl opened 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!
(message by CodeOwnersMention)
worldclock documentation worldclock source (message by IssueLinks)
Detail from the logbook for reference: Dubai changed to Tue, Aug 20, 2024 06:17 AM 14:17:10 - 18 seconds ago Las Vegas changed to Mon, Aug 19, 2024 07:17 PM 14:17:10 - 18 seconds ago Guernsey changed to Tue, Aug 20, 2024 03:17 AM 14:17:10 - 18 seconds ago
I just started using this integration and noticed this also. It seems like perhaps this is intended, and that it is expected that you exclude it from the logbook if you don't want it logged. i.e. home-assistant/core#73190 https://www.home-assistant.io/integrations/logbook/#exclude
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