Re: [weewx-user] Weewx does not update website with new data.

[Rainer Lang]

What I would do first is assigning one of your WH31 sensors (also) to 
the outdoor T/H sensor

in weewx.conf
[StdCalibrate]
[[Corrections]] add the lines
outTemp = extraTemp1
outHumidity = extraHumid1
(as an example - you can take whichever of your WH31 you prefer, 
extraTemp1, 2, 3, 4 ...))
As a result, weewx will save these WH31 values also as 
outTemp/outHumidity, so you missing tempf issue might disappear.

Try that and see what it gives
On 17.11.2022 22:31, Bob Rose wrote:
After running weewx with a ecowitt gw1000 for about 2 years I decided 
to build a new server. The initial install of 4.9.1 and “simulator” 
test went well. I used the "Deb" install method. Ubuntu server. weewx 
updated the new website with simulated data. I went ahead and 
installed the GW1000 driver. Weewx is now not updating the website. 
The old simulator data remains.  It is collecting data and seems to be 
parsing the generated files in the “website”/ecowitt/ directory. Well 
at least they appear and disappear. I did uses the sqlite file from 
the old install. nothing else. Note this station does not have an 
outside temperature sensor. I am using 3 Wh31s sensors in places 
outdoors. I did set debug to 1 trying to gain info from the logs. I 
did note that "tempf" seems to trigger the fault. see second log output.

From one of the files in /ecowitt/
Array
(
    [PASSKEY] => “a bunch of hex stuff”
    [stationtype] => GW1000B_V1.7.5
    [runtime] => 1033890
    [dateutc] => 2022-11-17 20:51:06
    [tempinf] => 69.08
    [humidityin] => 38
    [baromrelin] => 30.127
    [baromabsin] => 27.569
    [winddir] => 65
    [windspeedmph] => 2.91
    [windgustmph] => 4.47
    [maxdailygust] => 17.22
    [solarradiation] => 56.27
    [uv] => 0
    [rainratein] => 0.000
    [eventrainin] => 0.000
    [hourlyrainin] => 0.000
    [dailyrainin] => 0.000
    [weeklyrainin] => 0.000
    [monthlyrainin] => 0.000
    [yearlyrainin] => 5.346
    [totalrainin] => 5.346
    [temp1f] => 71.06
    [humidity1] => 20
    [temp2f] => 69.80
    [humidity2] => 20
    [temp3f] => 74.30
    [humidity3] => 18
    [soilmoisture1] => 48
    [soilmoisture2] => 27
    [lightning_num] => 8
    [lightning] => 14
    [lightning_time] => 1668699860
    [wh68batt] => 1.62
    [batt1] => 0
    [batt2] => 0
    [batt3] => 0
    [soilbatt1] => 1.3
    [soilbatt2] => 1.3
    [wh57batt] => 3
    [freq] => 915M
    [model] => GW1000B_Pro
)


From systemlog. Note it is bottom to top. Newest at top. Just after a 
restart of weewx.


Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Skipping 
lightning count of 8: no last count
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: skipping 
rain measurement of 135.8: no last rain
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Using 
't_rainyear' for rain total
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Next 
update in 60 seconds
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Unknown 
field address '7B' detected. Remaining data '00' ignored.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Starting 
main packet loop.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Daily 
summaries up to date
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Starting 
backfill of daily summaries
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Using 
binding 'wx_binding' to database 'weewx.sdb'
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Station 
does not support reading the time
Nov 17 14:00:57 ubuntserver weewx[552308] INFO __main__: Starting up 
weewx version 4.9.1
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: 'pyephem' 
not detected, extended almanac data is not available
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.restx.StdAWEKAS
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: AWEKAS: 
Posting not enabled.
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.restx.StdAWEKAS
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.restx.StdWOW
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: WOW: 
Posting not enabled.
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.restx.StdWOW
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
loading service weewx.restx.StdCWOP
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: CWOP: 
Posting not enabled.
Nov 17 14:00:57 ubuntserver weewx[552308

Re: [weewx-user] Weewx does not update website with new data.

[Rainer Lang]

I'm only realizing now - after having read Gary's mail which came in 
late due to internet issues - that you seem to use two different 
drivers/services in parallel in one weewx instance, which is likely to 
be the cause for unpredictable behaviour.
You better choose only one of them - and by experience, I'd prefer the 
Ecowitt Gateway (GW1000) driver and remove this AddEcowittData thing
which probably was once written to cover for a those days not yet 
existing GW-GW driver.
Gary's EW-GW driver is very stable and covers all sensors of the these 
days Ecowitt (sensor) universe.

On 18.11.2022 10:11, Rainer Lang wrote:
What I would do first is assigning one of your WH31 sensors (also) to 
the outdoor T/H sensor

in weewx.conf
[StdCalibrate]
[[Corrections]] add the lines
outTemp = extraTemp1
outHumidity = extraHumid1
(as an example - you can take whichever of your WH31 you prefer, 
extraTemp1, 2, 3, 4 ...))
As a result, weewx will save these WH31 values also as 
outTemp/outHumidity, so you missing tempf issue might disappear.

Try that and see what it gives
On 17.11.2022 22:31, Bob Rose wrote:
After running weewx with a ecowitt gw1000 for about 2 years I decided 
to build a new server. The initial install of 4.9.1 and “simulator” 
test went well. I used the "Deb" install method. Ubuntu server. weewx 
updated the new website with simulated data. I went ahead and 
installed the GW1000 driver. Weewx is now not updating the website. 
The old simulator data remains.  It is collecting data and seems to 
be parsing the generated files in the “website”/ecowitt/ directory. 
Well at least they appear and disappear. I did uses the sqlite file 
from the old install. nothing else. Note this station does not have 
an outside temperature sensor. I am using 3 Wh31s sensors in places 
outdoors. I did set debug to 1 trying to gain info from the logs. I 
did note that "tempf" seems to trigger the fault. see second log output.

