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
integration calling async_dispatcher_connect
with None
#111797
Comments
I guess we could add a guard for that so it blows up so we can find it |
I wonder if its actually be unloaded out from under it instead... hard to tell on this one |
It seems to me that |
Maybe a CC is using it? @Anto79-ops are you still seeing this on the latest beta? |
For my part, I can say that I still see it on b3. Will try booting in safe mode later. |
Yes, I'm still seeing on b3. |
When I start in safe mode, I no longer see this message. So this is more likely to be caused by a CC. |
@Anto79-ops Do you use Spook? |
Yea, it is Spook. Found it, will create a PR for it. |
frenck/spook#647 should fix this, applied this to my prod and the log disappeared |
~~Do you mind listing your CCs? I have dyson, spook, spook inverse, node red, hass agent, hacs, extended openai, nest protect, and gas buddy.~~ Oh never mind, you found it and yes, i have spook....for some reason github didn't show the previous messages until I posted . Thank you! |
You could try disable Spook, restart and see if the log messages disappear to confirm |
thanks @jpbede |
I'm going to close this one. Please continue at frenck/spook#647 |
Thanks all. |
The problem
hello,
updating to 2024.3.0b0 and these logs appear several times:
CC @bd
What version of Home Assistant Core has the issue?
2024.3.0b0
What was the last working version of Home Assistant Core?
2024.2.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: