fail to load in beta 2023.5.b0

[scooper1]

Logger: homeassistant.setup
Source: setup.py:214
First occurred: 01:25:09 (1 occurrences)
Last logged: 01:25:09

Setup failed for custom integration ecowitt: Unable to import component: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

[Homeassistjoenka]

We have also, the same problem #
/

[scooper1]

in the end removed the HACS version and used the standard included version

[Homeassistjoenka]

Where? dear its nothing standaard we see not

[dennidoubles]

@scooper1 , "the standard included version" ... ?
Where do I find this? I don't see any, when I look for the integration Ecowitt? Could you help us out please

[scooper1]

Remove from integrations
Remove from hacs
Reboot
Add to integrations It uses same name but this time you get a message to add a web hook to the ecowit
Edit custom on ecowit with new web hook
I reboot ha again to load integration

For me this worked and used original entries

[rodgrech]

carrying on from this, has anyone had issues with removing the intergration? i attempt to remove it but it doesnt delete

get Error occurred loading flow for integration ecowitt: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

[phurth]

carrying on from this, has anyone had issues with removing the intergration? i attempt to remove it but it doesnt delete

get Error occurred loading flow for integration ecowitt: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

Same issue here. HA 2023.5 (not beta). Can't delete the integration.

[johnnykang]

is there any suggestion to remove the integration manually since the remove button doesn't work?

[GSzabados]

any suggestion

Go back to 2023.4.X remove the integration there, add the built in and update to 2023.5. But the changes in HA for Alexa and Google will mess up other things probably....

[johnnykang]

any suggestion

Go back to 2023.4.X remove the integration there, add the built in and update to 2023.5. But the changes in HA for Alexa and Google will mess up other things probably....

yeah. i am restoring the backup to previous version right now. :(

[BartGysens]

Hi everyone, since my update last night to core_2023.4.5 HassIO, several add-ons/integrations (EcoFlow, OpenmediaVault, GoogleNest, localtuya) broke with this message, ex. OMV:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/openmediavault/init.py", line 37, in async_setup_entry
hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'

Restored backup

[Remko76]

Doesnt work for me. I removed everything, redownloaded the 0.7 version of the integration, but cannot set it up under integrations. It gives me the message "Config flow could not be loaded: {"message: "Invalid Handler specified"}

Redownloading the 0.6 version of the integration works then.

add the built in

What do you mean with this? Download the integration through HACS again.....?

[iculookn]

Here is the official integration
https://www.home-assistant.io/integrations/ecowitt/

I far as I understand. this HACS version is no longer maintained.

[lobolobo]

Some way to migrate from custom components integration to core one in ha?

[nady2804]

