Cumulus Support

Hi Hans
I found some time to add UserReports to my CumulusUtils webpage http://leonas.ddns.net/Wetterstation.Su ... CumulusMX/.
As I could stand on the shoulders of giants like Hans https://meteo-wagenborgen.nl/ and AndyK https://lalouettegoreyweather.uk/?dropd ... Report.txt I managed that with the wiki https://www.cumuluswiki.org/a/UserReports, https://www.cumuluswiki.org/a/Full_list_of_Webtags and the forum entry viewtopic.php?p=160007#p160007 without big issues.

Only some <webtags> seem not to work in my UserReport pages CURPTSystemOverview.txt and CURPTSystemAlarms.txt with my GW2000 that is connected as station via IP to my CumulusMX Windows PC (and not via Ecowitt HTTP custom server).
I activated also the corresponding CumulusMX Alarm Settings in the CumulusMX console (but could of course not find entries there for FirmwareVersion and IsSunny).

I wanted to ask you (as you also use Ecowitt GW1000), if the following CumulusMX webtages

• are supported by Ecowitt GW1000/GW2000 at all

• or only supported via Ecowitt HTTP custom server

• or only supported by newer CumulusMX/CumulusUtils versions.

The following webtags are affected:

• <#EcowittReception> (this might depend on at least CumulusUtils version 6.21.5),

• <#EcowittFirmwareVersion>, (but <#GW1000FirmwareVersion> is working fine also with GW2000),

• <#StationFreeMemory>,

• <#ExtraStationFreeMemory>,

• <#StationRuntime>,

• and <#IsSunny> (although e.g. <#IsRainingAlarm> is working fine)

regards
leo
I know that I am not using the most actual CumulusMX/CumulusUtils versions 3.24.2 (build: 3235) and Version 6.17.3 and an uprade is on my to-do-list as I am interested in a couple of new features as MeteoCam Ecowitt HP10, CustomLogs, lighning sensor fixes and rain graph rain.vs.EVT

Hi Leo,

Congrats with the CURPT handling , when used to it it's not too complex is it?

Important to understand is that it is CMX which translates the webtags, it is not Cutils!

lse-cumulus wrote: ↑Sun 25 Feb 2024 7:42 pm Only some <webtags> seem not to work in my UserReport pages CURPTSystemOverview.txt and CURPTSystemAlarms.txt with my GW2000 that is connected as station via IP to my CumulusMX Windows PC (and not via Ecowitt HTTP custom server).
I activated also the corresponding CumulusMX Alarm Settings in the CumulusMX console (but could of course not find entries there for FirmwareVersion and IsSunny).

I wanted to ask you (as you also use Ecowitt GW1000), if the following CumulusMX webtages

• are supported by Ecowitt GW1000/GW2000 at all

• or only supported via Ecowitt HTTP custom server

• or only supported by newer CumulusMX/CumulusUtils versions.

The following webtags are affected:

• <#EcowittReception> (this might depend on at least CumulusUtils version 6.21.5),

• <#EcowittFirmwareVersion>, (but <#GW1000FirmwareVersion> is working fine also with GW2000),

• <#StationFreeMemory>,

• <#ExtraStationFreeMemory>,

• <#StationRuntime>,

• and <#IsSunny> (although e.g. <#IsRainingAlarm> is working fine)

[...]

Yes, probably updating works best. I know some of these webtags have only been added recently but I do not know exactly which versions.
So update would at least make certain they will be translated.
Assuming you updated CMX and CUtils:

(Thought to be correct, not 100% sure)
<#EcowittReception> => works for API and HTTP
<#EcowittFirmwareVersion> => works for API and HTTP (pretty sure the latest version fixed a bug here)
<#StationFreeMemory> => works for API and HTTP
<#ExtraStationFreeMemory> => works for HTTP (could try API?)
<#StationRuntime> => works for HTTP only
<#IsSunny> Should work always if you have a solar sensor (which is the case with the GW2000) but I never used it so not sure.

If you are having problems please ask in the CumulusMX forum because webtags are a CMX feature.

CUtils simply passes the user reports on to CMX to translate the webtags. Another possibility would be to do it outside the CUtils system as Extra Webfiles within CMX.

Hope the above helps.

