Just an FYI… There has been some interest “lately” (over the last 12 months) in seeing updates to these drivers… I am likely to start looking at these requests in the next few weeks… Including the laser depth sensor, updated soil moisture sensor including temperature, and additional sensor readings, including aggregate rain readings.
New Ecowitt Water Quality product coming..
Re the Laser Depth Sensor, I would be interested to hear about how / where people have used this sensor and @kahn-hubitat‘s driver that supports it. Is it mostly people wanting to keep track of snow levels, or is there also people wanting to know water levels and other situations?
i have 2 LDS01, i didn’t link them in Hubitat. Alert from Ecowitt are enough for me = low and high level.
You can see my sensor : Ecowitt Weather
One look at my water level in my surface well. At 400mm = Water Level too low for my pump. Puit eau Min 400mm LDS01-Ch1
The other in the summer monitor the lake water level, in the winter, the amount of snow on my gallery. To know when to call someone to remove it above 24 inch. Lac LDS01-Ch2 158
Wave cause by the wind give changing level.
The advantage of sensor in Ecowitt is the ability to graph. Something not easy to have in Hubitat with a ZigBee sensor. Possible but not as user friendly than in Ecowitt
You can use both (I do for most of my sensors). Hubitat is useful for automations. For instance, if the water level is low, you could turn of the main water to prevent usage (not that I would do that). Still keep Ecowitt for the historical graphs - Like you said, it is easier and native to Ecowitt.
NOTE: This is a single sensor (not multi channel like the outdoor sensors) and only 1 either wh45 or wh46 can be on your system. It can also be powered over usb and is meant to be indoors as it does not have a solar charging battery capability.
I have a new version of my code both gw and device file and template file if anyone wants to pull it.
In addition to the snow depth or straight depth and percent full for the laser density it has support for the new wh46 sensor.
This new sensor in addition to measuring particulate matter less than 2.5 and 10 microns
also measures pm1 and pm4. (less than 1 and and 4 microns respsectively)
So these new attributes are added.. I also noticed i never reported raw pm25 and pm10 previously these numbers are only used to go into the aqi calculation.
This has not changed as the aqi calculation still onoly uses either pm25 or pm10.
The routine has and does take the best aqi if the sensor (wh41 and wh45 do) measures both.
so to summarize i also added pm1, p1_avg_24h, pm4, pm4_avg_24h, pm25, pm25_avg_24h, and finally pm10 and pm10_avg_24h new attributes.
and a new template entry shown below (14) for these attributes.. the template file needs to be uploaded to you hub file the settings/file interface.
I have not found documentation or am not 100% sure how it measures the brackets but I assume pm1 is<= 1 micron
pm25 is between 1.x and 2.5 microns
pm4 would be between 2.6 and 4 microns
etc etc.
anyone is welcome to use and sburke is welcome to look at the code and integrate at his leasure.
Sorry if this comes through twice....
The more perceptive of you will notice I have not posted here for a while... I still have "other life stuff" going on, limiting my ability for getting time to spend on projects such as this... I do appreciate the time others have spent offering their changes for review and I do still want to find time to integrate these when I can.
On a more practical note... I would be interested to hear if anyone has tried the built-in aggregator app released recently.
Cool, I will switch to this Ecowitt driver. Do I just need to load both those drivers shown above? I have a couple LDS sensors I want to get into Hubitat.
Looking for some help, not sure if the issue is in the Ecowitt vs Hubitat world.
For the relevance to Ecowitt, I have been using this integration for many, many years (provided by mircolino) and he even made some cool tweaks for me (implementing absolute humidity). Only by coming here and reading the start of this thread did I learn that he left the HE platform and it appears some divergence of code occurred and some intervention may be necessary.
The issue is that I have a rule set up that turns on a smart switch connected to a dehumidifier and there was a time when it was working reliably (possibly years ago) but now it doesn’t work at all. No changes to the rule have happened, I’ve only tried platform and driver updates to resolve it. I do recall Ecowitt causing excessive activity alarms on HE but I don’t know that’s related. At least once, a platform update and restart seemed to get it going, but stopped again soon after.
When I did the driver updates, it was via package manager…I was not aware of any transitional requirements.
It appears HE is receiving data from the GW1100 device. I can see in the device events, data updates coming in. I can even see some rule triggers under Events; albeit not when they should be triggered according to the rule. This makes me think its NOT an Ecowitt driver thing.
I had added turn-off rules since the range in the turn-on rule didn’t seem to be working, and because the dehumidifier makes the room hot. They’d turn the switch off <= 45%RH and temp>78 respectively. I’ve disabled those rules to see if they were causing a conflict, and no change.
I should mention I have multiple other “Simple Automation Rules” that work just fine (Dehu rule is also a Simple Automation Rule). Fan turns on reliably every evening at 8:00. Lights out at 10:00. Lights on at 8:00. Bathroom fan off after 20 minutes. All work perfectly and always have.
I’ll be damned. As I’m writing this, the dehumidifier clicked on, triggered by the rule for the first time in months. Granted, I was in HE tinkering with things…I did that update via package manager probably an hour ago, turned off those rules I mentioned and other than that…just poking around trying to see where the breakdown was. I also updated firmware on the GW1100, but it wasn’t very far behind. There were many temp/humidity events that came in after the last change, that didn’t trigger anything when it should have. So it doesn’t make sense that something I did made the difference. But now it decides to work? I don’t expect this situation to last long, so I’d appreciate any ideas regardless.
Should I start with the provided procedure to switch to the new driver? Or try something else?
There's 2 Drivers that I know of:
-- The one maintained by sburke781. I've been using this one for a couple years and its works fine. It does not have some of the more recent Ecowitt sensors Yet but updates on they way.
--The other maintained by kahn-hubitat. This one has all the latest sensors including the LDS and I loaded the driver to take a look. Its a bit more complicated so haven't committed to it yet. Still checking it out.
Each have 2 drivers to load and both named; "Ecowitt WiFi Gateway" Parent and "Ecowitt RF Sensor" Child
I suppose I don’t know which one I have. I installed mircolino’s driver years ago, and have been updating via HPM. Maybe that’s part of the problem, I don’t know.
Whichever it is, I want to stick with it because as mentioned it does have the calculated absolute humidity. I use that to determine when to ventilate; only when outside air is drier than inside.
I should update and mention that indeed whatever got jostled loose yesterday and forced the trigger, it didn’t stick…as expected. No triggers at all since, despite conditions existing that should produce one.
I'll try to get to your question after work or over the weekend @blackcloud77
I think the first thing to do is to work out what drivers you are using.
-
Open up the Device page for the gateway on your HE hub
-
Open the Device Info tab
-
Next to the "Type", click on the "User" link to open the driver code
-
Check the details at the top of the driver to see if they look like this, indicating that it is my drivers you are using
You can also get a listing of the Apps and Drivers in HPM, but I think it is best to go to the device so you know exactly which driver is used by the device.
I would also suggest:
- Posting some screenshots of the rule you have setup
- Enabling any logging you can for the rule to see what may be happening (or not), particularly when it stops working
- Turn on logging for the other devices involved in the rule, such as the switch for the dehumidifier
- Enable more detailed logging for the EcoWitt devices involved so you can see all the information together in the HE Logs, i.e. device events, triggers for the rule and actions on the switch
Review the logs and see what you think. You can always post some of them here if you are not sure.
How dare you have "other life stuff"?!? 
