Same behavior in Firefox for me. It works in Chrome, but we all know Firefox is better
3 Likes
sparkydave
(đŠđș Dave)
March 10, 2024, 11:49pm
189
One of my 4 todo lists has done this as well.
opened 08:10PM - 07 Mar 24 UTC
integration: local_todo
### The problem
Using Local To Do list integration. Created a new To Do list⊠item, then I edited it to add a description; once I tried to save it (& I DID NOT specify a due date or time), I then received this error, which was also posted to syslog: "No timezone information available for event: {key}". I could NOT save the To Do item & discovered that I could start new items, but could not edit them. But... I was able to edit items that had been previously created. Just can't edit any new items.
### What version of Home Assistant Core has the issue?
core-core-2024.3.0
### What was the last working version of Home Assistant Core?
core-core-2024.2.5
### What type of installation are you running?
Home Assistant Supervised
### Integration causing the issue
Local To-do
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/local_todo
### Diagnostics information
Attempted the above several times and kept getting the error. Checked my 'timezone' and it was correct:
(GMT-06:00) Central Time. I attempted to enter a due date and time, but still got the error. I was not able to save the To Do item so this basically means I cannot create any new To Do list items. NOTE: I was able to successfully edit and modify existing To Do items. Just not create any new ones. I have two To Do lists & and I could not create new items in either list.
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:239
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 1:40:31 PM (5 occurrences)
Last logged: 1:54:47 PM
[547421976384] No timezone information available for event: {key}
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/ical/store.py", line 64, in _ensure_timezone
return Timezone.from_tzif(key)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/timezone.py", line 166, in from_tzif
info = timezoneinfo.read(key)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/tzif/timezoneinfo.py", line 69, in read
raise TimezoneInfoError(f"Unable to find timezone in system timezones: {key}")
ical.tzif.timezoneinfo.TimezoneInfoError: Unable to find timezone in system timezones: CST
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 239, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2319, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2356, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 905, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 975, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/todo/__init__.py", line 511, in _async_update_todo_item
await entity.async_update_todo_item(item=TodoItem(**updated_data))
File "/usr/src/homeassistant/homeassistant/components/local_todo/todo.py", line 157, in async_update_todo_item
TodoStore(self._calendar).edit(todo.uid, todo)
File "/usr/local/lib/python3.12/site-packages/ical/store.py", line 319, in edit
self._apply_edit(
File "/usr/local/lib/python3.12/site-packages/ical/store.py", line 379, in _apply_edit
self._ensure_timezone(new_item.dtstart)
File "/usr/local/lib/python3.12/site-packages/ical/store.py", line 394, in _ensure_timezone
if (new_timezone := _ensure_timezone(dtstart, self._timezones)) is not None:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/store.py", line 66, in _ensure_timezone
raise EventStoreError(
ical.exceptions.EventStoreError: No timezone information available for event: {key}
```
### Additional information
I had forgotten to mention that I had also restarted HA and tested again. Same result.
allenporter:main
â allenporter:dev
opened 04:19PM - 10 Mar 24 UTC
Update the todo validation logic to perform repairs to get objects to be in an i⊠nvalid state. Previous the TodoStore would allow todos to have dates that flex independently of the dtstart, so they can get mismatched resulting in validation errors. Now they are repaired automatically, moving the dtstart to be valid.
Todo store updates now perform validation.
https://github.com/home-assistant/core/issues/112647
1 Like
Not sure what you mean. Can you provide more info?
I updated to 2024.3 and created a new tab on my dashboard using the beta. Now nothing syncs to my mobile app in iOS regardless of how much time has passed. Is it recommended to delete the beta tab for now?
Quick update. I deleted the new Experimental view and HA now syncs again with the app. The issue I was having is NOTHING in HA was syncing while this view was active.
pdwonline
(When a goat is on the net)
March 11, 2024, 6:43pm
194
Custom number box elemens doesnât work anymore and min-max is finally removed now
Works in my setup. Suggest to create an issue in a corr. repo if this cannot be fixed by reinstalling the card/purging cache/HA reboot/buying a new pc/etc.
tom_l
March 11, 2024, 9:43pm
196
Not sure what you mean by this either:
pdwonline
(When a goat is on the net)
March 12, 2024, 6:30am
197
I meant that the Min/Max integration has been moved to groups. and in this release finally removed without mentioning in the release notes.
My other issue seems because my HACS is version 1.34 and wouldânt update.
Unclear, see a screenshot above; how a helper could be âmoved to groupsâ?
1 Like
Nerdix
March 12, 2024, 11:09am
199
I assume you are mixing things up. You are using sensor groups (Group - Home Assistant ) which is not the same as a min/max sensorâŠ
patrix487
(Patrix487)
March 12, 2024, 11:38am
200
Dear lovely community, iâm running home-assistant on the truecharts app and iâm currently on: Core: 2024.3.0
Frontend: 20240306.0
is there a reason why the buttons in the header donât show status on with colors? apparently theyâre still working but they donât change yellow when i press them. can somebody tell me whatâs going on? Couldnât find anything on google (or maybe bad prompt?) related to that issue. i tested it on another card and the only thing that happens is that the automation icon gets âcrossed outâ but no color change.
You need state_color: true
aligned with entities:
1 Like
To see yellow colors, you need to specify âstate_color: trueâ, but for buttons it was broken in 2024.3. See a registered issue .
1 Like
snikay
(emka)
March 12, 2024, 11:57am
203
just as always: buggy as hell.
for me, there is no new drag-and-drop
is there a special g-point i have to trigger HomeAssistant with to activate drag-and-drop? or should i just wait, as always, for you guys to fix the bugs?
arganto
March 12, 2024, 11:58am
204
You can just read the release docs and see where drag&drop is and how to activate it.
2 Likes
snikay
(emka)
March 12, 2024, 12:02pm
205
there is nothing writting on section âDrag-and-drop rearrangement of cards and sections!â on how to activate it.
for Sections (experimental) there is a small hint how to activate. does it also includes drag and drop? who knowsâŠ
seems to be pretty hard to write such small blog post correctly.
This is just brilliant. Keep on, but better in some other place.
9 Likes
snikay
(emka)
March 12, 2024, 12:07pm
207
yep. itâs just like that.
there is nothing writting on âdrag and dropâ, but the actual hint on how to activate it, is in the section before that " A new experimental sections view" , which makes nothing to zero sense.
to HA team: many people donât have the time to read every single line in your blogs, nor do we want to fiddle around to see where stuff is hiding.
itâs experimental, okay⊠but why not have this in beta then? usually this is how experimental features are supposed to be rolled out.
in stable, i would expect ⊠well ⊠stable features? not âexperimentalâ things hiding in the closet and people wondering where it is.
but maybe iâm old fashioned