Hi Hans,
thx. As always your input is appreciated. I will focus on CumulusMX and especially check the local file WebTags.txt that CumulusMX produces at startup to show all supported <webtags> ob the built/installed version.

I checked the CumulusMX release Notes https://github.com/cumulusmx/CumulusMX/releases,
and almost all my missing <webtags> are introduced in later CumulusMX versions. So I have to upgrade my CumulusMX release to get these webtags working. From my POV this forum topic under CumulusUtils can be closed.
Only for <#isSunny> webtag I have not yet found a good explanation, but I will check on CumulusMX forum after my upgrade

Ok.

Hi,

Only for <#isSunny> webtag I have not yet found a good explanation, but I will check on CumulusMX forum after my upgrade

I couldn't find it in the WiKi now but: <#IsSunny> returns a 0 if Cumulus determines no sunshine, and 1 if Cumulus determines sunshine (needs solar sensor).

In my Custom Log Data Content settings I have> Is Sunny: <#IsSunny>, Hrs: <#SunshineHours>,
CustomLog.txt data output is> Sunny: 1, Hrs: 5.4,

Enjoy,
Paul

This is a javascript from my page (Weather Blues template) to convert the 0 or 1 to text:

thx Paul,
my problem is that the <#isSunny> webtag always returns 0 and never 1 in my installation, although I do have a solar sensor and my CumulusUtils webpage shows values for sun hours, UV index, ... and the other sun related webtags all show values <> 0 and work fine: <#SunshineHours>, <#UV>, <#SolarRad>, <#Light>, <#solarTH>, <#UVTH>.
I was wondering if <#isSunny> was introduced in later CumulusMX releases (>build 3225) )or how this tag is calculated by CumulusMX under which preconditions (e.g. at least a certain amount of SolarRad or at least sun shine hours > 1 hour, ...) or if this tag is not working with Ecowitt solars sensors at all (WS90, WS68, WS2910/WH65).

I was wondering if <#isSunny> was introduced in later CumulusMX releases (>build 3225)

Firstly the webtag is #IsSunny with capital I and it has been in Cumulus right from the beginning in Cumulus 1.

I must admit my PHP cumulus webtags say it applies to Davis and Oregon WS's so I wonder if the code only checks on those stations? Only Mark can tell us that!! However, #IsSunUp is registering 1 at the moment and we are currently overcast, so I wonder if the sun has to actually shine before #IsSunny registers 1.

As pointed out the tag is #IsSunny, the capitalisation is important.

It works for any station with a solar sensor - Davis Cloud, Davis VP2, Davia WLL, Ecowitt Cloud, Ecowitt GW1000, Ecowitt HTTP, Ambient, Tempest, WMR200, Fine Offset.

The value is true whenever the conditions to cause sunshine hours to increment is true.

Mark, what are "the conditions to cause sunshine hours to increment" as I think this maybe the cause.

Here it is cloudy and misty with occasional sunny spells and my sunshine hours 12.50 were
At 13.00 with what I thought about 10 mins of sunshine the tag was still the same. Perhaps we need sunshine hours to 2 decimal places to trigger it?

It whatever you set in Station Settings > Solar

Do you think 0.3 hrs sunshine is too high or too low?

My Sun Threshold (percent): is the default value of 75%.

Because the day started off misty and then turned cloudy with very small periods of sunshine it is difficult to say!!

I presume a lower Sun Threshold would record more sunshine, but I assume you set that as the default because that is a standard somewhere? I am using Ryan-Stolzenback, but only because it set it to that when I got the HP2551 with the Solar sensor, would Bras be better (although that still uses 75%).

The other element Solar minimum (W/m2): is set to 30 again the default value.

Every sensor is slightly different. The values need to be tuned to your sensor - there have been long threads (one ongoing I think!) on the main forum about doing this. Ideally it is done around mid-summer and mid-winter, then you can tune the two settings, and MX interpolates between them for the rest of the year.

I found the Bras curve fitted my Davis sensor slightly better than R-S, but again it is probably sensor dependent. I know Ecowitt use different sensors in each station type and have changed the sensor design within the same station over time.

So my Sunshine hours has incremented to 0.4 BUT the #IsSunny is still 0 (zero)?