home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.43k stars 30.67k forks source link

Connection Expires #123228

Open bockstone opened 3 months ago

bockstone commented 3 months ago

The problem

After an X period of time new incidents will not appear in HA, I need to delete the integration and login again to reconnect. I found an error in my logs that appeared a 3 times now, all 3 times I had to relogg and it was working again.

What version of Home Assistant Core has the issue?

core-2024.6.3

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

fireservicerota

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fireservicerota/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.config_entries
Source: config_entries.py:809
First occurred: July 22, 2024 at 10:51:09 AM (2 occurrences)
Last logged: August 5, 2024 at 7:39:01 PM

Error unloading entry *EMAIL* for fireservicerota
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 809, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/fireservicerota/__init__.py", line 70, in async_unload_entry
    hass.data[DOMAIN][entry.entry_id].websocket.stop_listener
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'dict' object has no attribute 'websocket'

Additional information

No response

home-assistant[bot] commented 3 months ago

Hey there @cyberjunky, mind taking a look at this issue as it has been labeled with an integration (fireservicerota) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `fireservicerota` 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 fireservicerota` 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)


fireservicerota documentation fireservicerota source (message by IssueLinks)

benna1990 commented 2 months ago

I'm experiencing the same issue with the fireservicerota integration on Home Assistant Core version core-2024.7.4. After a certain period of time, new incidents stop appearing in HA, and the only workaround I've found is to delete the integration and log in again.

Gerbenz commented 1 month ago

Im having the same issue.

Im trying to delete and reinstall. but i cant really find a uninstall button. Can someone help me?

if i delete my account all entities disappear, and the integration disappears aswell. but i dont think the integration actually gets deleted.

Gerbenz commented 1 month ago

I've now deleted and readded the integration several times, but the incident sensor is not updating. It still shows the last incident of last week, but several have happend since then. Any help?

BombaNL commented 1 week ago

Same problem here.

The only thing that works is to remove the integration. HA restart and reinstall the integration and log in. The automation then works again without having to adjust anything.

HA version 2024.10.4

cyberjunky commented 5 days ago

I will have a look shortly, the fact that you need to remove and add again surprises me to be honest. I think i saw a cannot close websocket error (wrong call) in the logs, not sure if this is related. I also need to check if my brandweerrooster test account is still functional.

Gerbenz commented 5 days ago

It was working again for a few weeks. The new incident from yesterday does not show up however. The probleem seem to be back.