Open ZhuDaHai opened 1 month 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)
The problem
As of Core 2024.8.0 we are being told the WorldClock yaml configuration is being deprecated and settings have been migrated to the Worldclock Integration.
However, the Worldclock integration is severely lacking in its functionality. While setting a New Worldclock entry, you are able to Name it, set the timezone, and set the time format:![image](https://github.com/user-attachments/assets/19846acd-3641-4ed2-ba21-7f0482dbc416)
However, once created, you cannot change, or even view, the timezone. (So what is it? timezone, or time_zone? It's displayed two different ways in HA)
Apparently, the only way to change it is to delete and re-create, or edit it in ./storage/core.config.entries Which IMO is really a bad idea (and dangerous) and totally negates the purpose of a UI for this Integration.
I'm hoping this gets address before configuration.yaml / worldclock: integration is totally disabled in Core 2025.2.0, but IMO this should have been taken care of before a Deprecation Statement was issued.
Thank you.
What version of Home Assistant Core has the issue?
2024.9.0
What was the last working version of Home Assistant Core?
Never, so I never used the UI Integration for WorldClock
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 diagnostics, just bad UI design
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
Thank you for your time and attention.