I have been running very standard weeWX on Raspberry Pi -Vantage Pro, all 
fully solar powered, in Australian bush for 2 years, connected to internet 
via cell phone /wireless router. Using a data plan that gave me a true IP 
address, after initial difficulties,  I was able to initiate web access to 
the Pi/weeWX  web server consistently. (Thank you, Tom). 


Unfortunately data usage plan was costly, so recently I reconfigured weeWX 
to ftp html files to my office server every 2 hours, about 180kB from 
memory, using a different phone data plan, but losing my ‘real’ inbound IP 
address- I can no longer SSH in. This too has been reliable, and a lot more 
economical. My office server is on fixed internet connection with static 
IP. I am experimenting adding proprietary sensors, occasional picture 
image, but also uploading  the database weekly as backup. So far no issues 
with standard SD card.


I am about to set up another remote, duplicate system, but wondering if I 
can do data transmission any more efficiently.  Eg, I note in other forums 
and weewx docs,  if I understand correctly, outputting data via skins, and 
then sending say text records, to another weewx running in my office, 
although my efforts installing weewx so far on my lan synology NAS box have 
not been successful. 


Does anyone think  implementing this would effectively be much more data 
efficient compared to my current approach of ftp of html files? Would MQTT 
have a fit here? I can live with the 2 hourly update and current data usage.

Regards.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to