[weewx-user] Re: Realtime Gauge-Data Extension 0.2.9 'gauge-data.txt' Issue

No, I didn't know about pypehem. I will install it. Thanks. Bob On Friday, March 17, 2017 at 5:41:14 PM UTC-7, gjr80 wrote: > > Do you have pypehem installed ? If > pyepehem is not installed the theoretical solar max cannot be calculated > and it is set to 0. I

[weewx-user] Re: wee_database --update fail

On Friday, 17 March 2017 21:54:36 UTC+10, Eelco F wrote: > > > So, after this I now have archive_day_wind, archive_day_windSpeed, > archive_day_windGust, archive_day_windGustDir, archive day_windDir. > > In my overview I used to have a line: $alltime.wind.max > ($alltime.wind.gustdir) at $alltime

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.9 'gauge-data.txt' Issue

Do you have pypehem installed ? If pyepehem is not installed the theoretical solar max cannot be calculated and it is set to 0. I thought it was listed as a pre-requisite but it appears not. 0.2.10 only adds the ability to import the scroller text from a file.

[weewx-user] Realtime Gauge-Data Extension 0.2.9 'gauge-data.txt' Issue

"CurrentSolarMax" is always set to zero in "gauge-data.txt" instead of to the daily solar maximum value, which causes the 0 to 100 range on the "Solar Radiation" gauge to always be painted red. I just noticed 0.2.10 has been released, but haven't installed it yet. Bob -- You received this mes

Re: [weewx-user] Vangtage driver, CentOS 6.8 i686, python 2.6.6., weex 3.7.0 : import of driver failed: zero length field name in format

Not a lot to go on here. Nothing in weewx uses the function str.format(), so I'm not sure what is creating this exception. Weewx should run on Python v2.5, v2.6, or v2.7. Could you please try running weewxd directly from the command line ? I

Re: [weewx-user] WMR200-reception can not be improved - What station should I replace it with?

If you get some really small ferrie core blocks then these might reduce interference over USB-cable. Not much space to fit them though. Also, if possible, clock-down the RPi CPU. It might help (unless it is the USB-circuit that causes it) -- You received this message because you are subscribed

Re: [weewx-user] WMR200-reception can not be improved - What station should I replace it with?

I also added this "mechanical" antenna amplifier: http://www.the-lighthouse.se/eng/teknik/antenn-amp/antenn-amp.html It is in swedish but just take some solid copper wire and remove the isolation. It improved my reception a bit more but looks ugly. Now, my motto is "Form follows function" so it

[weewx-user] Vangtage driver, CentOS 6.8 i686, python 2.6.6., weex 3.7.0 : import of driver failed: zero length field name in format

engine: Loading station type Vantage (weewx.drivers.vantage) Mar 17 19:53:57 weewx[1915]: import of driver failed: zero length field name in format () Mar 17 19:53:57 weewx[1915]: engine: Unable to load driver: zero length field name in format Mar 17 19:53:57 we

Re: [weewx-user] wee_database --update fail

Daily summaries without corresponding archive records is definitely an undefined situation, so wee_database probably did the right thing by raising an exception. But, I'd like to know how it came to be. Did you (Eelco) delete some rows in the archive database? -tk On Fri, Mar 17, 2017 at 2:27

[weewx-user] Re: RFComm problem

On Friday, March 17, 2017 at 11:27:33 AM UTC-4, mwall wrote: > > since python is not really multi-threaded, the separate thread that > monitors the usb transceiver could be dropping the sync (comms with the usb > transceiver and across the rf connection are extremely sensitive to timing). > > On

[weewx-user] Re: Cannot establish comms over MQTT. Weewx configuration file and syslog provided.

I found the problem. Apparently I had to subscribe to /loop from the MQTT client. Thanks Matt -- 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+unsubsc

[weewx-user] Re: WindRose data file format

Ask and ye shall receive. Thanks Garyworking now. On Friday, 17 March 2017 07:34:09 UTC-4, gjr80 wrote: > > Try v0.2.10 > > Gary > -- 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

[weewx-user] Re: weewxd says typeError 'float' object is not iterable

Where are the labels? Looks like reading the manual would do it. I see under Customization Guide - Appendix: Archive Types what appears to be the entire set of labels. Changed my labels to those and got past the TypeError and on to other problems. Got the latest problem fixed and weewx actual

[weewx-user] Re: weewxd says typeError 'float' object is not iterable

I suspect you need to either include a [[label_map]] stanza under [mypiweewxdriver] in weewx.conf or your data file needs to use weewx field names eg outTemp, windSpeed etc. The label map is described in the comments at the top of the fileparse driver file fileparse.py. It should look something

[weewx-user] Re: wee_database --update fail

Gary, My station is an Vantage Vue with data logger. After the error I put back a backup of the the old database, that was created in the night, and weex updated it from the datalogger. So that's not a problem. I did a dry run now, and it shows the same error. I tried your solution, and it ran w

[weewx-user] Re: weewxd says typeError 'float' object is not iterable

Below is the entire driver. I was using the archive database names which as far as I can see using Sqliteman have those names with no caps. It must mean that the archive and loop data don't have the same names. I change it easily enough. I see fileparse.py does have outTemp and outHumidity

[weewx-user] Re: WindRose data file format

Try v0.2.10 Gary -- 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/opto

[weewx-user] Re: WindRose data file format

I spoke too soon, it's not changing, so I guess will have to find a different way to do this. I'm also contemplating installing meteotemplate, so this requirement may not be so critical. Although for a dedicated weather meter display I have on my small raspberry pi it would be nice to have th

Re: [weewx-user] Re: Live Steel Series Gauges

There is one major problem and very good reason why I always want to use Rain as sum. Think about what happens when your station is offline for a short while. Temperature - not a big deal Humidity - not a big deal ... just small gaps Rain - major issue because the totals are not going to add up

Re: [weewx-user] Re: Live Steel Series Gauges

Luc we certanily can add things to the api, but only as long as it does not require any additional MySQL queries On Friday, March 17, 2017 at 12:07:47 PM UTC+1, Luc Heijst wrote: > > Well, I think I found a solution. Let meteotemplate do the aggregation of > 'rain_data_this_period' to 'rain_tota

Re: [weewx-user] Re: Live Steel Series Gauges

Well, I think I found a solution. Let meteotemplate do the aggregation of 'rain_data_this_period' to 'rain_total_since_midnight'. 1. Dump the complete mysql or sqlite database with the standard commands 2. Import this dump file in meteotemplate and choose option 'aggregate rain' *** *

Re: [weewx-user] Re: Live Steel Series Gauges

Thanks Andrew, What I need is a dump of the total database to a .txt or other useful format. To be used once to input historical weewx data in meteotemplate via a data import. I know how to program it, but don't know if there is a mysql statement which can do the same. The problem is the aggreg

[weewx-user] wee_database --update fail

Hi, Put simply --update will weight a number of daily summary fields according to the interval used in the archive. Judging by the error trace provided you appear to have daily summary records for days that have no records in your archive. I think you have 2 options: - The quick fix is to run

[weewx-user] wee_database --update fail

After upgrading to 3.7.0 I tried to update the database becuase of the max_wind issues. Running wee_database --update results in. Using configuration file /etc/weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_sqlite' The update process does not affect ar