Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Thanks! I started with Belchertown because of the rich amount of 
documentation and help that's available. If not Belchertown, then what 
would you both suggest i start with to build up a better understanding of 
weewx, skins, graphs and weather info presentation?
/David

On Thursday, March 11, 2021 at 7:57:15 AM UTC-8 vince wrote:

> On Thursday, March 11, 2021 at 3:25:55 AM UTC-8 kk44...@gmail.com wrote:
>
>> Belchertown is a very complex skin with lots of JavaScript and Python 
>> scripts contributing some values. Major changes in layout require deep 
>> study of the internal structure. If you have to fulfill special 
>> requirements in layout, may be you want to start based on another skin like 
>> Seasons.
>>
>>
> Agree.  Belchertown supports only minimal configurability within some 
> pretty strict bounds.   Figuring it all out end to end would require 
> examining the source html and the reasonably complicated javascript code 
> under the hood.  This is non-trivial especially for folks new to doing that 
> kind of stuff.
>
> See 
> https://github.com/poblabs/weewx-belchertown#add-custom-content-to-the-front-page
>  
> for the documentation.
>  
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1bbc2ca6-30ed-4555-8aa1-5ba2ecb6b1edn%40googlegroups.com.

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Belchertown. I just don't fully understand how each of the index, graphs,
skins and image file work to produce the homepage. More studying on my
part! Can you give me a rough outline of how the main homepage is
generated? Where static and dynamic content is assembled for nginx to
publish basic page? I'll try to read up on the chart generator also. Thanks
for the assists!

On Wed, Mar 10, 2021, 12:43 PM gjr80  wrote:

