[weewx-user] Re: Looking to replace my old Acurite 0203C weather station

I'm in the US I like Davis but those are super expensive. I like Ambient but haven't found any that I can buy that work with weeWX. I like this one http://a.co/d/1Lsy6fJ but it doesn't work with weewx. On Wednesday, December 26, 2018 at 6:58:55 AM UTC-8, Pat wrote: > > Not sure where you're

[weewx-user] Re: Belchertown Skin 0.8.1 released

Pat I seem to have missed something in setting up MQTT for the skin... I followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ except the SLL stuff since I wouldn't need it. weewx.conf [[MQTT]] server_url = mqtt://weewx:xx@127.0.0.1:1883/ topic =

[weewx-user] Re: weewx driver for acurite weather stations

If you mean the change log then yes that's quite likely. Drivers usually start life in a user's repo somewhere and once they are considered good enough (ie complete and stable enough) they may be added to the weeWX distribution if there is a sufficient audience. Quite possibly the January 2015

[weewx-user] Re: weewx driver for acurite weather stations

It looks like it does... Guess it never got updated in the logs. "insideTemp":"75.8 °F" On Wednesday, December 26, 2018 at 11:07:47 PM UTC-8, gjr80 wrote: > > > On Thursday, 27 December 2018 16:15:09 UTC+10, Scott Grayban wrote: >> >> To be clear the driver does NOT report inTemp at all ?

[weewx-user] Re: problem with wind in WMR300

Yes, there are speed values in the console. This before changing the template did not happen. I have activated the flag that you indicate to have the address at least. What can happen so that weewx does not receive those values? (I have rebooted the console). Greetings and thanks. El jueves,

[weewx-user] Re: weewx driver for acurite weather stations

On Thursday, 27 December 2018 16:15:09 UTC+10, Scott Grayban wrote: > > To be clear the driver does NOT report inTemp at all ? > The last sentence below seems fairly clear to me... On Friday, January 9, 2015 at 8:55:37 PM UTC-8, mwall wrote: >> >> folks, >> >> here is a driver for acurite

[weewx-user] Re: weewx driver for acurite weather stations

To be clear the driver does NOT report inTemp at all ? On Friday, January 9, 2015 at 8:55:37 PM UTC-8, mwall wrote: > > folks, > > here is a driver for acurite 5in1 weather stations. it should work with > any of the stations that have a usb port, including models 01025, 01035, > 01036, 02032,

[weewx-user] Re: rtl_433 and Weewxd config problems!!

Hi, Probably one for Matthew to look into, though I believe he has not had much time lately for things weeWX. In any case it would appear the SDR driver is not seeing an expected rain_counter value. You can work around the issue by editing sdr.py and changing line 487 from: if

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

I tried that but I still get the error. On Wednesday, December 26, 2018 at 5:15:50 PM UTC-8, Pat wrote: > > You need to make them an array. Something like: > > schema = schemas.wview.schema + [('appTemp', 'REAL'), ('windrun', > 'REAL')] > > > On Wednesday, December 26, 2018 at 6:27:53 PM

[weewx-user] Re: Belchertown Skin 0.8.1 released

# sqlite3 weewx.sdb_new SQLite version 3.16.2 2017-01-06 16:32:41 Enter ".help" for usage hints. sqlite> .schema archive CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL, `pressure` REAL, `altimeter`

[weewx-user] Re: Belchertown Skin 0.8.1 released

AHHH I got it It didn't dawn on me that this *schema = schemas.wview.schema + [('appTemp', 'REAL'), ('windRun', 'REAL')]* should be this *schema_apptemp = schemas.wview.schema + [('appTemp', 'REAL'), ('windRun', 'REAL')]* S stupid me... On Wednesday, December 26, 2018

[weewx-user] Re: problem with wind in WMR300

>From your logs it looks as though windspeed is not being received although wind direction IS being received. It looks as though your anemometer which is reading windspeed is not providing any output. Does your console show a windspeed?? Weewx will ignore wind direction if windspeed is zero

[weewx-user] Re: Belchertown Skin 0.8.1 released

Simple, delete the line: schema = user.extensions.schema_windrun We now put everything in schema_apptemp. Please post user/extensions.py Gary On Thursday, 27 December 2018 12:32:23 UTC+10, Scott Grayban wrote: > > The error is in the weewx.conf > > > [DataBindings] > > [[wx_binding]] >

[weewx-user] Re: Belchertown Skin 0.8.1 released

On Wednesday, December 26, 2018 at 5:19:35 PM UTC-8, gjr80 wrote: > > Hi Scott, > > On Thursday, 27 December 2018 09:19:11 UTC+10, Scott Grayban wrote: >> >> I tried adding 1 at a time but it deletes the previous one. Certainly you >> should be able to add more then just 1 right ? >> > > Do you

[weewx-user] Re: Belchertown Skin 0.8.1 released

The error is in the weewx.conf [DataBindings] [[wx_binding]] # The database must match one of the sections in [Databases]. # This is likely to be the only option you would want to change. database = archive_sqlite # The name of the table within the database

[weewx-user] Re: Belchertown Skin 0.8.1 released

Hi Scott, On Thursday, 27 December 2018 09:19:11 UTC+10, Scott Grayban wrote: > > I tried adding 1 at a time but it deletes the previous one. Certainly you > should be able to add more then just 1 right ? > Do you mean adding more than one field to your schema or more than one schema = entry

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

You need to make them an array. Something like: schema = schemas.wview.schema + [('appTemp', 'REAL'), ('windrun', 'REAL')] On Wednesday, December 26, 2018 at 6:27:53 PM UTC-5, Colin Larsen wrote: > > Maybe I did it wrong - but all I did was add the 2 new fields in the > original wview

