-
Notifications
You must be signed in to change notification settings - Fork 30
Description
Since yesterday, I noticed that no events were being triggered in HA. After investigating, I found an error message in the log:
"Error retrieving messages: {'reason': 'no_event_received'}"
which caused a crash. A bit more detail:
2026-01-23 16:36:34.754 ERROR (MainThread) [custom_components.meshcore.coordinator] Error retrieving messages: {'reason': 'no_event_received'}
2026-01-23 16:36:54.754 ERROR (MainThread) [custom_components.meshcore] Failed to get self telemetry: {'reason': 'no_event_received'}
2026-01-23 16:36:59.757 ERROR (MainThread) [custom_components.meshcore.coordinator] Error retrieving messages: {'reason': 'no_event_received'}....
A restart fixes the problem for a few minutes before it starts again. Has anyone else experienced this?
To this end, the HA has been working well with Meshcore for weeks. A traceback indicates the following:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/logging/handlers.py", line 1509, in emit
self.enqueue(self.prepare(record))
File "/usr/local/lib/python3.13/logging/handlers.py", line 1491, in prepare
msg = self.format(record)
File "/usr/local/lib/python3.13/logging/__init__.py", line 999, in format
return fmt.format(record)
~~~~~~~~~~^^^^^^^^
File "/usr/local/lib/python3.13/logging/__init__.py", line 712, in format
record.message = record.getMessage()
~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/logging/__init__.py", line 400, in getMessage
msg = msg % self.args
~~~~^~~~~~~~~~~
Could it be that a corrupt string is being received?
Thanks!