> Which homepage? Seasons or Belchertown?
>
> Gary
>
> On Thursday, 11 March 2021 at 03:02:53 UTC+10 david.a@gmail.com wrote:
>
>> Gary, hope all's okay (covid19 and all). is there a way to change the
>> general layout of the homepage? wife wants something different, large day,
>> date, time with summaries of weather conditions, leave most of the details
>> to lower pages. thanks!
>>
>>
>> On Wednesday, March 10, 2021 at 2:35:28 AM UTC-8 gjr80 wrote:
>>
>>> David,
>>>
>>> Apologies I have not had much time for WeeWX today. In any case it is good
>>> that you have it working.
>>>
>>> Gary
>>> On Wednesday, 10 March 2021 at 11:14:29 UTC+10 david.a@gmail.com
>>> wrote:
>>>
>>>> Gary, more GOOD news, i changed HTML_ROOT statement in weewx.conf for
>>>> [[Belchertown]] to  "HTML_ROOT = /home/weewx/public_html/belchertown" then
>>>> made some minor title changes to skin.conf in belchertown and it works!
>>>>
>>>> I think that nginx was looking at the base of /home/weewx/public_html
>>>> for all implementations of localhost. So, any calls to
>>>> http://localhost/weewx gets the basic pages found in /public_html; but
>>>> calls to http://localhost/weewx/belchertown will get the belchertown
>>>> pages (off of ../public_html/belchertown') instead of the ../public_html
>>>> pages.
>>>>
>>>> I think it's now working! Thanks!
>>>> /David
>>>> On Tuesday, March 9, 2021 at 4:53:48 PM UTC-8 David Prellwitz wrote:
>>>>
>>>>> Gary, did one more test - i copied all of the files in
>>>>> "/home/weewx/public_html/weewx/belchertown" to
>>>>> "/home/weewx/public_html/belchertown" and ran the browser to
>>>>> 'localhost/weewx/belchertown' - i worked!!! that means i need to modify 
>>>>> the
>>>>> conf file to point to "/home/weewx/public_html/belchertown" instead of
>>>>> "/home/weewx/public_html/weewx/belchertown"
>>>>>
>>>>> On Tuesday, March 9, 2021 at 3:58:32 PM UTC-8 David Prellwitz wrote:
>>>>>
>>>>>> Gary:
>>>>>> more - i've been studying the nginx package. I followed the
>>>>>> configuration file links. they start at /etc/nginx in the nginx.conf 
>>>>>> file.
>>>>>> It links /etc/nginx/sites-enabled; which redirects to
>>>>>> /etc/nginx/sites-avaialble. that configuration file links to 'default'
>>>>>> which has a declaration to include 'root' with /var/www/html which 
>>>>>> contains
>>>>>> the first mention of weewx; that links is a redirection to
>>>>>> /home/weewx/public_html directory. No mention of belchertown anywhere.
>>>>>>
>>>>>> I'm thinking that I need a reference to the
>>>>>> "/home/weewx/public_html/weewx/belchertown" somewhere in this chain,
>>>>>> otherwise nginx can't find the config, html and image files. what do you
>>>>>> think? attached is a text file of my findings on the nginx configuration
>>>>>> setup.
>>>>>> /David
>>>>>>
>>>>>> On Tuesday, March 9, 2021 at 12:56:47 PM UTC-8 David Prellwitz wrote:
>>>>>>
>>>>>>> Gary:
>>>>>>> yes to all. here's some examples. First file is a set of extracts
>>>>>>> from syslog; then annotated extracts from the index.html files in
>>>>>>> ../public_html and ../public_html/weewx/belchertown directories; then an
>>>>>>> annotated tree structure taken at /home/weewx/public_html; then screen
>>>>>>> shots from http://192.168.86.28/  - then screen shot from
>>>>>>> http://192.168.86.28/weewx and last from
>>>>>>> http://192.168.86.28/weewx/belchertown . as i noted in my extracts,
>>>>>>> both the index files show current info (i think). When i look in
>>>>>>>

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Gary, hope all's okay (covid19 and all). is there a way to change the 
general layout of the homepage? wife wants something different, large day, 
date, time with summaries of weather conditions, leave most of the details 
to lower pages. thanks!


On Wednesday, March 10, 2021 at 2:35:28 AM UTC-8 gjr80 wrote:

> David,
>
> Apologies I have not had much time for WeeWX today. In any case it is good 
> that you have it working. 
>
> Gary
> On Wednesday, 10 March 2021 at 11:14:29 UTC+10 david.a@gmail.com 
> wrote:
>
>> Gary, more GOOD news, i changed HTML_ROOT statement in weewx.conf for 
>> [[Belchertown]] to  "HTML_ROOT = /home/weewx/public_html/belchertown" then 
>> made some minor title changes to skin.conf in belchertown and it works!
>>
>> I think that nginx was looking at the base of /home/weewx/public_html for 
>> all implementations of localhost. So, any calls to http://localhost/weewx 
>> gets the basic pages found in /public_html; but calls to 
>> http://localhost/weewx/belchertown will get the belchertown pages (off 
>> of ../public_html/belchertown') instead of the ../public_html pages.  
>>
>> I think it's now working! Thanks!
>> /David
>> On Tuesday, March 9, 2021 at 4:53:48 PM UTC-8 David Prellwitz wrote:
>>
>>> Gary, did one more test - i copied all of the files in 
>>> "/home/weewx/public_html/weewx/belchertown" to 
>>> "/home/weewx/public_html/belchertown" and ran the browser to 
>>> 'localhost/weewx/belchertown' - i worked!!! that means i need to modify the 
>>> conf file to point to "/home/weewx/public_html/belchertown" instead of 
>>> "/home/weewx/public_html/weewx/belchertown"
>>>
>>> On Tuesday, March 9, 2021 at 3:58:32 PM UTC-8 David Prellwitz wrote:
>>>
>>>> Gary:
>>>> more - i've been studying the nginx package. I followed the 
>>>> configuration file links. they start at /etc/nginx in the nginx.conf file. 
>>>> It links /etc/nginx/sites-enabled; which redirects to 
>>>> /etc/nginx/sites-avaialble. that configuration file links to 'default' 
>>>> which has a declaration to include 'root' with /var/www/html which 
>>>> contains 
>>>> the first mention of weewx; that links is a redirection to 
>>>> /home/weewx/public_html directory. No mention of belchertown anywhere. 
>>>>
>>>> I'm thinking that I need a reference to the 
>>>> "/home/weewx/public_html/weewx/belchertown" somewhere in this chain, 
>>>> otherwise nginx can't find the config, html and image files. what do you 
>>>> think? attached is a text file of my findings on the nginx configuration 
>>>> setup.
>>>> /David
>>>>
>>>> On Tuesday, March 9, 2021 at 12:56:47 PM UTC-8 David Prellwitz wrote:
>>>>
>>>>> Gary:
>>>>> yes to all. here's some examples. First file is a set of extracts from 
>>>>> syslog; then annotated extracts from the index.html files in 
>>>>> ../public_html 
>>>>> and ../public_html/weewx/belchertown directories; then an annotated tree 
>>>>> structure taken at /home/weewx/public_html; then screen shots from 
>>>>> http://192.168.86.28/  - then screen shot from 
>>>>> http://192.168.86.28/weewx and last from 
>>>>> http://192.168.86.28/weewx/belchertown . as i noted in my extracts, 
>>>>> both the index files show current info (i think). When i look in 
>>>>> /home/weewx/public_html/weewx directory it's empty except for the 
>>>>> /belchertown subdirectory.  I also did "locate" commands for all 
>>>>> occurrences of "index.html" and nothing seemed out of place. So, i'm not 
>>>>> sure where weewx and belchertown execution put their respective web 
>>>>> files. 
>>>>> Nor am i aware of where nginx will pick up those files. It seems that the 
>>>>> default weewx skin operates correctly, that means weewx is operational 
>>>>> and 
>>>>> correct (i think). the syslog shows that weewx generates reports for 
>>>>> belchertown using the skin.conf in belchertown skins directory. almost 
>>>>> all 
>>>>> of the features of belchertown skin seem to be working... so i'm 
>>>>> officially 
>>>>> lost! thanks for the assistance.
>>>>>
>>>>>
>>>>> On Tuesday, March 9, 2021 at 2:21:19 AM UTC-8 gjr80 wrote:
>>>>>
&

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Gary, more GOOD news, i changed HTML_ROOT statement in weewx.conf for 
[[Belchertown]] to  "HTML_ROOT = /home/weewx/public_html/belchertown" then 
made some minor title changes to skin.conf in belchertown and it works!

I think that nginx was looking at the base of /home/weewx/public_html for 
all implementations of localhost. So, any calls to http://localhost/weewx 
gets the basic pages found in /public_html; but calls to 
http://localhost/weewx/belchertown will get the belchertown pages (off of 
../public_html/belchertown') instead of the ../public_html pages.  

I think it's now working! Thanks!
/David
On Tuesday, March 9, 2021 at 4:53:48 PM UTC-8 David Prellwitz wrote:

> Gary, did one more test - i copied all of the files in 
> "/home/weewx/public_html/weewx/belchertown" to 
> "/home/weewx/public_html/belchertown" and ran the browser to 
> 'localhost/weewx/belchertown' - i worked!!! that means i need to modify the 
> conf file to point to "/home/weewx/public_html/belchertown" instead of 
> "/home/weewx/public_html/weewx/belchertown"
>
> On Tuesday, March 9, 2021 at 3:58:32 PM UTC-8 David Prellwitz wrote:
>
>> Gary:
>> more - i've been studying the nginx package. I followed the configuration 
>> file links. they start at /etc/nginx in the nginx.conf file. It links 
>> /etc/nginx/sites-enabled; which redirects to /etc/nginx/sites-avaialble. 
>> that configuration file links to 'default' which has a declaration to 
>> include 'root' with /var/www/html which contains the first mention of 
>> weewx; that links is a redirection to /home/weewx/public_html directory. No 
>> mention of belchertown anywhere. 
>>
>> I'm thinking that I need a reference to the 
>> "/home/weewx/public_html/weewx/belchertown" somewhere in this chain, 
>> otherwise nginx can't find the config, html and image files. what do you 
>> think? attached is a text file of my findings on the nginx configuration 
>> setup.
>> /David
>>
>> On Tuesday, March 9, 2021 at 12:56:47 PM UTC-8 David Prellwitz wrote:
>>
>>> Gary:
>>> yes to all. here's some examples. First file is a set of extracts from 
>>> syslog; then annotated extracts from the index.html files in ../public_html 
>>> and ../public_html/weewx/belchertown directories; then an annotated tree 
>>> structure taken at /home/weewx/public_html; then screen shots from 
>>> http://192.168.86.28/  - then screen shot from 
>>> http://192.168.86.28/weewx and last from 
>>> http://192.168.86.28/weewx/belchertown . as i noted in my extracts, 
>>> both the index files show current info (i think). When i look in 
>>> /home/weewx/public_html/weewx directory it's empty except for the 
>>> /belchertown subdirectory.  I also did "locate" commands for all 
>>> occurrences of "index.html" and nothing seemed out of place. So, i'm not 
>>> sure where weewx and belchertown execution put their respective web files. 
>>> Nor am i aware of where nginx will pick up those files. It seems that the 
>>> default weewx skin operates correctly, that means weewx is operational and 
>>> correct (i think). the syslog shows that weewx generates reports for 
>>> belchertown using the skin.conf in belchertown skins directory. almost all 
>>> of the features of belchertown skin seem to be working... so i'm officially 
>>> lost! thanks for the assistance.
>>>
>>>
>>> On Tuesday, March 9, 2021 at 2:21:19 AM UTC-8 gjr80 wrote:
>>>
>>>> Just to remove all possibility of misinterpretation with abbreviated 
>>>> paths etc. You are saying /home/weewx/public_html/weewx/index.html and 
>>>> /home/weewx/public_html/weewx/belchertown/index.html both exist and 
>>>> appear to be current? And also when you put http://192.168.86.28/weewx 
>>>> into your browser it displays the Seasons skin main page and the data is 
>>>> current, but when you use http://192.168.86.28/weewx/belchertown you 
>>>> get a 404 error?
>>>>
>>>> Gary
>>>>
>>>> On Tuesday, 9 March 2021 at 20:08:20 UTC+10 david.a@gmail.com 
>>>> wrote:
>>>>
>>>>> Gary, they seem to be current. I read index.html files in 
>>>>> ../public_html/weewx/ and /belchertown and they shows labels and some 
>>>>> epoch 
>>>>> time that appears to be current. All the files in /public_html, weewx and 
>>>>> belchertown all seems to have current files. I still get a 404 error when 
>>>>> trying to open. default skin/browse

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Gary, did one more test - i copied all of the files in 
"/home/weewx/public_html/weewx/belchertown" to 
"/home/weewx/public_html/belchertown" and ran the browser to 
'localhost/weewx/belchertown' - i worked!!! that means i need to modify the 
conf file to point to "/home/weewx/public_html/belchertown" instead of 
"/home/weewx/public_html/weewx/belchertown"

On Tuesday, March 9, 2021 at 3:58:32 PM UTC-8 David Prellwitz wrote:

> Gary:
> more - i've been studying the nginx package. I followed the configuration 
> file links. they start at /etc/nginx in the nginx.conf file. It links 
> /etc/nginx/sites-enabled; which redirects to /etc/nginx/sites-avaialble. 
> that configuration file links to 'default' which has a declaration to 
> include 'root' with /var/www/html which contains the first mention of 
> weewx; that links is a redirection to /home/weewx/public_html directory. No 
> mention of belchertown anywhere. 
>
> I'm thinking that I need a reference to the 
> "/home/weewx/public_html/weewx/belchertown" somewhere in this chain, 
> otherwise nginx can't find the config, html and image files. what do you 
> think? attached is a text file of my findings on the nginx configuration 
> setup.
> /David
>
> On Tuesday, March 9, 2021 at 12:56:47 PM UTC-8 David Prellwitz wrote:
>
>> Gary:
>> yes to all. here's some examples. First file is a set of extracts from 
>> syslog; then annotated extracts from the index.html files in ../public_html 
>> and ../public_html/weewx/belchertown directories; then an annotated tree 
>> structure taken at /home/weewx/public_html; then screen shots from 
>> http://192.168.86.28/  - then screen shot from http://192.168.86.28/weewx 
>> and last from http://192.168.86.28/weewx/belchertown . as i noted in my 
>> extracts, both the index files show current info (i think). When i look in 
>> /home/weewx/public_html/weewx directory it's empty except for the 
>> /belchertown subdirectory.  I also did "locate" commands for all 
>> occurrences of "index.html" and nothing seemed out of place. So, i'm not 
>> sure where weewx and belchertown execution put their respective web files. 
>> Nor am i aware of where nginx will pick up those files. It seems that the 
>> default weewx skin operates correctly, that means weewx is operational and 
>> correct (i think). the syslog shows that weewx generates reports for 
>> belchertown using the skin.conf in belchertown skins directory. almost all 
>> of the features of belchertown skin seem to be working... so i'm officially 
>> lost! thanks for the assistance.
>>
>>
>> On Tuesday, March 9, 2021 at 2:21:19 AM UTC-8 gjr80 wrote:
>>
>>> Just to remove all possibility of misinterpretation with abbreviated 
>>> paths etc. You are saying /home/weewx/public_html/weewx/index.html and 
>>> /home/weewx/public_html/weewx/belchertown/index.html both exist and 
>>> appear to be current? And also when you put http://192.168.86.28/weewx 
>>> into your browser it displays the Seasons skin main page and the data is 
>>> current, but when you use http://192.168.86.28/weewx/belchertown you 
>>> get a 404 error?
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 20:08:20 UTC+10 david.a@gmail.com wrote:
>>>
>>>> Gary, they seem to be current. I read index.html files in 
>>>> ../public_html/weewx/ and /belchertown and they shows labels and some 
>>>> epoch 
>>>> time that appears to be current. All the files in /public_html, weewx and 
>>>> belchertown all seems to have current files. I still get a 404 error when 
>>>> trying to open. default skin/browser still works. 
>>>> /David
>>>> On Tuesday, March 9, 2021 at 1:06:24 AM UTC-8 gjr80 wrote:
>>>>
>>>>> Yes, deleting while tired is to be avoided. Interrupting a reporting 
>>>>> cycle is not critical, just means you probably deleted some files that 
>>>>> WeeWX had just generated, WeeWX will get over it.
>>>>>
>>>>> So forgetting about the browser, does 
>>>>> /home/weewx/public_html/weewx/belchertown contain any files and 
>>>>> directories? Are they current, check the content with an editor. If they 
>>>>> are current your issue is an nginx config issue, if they are not current 
>>>>> then you have a really bizarre WeeWX/Belchertown skin problem.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Tuesday, 9 March 2021 at 18:48:15 UTC+10 david.a@gmail.com 
>>>>> wrote:

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Gary:
more - i've been studying the nginx package. I followed the configuration 
file links. they start at /etc/nginx in the nginx.conf file. It links 
/etc/nginx/sites-enabled; which redirects to /etc/nginx/sites-avaialble. 
that configuration file links to 'default' which has a declaration to 
include 'root' with /var/www/html which contains the first mention of 
weewx; that links is a redirection to /home/weewx/public_html directory. No 
mention of belchertown anywhere. 

I'm thinking that I need a reference to the 
"/home/weewx/public_html/weewx/belchertown" somewhere in this chain, 
otherwise nginx can't find the config, html and image files. what do you 
think? attached is a text file of my findings on the nginx configuration 
setup.
/David

On Tuesday, March 9, 2021 at 12:56:47 PM UTC-8 David Prellwitz wrote:

> Gary:
> yes to all. here's some examples. First file is a set of extracts from 
> syslog; then annotated extracts from the index.html files in ../public_html 
> and ../public_html/weewx/belchertown directories; then an annotated tree 
> structure taken at /home/weewx/public_html; then screen shots from 
> http://192.168.86.28/  - then screen shot from http://192.168.86.28/weewx 
> and last from http://192.168.86.28/weewx/belchertown . as i noted in my 
> extracts, both the index files show current info (i think). When i look in 
> /home/weewx/public_html/weewx directory it's empty except for the 
> /belchertown subdirectory.  I also did "locate" commands for all 
> occurrences of "index.html" and nothing seemed out of place. So, i'm not 
> sure where weewx and belchertown execution put their respective web files. 
> Nor am i aware of where nginx will pick up those files. It seems that the 
> default weewx skin operates correctly, that means weewx is operational and 
> correct (i think). the syslog shows that weewx generates reports for 
> belchertown using the skin.conf in belchertown skins directory. almost all 
> of the features of belchertown skin seem to be working... so i'm officially 
> lost! thanks for the assistance.
>
>
> On Tuesday, March 9, 2021 at 2:21:19 AM UTC-8 gjr80 wrote:
>
>> Just to remove all possibility of misinterpretation with abbreviated 
>> paths etc. You are saying /home/weewx/public_html/weewx/index.html and 
>> /home/weewx/public_html/weewx/belchertown/index.html both exist and 
>> appear to be current? And also when you put http://192.168.86.28/weewx 
>> into your browser it displays the Seasons skin main page and the data is 
>> current, but when you use http://192.168.86.28/weewx/belchertown you get 
>> a 404 error?
>>
>> Gary
>>
>> On Tuesday, 9 March 2021 at 20:08:20 UTC+10 david.a@gmail.com wrote:
>>
>>> Gary, they seem to be current. I read index.html files in 
>>> ../public_html/weewx/ and /belchertown and they shows labels and some epoch 
>>> time that appears to be current. All the files in /public_html, weewx and 
>>> belchertown all seems to have current files. I still get a 404 error when 
>>> trying to open. default skin/browser still works. 
>>> /David
>>> On Tuesday, March 9, 2021 at 1:06:24 AM UTC-8 gjr80 wrote:
>>>
>>>> Yes, deleting while tired is to be avoided. Interrupting a reporting 
>>>> cycle is not critical, just means you probably deleted some files that 
>>>> WeeWX had just generated, WeeWX will get over it.
>>>>
>>>> So forgetting about the browser, does 
>>>> /home/weewx/public_html/weewx/belchertown contain any files and 
>>>> directories? Are they current, check the content with an editor. If they 
>>>> are current your issue is an nginx config issue, if they are not current 
>>>> then you have a really bizarre WeeWX/Belchertown skin problem.
>>>>
>>>> Gary
>>>>
>>>> On Tuesday, 9 March 2021 at 18:48:15 UTC+10 david.a@gmail.com 
>>>> wrote:
>>>>
>>>>> Gary:
>>>>> well, i should not make major changes while tired I 
>>>>> (unfortunately) wiped out my own user directory ("/home/david/...) so 
>>>>> i'll 
>>>>> have to live with that. Lost some files and copies of modified conf 
>>>>> files, 
>>>>> but not much else was lost... 
>>>>>
>>>>> I did wipe out the contents of public_html directory and it's 
>>>>> subdirectories. I must have interrupted a reporting cycle as syslog had 
>>>>> some serious errors. once i restarted weewx it all ran successfully. 
>>>>> However, still no joy. Now when i go to 
>>>>> ht

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

 Belchertown 
>>>> files is not the same place that the web engine (nginx) is not picking 
>>>> them 
>>>> up from. 
>>>> /D
>>>>
>>>>
>>>>
>>>>
>>>> On Monday, March 8, 2021 at 12:28:19 AM UTC-8 gjr80 wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I suggest as a start you edit weewx.conf, set debug=1, save weewx.conf 
>>>>> and the restart WeeWX. Let WeeWX run for at least two report cycles and 
>>>>> then post a log extract here showing the entire WeeWX startup and the two 
>>>>> report cycles. Then we can see what WeeWX and the skins are doing.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Monday, 8 March 2021 at 15:30:41 UTC+10 david.a@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> lecoqacr - i can access the belchertown link from my mobile, which is 
>>>>>> sharing the same meshed net. Interesting, both Belchertown homepages 
>>>>>> show a 
>>>>>> "last updated" date as yesterday noon; i've restarted all aspects of 
>>>>>> this 
>>>>>> machine (Debian 10 on a Dell laptop), from the laptop thru weewx (three 
>>>>>> times) and wee-reports (atleast 10 times). but all of the Belchertown 
>>>>>> pages 
>>>>>> show yesterday noon as the last update. However, the Weewx default skin 
>>>>>> updates and shows current data. That's why i think its an issue with my 
>>>>>> weewx.conf/skin.conf/graphs.conf files - and/or their location...
>>>>>>
>>>>>>
>>>>>> On Sunday, March 7, 2021 at 7:23:41 PM UTC-8 lecoqacr...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Maybe this thread is what you are having a problem with.
>>>>>>>
>>>>>>>  https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/O-wO1GiVAwAJ
>>>>>>> Try going to another computer on the network and enter the address 
>>>>>>> of the weewx belchertown address computer.
>>>>>>>
>>>>>>> On Sun, Mar 7, 2021 at 7:12 PM David Prellwitz <
>>>>>>> david.a@gmail.com> wrote:
>>>>>>>
>>>>>>>> More info - looking at syslog, i notice that 8, 11, 15 season files 
>>>>>>>> generated, but  are written to /home/weewx/public_html. Sometimes i'll 
>>>>>>>> get 
>>>>>>>> 2 files written to /home/weewx/public_html/weewx.  But, still no 
>>>>>>>> updates on 
>>>>>>>> belchertown web page. I'm now officially confused as to where 
>>>>>>>> skin.conf, 
>>>>>>>> graphs.conf need to be in relationship to /home/weewx. 
>>>>>>>> /David
>>>>>>>> On Sunday, March 7, 2021 at 1:36:35 PM UTC-8 David Prellwitz wrote:
>>>>>>>>
>>>>>>>>> New issue; i can't get graphs.conf to work, irrespective of where 
>>>>>>>>> i put it. It's now in /home/weewx/skins/belchertown directory with 
>>>>>>>>> graphs.conf.example file. I've even changed example filename - still 
>>>>>>>>> can't 
>>>>>>>>> get belchertown skin to use the minor changes i made to the graphs. 
>>>>>>>>> It has 
>>>>>>>>> to be a configuration issue, something i've overlooked. help!
>>>>>>>>> /David
>>>>>>>>>
>>>>>>>>> On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> kool! thanks!
>>>>>>>>>>
>>>>>>>>>> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Try localhost/weewx/belchertown
>>>>>>>>>>>
>>>>>>>>>>> Dave - KB1PVH
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Sent from my Galaxy S21
>&

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Gary:
well, i should not make major changes while tired I (unfortunately) 
wiped out my own user directory ("/home/david/...) so i'll have to live 
with that. Lost some files and copies of modified conf files, but not much 
else was lost... 

I did wipe out the contents of public_html directory and it's 
subdirectories. I must have interrupted a reporting cycle as syslog had 
some serious errors. once i restarted weewx it all ran successfully. 
However, still no joy. Now when i go to 
http://192,168.86.28/weewx/belchertown i get a 404 error (not found). the 
default skin (http://192,168.86.28/weewx) runs fine. Files all seem to have 
a current date/time, but i still don't get a belchertown page loaded.
/David

On Monday, March 8, 2021 at 10:11:54 PM UTC-8 gjr80 wrote:

> OK. Let's forget about the browser for the time being and work with the 
> files in /home/weewx/public_html, get them right and the browser will 
> fall into place. Since you have made various changes to where WeeWX 
> generated files are going, but seem to have that set correctly now, go 
> ahead and delete everything in /home/weewx/public_html. Everything 
> includes files and directories. WeeWX will re-generate it all on the next 
> report cycle, then next report cycle might take a little longer depending 
> on how much historical data you have as WeeWX will re-generate all NOAA 
> format files. No need to stop/start or restart WeeWX, just make sure that 
> you get everything deleted before a report cycle starts and not during.
>
> Monitor the log and once that next report cycle has completed have a look 
> at what files/directories are where in /home/weewx/public_html and when 
> are they timestamped.
>
> Gary
>
> On Tuesday, 9 March 2021 at 15:53:24 UTC+10 david.a@gmail.com wrote:
>
>> Gary:
>> no joy. changed weewx.conf to show Belchertown HTML_ROOT as you suggested 
>> ("/home/weewx/public_html/weewx/belchertown"), stopped weewx, started 
>> weewx, ran weewx status. waited for updates, browsed to 
>> http://192.168.86.28/weewx and got the original weewx skin with correct 
>> info. Then browsed to http://192.168.86.28/weewx/belchertown and got the 
>> old belchertown skin with March 6, 2021 at 1:55 pm. (Same problem i started 
>> with.) no errors or problems indicated on syslog, debug or messages. I 
>> checked the file/directory structure in /home/weewx/public_html and see 
>> that there is a belchertown and a weewx subdirectories. However, the files 
>> in /home/public_html/belchertown show a date of Mar 6, 2021 at 13:55 - same 
>> as the offending pages. When i checked the .../public_html/belchertown 
>> directory, However, there is NOT a 
>> /home/weewx/publich_html/weewx/belchertown subdirectory. 
>>
>> More interesting stuff: i looked at the index.html file in 
>> "../public_html/weewx" directory and it has the correct belchertown 
>> date/time and it contains the corrected labels/headers and chart specifics 
>> i'd modified. When i looked at the index.html file in 
>> "../public_html/belchertown" directory it contains the March 6 layout 
>> (first modifications to only change the title name). Whatever is happening 
>> means wherever weewx is putting the html files for the newer Belchertown 
>> files is not the same place that the web engine (nginx) is not picking them 
>> up from. 
>> /D
>>
>>
>>
>>
>> On Monday, March 8, 2021 at 12:28:19 AM UTC-8 gjr80 wrote:
>>
>>> Hi,
>>>
>>> I suggest as a start you edit weewx.conf, set debug=1, save weewx.conf 
>>> and the restart WeeWX. Let WeeWX run for at least two report cycles and 
>>> then post a log extract here showing the entire WeeWX startup and the two 
>>> report cycles. Then we can see what WeeWX and the skins are doing.
>>>
>>> Gary
>>>
>>> On Monday, 8 March 2021 at 15:30:41 UTC+10 david.a@gmail.com wrote:
>>>
>>>> lecoqacr - i can access the belchertown link from my mobile, which is 
>>>> sharing the same meshed net. Interesting, both Belchertown homepages show 
>>>> a 
>>>> "last updated" date as yesterday noon; i've restarted all aspects of this 
>>>> machine (Debian 10 on a Dell laptop), from the laptop thru weewx (three 
>>>> times) and wee-reports (atleast 10 times). but all of the Belchertown 
>>>> pages 
>>>> show yesterday noon as the last update. However, the Weewx default skin 
>>>> updates and shows current data. That's why i think its an issue with my 
>>>> weewx.conf/skin.conf/graphs.conf files - and/or their location...
>>>&g

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

Gary:
no joy. changed weewx.conf to show Belchertown HTML_ROOT as you suggested 
("/home/weewx/public_html/weewx/belchertown"), stopped weewx, started 
weewx, ran weewx status. waited for updates, browsed to 
http://192.168.86.28/weewx and got the original weewx skin with correct 
info. Then browsed to http://192.168.86.28/weewx/belchertown and got the 
old belchertown skin with March 6, 2021 at 1:55 pm. (Same problem i started 
with.) no errors or problems indicated on syslog, debug or messages. I 
checked the file/directory structure in /home/weewx/public_html and see 
that there is a belchertown and a weewx subdirectories. However, the files 
in /home/public_html/belchertown show a date of Mar 6, 2021 at 13:55 - same 
as the offending pages. When i checked the .../public_html/belchertown 
directory, However, there is NOT a 
/home/weewx/publich_html/weewx/belchertown subdirectory. 

More interesting stuff: i looked at the index.html file in 
"../public_html/weewx" directory and it has the correct belchertown 
date/time and it contains the corrected labels/headers and chart specifics 
i'd modified. When i looked at the index.html file in 
"../public_html/belchertown" directory it contains the March 6 layout 
(first modifications to only change the title name). Whatever is happening 
means wherever weewx is putting the html files for the newer Belchertown 
files is not the same place that the web engine (nginx) is not picking them 
up from. 
/D




On Monday, March 8, 2021 at 12:28:19 AM UTC-8 gjr80 wrote:

> Hi,
>
> I suggest as a start you edit weewx.conf, set debug=1, save weewx.conf and 
> the restart WeeWX. Let WeeWX run for at least two report cycles and then 
> post a log extract here showing the entire WeeWX startup and the two report 
> cycles. Then we can see what WeeWX and the skins are doing.
>
> Gary
>
> On Monday, 8 March 2021 at 15:30:41 UTC+10 david.a@gmail.com wrote:
>
>> lecoqacr - i can access the belchertown link from my mobile, which is 
>> sharing the same meshed net. Interesting, both Belchertown homepages show a 
>> "last updated" date as yesterday noon; i've restarted all aspects of this 
>> machine (Debian 10 on a Dell laptop), from the laptop thru weewx (three 
>> times) and wee-reports (atleast 10 times). but all of the Belchertown pages 
>> show yesterday noon as the last update. However, the Weewx default skin 
>> updates and shows current data. That's why i think its an issue with my 
>> weewx.conf/skin.conf/graphs.conf files - and/or their location...
>>
>>
>> On Sunday, March 7, 2021 at 7:23:41 PM UTC-8 lecoqacr...@gmail.com wrote:
>>
>>> Maybe this thread is what you are having a problem with.
>>>
>>>  https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/O-wO1GiVAwAJ
>>> Try going to another computer on the network and enter the address of 
>>> the weewx belchertown address computer.
>>>
>>> On Sun, Mar 7, 2021 at 7:12 PM David Prellwitz  
>>> wrote:
>>>
>>>> More info - looking at syslog, i notice that 8, 11, 15 season files 
>>>> generated, but  are written to /home/weewx/public_html. Sometimes i'll get 
>>>> 2 files written to /home/weewx/public_html/weewx.  But, still no updates 
>>>> on 
>>>> belchertown web page. I'm now officially confused as to where skin.conf, 
>>>> graphs.conf need to be in relationship to /home/weewx. 
>>>> /David
>>>> On Sunday, March 7, 2021 at 1:36:35 PM UTC-8 David Prellwitz wrote:
>>>>
>>>>> New issue; i can't get graphs.conf to work, irrespective of where i 
>>>>> put it. It's now in /home/weewx/skins/belchertown directory with 
>>>>> graphs.conf.example file. I've even changed example filename - still 
>>>>> can't 
>>>>> get belchertown skin to use the minor changes i made to the graphs. It 
>>>>> has 
>>>>> to be a configuration issue, something i've overlooked. help!
>>>>> /David
>>>>>
>>>>> On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz wrote:
>>>>>
>>>>>> kool! thanks!
>>>>>>
>>>>>> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Try localhost/weewx/belchertown
>>>>>>>
>>>>>>> Dave - KB1PVH
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Sent from my Galaxy S21
>>>>>>>
>>>>>>> On Sat, Mar 

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

I've been running debug since the beginning! Attached is a  text file with 
200 line extract of syslog, 100 lines of "/var/log/debug",  100 lines of 
"/var/log/messages"; next is a copy of my weewx.conf. Let me know if you'd 
like to have skin.conf and graphs.conf.
/David

On Monday, March 8, 2021 at 12:28:19 AM UTC-8 gjr80 wrote:

> Hi,
>
> I suggest as a start you edit weewx.conf, set debug=1, save weewx.conf and 
> the restart WeeWX. Let WeeWX run for at least two report cycles and then 
> post a log extract here showing the entire WeeWX startup and the two report 
> cycles. Then we can see what WeeWX and the skins are doing.
>
> Gary
>
> On Monday, 8 March 2021 at 15:30:41 UTC+10 david.a@gmail.com wrote:
>
>> lecoqacr - i can access the belchertown link from my mobile, which is 
>> sharing the same meshed net. Interesting, both Belchertown homepages show a 
>> "last updated" date as yesterday noon; i've restarted all aspects of this 
>> machine (Debian 10 on a Dell laptop), from the laptop thru weewx (three 
>> times) and wee-reports (atleast 10 times). but all of the Belchertown pages 
>> show yesterday noon as the last update. However, the Weewx default skin 
>> updates and shows current data. That's why i think its an issue with my 
>> weewx.conf/skin.conf/graphs.conf files - and/or their location...
>>
>>
>> On Sunday, March 7, 2021 at 7:23:41 PM UTC-8 lecoqacr...@gmail.com wrote:
>>
>>> Maybe this thread is what you are having a problem with.
>>>
>>>  https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/O-wO1GiVAwAJ
>>> Try going to another computer on the network and enter the address of 
>>> the weewx belchertown address computer.
>>>
>>> On Sun, Mar 7, 2021 at 7:12 PM David Prellwitz  
>>> wrote:
>>>
>>>> More info - looking at syslog, i notice that 8, 11, 15 season files 
>>>> generated, but  are written to /home/weewx/public_html. Sometimes i'll get 
>>>> 2 files written to /home/weewx/public_html/weewx.  But, still no updates 
>>>> on 
>>>> belchertown web page. I'm now officially confused as to where skin.conf, 
>>>> graphs.conf need to be in relationship to /home/weewx. 
>>>> /David
>>>> On Sunday, March 7, 2021 at 1:36:35 PM UTC-8 David Prellwitz wrote:
>>>>
>>>>> New issue; i can't get graphs.conf to work, irrespective of where i 
>>>>> put it. It's now in /home/weewx/skins/belchertown directory with 
>>>>> graphs.conf.example file. I've even changed example filename - still 
>>>>> can't 
>>>>> get belchertown skin to use the minor changes i made to the graphs. It 
>>>>> has 
>>>>> to be a configuration issue, something i've overlooked. help!
>>>>> /David
>>>>>
>>>>> On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz wrote:
>>>>>
>>>>>> kool! thanks!
>>>>>>
>>>>>> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Try localhost/weewx/belchertown
>>>>>>>
>>>>>>> Dave - KB1PVH
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Sent from my Galaxy S21
>>>>>>>
>>>>>>> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz  
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I installed the Belchertown skin; configured weewx.conf and 
>>>>>>>> skin.conf; stopped and started weewx; corrected duplication error in 
>>>>>>>> weewx.conf and stopped/restarted weews - no errors. Checked file 
>>>>>>>> date/times 
>>>>>>>> in /home/weewx/public_html/Belchertown_html directory and files are 
>>>>>>>> being 
>>>>>>>> updated.  However, when i look at 'localhost/weewx' i get the original 
>>>>>>>> skin. when i enter 192.168.82.24 (url of this machine) i get the nginx 
>>>>>>>> welcome screen.
>>>>>>>>
>>>>>>>> I believe it's a config or a setup issue on my part, but i don't 
>>>>>>>> know where to look. I'm sure i've failed to link the Belchertown skin 
>>>>>>>> to 
>>>>>>>> the web engine, just not sure how that link is setup. Sugges

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

lecoqacr - i can access the belchertown link from my mobile, which is 
sharing the same meshed net. Interesting, both Belchertown homepages show a 
"last updated" date as yesterday noon; i've restarted all aspects of this 
machine (Debian 10 on a Dell laptop), from the laptop thru weewx (three 
times) and wee-reports (atleast 10 times). but all of the Belchertown pages 
show yesterday noon as the last update. However, the Weewx default skin 
updates and shows current data. That's why i think its an issue with my 
weewx.conf/skin.conf/graphs.conf files - and/or their location...


On Sunday, March 7, 2021 at 7:23:41 PM UTC-8 lecoqacr...@gmail.com wrote:

> Maybe this thread is what you are having a problem with.
>
>  https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/O-wO1GiVAwAJ
> Try going to another computer on the network and enter the address of the 
> weewx belchertown address computer.
>
> On Sun, Mar 7, 2021 at 7:12 PM David Prellwitz  
> wrote:
>
>> More info - looking at syslog, i notice that 8, 11, 15 season files 
>> generated, but  are written to /home/weewx/public_html. Sometimes i'll get 
>> 2 files written to /home/weewx/public_html/weewx.  But, still no updates on 
>> belchertown web page. I'm now officially confused as to where skin.conf, 
>> graphs.conf need to be in relationship to /home/weewx. 
>> /David
>> On Sunday, March 7, 2021 at 1:36:35 PM UTC-8 David Prellwitz wrote:
>>
>>> New issue; i can't get graphs.conf to work, irrespective of where i put 
>>> it. It's now in /home/weewx/skins/belchertown directory with 
>>> graphs.conf.example file. I've even changed example filename - still can't 
>>> get belchertown skin to use the minor changes i made to the graphs. It has 
>>> to be a configuration issue, something i've overlooked. help!
>>> /David
>>>
>>> On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz wrote:
>>>
>>>> kool! thanks!
>>>>
>>>> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com wrote:
>>>>
>>>>> Try localhost/weewx/belchertown
>>>>>
>>>>> Dave - KB1PVH
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Sent from my Galaxy S21
>>>>>
>>>>> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz  
>>>>> wrote:
>>>>>
>>>>>> I installed the Belchertown skin; configured weewx.conf and 
>>>>>> skin.conf; stopped and started weewx; corrected duplication error in 
>>>>>> weewx.conf and stopped/restarted weews - no errors. Checked file 
>>>>>> date/times 
>>>>>> in /home/weewx/public_html/Belchertown_html directory and files are 
>>>>>> being 
>>>>>> updated.  However, when i look at 'localhost/weewx' i get the original 
>>>>>> skin. when i enter 192.168.82.24 (url of this machine) i get the nginx 
>>>>>> welcome screen.
>>>>>>
>>>>>> I believe it's a config or a setup issue on my part, but i don't know 
>>>>>> where to look. I'm sure i've failed to link the Belchertown skin to the 
>>>>>> web 
>>>>>> engine, just not sure how that link is setup. Suggestions as to where to 
>>>>>> look?
>>>>>> /David
>>>>>>
>>>>>> -- 
>>>>>> 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.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>>
>>>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/929bfde0-c860-4105-9fcd-89551acdfa88n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/929bfde0-c860-4105-9fcd-89551acdfa88n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/056f0e19-0b13-4beb-b3e0-9038d42edfccn%40googlegroups.com.

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

More info - looking at syslog, i notice that 8, 11, 15 season files 
generated, but  are written to /home/weewx/public_html. Sometimes i'll get 
2 files written to /home/weewx/public_html/weewx.  But, still no updates on 
belchertown web page. I'm now officially confused as to where skin.conf, 
graphs.conf need to be in relationship to /home/weewx. 
/David
On Sunday, March 7, 2021 at 1:36:35 PM UTC-8 David Prellwitz wrote:

> New issue; i can't get graphs.conf to work, irrespective of where i put 
> it. It's now in /home/weewx/skins/belchertown directory with 
> graphs.conf.example file. I've even changed example filename - still can't 
> get belchertown skin to use the minor changes i made to the graphs. It has 
> to be a configuration issue, something i've overlooked. help!
> /David
>
> On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz wrote:
>
>> kool! thanks!
>>
>> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com wrote:
>>
>>> Try localhost/weewx/belchertown
>>>
>>> Dave - KB1PVH
>>>
>>>
>>>
>>>
>>> Sent from my Galaxy S21
>>>
>>> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz  
>>> wrote:
>>>
>>>> I installed the Belchertown skin; configured weewx.conf and skin.conf; 
>>>> stopped and started weewx; corrected duplication error in weewx.conf and 
>>>> stopped/restarted weews - no errors. Checked file date/times in 
>>>> /home/weewx/public_html/Belchertown_html directory and files are being 
>>>> updated.  However, when i look at 'localhost/weewx' i get the original 
>>>> skin. when i enter 192.168.82.24 (url of this machine) i get the nginx 
>>>> welcome screen.
>>>>
>>>> I believe it's a config or a setup issue on my part, but i don't know 
>>>> where to look. I'm sure i've failed to link the Belchertown skin to the 
>>>> web 
>>>> engine, just not sure how that link is setup. Suggestions as to where to 
>>>> look?
>>>> /David
>>>>
>>>> -- 
>>>> 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.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/929bfde0-c860-4105-9fcd-89551acdfa88n%40googlegroups.com.

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

New issue; i can't get graphs.conf to work, irrespective of where i put it. 
It's now in /home/weewx/skins/belchertown directory with 
graphs.conf.example file. I've even changed example filename - still can't 
get belchertown skin to use the minor changes i made to the graphs. It has 
to be a configuration issue, something i've overlooked. help!
/David

On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz wrote:

> kool! thanks!
>
> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com wrote:
>
>> Try localhost/weewx/belchertown
>>
>> Dave - KB1PVH
>>
>>
>>
>>
>> Sent from my Galaxy S21
>>
>> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz  
>> wrote:
>>
>>> I installed the Belchertown skin; configured weewx.conf and skin.conf; 
>>> stopped and started weewx; corrected duplication error in weewx.conf and 
>>> stopped/restarted weews - no errors. Checked file date/times in 
>>> /home/weewx/public_html/Belchertown_html directory and files are being 
>>> updated.  However, when i look at 'localhost/weewx' i get the original 
>>> skin. when i enter 192.168.82.24 (url of this machine) i get the nginx 
>>> welcome screen.
>>>
>>> I believe it's a config or a setup issue on my part, but i don't know 
>>> where to look. I'm sure i've failed to link the Belchertown skin to the web 
>>> engine, just not sure how that link is setup. Suggestions as to where to 
>>> look?
>>> /David
>>>
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c069fc99-8cfa-460d-9e29-9f8d919b4152n%40googlegroups.com.

Re: [weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

kool! thanks!

On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com wrote:

> Try localhost/weewx/belchertown
>
> Dave - KB1PVH
>
>
>
>
> Sent from my Galaxy S21
>
> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz  
> wrote:
>
>> I installed the Belchertown skin; configured weewx.conf and skin.conf; 
>> stopped and started weewx; corrected duplication error in weewx.conf and 
>> stopped/restarted weews - no errors. Checked file date/times in 
>> /home/weewx/public_html/Belchertown_html directory and files are being 
>> updated.  However, when i look at 'localhost/weewx' i get the original 
>> skin. when i enter 192.168.82.24 (url of this machine) i get the nginx 
>> welcome screen.
>>
>> I believe it's a config or a setup issue on my part, but i don't know 
>> where to look. I'm sure i've failed to link the Belchertown skin to the web 
>> engine, just not sure how that link is setup. Suggestions as to where to 
>> look?
>> /David
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4ea4a232-73e4-41a3-968d-fac2ce6fef4an%40googlegroups.com.

[weewx-user] Belchertown skin not linked to nginx

[David Prellwitz]

I installed the Belchertown skin; configured weewx.conf and skin.conf; 
stopped and started weewx; corrected duplication error in weewx.conf and 
stopped/restarted weews - no errors. Checked file date/times in 
/home/weewx/public_html/Belchertown_html directory and files are being 
updated.  However, when i look at 'localhost/weewx' i get the original 
skin. when i enter 192.168.82.24 (url of this machine) i get the nginx 
welcome screen.

I believe it's a config or a setup issue on my part, but i don't know where 
to look. I'm sure i've failed to link the Belchertown skin to the web 
engine, just not sure how that link is setup. Suggestions as to where to 
look?
/David

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com.

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Duh, perhaps i ! those glasses! what's a 'release' between commands, 
anywho? thanks!
On Thursday, March 4, 2021 at 9:43:42 PM UTC-8 gjr80 wrote:

> Perhaps I need to change my glasses, but the last time I looked 
> *weewx-belchertown-release-1.2.tar.gz* is different to 
> *weewx-belchertown-1.2.tar.gz*.
>
> Perhaps you should try:
>
> $ sudo /home/weewx/bin/wee_extension --install 
> /home/david/Downloads/weewx-belchertown-release-1.2.tar.gz
>
> Gary
> On Friday, 5 March 2021 at 15:34:46 UTC+10 david.a@gmail.com wrote:
>
>> Gary:
>> ls -l /home/david/Downloads:
>> -r 1 david david 1518145 Mar  3 18:02 
>> weewx-belchertown-release-1.2.tar.gz
>> and i used the fully qualified sudo string for execution:
>> sudo /home/weewx/bin/wee_extension --install 
>> /home/david/Downloads/weewx-belchertown-1.2.tar.gz
>>
>> On Thursday, March 4, 2021 at 6:40:46 PM UTC-8 gjr80 wrote:
>>
>>> Did you ls the directory containing the extension package to confirm the 
>>> file name? According to the Belchertown repo the 1.2 extension package is 
>>> named weewx-belchertown-release-1.2.tar.gz, slightly different to that used 
>>> in your commands.
>>>
>>> Gary
>>>
>>> On Friday, 5 March 2021 at 12:28:08 UTC+10 david.a@gmail.com wrote:
>>>
>>>> Vince - thanks! I'll take that approach on the imports!
>>>>
>>>> Glenn:
>>>> I had hand-transcribed the command entry - i'd entered the correct 
>>>> command string:
>>>> sudo /home/weewx/bin/wee_extension --install 
>>>> /home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
>>>> /tmp/wee-extension-out.txt
>>>>
>>>> This is the results:
>>>> ==
>>>> Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
>>>> Traceback (most recent call last):
>>>>   File "/home/weewx/bin/wee_extension", line 88, in 
>>>> main()
>>>>   File "/home/weewx/bin/wee_extension", line 80, in main
>>>> ext.install_extension(options.install)
>>>>
>>>>   File "/home/weewx/bin/weecfg/extension.py", line 134, in 
>>>> install_extension
>>>> raise InstallError("Extension '%s' not found." % extension_path)
>>>> weecfg.extension.InstallError: Extension 
>>>> '/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.
>>>> 
>>>>
>>>> No info about where to put the tar.gz file. Again, i'd used the 
>>>> "setup.py" script to install weewx, so all the relevant folders are off 
>>>> "/home". 
>>>> /David
>>>> On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:
>>>>
>>>>> /home/david/Downloads/weewx-belchertown.1.2.tar.gz 
>>>>>
>>>>> Check the filename 
>>>>>
>>>>> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet) 
>>>>> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at 
>>>>>
>>>>> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>>>>>  
>>>>>
>>>>> note: there are 2 dashes in the correct name. 
>>>>>
>>>>> On 04/03/2021, David Prellwitz  wrote: 
>>>>> > error trying to install belchertown. my weewx install was using 
>>>>> setup.py. I 
>>>>> > 
>>>>> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
>>>>> folder. 
>>>>> > I ran the sudo wee-extension command and get "File 
>>>>> > "/home/weewx/bin/weecfg/extension.py", line 134, in 
>>>>> install_extension 
>>>>> > weecfg.extension.InstallError: Extension 
>>>>> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found. 
>>>>> > can't find what i did wrong. Should i extract the tar.gz file first? 
>>>>> move 
>>>>> > it to another folder to start install? 
>>>>> > /David 
>>>>> > 
>>>>> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote: 
>>>>> > 
>>>>> >> Lightning is difficult because there's no units for 'energy' in the 
>>>>> UDP 
>>>>> >> API. I might also add perhaps don't both

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Gary:
ls -l /home/david/Downloads:
-r 1 david david 1518145 Mar  3 18:02 
weewx-belchertown-release-1.2.tar.gz
and i used the fully qualified sudo string for execution:
sudo /home/weewx/bin/wee_extension --install 
/home/david/Downloads/weewx-belchertown-1.2.tar.gz

On Thursday, March 4, 2021 at 6:40:46 PM UTC-8 gjr80 wrote:

> Did you ls the directory containing the extension package to confirm the 
> file name? According to the Belchertown repo the 1.2 extension package is 
> named weewx-belchertown-release-1.2.tar.gz, slightly different to that used 
> in your commands.
>
> Gary
>
> On Friday, 5 March 2021 at 12:28:08 UTC+10 david.a@gmail.com wrote:
>
>> Vince - thanks! I'll take that approach on the imports!
>>
>> Glenn:
>> I had hand-transcribed the command entry - i'd entered the correct 
>> command string:
>> sudo /home/weewx/bin/wee_extension --install 
>> /home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
>> /tmp/wee-extension-out.txt
>>
>> This is the results:
>> ==
>> Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/wee_extension", line 88, in 
>> main()
>>   File "/home/weewx/bin/wee_extension", line 80, in main
>> ext.install_extension(options.install)
>>
>>   File "/home/weewx/bin/weecfg/extension.py", line 134, in 
>> install_extension
>> raise InstallError("Extension '%s' not found." % extension_path)
>> weecfg.extension.InstallError: Extension 
>> '/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.
>> 
>>
>> No info about where to put the tar.gz file. Again, i'd used the 
>> "setup.py" script to install weewx, so all the relevant folders are off 
>> "/home". 
>> /David
>> On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:
>>
>>> /home/david/Downloads/weewx-belchertown.1.2.tar.gz 
>>>
>>> Check the filename 
>>>
>>> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet) 
>>> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at 
>>>
>>> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>>>  
>>>
>>> note: there are 2 dashes in the correct name. 
>>>
>>> On 04/03/2021, David Prellwitz  wrote: 
>>> > error trying to install belchertown. my weewx install was using 
>>> setup.py. I 
>>> > 
>>> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
>>> folder. 
>>> > I ran the sudo wee-extension command and get "File 
>>> > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension 
>>> > weecfg.extension.InstallError: Extension 
>>> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found. 
>>> > can't find what i did wrong. Should i extract the tar.gz file first? 
>>> move 
>>> > it to another folder to start install? 
>>> > /David 
>>> > 
>>> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote: 
>>> > 
>>> >> Lightning is difficult because there's no units for 'energy' in the 
>>> UDP 
>>> >> API. I might also add perhaps don't bother, as lightning is bogus 
>>> anyway. 
>>> >> 
>>> >> It's what your sensor reported, but it is not remotely close to the 
>>> >> crowd-sourced info their web or mobile interfaces provide, of which 
>>> your 
>>> >> sensor measurements are just a small part of what they aggregate and 
>>> >> display. 
>>> >> 
>>> >> I think the simplest thing to do is map stuff and see what the driver 
>>> puts 
>>> >> 
>>> >> in the db. It's possible the driver forces metric (or not metric) and 
>>> >> does the conversions under the hood before weewx ever sees the 
>>> assembled 
>>> >> LOOP. Sometimes it's easier to just look at the code or do a little 
>>> >> experimentation. 
>>> >> 
>>> >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 david.a@gmail.com 
>>> >> wrote: 
>>> >> 
>>> >>> Vince, if i'm reading your post correctly (and carefully reading the 
>>> >>> links you've provided), weewx.sdb stores all elements in a unit-base 
>>> type 
>

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Vince - thanks! I'll take that approach on the imports!

Glenn:
I had hand-transcribed the command entry - i'd entered the correct command 
string:
sudo /home/weewx/bin/wee_extension --install 
/home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
/tmp/wee-extension-out.txt

This is the results:
==
Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
Traceback (most recent call last):
  File "/home/weewx/bin/wee_extension", line 88, in 
main()
  File "/home/weewx/bin/wee_extension", line 80, in main
ext.install_extension(options.install)
  File "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension
raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension 
'/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.


No info about where to put the tar.gz file. Again, i'd used the "setup.py" 
script to install weewx, so all the relevant folders are off "/home". 
/David
On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:

> /home/david/Downloads/weewx-belchertown.1.2.tar.gz
>
> Check the filename
>
> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet)
> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at
>
> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>
> note: there are 2 dashes in the correct name.
>
> On 04/03/2021, David Prellwitz  wrote:
> > error trying to install belchertown. my weewx install was using 
> setup.py. I
> >
> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
> folder.
> > I ran the sudo wee-extension command and get "File
> > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension
> > weecfg.extension.InstallError: Extension
> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found.
> > can't find what i did wrong. Should i extract the tar.gz file first? move
> > it to another folder to start install?
> > /David
> >
> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote:
> >
> >> Lightning is difficult because there's no units for 'energy' in the UDP
> >> API. I might also add perhaps don't bother, as lightning is bogus 
> anyway.
> >>
> >> It's what your sensor reported, but it is not remotely close to the
> >> crowd-sourced info their web or mobile interfaces provide, of which your
> >> sensor measurements are just a small part of what they aggregate and
> >> display.
> >>
> >> I think the simplest thing to do is map stuff and see what the driver 
> puts
> >>
> >> in the db. It's possible the driver forces metric (or not metric) and
> >> does the conversions under the hood before weewx ever sees the assembled
> >> LOOP. Sometimes it's easier to just look at the code or do a little
> >> experimentation.
> >>
> >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 david.a@gmail.com
> >> wrote:
> >>
> >>> Vince, if i'm reading your post correctly (and carefully reading the
> >>> links you've provided), weewx.sdb stores all elements in a unit-base 
> type
> >>>
> >>> as specified in the usUnits group (*"Each observation type, such
> >>> as outTemp or pressure, is associated with a unit group, such
> >>> as group_temperature or group_pressure. Each unit group is associated
> >>> with
> >>> a unit type such as degree_F or mbar.*" So, as my weewx.conf has an
> >>> entry in [StdConvert] section "target_unit = us " i can assume that all
> >>> weewx.sdb entries conform to the US Group column. further assumption is
> >>> that if WeatherFlow Tempest device provides data in m/b and i spec it 
> as
> >>>
> >>> m/b for the LOOP process, it will be converted to inHg as part of the 
> UDP
> >>>
> >>> LOOP process. If i import data from WF using the API's i just need to
> >>> spec
> >>> the API page's listing of unit WF will be providing for those fields 
> and
> >>>
> >>> wee_import will correct those to the weewx.sdb needed units? If i wish
> >>> to
> >>> have lightning information, i'll need to map to those "signal7/8" 
> and/or
> >>>
> >>> "xxx/yyy" fields, and i'll have to figure out what units they use?
> >>> thanks!
> >>>
> >>>
> >>> On Wednesday, March 3, 2021 a

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

error trying to install belchertown. my weewx install was using setup.py. I 
downloaded the belchertown 1.2 tar.gz into my home/david/Downloads folder. 
I ran the sudo wee-extension command and get "File 
"/home/weewx/bin/weecfg/extension.py", line 134, in install_extension 
weecfg.extension.InstallError: Extension 
'/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found.
can't find what i did wrong. Should i extract the tar.gz file first? move 
it to another folder to start install?
/David

On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote:

> Lightning is difficult because there's no units for 'energy' in the UDP 
> API.  I might also add perhaps don't bother, as lightning is bogus anyway. 
>  It's what your sensor reported, but it is not remotely close to the 
> crowd-sourced info their web or mobile interfaces provide, of which your 
> sensor measurements are just a small part of what they aggregate and 
> display.
>
> I think the simplest thing to do is map stuff and see what the driver puts 
> in the db.   It's possible the driver forces metric (or not metric) and 
> does the conversions under the hood before weewx ever sees the assembled 
> LOOP.  Sometimes it's easier to just look at the code or do a little 
> experimentation.
>
> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 david.a@gmail.com 
> wrote:
>
>> Vince, if i'm reading your post correctly (and carefully reading the 
>> links you've provided), weewx.sdb stores all elements in a unit-base type 
>> as specified in the usUnits group  (*"Each observation type, such 
>> as outTemp or pressure, is associated with a unit group, such 
>> as group_temperature or group_pressure. Each unit group is associated with 
>> a unit type such as degree_F or mbar.*"  So, as my weewx.conf has an 
>> entry in [StdConvert] section "target_unit = us " i can assume that all 
>> weewx.sdb entries conform to the US Group column. further assumption is 
>> that if WeatherFlow Tempest device provides data in m/b and i spec it as 
>> m/b for the LOOP process, it will be converted to inHg as part of the UDP 
>> LOOP process. If i import data from WF using the API's i just need to spec 
>> the API page's listing of unit WF will be providing for those fields and 
>> wee_import will correct those to the weewx.sdb needed units?  If i wish to 
>> have lightning information, i'll need to map to those "signal7/8" and/or 
>> "xxx/yyy" fields, and i'll have to figure out what units they use?
>> thanks!
>>
>>
>> On Wednesday, March 3, 2021 at 11:34:05 AM UTC-8 David Prellwitz wrote:
>>
>>> Vince - yea, my way of apologizing for running down some rabbit hole i 
>>> didn't need to. Thanks for the guidance, I'll map it out and see if it 
>>> works. I'll try to get a decent mapping setup and forward to you for 
>>> comment.
>>> My next attempt is to install and use Belchertown skins.  
>>>
>>> On Wednesday, March 3, 2021 at 8:31:12 AM UTC-8 vince wrote:
>>>
>>>> That's a lot of words, but I still think you're possibly overthinking.
>>>>
>>>> Anyway,  I'm pretty lost re: what you're actually trying to do.
>>>>
>>>>- There is a sample mapping of Tempest UDP elements to Weewx 
>>>>database elements both in the driver code and in the docs on the github 
>>>>site for the driver.
>>>>- There are a couple forks of the original driver, but they all 
>>>>have an example looking like (this map) 
>>>>
>>>> <https://github.com/jjvdgeer/weatherflow-udp/blob/master/sample_Tempest_sensor_map>
>>>>
>>>> So using outside temperature as an example, you'll see a mapping that 
>>>> looks like:
>>>>
>>>>- outTemp = air_temperature.ST-0025.obs_st
>>>>
>>>> Which means:
>>>>
>>>>- map the driver's air_temperature element
>>>>- for sensor ST-0025
>>>>- from the obs_st observation type emitted by the WF gear
>>>>- to weewx's outTemp database element
>>>>
>>>> The driver's terminology is in the code around line 211 of the driver 
>>>> (here) 
>>>> <https://github.com/jjvdgeer/weatherflow-udp/blob/master/bin/user/weatherflowudp.py>.
>>>>  
>>>>   So why is it different ?  Because the driver references the WF UDP API 
>>>> (here) <https://weatherflow.github.io/Tempest/api/udp/v143/> which 
>>>> uses the description 'air temperature' in the obs_st (tempe

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

You've been patient, thanks! I'll review the links and extensions and move 
forward. 

On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 David Prellwitz wrote:

> Vince, if i'm reading your post correctly (and carefully reading the links 
> you've provided), weewx.sdb stores all elements in a unit-base type as 
> specified in the usUnits group  (*"Each observation type, such 
> as outTemp or pressure, is associated with a unit group, such 
> as group_temperature or group_pressure. Each unit group is associated with 
> a unit type such as degree_F or mbar.*"  So, as my weewx.conf has an 
> entry in [StdConvert] section "target_unit = us " i can assume that all 
> weewx.sdb entries conform to the US Group column. further assumption is 
> that if WeatherFlow Tempest device provides data in m/b and i spec it as 
> m/b for the LOOP process, it will be converted to inHg as part of the UDP 
> LOOP process. If i import data from WF using the API's i just need to spec 
> the API page's listing of unit WF will be providing for those fields and 
> wee_import will correct those to the weewx.sdb needed units?  If i wish to 
> have lightning information, i'll need to map to those "signal7/8" and/or 
> "xxx/yyy" fields, and i'll have to figure out what units they use?
> thanks!
>
>
> On Wednesday, March 3, 2021 at 11:34:05 AM UTC-8 David Prellwitz wrote:
>
>> Vince - yea, my way of apologizing for running down some rabbit hole i 
>> didn't need to. Thanks for the guidance, I'll map it out and see if it 
>> works. I'll try to get a decent mapping setup and forward to you for 
>> comment.
>> My next attempt is to install and use Belchertown skins.  
>>
>> On Wednesday, March 3, 2021 at 8:31:12 AM UTC-8 vince wrote:
>>
>>> That's a lot of words, but I still think you're possibly overthinking.
>>>
>>> Anyway,  I'm pretty lost re: what you're actually trying to do.
>>>
>>>- There is a sample mapping of Tempest UDP elements to Weewx 
>>>database elements both in the driver code and in the docs on the github 
>>>site for the driver.
>>>- There are a couple forks of the original driver, but they all have 
>>>an example looking like (this map) 
>>>
>>> <https://github.com/jjvdgeer/weatherflow-udp/blob/master/sample_Tempest_sensor_map>
>>>
>>> So using outside temperature as an example, you'll see a mapping that 
>>> looks like:
>>>
>>>- outTemp = air_temperature.ST-0025.obs_st
>>>
>>> Which means:
>>>
>>>- map the driver's air_temperature element
>>>- for sensor ST-0025
>>>- from the obs_st observation type emitted by the WF gear
>>>- to weewx's outTemp database element
>>>
>>> The driver's terminology is in the code around line 211 of the driver 
>>> (here) 
>>> <https://github.com/jjvdgeer/weatherflow-udp/blob/master/bin/user/weatherflowudp.py>.
>>>  
>>>   So why is it different ?  Because the driver references the WF UDP API 
>>> (here) <https://weatherflow.github.io/Tempest/api/udp/v143/> which uses 
>>> the description 'air temperature' in the obs_st (tempest observation) type. 
>>>   The driver is written to reconcile versus the vendor's public API.   The 
>>> mapping reconciles that to weewx-speak.
>>>
>>> So what units does outTemp use and how do you figure THAT out ?
>>>
>>>- it's set in your weewx.conf or skin.conf for the item 
>>>group_temperature
>>>- which is documented in the Customization Guide 
>>><http://weewx.com/docs/customizing.htm#units> appendix detailing the 
>>>units weewx uses for each thing in the database
>>>
>>> So if you want to see the mapping of any database element to units, just 
>>> reference the Customization Guide appendix.
>>>
>>> This stuff really is documented in excruciating detail, but it is a bit 
>>> of a trail of things to follow to put all the pieces together notionally.
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/364689f3-82af-451b-8788-8fc56e77c041n%40googlegroups.com.

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Vince, if i'm reading your post correctly (and carefully reading the links 
you've provided), weewx.sdb stores all elements in a unit-base type as 
specified in the usUnits group  (*"Each observation type, such 
as outTemp or pressure, is associated with a unit group, such 
as group_temperature or group_pressure. Each unit group is associated with 
a unit type such as degree_F or mbar.*"  So, as my weewx.conf has an entry 
in [StdConvert] section "target_unit = us " i can assume that all weewx.sdb 
entries conform to the US Group column. further assumption is that if 
WeatherFlow Tempest device provides data in m/b and i spec it as m/b for 
the LOOP process, it will be converted to inHg as part of the UDP LOOP 
process. If i import data from WF using the API's i just need to spec the 
API page's listing of unit WF will be providing for those fields and 
wee_import will correct those to the weewx.sdb needed units?  If i wish to 
have lightning information, i'll need to map to those "signal7/8" and/or 
"xxx/yyy" fields, and i'll have to figure out what units they use?
thanks!


On Wednesday, March 3, 2021 at 11:34:05 AM UTC-8 David Prellwitz wrote:

> Vince - yea, my way of apologizing for running down some rabbit hole i 
> didn't need to. Thanks for the guidance, I'll map it out and see if it 
> works. I'll try to get a decent mapping setup and forward to you for 
> comment.
> My next attempt is to install and use Belchertown skins.  
>
> On Wednesday, March 3, 2021 at 8:31:12 AM UTC-8 vince wrote:
>
>> That's a lot of words, but I still think you're possibly overthinking.
>>
>> Anyway,  I'm pretty lost re: what you're actually trying to do.
>>
>>- There is a sample mapping of Tempest UDP elements to Weewx database 
>>elements both in the driver code and in the docs on the github site for 
>> the 
>>driver.
>>- There are a couple forks of the original driver, but they all have 
>>an example looking like (this map) 
>>
>> <https://github.com/jjvdgeer/weatherflow-udp/blob/master/sample_Tempest_sensor_map>
>>
>> So using outside temperature as an example, you'll see a mapping that 
>> looks like:
>>
>>- outTemp = air_temperature.ST-0025.obs_st
>>
>> Which means:
>>
>>- map the driver's air_temperature element
>>- for sensor ST-0025
>>- from the obs_st observation type emitted by the WF gear
>>- to weewx's outTemp database element
>>
>> The driver's terminology is in the code around line 211 of the driver 
>> (here) 
>> <https://github.com/jjvdgeer/weatherflow-udp/blob/master/bin/user/weatherflowudp.py>.
>>  
>>   So why is it different ?  Because the driver references the WF UDP API 
>> (here) <https://weatherflow.github.io/Tempest/api/udp/v143/> which uses 
>> the description 'air temperature' in the obs_st (tempest observation) type. 
>>   The driver is written to reconcile versus the vendor's public API.   The 
>> mapping reconciles that to weewx-speak.
>>
>> So what units does outTemp use and how do you figure THAT out ?
>>
>>- it's set in your weewx.conf or skin.conf for the item 
>>group_temperature
>>- which is documented in the Customization Guide 
>><http://weewx.com/docs/customizing.htm#units> appendix detailing the 
>>units weewx uses for each thing in the database
>>
>> So if you want to see the mapping of any database element to units, just 
>> reference the Customization Guide appendix.
>>
>> This stuff really is documented in excruciating detail, but it is a bit 
>> of a trail of things to follow to put all the pieces together notionally.
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/75ff0b6e-3049-4ff3-8ae7-74a7c9dda8d9n%40googlegroups.com.

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Vince - yea, my way of apologizing for running down some rabbit hole i 
didn't need to. Thanks for the guidance, I'll map it out and see if it 
works. I'll try to get a decent mapping setup and forward to you for 
comment.
My next attempt is to install and use Belchertown skins.  

On Wednesday, March 3, 2021 at 8:31:12 AM UTC-8 vince wrote:

> That's a lot of words, but I still think you're possibly overthinking.
>
> Anyway,  I'm pretty lost re: what you're actually trying to do.
>
>- There is a sample mapping of Tempest UDP elements to Weewx database 
>elements both in the driver code and in the docs on the github site for 
> the 
>driver.
>- There are a couple forks of the original driver, but they all have 
>an example looking like (this map) 
>
> 
>
> So using outside temperature as an example, you'll see a mapping that 
> looks like:
>
>- outTemp = air_temperature.ST-0025.obs_st
>
> Which means:
>
>- map the driver's air_temperature element
>- for sensor ST-0025
>- from the obs_st observation type emitted by the WF gear
>- to weewx's outTemp database element
>
> The driver's terminology is in the code around line 211 of the driver 
> (here) 
> .
>  
>   So why is it different ?  Because the driver references the WF UDP API 
> (here)  which uses 
> the description 'air temperature' in the obs_st (tempest observation) type. 
>   The driver is written to reconcile versus the vendor's public API.   The 
> mapping reconciles that to weewx-speak.
>
> So what units does outTemp use and how do you figure THAT out ?
>
>- it's set in your weewx.conf or skin.conf for the item 
>group_temperature
>- which is documented in the Customization Guide 
> appendix detailing the 
>units weewx uses for each thing in the database
>
> So if you want to see the mapping of any database element to units, just 
> reference the Customization Guide appendix.
>
> This stuff really is documented in excruciating detail, but it is a bit of 
> a trail of things to follow to put all the pieces together notionally.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/755c6aa7-0b16-44bc-988c-20a70bfb5701n%40googlegroups.com.

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Thank you both for the replies! I've dived into the end of this pool 
without comprehending its depth. 
This all started after spending more than a few frustrating days trying to 
find the documents for, or figure out a proper set of, field maps to cover 
three apparent subsets of WeatherFlow data into the Weewx (UDP capture from 
station; Lightning data import; API get from WF) plus slightly different 
field names from some of those CSV headers.  As i looked over each of the 
CSV header entries, each header seemed to have several anomalies (names, 
abbreviations). Then i couldn't find the unit values for each as compared 
to what Weewx was looking for.  I started looking for a definitive source 
for field data-type/unit default values. Then i started looking for what 
each of the field elements actually represented, eg - link wind elements 
(wind gusts, wind lulls, etc), lightning elements (energy, avg distance), 
precipitation elements, and other elements.   I started to map all the 
published fields from WF, Weewx, GitHub, Google Groups, etc to see if i 
could document each use to a valid Weewx field name. So, i found several 
lightning elements mapped to fields with "XXX", "YYY", signal7, signal8, so 
on and so forth. I started looking for a Tempest station data mapping info 
similar to other station data (Acurite, CC3000, etc) found in the Hardware 
section, and tried to find measurement unit values (i.e., m/s vice 
meters-per-second; etc) and defaults for each field element. Not found. So 
i thought i'd try to map all of WF's elements, with measurement values, 
with weewx fields - as many as i could find. But, to do that, i need to 
know what each element represents - on both sides. 

So that's were i sit - trying to use the tools i know to document WF/Weewx 
data fields. Can you provide some useful links and/or point me in the right 
direction to gather such info? I'll try to gather what i can and get it 
back to you if it doesn't exist,
thanks!
On Sunday, February 28, 2021 at 5:31:21 PM UTC-8 tke...@gmail.com wrote:

> Yes, the other tables are "daily summaries." They are strictly an 
> optimization. There's nothing in them that cannot be extracted from the 
> main archive table and, indeed, they can be rebuilt from the latter using 
> the tool wee_database.
>
> WeeWX is multi-threaded, but not in the way you describe. Yes, there is a 
> single "main" thread that blocks, waiting for data, then process it, then 
> stores it in the database. A separate thread handles reporting. Still other 
> threads upload through a RESTful facility.
>
> On the surface, multi-threading data acquisition (or, alternatively, using 
> an async interface) sounds attractive. However, if the goal is to acquire 
> data simultaneously from several sources, that can as easily be 
> accomplished by launching multiple instances of WeeWX. If the goal is to 
> intertwine the various sources and have them all stored in the same table 
> in the same database, that is far more complicated. The simple architecture 
> of WeeWX would be lost. 
>
> However, if you have some concrete, specific, ideas on how to service more 
> than one device simultaneously, then I'm all ears. I would really love to 
> take advantage of the new "async" interfaces in modern versions of Python 
> (unfortunately, the 3rd party libraries needed to use them have not caught 
> up. Specifically, async versions of pyusb and pyserial). But, we are way 
> beyond general ideas. What's needed is a working framework, even if it's 
> merely a prototype.
>
> Through the years, these ideas have come up from time to time. Various 
> alternative architectures have been considered. However, simplicity has 
> always won out. I think the rich ecosystem of 3rd party extensions that 
> surrounds WeeWX has shown that to be a good choice. 
>
> -tk
>
> On Sun, Feb 28, 2021 at 2:44 PM David Prellwitz  
> wrote:
>
>> Thanks for the quick reply!  I apologize for any negative connotations 
>> (not intended), i guess my perceptions and assumptions are off-base! it's 
>> just in all my professional DB roles (25yrs +) i've had to use visual 
>> layout tools to understand existing data creation, utilization, ranges, 
>> applications and operational impacts. These visual tools allowed us to use 
>> as much third-normal form reduction steps as possible to simplify data 
>> architecture to the lowest possible level. My misjudgement of WeeWx layout 
>> and structure is just that, my misjudgement. 
>>
>> Perhaps i am over-thinking things as i try to get basic things done. 
>> Habits of a long life in IT Management/DB Architecture/Programming. I just 
>> think i may be some ideas and observations that may improve WeeWx but, I 
>> can drop these distract

[weewx-user] Re: SQLite schema report

[David Prellwitz]

Side note:
re-reading Vince's post, i had the process backwards - detailed event 
records in Archive table; summary/special info in separate tables... 

On Sunday, February 28, 2021 at 2:44:18 PM UTC-8 David Prellwitz wrote:

> Thanks for the quick reply!  I apologize for any negative connotations 
> (not intended), i guess my perceptions and assumptions are off-base! it's 
> just in all my professional DB roles (25yrs +) i've had to use visual 
> layout tools to understand existing data creation, utilization, ranges, 
> applications and operational impacts. These visual tools allowed us to use 
> as much third-normal form reduction steps as possible to simplify data 
> architecture to the lowest possible level. My misjudgement of WeeWx layout 
> and structure is just that, my misjudgement. 
>
> Perhaps i am over-thinking things as i try to get basic things done. 
> Habits of a long life in IT Management/DB Architecture/Programming. I just 
> think i may be some ideas and observations that may improve WeeWx but, I 
> can drop these distractions if it's an issue. 
>
> Now, the issue I had was the lack of understanding the role of the 
> additional tables - they didn't seem to have any relationship to the 
> archive table; other than Epoch. If i'm reading your statement correctly, 
> all the other tables are the detail records for each of the elements in the 
> archive table - just related by element type ("Name"?) and epoch timestamp? 
> So if i went looking for "Wind Gust Direction" instances, I'd look in the 
> Archive table for "WindGustDir" and find an entry (which represents what, a 
> summary, an average, ?),  and one or more "Archive_day_windGustDir" 
> entries, depending on the frequency of that element's recording? (Assuming 
> archived wind-gust data is recorded for one-minute intervals, but 
> "Archive_day_windGustDir" are recorded at 3second intervals for 
> Wind-Gust-Dir table.)  Knowledge at that level of detail should be known 
> somewhere, right? Perhaps somewhere in GitHub?
>
> How is this useful? It appears to me (IMHO) that a good understanding of 
> the data flow and mapping could help reduce event process time; reduce data 
> storage needs; increase functionality; improve simplicity and make it a 
> better product. Looking at the architecture of WeeWx, the process diagram 
> shows a single thread for each event (i.e., UDP packet arrival); followed 
> by event processing; followed by data-recording; followed by report 
> generation. All of these appear to be serial. If the front end was to be 
> multi-threaded to allow multiple device/station packet reception and placed 
> in a triggered repository that the rest of WeeWx processed, wouldn't WeeWx 
> be able to process multiple stations data without having multiple instances 
> of WeeWx (and multiple SQL db's). A quick, multi-threaded front-end could 
> be prioritized to allow for sub-second processing. Leaving more "leisured" 
> approach for the rest of Weewx to process and create reports. 
>
> I'm a bit rusty in data-mapping (did it from 1975 through 1998) so i'm 
> sure any post-grad would be sharper at this then I am.  Perhaps having some 
> Data Science Professor create a post-doc project that would help (assuming 
> i'm not too far off base here)!  Being retired, i now have time on my hands 
> to assist if anyone thinks that would be useful.
>
> On Saturday, February 27, 2021 at 5:43:09 PM UTC-8 vince wrote:
>
>> I'd suggest your commentary is more than a little bit unfair and 
>> inaccurate, and I'll leave it at that.
>>
>> Weewx by default uses an underlying sqlite3 database and puts its 
>> readings into an 'archive' table that has a large number of fields for the 
>> actual weather measurements.
>>
>> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
>> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `altimeter` REAL, 
>> `appTemp` REAL, `appTemp1` REAL, `barometer` REAL, `batteryStatus1` REAL, 
>> `batteryStatus2` REAL, `batteryStatus3` REAL, `batteryStatus4` REAL, 
>> `batteryStatus5` REAL, `batteryStatus6` REAL, `batteryStatus7` REAL, 
>> `batteryStatus8` REAL, `cloudbase` REAL, `co` REAL, `co2` REAL, 
>> `consBatteryVoltage` REAL, `dewpoint` REAL, `dewpoint1` REAL, `ET` REAL, 
>> `extraHumid1` REAL, `extraHumid2` REAL, `extraHumid3` REAL, `extraHumid4` 
>> REAL, `extraHumid5` REAL, `extraHumid6` REAL, `extraHumid7` REAL, 
>> `extraHumid8` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` 
>> REAL, `extraTemp4` REAL, `extraTemp5` REAL, `extraTemp6` REAL, `extraTemp7` 
>> REAL, `extraTemp8` REAL, `forecast` REAL, `hail` REAL, `hailBatteryStatus` 
>>

[weewx-user] Re: SQLite schema report

[David Prellwitz]

Thanks for the quick reply!  I apologize for any negative connotations (not 
intended), i guess my perceptions and assumptions are off-base! it's just 
in all my professional DB roles (25yrs +) i've had to use visual layout 
tools to understand existing data creation, utilization, ranges, 
applications and operational impacts. These visual tools allowed us to use 
as much third-normal form reduction steps as possible to simplify data 
architecture to the lowest possible level. My misjudgement of WeeWx layout 
and structure is just that, my misjudgement. 

Perhaps i am over-thinking things as i try to get basic things done. Habits 
of a long life in IT Management/DB Architecture/Programming. I just think i 
may be some ideas and observations that may improve WeeWx but, I can drop 
these distractions if it's an issue. 

Now, the issue I had was the lack of understanding the role of the 
additional tables - they didn't seem to have any relationship to the 
archive table; other than Epoch. If i'm reading your statement correctly, 
all the other tables are the detail records for each of the elements in the 
archive table - just related by element type ("Name"?) and epoch timestamp? 
So if i went looking for "Wind Gust Direction" instances, I'd look in the 
Archive table for "WindGustDir" and find an entry (which represents what, a 
summary, an average, ?),  and one or more "Archive_day_windGustDir" 
entries, depending on the frequency of that element's recording? (Assuming 
archived wind-gust data is recorded for one-minute intervals, but 
"Archive_day_windGustDir" are recorded at 3second intervals for 
Wind-Gust-Dir table.)  Knowledge at that level of detail should be known 
somewhere, right? Perhaps somewhere in GitHub?

How is this useful? It appears to me (IMHO) that a good understanding of 
the data flow and mapping could help reduce event process time; reduce data 
storage needs; increase functionality; improve simplicity and make it a 
better product. Looking at the architecture of WeeWx, the process diagram 
shows a single thread for each event (i.e., UDP packet arrival); followed 
by event processing; followed by data-recording; followed by report 
generation. All of these appear to be serial. If the front end was to be 
multi-threaded to allow multiple device/station packet reception and placed 
in a triggered repository that the rest of WeeWx processed, wouldn't WeeWx 
be able to process multiple stations data without having multiple instances 
of WeeWx (and multiple SQL db's). A quick, multi-threaded front-end could 
be prioritized to allow for sub-second processing. Leaving more "leisured" 
approach for the rest of Weewx to process and create reports. 

I'm a bit rusty in data-mapping (did it from 1975 through 1998) so i'm sure 
any post-grad would be sharper at this then I am.  Perhaps having some Data 
Science Professor create a post-doc project that would help (assuming i'm 
not too far off base here)!  Being retired, i now have time on my hands to 
assist if anyone thinks that would be useful.

On Saturday, February 27, 2021 at 5:43:09 PM UTC-8 vince wrote:

> I'd suggest your commentary is more than a little bit unfair and 
> inaccurate, and I'll leave it at that.
>
> Weewx by default uses an underlying sqlite3 database and puts its readings 
> into an 'archive' table that has a large number of fields for the actual 
> weather measurements.
>
> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `altimeter` REAL, 
> `appTemp` REAL, `appTemp1` REAL, `barometer` REAL, `batteryStatus1` REAL, 
> `batteryStatus2` REAL, `batteryStatus3` REAL, `batteryStatus4` REAL, 
> `batteryStatus5` REAL, `batteryStatus6` REAL, `batteryStatus7` REAL, 
> `batteryStatus8` REAL, `cloudbase` REAL, `co` REAL, `co2` REAL, 
> `consBatteryVoltage` REAL, `dewpoint` REAL, `dewpoint1` REAL, `ET` REAL, 
> `extraHumid1` REAL, `extraHumid2` REAL, `extraHumid3` REAL, `extraHumid4` 
> REAL, `extraHumid5` REAL, `extraHumid6` REAL, `extraHumid7` REAL, 
> `extraHumid8` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` 
> REAL, `extraTemp4` REAL, `extraTemp5` REAL, `extraTemp6` REAL, `extraTemp7` 
> REAL, `extraTemp8` REAL, `forecast` REAL, `hail` REAL, `hailBatteryStatus` 
> REAL, `hailRate` REAL, `heatindex` REAL, `heatindex1` REAL, `heatingTemp` 
> REAL, `heatingVoltage` REAL, `humidex` REAL, `humidex1` REAL, `inDewpoint` 
> REAL, `inHumidity` REAL, `inTemp` REAL, `inTempBatteryStatus` REAL, 
> `leafTemp1` REAL, `leafTemp2` REAL, `leafWet1` REAL, `leafWet2` REAL, 
> `lightning_distance` REAL, `lightning_disturber_count` REAL, 
> `lightning_energy` REAL, `lightning_noise_count` REAL, 
> `lightning_strike_count` REAL, `luminosity` REAL, `maxSolarRad` REAL, `nh3` 
> REAL, `no2` REAL, `noise` REAL, `o3` REAL, `outHumidity` REAL, `outTemp` 
> REAL, `outTempBatteryStatus` REAL, `pb` REAL, `pm10_0` REAL, `pm1_0` REAL, 
> `pm2_5` REAL, `pressure` REAL, 

[weewx-user] Re: SQLite schema report

[David Prellwitz]

Also, i'll try to just document the base and extended schema's to give a 
good base model. 
p.s., I'm using Visio as it's the tools i've used for years. If you have a 
suggestion for another tool, let me know and i'll see if i can 
load/install/use that tool. 

On Saturday, February 27, 2021 at 2:33:01 PM UTC-8 David Prellwitz wrote:

> Vince - I did all of that and the schema view is bare, i.e., it's still a 
> whole lot of nothing  other than the field names - and it's not complete 
> (or even close). I've run a Visio Data Model on Weewx.sdb (my running copy) 
> and found 114 separate tables; many matching field names. All with the same 
> PK and little - if any - SK/FK to differentiate what device/station 
> generated that instance of data. And, all without (relationship) links. All 
> without documentation or a word anywhere as to what some or most of the 
> tables are for and/or pertaining to. 
>
> So, rather than slogging through a morass of blogs, texts and various 
> thousands of pages to try to figure out what most of those tables are for, 
> i'm okay with adding notes and documentation to my Visio workspace and 
> publish that info as i complete each piece. I just need people to send me, 
> or provide links to, any specific documents describing these tables. 
> Better, if something exists that shows some/most of this info, please 
> provide it. 
>
> On Thursday, February 25, 2021 at 2:17:50 PM UTC-8 vince wrote:
>
>> echo ".schema" | sqlite3 mydatabasename.sdb
>>
>> or look at 
>> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py 
>> for the default schema for current v4 weewx.
>>
>> On Thursday, February 25, 2021 at 1:48:45 PM UTC-8 david.a@gmail.com 
>> wrote:
>>
>>> Looking through both SQLite and Weewx documentation, i can't find a 
>>> reference to a tool or report that will take a existing SQLdb and display 
>>> the underlying DB's structure? I can see that wee-debug will give a listing 
>>> of fields and key's, but there's no references to the relationships 
>>> established for the exiting db. I ask because i'd like to understand how 
>>> the existing data maintains keys. i.e., if data is stored with the only 
>>> primary key as epoch time, can weewx manage joined keys of epoch+Device-ID? 
>>> That would allow me to store multiple occurrences of epochDT, but different 
>>> devices. that would allow me to store data from devices as raw data and 
>>> data from WF (or other weather services) corrected data concurrently. It 
>>> would also solve the often-mentioned "What's raw data and what has WF 
>>> 'conditioned' data in my SQLdb?" issues.
>>> /David
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a4d7e4d2-60bb-48cc-9faa-ee8843699fbfn%40googlegroups.com.

[weewx-user] Re: SQLite schema report

[David Prellwitz]

Vince - I did all of that and the schema view is bare, i.e., it's still a 
whole lot of nothing  other than the field names - and it's not complete 
(or even close). I've run a Visio Data Model on Weewx.sdb (my running copy) 
and found 114 separate tables; many matching field names. All with the same 
PK and little - if any - SK/FK to differentiate what device/station 
generated that instance of data. And, all without (relationship) links. All 
without documentation or a word anywhere as to what some or most of the 
tables are for and/or pertaining to. 

So, rather than slogging through a morass of blogs, texts and various 
thousands of pages to try to figure out what most of those tables are for, 
i'm okay with adding notes and documentation to my Visio workspace and 
publish that info as i complete each piece. I just need people to send me, 
or provide links to, any specific documents describing these tables. 
Better, if something exists that shows some/most of this info, please 
provide it. 

On Thursday, February 25, 2021 at 2:17:50 PM UTC-8 vince wrote:

> echo ".schema" | sqlite3 mydatabasename.sdb
>
> or look at 
> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py 
> for the default schema for current v4 weewx.
>
> On Thursday, February 25, 2021 at 1:48:45 PM UTC-8 david.a@gmail.com 
> wrote:
>
>> Looking through both SQLite and Weewx documentation, i can't find a 
>> reference to a tool or report that will take a existing SQLdb and display 
>> the underlying DB's structure? I can see that wee-debug will give a listing 
>> of fields and key's, but there's no references to the relationships 
>> established for the exiting db. I ask because i'd like to understand how 
>> the existing data maintains keys. i.e., if data is stored with the only 
>> primary key as epoch time, can weewx manage joined keys of epoch+Device-ID? 
>> That would allow me to store multiple occurrences of epochDT, but different 
>> devices. that would allow me to store data from devices as raw data and 
>> data from WF (or other weather services) corrected data concurrently. It 
>> would also solve the often-mentioned "What's raw data and what has WF 
>> 'conditioned' data in my SQLdb?" issues.
>> /David
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8ae243bf-0fa0-4844-a582-38f40fefe522n%40googlegroups.com.

[weewx-user] SQLite schema report

[David Prellwitz]

Looking through both SQLite and Weewx documentation, i can't find a 
reference to a tool or report that will take a existing SQLdb and display 
the underlying DB's structure? I can see that wee-debug will give a listing 
of fields and key's, but there's no references to the relationships 
established for the exiting db. I ask because i'd like to understand how 
the existing data maintains keys. i.e., if data is stored with the only 
primary key as epoch time, can weewx manage joined keys of epoch+Device-ID? 
That would allow me to store multiple occurrences of epochDT, but different 
devices. that would allow me to store data from devices as raw data and 
data from WF (or other weather services) corrected data concurrently. It 
would also solve the often-mentioned "What's raw data and what has WF 
'conditioned' data in my SQLdb?" issues.
/David

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9640c4bd-5b2a-45eb-b0a1-50a16bc33248n%40googlegroups.com.

[weewx-user] Re: Importing Weatherflow data

[David Prellwitz]

sorry, my touchpad has caused early posting!
To continue, 
5. Edit the import file to include the field names.
6. run wee-import --test only
7. evaluate results, make corrections
8. run final import
9. restart weewx

any way to verify success?


On Monday, February 22, 2021 at 10:27:44 PM UTC-8 David Prellwitz wrote:

> I'm trying to import (wee_import) two weeks of data from my tempest 
> repository held at Weatherflow. The API page example of my data shows no 
> header in the csv file. How should i handle this import? should i edit the 
> file by adding the first reacord and inserting the proper field names?
> i assume the normal approach is to:
> 1. create the import config file.
> 2. extract the WeatherFlow data use their API.
> 3. stop weewx, 
> 4. copy current db as backup, 
> 5. edit 
> 6. 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cf1c3360-2673-47d0-8ba0-14de86edfd07n%40googlegroups.com.

[weewx-user] Importing Weatherflow data

[David Prellwitz]

I'm trying to import (wee_import) two weeks of data from my tempest 
repository held at Weatherflow. The API page example of my data shows no 
header in the csv file. How should i handle this import? should i edit the 
file by adding the first reacord and inserting the proper field names?
i assume the normal approach is to:
1. create the import config file.
2. extract the WeatherFlow data use their API.
3. stop weewx, 
4. copy current db as backup, 
5. edit 
6. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0b956915-bd15-45d3-806c-bb6c80ab1bfan%40googlegroups.com.