Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

['Rainer Lang' via weewx-user]

@vince
for his GW2000 yes, but for his W830 no - the W830 doesn't have the 
local Ecowitt API - there only the interceptor works (and quite well)


On 18.03.2024 21:59, vince wrote:
FWIW the gw1000 driver is 'much' easier to get going especially if 
you're new to the pi.  Works great.


On Monday, March 18, 2024 at 1:12:19 PM UTC-7 Pi Radio wrote:

Interceptor... I saw that earlier?

Going forwards I'll stop running and walk slowly through this.
Thank you.

By the way the Clock on my VHS VCR is still Flashing... I must
read the Instruction Manual one day. (If you are not of a certain
age, you are not going to get that joke).

But in all seriousness, I am struggling a bit finding my way
around all of this jargon, so I thought that before getting too
much further lost, I thought I'd wave and ask for guidance.

I've learnt a great deal so far on this massive learning curve,
but obviously I am not up to this ...yet.

Bear with me whilst I uninstall it all again, and start a fresh again.

Many thanks for the Links, I'm off to do some more reading.

On Mon, Mar 18, 2024 at 7:55 PM 'Rainer Lang' via weewx-user
 wrote:

The Ventus W830 is a Ecowitt WH2910 clone. In your mail it is
not clear what "it" means. Your RaspberryPi, weewx, the
console ?
Maybe you should first make yourself familiar with your
environment, your setup, the architecture and then see where
weewx comes into play.

I suggest you read
https://www.wxforum.net/index.php?topic=40730.0 and read the
Ecowitt/FineOffset WiKi linked therein.
Read the chapters about data flow and understand where weewx
comes into play.
Then there are several chapters about how to connect an
Ecowitt console to data logger programs like weewx - even with
the special example of weewx.

For your W830 you can (only) use the weewx interceptor driver,
for your GW2000 the Ecowitt gateway driver aka GW1000 driver.

The weewx WiKi, even though having significantly improved over
time, does not give too much attention to the Ecowitt universe
yet.
But there is the Fine Offset / Ecowitt WiKi which jumps in
here regarding which Ecowitt (clone) consoles are supported.
The weewx WiKi itself is still widely focused on old legacy
models of Fine Offset clone consoles and stations.

So, I suggest you read this first (see above) and then come
back here if still needed - by the way, the Simulator driver
is only to show that weewx has been set up properly in
principle. It won't work with your console (Weather Station).
Having read the weewx documentation you could have understood
that - but to be fair, it took me also a longer time to come
to grips with the jargon etc. used even though being an IT
professional.


On 18.03.2024 20:15, Pi Radio wrote:

I have just joined, and cannot get my Raspberry Pi configured
for my Ventus W830 PWS.  It is linked to various Online
Weather sites including Weather Underground via it's Display.
I also have it linked to an Ecowitt GW2000 that is not
currently linked to any Online Weather sites.

I have read the User Guide, and followed various Tutorials,
but I am none the wiser as to why it does not work?

Is there a step by step guide that is written for a complete
novice like me to follow?

Although the Ventus W830 is listed in the Compatible Hardware
List as a Fine Offset model it does not appear in the
Available Hardware Types in the Software on my Raspberry Pi.
I have tried using Simulator, plus all of the (dozen or so)
options for the various types of PWS listed in the software.

What am I not doing correctly, or what I have missed, I have
no idea? I have just followed the Instructions in the
"Guide". But there still seem to be lots of CRITICAL
__main__: errors in Red, so it is a bit catistrophic?

I am not a programmer, nor that familiar with a Raspberry Pi.
All I know is what I have been struggling with here, and
following YouTube videos.

Any help would be very, very much appreciated.
-- 
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/b6dde367-1685-40a0-a908-8050ccbe9e86n%40googlegroups.com

.
-- 
You re

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

We cannot help if you say you have errors on permissions if you do not 
include the logs so we can look at them.

On Monday, March 18, 2024 at 1:49:21 PM UTC-7 salinois wrote:

