Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

And just to close this off - this fixed my problems [[MQTT]] #This section is for the MQTT service setup server_url = mqtt://192.168.20.121:1883/ topic = weather/41south unit_system = METRIC binding = loop aggregation = aggregate

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

Log onto your broker from your phone or computer and subscribe to the topic and check for messages. Specifically the dateTime message is what changes the status. Also after a weewx restart it may take it a minute or two to populate all observations. -- You received this message because you

[weewx-user] Re: MQTT Metric vs Metricwx conundrum

...and it looks like the weewx-mqtt extension already has the ability to do just that - specify unit overrides. Taking a look at the weewx-mqtt code has this comment: [StdRestful] [[MQTT]] ... unit_system = METRIC # default to metric [[[inputs]]]

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

With those added fields it went to only publishing a record every 2 minutes or so, take them out and it's back to normal :/ Will try again. Is it case sensitive? On Wed, Nov 21, 2018 at 4:50 PM Pat wrote: > Log onto your broker from your phone or computer and subscribe to the > topic and check

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

Thinking about it the only other one will be the rain rate for Pats skin and MQTT Thanks for the help all - really really appreciate getting to the bottom of that one! On Wed, Nov 21, 2018 at 5:30 PM Colin Larsen wrote: > Boom! Thanks Matt, that was the problem. Also [[[inputs]]] needs to be

[weewx-user] Re: Move data files from /NOAA to new computer

You can just copy the NOAA files around do you mean that you have the old data ONLY in NOAA files, or also in the database?? if you had salvaged the old database and copied that to the new machine then weewx should have regenerated the NOAA files for you anyway on startup can you possibly

[weewx-user] Re: MQTT Metric vs Metricwx conundrum

The Belchertown skin extension allows users to specify which group units they want (much like the standard skin). I think this Issue on my GitHub repo (which Colin started) tries to a) get my own head wrapped

[weewx-user] Re: MQTT Metric vs Metricwx conundrum

Thinking about this further, I said: So would the answer be to have weewx-mqtt transmit in METRICWX and then > specify in the skin options group_wind = km_per_hour? Or would that cause > some miscalculations of wind data? This would be invalid because the base skin would probably do the

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

This is my MQTT section in weewx.conf, the skin just says "Connected. Waiting for data" and never gets any. I'll have a look for errors [[MQTT]] #This section is for the MQTT service setup server_url = mqtt://192.168.20.121:1883/ topic = weather/41south

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

Ok it works as far as changing the units goes but MQTT now only publishes every 5 minutes with the rest of the outputs "monthRain_cm": "0.0", "outsideAlarm1": "0.0", "windSpeed_kph": "0.0", "outsideAlarm2": "0.0", "forecastRule": "0.0", "windrun_km": "8.72121676916", "dayRain_mm": "1.64",

[weewx-user] MQTT Metric vs Metricwx conundrum

Hi all I'm putting this out on the Weewx forum as I'm not sure if there is a simple answer within Weewx for this problem. Down in NZ it is common to report rain in mm and wind speed in kp/hr In publishing MQTT data for Pats Belchertown skin this is causing an issue whereby if I set MQTT to

[weewx-user] Re: MQTT Metric vs Metricwx conundrum

Colin, US, METRIC or METRICWX merely defines the units used in the weeWX database, it really should have no bearing on the presentation of data. For example, in the weeWX Standard skin (and for that matter other skins that simply use the weeWX report system for generating reports) the weeWX

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

On Tuesday, November 20, 2018 at 10:45:39 PM UTC-5, Colin Larsen wrote: > > This is my MQTT section in weewx.conf, the skin just says "Connected. > Waiting for data" and never gets any. I'll have a look for errors > > [[MQTT]] > > #This section is for the MQTT service setup > >

[weewx-user] Move data files from /NOAA to new computer

I had a computer running Ubuntu 12.04 and weewx v3.2.1. It died. It stored its data in /var/www/weewx/NOAA/ I got a new computer and it has Ubuntu 18.04 and weewx v3.8.2 and the data is stored in /var/www/html/weewx/NOAA. If I move the data from the old computer to the new one, how can

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

+1 on Gary's comments. The right way to do this is to have the MQTT extension specify what unit system it is using to transmit values. Alternatively, it can hardwire in a unit system, then always send values in that system and only that system. Either way, the consumer of the data knows what unit

Re: [weewx-user] Re: MQTT Metric vs Metricwx conundrum

Boom! Thanks Matt, that was the problem. Also [[[inputs]]] needs to be all lower case Now - do I need to do that for all of the rain measurements? On Wed, Nov 21, 2018 at 5:21 PM mwall wrote: > On Tuesday, November 20, 2018 at 10:45:39 PM UTC-5, Colin Larsen wrote: >> >> This is my MQTT

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

debian9 + weewx3.8.2 + interceptor0.41 WH2950 it work very wall to upload pwsweather , Windguru , AWEKAS

Re: [weewx-user] Re: Belchertown 0.8

I think we're done with that testing, let 0.8 loose when you're ready On Wed, Nov 21, 2018 at 7:43 AM Colin Larsen wrote: > I'll get that testing done very shortly :) > > On Wed, 21 Nov 2018, 02:56 Pat >> I know I keep saying "soon", but every time I say that another bug pops >> up. Waiting

Re: [weewx-user] Re: Belchertown 0.8

I'll get that testing done very shortly :) On Wed, 21 Nov 2018, 02:56 Pat I know I keep saying "soon", but every time I say that another bug pops > up. Waiting for some final metric testing then I'll press the release > button! > > On Tuesday, November 20, 2018 at 2:06:25 AM UTC-5, John Clark

[weewx-user] Re: Belchertown 0.8

I know I keep saying "soon", but every time I say that another bug pops up. Waiting for some final metric testing then I'll press the release button! On Tuesday, November 20, 2018 at 2:06:25 AM UTC-5, John Clark wrote: > > Was just curious as to whether there is a timeframe or projected release

Re: [weewx-user] Second crash after 11 days

Two things. You don't have to run top as root, and if root's crontab you are editing is /etc/crontab, then the entry has to include the userID after the time spec, whereas a regular user's crontab entries do not. Chris -- You received this message because you are subscribed to the Google

Re: [weewx-user] Second crash after 11 days

On Monday, November 19, 2018 at 5:57:06 PM UTC-8, Steve2Q wrote: > > ...: once I save the crontab, why does a "new" one come up rather than the > edited version when I run sudo crontab -e again? If I go (as root) to > /etc/crontab.xx/crontab and open crontab with nano the lines I >