Re: [weewx-user] Re: Error reading lock file /etc/weewx/.weewx.conf.swp: Not enough data read
Close the editor and delete that swap file -- /etc/weewx/.weewx.conf.swp Then try opening weewx.conf again. ie; see if it's a problem with the swap file Which editor? nano? and vi (vim)? It won't matter if weewx is running or not. weewx.conf can be edited at any time. Any changes made won't take affect until you restart weewx . Cheers Glenn rorpi - read only raspberry pi & various weewx addons https://github.com/glennmckechnie On 7 April 2018 at 12:49, Kimberly Olsenwrote: > I should have added I have stopped WeeWX before editing but that makes no > difference > > -- > 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 weewx-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Error reading lock file /etc/weewx/.weewx.conf.swp: Not enough data read
I should have added I have stopped WeeWX before editing but that makes no difference -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Error reading lock file /etc/weewx/.weewx.conf.swp: Not enough data read
I've been attempting to get ftp working this morning and suddenly when attempting to edit weewx.conf, I get the message below This is when I am ssh-ing in from my Mac. When I attempt to edit the file directly on the pi, I cannot save it Any ideas ? Error reading lock file /etc/weewx/.weewx.conf.swp: Not enough data read -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] (offtopic perhaps) - nice review of different model SD cards
We get a lot of questions/issues here from Pi users regarding SD cards and what to buy (or not buy), so I thought I'd pass along a link to a review of current cards... https://www.jeffgeerling.com/blog/2018/raspberry-pi-microsd-card-performance-comparison-2018 I've had lots of luck with the SanDisk Extreme here on my zero/zeroW/pi3 cards -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Current wind graphic?
Thanks for the tips on color, Glenn. (Thanks also for providing a live example of how this looks.) I hope someone can come up with a more attractive color combination that provides enough contrast between wind and gusts, without clashing. Colors are not my forte. Just ask my wife. The other thing I'm less than happy with is the fatness of that gust pointer. It needs to be significantly larger than the wind pointer, so it's visible when they're pointing in the same direction. But it's really ugly. At present, I'm trying this as a substitute for the gust pointer definition: I think it's a slight improvement. On Friday, April 6, 2018 at 4:42:40 AM UTC-4, Glenn McKechnie wrote: > > For any one else who wants to tweak the colours to match their weewx > skin.conf of choice. > It's worth noting the hint that's in the [ImageGenerator] section of the > Standard skin.conf file > > # Colors can be specified any of three ways: > # 1. Notation 0xBBGGRR; > # 2. Notation #RRGGBB; or > # 3. Using an English name, such as 'yellow', or 'blue'. > # So, 0xff, #ff, or 'blue' would all specify a pure blue color. > > The existing skin colors are probably in the first format. > To use those values in the svg windrose they needs to be changed to the > 2nd format. > > Note the BGR -- RGB reversal and you'll be less likely to be surprised by > the weird results ;-) > > > > Cheers > Glenn > > rorpi - read only raspberry pi & various weewx addons > https://github.com/glennmckechnie > > On 6 April 2018 at 05:36, RobbHwrote: > >> I finally came to the realization that everything I wanted to do could be >> done with the Cheetah engine, and even learned a tiny bit of Python in the >> process. The following code, added to index,html.tmpl (or some other >> template) generates a crude compass rose with up to two directional vanes, >> one (in red) for gust direction and one (in blue) for wind direction. The >> length of the vanes is proportional to the corresponding speed value, on a >> logarithmic scale. >> >> #import math >>> xmlns="http://www.w3.org/2000/svg;> >> >> > stroke-dasharray="1,12.08" fill="transparent" /> >> > stroke-width="10" fill="transparent" /> >> > fill="transparent" /> >> > fill="transparent" /> >> > fill="gray">100 >> > fill="gray">10 >> > fill="gray">1 >> >> >> >> > fill="gray">N >> > fill="gray">S >> > fill="gray">W >> > fill="gray">E >> >> >> > fill="orangered">$current.windGust.formatted >> > fill="dodgerblue">$current.windSpeed.formatted >>#if $current.windGustDir.formatted != " N/A" and >> float($current.windGust.formatted) > 0 >>#set $wg = 65 - 18 * (1 + >> math.log(float($current.windGust.formatted), 10)) >> > transform="rotate($current.windGustDir.formatted 90 85)" /> >>#end if >> #if $current.windDir.formatted != " N/A" and >> float($current.windSpeed.formatted) > 0 >>#set $ws = 65 - 18 * (1 + >> math.log(float($current.windSpeed.formatted), 10)) >> > transform="rotate($current.windDir.formatted 90 85)" /> >>#end if >> >> >> >> This is set up to work with speeds measured in miles per hour. Some >> modification would be needed to make it work with other units. I hope >> someone will find it useful. Improvements welcome. >> >> > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Using WeeWxMQTT - problems
My goals is to add some sensors via MQTT to my stations which are all RPi 3 and use WeeWx 3.8.0. I am running the Mosquitto broker on the same RPi as WeeWx One station uses a Ultimeter 2100 driver -* can I use WeeWxMQTT as a service*? Other stations are a combination of OWFS and FileParse (using a python program to read from i2c bus on RPi). The station I am testing/developing (driving myself crazy) on now has WeeWxMQTT set as driver and OWFS as a service. It gives me errors like: Apr 6 09:22:44 ru-pi weewx[17871]: wxMesh: Working on queue of 0 Apr 6 09:22:44 ru-pi weewx[17871]: wxMesh: Sleeping for 5 This tells me that WeeWxMqTT is not finding the MQTT messages in the correct format. I am struggling with getting the esp8266 to output anything resembling the expected: TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 4.44,IRRA:12,BATV:974,PHOV:673,SYST:33.20,WIND: 0.0,WDIR: 0.0 (from the WeeWxMQTT wiki) The output is have managed to send is like this: * {"temperature":69.12} * *My Arduino sketch for the esp8266 is:* // use OWFS temperature sensor #include #include #include #include // Data wire is plugged into pin 2 on the Arduino #define ONE_WIRE_BUS 5 // Setup a oneWire instance to communicate with any OneWire devices // (not just Maxim/Dallas temperature ICs) OneWire oneWire(ONE_WIRE_BUS); DallasTemperature sensors(); // Update these with values suitable for your network. const char* ssid = "My Network"; const char* password = "MyPW"; const char* mqtt_server = "10.0.0.161"; char* topic ="weather"; WiFiClient espClient; PubSubClient client(espClient); long lastMsg = 0; float temp = 0; int inPin = 5; String dataString; char charBuf[150]; void setup_wifi() { delay(10); // We start by connecting to a WiFi network Serial.println(); Serial.print("Connecting to "); Serial.println(ssid); WiFi.begin(ssid, password); while (WiFi.status() != WL_CONNECTED) { delay(500); Serial.print("."); } Serial.println(""); Serial.println("WiFi connected"); Serial.println("IP address: "); Serial.println(WiFi.localIP()); } void reconnect() { // Loop until we're reconnected while (!client.connected()) { Serial.print("Attempting MQTT connection..."); // Attempt to connect if (client.connect("arduinoClient_temperature_sensor")) { Serial.println("connected"); } else { Serial.print("failed, rc="); Serial.print(client.state()); Serial.println(" try again in 5 seconds"); // Wait 5 seconds before retrying delay(5000); } } } void setup() { Serial.begin(115200); setup_wifi(); client.setServer(mqtt_server, 1883); pinMode(inPin, INPUT); sensors.begin(); } void loop() { if (!client.connected()) { reconnect(); } client.loop(); long now = millis(); if (now - lastMsg > 5000) { lastMsg = now; sensors.setResolution(12); sensors.requestTemperatures(); // Send the command to get temperatures temp = sensors.getTempCByIndex(0); Serial.println(temp); temp = (temp *1.8) + 32; // convert to F Serial.println(temp); if((temp > -20) && (temp <110)) dataString = String("{\"temperature\":") + temp + String("}"); dataString.toCharArray(charBuf, 150); { client.publish(topic,charBuf ); } } } *Any advice would be greatly appreciated. * -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Saltwater temp sent wireless to pi
Is there any other way to send the 1 wire signal wirelessly from the dock to the web? I guess a pi encased in rafters of boat house and run the wire down to water? How often would it report temp to the net ? Could I set it for every hour in weewx to PWS weather.. Can I make it private so that it won't interfere with PWS weather as it is water temp? Or do they allow custom Temps to be broadcasted? Thanks On Apr 6, 2018 10:16 AM, "mwall"wrote: On Friday, April 6, 2018 at 10:11:14 AM UTC-4, shane turner wrote: > > > If I were to get a cheap one wire sensor could I solder it into an old > accurite transmitter? > only if the acurite transmitter uses 1-wire as its protocol, which is not very likely you would have to find something that is pin-compatible with whatever sensor is on the transmitter -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Saltwater temp sent wireless to pi
On Friday, April 6, 2018 at 10:11:14 AM UTC-4, shane turner wrote: > > > If I were to get a cheap one wire sensor could I solder it into an old > accurite transmitter? > only if the acurite transmitter uses 1-wire as its protocol, which is not very likely you would have to find something that is pin-compatible with whatever sensor is on the transmitter -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Saltwater temp sent wireless to pi
Mwall If I were to get a cheap one wire sensor could I solder it into an old accurite transmitter? Thanks On Fri, Apr 6, 2018, 10:04 AM mwallwrote: > > > On Friday, April 6, 2018 at 9:38:09 AM UTC-4, shane turner wrote: >> >> Hello all >> >> I have an accurite that is currently set up on a dock sending data to >> greyscale receiver in the house.It then goes into pi via weewx and then to >> the web. >> >> I would like to add saltwater temp. Could I hack up an old accurite >> system that had been broken in storm as I would only need temp, no wind >> ect..? .. Then solder in a sensor and drop it off my dock and have it send >> data to a second accurite receiver. At this point would I need a second >> piece or can I run 2 usbs on 1 pi with weewx then out to wunderground ect? >> > > if you put two usb acurite consoles on a pi, you will not be able to tell > the difference between them. there is no serial number in the acurite usb > info, so no chance of writing a udev rule. you would have to probe each > console for data, then distinguish based on the actual temperature/wind > values. > > you might be better off buying a acurite bridge (aka smarthub). they are > discontinued now but should be available for about $40. an acurite access > could work too, but that would be a waste of money imho ($120). the bridge > reports the sensor's serial number, so you could use a single bridge to get > data from two or more 5-in-1 or tower sensors. > > or you could just get an SDR dongle ($20) and grab the data directly from > the sensor cluster. > > > >> Additionally what is a good sensor that won't attract barnacles? >> > > pretty much anything you put in saltwater will end up with stuff growing > on it. freshwater too, but different critters :) > > we use one-wire temperature sensors for this - they cost about $1 each, > potted in a stainless can. search for DS18B20 on amazone or ebay. then > you will need a 1-wire interface such as a usb-to-1-wire adapter. to > collect data, use the weewx-onewire extension as a service or as a driver. > > that is how we measure water temperature here: > > http://sailing.mit.edu/weather/ > > no barnacles, but it is briney with lots of slime and algae. you can > paint the sensor with a hard or ablative bottom paint. that should not > affect the temperature readings much. > > m > > -- > 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 weewx-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Saltwater temp sent wireless to pi
On Friday, April 6, 2018 at 9:38:09 AM UTC-4, shane turner wrote: > > Hello all > > I have an accurite that is currently set up on a dock sending data to > greyscale receiver in the house.It then goes into pi via weewx and then to > the web. > > I would like to add saltwater temp. Could I hack up an old accurite system > that had been broken in storm as I would only need temp, no wind ect..? .. > Then solder in a sensor and drop it off my dock and have it send data to a > second accurite receiver. At this point would I need a second piece or can > I run 2 usbs on 1 pi with weewx then out to wunderground ect? > if you put two usb acurite consoles on a pi, you will not be able to tell the difference between them. there is no serial number in the acurite usb info, so no chance of writing a udev rule. you would have to probe each console for data, then distinguish based on the actual temperature/wind values. you might be better off buying a acurite bridge (aka smarthub). they are discontinued now but should be available for about $40. an acurite access could work too, but that would be a waste of money imho ($120). the bridge reports the sensor's serial number, so you could use a single bridge to get data from two or more 5-in-1 or tower sensors. or you could just get an SDR dongle ($20) and grab the data directly from the sensor cluster. > Additionally what is a good sensor that won't attract barnacles? > pretty much anything you put in saltwater will end up with stuff growing on it. freshwater too, but different critters :) we use one-wire temperature sensors for this - they cost about $1 each, potted in a stainless can. search for DS18B20 on amazone or ebay. then you will need a 1-wire interface such as a usb-to-1-wire adapter. to collect data, use the weewx-onewire extension as a service or as a driver. that is how we measure water temperature here: http://sailing.mit.edu/weather/ no barnacles, but it is briney with lots of slime and algae. you can paint the sensor with a hard or ablative bottom paint. that should not affect the temperature readings much. m -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Run Davis Weatherlink an Weewx at the same time
hi, I continue using for testing weewx with wlink on my ubuntu, I had just update the wlink driver with wlink.0.14 and it's always ok . I try also to install in the same way weewx on a raspberry Pi 3 with the wlink driver but the file index.html is not created, I installed weewx on the RPI 3 using the Python utility setup.py and with Mysql database, I have install also un NTP server in the log I see these errors :" Internal errors detected .Catchup abondonned" and " cheetahgenerator skipping template ...: cannot find start time" I try to use "wee_device --clear-memory " but without effect See you the log file with debug= 1 Have you an idea what's wrong. Thanks Best regards Le vendredi 9 janvier 2015 20:31:53 UTC+1, Tom Keffer a écrit : > > Unfortunately, no. They both want to manage the state of the console. > > -tk > > Fat-fingered from my Android > On Jan 9, 2015 1:10 PM, "Fritz Lembke"> wrote: > >> Hi >> I would like to run weewx and the davis weatherlink software at the same >> time. But they seem to block each other. >> Can I change some setting to have them both running simultaneously? >> Thanks >> >> -- >> 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 weewx-user+...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Run Davis Weatherlink an Weewx at the same time
Sorry, this the logfile ! : Apr 6 14:25:47 raspberryApr 6 14:30:49 raspberrypi weewx[27588]: wlink: found 2 archive records since 0 Apr 6 14:30:49 raspberrypi weewx[27588]: engine: Internal error detected. Catchup abandoned Apr 6 14:30:49 raspberrypi weewx[27588]: Unknown archive type: 0x73 Apr 6 14:30:49 raspberrypi weewx[27588]: reportengine: Running reports for latest time in the database. Apr 6 14:30:49 raspberrypi weewx[27588]: reportengine: Running report StandardReport Apr 6 14:30:49 raspberrypi weewx[27588]: reportengine: Found configuration file /home/weewx/skins/Standard/skin.conf for report StandardReport Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] Apr 6 14:30:49 raspberrypi weewx[27588]: manager: Daily summary version is 2.0 Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template NOAA/NOAA-.txt.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template NOAA/NOAA--MM.txt.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template week.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template smartphone/temp_outside.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template mobile.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template smartphone/radar.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template smartphone/wind.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template month.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template smartphone/rain.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template year.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template smartphone/barometer.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template smartphone/index.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template index.html.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Skipping template RSS/weewx_rss.xml.tmpl: cannot find start time Apr 6 14:30:49 raspberrypi weewx[27588]: cheetahgenerator: Generated 0 files for report StandardReport in 0.09 seconds Apr 6 14:30:49 raspberrypi weewx[27588]: manager: Daily summary version is 2.0 Apr 6 14:30:50 raspberrypi weewx[27588]: imagegenerator: Generated 12 images for StandardReport in 0.70 seconds Apr 6 14:30:50 raspberrypi weewx[27588]: copygenerator: copied 0 files to /home/weewx/public_html Apr 6 14:30:50 raspberrypi weewx[27588]: reportengine: Running report FTP Apr 6 14:30:50 raspberrypi weewx[27588]: reportengine: Found configuration file /home/weewx/skins/Ftp/skin.conf for report FTP Apr 6 14:30:50 raspberrypi weewx[27588]: ftpupload: Attempting connection to ftp.meteo-senlis-tombray.com Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Connected to ftp.meteo-senlis-tombray.com Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/dayrx.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/daybarometer.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/dayuv.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/daywinddir.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/daytempdew.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/daywindvec.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/dayinside.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/dayrain.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/daywind.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/dayhumidity.png Apr 6 14:30:52 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/daytempchill.png Apr 6 14:30:53 raspberrypi weewx[27588]: ftpupload: Uploaded file /www/weewx/dayradiation.png Apr 6 14:30:53 raspberrypi weewx[27588]: ftpgenerator: ftp'd 12 files in 2.97 seconds Le vendredi 9 janvier 2015 20:31:53 UTC+1, Tom Keffer a écrit : > > Unfortunately, no. They both want to manage the state of the console. > > -tk > > Fat-fingered from my Android > On Jan 9,
Re: [weewx-user] IndexError: list index out of range
Attached -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. forecast.html.tmpl Description: Binary data -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. skin.conf Description: Binary data -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. [StdReport] # Where the skins reside, relative to WEEWX_ROOT SKIN_ROOT = skins # Where the generated reports should go, relative to WEEWX_ROOT HTML_ROOT = public_html/vantage # The database binding indicates which data should be used in reports. data_binding = wx_binding # Each of the following subsections defines a report that will be run. [[StandardReport]] # See the customizing guide to change the units, plot types and line # colors, modify the fonts, display additional sensor data, and other # customizations. Many of those changes can be made here by overriding # parameters, or by modifying templates within the skin itself. # The StandardReport uses the 'Standard' skin, which contains the # images, templates and plots for the report. skin = exfoliation [[[Units]]] Groups group_altitude = foot group_speed2 = mile_per_hour2 group_pressure = inHg group_rain = inch group_rainrate = inch_per_hour group_temperature = degree_F group_degree_day = degree_F_day group_speed = mile_per_hour [[SteelSeries]] HTML_ROOT = public_html/vantage/ss skin = ss [[[Units]]] StringFormats mm_per_hour = %.1f mile_per_hour = %.0f degree_compass = %.0f degree_C = %.1f inHg = %.3f mmHg = %.1f meter_per_second = %.1f meter = %.0f mile = %.1f uv_index = %.1f watt_per_meter_squared = %.0f percent = %.0f km_per_hour = %.0f inch = %.2f degree_F = %.1f knot = %.0f foot = %.0f hPa = %.1f mbar = %.1f inch_per_hour = %.2f mm = %.1f km = %.1f Groups group_temperature = degree_C group_altitude = foot group_pressure = hPa group_rain = mm group_rainRate = mm_per_hour group_speed = km_per_hour [[forecast]] HTML_ROOT = public_html/vantage/forecast skin = forecast [[exfoliation]] HTML_ROOT = public_html/vantage/exfoliation skin = exfoliation [[wdTesttags]] HTML_ROOT = public_html/vantage/WD skin = Testtags [[[Units]]] TimeFormats date_time_f = %d/%m/%Y %H:%M date_f = %d/%m/%Y Groups group_altitude = foot group_speed2 = km_per_hour2 group_pressure = hPa group_rain = mm group_rainrate = mm_per_hour group_temperature = degree_C group_degree_day = degree_C_day group_speed = km_per_hour [[wdPWS]] HTML_ROOT = public_html/vantage/WD skin = PWS [[[Units]]] Groups group_speed2 = km_per_hour2 group_temperature = degree_C group_pressure = hPa group_rain = mm group_rainrate = mm_per_hour group_speed = km_per_hour [[wdClientraw]] HTML_ROOT = public_html/vantage/WD skin = Clientraw [[wdStackedWindRose]] HTML_ROOT = public_html/vantage/WD skin = StackedWindRose [[[Units]]] TimeFormats date_time_f = %d/%m/%Y %H:%M date_f = %d/%m/%Y Groups group_speed2 = km_per_hour2 group_speed = km_per_hour [[wdSteelGauges]] HTML_ROOT = public_html/vantage/WD skin = SteelGauges
[weewx-user] Saltwater temp sent wireless to pi
Hello all I have an accurite that is currently set up on a dock sending data to greyscale receiver in the house.It then goes into pi via weewx and then to the web. I would like to add saltwater temp. Could I hack up an old accurite system that had been broken in storm as I would only need temp, no wind ect..? .. Then solder in a sensor and drop it off my dock and have it send data to a second accurite receiver. At this point would I need a second piece or can I run 2 usbs on 1 pi with weewx then out to wunderground ect? Additionally what is a good sensor that won't attract barnacles? Thanks -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: WeatherLinkIP disconnection from WeeWX frequently
> > :-) > fat fingers I found the IP address for the WLIP set to 192.168.0.20 instead of 192.168.1.20 -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: WeatherLinkIP disconnection from WeeWX frequently
> > Turns out it was not the socket error this time as revealed below, but for > some reason it is not posting to PWS not anywhere else. > *pi@raspberrypi*:*~ $* sudo tail -f /var/log/syslog Apr 6 06:25:02 raspberrypi CRON[2367]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Apr 6 07:17:01 raspberrypi CRON[2550]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 6 07:57:41 raspberrypi systemd[1]: Reached target Network is Online. Apr 6 07:57:41 raspberrypi systemd[1]: Starting Daily apt download activities... Apr 6 07:57:49 raspberrypi systemd[1]: Started Daily apt download activities. Apr 6 07:57:49 raspberrypi systemd[1]: apt-daily.timer: Adding 1h 37min 12.581498s random time. Apr 6 07:57:49 raspberrypi systemd[1]: apt-daily.timer: Adding 4h 17min 36.948143s random time. Apr 6 08:17:01 raspberrypi CRON[2733]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 6 09:17:01 raspberrypi CRON[2896]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 6 09:37:22 raspberrypi systemd[1]: Started Session c4 of user pi. -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.