Hi Greg et al.,

My soil moisture sensors are Ecowitt WH51.
Online I found their specs:
Moisture Range: 0 - 100 %
Resolution: 1 %

(so, it is % and not centibar?!)

I do not understand how my moisture graph displays values after the decimal
point.

I use the https://github.com/matthewwall/weewx-mqtt weewx mqtt extension
version 0.24 for broadcasting the Ecowitt GW 1100 data thru a local
mosquitto server into Belchertown skin.

Is there another weewx mqtt extension which is recommended to be used as a
publisher?

TIA,
Stefan

On Mon, Oct 9, 2023 at 4:37 PM Greg Troxel <[email protected]> wrote:

> Stefan Gliessmann <[email protected]> writes:
>
> > Using the inspect function of google chrome, I see this error message:
> >
> > *MQTT: 2023-10-09T16:01:34+02:00: mqtt Connection Lost: AMQJS0005E
> Internal
> > error. Error Message: minimumFractionDigits value is out of range.,
> Stack
> > trace: No Error Stack Available*
> >
> > I can see that the GW1100 is broadcasting the soil moisture values as
> > integers in the EcoWitt app as well as the gw1000 weewx driver:
> >   *'soilmoist1': 12, 'soilmoist2': 20, 'soilmoist3': 17, 'soilmoist4':
> 26*
>
> mqtt is strings.   It is not integers or floats.
>
> It is  perfectly normal for a receiver to try to parse a number from
> that string, but I would say that "17" is a perfectly reasonable number
> and that objecting to it because it is not "17.0" is a bug.  If that's
> what is going on of course!
>
> > I can also see that user.mqtt sends the values as fractions adding ".0"
> to
> > the values from gw1000 driver:
> >   *'soilMoist1_centibar': '12.0'*, 'wh51_ch1_batt': '1.6',
> 'wh51_ch1_sig':
> > '4.0', *'soilMoist2_centibar': '20.0'*, 'wh51_ch2_batt': '1.6',
> > 'wh51_ch2_sig': '4.0', *'soilMoist3_centibar': '17.0'*, 'wh51_ch3_batt':
> > '1.6', 'wh51_ch3_sig': '4.0', *'soilMoist4_centibar': '26.0'*,
> > 'wh51_ch4_batt': '1.6', 'wh51_ch4_sig': '4.0'
> >
> > In my graph for soil moisture I can see "sometimes" fractions, too,
> which
> > are not ".0" (as it is archive data and not loop data?):
> > [image: Screenshot 2023-10-09 at 16.25.08.png]
> >
> > Any clue what I need to adjust?
>
> First you need to find out what the resolution of the sensor really is.
> (Very cool that is it moisture in pressure instead of the usual %.)
> Then  a publisher might need to adjust.  Separately the subscriber
> should probably be fixed too.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACXWM9TZtZgyLjaMiECvfpj%2BSrb1ALf5JbRKzuDA79cvMQVXCw%40mail.gmail.com.

Reply via email to