This may not exactly be related to the integration, but I thought I’d ask: does anyone have a definition list for the various values that are reported to home assistant. I’m thinking of questions like “how is ‘wind gust’ defined” and “what is ‘event rain rate’”?
Hi,
Any update on this, or details of the integration/plugin they said they will work on? I’m keen to integrate the wittflow to HA.
Thanks
No update on the Wittflow integration yet. Still awaiting the plugin development. I’m using my valves with the cloud based smart watering rules and had a few ‘glitches’ with rules not firing. However the development team has been very proactive sorting out the glitches so I have no doubt they are also working proactively on the plug-in as promised.
No problem, thanks for giving the update. Hopefully its something thats available sooner rather than later!
More people see that ecowitt.net does not work?
My GW2001 Wittboy does work and I get data from the device.
But the ecowitt app and also the site https://www.ecowitt.net/ does not work from my place ( the netherlands). Try mobile, internet nothing.
After a reboot of my router I have acces to ecowitt.net.
But my ecowit device is (with reboot) is still offline… strange
Hi Ecowitt HA community:
I’m trying to reinstall the HACS Ecowitt integration on my RP4. I get this error when I install it. Anyone else?
Config flow could not be loaded: {“message”:“Invalid handler specified”}
I don’t think this is an Ecowitt specific error, but seems to appear with certain integrations.
I’ve removed and reinstalled and rebooted multiple times, but no luck. Any ideas?
many thanks in advance
2 Likes
Got the same issue
Hi,
I found the solution in another thread:
Got me working again.
1 Like
Anybody got an update on the Ecowitt team to get it to work in HA? Summer is coming 
I noticed a screenshot from @mn_box about the rain sensors. I just installed the Wittboy, no problems occured but I think the sensor names are wrong.
The hourly, daily, weekly, momthly and yearly rain sensors do not show the rate but the actual rainfall in that period. This is also clear from the sensor unit of measurement being mm instead of mm/h.
Therefore it would be good to omit the “rate” part from the default naming.
Hi,
dokumentation here: start [Wiki - Fine Offset Ecowitt Ambient Weather Stations (and clones)]
says that they have added support for first raindrop feature "start of rainfall detection
with an upcoming firmware upgrade (August 2024) a “first raindrop detection functionality” will be introduced." this is as i know for the GW2000 and WS90
see attached image from forum.
Could this please be added to the integration so one can get a trigger for when it starts to rain from the sensor.
thanks
1 Like
Great idea - I’d like this as well.
What I’d like better is for my Ecowitt rain sensor to … actually work! It just quit suddenly a couple of weeks ago, but the rest of the unit is all fine.
After gw update there is new rain sensor.
Thumbs up for
1 Like
The rain start addition seems to work really well. Look forward to this getting added into the integration so it can be used as a quicker trigger.
you could use the rain rate sensor with numeric trigger greater than 0 (its what I do now for my WS90).
1 Like
Yeah, I have created that sensor for dry or raining but it’s so slow. Thankfully their own works really quite quickly.
ahh ok, usually, within 30 to 60 seconds I get the trigger for the rain detection when using rain rate sensor. It could be quicker, you’re right.
Hi all,
I’ve been looking into migrating my Ecowitt integration (HACS) to the official one to get rid of the warnings which will become breaking changes soon. Unfortunately it seems that the HACS version is not maintained anymore.
I just have a few doubts before doing the migration.
- Are all sensors from the Wittboy (WS90) supported? I also have soil sensors (WH51) and internal sensors (WH31), plus an air quality sensor (WH45): they all worked out of the box with the HACS integration.
- The station is in the same network as the home assistant server. From what I understand this shouldn’t be an issue when migrating to the official integration which uses webhooks, as it should still be able to reach the home assistant instance on whatever port it needs. I have homeassistant running on docker so all ports should be reachable. Am I wrong?
- Is there a way to migrate without losing all history up to now by matching the newly created entities to the old ones? Do I need to manually rename all entities to match the old names once I install the new integration?
Thanks!
Just wanted to say thanks - lifesaver - this works perfectly and brilliant suggestion - nicely done. Added benefit I should now be able to feed the data off to non-ha containers on other machines like Influx/Grafana.
All sensors on the WS90 work for me on the official integration. As does the lightening sensor - so I suspect pretty much anything the WS2000 gateway creates gets correctly interpreted and instantiated in HA.
I run HA in a docker container. Just fired up the official integration, let it create a webhook (and wrote that bit down), and ignored the host and port it suggested as I run my HA with https enabled locally and also (obviously) with Nabu Casa.
Then with NodeRed used the flow given earlier in this thread Post 288 to create an http port with just a path of ‘/ecowitt’ on the nodered container and pointed the ecowitt at that. Then pointed the https node from the nodered flow at the local https address for Ha with the appropriate webhook. All works perfectly.
Not sure on the migration point - but I suspect that won’t work nicely without a lot of wrangling in HA - but I may be wrong on that.