Couple of CMX questions
Posted: Wed 16 Dec 2020 12:00 pm
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?
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?