Re: [weewx-user] Re: Belchertown DarkSky Alerts

I've made more changes to this. Now you have to opt in for the alerts. Erring on the side that alerts may not appeal or be available to everyone in every region, it's opt-in. Simply add forecast_alert_enabled = 1 to your skin options in weewx.conf. The alert description has a default truncate

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

Maybe I did it wrong - but all I did was add the 2 new fields in the original wview schema, which for me was hiding in /var/lib/weewx/schemas from memory and then did the --rebuild which ran perfectly. There may be a good reason for not doing that :) so I may not be giving you the best advice but

[weewx-user] Re: Belchertown Skin 0.8.1 released

I tried adding 1 at a time but it deletes the previous one. Certainly you should be able to add more then just 1 right ? On Wednesday, December 26, 2018 at 6:54:40 AM UTC-8, Andrew Milner wrote: > > I think You should probably only have one new schema specified - not two - > when you do the

Re: [weewx-user] Re: Belchertown DarkSky Alerts

Does that mean that I'll see alerts even though I only use the Darksky current conditions? Did you pop in the option to disable the alerts? On Thu, 27 Dec 2018, 09:49 Pat Sounds good! > > I should add another disclaimer that the showing and hiding of the alert > bar automatically without

[weewx-user] Re: Fine Offset WH-2650 and weewx

Hello Matt Yes I'm using the observer as a device-type. As you can see from the attached photo, the WH-2650 weather station has a sensor that independent of temperature, humidity and atmospheric pressure. This sensor is usually placed inside the house, and clearly the external sensor package

[weewx-user] Re: Belchertown DarkSky Alerts

Sounds good! I should add another disclaimer that the showing and hiding of the alert bar automatically without reloading the website is only accomplished if you have the MQTT feature enabled. Which reminds me I need to add an option to show that bar if MQTT is disabled. I'll have to make

[weewx-user] Re: Belchertown DarkSky Alerts

Thanks Pat...Downloaded and installed both files and restarted weewx. No alerts in the area at this time; mostly likely some alerts towards end of week when the icy weather comes through. We'll keep you informed. Rich On Wednesday, December 26, 2018 at 11:47:44 AM UTC-5, Pat wrote: > Oops -

[weewx-user] Re: Belchertown DarkSky Alerts

Oops - forgot to hide the alert bar when an alert clears. Try this updated version attached. Same rules apply as above. On Wednesday, December 26, 2018 at 11:39:24 AM UTC-5, Pat wrote: > > I just

[weewx-user] Re: problem with wind in WMR300

Better info... sudo journalctl -f | grep wind Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 131.0, 'wind_gust_dir': 121.0, 'channel': 1, 'windchill': None} Dec 26 17:33:39 meteomontaos

[weewx-user] Re: problem with wind in WMR300

Data today... exist wind dir and wind gust... but not represent in template now. ec 26 17:25:24 meteomontaos weewx[13518]: wmr300: converted packet: {'extraHeatindex5': None, 'extraDewpoint5': None, 'dateTime': 1545841525, 'extraHumid5': None, 'extraTemp5': None, 'usUnits': 17} Dec 26 17:25:24

[weewx-user] Re: Belchertown DarkSky Alerts

I think underneath the timestamp with the Icon would look fine. Same text size as the timestamp but bold. Maybe make the Alerts optional feature, so the users has a choice to display the Alerts. On Wednesday, December 26, 2018 at 9:29:16 AM UTC-5, Pat wrote: > > Ok cool. That GitHub repo just

[weewx-user] Re: Looking to replace my old Acurite 0203C weather station

Not sure where you're located but check into some of the FineOffset stations. If you're in the US, AmbientWeather.com has some rebranded ones for their brand. I don't have one, so other's here who have a FineOffset station may be able to offer their feedback. On Wednesday, December 26, 2018

[weewx-user] Re: Belchertown Skin 0.8.1 released

I think You should probably only have one new schema specified - not two - when you do the reconfigure On Wednesday, 26 December 2018 14:19:27 UTC+2, Scott Grayban wrote: > > Step 2 is not working at all for me... > > If I have > *schema = user.extensions.schema_apptemp* > *

[weewx-user] Re: Belchertown DarkSky Alerts

Agreed. Let me work on a concept On Wednesday, December 26, 2018 at 9:47:56 AM UTC-5, rich T wrote: > > I think underneath the timestamp with the Icon would look fine. Same text > size as the timestamp but bold. Maybe make the Alerts optional feature, so > the users has a choice to display

[weewx-user] Re: Belchertown DarkSky Alerts

Ok cool. That GitHub repo just confirmed that I am doing what they're doing. I'm not using JavaScript though, I'm just grabbing the raw JSON from DarkSky. I guess I've never seen the alerts array in my output when I initially created it, so out of sight out of mind? I just grabbed a forecast

[weewx-user] Re: problem with wind in WMR300

When the wind speed is zero then the direction is deliberately set to None, so you can only check direction when there is some wind. That rule applies both to average and to gust readings. When you set debug=1 you also need to check which debug suboptions are set in the wmr300 section of the

[weewx-user] Re: Belchertown Skin 0.8.1 released

Step 2 is not working at all for me... If I have *schema = user.extensions.schema_apptemp* *schema = user.extensions.schema_windrun* added in the *[DataBindings]* *[[wx_binding]]* *wee_database weewx.conf --reconfigure* Gives this error *configobj.DuplicateError:

[weewx-user] Re: Belchertown Skin 0.8.1 released

When I run wee_database weewx.conf --reconfigure I am getting python errors Traceback (most recent call last): File "/usr/bin/wee_database", line 793, in main() File "/usr/bin/wee_database", line 133, in main config_path, config_dict = weecfg.read_config(options.config_path, args)