> again, I follow the link an other time ; I found also the same link with 
> my error
>
> I put this line in my config.txt
>
> # Uncomment some or all of these to enable the optional hardware interfaces
> dtparam=i2c_arm=on
> #dtparam=i2s=on
>
> dtparam=spi=on
>
> but always an issue with permissions !
>
> sorry for my ignorance but I can't find it.
>
> Patrick
> Le 18/03/2024 à 21:09, salinois a écrit :
>
> YES YES
>
> but I don't use SPI in my driver 
>
>
> Le 18/03/2024 à 20:57, vince a écrit :
>
> Look at the answer in 
> https://raspberrypi.stackexchange.com/questions/69911/how-to-make-raspbian-load-the-spi-module-on-boot-up
>
> Always always always google for your exact error message.  If you had 
> googled for "*SPISoftwareFallback: failed to initialize hardware SPI, 
> falling back to software"* you would have found this and similar pages.
>
> On Monday, March 18, 2024 at 12:34:24 PM UTC-7 salinois wrote:
>
>> hello Vince,
>>
>> I am come back at home.
>>
>> And I have always an error but different:
>>
>> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: Loading 
>> station type BYOWS (user.byows)
>> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: using driver BYOWS
>> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: driver version is 0.51
>> Mar 18 19:20:51 raspberrypi weewxd[1976]: 
>> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 2] Aucun fichier ou dossier de ce type)
>> Mar 18 19:20:51 raspberrypi weewxd[1976]:   warnings.warn(
>> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: StdConvert 
>> target unit is 0x1
>>
>> just after a restart of weewx; *but weewx works fine.*
>>
>> lines in my /boot/config.txt:
>>
>> # Uncomment some or all of these to enable the optional hardware 
>> interfaces
>> dtparam=i2c_arm=on
>> #dtparam=i2s=on
>> #dtparam=spi=on
>>
>>
>> I follow all requisites for permissions.
>>
>> I don't see where is the issue.
>>
>> Patrick
>>
>>
>> Le 07/03/2024 à 01:53, vince a écrit :
>>
>> Patrick - when the sun comes around again in France and you get back to 
>> this, I did more research and updated the permissions wiki page.  Check out 
>> the new section at the bottom of the page (link) 
>> 
>>  which 
>> hopefully explains better.  I got this information from the debian wiki and 
>> a few blogs and other documents available online in recent years.
>>
>> On Wednesday, March 6, 2024 at 2:06:03 PM UTC-8 salinois wrote:
>>
>>> OK Vince,
>>>
>>> this is new with the version 5.
>>>
>>> I'm going to watch the link "github' and I comme back to you.
>>>
>>> good night from France.
>>>
>>> Patrick
>>> Le 06/03/2024 à 22:52, vince a écrit :
>>>
>>> 4.9 runs as root so you do not see permission issues there. 
>>>
>>> 5.x runs as user 'weewx' so you have to add that user to the correct 
>>> group(s) to access hardware
>>>
>>>
>>> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>>>
>>> On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:
>>>
 I understand that you say me, but why I don't have this issue with 
 version weewx 4.9 ?

 the only difference is RPi 3b and now RPi 4b with bulleyes.

 Weewx 4.9 on RPi 3b with Buster

 Weewx 5.0.2 on RPi 4b with bulleyes "error"

 I am watching the link "robotics"

 Patrick



 Le 06/03/2024 à 22:31, vince a écrit :

 You need to work through googling your exact error message. 
 "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
 software (error was: [Errno 13] Permission" 

 See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
 helps any.   It might be group 'spi' that you need to add the user to.

 Rather than changing things randomly please read the link end to end to 
 understand it.


 On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:

> Yes, Vince, I took as you said me.
>
>  $ getent group gpio
> gpio:x:997:pi,weewx
>
> but it is always the same things, this error come , only when I 
> restart weewx. !!!
>
> patrick
> Le 06/03/2024 à 22:15, vince a écrit :
>
> patrick - as I said earlier, 
> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 13] Permission non accordée)" clearly 
> indicates 
> a permission issue. 
>
> add the weewx user to group gpio.  Really.
>
> On Wednesday, March 6

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

FWIW the gw1000 driver is 'much' easier to get going especially if you're 
new to the pi.  Works great.

On Monday, March 18, 2024 at 1:12:19 PM UTC-7 Pi Radio wrote:

> Interceptor... I saw that earlier?  
>
> Going forwards I'll stop running and walk slowly through this. Thank you.
>
> By the way the Clock on my VHS VCR is still Flashing... I must read the 
> Instruction Manual one day. (If you are not of a certain age, you are not 
> going to get that joke).
>
> But in all seriousness, I am struggling a bit finding my way around all of 
> this jargon, so I thought that before getting too much further lost, I 
> thought I'd wave and ask for guidance.
>
> I've learnt a great deal so far on this massive learning curve, but 
> obviously I am not up to this ...yet.
>
> Bear with me whilst I uninstall it all again, and start a fresh again.
>
> Many thanks for the Links, I'm off to do some more reading.
>
> On Mon, Mar 18, 2024 at 7:55 PM 'Rainer Lang' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> The Ventus W830 is a Ecowitt WH2910 clone. In your mail it is not clear 
>> what "it" means. Your RaspberryPi, weewx, the console ?
>> Maybe you should first make yourself familiar with your environment, your 
>> setup, the architecture and then see where weewx comes into play.
>>
>> I suggest you read https://www.wxforum.net/index.php?topic=40730.0 and 
>> read the Ecowitt/FineOffset WiKi linked therein.
>> Read the chapters about data flow and understand where weewx comes into 
>> play. 
>> Then there are several chapters about how to connect an Ecowitt console 
>> to data logger programs like weewx - even with the special example of weewx.
>>
>> For your W830 you can (only) use the weewx interceptor driver, for your 
>> GW2000 the Ecowitt gateway driver aka GW1000 driver.
>>
>> The weewx WiKi, even though having significantly improved over time, does 
>> not give too much attention to the Ecowitt universe yet.
>> But there is the Fine Offset / Ecowitt WiKi which jumps in here regarding 
>> which Ecowitt (clone) consoles are supported.
>> The weewx WiKi itself is still widely focused on old legacy models of 
>> Fine Offset clone consoles and stations.
>>
>> So, I suggest you read this first (see above) and then come back here if 
>> still needed - by the way, the Simulator driver is only to show that weewx 
>> has been set up properly in principle. It won't work with your console 
>> (Weather Station). Having read the weewx documentation you could have 
>> understood that - but to be fair, it took me also a longer time to come to 
>> grips with the jargon etc. used even though being an IT professional.
>>
>>
>> On 18.03.2024 20:15, Pi Radio wrote:
>>
>> I have just joined, and cannot get my Raspberry Pi configured for my 
>> Ventus W830 PWS.  It is linked to various Online Weather sites including 
>> Weather Underground via it's Display. I also have it linked to an Ecowitt 
>> GW2000 that is not currently linked to any Online Weather sites. 
>>
>> I have read the User Guide, and followed various Tutorials, but I am none 
>> the wiser as to why it does not work?
>>
>> Is there a step by step guide that is written for a complete novice like 
>> me to follow?
>>
>> Although the Ventus W830 is listed in the Compatible Hardware List as a 
>> Fine Offset model it does not appear in the Available Hardware Types in the 
>> Software on my Raspberry Pi. I have tried using Simulator, plus all of the 
>> (dozen or so) options for the various types of PWS listed in the software. 
>>
>> What am I not doing correctly, or what I have missed, I have no idea? I 
>> have just followed the Instructions in the "Guide". But there still seem to 
>> be lots of CRITICAL __main__: errors in Red, so it is a bit catistrophic?
>>
>> I am not a programmer, nor that familiar with a Raspberry Pi. All I know 
>> is what I have been struggling with here, and following YouTube videos.
>>
>> Any help would be very, very much appreciated.  
>> -- 
>> 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/b6dde367-1685-40a0-a908-8050ccbe9e86n%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/ec992847-5678-43b7-b314-2be91f896aff%40gmail.com
>>  
>> 

