It is added to the gateway as a “sub device” which may require a different process to integrate this? It allows to run water on time or volume which is handy for topping up a pool for example.
Does anyone know if there’s any movement (or progress!) on this? I’ve had a couple of WFC01’s since launch with the intention of setting them up with automations in HA. still a bit disappointed that we’re yet to see any integration in HA.
I did see there was a response from Ecowitt support that suggested they were working on a HA plugin amongst other things back in December and suggested 3-4 months as an ETA but not seen anything since. Also unsure if this would require the original owner of the HA Ecowitt integration to do anything too?
It also appears another community member has done work to integrate subdevices, so it might not be a large effort to merge into the official integration.
+1 on this feature request. As many of you in this thread, I have a GW2000 and a WFC01 smart valve, which is very surprisingly not supported by the Ecowitt integration. Hope that it will be feasible technically. Will also follow the corresponding Github issue and alternatives.
Dev here. Thanks for linking back to my pet project!
Unfortunately, due to the way Ecowitt has built the API of the subdevices, it’s probably a bit more challenging. Subdevices are to some degree dependent on the parent device, so you have to keep the state of the entire gateway+subdevices in-memory or on-disk. I have my API findings (randomly) distributed in the code, if there’s interest I’ll will put them in a single file and share it in the repository.
I would like to see this as well. I was planning to monitor situations where latching valves don’t turn off and use this as a fail safe to shut off water.
Thanks for your work on the integration! So are you saying currently it’s not really possible unless they make some changes how they’ve setup the API’s for subdevices?
Yes, more or less. HA will need to keep track of the entire device and “actively” ping the subdevices via their API (that isn’t completly RESTful). There is no “real” id that connects a subdevice to a parent device. They have one on the gateway but it’s not being used on the subdevice. It feels like there are two different, disconnected development teams developing the software.
I’ve been working on an updated version of the ecowitt-controller over the last months that will adress a few issues and requests that have been collected over the year or that i have discovered during use. feel free to browse through the code in one of the refactoring branches
@mplogas I’m not one of the devs on this project. I just wanted to be able to control my WFC01 with home assistant. I found this thread and then went on a deep dive and found that Ecowitt was already working on a new official integration. I assume they will probably move it out of HACS and into the ha official integrations at some point.