Noticed this issue with a NanoSD/Envoy using Tx:2 (Standard VP2 ISS) uploading to WeatherLink.com via WeatherLink Cloud then when downloading back to WeatherLinkPC, Tx (Wind Tx) value is 1?
Downloading direct through the local network Tx value (2) is correct. Have not checked what occurs for Tx: 3 and above.
NanoSD => WeatherLink Cloud => WeatherLinkPC - Tx ID
Moderator: Mattk
Re: NanoSD => WeatherLink Cloud => WeatherLinkPC - Tx ID
Do you mean when reading back from the WL Cloud into Metebridge the station identifier (ISS, Wind, Soil, extra Temp, etc) is not reflected correctly?
This is to be expected as Meteobridge just takes all available data from WL Cloud and does not map this to the classical predefined sensor configurations. It is much simpler that way from a coding perspective. Does it harm somehow? I assumed it does not.
This is to be expected as Meteobridge just takes all available data from WL Cloud and does not map this to the classical predefined sensor configurations. It is much simpler that way from a coding perspective. Does it harm somehow? I assumed it does not.
Re: NanoSD => WeatherLink Cloud => WeatherLinkPC - Tx ID
It is the read back (download) from WeatherLink Cloud (WeatherLink.com) back into WeatherLinkPC.
There is probably no harm to anything apart from initially showing up as not the correct Tx ID and looking a bit odd but I suppose knowing now what it does probably won't raise questions.
There are probably 2 scenarios here, one where there is only one(1) ISS which could be set to any one of 8 Tx ID's and there won't be much confusion knowing that what ever the Tx ID is set (#1 to #8) download will always be Tx:1
The second is where multiple ISS's can be available and in particular for additional/separate/backup anemometers. Wind Tx in a typical WeatherLinkPC database indicates which anemometer is being used relative to or including the main/primary ISS (as such).
Mixing WeatherLink.com and WeatherLinkPC downloads for non Tx 1 ID's and separate anemometers was a bit misleading when first encountered. Can work around it now knowing what it does.
There is probably no harm to anything apart from initially showing up as not the correct Tx ID and looking a bit odd but I suppose knowing now what it does probably won't raise questions.
There are probably 2 scenarios here, one where there is only one(1) ISS which could be set to any one of 8 Tx ID's and there won't be much confusion knowing that what ever the Tx ID is set (#1 to #8) download will always be Tx:1
The second is where multiple ISS's can be available and in particular for additional/separate/backup anemometers. Wind Tx in a typical WeatherLinkPC database indicates which anemometer is being used relative to or including the main/primary ISS (as such).
Mixing WeatherLink.com and WeatherLinkPC downloads for non Tx 1 ID's and separate anemometers was a bit misleading when first encountered. Can work around it now knowing what it does.