You are very welcome. If you need any help, just let me know, I can give some advises how to set it up and what to do, if you get stuck with something.
The integration works well with Ecowitt weather stations. For the weather stations you will need the WSView app on your mobile to configure the custom server.
To access the data sent to HA, you just need to open and view the created entities. If you want to log it for long term, then set up an InfluxDB and Grafana addons.
Thanks ā¦ indeed I would ask 1 more thing.
Since I installed the integration I got a ton of those Log entries.
Logger: custom_components.ecowitt
Source: custom_components/ecowitt/init.py:274
Integration: Ecowitt Weather Station
First occurred: 7. Juni 2022, 10:35:18 (2133 occurrences)
Last logged: 22:42:55
Unhandled sensor type runtime value 203864, file a PR.
Unhandled sensor type runtime value 203925, file a PR.
Unhandled sensor type runtime value 203986, file a PR.
Unhandled sensor type runtime value 204047, file a PR.
Unhandled sensor type runtime value 204108, file a PR
hey there
I liked the Ecowitt and this integration so much ā¦ I upgraded to the new Wittboy.
The data is coming ā¦ some ā¦ but the Device in HA still says GW1100 instead of GW2000
and not all sensor data (also added moisture etc.) is coming.
Is it needed to delete and readd the device when adding a sensor?
Is it needed to delete and readd the device when replacing / upgradind the ecowitt hub?
Is there a a way to have prefixes automatically?
so in belows example not only sensor.absolute_pressure etc.
but like: sensor.gw2000_absolute_pressure
edit: here is a dump of my ecowitt
It is a GW2000 base + wh90 (wittboy) outdoor array + WH31 + soil sensor + currently additonal still the old wh65 outdoor sensor array
Iāve been using @garbled1 for months now (still do), and works great and very stable ā¦execpt all the errors in the log files and unsupported sensors. I came across another Ecowitt/HA integration @bachya and it works amazingly well, even with my GW2000
Right now I have my GW1100 on garbled1 and GW2000 on bachya.
is there a way to also create a native weather entity out of that data directly in the integration or does someone have a template sensor that can be shared that takes all the data from inidivual entiitys and puts it in a weather entity so the standard cards work directly?
For those of you with multiple devices on the same HA instance (such as a GW1000 and a GW1100) that each handle their own unique sensors, how did you set the configuration settings? Are they different for each device, or should they be the same? For instance port 4199 and path: /data/report/ for both of the devices.
I am having trouble with my integration seeing both devices (2 devices), but only wanting to connect to one at a time. When I restart HA, it seems to randomly pick which one it wants to connect to, but never both at the same time. Any ideas would be very helpful.
And what if you would jsut read an follow the clear instructions?
The following steps must be performed before setting up this integration.
If you have not already done so, please do this now.
Use the WS View app (on your phone) for your Ecowitt device, and connect to it.
Pick menu ā device list ā Pick your station.
Hit next repeatedly to move to the last screen titled āCustomizedā
Pick the protocol Ecowitt, and put in the ip/hostname of your hass server.
Path doesnāt matter as long as it ends in /, leave the default, or change it to just /.
Pick a port that is not in use on the server (netstat -lt). (4199 is probably a good default)
Pick a reasonable value for updates, like 60 seconds.
Save configuration. The Ecowitt should then start attempting to send data to your server.
Click submit when these instructions have been completed.
The weather station just sends data. The integration just interprets the incoming data on the set port.
Hi @darlezior - yep I also just got a Wittboy and am having the same issue. It looks like somebody has already fixed it and submitted a pull request in April for the change to be merged into the integration, but this hasnāt yet been approvedā¦
Iāve been trying to get this up and running myself and Iām not having much luck. It seems like Iām just missing one step somewhere and I canāt quite get it going.
Iāve added the integration in HomeAssistant with Port 4199 and āecowittā in the text box below it (not sure what that text is for) and confirmed that the port is open and itās listening via netstat -aon. I have even deleted the integration and run netstat to confirm that nothing is using that port otherwise. Iām using a GW1100C with the latest firmware (v2.1.5)
Hereās the way Iāve tried this the last time:
Use WSView to set up the Customized upload. Top to bottom:
Enable
Protocol: Ecowitt
Server IP: IP of the RPi running HomeAssistant
Path: /
Port: 4199
Upload Interval: 60
Then, in HA Iāve added the integration. Iāve checked and HA is listening on that IP and port. However, no devices nor entities appear. Where am I going wrong?
Checked the logs and this is the only entry in there for ecowitt:
That was one of the times that I had an issue deleting the integration to try readding it after Iād changed something in WS View.
More info on how everything is set up here. Iām running HomeAssistant on an RPi 4 in a docker container. Iāve got AdGuard Home running in a second container on that same Pi. Everything is running through the Balena ecosystem. Iāve tried the private IP of the Pi, the public IP of the Pi, and even a URL that is how I can login to manage things from offsite.
OK, will update after I learn how to use netcat. First step: Google netcat.
Edit: Do I need to be removing and reinstalling the integration each time I make a change? Or if I leave it set up will it suddenly start showing a device and entities once I fix whateverās broken?