Cumulus Support

Hi there,

I have a WS 1080 Fine Offset weather Station without any solar sensors. Well, I noticed that - in spite of the absense of any solar senors - my web pages as well as the local interface of Cumulus MX show pages for solar without any reasonible data input.

I thought, that I read recently, that this would automatically disappear with release 3025, but obviously it is not.

Don't know what to do about this - can I hide the wrong and superfluous readings somehow (?) or do I have to do something else (?) or is it simply a bug in CumulusMX which will be fixed later (?)

Wilfried

p.s.: I am asking this question also because I've noticed, that there is also the selection of "Fine Weather with solar" in the station Settings menu available...

For your web updates modify indexT.htm as per this comment in the file:
<!-- Solar data. If you don't have a solar sensor, you may wish to delete everything from here to the next comment
<tr class="td_temperature_data">
<td>Solar Radiation</td>
<td><#SolarRad>&nbsp;W/m&sup2;</td>
<td>Evapotranspiration Today</td>
<td><#ET>&nbsp;<#rainunit></td>
</tr>
End of solar data -->

I believe you can do something similar for MX dashboard.

Paul

deleted as answered by Steve

For the MX UI pages, one of the reasons for having the UI separate in MX is that users can modify and customise it to their own requirements (just as with the web pages). I may look at trying to do something automatically for the specific case of solar sensors at some point in the javascript. But I certainly never said it would be in 3025.

To remove the solar data from the dashboard page, for example, look for this code in index.html and remove it:

I believe Jacques DesRoches alternative PHP based web pages simply look to see if particular (those not available from all weather stations) values stay zero and if so decide those rows should not appear on the page the script generates concluding the weather station being used is not measuring that parameter. As Cumulus actually knows weather station type, it could make more intelligent decisions based on that. But surely it is only a low priority enhancement, simply because it can be done manually once, more efficiently than script code working it out each time?

sfws wrote:As Cumulus actually knows weather station type, it could make more intelligent decisions based on that.

The MX UI is actually just a web site anyway, so there's no difference. The modifications need to be done by the web page code, not by the MX 'server' code.

Hello All - thanks a lot for the hints and links. I will try to customize my web pages accordingly.
Sorry for not searching for that beforehand myself, but I was a little bit misled be the possibility to select "Fine Offset" and "Fine Offset with Solar Sensors" in the Station Settings menu of Cumulus MX. And then I took the wrong conclusions based on my imagination ... (sorry Steve)

thanks,

Wilfried

steve wrote:

sfws wrote:As Cumulus actually knows weather station type, it could make more intelligent decisions based on that.

The MX UI is actually just a web site anyway, so there's no difference. The modifications need to be done by the web page code, not by the MX 'server' code.

I have had a very busy day today and was rather vague re my gem of an idea earlier, but it was rather like

willyweather wrote: I was a little bit misled by the possibility to select "Fine Offset" and "Fine Offset with Solar Sensors" in the Station Settings menu

.

I do not know how Jacques does his PHP code but it might be "if <#SolarRad>, <#SunshineHours> and <#YSunshineHours> are all zero assume there is no solar sensor". I use 1.9.4 not MX but I suppose the question I was implicitly posing is "can either Cumulus version always work out whether a station has a solar sensor" and set a flag (web tag) accordingly.

For Fine Offset, Cumulus knows whether it is type 5 or type 7; similarly Cumulus knows only Davis can supply ET. What about other makes? If there is a logic test that can end up setting a boolean web tag as "Y" or "N" (alternatively "1" or "0"), then HTML web pages can decide whether to show or hide elements:
For example in "todayT.htm" (or "yesterdayT.htm") the solar row in the HTML could be adjusted to quote the new web tag: then adding CSS class definition in "weatherstyle.css": could hide the row for a station without solar sensor (web tag would be set to "N"). Conversely, the row would show for one with solar sensor because web tag would be set to "Y" and as class .solarY is not in the CSS there is no hide instruction. That sort of boolean HTML http://wiki.sandaysoft.com/a/Webtags_as ... rs_in_HTML can be applied to any web page be it UI or a standard Cumulus template.

I'm not saying that it can't be done; Cumulus 1 makes an attempt to do something appropriate on its main screen. In the case of MX, as the interface is a web site, it would require MX passing the required information to the web pages (by whatever means) so that (by whatever mechanism) the page could be updated.

Hi - it's me again

This time I'm thinking about the opposite ... I have extra HW now (Homematic), which provides a solar measurement result every 3 minutes (in "Flux").

Now I would like to feed this external measurement results somehow into the result files of CumulusMX so that these will be shown in my website
as if my weather station would provide this (which the WH1080 doesn't at all).

There are certainly more than one possibilities to get that. Maybe someone knows, which one would be best ?

Thanks for any hint.

regards,

Wilfried