Using the Ecowitt API to retrieve data from your Personal Weather Station (PWS)

exxamalte · July 4, 2022, 8:35am

Good to know how to access Ecowitt’s API.
However, have you tried the HACS custom component that allows for the weather station to push all data locally to Home Assistant. Probably took me less than 15 minutes to set all up.

nickrout · July 4, 2022, 9:51am

There is also ecowitt2mqtt

rodw · July 4, 2022, 10:22am

Yes, I tried it and another fork of it but they both were broken for me so I looked for another solution. I also tried my wunderground api but it failed too.

rodw · July 4, 2022, 10:40am

I did not know about ecowitt2mqtt. I’ll see if I can install the Docker image on my Synology NAS.

DaHype · September 4, 2022, 11:51am

Is there any way to get the Dashboard ecowitt.net into Home Assistant?
Sure i can create an Webpage card but i have to insert login in the Card, and that don´t works.
There only flash the card, because i cant log in.

Any Idea?

Thanks

rodw · September 5, 2022, 9:50am

Not that I know sorry… i just used an entity tile.

giqcass · September 21, 2022, 10:02pm

I’m surprised you had issues. I use the 1100 gateway and it’s been flawless. I wanted something similar to the old barometric gauges that predict weather. This is what I came up with. It’s still a work in progress as I dial in. The red and dark blue lines may get removed later but are helpful markers right now. Above the second dark blue line moving clockwise I have never had precipitation. Each red line as you move down counter clockwise the chance of rain increases. The label “Change” will read Storm, Rain, Change, Sunny, or Dry depending on the pressure.

weather

type: gauge
entity: sensor.absolute_pressure
needle: true
min: 942
max: 1050
segments:
  - from: 940
    color: '#765d91'
    label: Storm
  - from: 964
    color: '#543773'
    label: Rain
  - from: 979
    color: '#ff0000'
    label: Change
  - from: 980
    color: '#543773'
    label: Change
  - from: 982
    color: '#ff0000'
    label: Change
  - from: 983
    color: '#543773'
    label: Change
  - from: 985
    color: '#ff0000'
    label: Change
  - from: 986
    color: '#6cd1f0'
    label: Change
  - from: 988
    color: '#ff0000'
    label: Change
  - from: 989
    color: '#6cd1f0'
    label: Change
  - from: 991
    color: '#ff0000'
    label: Change
  - from: 992
    color: '#6cd1f0'
    label: Change
  - from: 994
    color: '#ff0000'
    label: Change
  - from: 995
    color: '#6cd1f0'
    label: Change
  - from: 1000
    color: '#080182'
    label: Change
  - from: 1001
    color: '#6cd1f0'
    label: Change
  - from: 1003
    color: '#080182'
    label: Change
  - from: 1004
    color: '#6cd1f0'
    label: Change
  - from: 1014
    color: '#f5f176'
    label: Sunny
  - from: 1040
    color: '#fa7f41'
    label: Dry
unit: mb

rodw · September 22, 2022, 12:46am

I tried the new ecowitt module since its been added to the HA core and it still fails for me so this API is still my solution. It has been flawless.

giqcass · September 24, 2022, 9:42pm

When you set up the gateway did you use a local IP address? You don’t want it to have to leave your network and try to make a round trip back in. Port 4199 might get blocked or redirected traversing NAT. I’m not sure if the Ecowhitt device can interpret mDNS either so I would stick with an IP. Personally I prefer avoiding the cloud. I like that the device speaks directly to HA.

rodw · September 25, 2022, 11:58am

Thats all very well if the device speaks to HA but it doesn’t I tried again several times.
The integration says to use data similar to this. The web hook changes every time the integration setup is selected.

Server IP: 192.168.1.29
Path: /api/webhook/f796e0a72913a097455e7d4ab7adxxxx
Port: 8123

So far the external API has been bulletproof. It uses https so no issues with ports.

giqcass · September 26, 2022, 11:45pm

You don’t need to create a webhook to use the integration and you use the port the integration exposes instead of the HA port. I believe the port is always 4199 by default. We must be using different integrations or different versions.

rodw · September 27, 2022, 9:49am

hmm,
there is something going on. This is what I get when installing the integration after a reboot

I can’t see there is anything to uninstall from the past. I dug around some folders
Using 2022.9.1 cos I get an error if I update but thats another story
2022-09-27 19:44:58.491 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547269756480] Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy

rodw · September 27, 2022, 9:59am

SO I tried using the different settings from the screendump above. The integration failed with an error.
In the log I get.

2022-09-27 19:36:26.017 INFO (SyncWorker_1) [homeassistant.loader] Loaded ecowitt from homeassistant.components.ecowitt
2022-09-27 19:38:13.292 INFO (MainThread) [homeassistant.setup] Setting up ecowitt
2022-09-27 19:38:13.293 INFO (MainThread) [homeassistant.setup] Setup of domain ecowitt took 0.0 seconds
2022-09-27 19:38:13.299 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.ecowitt
2022-09-27 19:38:13.302 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ecowitt
2022-09-27 19:51:47.664 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.ecowitt
2022-09-27 19:51:47.666 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ecowitt
2022-09-27 19:51:47.670 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Ecowitt for ecowitt
File "/usr/src/homeassistant/homeassistant/components/ecowitt/__init__.py", line 29, in async_setup_entry

Any ideas? I am quite a noob so don’t really know how to clean up errors.

exxamalte · September 27, 2022, 2:51pm

That line just points to code that tries to register the new webhook internally, which then apparently fails without giving any reason.
Are there any other error messages in your log, maybe related to setting up webhooks?

rodw · September 27, 2022, 7:29pm

yeh I saw that. I can’t access that folder.
When I walk the folders one by one, this one is not found in the terminal
/usr/src/homeassistant

I must need root access and I can’t use sudo or su either.

giqcass · September 27, 2022, 7:30pm

This is where we have to ask questions like how you have HA installed.

Tell us how you installed Home Assistant

Tell us if you’re running Hass.io 199 using an official HassOS image, a Docker install, Hassbian, a venv install, and so on. Things that are often really useful to know include:
What version number of Home Assistant are you running?
How you installed it. If you’re not using Hassbian or a HassOS based 
Hass.io 199 install, remember to tell us the operating system
Any relevant code - correctly formatted

For example:
Home Assistant 0.42.0 using Hass.io 199 with the HassOS image
Home Assistant 0.84.2 in a venv following this guide 13 on Windows 10
Home Assistant 0.90.2 using Hass.io 199 on Ubuntu 18.04 following this guide 23
Please remember that words like latest, current, newest and so on are not version numbers.

rodw · September 27, 2022, 7:38pm

Thanks, I’m using the raspberry pi (4b) version of the Home assistant OS.
Version is 2022.9.1
I am stuck there and can’t upgrade further becasue of

[547453715456] Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 299, in async_install
    await async_update_core(self.hass, version=version, backup=backup)
  File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 45, in _wrapper
    raise HassioAPIError(data["message"])
homeassistant.components.hassio.handler.HassioAPIError: 'HomeAssistantCore.update' blocked from execution, system is not healthy

Seems to be trying to access the same folder

giqcass · September 27, 2022, 8:21pm

Assuming you didn’t change anything in the file system yourself I can’t help but wonder if this is an issue created by failing storage. Are you using an SD card? SD cards give a poorer user experience. I use an inexpensive SSD and a SATA adapter on most of my full size PI boards.

I would definitely make sure I created a backup. Save that backup and a couple of the earlier backups on a different device if you haven’t done so. I make sure the file size matches when manually downloading a backup. You can also open the backup with WinRAR, Winzip, or whatever you like to verify you downloaded the whole file. It may sound paranoid but I have had issues with partial downloads using the manual backup download interface.

hassip:8123//hassio/backups or Settings >> System >> Backups

Then I would consider creating a fresh install on a different storage device if possible. Use the backup to do a restore. I suspect that would eliminate the errors.

rodw · September 27, 2022, 9:01pm

Thanks, I doubt its a hardware issue. I solved my upgrade issue

so am now finally running 2022.9.7.
I went and had a look at HACS and deleted a ecowitt repo there, restarted and tried again.
It still showed me webhook info which I entered on the phone app.
Nothing works.
There are a number of people with the same problem on the ecowitt github issues.
I think I will call it a day.
I might try mqtt one day but its not a high priority.

giqcass · September 27, 2022, 9:11pm

Glad to hear you solved the important part! I of course stand by my backup suggestion even if you fixed it.
When I rebuilt my system I pulled files from my backup for reference. I’ve also reverted when I messed up the yaml. I see a lot of people not doing proper backups so I can’t say it enough.