And now I will do the same thing on the Settings page for the hub, which is correct on Celsius, and all other thermometers (not EcoWitt) are on Celsius.
On the Hub logs there are no messages for changing to Farenheit and saving, and also for changing to Celsius and saving.
No messages!
Edit: it seems like the Save Changes option is not doing anything. Even if I change the Log Verbosity to something different it will go back to the previous settings.
There does appear to be a general issue with certain preference setting types in the new beta platform version, which I am sure will be addressed shortly.
First of all, thanks for the driver, I have received my Wittboy WS90 about a week ago and the integration runs very neatly!
There is one attribute though that is not being populated on the HE device: srain_piezo.
It indicates if it is raining or not, and for me, it is probably the single most important information I want to use for my automations.
It has only 2 values, 0 (no rain) or 1 (raining), regardless of the rain rate.
Depending on the rain intensity, it triggers before the rain rate, as seen here:
Thanks for the request @eduardo . That certainly looks easy enough to add. "When" might be the main challenge.... I might be busy over the next few weeks, so it could be a little while before I can look at it, but if I can I will try. I also have a few loose ends to tie up on other projects as well.
Two questions (edit, One question!), as I'm predominantly interested in just the humidity reading of the Soil Sensor, is there anyway to turn off the Pressure reporting from the gateway, and maybe also Temp, the readings bounce back and forth, and max reporting interval is 10 minutes.
Re the temperature and humidity readings, I expect technically that would be possible to hold them back, but I would like to understand a little more about why you would like to have this option. Are you concerned about the number of events generated, as I don't expect this would pose a significant issue for the hub in any way.
Unfortunately my personal circumstances at the moment will mean I won't be able to work on this driver for some time (at least the next few months). That won't last forever, but I can't say when I will be able to deliver on recent requests. I hope people will understand.
Please continue to post any questions or issues, I do still log into the Community each day and am happy to help where I can or allow others to do the same.
Hi @sburke781 thanks for the reply, you've been very helpful and accomodating so we appreciate the time you give.
As you say, this driver receives info from the gateway. Regarding the Indoor Ambient Sensor the data it gives from the Hub aren't accurate
humidity : 60
orphaned : false
pressure : 1035.79
pressureAbs : 1035.79
temperature 19
And thus are just spamming my Hubitat, even at max 10 minute reporting frequency, the data just jumps back and forth repeatedly so isn't reliable. The Ecowitt driver is using using roughly 35% of hub resources.
So ideally I'd like to minimize unecessary data.
I have 4 soil sensors, but the internal calculation the gateway does for Humidity has issues also. Where as the "AD" reading of the soil sensors is always correct and steady, the gateway sends inconsitent Humidity reports, jumping back and forth for no reason. As you can see from the screenshot below, the yellow line is the gateways humidity calculation, and the blue line is the "AD" reading. It would almost be better to receive the "AD" reading that is reliable and allow WebCoRE to calculate the correct Humidity precentage.
16/12/2024, 09:42:12 +238ms
+63ms ║Garden Pot is 50%
16/12/2024, 09:32:10 +985ms
+62ms ║Garden Pot is 51%
16/12/2024, 09:22:09 +888ms
+63ms ║Garden Pot is 50%
16/12/2024, 09:12:13 +301ms
+63ms ║Garden Pot is 51%
16/12/2024, 07:21:58 +534ms
+63ms ║Garden Pot is 50%
16/12/2024, 07:11:57 +838ms
+64ms ║Garden Pot is 51%
16/12/2024, 04:11:38 +305ms
+64ms ║Garden Pot is 50%
16/12/2024, 04:01:37 +285ms
+62ms ║Garden Pot is 51%
16/12/2024, 00:41:17 +606ms
+63ms ║Garden Pot is 50%
16/12/2024, 00:31:16 +327ms
+65ms ║Garden Pot is 51%
16/12/2024, 00:21:15 +269ms
+62ms ║Garden Pot is 50%
16/12/2024, 00:11:14 +515ms
+63ms ║Garden Pot is 51%
16/12/2024, 00:01:13 +397ms
+64ms ║Garden Pot is 50%
15/12/2024, 23:51:13 +259ms
+69ms ║Garden Pot is 51%
15/12/2024, 23:41:12 +237ms
+63ms ║Garden Pot is 50%
And during this time the "AD" reading of this sensor didn't change.
This is unneccesary. Even at 3 minute intervals my.l hub has very low usage. So.at 10 .min intervals it would be no issue. recommend you look into hatever else is going on with your hub. It.may be 35% of hub usage but that is probably.
only 2%. Total usage.
Here is one of my stations .7% of .4% so.bassically nothing
Yeah, like @kahn-hubitat , my suspicion would be that the usage is not something to be concerned about, it is more likely the hub isn't doing much, but the EcoWitt driver is doing a larger proportion of not much. It's been a while since I looked at the stats data, but there can be a bit of a trick to interpreting the figures sometimes. It can be a case of diminishing returns with respect to the time and effort required to squeeze minor to no improvements in performance at times. Not to say it is something I don't want discussed here, but if you do want to pursue it further a separate topic may provide a broader group of people responding, but I don't think it is something you need to worry about.
Re the readings ... I can't remember if I asked, but do these match what you see in the EcoWitt mobile app or other EcoWitt interfaces?
The CPU s not the issue, I agree with you, and I'm sorry for mentioning it, it was poorly chosen.
My issue is that the Ecowit is calculating the humidity readings from the 4 soul sensors incorrectly, and sending this nonsensical data to the hub, which I am hoping to avoid.
I don't think the Hubitat should be processing this bad data, that's why I have maxed reporting to 10 minutes to try to mitigate, I would prefer 2 minutes.
Whereas the AD readings from the soil sensors, I can see in the app, is correct, I can actually see what the soil is "doing", how it responds to moisture, whereas the humidity readings are back and forth, jumping around very unusually.
Yes the readings are the same in app as in Hubitat.
If there was a way just to get AD readings from the aecowitt it would be more reliable.
No harm in mentioning it, always happy to see people asking questions, no matter what they are.
Presuming there is a slight typo.... I am wondering if there could be a slight misunderstanding in what the humidity readings is .. are you referring to the one linked to the gateway? The ambient sensor? That is a separate sensor to the soil sensors.
No, I'm talking about the soil sensors, specifically the soil sensor humidity reading that the gateway does. Which is not reliable. I'm trying to be as susinct as possible by just talking about the soil sensor humidity calculations, so I don't want to bring in battery readings or temp readings from the gateway or pressure readings that fluctuate randomly also because someone will discuss those. So to try to make my point clearer, I'm talking about the soil sensor. The soil sensor is a capacitive probe that reads voltage and sends that pure data, only if there is moisture change, however if there is no moisture change, it's not raining, it's been dry for a while, it doesnt send data. However the Ecowitt gateway decides inspite of this, the humidity percentage has changed by 1% or 2% and sends that to the Hubitat which I regard as spamming and unecessary.
To give you some background for many years I've been using the maestro @iharyadi's soil sensor solution. Which was very reliable, essentialy the same capacitive moisture sensor, and sent reliable voltage readings. I would prefer just to receive the voltage readings from the soil sensors and calculate the humidity percentage myself, because at the moment I'm not able to look at or understand the data the Ecowitt thinks is the humidity percentage, I can live with it, but it's not good for my OCD.
Made me assume you were still referring to the ambient sensor readings as well, or you were thinking this was somehow an average of the soil sensors readings. Bur happy to put that to one side for now.
I haven't changed the batteries in my soil sensors for some time, so mine are not currently reporting and I cannot look at what the AD value represents. My expectation is the driver simply receives a percentage reading from the gateway, but I am not sure.... Not without looking at the code in more detail.
Ultimately if you could turn on some more detailed logging on the gateway in HE and provide the logs, that may provide some more information. You are welcome to post here or send me a PM if you prefer.
I've been having a play, when you factory reset the Gateway and connect via it's WIFI network it has a local LAN interface on 192.168.4.1, so the app isn't actually needed at all. As I mentioned, the Ecowitt WH51 Soil Sensor does not natively expose the raw AD (Analog-to-Digital) readings through the Ecowitt gateway. Instead the gateway performs an internal conversion from the sensor's raw ADC value into a percentage soil moisture reading, that gets sent in the payload. To counter the "jumpiness" of the humidity messages I use WebCoRE to ignore changes of 1%. With this Condition that goes in the Expression field..
ok, i finally got around to updating my ws90 at the condo to firmware 1.4.8
As mentioned above by @eduardo there are some new attributes coming out:
namely srain_piezo which signifies if it is raining,
and ws90_ver which signifies the firmware version of the ws90 (not to be confused with the receiver firmware)
and finally ws90_cap which is the capacitor voltage which from my reading should be between 4.0 and 5.0
Anyway i added those 3 as attributes in my custom version of the driver, as capacitorVoltage, raining, and ws90Firmware.
it sticks them on the rain device for rain and the wind device for the other two.,
i will do a pull request and add the code to the stock versions in a few days.,