Please can anybody describe the whole procedure for the Ecowitt integration change.
I think there are many users they use the HACS custom integrattion.
I mean the deinstall / reinstall process because i delete the integration ecowitt then i delete the custom repository in HACS.
Reboot and go to Integrations and see the Ecowitt click on it and got the error: Config flow could not be loaded: {"message: "Invalid Handler specified"}

So what is wrong please?

Thx Manfred

[darlezior]

Hi, i just went back to 4.6, I unistalled the custom one and installed the official ecowitt integration. The issue is that it doesn't get any entity... what should i do? thanks

[t3lmoazevedo]

The core official component Ecowitt doesn’t support TLS/SSL so the configuration with webhocks doesnt work for mosts setup with external HTTPS access.
Is there a way to fix this custom integration to be able to keep using it?

[mathep34]

Solution that works for me
(Offical Core ecowitt not working due to TLS/SSL restriction)

1. disable integration
2. reboot HA
3. stop HA
4. delete folder ( /config/custom_components/ecowitt) (backup is your friend)
5. start HA
6. install ecowitt addon 0.6 (not 0.7)
7. reboot HA

everything works while waiting for a fix...

[dennidoubles]

Solution that works for me (Offical Core ecowitt not working due to TLS/SSL restriction)

1. disable integration
2. reboot HA
3. stop HA
4. delete folder ( /config/custom_components/ecowitt) (backup is your friend)
5. start HA
6. install ecowitt addon 0.6 (not 0.7)
7. reboot HA

everything works while waiting for a fix...

Sounds great! But...for my knowledge:
How do I delete that folder, whilst HA has been stopped then?

Many thanks

[silfax]

Solution that works for me (Offical Core ecowitt not working due to TLS/SSL restriction)

1. disable integration
2. reboot HA
3. stop HA
4. delete folder ( /config/custom_components/ecowitt) (backup is your friend)
5. start HA
6. install ecowitt addon 0.6 (not 0.7)
7. reboot HA

everything works while waiting for a fix...

It worked for me just by using the "redownload" option in HACS and selecting version 0.6. No need to uninstall.

[mathep34]

delete with a ssh session or winscp
(return on 0.6 from 0.7 don't work for me)

[pvizeli]

Running an unsupported integration is not a fix, just a temporary solution until next thing change because of HA or Ecowitt firmware

[silfax]

It's a workaround. Better than no fix. And for me at least looks simpler than:

[dennidoubles]

Strange...I did all the needed steps:

Removed from integrations
Removed from hacs
Rebooted HA
Added to integrations and added the webhook path into the ecowitt app
Rebooted ha again to load integration, integration is there.
But it is disabled by config entry and I don't have the possibility to just enable it.

Anyone?

[t3lmoazevedo]

Solution that works for me (Offical Core ecowitt not working due to TLS/SSL restriction)

Perfect, its working again. Thanks

[dennidoubles]

Nevermind. Deleted the ingeration, installed with a new webhook and now it is working again.

[nady2804]

Added to integrations and added the webhook path into the ecowitt app

What do you mean with: Added to integrations and added the webhook path into the ecowitt app ??
thx

[kisjeth]

Is there no one who can help me? I have Cloud Nabu active and therefore I am connected in TSL/SSL. how do i solve it?

[lobolobo]

Another solution form the forum:
https://community.home-assistant.io/t/2023-5-lets-talk/567331/155
And actually there are 4 PRs with the same fix....

"So I was able to get mine working… again. I wish there was a clean way to migrate integrations, but that’s what I get for HACS.
I have a verified Ecowitt HACS integration. This is how I did it. -Using HA file editor, go to “/config/custom_components/ecowitt/” -Download “init.py” -Edit line 21 to " async_get as async_get_entity_registry," -Save file. -In HA file editor, upload file, overwrite existing one. -Reboot. -Update to 2023.5 -Profit.
Good luck all! "
It worked for me :-)

Thanks, that helped! I tried the official one, but it never found any device/entities.

Same here, exactly the same ...

[gferen]

here is what happens when i try add oficial Ecowit

2023-05-06 12:32:52.203 ERROR (MainThread) [aiohttp.server] Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle resp = await handler(request) File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle result = await result File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper result = await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 271, in async_configure result = await self._async_handle_step( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step result: FlowResult = await getattr(flow, method)(user_input) File "/usr/src/homeassistant/homeassistant/components/ecowitt/config_flow.py", line 35, in async_step_user base_url = URL(get_url(self.hass)) File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 200, in get_url raise NoURLAvailableError homeassistant.helpers.network.NoURLAvailableError 2023-05-06 12:32:55.933 ERROR (MainThread) [aiohttp.server] Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle resp = await handler(request) File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle result = await result File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper result = await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 271, in async_configure result = await self._async_handle_step( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step result: FlowResult = await getattr(flow, method)(user_input) File "/usr/src/homeassistant/homeassistant/components/ecowitt/config_flow.py", line 35, in async_step_user base_url = URL(get_url(self.hass)) File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 200, in get_url raise NoURLAvailableError homeassistant.helpers.network.NoURLAvailableError

[lobolobo]

I tried the official one, but it never found any device/entities.

When i tried the official Ecowitt integration (having uninstalled the one from hacs previously), it never found any device or entities.

[Remko76]

You also need to change the settings in the app of the weather station. It worked for me.
I now went a complete different way by using ecowitt2mqtt from here:
https://github.com/bachya/ecowitt2mqtt

[Homeassistjoenka]

You follow this steps? In the ecowitt app? En you have the api out the intergratie app??

[ChrisDHughes]

I got mine working again by doing the following...

1. Rolled back HA Core to 2023.4.5 (using System | Backups, although there are other ways).
2. Checked the HACS Ecowitt Integration was version was on 0.7
3. Removed the HA Ecowitt Integration.
4. Added it again (setting the Listening Port to 4199).
5. Opened the Ecowitt Android app (... | Others | DIY Upload Servers | Customized). Set the Host Name to my HA IP Address, set the path as just forward slash /, port as 4199. Clicked Save.
6. Restarted HA.

I won't be going to HA Core 2023.5.x until someone can tell me how to do that without screwing up the Ecowitt config. I tried all the other methods described above without any luck.

[sat-fan2019]

I am confused with the different solutions here. which one works without going back to 2023.4 ?
I already have 2023.5.2
which is the right source (hacs or direct) and what should I do than. Thx !

[RJ-Make]

I am confused with the different solutions here. which one works without going back to 2023.4 ? I already have 2023.5.2 which is the right source (hacs or direct) and what should I do than. Thx !

IMO, the correct choice is to use the HA Integration version as the OG (HACS) version is no longer maintained. I think the problem is some updated HA to .5 before removing the OG version and then it became orphaned, which is apparently difficult to removed at that point.

This is what I did

1. While on HA .4.6, I copied the entity list for Ecowitt.
2. Completely removed the OG (HACS) Ecowitt app.
3. Restarted HA
4. Installed the Ecowitt HA Integration and setup via the instructions provided.
5. Adjusted naming where necessary in HA using my step 1 copy.

[mortenx]

Solution :
Using HA file editor, go to “/config/custom_components/ecowitt/”
Edit line 21 to " async_get as async_get_entity_registry,"
Save file.

[sat-fan2019]

Solution : Using HA file editor, go to “/config/custom_components/ecowitt/” Edit line 21 to " async_get as async_get_entity_registry," Save file.

with the hacs or the direct installation ?

[jacobchurch]

Solution : Using HA file editor, go to “/config/custom_components/ecowitt/” Edit line 21 to " async_get as async_get_entity_registry," Save file.

with the hacs or the direct installation ?

hacs

[gferen]

i solved this with latest HA, Hacks Ecowittg 0.7 version and “/config/custom_components/ecowitt/” Edit line 21 to " async_get as async_get_entity_registry,"
Official integration seems broken in my eyes.

[Remko76]

Official integration works flawelesly, you just need to setup your weather station according to the instructions when you set up the integration.

[RJ-Make]

Official integration works flawelesly, you just need to setup your weather station according to the instructions when you set up the integration.

and you get the benefit of some added sensors that are not available in the HACS version. (leaf is one)

[Remko76]

I actually went a different route all together; I am now using exowitt2mqtt. Like that even better.

[ChrisDHughes]

I can confirm that I finally got it working...

1. Whilst running Core 2023.4.5, I uninstalled the Ecowitt HA and HACS integrations.
2. Restarted HA.
3. Installed Core 2023.5.2
4. Installed the HA Ecowitt Integration.
5. Set my Ecowitt app to use a DIY server config using the details provided during the Integration setup, making sure to remove the first forward slash on the 'api/webhook/blahblah' line and now using port 8123, rather than 4199.

Note: previously I had not removed the forward slash from the api webhook line and no device or entities were showing up in the Integration. As soon as I corrected that in the Ecowitt app and Saved, they suddenly appeared.

I think the main issue, though, was having to go back to 2023.4.x before uninstalling both HA and HACS Integrations.

[snarlingllama]

I can confirm that I finally got it working...

1. Whilst running Core 2023.4.5, I uninstalled the Ecowitt HA and HACS integrations.
2. Restarted HA.
3. Installed Core 2023.5.2
4. Installed the HA Ecowitt Integration.
5. Set my Ecowitt app to use a DIY server config using the details provided during the Integration setup, making sure to remove the first forward slash on the 'api/webhook/blahblah' line and now using port 8123, rather than 4199.

Note: previously I had not removed the forward slash from the api webhook line and no device or entities were showing up in the Integration. As soon as I corrected that in the Ecowitt app and Saved, they suddenly appeared.

I think the main issue, though, was having to go back to 2023.4.x before uninstalling both HA and HACS Integrations.

Is this integration local only? It lists the IoT class as local push, but seeing instructions about api webhooks makes me wonder if its going out to the internet to get this data.

Is the is using the webhook api locally and directly to the station?

[GSzabados]

Is the is using the webhook api locally and directly to the station?

Both the custom component and the built in HA integration are local.

The built in needs a webhook where it can post the data. It is fully local. No need to go out to the Internet.
The weather station will post the data periodically to the webhook provided by HA locally.

[BubiBalboa]

I had to downgrade and migrate to the native integration as well. Worked fine until the latest update to 2023.5.3

The log says:

Error setting up entry Ecowitt on port 4199 for ecowitt

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/ecowitt/__init__.py", line 30, in async_setup_entry hass, DOMAIN, entry.title, entry.data[CONF_WEBHOOK_ID], handle_webhook KeyError: 'webhook_id'

Looks similar to what you describe @ChrisDHughes . Can you please explain your 5th step in a little more detail? Maybe that can help me fix this.

[ChrisDHughes]

I had to downgrade and migrate to the native integration as well. Worked fine until the latest update to 2023.5.3

The log says:

Error setting up entry Ecowitt on port 4199 for ecowitt

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/ecowitt/__init__.py", line 30, in async_setup_entry hass, DOMAIN, entry.title, entry.data[CONF_WEBHOOK_ID], handle_webhook KeyError: 'webhook_id'

Looks similar to what you describe @ChrisDHughes . Can you please explain your 5th step in a little more detail? Maybe that can help me fix this.

@BubiBalboa

Sure...firstly when you install the native HA Ecowitt Integration on 2023.5.x (It's easiest to do this on your phone with the HA app), before you click Finish, it basically lists all the information you need to plug into the standalone Ecowitt app on your phone. i.e...

a) the IP address.
b) the api webhook.
c) the port (8123 not 4199).

At the very least copy the whole api webhook into your clipboard.

• Open the standalone Ecowitt app on your phone, select '...' from the top right.

• Select 'Others'.

• Select 'DIY Upload Servers'

• Select 'Customized'

• Enter 'Protocol type same as:' Ecowitt.

• Server IP / Host name, enter the IP address in a) above.