From one of the files in /ecowitt/
Array
(
    [PASSKEY] => “a bunch of hex stuff”
    [stationtype] => GW1000B_V1.7.5
    [runtime] => 1033890
    [dateutc] => 2022-11-17 20:51:06
    [tempinf] => 69.08
    [humidityin] => 38
    [baromrelin] => 30.127
    [baromabsin] => 27.569
    [winddir] => 65
    [windspeedmph] => 2.91
    [windgustmph] => 4.47
    [maxdailygust] => 17.22
    [solarradiation] => 56.27
    [uv] => 0
    [rainratein] => 0.000
    [eventrainin] => 0.000
    [hourlyrainin] => 0.000
    [dailyrainin] => 0.000
    [weeklyrainin] => 0.000
    [monthlyrainin] => 0.000
    [yearlyrainin] => 5.346
    [totalrainin] => 5.346
    [temp1f] => 71.06
    [humidity1] => 20
    [temp2f] => 69.80
    [humidity2] => 20
    [temp3f] => 74.30
    [humidity3] => 18
    [soilmoisture1] => 48
    [soilmoisture2] => 27
    [lightning_num] => 8
    [lightning] => 14
    [lightning_time] => 1668699860
    [wh68batt] => 1.62
    [batt1] => 0
    [batt2] => 0
    [batt3] => 0
    [soilbatt1] => 1.3
    [soilbatt2] => 1.3
    [wh57batt] => 3
    [freq] => 915M
    [model] => GW1000B_Pro
)


From systemlog. Note it is bottom to top. Newest at top. Just after a 
restart of weewx.


Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Skipping 
lightning count of 8: no last count
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: skipping 
rain measurement of 135.8: no last rain
Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Using 
't_rainyear' for rain total
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Next 
update in 60 seconds
Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Unknown 
field address '7B' detected. Remaining data '00' ignored.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Starting 
main packet loop.
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Daily 
summaries up to date
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: 
Starting backfill of daily summaries
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Using 
binding 'wx_binding' to database 'weewx.sdb'
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Station 
does not support reading the time
Nov 17 14:00:57 ubuntserver weewx[552308] INFO __main__: Starting up 
weewx version 4.9.1
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: 
Finished loading service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: 
'pyephem' not detected, extended almanac data is not available
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdReport
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: 
Finished loading service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Loading 
service weewx.engine.StdPrint
Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: 
Finished loading service weewx.restx.StdAWEKAS
Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.restx: AWEKAS: 
Posting not enabled.
Nov

Re: [weewx-user] Re: Neowx skin sample site

['Rory Gillies' via weewx-user]

Head over to this GitHub 
repository: https://github.com/seehase/neowx-material you'll find many of 
the enhancements there including the history page and the wind direction 
graph. Some of the additions are my own, such as the Windy forecast and 
satellite cards, I'll attach them here once I change the default 
index.html.tmpl (mine has many changes from the default which won't be 
applicable to most).

Best,

Rory

On Thursday, November 17, 2022 at 12:06:49 PM UTC Artvd wrote:

> @Rory
>  I also have installed Neowx materials skin but it does not work as good 
> as on your site. I have contacted the developper but he does not react. 
> Like Rainer i would be interest in getting the relevant files. This is my 
> site https://tinyurl.com/a12312223
>
> Op woensdag 16 november 2022 om 18:39:13 UTC+1 schreef kawa...@gmail.com:
>
>> Hallo ich schreibe einmal auf deutsch und dann die übersetzung ins 
>> Englische.
>> Ich habe nicht gewusst das man in der weewx.conf das so wie oben 
>> beschrieben rein schreiben muss.
>> Darum habe ich es so wie in meiner weewx.conf ausgeführt.
>> Mittlerweile funktioniert es auch mit neowx.
>> Ebenso bin ich kein Forum oder Gruppen Kenner darum habe ich keinen neuen 
>> Thread gemacht.
>> Ich entschuldige mich für die Umstände und danke für die Hilfe!
>>
>> Danke sehr Günther
>>
>>
>> Hello I write once on german and then the translation into English.
>> I didn't know that you have to write in the weewx.conf as described above.
>> That's why I ran it as in my weewx.conf.
>> Meanwhile, it also works with neowx.
>> Likewise, I'm not a forum or group connoisseur so I didn't make a new 
>> thread.
>> I apologize for the inconvenience and thank you for the help!
>>
>> Thank you very much Günther
>> lang@googlemail.com schrieb am Montag, 14. November 2022 um 22:45:54 
>> UTC+1:
>>
>>> I don't know why you couldn't change or add the neowx-material skin to 
>>> your weewx installation.
>>> Probably because you didn't install the skin - or at least didn't modify 
>>> weewx.conf accordingly.
>>> That's what your weewx.conf is saying - there is no proper entry for the 
>>> neowx-material skin in the [StdReport] stanza.
>>>
>>> What you have obviously done is to mix up skins - made a neowx-material 
>>> entry inside the [[Seasons]] stanza - which won't work.
>>> What you are trying to do is to convert a Mercedes car into a BMW car by 
>>> changing the name on the car tail.
>>>
>>> What you need to have are the following entries in weewx.conf:
>>>
>>>  -- start excerpt weewx.conf [StdReport] stanza 
>>> --
>>>
>>> [[neowx]]
>>> skin = neowx-material
>>> enable = true
>>> HTML_ROOT = /var/www/html/weewx/neowx
>>>
>>> [[SeasonsReport]]
>>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>>> # images, templates and plots for the report.
>>> skin = Seasons
>>> enable = true
>>>
>>>  -- end excerpt weewx.conf [StdReport] stanza --
>>>
>>> Then you can have the seasons skin with 
>>> http://IP-address/weewx
>>> and the neowx-material skin with
>>> http://IP-address/weewx/neowx
>>>
>>>
>>> On 14.11.2022 22:28, Günther Wrana wrote:
>>>
>>> Hi 
>>>
>>> I have the .conf and a little bit from the syslog file send.
>>>
>>> Why could i not my skin canch to neowx?
>>>
>>> Thank you for all your help
>>>
>>> Günther Wrana schrieb am Donnerstag, 12. März 2020 um 07:40:18 UTC+1:
>>>

  Hello this is my page http://guentherwrana.ddns.net/weewx/ but for me 
 no values ​​are shown on the curves.
 I would also be interested in how I change the language.
 Could you give me a tip?
 On the weewx.com site I have not yet figured out how to change the 
 language of the skins.
 Thanks Günther


 Am Mittwoch, 30. Januar 2019 13:39:34 UTC+1 schrieb Alan Jackson: 