[weewx-user] Re: After new installation problems with season skin / no site

[Thomas Hackler]

Hello,
I copied the historygenerator.py file from my old backup to the bin/user 
directory and now it works
thank you!
The bootstrap skin looks nice but I am not sure if I ever installed it, I 
guess no

Vince is right too, there are new and corrected files at github for the 
neowx skin to remove the warnings because of new python versions
I hope that this system with the newest raspian and only necessary 
installations will run a long time.

michael.k...@gmx.at schrieb am Montag, 18. März 2024 um 08:58:19 UTC+1:

> He maybe never installed the Bootstrap skin, there are a couple of skins 
> around that took the historygenerator from the skin, often many years ago, 
> so usually, these are very outdated. Either try to get the 
> historygenerator.py from the old installation, or from some outdated 
> version of the Bootstrap skin, I doubt (but you can give it a try) that a 
> recent version will work without updating the config, there were 
> significant changes.
>
> gjr80 schrieb am Sonntag, 17. März 2024 um 21:43:34 UTC+1:
>
>> Yes, that will be fine. [[Bootstrap]] is only created when you install 
>> the bootstrap skin.
>>
>> Gary
>>
>> On Monday 18 March 2024 at 06:37:52 UTC+10 Thomas Hackler wrote:
>>
>>> I have a copy of my old /etc/weewx/bin/user. there is a 
>>> historygenerator.py file
>>> but there is no [[Bootstrap]] in my new or in my old weewx.conf file
>>>
>>> so maybe it is enough to copy the file historygenerator.py from my old 
>>> system to /etc/weewx/bin/user or should I install the bootstrap skin?
>>>
>>> So I guess I should install the neowx skin again too ?
>>>
>>> gjr80 schrieb am Sonntag, 17. März 2024 um 21:26:05 UTC+1:
>>>
 Agree the problem is a missing user.historygenerator search list 
 extension which (from memory) is provided by the bootstrap skin, but 
 user.historygenerator is being called by the Seasons skin. So I 
 suspect you have modified your Season skin in the past and added 
 user.historygenerator to the Seasons skin config file, 
 skins/Seasons/skin.conf. This would explain why you missed it when 
 checking your backup weewx.conf.

 The solution is to obtain the historygenerator.py from the bootstrap 
 skin and add it to your system. You could simply extract this file from 
 the 
 bootstrap skin and save it to you system, but the easiest way will be as 
 Vince said - just install the bootstrap skin. I would go one step further 
 and disable the bootstrap skin (set enable = False  under [StdReport] 
 [[Bootstrap]] in weewx.conf). This will have no impact on the 
 availability of user.historygenerator, but will prevent the Bootstrap 
 skin from generating its content/output.

 Gary
 On Monday 18 March 2024 at 05:43:50 UTC+10 vince wrote:

> Not quite.
>
> You need to install all added user extensions and skins. In your case 
> it looks like you had the bootstrap skin on your old system which has a 
> file bin/user/historygenerator.py that you are missing on the new system. 
> Either remove the reference to historygenerator in your weewx.conf or 
> install the bootstrap skin to add the missing file.
>
>
> On Sunday, March 17, 2024 at 12:23:43 PM UTC-7 Thomas Hackler wrote:
>
>> sorry I don't understand, I followed this guide
>>
>> https://weewx.com/docs/5.0/usersguide/backup/
>>
>> I compared the weewx.conf file from the fresh installation with my 
>> old one and added all the missing things
>> so I guess everything should work after that? 
>> The neowx skin works normal at the moment, so I will check the 
>> warnings later
>>
>>
>> vince schrieb am Sonntag, 17. März 2024 um 18:33:09 UTC+1:
>>
>>> ModuleNotFoundError: No module named 'user.historygenerator'
>>> You need to install all skins and extensions referenced in your 
>>> .conf files
>>>
>>> You also have a variety of warnings from neowx:
>>> _etc_weewx_skins_neowx_material_month__Y__m_html_tmpl.py:406: 
>>> SyntaxWarning: "is not" with a literal. Did you mean "!="?
>>>
>>> I 'think' this is related to newer versions of python being more 
>>> strict.  I recall trying neowx once and simply editing all the places 
>>> that 
>>> weewx logged those warnings and they went away.
>>>
>>> On Sunday, March 17, 2024 at 8:12:09 AM UTC-7 Thomas Hackler wrote:
>>>
 Hello,
 my raspberry pi crashed and I started with a new system. 
 Fortunately I have copies from my database and the skins.
 I started installing weewx and the gw1000 driver, then I copied the 
 skin folder and the database.
 I had some issues with permissions with the database but this works 
 now. 
 I use two skins. The neowx skin works fine but I get errors for the 
 season skin and no site is made and I don't understand why.

 Mar 

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[Pi Radio]

Interceptor... I saw that earlier?

Going forwards I'll stop running and walk slowly through this. Thank you.

By the way the Clock on my VHS VCR is still Flashing... I must read the
Instruction Manual one day. (If you are not of a certain age, you are not
going to get that joke).

