Couple of CMX questions if I may - can't quickly spot definitive answers:
1. Is there any reason that CMX can't be used to download archive data from weatherlink.com for a non-local station? This is a scenario where a user might have a station at another location uploading to wl.com, which provides access to current data and basic access to historic data.
But users do sometimes want more flexibility to handle the historic data than wl.com currently provides. Would CMX fit the bill here, despite not having any local data to download? Are there any limitations on the station type that would be configured? Obviously EM data wouldn't be suitable (because the potential sensor mix couldn't be handled by CMX) but what about say Connect data, which is AFAIAA almost identical to standard VP2 data, accessed via the v2 API?
If the answer's no or don't know then don't worry - it's not a feature request - I'm just looking at possible solutions that might provide extra archive data-handling for non-local stations.
2. (I'm guessing the answer is no to this, but maybe wrongly?) Can CMX support multiple stations, eg running multiple instances of CMX? Again this is not a common scenario so no big deal, but does crop up sometimes. If it is possible then can the two (or more) instances still run as a service?
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
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
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
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
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Couple of CMX questions
Moderator: mcrossley
- mcrossley
- Posts: 14388
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Couple of CMX questions
1) In theory yes, but I would say only for WLL stations (maybe VP2) - the wl.com API v2 is *very* comprehensive and uses different catalogue types for every sensor type. Cumulus will only be looking for ISS and WLL type sensors associated with a WLL.
I do not know for certain if it would work though if it cannot contact the sensor locally, I'd have to see it it does the "find it" check for the station before the history data download or after.
It is something that could be considered though - an "offline" wl.com station - that could probably be extended to WU and possibly others too, for these "Internet stations" that only upload to fixed services and do not provide local data access. It would be down the priority list at the moment though.
2) Yes. You can multiple copies of Cumulus, you just have to...
a. Disable the "Prevent multiple copies running" option.
b. Start each instance on a different network port using the -port NNNN command line parameter.
I do not know for certain if it would work though if it cannot contact the sensor locally, I'd have to see it it does the "find it" check for the station before the history data download or after.
It is something that could be considered though - an "offline" wl.com station - that could probably be extended to WU and possibly others too, for these "Internet stations" that only upload to fixed services and do not provide local data access. It would be down the priority list at the moment though.
2) Yes. You can multiple copies of Cumulus, you just have to...
a. Disable the "Prevent multiple copies running" option.
b. Start each instance on a different network port using the -port NNNN command line parameter.