>
> I just installed it. http://www.ajackson.org/weewx

 -- 
>>> 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/91db6e74-6d3c-4f1a-989a-dd21517ea972n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>>

-- 
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/58e3ab82-a6da-4370-909b-a79128062e6fn%40googlegroups.com.

Re: [weewx-user] Neowx skin sample site [3]

['Rory Gillies' via weewx-user]

See my reply to Artvd, you can get the history page there. I'll also attach 
the ephemeris template. I have never tried two data sources with this skin, 
however if it works in Seasons it should work with Neowx.

Best,

Rory

On Tuesday, November 15, 2022 at 6:21:27 PM UTC lang@googlemail.com 
wrote:

> Hi Rory,
>
> looks nice and interesting, especially the ephemeris part and the records 
> (for me). Great work.
> Any chance to get the respective skin.conf, index.html.tmpl and related 
> .inc files - and/or (if needed) related entries in extensions.py ?
> In order to see how you managed to set this up.
> By the way - did you manage to integrate readings from a 2nd database 
> (different binding) into a combined chart, e.g. rainfall reading from 
> different consoles (and databases)
> with the approach used in the neowx-material index.html.tmpl ?
> While I managed to do this in the Seasons skin, I was never successful 
> with neowx-material.
>
> cheers
>
> Rainer
> On 15.11.2022 12:51, 'Rory Gillies' via weewx-user wrote:
>
>
> I've been using it for a while now, there's a few of us working on 
> enhancements, some of them you can see on my site: 
>
> https//www.360shetland.co.uk/weather
>
> On Monday, November 14, 2022 at 9:52:45 PM UTC lang@googlemail.com 
> wrote:
>
>> Vielleicht ist Englisch zu kompliziert - also, man kann eine neue Skin 
>> nicht dadurch einführen, indem man den Namen einer bestehenden ändert.
>> Was Du gemacht hast ist wie der Versuch, einen Mercedes zu einem BMW zu 
>> machen, indem Du den Namen Mercedes am Heck durch BMW ersetzt - geht 
>> natürlich so nicht.
>> Jede Skin braucht ihren eigenen Eintrag in der [StdReport] Stanza von 
>> weewx.conf, eine eigene [[skin]] Stanza
>> Das funktionierende Beispiel ist unten angeführt.
>> On 14.11.2022 22:45, Rainer Lang wrote:
>>
>> I don't know why you couldn't change or add the neowx-material skin to 
>> your weewx installation.
>> Probably because you didn't install the skin - or at least didn't modify 
>> weewx.conf accordingly.
>> That's what your weewx.conf is saying - there is no proper entry for the 
>> neowx-material skin in the [StdReport] stanza.
>>
>> What you have obviously done is to mix up skins - made a neowx-material 
>> entry inside the [[Seasons]] stanza - which won't work.
>> What you are trying to do is to convert a Mercedes car into a BMW car by 
>> changing the name on the car tail.
>>
>> What you need to have are the following entries in weewx.conf:
>>
>>  -- start excerpt weewx.conf [StdReport] stanza --
>>
>> [[neowx]]
>> skin = neowx-material
>> enable = true
>> HTML_ROOT = /var/www/html/weewx/neowx
>>
>> [[SeasonsReport]]
>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>> # images, templates and plots for the report.
>> skin = Seasons
>> enable = true
>>
>>  -- end excerpt weewx.conf [StdReport] stanza --
>>
>> Then you can have the seasons skin with 
>> http://IP-address/weewx
>> and the neowx-material skin with
>> http://IP-address/weewx/neowx
>>
>>
>> On 14.11.2022 22:28, Günther Wrana wrote:
>>
>> Hi 
>>
>> I have the .conf and a little bit from the syslog file send.
>>
>> Why could i not my skin canch to neowx?
>>
>> Thank you for all your help
>>
>> Günther Wrana schrieb am Donnerstag, 12. März 2020 um 07:40:18 UTC+1:
>>
>>>
>>>  Hello this is my page http://guentherwrana.ddns.net/weewx/ but for me 
>>> no values ​​are shown on the curves.
>>> I would also be interested in how I change the language.
>>> Could you give me a tip?
>>> On the weewx.com site I have not yet figured out how to change the 
>>> language of the skins.
>>> Thanks Günther
>>>
>>>
>>> Am Mittwoch, 30. Januar 2019 13:39:34 UTC+1 schrieb Alan Jackson: 

 I just installed it. http://www.ajackson.org/weewx