But in all seriousness, I am struggling a bit finding my way around all of
this jargon, so I thought that before getting too much further lost, I
thought I'd wave and ask for guidance.

I've learnt a great deal so far on this massive learning curve, but
obviously I am not up to this ...yet.

Bear with me whilst I uninstall it all again, and start a fresh again.

Many thanks for the Links, I'm off to do some more reading.

On Mon, Mar 18, 2024 at 7:55 PM 'Rainer Lang' via weewx-user <
weewx-user@googlegroups.com> wrote:

> The Ventus W830 is a Ecowitt WH2910 clone. In your mail it is not clear
> what "it" means. Your RaspberryPi, weewx, the console ?
> Maybe you should first make yourself familiar with your environment, your
> setup, the architecture and then see where weewx comes into play.
>
> I suggest you read https://www.wxforum.net/index.php?topic=40730.0 and
> read the Ecowitt/FineOffset WiKi linked therein.
> Read the chapters about data flow and understand where weewx comes into
> play.
> Then there are several chapters about how to connect an Ecowitt console to
> data logger programs like weewx - even with the special example of weewx.
>
> For your W830 you can (only) use the weewx interceptor driver, for your
> GW2000 the Ecowitt gateway driver aka GW1000 driver.
>
> The weewx WiKi, even though having significantly improved over time, does
> not give too much attention to the Ecowitt universe yet.
> But there is the Fine Offset / Ecowitt WiKi which jumps in here regarding
> which Ecowitt (clone) consoles are supported.
> The weewx WiKi itself is still widely focused on old legacy models of Fine
> Offset clone consoles and stations.
>
> So, I suggest you read this first (see above) and then come back here if
> still needed - by the way, the Simulator driver is only to show that weewx
> has been set up properly in principle. It won't work with your console
> (Weather Station). Having read the weewx documentation you could have
> understood that - but to be fair, it took me also a longer time to come to
> grips with the jargon etc. used even though being an IT professional.
>
>
> On 18.03.2024 20:15, Pi Radio wrote:
>
> I have just joined, and cannot get my Raspberry Pi configured for my
> Ventus W830 PWS.  It is linked to various Online Weather sites including
> Weather Underground via it's Display. I also have it linked to an Ecowitt
> GW2000 that is not currently linked to any Online Weather sites.
>
> I have read the User Guide, and followed various Tutorials, but I am none
> the wiser as to why it does not work?
>
> Is there a step by step guide that is written for a complete novice like
> me to follow?
>
> Although the Ventus W830 is listed in the Compatible Hardware List as a
> Fine Offset model it does not appear in the Available Hardware Types in the
> Software on my Raspberry Pi. I have tried using Simulator, plus all of the
> (dozen or so) options for the various types of PWS listed in the software.
>
> What am I not doing correctly, or what I have missed, I have no idea? I
> have just followed the Instructions in the "Guide". But there still seem to
> be lots of CRITICAL __main__: errors in Red, so it is a bit catistrophic?
>
> I am not a programmer, nor that familiar with a Raspberry Pi. All I know
> is what I have been struggling with here, and following YouTube videos.
>
> Any help would be very, very much appreciated.
> --
> 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/b6dde367-1685-40a0-a908-8050ccbe9e86n%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/ec992847-5678-43b7-b314-2be91f896aff%40gmail.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 
http

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[vince]

Look at the answer in 
https://raspberrypi.stackexchange.com/questions/69911/how-to-make-raspbian-load-the-spi-module-on-boot-up

Always always always google for your exact error message.  If you had 
googled for "*SPISoftwareFallback: failed to initialize hardware SPI, 
falling back to software"* you would have found this and similar pages.

On Monday, March 18, 2024 at 12:34:24 PM UTC-7 salinois wrote:

