[weewx-user] Re: Belchertown Skin 0.8.1 released

`outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL, `appTemp` REAL, `windRun` REAL, `cloudbase` REAL); Yup it's there. On Saturday, December 29, 2018 at 6:52:30 AM UTC-8, Pat wrote: > > Verify your database has the windrun column > > On Saturday, December 29, 2018 at 1:09:14 AM UTC-5, Scott

[weewx-user] Re: Belchertown Skin 0.8.1 released

shit its windrun not windRun On Saturday, December 29, 2018 at 6:52:30 AM UTC-8, Pat wrote: > > Verify your database has the windrun column > > On Saturday, December 29, 2018 at 1:09:14 AM UTC-5, Scott Grayban wrote: >> >> Am I missing something ??? >> >> No data is getting pulled for *Highest

[weewx-user] Re: Belchertown Skin 0.8.1 released

Verify your database has the windrun column On Saturday, December 29, 2018 at 1:09:14 AM UTC-5, Scott Grayban wrote: > > Am I missing something ??? > > No data is getting pulled for *Highest Daily Wind Run* records. > -- You received this message because you are subscribed to the Google Groups

[weewx-user] Re: Belchertown Skin 0.8.1 released

Am I missing something ??? No data is getting pulled for *Highest Daily Wind Run* records. -- 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...@

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

Created a new issue #33 On Friday, December 28, 2018 at 5:21:40 AM UTC-8, Pat wrote: > > Thanks for the support. I'm due for another coffee! > > On Friday, December 28, 2018 at 8:17:26 AM UTC-5, Scott Grayban wrote: >> >> Do

[weewx-user] Re: Belchertown Skin 0.8.1 released

Yeah I haven't documented much of it yet since it's not officially released. But if you want to expand your database (again) to add cloudbase, update your extensions.py like you did the other day and add this inside the brackets where you have your appTemp and windrun , ('cloudbase', 'REAL')

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

Thanks for the support. I'm due for another coffee! On Friday, December 28, 2018 at 8:17:26 AM UTC-5, Scott Grayban wrote: > > Donated also... > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving e

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

Donated also... On Friday, December 28, 2018 at 5:02:40 AM UTC-8, Pat wrote: > > You're welcome! MQTT can be confusing at first but once you get the > concept down that 1 client publishes, and MANY clients can subscribe and > get instant updates, it starts to make sense and open doors to other

[weewx-user] Re: Belchertown Skin 0.8.1 released

I know its a bit early but I noticed you added cloudbase and you need to expand the db to use it. In the changelog you only mention to read wiki but it's not there What would the format be ? On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote: > > The last thread was getting a bit lo

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

You're welcome! MQTT can be confusing at first but once you get the concept down that 1 client publishes, and MANY clients can subscribe and get instant updates, it starts to make sense and open doors to other projects :) On Thursday, December 27, 2018 at 10:16:20 PM UTC-5, Scott Grayban wrote:

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

I did learn a lot. It's the first time in my 40 years of working on linux that I ever used MQTT and have to admit I can now use that knowledge on a few sites clients are complaining about. I want to thank each of those who helped because this was a little learning curve for me. And especially P

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

Looking good! Look at all you learned and be proud of your new knowledge. On Thu, Dec 27, 2018 at 8:50 PM Scott Grayban wrote: > ok I did a test from the outside seems to work but of course it > doesn't work in-house but I can live with that. > > Can everyone else check again please ? > > On

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

I just checked your website and it's working for me. Congratulations! phil On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, Scott Grayban wrote: > > ok I did a test from the outside seems to work but of course it > doesn't work in-house but I can live with that. > > Can everyone else check

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

He sure does - you can buy him a coffee :) Links are on the Github pages On Fri, Dec 28, 2018 at 3:41 PM Scott Grayban wrote: > Thank you Pat for all your help... Do you take donations ? > > On Thursday, December 27, 2018 at 6:07:14 PM UTC-8, Pat wrote: >> >> Looks good! >> >> >> On Thursday

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

Thank you Pat for all your help... Do you take donations ? On Thursday, December 27, 2018 at 6:07:14 PM UTC-8, Pat wrote: > > Looks good! > > > On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, Scott Grayban wrote: >> >> ok I did a test from the outside seems to work but of course it >>

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

Looks good! On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, Scott Grayban wrote: > > ok I did a test from the outside seems to work but of course it > doesn't work in-house but I can live with that. > > Can everyone else check again please ? > > On Thursday, December 27, 2018 at 5:40:04

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

Yep bingo. Well done. Mine works from inside and outside, not sure what you have different though On Fri, Dec 28, 2018 at 2:55 PM Scott Grayban wrote: > I guess I could move the MQTT to a public side server in my house so data > is collected in-house also Wouldn't be hard to do seeing that P

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

I guess I could move the MQTT to a public side server in my house so data is collected in-house also Wouldn't be hard to do seeing that Pat get me all sorted out. Just transfer all my settings. On Thursday, December 27, 2018 at 5:50:25 PM UTC-8, Scott Grayban wrote: > > ok I did a test from

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

ok I did a test from the outside seems to work but of course it doesn't work in-house but I can live with that. Can everyone else check again please ? On Thursday, December 27, 2018 at 5:40:04 PM UTC-8, Scott Grayban wrote: > > Ahh so use my router IP instead and port forward > > On Thursda

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

Yes indeed, that should do it. You can just put your domain name in the same as I have. And port forward external port 9001 to 192.168.0.4 port 9001 On Fri, Dec 28, 2018 at 2:40 PM Scott Grayban wrote: > Ahh so use my router IP instead and port forward > > On Thursday, December 27, 2018 at 5:33:

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

Ahh so use my router IP instead and port forward On Thursday, December 27, 2018 at 5:33:59 PM UTC-8, Colin Larsen wrote: > > My MQTT settings in skin.conf look like this - with my public web site > name in there > > # MQTT Defaults > > mqtt_enabled = 1 > > mqtt_host = "41south.net.nz" >

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

My MQTT settings in skin.conf look like this - with my public web site name in there # MQTT Defaults mqtt_enabled = 1 mqtt_host = "41south.net.nz" mqtt_port = 9001 mqtt_ssl = 0 mqtt_topic = "weather/41south/loop" disconnect_live_website_visitor = 180 On Fri, Dec

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

On Fri, Dec 28, 2018 at 2:29 PM Colin Larsen wrote: > My browser won't connect to your data, which is due to the fact that you > need to port forward the 9001 in your router - otherwise other users > outside your network can't access the MQTT data. You'll also need to > provide your public ip add

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

My browser won't connect to your data, which is due to the fact that you need to port forward the 9001 in your router - otherwise other users outside your network can't access the MQTT data. You'll also need to provide your public ip address or use your FQDN in that setting On Fri, Dec 28, 2018 at

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

I get connecting for about a minute then failed try again later. On Thu, Dec 27, 2018 at 8:25 PM Scott Grayban wrote: > Got it !!! > > See if it works on your end http://www.nettletondistrict.com/Nettleton/ > > On Thursday, December 27, 2018 at 5:14:02 PM UTC-8, Pat wrote: >> >> Also, Belchertow

[weewx-user] Re: Belchertown Skin 0.8.1 released

Got it !!! See if it works on your end http://www.nettletondistrict.com/Nettleton/ On Thursday, December 27, 2018 at 5:14:02 PM UTC-8, Pat wrote: > > Also, Belchertown uses websockets, so you should change your [[[Extras]]] > mqtt_port to 9001 since that's what you have defined in myconfig.conf.

[weewx-user] Re: Belchertown Skin 0.8.1 released

Also, Belchertown uses websockets, so you should change your [[[Extras]]] mqtt_port to 9001 since that's what you have defined in myconfig.conf. I didn't catch that earlier. On Thursday, December 27, 2018 at 8:13:12 PM UTC-5, Pat wrote: > > Ok, so thinking about this. I'm an outside person, and

[weewx-user] Re: Belchertown Skin 0.8.1 released

Ok, so thinking about this. I'm an outside person, and I cannot reach your 192.168.0.4 from the outside world. This is a problem because I need to reach that in order to get MQTT data on your website. You need to port forward 9001 to 192.168.0.4 so I can reach it from the outside On Thursday

[weewx-user] Re: Belchertown Skin 0.8.1 released

192.168.0.4 is a local IP that has the weewx installed and data pulled from the station but the website itself is served to the public with a outside IP 63.230.134.161 via a reverse proxy see http://www.nettletondistrict.com/Nettleton/ it works fine doing a reverse proxy for everything but the

[weewx-user] Re: Belchertown Skin 0.8.1 released

I'm not sure what is causing that. Might be best to start from the basics again. Check out my article to compare your settings, read the descriptions again, and also check out the skin options to make sure you're not missing something. Is your broker or weewx available to the public? On Thur

[weewx-user] Re: Belchertown Skin 0.8.1 released

Shit.mosquitto.log is showing Socket error on client , disconnecting. 1545958518: New connection from 192.168.0.4 on port 1883. 1545958518: New client connected from 192.168.0.4 as d413f626-b78b-4bca-8e99-43861d26dc6a (c1, k60, u'weewx'). 1545958518: Client d413f626-b78b-4bca-8e99-43861d26dc

[weewx-user] Re: Belchertown Skin 0.8.1 released

Looks good On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott Grayban wrote: > > Is my /etc/mosquitto/acl correct ? Or do I need to change those values ? > > # Allow anonymous access to the sys > topic read $SYS/# > # Allow anonymous to read weather > topic read weather/# > # weewx readwrit

[weewx-user] Re: Belchertown Skin 0.8.1 released

Is my /etc/mosquitto/acl correct ? Or do I need to change those values ? # Allow anonymous access to the sys topic read $SYS/# # Allow anonymous to read weather topic read weather/# # weewx readwrite to the loop user weewx topic weather/# On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat w

[weewx-user] Re: Belchertown Skin 0.8.1 released

Ok, there's a few more things not quite right. 1. MQTT is very picky about it's config file. Change your myconfig.conf so that there is no space between listener 1883 and protocol mqtt. See my post from last night above a few. listener 1883 protocol mqtt Restart your mosquitto - or to be saf

[weewx-user] Re: Belchertown Skin 0.8.1 released

# netstat -tulpn | grep mosquitto tcp0 0 0.0.0.0:90010.0.0.0:* LISTEN 15091/mosquitto tcp0 0 0.0.0.0:18830.0.0.0:* LISTEN 15091/mosquitto tcp6 0 0 :::1883 :::*

[weewx-user] Re: Belchertown Skin 0.8.1 released

Ok getting close. in EXTRAS I have mqtt_enabled = 1 mqtt_host = 192.168.0.4 mqtt_topic = weather/# mqtt_port = 1883 mqtt_ssl = 0 disconnect_live_website_visitor = 180 which now is giving *Failed connecting to the we

[weewx-user] Re: Belchertown Skin 0.8.1 released

Under [[[Extras]]] you don't have any of the skin specific MQTT settings . At a minimum you need mqtt_enabled, which you have, but also mqtt_host and mqtt_topic. As mentioned previously, weewx is posting to your

[weewx-user] Re: Belchertown Skin 0.8.1 released

[[Belchertown]] HTML_ROOT = /home/weewx/public_html/Nettleton skin = Nettleton [[[Extras]]] belchertown_root_url = http: //www.nettletondistrict.com/Nettleton logo_image = http: //www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg

[weewx-user] Re: Belchertown Skin 0.8.1 released

Please post your Belchertown skin settings. On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote: > > Ok so my weewx.conf looks like this now > [[MQTT]] > server_url = mqtt://weewx:passwordX@192.168.0.4:1883/ > topic = weather/# > unit_system

[weewx-user] Re: Belchertown Skin 0.8.1 released

Try server_url = http://weewx:password@192.168.0.4:1883/ Rich On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote: > > Ok so my weewx.conf looks like this now > [[MQTT]] > server_url = mqtt://weewx:passwordX@192.168.0.4:1883/ > topic = weather/#

[weewx-user] Re: Belchertown Skin 0.8.1 released

Ok so my weewx.conf looks like this now [[MQTT]] server_url = mqtt://weewx:passwordX@192.168.0.4:1883/ topic = weather/# unit_system = US binding = archive, loop aggregation = aggregate My /etc/mosquitto/conf.d/myconfig.conf looks like this per

[weewx-user] Re: Belchertown Skin 0.8.1 released

This is because your MQTT is isolated to localhost only. Local host in this case would be your weewx server, which you must have installed MQTT on as well. Which works for weewx ==> MQTT since they are on the same system, but nothing else First, change your MQTT to listen on 1883 for external c

[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 = weather/#

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 UTC

[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` RE