>>>
>>> -- 
>> 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/91db6e74-6d3c-4f1a-989a-dd21517ea972n%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
> 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/226a15f1-4801-495e-a8b6-03b2455ebbedn%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because y

Re: [weewx-user] Neowx skin sample site [3]

[Rainer Lang]

Hi Rory,
"should" is the theory - that I also thought from the beginning. And it 
works with the tiles. But unfortunately the syntax which works with 
Seasons doesn't work with neowx charts ...

All kind of "tricks" tried - at no avail.
cheers
Rainer
On 18.11.2022 11:10, 'Rory Gillies' via weewx-user wrote:
See my reply to Artvd, you can get the history page there. I'll also 
attach the ephemeris template. I have never tried two data sources 
with this skin, however if it works in Seasons it should work with Neowx.


Best,

Rory

On Tuesday, November 15, 2022 at 6:21:27 PM UTC 
lang@googlemail.com wrote:


Hi Rory,

looks nice and interesting, especially the ephemeris part and the
records (for me). Great work.
Any chance to get the respective skin.conf, index.html.tmpl and
related .inc files - and/or (if needed) related entries in
extensions.py ?
In order to see how you managed to set this up.
By the way - did you manage to integrate readings from a 2nd
database (different binding) into a combined chart, e.g. rainfall
reading from different consoles (and databases)
with the approach used in the neowx-material index.html.tmpl ?
While I managed to do this in the Seasons skin, I was never
successful with neowx-material.

cheers

Rainer

On 15.11.2022 12:51, 'Rory Gillies' via weewx-user wrote:


I've been using it for a while now, there's a few of us working
on enhancements, some of them you can see on my site:

https//www.360shetland.co.uk/weather


On Monday, November 14, 2022 at 9:52:45 PM UTC
lang@googlemail.com wrote:

Vielleicht ist Englisch zu kompliziert - also, man kann eine
neue Skin nicht dadurch einführen, indem man den Namen einer
bestehenden ändert.
Was Du gemacht hast ist wie der Versuch, einen Mercedes zu
einem BMW zu machen, indem Du den Namen Mercedes am Heck
durch BMW ersetzt - geht natürlich so nicht.
Jede Skin braucht ihren eigenen Eintrag in der [StdReport]
Stanza von weewx.conf, eine eigene [[skin]] Stanza
Das funktionierende Beispiel ist unten angeführt.

On 14.11.2022 22:45, Rainer Lang wrote:


I don't know why you couldn't change or add the
neowx-material skin to your weewx installation.
Probably because you didn't install the skin - or at least
didn't modify weewx.conf accordingly.
That's what your weewx.conf is saying - there is no proper
entry for the neowx-material skin in the [StdReport] stanza.

What you have obviously done is to mix up skins - made a
neowx-material entry inside the [[Seasons]] stanza - which
won't work.
What you are trying to do is to convert a Mercedes car into
a BMW car by changing the name on the car tail.

What you need to have are the following entries in weewx.conf:

 -- start excerpt weewx.conf [StdReport] stanza
--

    [[neowx]]
    skin = neowx-material
    enable = true
    HTML_ROOT = /var/www/html/weewx/neowx

    [[SeasonsReport]]
    # The SeasonsReport uses the 'Seasons' skin, which
contains the
    # images, templates and plots for the report.
    skin = Seasons
    enable = true

 -- end excerpt weewx.conf [StdReport] stanza
--

Then you can have the seasons skin with
http://IP-address/weewx 
and the neowx-material skin with
http://IP-address/weewx/neowx 


On 14.11.2022 22:28, Günther Wrana wrote:

Hi

I have the .conf and a little bit from the syslog file send.

Why could i not my skin canch to neowx?

Thank you for all your help

Günther Wrana schrieb am Donnerstag, 12. März 2020 um
07:40:18 UTC+1:


 Hello this is my page
http://guentherwrana.ddns.net/weewx/ but for me no
values ​​are shown on the curves.
I would also be interested in how I change the language.
Could you give me a tip?
On the weewx.com  site I have not yet
figured out how to change the language of the skins.
Thanks Günther


Am Mittwoch, 30. Januar 2019 13:39:34 UTC+1 schrieb
Alan Jackson:

I just installed it. http://www.ajackson.org/weewx

-- 
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-u

[weewx-user] Problems with rtl driver. Don't kill rtl_433

[enu...@gmail.com]

I have been having random problems with the sdr driver for a long time.
The log shows this:
Nov 18 11:02:51 raspberrypi python3[738]: weewx[738] INFO weewx.engine: 
Starting main packet loop.
Nov 18 11:02:54 raspberrypi python3[738]: weewx[738] INFO weewx.engine: 
Main loop exiting. Shutting engine down.
Nov 18 11:02:54 raspberrypi python3[738]: weewx[738] INFO user.sdr: 
shutdown process rtl_433 -q -F json -R 32 -M utc -M level -f 868.3M -Y 
classic
Nov 18 11:02:54 raspberrypi python3[738]: weewx[738] CRITICAL __main__: 
Caught WeeWxIOError: rtl_433 process is not running
Nov 18 11:02:54 raspberrypi python3[738]: weewx[738] CRITICAL __main__: 
 Waiting 60 seconds then retrying...
