-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Fault by pysolarman #420
Comments
Could you try to catch this w/ debug logging enabled, please? Thanks! |
I'll do it too, even if it won't be an easy trace. |
Her the log Dieser Fehler stammt von einer benutzerdefinierten Integration Logger: homeassistant Error doing job: Task exception was never retrieved (None) Dieser Fehler stammt von einer benutzerdefinierten Integration Logger: custom_components.solarman.pysolarman.pysolarman [3907049102] Write error: Connection lost |
Description
Hey David,
Today with the New Skript i become this error some times
Dieser Fehler stammt von einer benutzerdefinierten Integration
Logger: homeassistant
Quelle: custom_components/solarman/pysolarman/pysolarman.py:169
Integration: Solarman (Dokumentation, Probleme)
Erstmals aufgetreten: 17:27:51 (1 Vorkommnisse)
Zuletzt protokolliert: 17:27:51
Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/config/custom_components/solarman/pysolarman/pysolarman.py", line 169, in _conn_keeper
data = await self.reader.read(1024)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/streams.py", line 730, in read
await self._wait_for_data('read')
File "/usr/local/lib/python3.13/asyncio/streams.py", line 525, in _wait_for_data
raise RuntimeError(
f'{func_name}() called while another coroutine is '
f'already waiting for incoming data')
RuntimeError: read() called while another coroutine is already waiting for incoming data
Reproduction Steps
No idee for steps
Log
No log
Version
25.02.14
Home Assistant Core Version
2025.2.1 up .4
Home Assistant Operating System Version
14.2
The text was updated successfully, but these errors were encountered: