I visited your GitHub site linked above and grabbed the raw files. I opened each of the two drivers files and pasted your new code and saved. I didn't do anything with HPM. I think I did things right, but please direct me if I made any mistakes here.
Thx!
weird i am at a loss i would have expected an error.. but not it to say unrecog. attrribute..
Yeah, very strange. I may play around with it a bit and see what I can come up with. Thanks for helping out!
maybe it doesnt like the two digits there for testing you could hardcode like this
//
case "soilbatt1":
case "soilbatt2":
case "soilbatt3":
case "soilbatt4":
case "soilbatt5":
case "soilbatt6":
case "soilbatt7":
case "soilbatt8":
case "soilbatt9":
case "soilbatt10":
case "soilbatt11":
case "soilbatt12":
case "soilbatt13":
case "soilbatt14":
case "soilbatt15":
case "soilbatt16":
case "soilmoisture1":
case "soilmoisture2":
case "soilmoisture3":
case "soilmoisture4":
case "soilmoisture5":
case "soilmoisture6":
case "soilmoisture7":
case "soilmoisture8":
case "soilmoisture9":
case "soilmoisture10":
case "soilmoisture11":
case "soilmoisture12":
case "soilmoisture13":
case "soilmoisture14":
case "soilmoisture15":
case "soilmoisture16":
case "soilad1":
case "soilad2":
case "soilad3":
case "soilad4":
case "soilad5":
case "soilad6":
case "soilad7":
case "soilad8":
case "soilad9":
case "soilad10":
case "soilad11":
case "soilad12":
case "soilad13":
case "soilad14":
case "soilad15":
case "soilad16":
updated = sensor(it.key, it.value, 6, java.util.regex.Matcher.lastMatcher.group(1).toInteger());
break;
also confirm is the uncreg attribute warning coming out from the gateway driver or the sensor driver.
The attribute warning is coming from the Gateway. I don't seem to have any. logs from the sensor driver.
I also changed the code to use the explicit case statements, and I get this error:
2nd try.. try the new files posted above again.. i made some changes...
Hub migration question. Im migrating from an C8 to a C8 pro. in the documents it says to disable land devices and apps. Do I need to disable my Ecowitt app and integration before doing the migration?
I would suggest pausing the data feed from within the EcoWitt App.
I think your latest update has things working for me! I only have 9 sensors, but all 9 now appear to be added and functional with regard to the moisture percentage. Awesome!!
One thing that appears to not be correct is the battery levels of these sensors. Not a huge issue for me, but it'd be nice for completeness. Here's the main device page showing battery:
Here's the Ecowitt hub moisure/battery display:
And here are the logs when doing a Refresh of the driver:
Thanks for working through all of this, I really appreciate it. Now I can purchase a few more sensors for the rest of my tomato and pepper beds!
NGL, I've not read the 1800+ posts.
If I buy an EcoWitt GW1100 or 3000 Wifi Gateway and a few soil moisture meters, or the EcoWitt GW1206 kit that includes the GW1200 and a WH51 soil moisture sensor (and add some WH51's), can I connect this to Hubitat totally locally, and have the results of the moisture sensor control the irrigation valves connected to Hubitat?
Is there a HE specific benefit to one or the other Gateway (GW1100 vs GW1200 vs GW3000) other than their capabilities outlined here?:: https://smartout.net/ecowitt-gateways-compared-gw1100-gw1200-gw2000-gw3000/
Is there a limit to the quantity of moisture sensors HE will report on?
If I get an EcoWitt rain gauge , does HE pull in the data from the rain gauge, still locally?
From Hubitat’s perspective, all the gateways are the same.
If the gateway has connected soil sensors, it will report that data to Hubitat. Same for a rain gauge. There’s no upper limit from Hubitat’s perspective, only the limits on directly connected sensors of various types (to the Ecowitt gateway) imposed by Ecowitt directly.
The integration between Ecowitt and Hubitat is local if using the integration in this thread.
I use the GW1100, and I connect it to Hubitat via MAC address, and it's fully local. With some updates to the Hubitat Ecowitt Driver recently (thx Larry!) we can now have all 16 supported soil moisture sensors (WH51) connected locally to Hubitat. You could easily create rules to control valves based on the WH51 values.
I also have a Wittboy with rain gauge, and here are all the values that are recognized by Hubitat:
I'm very happy with the integration, it's been a lifesaver for my gardens during hot dry stretches in Northern California.
nothing i changed should have affected the battery code.. are the battery levels the same if you go back to the stock driver or are they different. would good to see debugging on and what is actually reported for the batteries. .my guess is maybe they were wrong all along?
@marktheknife & @spotty
Thank you both.
Is the EcoWitt soil moisture sensor the best solution for monitoring soil moisture with the Hubitat? Just trying to confirm if I should invest in this ecosystem...
I don’t have any experience with moisture sensors besides these Ecowitt ones. That said, I’ve been happy with them for several years now. I replace the AA battery in each one every season, and I’ve never had a problem. I have the sensors positioned up to 75 feet from the Ecowitt hub, and I haven’t had any connectivity problems. They are pretty clear line of sight to the hub.
Now that I think about it, I’m sure you’re right. I believe the battery values were the same with the code prior to these updates. I’m actually not sure where the problem might be, if there is one at all. Battery reporting seems to be inaccurate at best much of the time. The Ecowitt software doesn’t have specific battery values presented, only battery icons that aren’t very specific. Maybe I’ll go check the actual battery voltage to see if they match what Hubitat thinks they are.
I took a multimeter to the AA batteries in the Soil sensors, and the voltages match with the prefs and code in the Hubitat driver. Looks like things are working as expected.
Thanks again!
Download the Hubitat app