Nov 18 11:03:57 raspberrypi python3[738]: weewx[738] ERROR user.sdr: err: 
[b'rtl_433 version unknown inputs file rtl_tcp RTL-SDR SoapySDR\n', b'Use 
-h for usage help and see https://triq.org/ for documentation.\n', b'Trying 
conf file at "rtl_433.co>
Nov 18 11:03:57 raspberrypi python3[738]: weewx[738] INFO weewx.engine: 
Main loop exiting. Shutting engine down.
Nov 18 11:03:57 raspberrypi python3[738]: weewx[738] INFO user.sdr: 
shutdown process rtl_433 -q -F json -R 32 -M utc -M level -f 868.3M -Y 
classic
Nov 18 11:03:58 raspberrypi python3[738]: weewx[738] CRITICAL __main__: 
Caught WeeWxIOError: rtl_433 process is not running
Nov 18 11:03:58 raspberrypi python3[738]: weewx[738] CRITICAL __main__: 
 Waiting 60 seconds then retrying...
Nov 18 11:04:58 raspberrypi python3[738]: weewx[738] INFO __main__: 
retrying...

The problem is that the sdr driver fails to kill the rtl_433 process and 
when it tries to start it again it finds that the resource is busy and it 
keeps failing until I stop weewx, kill the process and start weewx 
again. If I just do restart it doesn't fix the problem for the same reason 
rtil_433 is running and weewx can't kill the process.
I don't know the reason but it happens often, it can take less than 1 day 
or take a month.

-- 
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/60deeec0-17cd-43ef-b15d-ce9cd2104123n%40googlegroups.com.

[weewx-user] Acurite Atlas (w/Access) - Acuparse works, Inteceptor doesn't

[ezekield]

Maybe worth mentioning I've been using weewx on Linux with Acurite 01036 
for ~7years. This is a newer, more recent setup...

Acurite Atlas with an Access bridge: It's been sending data to 
myacurite.com (and wunderground) for some time now. However repeated 
attempts to get it working with weewx RTL/SDR, and more recently, 
Interceptor, have failed. 

I just completed a successful experiment with Acuparse. My setup was 
entirely defaults. I only: 1) changed Server Name on the Acurite Access 
device https://imgur.com/a/7hptaIr 2) provided Acuparse with the Access 
MAC/Device ID 3) provided Acuparse with Station ID / Sensor ID. 

I would prefer to use weewx with the Atlas. I've read 
through https://github.com/matthewwall/weewx-interceptor as well as a few 
posts via search however numerous attempts have been unsuccessful. Here the 
Access is hostname atlas.foobar.com (.98) and weewx (.99) is running on 
acuparse.foobar.com There is no firewall between them, full open access. 
Yes, acuparse is disabled for these tests. 

What I see when running weewx and tcpdump (atlas.foobar.com  = 
192.168.1.98). This tcpdump is done on weewx host acuparse.foobar.com 
(192.168.1.99). 

# tcpdump -i eth1 src 192.168.1.98

11:18:17.846452 IP atlas.foobar.com.5678 > acuparse.foobar.com.https: Flags 
[S], seq 3747456072, win 8192, options [mss 1460], length 0
11:18:17.846480 IP acuparse.foobar.com.https > atlas.foobar.com.5678: Flags 
[R.], seq 217488705, ack 2355357015, win 0, length 0
11:18:17.902067 IP atlas.foobar.com.5678 > acuparse.foobar.com.https: Flags 
[S], seq 3748847508, win 8192, options [mss 1460], length 0
11:18:17.902097 IP acuparse.foobar.com.https > atlas.foobar.com.5678: Flags 
[R.], seq 217488705, ack 2356748451, win 0, length 0
11:18:17.957792 IP atlas.foobar.com.5678 > acuparse.foobar.com.https: Flags 
[S], seq 3750240717, win 8192, options [mss 1460], length 0
11:18:17.957818 IP acuparse.foobar.com.https > atlas.foobar.com.5678: Flags 
[R.], seq 217488705, ack 2358141660, win 0, length 0

Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.manager: Starting backfill 
of daily summaries
Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.manager: Daily summaries 
up to date
Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.engine: Starting main 
packet loop.
Nov 18 11:17:13 acuparse weewx[68764] DEBUG user.interceptor: empty queue

This tells me data is being sent from Access to weewx via port 443 but 
weewx isn't seeing it (IS THAT CORRECT?). weewx config is all defaults and 
interceptor is simply:

[Interceptor]
driver = user.interceptor
device_type = acurite-bridge

Also, this provides no output with port as 80 or 443:

PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
--device=acurite-bridge --mode=listen --port=80 --debug

Why does Interceptor doc not mention anything about 443/ssl/tls? Given the 
ease and success of Acuparse I was expecting to find an easier path to move 
this to weewx. 

Can you please let me know what is correct/incorrect about this setup and 
any good/bad assumptions I've made? I'd be happy to provide additional 
details! 


-- 
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/14019777-9e46-4711-91cf-7b4340a0baa2n%40googlegroups.com.

Re: [weewx-user] Accumulator configuration and WeeWX crash

[Tom Keffer]

The problem is that FirstLast values are not designed to be stored in the
daily summaries (although there's no reason they couldn't be).

Try removing upsEstimatedChargeRemaining, upsSecondsOnBattery,
and upsEstimatedMinutesRemaining from the daily summary schema.

On Thu, Nov 17, 2022 at 11:15 AM Karen K  wrote:

> I added accumulator definitions in weewx.conf:
>
> [Accumulator]
> ...
> [[upsEstimatedChargeRemaining]]
> accumulator = firstlast
> extractor = last
> [[upsSecondsOnBattery]]
> accumulator = firstlast
> extractor = last
> [[upsEstimatedMinutesRemaining]]
> accumulator = firstlast
> extractor = last
>
> WeeWx crashes then with the error messages shown below.
>
> If I then remove the line accumulator = firstlast, no error occurs any
> more. So that configuration works fine:
> [Accumulator]
> ...
> [[upsEstimatedChargeRemaining]]
> extractor = last
> [[upsSecondsOnBattery]]
> extractor = last
> [[upsEstimatedMinutesRemaining]]
> extractor = last
>
> Error messages for the configuration including the line accumulator =
> firstlast:
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: Caught
> unrecoverable exception:
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__:   too
> many values to unpack (expected 4)
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> Traceback (most recent call last):
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 214, in run
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> callback(event)
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 634, in check_loop
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> raise BreakLoop
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> weewx.engine.BreakLoop
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__:   During
> handling of the above exception, another exception occurred:
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> Traceback (most recent call last):
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 650, in post_loop
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> self._catchup(self.engine.console.genArchiveRecords)
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 697, in _catchup
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> for record in generator(lastgood_ts):
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/drivers/__init__.py", line 30, in genArchiveRecords
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> raise NotImplementedError("Method 'genArchiveRecords' not implemented")
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> NotImplementedError: Method 'genArchiveRecords' not implemented
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__:   During
> handling of the above exception, another exception occurred:
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> Traceback (most recent call last):
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewxd", line 154, in main
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> engine.run()
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 221, in run
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> callback(event)
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 652, in post_loop
>
> Nov 17 19:30:17 LokalWiki weewx[85284] CRITICAL __main__: 
> self._software_catchup()
>
> Nov 17 1

[weewx-user] Cumulus Import Fail

[FIA Ranch]

Did not see any recent Cumulus import issues.  Don't know how that is.

This failure looks beyond my scope of knowledge.

Following are the pertinent pieces and parts (I think) other than printing 
lines out of the reported python files.

*Installed = WeeWX Version 4.9.1*

*This is an actual Cumulus data file line record (wrapped only here)*
27/06/13,07:20,71.7,24,33.0,0.0,3.0,338,0.00,0.00,29.714,2.13,85.5,14,0.0,71.7,71.7,0.7,248,0.000,22.308,68.3,225,0.1,339,0.00


*Definitions From Cumulus Report (Spaced For Clarity)*
[image: Screenshot 2022-11-18 14:36:34.png]

*Cumulus.conf file entries*
source = Cumulus
[Cumulus]
directory = /home/fiaranch/Files/cumulus_data
interval = x#There are likely missing records
qc = True#Assume invalid/extreme records
calc_missing = True#Not sure about this one.
separator = '/'
delimiter = ','
decimal = '.'
ignore_invalid_data = True
tranche = 250
UV_sensor = True
solar_sensor = True
[[Units]]
temperature = degree_F
pressure = mbar
rain = inch
speed = mile_per_hour


*Dry Run Request*
root@weather:~# wee_import 
--import-config=/home/fiaranch/Files/cumulus.conf --dry-run --verbose

*Result*
Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
Cumulus monthly log files in the '/home/fiaranch/Files/cumulus_data' 
directory will be imported
The following options will be used:
 config=/etc/weewx/weewx.conf, 
import-config=/home/fiaranch/Files/cumulus.conf
 from=None, to=None
 dry-run=True, calc_missing=True, ignore_invalid_data=True
 tranche=250, interval=x
 UV=True, radiation=True
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
This is a dry run, imported data will not be saved to archive.
Starting dry run import ...
Records covering multiple periods have been identified for import.
Period 1 ...
Obtaining raw import data for period 1 ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_import", line 899, in 
main()
  File "/usr/share/weewx/wee_import", line 829, in main
source_obj.run()
  File "/usr/share/weewx/weeimport/weeimport.py", line 382, in run
_raw_data = self.getRawData(period)
  File "/usr/share/weewx/weeimport/cumulusimport.py", line 346, in 
getRawData
_line = clean_row.replace(self.decimal, '.')
AttributeError: 'CumulusSource' object has no attribute 'decimal'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in 
apport_excepthook
with os.fdopen(os.open(pr_filename,
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_share_weewx_wee_import.0.crash'

Original exception was:
Traceback (most recent call last):
  File "/usr/share/weewx/wee_import", line 899, in 
main()
  File "/usr/share/weewx/wee_import", line 829, in main
source_obj.run()
  File "/usr/share/weewx/weeimport/weeimport.py", line 382, in run
_raw_data = self.getRawData(period)
  File "/usr/share/weewx/weeimport/cumulusimport.py", line 346, in 
getRawData
_line = clean_row.replace(self.decimal, '.')
AttributeError: 'CumulusSource' object has no attribute 'decimal'

Thanks in advance!

-- 
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/247e9cdd-31cf-48dc-8fbf-728646d76a5an%40googlegroups.com.

Re: [weewx-user] Weewx 4.9.1 usb.core.USBError: [Errno 32] Pipe error

[michael.k...@gmx.at]

I've upgraded to 4.9.1 and cannot reproduce the issue. Since I know 
Claudio178 personally, I know we have a very similar setup and we are 
running weewx with ws28xx on a raspberrypi4. However, his station is a 
newer revision. We'll check it out the next few days.

tke...@gmail.com schrieb am Dienstag, 1. November 2022 um 11:33:09 UTC+1:

> The ws28xx driver has been unchanged since v4.6.0 and even that change had 
> nothing to do with its functionality. 
>
> Is it possible that the version of pyusb changed? Or, a different usb 
> kernel module is being loaded? 
>
> Try power cycling, then set debug=1, then restart weewxd. Post the log 
> from restart through the first report cycle.
>
> On Tue, Nov 1, 2022 at 12:48 AM Claudio178  wrote:
>
>> Hi,
>> I just upgraded from Version 4.8.0 to 4.9.1 and can not run weewx anymore 
>> because I am getting following error code:
>>
>> weewx[20874] ERROR weewx.drivers.ws28xx:   File 
>> "/usr/lib/python3/dist-packages/usb/legacy.py", line 211, in controlMsg
>> weewx[20874] ERROR weewx.drivers.ws28xx: timeout = timeout)
>> weewx[20874] ERROR weewx.drivers.ws28xx:   File 
>> "/usr/lib/python3/dist-packages/usb/core.py", line 1043, in ctrl_transfer
>> weewx[20874] ERROR weewx.drivers.ws28xx: self.__get_timeout(timeout))
>> weewx[20874] ERROR weewx.drivers.ws28xx:   File 
>> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 883, in 
>> ctrl_transfer
>> weewx[20874] ERROR weewx.drivers.ws28xx: timeout))
>> weewx[20874] ERROR weewx.drivers.ws28xx:   File 
>> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in _check
>> weewx[20874] ERROR weewx.drivers.ws28xx: raise 
>> USBError(_strerror(ret), ret, _libusb_errno[ret])
>> weewx[20874] ERROR weewx.drivers.ws28xx: usb.core.USBError: [Errno 32] 
>> Pipe error
>> weewx[20874] INFO weewx.drivers.ws28xx: Scanned 23 records: current=593 
>> latest=651 remaining=58
>>
>> does anyone else facing this error or know a solution for that?
>>
>> Thx ;)
>>
>> -- 
>> 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/16683d1f-56a5-4883-97c3-8063b6ab1a53n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/6d5f22e4-3533-475c-83d1-069b277d1ed6n%40googlegroups.com.

[weewx-user] adding extra values from external sensors to weewx

[George Michalopoulos]

hello all, 

i get some extra values via mqtt, but there are not displayed under 
"Current Conditions" column.
Take a look here:
https://metron6.gr/weather/weewx/

there are also the values for GirlsRoom (temp+hum) but they are not 
displayed..

on the other hand, it is graphing extratemp1+extratemp2+extratemp3, but i 
want to add intemp also (its the livingroom values)..

can anyone help me ?

-- 
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/2e85391a-cc52-485d-8c52-e0406afcaafcn%40googlegroups.com.

Re: [weewx-user] Weewx does not update website with new data.

[Bob Rose]

Thanks Lang. I have it all working except the battery stuff. Not sure if 
that is important to me. I do have all the other data points being 
displayed. This really functions well.


On Friday, November 18, 2022 at 2:51:44 AM UTC-7 lang@googlemail.com 
wrote:

> I'm only realizing now - after having read Gary's mail which came in late 
> due to internet issues - that you seem to use two different 
> drivers/services in parallel in one weewx instance, which is likely to be 
> the cause for unpredictable behaviour.
> You better choose only one of them - and by experience, I'd prefer the 
> Ecowitt Gateway (GW1000) driver and remove this AddEcowittData thing
> which probably was once written to cover for a those days not yet existing 
> GW-GW driver.
> Gary's EW-GW driver is very stable and covers all sensors of the these 
> days Ecowitt (sensor) universe.
> On 18.11.2022 10:11, Rainer Lang wrote:
>
> What I would do first is assigning one of your WH31 sensors (also) to the 
> outdoor T/H sensor
> in weewx.conf
> [StdCalibrate] 
> [[Corrections]] add the lines 
> outTemp = extraTemp1 
> outHumidity = extraHumid1
> (as an example - you can take whichever of your WH31 you prefer, 
> extraTemp1, 2, 3, 4 ...))
> As a result, weewx will save these WH31 values also as 
> outTemp/outHumidity, so you missing tempf issue might disappear.
> Try that and see what it gives
> On 17.11.2022 22:31, Bob Rose wrote:
>
> After running weewx with a ecowitt gw1000 for about 2 years I decided to 
> build a new server. The initial install of 4.9.1 and “simulator” test went 
> well. I used the "Deb" install method. Ubuntu server. weewx updated the new 
> website with simulated data. I went ahead and installed the GW1000 driver. 
> Weewx is now not updating the website. The old simulator data remains.  It 
> is collecting data and seems to be parsing the generated files in the 
> “website”/ecowitt/ directory. Well at least they appear and disappear. I 
> did uses the sqlite file from the old install. nothing else. Note this 
> station does not have an outside temperature sensor. I am using 3 Wh31s 
> sensors in places outdoors. I did set debug to 1 trying to gain info from 
> the logs. I did note that "tempf" seems to trigger the fault. see second 
> log output.
> From one of the files in /ecowitt/
> Array
> (
> [PASSKEY] => “a bunch of hex stuff”
> [stationtype] => GW1000B_V1.7.5
> [runtime] => 1033890
> [dateutc] => 2022-11-17 20:51:06
> [tempinf] => 69.08
> [humidityin] => 38
> [baromrelin] => 30.127
> [baromabsin] => 27.569
> [winddir] => 65
> [windspeedmph] => 2.91
> [windgustmph] => 4.47
> [maxdailygust] => 17.22
> [solarradiation] => 56.27
> [uv] => 0
> [rainratein] => 0.000
> [eventrainin] => 0.000
> [hourlyrainin] => 0.000
> [dailyrainin] => 0.000
> [weeklyrainin] => 0.000
> [monthlyrainin] => 0.000
> [yearlyrainin] => 5.346
> [totalrainin] => 5.346
> [temp1f] => 71.06
> [humidity1] => 20
> [temp2f] => 69.80
> [humidity2] => 20
> [temp3f] => 74.30
> [humidity3] => 18
> [soilmoisture1] => 48
> [soilmoisture2] => 27
> [lightning_num] => 8
> [lightning] => 14
> [lightning_time] => 1668699860
> [wh68batt] => 1.62
> [batt1] => 0
> [batt2] => 0
> [batt3] => 0
> [soilbatt1] => 1.3
> [soilbatt2] => 1.3
> [wh57batt] => 3
> [freq] => 915M
> [model] => GW1000B_Pro
> )
>
>
> From systemlog. Note it is bottom to top. Newest at top. Just after a 
> restart of weewx.
>
> Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Skipping 
> lightning count of 8: no last count
> Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: skipping rain 
> measurement of 135.8: no last rain
> Nov 17 14:00:58 ubuntserver weewx[552308] INFO user.gw1000: Using 
> 't_rainyear' for rain total
> Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Next update 
> in 60 seconds
> Nov 17 14:00:58 ubuntserver weewx[552308] DEBUG user.gw1000: Unknown field 
> address '7B' detected. Remaining data '00' ignored.
> Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Starting main 
> packet loop.
> Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Daily 
> summaries up to date
> Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.manager: Starting 
> backfill of daily summaries
> Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Station does 
> not support reading the time
> Nov 17 14:00:57 ubuntserver weewx[552308] INFO __main__: Starting up weewx 
> version 4.9.1
> Nov 17 14:00:57 ubuntserver weewx[552308] DEBUG weewx.engine: Finished 
> loading service weewx.engine.StdReport
> Nov 17 14:00:57 ubuntserver weewx[552308] INFO weewx.engine: 'pyephem' not 
> detected, extended almanac data is not available
> Nov 17 14:00:57 ubuntser