• Path, paste the webhook api string from b) above...but remove the first / before 'api/webhook/.....'

• Port: Enter 8123 (not 4199).

• Upload interval: 60 seconds (or whatever you want).

• Click 'Save'.

• Close the standalone Ecowitt app.

• Restart HA.

That should do it.

Good luck. Chris.

[mr-sneezy]

• Path, paste the webhook api string from b) above...but remove the first / before 'api/webhook/.....'

That should do it.

Good luck. Chris.
@ChrisDHughes

I'm also trying to migrate to the built in integration but failing (after a long happy time with the HACS version). I followed the thread here and deleted the old HACS integration before updating to 2023.5.3. Installed Ecowitt integration after rebooting. However, I don't get any webhook string info from the installation help process so I can't enter it. Does that mean I am still installing the old HACS integration not the new one ?
After submitting I get a blank Ecowitt tile with no entities and this is what the setup info says...

[mr-sneezy]

OK I found the reason I could not get the built in integration to install. Mostly not being familiar with removing a HACS integration from the HACS menu (HACS in sidebar). What screwed me around was in that menu the Ecowitt integration was hidden so I could not find anything to 'remove'. Possibly by the filters being active when they had been 'cleared'.
Fluked I think after refreshing the browser and then Ecowitt and a few other integration appeared incuding Ecowitt. Removed it from there, restrated HA, waited about 15 minutes for EVERYTHING to be restarted and this time I got the right installation instructions with webhook...