[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 at

[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 un

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 sch

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 reco

[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* > *sche

[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: Duplica

[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)

[weewx-user] Re: Belchertown Skin 0.8.1 released

I love the skin... tweaked it a bit for my taste, added location, server and weeWX stats to the about page... http://www.nettletondistrict.com/Nettleton/ It's being served from my local IP via a reverse proxy. Next task is to get MQTT working !! Thanks for all your work !! On Friday, December

[weewx-user] Re: Belchertown Skin 0.8.1 released

Haven't seen this before, my initial guess is that this is something to do with Cheetah I think, and not my skin necessarily. Does your configuration or database have some sort of ascii character in it like the degrees symbol or something like that? Seems to be something with your setup. Check

[weewx-user] Re: Belchertown Skin 0.8.1 released

Hi Pat, I've installed the latest version and have followed all of your instructions, however, I keep getting the following errors when weeex tries to generate the actual index.html files: Dec 21 16:40:22 debian weewx[6732]: reportengine: Running report Belchertown Dec 21 16:40:22 debian weewx[

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

Yes, unfortunately that is taken from the Darksky current conditions so it breaks. I was considering raising a request with Pat to use that independent of using the forecast display On Fri, 14 Dec 2018, 05:25 G Hammer Did that change affect the current condition graphic next to the current > temp

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

Did that change affect the current condition graphic next to the current temp? On Tuesday, December 11, 2018 at 8:33:57 PM UTC-5, Colin Larsen wrote: > > I came across the Darksky widgets today and they do include alerts > > https://darksky.net/widgets > > I've just replaced the whole Darksky fo

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

haha, nope, maybe an early bed time On Wednesday, December 12, 2018 at 8:00:05 PM UTC-5, Colin Larsen wrote: > > Quick, more coffee! :D > > On Thu, 13 Dec 2018, 13:56 Pat wrote: > >> Wow, I'm having a hard time replying clearly tonight. >> >> Find this. It should say "false". >> >> navigator:

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

Quick, more coffee! :D On Thu, 13 Dec 2018, 13:56 Pat Wow, I'm having a hard time replying clearly tonight. > > Find this. It should say "false". > > navigator: { > enabled: false > }, > > > and set it to true :) > > > On Wednesday, December 12, 2018 at 7:54:51 PM UTC-5, Pat wrote: >> >> The s

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

Wow, I'm having a hard time replying clearly tonight. Find this. It should say "false". navigator: { enabled: false }, and set it to true :) On Wednesday, December 12, 2018 at 7:54:51 PM UTC-5, Pat wrote: > > The skin actually uses HighStock >

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

The skin actually uses HighStock but has the timeline disabled. Feel free to en

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

The skin actually uses HighStock but has the timeline disabled. Feel free to enable it in your setup :) On Tuesday, December 11, 2018 at 11:38:07 PM UTC-5, WILWetter25 wrote: > > The

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

The Akin use Highcharts currently. In the link I posted you will See a example for HighStock. The difference between Highcharts and HighStock: In HighStock you can choose a Date, time. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscri

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

Which part of the highcharts demo page do you think should be incorporated into the Belchertown skin, and instead of what?? On Tuesday, 11 December 2018 22:38:34 UTC+2, WILWetter25 wrote: > > Thank you for your hard work. I am looking around for a alternative to > Highcharts and I found this: >

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

I came across the Darksky widgets today and they do include alerts https://darksky.net/widgets I've just replaced the whole Darksky forecast section with a 'hook' page to place the week widget there instead. Apparently it does include alerts. I have found the downloaded forecast data to be way of

[weewx-user] Re: Belchertown Skin 0.8.1 released

Is there a way to include alerts from Darksky? On Friday, December 7, 2018 at 5:12:23 PM UTC-5, Pat wrote: > > The last thread was getting a bit long. So I've started a new one. > > Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. See > the release notes, and install instru

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

Thank you for your hard work. I am looking around for a alternative to Highcharts and I found this: https://www.highcharts.com/stock/demo/basic-line It would be cool if this could be integrated in the skin :) Just a suggestion Am Freitag, 7. Dezember 2018 23:12:23 UTC+1 schrieb Pat: > > The last

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

Great news, glad to hear you sorted it. Cheers Colin On Wed, 12 Dec 2018, 03:47 G Hammer I did. The sqlite3 commands from Phil allowed me to see that whatever > config I did was not actually active. > I blame user error as I had edited files on one machine and ftp'd the > files to the server. >

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

I did. The sqlite3 commands from Phil allowed me to see that whatever config I did was not actually active. I blame user error as I had edited files on one machine and ftp'd the files to the server. Performing the entire process on the server gave the expected result. Thanks for the education to

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

Do you also see errors on your Records page where Highest App Temp and Lowest App temp are? On Tue, Dec 11, 2018 at 12:03 PM wrote: > That should do it. > > If you have sqlite3 installed, you can open the database with the command > sqlite3 > weewx.sdb and then issue the command: > > .sche

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

That should do it. If you have sqlite3 installed, you can open the database with the command sqlite3 weewx.sdb and then issue the command: .schema archive You should see `appTemp` REAL at the end of the list. The command: .tables should show archive_day_appTemp somewhere in the li

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

Hmmm, well then I'm at a loss. I though the database had been extended. Here's what I did: Edit extensions.py to be: import schemas.wview schema_apptemp = schemas.wview.schema + [('appTemp', 'REAL')] Stop weewx Edit weewx.conf to have: [DataBindings] [[wx_binding]] # The databa

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

If you haven't extended the database as per the Weewx wiki you will get those errors. I haven't written a guide but it is reasonably straightforward On Tue, 11 Dec 2018, 07:05 G Hammer Yes, in fact followed your guide above. > The Feels like shows in the temp display, but when enabled in charts y

[weewx-user] Re: Belchertown Skin 0.8.1 released

Yes, in fact followed your guide above. The Feels like shows in the temp display, but when enabled in charts you get the error. -- 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, se

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

You don't have the database extended for appTemp, it's an easy operation. You will also have errors on the records page? On Tue, 11 Dec 2018, 06:39 Philip Kutzenco See my post above in this topic : > https://groups.google.com/d/msg/weewx-user/ARBHWDXiDpQ/7cz4m-Q7BAAJ. >

[weewx-user] Re: Belchertown Skin 0.8.1 released

See my post above in this topic : https://groups.google.com/d/msg/weewx-user/ARBHWDXiDpQ/7cz4m-Q7BAAJ. phil On Monday, December 10, 2018 at 11:22:58 AM UTC-5, Wes Witt wrote: > > following. i'm interested in using apptemp to

[weewx-user] Re: Belchertown Skin 0.8.1 released

following. i'm interested in using apptemp to but would like to know what is necessary to get the archive table configured properly. On Monday, December 10, 2018 at 7:54:39 AM UTC-8, Philip Kutzenco wrote: > > This is likely a naive question on my part. But did you extend the schema > on the arc

[weewx-user] Re: Belchertown Skin 0.8.1 released

This is likely a naive question on my part. But did you extend the schema on the archive table for your database to include appTemp? Assuming so, did you rebuild the daily value tables? Are the values in the archive table and the archive_day_appTemp table being populated? When I look at your web

[weewx-user] Re: Belchertown Skin 0.8.1 released

Pat, When I have show_apptemp=1 I do see the Feels like temp as I expect. If I set highcharts_show_apptemp = 1 I do not get an apptemp plot, the report generator errors out: Dec 10 09:55:50 ftp weewx[13683]: reportengine: Caught unrecoverable exception in generator weewx.cheetahgenerator.Cheetah

[weewx-user] Re: Belchertown Skin 0.8.1 released

Here's the rest of the pertinent log entries that Groups cut off: Dec 10 09:55:50 ftp weewx[13683]: raise weedb. NoColumnError(e) Dec 10 09:55:50 ftp weewx[13683]: NoColumnError: no such column: appTemp Dec 10 09:55:50 ftp weewx[13683]: Generator termi

[weewx-user] Re: Belchertown Skin 0.8.1 released

https://www.davisinstruments.com/product_documents/weather/app_notes/AN_28-derived-weather-variables.pdf On Sunday, December 9, 2018 at 8:07:28 PM UTC-5, Philip Kutzenco wrote: > > First, let me apologize for hijacking this Belchertown thread to get > educated on Apparent Temperature. > > Second,

[weewx-user] Re: Belchertown Skin 0.8.1 released

Thanks for all of the help, and the explanation of how appTemp is calculated. I am much less confused about it now, and think I will put a blurb on the "about" page as an explanation to others. -Dj -- You received this message because you are subscribed to the Google Groups "weewx-user" grou

[weewx-user] Re: Belchertown Skin 0.8.1 released

First, let me apologize for hijacking this Belchertown thread to get educated on Apparent Temperature. Second, thanks Gary, your explanation clarifies it for me. It seems I was fixed on a simplistic definition of Apparent Temperature sometimes used in the US which yields the same value as eithe

[weewx-user] Re: Belchertown Skin 0.8.1 released

As you point out weeWX windchill and heatindex values track outTemp below certain minimums and above certain maximums respectively. The weeWX calculated appTemp uses the formulas mentioned in the post you linked and is quite different to a composite heatindex and windchill (by composite I mean w

[weewx-user] Re: Belchertown Skin 0.8.1 released

Dj, Check out this link for details: https://groups.google.com/d/msg/weewx-user/bNz3ymPNHHc/caYi1nqlAgAJ I must say that I have been a bit confused about the appTemp value weewx calculates. My understanding is that the Apparent Temperature is equal to the Wind Chill number when the temp is 50

[weewx-user] Re: Belchertown Skin 0.8.1 released

That worked beautifully, thank you Philip! I don't believe the data it is showing is correct, though. Outside temp is 23.5 F currently, with no wind. It is showing a "feels like" temperature of 18.1 F. Other sources are showing the feels like temp in my area being the same as the outside te

[weewx-user] Re: Belchertown Skin 0.8.1 released

One more thing: extensions.py could be in /home/weewx/bin/user if you installed weewx with setup.py rather than with apt-get. phil On Sunday, December 9, 2018 at 4:51:15 PM UTC-5, Philip Kutzenco wrote: > > Dj, > > (I deleted the first version of this post as I left out a trailing "]" in > ste

[weewx-user] Re: Belchertown Skin 0.8.1 released

Dj, (I deleted the first version of this post as I left out a trailing "]" in step 1). This is from instructions Pat gave me in the past to extend the schema: 1) Extend the database nano /usr/share/weewx/user/extensions.py then add the following: *import schemas.wviewschema_apptemp = schema

[weewx-user] Re: Belchertown Skin 0.8.1 released

Dj, This is from instructions Pat gave me in the past to extend the schema: 1) Extend the database nano /usr/share/weewx/user/extensions.py then add the following: *import schemas.wviewschema_apptemp = schemas.wview.schema + [('appTemp', 'REAL')* 2) Stop weewx and edit weewx.conf to tel

[weewx-user] Re: Belchertown Skin 0.8.1 released

Please forgive my ignorance. It is not clear after reading the instructions on extending the database precisely what I should do in this case. Obviously we don't have an "user/electricity.py" file, but we do have a "user/belchertown.py" file. Should I modify the "belchertown.py" file with som

[weewx-user] Re: Belchertown Skin 0.8.1 released

Dj, In addition to extending the schema for your database to include appTemp, as Pat notes (this is a requirement), I recommend you add the line mentioned by Rich show apptemp = 1 in the [[[Extras]]] stanza of the [[Belchertown]] stanza in weewx.conf (instead of adding it to skin.conf). This

[weewx-user] Re: Belchertown Skin 0.8.1 released

Thanks Dj! As mentioned in the general options guide , your database will need to be extended for the appTemp observations. On Sunday, December 9, 2018 at 3:44:00 PM UTC-5, ri

[weewx-user] Re: Belchertown Skin 0.8.1 released

Dj In the skin.conf file located in the Belchertown folder, set "show_apptemp = 1". Restart weewx. Rich On Sunday, December 9, 2018 at 3:27:35 PM UTC-5, Dj Merrill wrote: > Pat, what a beautiful piece of work! Thank you for sharing this with us! > > I notice on your site there is a "Feels li

[weewx-user] Re: Belchertown Skin 0.8.1 released

Pat, what a beautiful piece of work! Thank you for sharing this with us! I notice on your site there is a "Feels like" temperature shown under the outside temperature and above the high/low temps on the top of the main page. I don't see that on my site, and am wondering how to enable that? Th

[weewx-user] Re: Belchertown Skin 0.8.1 released

Got it to show...thanks Pat On Sunday, December 9, 2018 at 2:07:20 PM UTC-5, Pat wrote: > > No tag, but the version number is in the view source at the bottom. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and st

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

a "watermark" for the site. Was just thinking out loud that it would be nice to do if it weren't too much of a hassle. ---- Forwarded Message Subject:Re: [weewx-user] Re: Belchertown Skin 0.8.1 released Date: Sun, 9 Dec 2018 08:19:58 -0600 Fr

  1   2   >