> hello Vince,
>
> I am come back at home.
>
> And I have always an error but different:
>
> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: Loading 
> station type BYOWS (user.byows)
> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: using driver BYOWS
> Mar 18 19:20:51 raspberrypi weewxd.py: BYOWS RPi: driver version is 0.51
> Mar 18 19:20:51 raspberrypi weewxd[1976]: 
> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 2] Aucun fichier ou dossier de ce type)
> Mar 18 19:20:51 raspberrypi weewxd[1976]:   warnings.warn(
> Mar 18 19:20:51 raspberrypi weewxd[1976]: INFO weewx.engine: StdConvert 
> target unit is 0x1
>
> just after a restart of weewx; *but weewx works fine.*
>
> lines in my /boot/config.txt:
>
> # Uncomment some or all of these to enable the optional hardware interfaces
> dtparam=i2c_arm=on
> #dtparam=i2s=on
> #dtparam=spi=on
>
>
> I follow all requisites for permissions.
>
> I don't see where is the issue.
>
> Patrick
>
>
> Le 07/03/2024 à 01:53, vince a écrit :
>
> Patrick - when the sun comes around again in France and you get back to 
> this, I did more research and updated the permissions wiki page.  Check out 
> the new section at the bottom of the page (link) 
> 
>  which 
> hopefully explains better.  I got this information from the debian wiki and 
> a few blogs and other documents available online in recent years.
>
> On Wednesday, March 6, 2024 at 2:06:03 PM UTC-8 salinois wrote:
>
>> OK Vince,
>>
>> this is new with the version 5.
>>
>> I'm going to watch the link "github' and I comme back to you.
>>
>> good night from France.
>>
>> Patrick
>> Le 06/03/2024 à 22:52, vince a écrit :
>>
>> 4.9 runs as root so you do not see permission issues there. 
>>
>> 5.x runs as user 'weewx' so you have to add that user to the correct 
>> group(s) to access hardware
>>
>>
>> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>>
>> On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:
>>
>>> I understand that you say me, but why I don't have this issue with 
>>> version weewx 4.9 ?
>>>
>>> the only difference is RPi 3b and now RPi 4b with bulleyes.
>>>
>>> Weewx 4.9 on RPi 3b with Buster
>>>
>>> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>>>
>>> I am watching the link "robotics"
>>>
>>> Patrick
>>>
>>>
>>>
>>> Le 06/03/2024 à 22:31, vince a écrit :
>>>
>>> You need to work through googling your exact error message. 
>>> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>> software (error was: [Errno 13] Permission" 
>>>
>>> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
>>> helps any.   It might be group 'spi' that you need to add the user to.
>>>
>>> Rather than changing things randomly please read the link end to end to 
>>> understand it.
>>>
>>>
>>> On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:
>>>
 Yes, Vince, I took as you said me.

  $ getent group gpio
 gpio:x:997:pi,weewx

 but it is always the same things, this error come , only when I restart 
 weewx. !!!

 patrick
 Le 06/03/2024 à 22:15, vince a écrit :

 patrick - as I said earlier, 
 " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
 SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
 software (error was: [Errno 13] Permission non accordée)" clearly 
 indicates 
 a permission issue. 

 add the weewx user to group gpio.  Really.

 On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:

> yes, I took that.
>
> ls -ail /etc/weewx/bin/user/
> total 36
> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>
>
> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>
> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>
> This is again better.
>
> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
> value: 0.0
> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>

Re: [weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

['Rainer Lang' via weewx-user]

The Ventus W830 is a Ecowitt WH2910 clone. In your mail it is not clear 
what "it" means. Your RaspberryPi, weewx, the console ?
Maybe you should first make yourself familiar with your environment, 
your setup, the architecture and then see where weewx comes into play.


I suggest you read https://www.wxforum.net/index.php?topic=40730.0 and 
read the Ecowitt/FineOffset WiKi linked therein.
Read the chapters about data flow and understand where weewx comes into 
play.
Then there are several chapters about how to connect an Ecowitt console 
to data logger programs like weewx - even with the special example of weewx.


For your W830 you can (only) use the weewx interceptor driver, for your 
GW2000 the Ecowitt gateway driver aka GW1000 driver.


The weewx WiKi, even though having significantly improved over time, 
does not give too much attention to the Ecowitt universe yet.
But there is the Fine Offset / Ecowitt WiKi which jumps in here 
regarding which Ecowitt (clone) consoles are supported.
The weewx WiKi itself is still widely focused on old legacy models of 
Fine Offset clone consoles and stations.


So, I suggest you read this first (see above) and then come back here if 
still needed - by the way, the Simulator driver is only to show that 
weewx has been set up properly in principle. It won't work with your 
console (Weather Station). Having read the weewx documentation you could 
have understood that - but to be fair, it took me also a longer time to 
come to grips with the jargon etc. used even though being an IT 
professional.



On 18.03.2024 20:15, Pi Radio wrote:
I have just joined, and cannot get my Raspberry Pi configured for my 
Ventus W830 PWS.  It is linked to various Online Weather sites 
including Weather Underground via it's Display. I also have it linked 
to an Ecowitt GW2000 that is not currently linked to any Online 
Weather sites.


I have read the User Guide, and followed various Tutorials, but I am 
none the wiser as to why it does not work?


Is there a step by step guide that is written for a complete novice 
like me to follow?


Although the Ventus W830 is listed in the Compatible Hardware List as 
a Fine Offset model it does not appear in the Available Hardware Types 
in the Software on my Raspberry Pi. I have tried using Simulator, plus 
all of the (dozen or so) options for the various types of PWS listed 
in the software.


What am I not doing correctly, or what I have missed, I have no idea? 
I have just followed the Instructions in the "Guide". But there still 
seem to be lots of CRITICAL __main__: errors in Red, so it is a bit 
catistrophic?


I am not a programmer, nor that familiar with a Raspberry Pi. All I 
know is what I have been struggling with here, and following YouTube 
videos.


Any help would be very, very much appreciated.
--
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/b6dde367-1685-40a0-a908-8050ccbe9e86n%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/ec992847-5678-43b7-b314-2be91f896aff%40gmail.com.

[weewx-user] Re: Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[vince]

It's a little hard to guess what exactly you're trying to do and certainly 
impossible to guess what you're seeing as errors.   Are you trying to get 
weewx to get your Ventus data from the gw2000 gateway ? 

But regardless, you should take tiny steps toward the goal:

   - there are zillions of "Guide"(s).  Which one are you using ?
   - what did you do ?  What did you see ?
   - Hopefully you are following the 'debian' instructions (link) 
    to install it. 
  - That should run almost certainly without error on a pi to install a 
  working setup using the Simulator driver
  - if you tried, but failed there, what exactly did you see in 
  console/logfile output ?  Again, please no screenshots.  Copy/paste what 
  you see as output
   - once you get the Simulator running, we can help you switch to getting 
   data from the gw2000if that is what you're trying to do 
   
You might start with the FAQ (link) 
 and 
how to ask questions and provide enough detail that we can try to help. 
 There's info there on how to find your logs as well.

On Monday, March 18, 2024 at 12:17:38 PM UTC-7 Pi Radio wrote:

> I have just joined, and cannot get my Raspberry Pi configured for my 
> Ventus W830 PWS.  It is linked to various Online Weather sites including 
> Weather Underground via it's Display. I also have it linked to an Ecowitt 
> GW2000 that is not currently linked to any Online Weather sites. 
>
> I have read the User Guide, and followed various Tutorials, but I am none 
> the wiser as to why it does not work?
>
> Is there a step by step guide that is written for a complete novice like 
> me to follow?
>
> Although the Ventus W830 is listed in the Compatible Hardware List as a 
> Fine Offset model it does not appear in the Available Hardware Types in the 
> Software on my Raspberry Pi. I have tried using Simulator, plus all of the 
> (dozen or so) options for the various types of PWS listed in the software. 
>
> What am I not doing correctly, or what I have missed, I have no idea? I 
> have just followed the Instructions in the "Guide". But there still seem to 
> be lots of CRITICAL __main__: errors in Red, so it is a bit catistrophic?
>
> I am not a programmer, nor that familiar with a Raspberry Pi. All I know 
> is what I have been struggling with here, and following YouTube videos.
>
> Any help would be very, very much appreciated.  
>

-- 
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/0db49652-ef8b-49ca-8a93-7ef885464f8fn%40googlegroups.com.

[weewx-user] Ventus W830 or Ecowitt GW2000 help for Raspberry Pi

[Pi Radio]

I have just joined, and cannot get my Raspberry Pi configured for my Ventus 
W830 PWS.  It is linked to various Online Weather sites including Weather 
Underground via it's Display. I also have it linked to an Ecowitt GW2000 
that is not currently linked to any Online Weather sites. 

I have read the User Guide, and followed various Tutorials, but I am none 
the wiser as to why it does not work?

Is there a step by step guide that is written for a complete novice like me 
to follow?

Although the Ventus W830 is listed in the Compatible Hardware List as a 
Fine Offset model it does not appear in the Available Hardware Types in the 
Software on my Raspberry Pi. I have tried using Simulator, plus all of the 
(dozen or so) options for the various types of PWS listed in the software. 

What am I not doing correctly, or what I have missed, I have no idea? I 
have just followed the Instructions in the "Guide". But there still seem to 
be lots of CRITICAL __main__: errors in Red, so it is a bit catistrophic?

I am not a programmer, nor that familiar with a Raspberry Pi. All I know is 
what I have been struggling with here, and following YouTube videos.

Any help would be very, very much appreciated.  

-- 
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/b6dde367-1685-40a0-a908-8050ccbe9e86n%40googlegroups.com.

Re: [weewx-user] Problem after downgrading

[Pierre-Yves]

Hello George,
Maybe try:
sudo usermod -aG i2c weewx
and 
sudo usermod -aG gpio weewx"

I my case, that fixed the problems I had with the BME280 and as3935 
extensions
PY
Le lundi 18 mars 2024 à 15:52:57 UTC+1, George Nimrodel a écrit :

> I'm making progress...
>
> The last upgrade/downgrade relocated my device's driver (BCRobotics) and 
> extensions file to a new User folder.
>
>  I returned them to the primary User folder. However, upon doing so, I 
> encountered the same error I experienced when I upgraded to version 5.0.2.
>
> Subsequently, I attempted another upgrade to version 5.0.2, and the error 
> persisted:
>
> Mar 18 16:23:41 edessa /weewxd.py[414]: BCRobo: MainThread: W1ThermSensor 
> setup fine.
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: Caught OSError: 
> [Errno 13] Permission denied: '/dev/i2c-1'
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   Traceback 
> (most recent call last):
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/share/weewx/weewxd.py", line 160, in main
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  engine = weewx.engine.StdEngine(config_dict)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 77, in __init__
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self.setupStation(config_dict)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  __import__(driver)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/etc/weewx/bin/user/BCRobotics.py", line 80, in 
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   i2c = 
> busio.I2C(board.SCL, board.SDA)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/busio.py", line 32, in __init__
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self.init(scl, sda, frequency)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/busio.py", line 107, in init
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self._i2c = _I2C(portId, mode=_I2C.MASTER, baudrate=frequency)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py",
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self._i2c_bus = smbus.SMBus(bus_num)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/smbus.py", line 
> 125, in __init__
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self.open(bus)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/smbus.py", line 
> 151, in open
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self._device = open("/dev/i2c-{0}".format(bus), "r+b", buffering=0)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  PermissionError: [Errno 13] Permission denied: '/dev/i2c-1'
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   Waiting 
> 10 seconds then retrying... 
>
> I added the weewx user to the group defined on the device.
>
> Station is running but I still get errors from some sensors:
>
> Mar 18 16:47:51 edessa /weewxd.py[416]: BCRobo: MainThread: Error setting 
> up GPIO 17: No access to /dev/mem.  Try running as root!
>
> Another thing I don't understand is how the station reverted to Simulator 
> mode despite keeping the .conf file intact.
>
> On Monday, March 18, 2024 at 3:18:47 PM UTC+2 George Nimrodel wrote:
>
>> Hello again,
>>
>> even after debug=1 I don't see any more information:
>>
>> Mar 18 14:49:45 edessa systemd[1]: Started WeeWX.
>> Mar 18 14:49:48 edessa weewxd[411]: Traceback (most recent call last):
>> Mar 18 14:49:48 edessa weewxd[411]:   File "/usr/share/weewx/weewxd", 
>> line 29, in 
>> Mar 18 14:49:48 edessa weewxd[411]: import user.extensions
>> Mar 18 14:49:48 edessa weewxd[411]: ModuleNotFoundError: No module named 
>> 'user.extensions'
>> Mar 18 14:49:48 edessa systemd[1]: weewx.service: Main process exited, 
>> code=exited, status=1/FAILURE
>> Mar 18 14:49:48 edessa systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>>
>> On Monday, March 18, 2024 at 1:13:31 AM UTC+2 Tom Keffer wrote:
>>
>>> Please set debug=1, then restart weewx. Post the log from startup to 
>>> crash.
>>>
>>> The startup gives important clues on where weewxd thinks things are 
>>> located.
>>>
>>> -tk
>>>
>>> On Sun, Mar 17, 2024 at 12:08 PM George Nimrodel  
>>> wrote:
>>>
 Hello everyone,

Re: [weewx-user] Problem after downgrading

[George Nimrodel]

I'm making progress...

The last upgrade/downgrade relocated my device's driver (BCRobotics) and 
extensions file to a new User folder.

 I returned them to the primary User folder. However, upon doing so, I 
encountered the same error I experienced when I upgraded to version 5.0.2.

Subsequently, I attempted another upgrade to version 5.0.2, and the error 
persisted:

Mar 18 16:23:41 edessa /weewxd.py[414]: BCRobo: MainThread: W1ThermSensor 
setup fine.
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: Caught OSError: 
[Errno 13] Permission denied: '/dev/i2c-1'
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   Traceback 
(most recent call last):
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/share/weewx/weewxd.py", line 160, in main
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   engine 
= weewx.engine.StdEngine(config_dict)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 77, in __init__
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 self.setupStation(config_dict)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 104, in setupStation
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 __import__(driver)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/etc/weewx/bin/user/BCRobotics.py", line 80, in 
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   i2c = 
busio.I2C(board.SCL, board.SDA)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/local/lib/python3.7/dist-packages/busio.py", line 32, in __init__
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 self.init(scl, sda, frequency)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/local/lib/python3.7/dist-packages/busio.py", line 107, in init
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 self._i2c = _I2C(portId, mode=_I2C.MASTER, baudrate=frequency)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/local/lib/python3.7/dist-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py",
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 self._i2c_bus = smbus.SMBus(bus_num)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/smbus.py", line 
125, in __init__
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 self.open(bus)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
"/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/smbus.py", line 
151, in open
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 self._device = open("/dev/i2c-{0}".format(bus), "r+b", buffering=0)
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
 PermissionError: [Errno 13] Permission denied: '/dev/i2c-1'
Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   Waiting 10 
seconds then retrying... 

I added the weewx user to the group defined on the device.

Station is running but I still get errors from some sensors:

Mar 18 16:47:51 edessa /weewxd.py[416]: BCRobo: MainThread: Error setting 
up GPIO 17: No access to /dev/mem.  Try running as root!

Another thing I don't understand is how the station reverted to Simulator 
mode despite keeping the .conf file intact.

On Monday, March 18, 2024 at 3:18:47 PM UTC+2 George Nimrodel wrote:

> Hello again,
>
> even after debug=1 I don't see any more information:
>
> Mar 18 14:49:45 edessa systemd[1]: Started WeeWX.
> Mar 18 14:49:48 edessa weewxd[411]: Traceback (most recent call last):
> Mar 18 14:49:48 edessa weewxd[411]:   File "/usr/share/weewx/weewxd", line 
> 29, in 
> Mar 18 14:49:48 edessa weewxd[411]: import user.extensions
> Mar 18 14:49:48 edessa weewxd[411]: ModuleNotFoundError: No module named 
> 'user.extensions'
> Mar 18 14:49:48 edessa systemd[1]: weewx.service: Main process exited, 
> code=exited, status=1/FAILURE
> Mar 18 14:49:48 edessa systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
>
> On Monday, March 18, 2024 at 1:13:31 AM UTC+2 Tom Keffer wrote:
>
>> Please set debug=1, then restart weewx. Post the log from startup to 
>> crash.
>>
>> The startup gives important clues on where weewxd thinks things are 
>> located.
>>
>> -tk
>>
>> On Sun, Mar 17, 2024 at 12:08 PM George Nimrodel  
>> wrote:
>>
>>> Hello everyone,
>>>
>>> I encountered an issue with my installation following an update from 
>>> version 4.10.2 to 5.0.2 (unfortunately, no logs were retained). 
>>> Consequently, I attempted to revert to the previous version.
>>>
>>> However, even after the downgrade, I still encountered difficulties:
>>>
>>> ● weewx.service - WeeWX
>>>Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>>> prese

Re: [weewx-user] Problem after downgrading

[George Nimrodel]

Hello again,

even after debug=1 I don't see any more information:

Mar 18 14:49:45 edessa systemd[1]: Started WeeWX.
Mar 18 14:49:48 edessa weewxd[411]: Traceback (most recent call last):
Mar 18 14:49:48 edessa weewxd[411]:   File "/usr/share/weewx/weewxd", line 
29, in 
Mar 18 14:49:48 edessa weewxd[411]: import user.extensions
Mar 18 14:49:48 edessa weewxd[411]: ModuleNotFoundError: No module named 
'user.extensions'
Mar 18 14:49:48 edessa systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Mar 18 14:49:48 edessa systemd[1]: weewx.service: Failed with result 
'exit-code'.

On Monday, March 18, 2024 at 1:13:31 AM UTC+2 Tom Keffer wrote:

> Please set debug=1, then restart weewx. Post the log from startup to crash.
>
> The startup gives important clues on where weewxd thinks things are 
> located.
>
> -tk
>
> On Sun, Mar 17, 2024 at 12:08 PM George Nimrodel  
> wrote:
>
>> Hello everyone,
>>
>> I encountered an issue with my installation following an update from 
>> version 4.10.2 to 5.0.2 (unfortunately, no logs were retained). 
>> Consequently, I attempted to revert to the previous version.
>>
>> However, even after the downgrade, I still encountered difficulties:
>>
>> ● weewx.service - WeeWX
>>Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: enabled)
>>Active: failed (Result: exit-code) since Sat 2024-03-16 12:24:07 EET; 
>> 1 day 6h ago
>>  Docs: https://weewx.com/docs
>>   Process: 411 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf 
>> (code=exited, status=1/FAILURE)
>>  Main PID: 411 (code=exited, status=1/FAILURE)
>>
>>
>> Mar 17 18:43:50 edessa weewxd[419]: Traceback (most recent call last):
>> Mar 17 18:43:50 edessa weewxd[419]:   File "/usr/share/weewx/weewxd", 
>> line 29, in 
>> Mar 17 18:43:50 edessa weewxd[419]: import user.extensions
>> Mar 17 18:43:50 edessa weewxd[419]: ModuleNotFoundError: No module named 
>> 'user.extensions'
>> Mar 17 18:43:50 edessa systemd[1]: weewx.service: Main process exited, 
>> code=exited, status=1/FAILURE
>> Mar 17 18:43:50 edessa systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>>
>> This occurred on a Raspberry Pi 3b+ running version 4.10.2 with the 
>> BCRobotics 
>> driver .
>>
>> Any assistance would be greatly appreciated. Thank you.
>>
>> -- 
>> 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/70b373c6-8597-487f-a8f8-457275c3a510n%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/c021d248-3186-46dd-9d9e-7f6ea1804eebn%40googlegroups.com.

[weewx-user] Re: After new installation problems with season skin / no site

['michael.k...@gmx.at' via weewx-user]

He maybe never installed the Bootstrap skin, there are a couple of skins 
around that took the historygenerator from the skin, often many years ago, 
so usually, these are very outdated. Either try to get the 
historygenerator.py from the old installation, or from some outdated 
version of the Bootstrap skin, I doubt (but you can give it a try) that a 
recent version will work without updating the config, there were 
significant changes.

gjr80 schrieb am Sonntag, 17. März 2024 um 21:43:34 UTC+1:

> Yes, that will be fine. [[Bootstrap]] is only created when you install the 
> bootstrap skin.
>
> Gary
>
> On Monday 18 March 2024 at 06:37:52 UTC+10 Thomas Hackler wrote:
>
>> I have a copy of my old /etc/weewx/bin/user. there is a 
>> historygenerator.py file
>> but there is no [[Bootstrap]] in my new or in my old weewx.conf file
>>
>> so maybe it is enough to copy the file historygenerator.py from my old 
>> system to /etc/weewx/bin/user or should I install the bootstrap skin?
>>
>> So I guess I should install the neowx skin again too ?
>>
>> gjr80 schrieb am Sonntag, 17. März 2024 um 21:26:05 UTC+1:
>>
>>> Agree the problem is a missing user.historygenerator search list 
>>> extension which (from memory) is provided by the bootstrap skin, but 
>>> user.historygenerator is being called by the Seasons skin. So I suspect 
>>> you have modified your Season skin in the past and added 
>>> user.historygenerator to the Seasons skin config file, 
>>> skins/Seasons/skin.conf. This would explain why you missed it when 
>>> checking your backup weewx.conf.
>>>
>>> The solution is to obtain the historygenerator.py from the bootstrap 
>>> skin and add it to your system. You could simply extract this file from the 
>>> bootstrap skin and save it to you system, but the easiest way will be as 
>>> Vince said - just install the bootstrap skin. I would go one step further 
>>> and disable the bootstrap skin (set enable = False  under [StdReport] 
>>> [[Bootstrap]] in weewx.conf). This will have no impact on the 
>>> availability of user.historygenerator, but will prevent the Bootstrap 
>>> skin from generating its content/output.
>>>
>>> Gary
>>> On Monday 18 March 2024 at 05:43:50 UTC+10 vince wrote:
>>>
 Not quite.

 You need to install all added user extensions and skins. In your case 
 it looks like you had the bootstrap skin on your old system which has a 
 file bin/user/historygenerator.py that you are missing on the new system. 
 Either remove the reference to historygenerator in your weewx.conf or 
 install the bootstrap skin to add the missing file.


 On Sunday, March 17, 2024 at 12:23:43 PM UTC-7 Thomas Hackler wrote:

> sorry I don't understand, I followed this guide
>
> https://weewx.com/docs/5.0/usersguide/backup/
>
> I compared the weewx.conf file from the fresh installation with my old 
> one and added all the missing things
> so I guess everything should work after that? 
> The neowx skin works normal at the moment, so I will check the 
> warnings later
>
>
> vince schrieb am Sonntag, 17. März 2024 um 18:33:09 UTC+1:
>
>> ModuleNotFoundError: No module named 'user.historygenerator'
>> You need to install all skins and extensions referenced in your .conf 
>> files
>>
>> You also have a variety of warnings from neowx:
>> _etc_weewx_skins_neowx_material_month__Y__m_html_tmpl.py:406: 
>> SyntaxWarning: "is not" with a literal. Did you mean "!="?
>>
>> I 'think' this is related to newer versions of python being more 
>> strict.  I recall trying neowx once and simply editing all the places 
>> that 
>> weewx logged those warnings and they went away.
>>
>> On Sunday, March 17, 2024 at 8:12:09 AM UTC-7 Thomas Hackler wrote:
>>
>>> Hello,
>>> my raspberry pi crashed and I started with a new system. Fortunately 
>>> I have copies from my database and the skins.
>>> I started installing weewx and the gw1000 driver, then I copied the 
>>> skin folder and the database.
>>> I had some issues with permissions with the database but this works 
>>> now. 
>>> I use two skins. The neowx skin works fine but I get errors for the 
>>> season skin and no site is made and I don't understand why.
>>>
>>> Mar 17 15:45:28 raspberrypi weewxd[114945]: ERROR 
>>> weewx.reportengine: Caught unrecoverable exception in generator 
>>> 'weewx.cheetahgenerator.CheetahGenerator'
>>>
>>> Full log file attached.
>>> Thank you for helping!
>>> Thomas Hackler
>>>
>>>
>>>

-- 
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/83dfc84e-cf3f-4089-8e8d-8559207305f5