-
Notifications
You must be signed in to change notification settings - Fork 17
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
Error with 2023.7.1 #215
Comments
Same issue here. |
Same issue as well. |
Just updated to 2023.7.1 and experiencing the same issue |
I tried a rudamental fix of this but couldn't work it out. Not clear to me if it's a core bug or multiscrape but leaning towards a multiscrape issue. |
I think you are lacking service descriptions. It does look like a core regression. But may be a bit hard to report since it's a custom integration triggering it. |
same here |
1 similar comment
same here |
same here with 2023.7.1 |
same here - after downgrade to my last working core 2023.6.3 it works |
same here with 2023.7.1 |
same here after HA core 2023.7.1 update |
It looks like async_set_service_schema is being called with a different service name than what is actually be registered |
Rollback to 2023.7.0 does solve the issue. home-assistant/core#95911 was in 2023.7.1, so might very likely be the reason for this failing now, as @elupus said. |
Indeed: issue is not core, issue is here:
Unclear why this didnt crash before. |
Thanks @bdraco, you were right. Fixed in v6.7.1! |
Can confirm 6.7.1 is working. |
Confirming the same, HA 2023.7.1 and Multiscrape 6.7.1 work nicely now. Thanks for the quick fixes by all involved! |
Fixed by 683d63f |
i not received any error with 2023.7.0, but with 2023.7.1 i see:
The text was updated successfully, but these errors were encountered: