Problem with Ecowitt

[Vicio88]

The problem

I have a problem with the Ecowitt integration. I've done all the steps but can't find anything

What version of Home Assistant Core has the issue?

Core-2023.9.3

What was the last working version of Home Assistant Core?

Core2023.9.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ecowitt

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

[frenck]

I have a problem with the Ecowitt integration. I've done all the steps but can't find anything

Please describe your steps, so we can reproduce. Additionally, is there anything in the logs or any other error message we can get information from?

There is not much for us to work with, if the only thing you report "can't find anything". Thanks for understanding.

../Frenck

[home-assistant[bot]]

Hey there @pvizeli, mind taking a look at this issue as it has been labeled with an integration (ecowitt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ecowitt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ecowitt Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

ecowitt documentation ecowitt source _{^{(message by IssueLinks)}}

[Vicio88]

I entered all the data to be entered but it finds nothing. There are no errors

[frenck]

I entered all the data to be entered but it finds nothing. There are no errors

Sorry, there is not much we can do to help you with "finds nothing". Please provide reproduction steps and logs.

../Frenck

[Vicio88]

I enter the IP, the port and the path but it doesn't find any device

[tanderloco]

Try changing the port adress from 8123 to 4199. The port 8123 can't be used.

[cpuks]

Looks like this is related #100005 - as soon as I stopped using webhook my HA instance started to behave as it should with 2 x 1240p cores and 4 GB RAM. Can we give an option to use a other port than 8123 to see if this helps? As HA creates a webhook automatically and port cannot be changed. @Vicio88 you're missing / at front of API - you didn't copy and paste this right - try again, wait 60-120 sec and it'll be all good, @tanderloco port has to be 8123 otherwise it won't work - this integration on 2023.9 onward causes really poor UI performance in my case - I've got now 3 different HA instances to test that - HASSOS production / HA docker and HA yellow so I can volunteer with that matter also probably new bug has to be opened to investigate my problems.

[jenningschris]

@cpuks not sure what op is using, but on my iPad I couldn’t get it to work when I put the / I finally noticed Ecowitt puts a / in front of the path for you.

[cpuks]

Ok can you get app https://play.google.com/store/apps/details?id=com.ost.wsautool and do it right there?

[staggartcreations]

Ok can you get app https://play.google.com/store/apps/details?id=com.ost.wsautool and do it right there?

I had the same issue, and I must say using this (alternative) app worked for me. It seems to be practically the same in terms of set up. The difference is that it does not prepend a '/' character at the start of the Path, unlike the Ecowitt app.

In this case, yes, the exact webhook path provided by the Ecowitt integration must be copy/pasted. In the context of the Ecowitt app (as opposed to the WSView Plus app) the leading '/' must be omitted.

In my case, it was actually the trailing '/' that needed to be removed. I suppose this was difficult to notice in the Ecowitt app since the text field gets cropped on the right side.

PS: I am using port 8123, and do not have SSL set up.

[machyaer]

Hello, I have the same problem with this integration... but I found that with these settings:

Every thing worked perfectly with an older version of HA (i.e. 2023.6.1):

but not with the newer one (i.e. 2023.11.3):

[Coder84619]

I just got my Ecowitt and HA is not pulling in any data. 2023.11.3.

[Yarryman]

If you are using the web front end to Ecowitt and not an app then you need to add the / at the front of the path. Anyone mentioning the 4199 port is referring to the HACS integration not the Core integration to Ecowitt.

Also check that the port for your web front end is 8123 as mine was not since i installed in docker and had a need to change it and forgot.

Also note that if you have installed the Hacs integration you must remove the interface and uninstall in Hacs before the standard integration shows up.

[machyaer]

If you are using the web front end to Ecowitt and not an app then you need to add the / at the front of the path. Anyone mentioning the 4199 port is referring to the HACS integration not the Core integration to Ecowitt.

Also check that the port for your web front end is 8123 as mine was not since i installed in docker and had a need to change it and forgot.

Also note that if you have installed the Hacs integration you must remove the interface and uninstall in Hacs before the standard integration shows up.

I solved my issue using ecowitt2MQTT integration, the problem is due to the SSL protocol of my HA... see here for more details: https://github.com/home-assistant/addons/issues/3337

[Xanthomonia]

I placed http:// in front of server name and made sure that a / is in front of webhook and everything worked.

[machyaer]

Just a question: do you have ssl enabled in HA?

[Xanthomonia]

No, I did not enable SSL, i installed HA straight forward on a NUC.

[machyaer]

My problem was there... I have SSL protocol enabled...

see: https://github.com/home-assistant/addons/issues/3337

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.