Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Please DO NOT use this to publish your entire wish. This Forum is for specific suggestions to enhance the usability of Cumulus MX for all users, NOT your personal requirements. Please check this forum and the rejected forum to make sure you are NOT posting a DUPLICATE suggestion. It will be heavily monitored by Admin and Mark Crossley to determine the feasibility and the difficulty of the suggestion. Those Topics that are deemed inadmissible will moved to the rejected Forum. The remaining Topics will be the Accepted list of future developments, and when our voluntary development group adds it to a build, the build number will be added to the Topic title.
HansR wrote: ↑Mon 08 Feb 2021 8:40 am
And beyond that: nobody reacted on my remark above about:
HansR wrote: ↑Tue 02 Feb 2021 10:28 am
device independent Air Quality datamodel is needed before adding more of that type of devices.
Do I have to interpret this lack of reaction as 'the datamodel will just expanded be with every AQ device'. That seems weird as the meteo stations do share tables and fields. Multiple meteo stations require multiple instances of CMX. Should multiple AQ stations not require the same?
It does! But implementing this will probably mean dropping device specific data and like the weather data just storing common attributes. If anybody wants to kick off a discussion on the attributes to store then that could be beneficial.
This topic split into a separate thread - viewtopic.php?f=36&t=18988
