RuntimeError: Detected that custom integration 'alexa_media' calls async_write_ha_state #2256
Comments
|
``hi, Worse than that, today I discovered my HomeAssistant has filled to 100% the disk by writing this kind of messages to the log: not sure if the the WARNING messages about SSL and socket exceptions are related to this integration though, just mentioning. |
alandtse
added
bug
|
Thanks for reporting. |
alandtse
changed the title
|
I think my issue is related. Yesterday evening, my RPI-based with SSD, HAOS system crashed. I tried rebooting several times and could not access it at all. Finally I could ping it, but still couldn't access HAOS. Eventually, about 10 min later it suddenly came up. About 10min later the same thing happened again. Multiple reboots later, and waiting even longer, and HAOS came up again. The only CORE errors relate to alexa_media. See 3 errors below. Then further below I pasted the Supervisor log, which while it doesn't have any errors appears to suggest (looking at the time stamps and repeated processes) that it restarted on its own a few times in the middle of the night/early morning. I'm on HAOS 12.3, Core 2024.5.3 I received the following error messages: Error doing job: Future exception was never retrieved I bit later: Logger: alexapy.alexaapi Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests) And a bit later: Logger: custom_components.alexa_media Error fetching alexa_media data: Error communicating with API: Too Many Requests And here are the Supervisor logs Thanks for any help. |
|
If someone wants to work on this, the docs are here: https://developers.home-assistant.io/docs/asyncio_thread_safety#hassbusasync_fire https://developers.home-assistant.io/docs/asyncio_thread_safety#async_write_ha_state |
|
Same here i think. Logger: homeassistant.util.logging Exception in _handle_event when dispatching 'alexa_media_t*m@f***********t': ({'queue_state': {'dopplerId': {'deviceSerialNumber': 'G090LF1181340N1J', 'deviceType': 'A3S5BH2HU6VAYF'}, 'changeType': 'NEW_QUEUE', 'playBackOrder': 'NORMAL', 'loopMode': 'NORMAL', 'trackOrderChanged': False, 'destinationUserId': 'A2CE33QXLYXM29'}},) Traceback (most recent call last): File "/config/custom_components/alexa_media/switch.py", line 217, in _handle_event self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1008, in async_write_ha_state self.hass.verify_event_loop_thread("async_write_ha_state") File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread frame.report( File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report _report_integration(what, integration_frame, level, error_if_integration) File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration raise RuntimeError( RuntimeError: Detected that custom integration 'alexa_media' calls async_write_ha_state from a thread at custom_components/alexa_media/switch.py, line 217: self.async_write_ha_state(). Please report it to the author of the 'alexa_media' custom integration. ———————————————————————- Logger: homeassistant.helpers.frame Detected that custom integration 'alexa_media' calls async_write_ha_state from a thread at custom_components/alexa_media/switch.py, line 217: self.async_write_ha_state(), please report it to the author of the 'alexa_media' custom integration |
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
Received this error today, not sure what caused it, I just found it in the logs. I am not aware of anything failing. I have only just updated HA and the integration to latest levels (yesterday).
To Reproduce
Cannot reproduce.
Expected behavior
Screenshots
System details
const.pyor HA startup): 4.10.0pip show alexapyor HA startup): 1.27.10Logs
Please provide logs.
Additional context
The text was updated successfully, but these errors were encountered: