have you tried to find where it HAS put the file (if anywhere)?? sudo find / -iname "gauge*"
On Tuesday, 24 April 2018 01:06:16 UTC+3, A.J. Burnett wrote: > Hi Gary... > > I never did THANK YOU for all your help with this issue from months ago. I > got it all to work very well, thanks to your assistance! It is much > appreciated! > > I'm working on another station/page for work now and have a similar but > different issue that I'm hoping you can assist with. > > I have installed the realtime gauge data extension on a RPi. The same Rpi > is hosting the intranet page to display the data. I've set up the guages.js > script to write to the directory I need gauge-data.txt to go to, but the > file is not making it there. > > weewx root = /home/weewx > skin = [weewx root]/skins/ss > HTML root = /var/www/html // This is where I'm hoping to get the realtime > gauge-data.txt file to, every 2.5 seconds or LOOP packet generation. > > My syslog is attached as a .txt file (shows the file being generated, but > no more info available). > > Any thoughts? > > Thank you once again! > > A.J. > > > > > > On Saturday, February 17, 2018 at 8:49:11 PM UTC-5, gjr80 wrote: >> >> Sorry this has taken a couple of days, unfortunately there is more to >> life than weeWX :) >> >> Some background for others who stumble on this. >> >> If you are using the SteelSeries Gauges skin to produce gauge-data.txt >> then you can use the normal weeWX FTP or Rsync reports to upload >> gauge-data.txt; gauge-data.txt is only generated once per archive >> interval so there is no need to upload it any more freuently. If you are >> using the Realtime gauge-data (RTGD) extension which can generate >> gauge-data.txt as often as once per loop period, the weeWX FTP and Rsync >> reports can still be used but they will still only upload gauge-data.txt >> once per archive interval. If your web server is the same machine as your >> weeWX server the issue can be addressed by having the RTGD extension save >> gauge-data.txt to an approparite directory accessible by the web server. >> If your web server is remote to your weeWX machine one approach is to have >> the RTGD extension transfer gauge-data.txt to your web server via HTTP >> POST. You could also conceivably have some external method of transferring >> the file by FTP or RSYNC; CRON based transfers are of limited use as CRON >> has a 1 minute 'resolution'. WeeWX has no builtin mechanism for >> transferring files every loop period; it only has the report based transfer >> reports that work on an archive interval period. >> >> To have the RTGD extension transfer gauge-data.txt to your web server >> via HTTP POST refer to the section Using HTTP POST to transfer >> gauge-data.txt to a remote server >> <https://github.com/gjr80/weewx-realtime_gauge-data/wiki/User's-Guide#using-http-post-to-transfer-gauge-datatxt-to-a-remote-server> >> >> in the RTGD extension User's Guide. Bear in mind this was wrritten about 8 >> months agao, I have reviewed it quickly thismorning and believe it is still >> correct, though if you find any issues please let me know. >> >> Gary >> >> On Sunday, 18 February 2018 00:57:30 UTC+10, WxManAJB wrote: >>> >>> So, I’ve got data being produced, but getting that near real time >>> gauge-data.txt file to my server at a rapid fire interval is proving >>> elusive. I’ve tried getting the rsync skin running by producing a key pair >>> for ssh and using those credentials in the skin setting of Weewx.conf, but >>> it’s not sending anything and nothing is showing up in my log reflecting an >>> attempt to do so. >>> >>> Any ideas? >>> >>> Thanks again for all your help! >>> >>> A.J. >> >> -- 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.
