Windspeed does not drop to zero if there is any wind. See the graph. Wind gust does.
1 Like
Sorry, but I'll need to look at this in a few days, when I have some more time.
Thanks for the continued feedback! I found more info specific to the ecowitt WS90 sensor, see snap below. I think I'll be using windSpeed and windGust attributes based on this. Although I definitely would like to understand the windSpeed_avg_10m attribute too. Hopefully Simon can chime in over the next few days also.
I appreciate it Simon! This is turning out to be more challenging than I thought it would be (my whole shade automation setup).
1 Like
There is no such attribute wind10m or whatever. Not in the attrs reported to hubitat nor in the.ecowitt aps. Not sure where u are seeing that.
Hi,
Did you get this WFC01 working on HE ?
Thanks
I didn't find anything official to explain what that attribute represents, but the best I could find indicates that it is a 10 minute average wind speed, as you might expect. The reasons why some may see it and some may not is a little hard to be clear on, I wonder if it is a mix of the weather station or sensor model and/or the model of gateway being used.
The driver does handle it:
Gateway driver:
//
// Wind & Solar Sensor (WH80 -> WH69, WS90)
//
case "wh65batt":
case "wh68batt":
case "wh80batt":
case "wh90batt":
case "ws80cap_volt":
case "ws90cap_volt":
case "ws80_ver":
case "ws90_ver":
case "winddir":
case "winddir_avg10m":
case "windspeedmph":
case "windspdmph_avg10m":
case "windgustmph":
case "maxdailygust":
case "uv":
case "solarradiation":
case "ws90cap_volt":
case "ws90_ver":
updated = sensor(it.key, it.value, 9);
break;
Sensor driver:
case ~/windspdmph_avg10m_wf[1-8]/:
case "windspdmph_avg10m":
updated = attributeUpdateWindSpeed(val, "windSpeed_avg_10m");
break;
In terms of your rule, I don't think an average is the best option for an automation, at least not that I can think of. As for the wind speed itself, or the gust.... I'd also be mindful of your update frequency, but I haven't read back through all of the previous conversation on that yet.
Hi @marung8 , unfortunately that hasn't been added to this set of drivers yet. I'm not sure whether any other community drivers have added it... Note, the way the product information reads (at least what I have read), much of the functionality of this device appears to rely on the EcoWitt cloud. But I will need to read into some more to understand it better.
You may also be interested in the WFC02:
What were you hoping to do with the water timer?
First of all I want to thank you for your support.
I already bought this WCF01 which is intend to automate garden irrigation. I see can use the app to create this automatization, but I just want to use HE to do this.
Anyway I will have patience and hope that one day will be sot out the driver for this device.
Thank you.
2 Likes
I also have the WFC01 plus the humidity readers. So i programmed it to water my plants as soon as the humidity is too low. It would be fun to have it supported by the driver. Thanks you.
1 Like
Ok, maybe my arm is being twisted a little more (in a good way) 
If anyone else is interested please post to register your interest.
1 Like
In case it could help, they have it work in Home Assistant and here is the code:
1 Like
I'm always open to stealing building on the work of others.... Thankyou for finding this repository. I'll take a look.
2 Likes
I have had a WFC01 for a few years. Garden watering is currently running off a fixed schedule via the Ecowitt app (cloud) and watering schedule skipping is set up using my Ecowitt rain gauge actual rainfall (again cloud based skipping). Count me in for Hubitat integration of the WFC01 and the ability to control the garden watering via Rule Machine with local control.
1 Like
gw1100x firmware updated to 2.4.2 then 2.4.3 in last few days.
new attribute added last24hrainin and last24hrain_piezo
changes to gateway driver
changes to sensor driver
2 Likes
I have my Ecowitt sensors integrated into Hubitat and also forwarded through to Home Assistant for dashboard display. Today I updated HA to the latest core version and noticed my soil moisture sensors have become ‘unavailable’ in the Ecowitt HA service. All the other Ecowitt entities (I have 95 Ecowitt entities in total across 3 gateway devices passed through from Hubitat to HA) are still available and are updating fine. It’s just my 16 soil moisture sensors that have become unavailable since the HA core software update.
When I go into the entity settings in HA for any of the soil moisture sensors I get an error message stating “This entity is no longer being provided by the Ecowitt integration. If the entity is no longer in use, delete it in settings”
I’m sure this is a Home Assistant Ecowitt integration issue as everything seems to be working fine with all my Ecowitt sensors in Hubitat. Just wondering if anyone else who is also forwarding Ecowitt sensors from Hubitat to HA has also noticed this issue?
I don't actively use the feature, even though I introduced it, but I can take a look in the next few weeks if I get some time.
1 Like
Thanks Simon for your quick response and kind offer to look further into the problem. I just found a status update on the HA forums confirming it is an HA issue and will be fixed in the next HA core software release, so no need to look further on the Hubitat side of the integration. Posting the update here to inform other Hubitat users that may be experiencing the same issue.
2 Likes
My soil moisture sensor is working in Home Assistant reporting the same percentage as it shows in Hubitat and the WS View App.
1 Like