[RoelDU]

I have removed the HACS version and validated in the explorer the folder is gone.
I installed the native integration and the below is shown to me.
I copy and paste (to prevent typo's) the webhook without the first "/" in the Ecowit App and I use the local IP and port 8123. However the Ecowit integration does not find my Ecowit server. If I install Ecowit the old way with HACS version and the hack to change the cope in the .py file it all works fine. Why in my case does it not work with the new Ecowit integration? :-(

[Remko76]

Guessing you are running everything in your local network as well; I used the internal IP adress, not my Duckdns name and used port 8123....
Maybe you are trying to configure it while connected through the external access and that is why it is showing the external path. I would try with the local adress....

[RoelDU]

I have removed the HACS version and validated in the explorer the folder is gone.
I installed the native integration and the below is shown to me.
I copy and paste (to prevent typo's) the webhook without the first "/" in the Ecowit App and I use the local IP and port 8123. However the Ecowit integration does not find my Ecowit server. If I iintall the HACS version and

[RoelDU]

Thank you for your quick response. Yes that is what I thought initially as well but I started home assistant from http://:8123. And I'm still getting the screen I showed earlier.

[Remko76]

I would try to configure the Ecowitt app with the local adress and port and the Webhook provided there and see if you get it to work.
Another option (what I have done in the end) is to use ecowitt2mqtt....I think that is even a nicer solution and works flawelessly for me.