-
Notifications
You must be signed in to change notification settings - Fork 70
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
Home Assistant Core 2023.5 breaks integration #157
Comments
see #155 duplicate plz close |
I have the same! Any idea - how can I delete the integration? |
Not entirely. I additionally informed, that I am unable to remove the integration. |
Same here. I renamed and labeled many sensors. So I have to do that all again !?! I would very much like a fix for anyone using this integration ! |
same here. Error doing job: Task exception was never retrieved The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Same here, I removed it and when I try to add the integration again, I get: Config flow could not be loaded: {"message":"Invalid handler specified"} Error log: |
Same and I am not able to remove this integration 😔 |
|
you can try my fork it is still working in 2023.5 I haven't tried it myself but have been meaning too |
I can't get the official integration to work. Never had problems with the HACS one and the whole webhook thing has me puzzled as to why it is needed. |
I gave up with the official integration and reverted back to HACS as the official integration doesn't support Official Home Assistant Hardware / OS. |
Same thing here. The official integration requires all kinds of reverse proxy if you use https and offers nothing that is not in the HACS version. |
Yeah, I guess getting the integration into the core adds more requirements, like maybe not using private listening ports. Anyway, I put in a feature request that would solve the problem. And I have a workaround for using the new core integration. Probably a way to do it with Python also. |
From what I read the core version also used private listening ports.
…On Wed, 14 Jun 2023 at 01:04, rbauman70 ***@***.***> wrote:
Yeah, I guess getting the integration into the core adds more
requirements, like maybe not using private listening ports. Anyway, I put
in a feature request
<https://community.home-assistant.io/t/add-webhook-support-on-non-ssl-port-for-integrations/579725>
that would solve the problem. And I have a workaround
<#154> for using
the new core integration. Probably a way to do it with Python also.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALJQCYNJEWUSXBPHNTSDX3XLB6OLANCNFSM6AAAAAAXYX4YPM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Since we seem to have lost the author's support, maybe we can revert the core's implementation back to the private port method then? Can you merge your fork? |
This Worked for me, only need to change 2 lines in the .py of ecowitt and works. |
When upgrading from 2023.4.X to 2023.5.X, the integration does no longer load. Error message:
It is impossible to delete the integration (in my case nothing happens an the integration just stays "active"). So the repository can't be removed.
Possebly relatet log-entrys:
My device:
WS2900_V2.01.18
von ecowitt
Firmware: EasyWeatherV1.6.4
The text was updated successfully, but these errors were encountered: