-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unexpected error fetching omnik_inverter data: coroutine ignored GeneratorExit #116
Unexpected error fetching omnik_inverter data: coroutine ignored GeneratorExit #116
Comments
I was able to mitigate it by adding |
I've also seen this Perhaps this workaround makes the @klaasnicolaas pointed out that this is also done for the other (JS/HTML) data sources: We should probably quickly release a followup that adds this to the TCP backend, but I'd like to get the conversion from poll to push over with sooner rather than later (where this is handled differently or not at all). Thanks for testing out the new TCP backend though! While I don't like it, it's technically still early days and bugs have to be fully ironed out 🤞 |
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
This mitigation is now up in klaasnicolaas/python-omnikinverter#207, still unsure where the error is coming from... Fwiw the HTML/JS code re-wraps this exception as |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
Is there a fix for this actually applied? I'm running HA 2023.2 and still getting this same error (149 times since installing 2023.2 yesterday). |
Nope. |
Fair enough! |
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
There have recently been [reports of `RuntimeError: coroutine ignored GeneratorExit`] which are presumably triggered by timeouts on the socket, without being raised as `TimeoutError`. This case seems to be mitigated by timing out the request after a default of 10 seconds which doesn't give `GeneratorExit` - triggered by something yet unknown - enough time to surface. [reports of `RuntimeError: coroutine ignored GeneratorExit`]: robbinjanssen/home-assistant-omnik-inverter#116
I get this error every now and then since switching to TCP mode for my Omnik 3000TL:
The text was updated successfully, but these errors were encountered: