What am I missing here?
Now that World Clock is being forced to the Integrations UI, how to do change the timezone of an existing service/entity?
Even if you create a new Entry, which allows you to set the timezone, after that you cannot change the timezone (or even see what it’s set too) - or at least I can’t find it.
Help?
To change the timezone, you’d have to delete the entity and create a new one. It appears all you can do is change the format of the sensor.
I do not use this integration but I did just create a sensor to see what I could find out. I agree it is poorly implemented; the default name of the sensor isn’t based off the timezone selected (it is set to sensor.worldclock_sensor
) so you will want to rename it. And there is no way to determine what timezone the sensor is based off, from within the UI.
If you really need to find out, you can open up the core.config_entries
file in the \config\.storage
folder and search for the entity name.
You’ll see an entry like this:
{
"created_at": "2024-08-08T03:48:16.728894+00:00",
"data": {},
"disabled_by": null,
"domain": "worldclock",
"entry_id": "01J4R1M0PRZJ3DJJ07VT2FQRCV",
"minor_version": 1,
"modified_at": "2024-08-08T03:48:16.728899+00:00",
"options": {
"name": "Worldclock Sensor",
"time_zone": "Europe/Brussels",
"time_format": "%Y-%m-%d %H:%M"
},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"title": "Worldclock Sensor",
"unique_id": null,
"version": 1
}
At the very least this integration should create some attributes to the sensor so we can see what it was set up to do. Even better would be if one of those attributes was a python datetime object that was timezone aware so it contains a tzinfo
object (like what is done with the time zone sensor custom component)
Thank you for the reply. Glad I’m not losing my mind. I’ll post the Issue in Core and maybe someone will run with it.
Thanks again!