[weewx-user] Re: Cumulus Import Fail

[gjr80]

Looks like there were a couple of typos when I added support for decimal 
points other than a period to the Cumulus and WD import classes. I believe 
I have fixed it, though am unable to test due to being away from home. You 
can try the fix by downloading and installing the updated file as follows:

1. move aside your existing /usr/share/weewx/weeimport/cumulusimport.py by 
renaming it, eg rename to cumulusimport_orig.py
2. download the updated file and save in place of the old cumulusimport.py:
$ wget -P 
/usr/share/weewx/weeimport 
https://raw.githubusercontent.com/weewx/weewx/master/bin/weeimport/cumulusimport.py

Try the import again, the 'decimal' attribute issue should be fixed.

Not applicable to you (unless you also wish to import from WD) but the WD 
import in v4.9.1 will also suffer from the same error. It was fixed in the 
same commit.

Gary

On Saturday, 19 November 2022 at 07:45:23 UTC+10 FIA Ranch wrote:

> Did not see any recent Cumulus import issues.  Don't know how that is.
>
> This failure looks beyond my scope of knowledge.
>
> Following are the pertinent pieces and parts (I think) other than printing 
> lines out of the reported python files.
>
> *Installed = WeeWX Version 4.9.1*
>
> *This is an actual Cumulus data file line record (wrapped only here)*
>
> 27/06/13,07:20,71.7,24,33.0,0.0,3.0,338,0.00,0.00,29.714,2.13,85.5,14,0.0,71.7,71.7,0.7,248,0.000,22.308,68.3,225,0.1,339,0.00
>
>
> *Definitions From Cumulus Report (Spaced For Clarity)*
> [image: Screenshot 2022-11-18 14:36:34.png]
>
> *Cumulus.conf file entries*
> source = Cumulus
> [Cumulus]
> directory = /home/fiaranch/Files/cumulus_data
> interval = x#There are likely missing records
> qc = True#Assume invalid/extreme records
> calc_missing = True#Not sure about this one.
> separator = '/'
> delimiter = ','
> decimal = '.'
> ignore_invalid_data = True
> tranche = 250
> UV_sensor = True
> solar_sensor = True
> [[Units]]
> temperature = degree_F
> pressure = mbar
> rain = inch
> speed = mile_per_hour
>
>
> *Dry Run Request*
> root@weather:~# wee_import 
> --import-config=/home/fiaranch/Files/cumulus.conf --dry-run --verbose
>
> *Result*
> Using WeeWX configuration file /etc/weewx/weewx.conf
> Starting wee_import...
> Cumulus monthly log files in the '/home/fiaranch/Files/cumulus_data' 
> directory will be imported
> The following options will be used:
>  config=/etc/weewx/weewx.conf, 
> import-config=/home/fiaranch/Files/cumulus.conf
>  from=None, to=None
>  dry-run=True, calc_missing=True, ignore_invalid_data=True
>  tranche=250, interval=x
>  UV=True, radiation=True
> Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Missing derived observations will be calculated.
> This is a dry run, imported data will not be saved to archive.
> Starting dry run import ...
> Records covering multiple periods have been identified for import.
> Period 1 ...
> Obtaining raw import data for period 1 ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_import", line 899, in 
> main()
>   File "/usr/share/weewx/wee_import", line 829, in main
> source_obj.run()
>   File "/usr/share/weewx/weeimport/weeimport.py", line 382, in run
> _raw_data = self.getRawData(period)
>   File "/usr/share/weewx/weeimport/cumulusimport.py", line 346, in 
> getRawData
> _line = clean_row.replace(self.decimal, '.')
> AttributeError: 'CumulusSource' object has no attribute 'decimal'
> Error in sys.excepthook:
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, 
> in apport_excepthook
> with os.fdopen(os.open(pr_filename,
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/var/crash/_usr_share_weewx_wee_import.0.crash'
>
> Original exception was:
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_import", line 899, in 
> main()
>   File "/usr/share/weewx/wee_import", line 829, in main
> source_obj.run()
>   File "/usr/share/weewx/weeimport/weeimport.py", line 382, in run
> _raw_data = self.getRawData(period)
>   File "/usr/share/weewx/weeimport/cumulusimport.py", line 346, in 
> getRawData
> _line = clean_row.replace(self.decimal, '.')
> AttributeError: 'CumulusSource' object has no attribute 'decimal'
>
> Thanks in advance!
>
>

-- 
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/e40f12f5-5dab-49d9-9abe-f4b4767bf3d5n%40googlegroups.com.