Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[flor...@pre-vost.fr]

Hi,

I'm the author of WLLDriver on Github.
Yes, I think that *altimeter *is the good value. But I suggest to confirm 
that by directly ask Davis.

Regards,

Le samedi 21 novembre 2020 à 22:31:04 UTC+1, kk44...@gmail.com a écrit :

> I found that additional information at 
> https://www.manula.com/manuals/pws/davis-kb/1/en/topic/barometric-pressure-issues
> .
>
> There they say, that Davis uses different calculations in different 
> devices:
>
>- VP2 and envoy consoles: sea-level pressure ("barometer", QFF)
>- WeatherLinkLive: altimeter pressure ("altimeter", QNH)
>- Vue consoles: user can choose between the two
>
> So it seems, the author of the "weatherlinkliveudp" driver read the 
> documentation most carefully. 
>
> And to confuse the user or something, in the LOOP data record, Davis calls 
> the value, what we learnt is altimeter, "bar_sea_level". 
>
> The archive record contains all the three values barometer, altimeter, and 
> pressure (I checked). Since the "weatherlinkliveudp" driver does not 
> provide a value for barometer, may be, WeeWX calculates it by itself.
>
> didier@gmail.com schrieb am Samstag, 21. November 2020 um 20:54:45 
> UTC+1:
>
>> Thank's a lot
>> I'm learning a lot of things with you
>>
>> Le sam. 21 nov. 2020 à 18:59, vince  a écrit :
>>
>>> On Saturday, November 21, 2020 at 9:31:11 AM UTC-8 kk44...@gmail.com 
>>> wrote:
>>>
 didier@gmail.com schrieb am Samstag, 21. November 2020 um 16:09:22 
 UTC+1:

> Ooops, after 10 mn the 2 values have diverged (only 1 mbar)
> The explanation is that weatherlinkliveudp driver uses "altimeter" and 
> WLLDriver uses "barometer" for the station info
>

 That I do not understand. Does the driver only retrieves the readings 
 from the hardware, doesn't it? So, which way the driver can influence 
 which 
 values is displayed?
  

>>>
>>> There are two pressure-related elements provided by the Davis hardware. 
>>>One is the pressure as reported by the sensor, the other is the pressure 
>>> corrected to sea-level pressure based on your altitude.The driver code 
>>> defines which sensor values it uses for what generic weewx database element
>>>
>>> Both drivers map 'bar_absolute' from the hardware to weewx 'pressure' 
>>> in the database.
>>>
>>> But...the two drivers map 'bar_sea_level' from the hardware to 
>>> different elements in weewx's database.
>>>
>>>- WLLDriver.py   puts the value into 'barometer' in weewx
>>>- weatherlinkliveudp.py  puts the value into 'altimeter' in weewx
>>>
>>> According to 
>>> https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter, 
>>> the correction math differs slightly, so I'd expect slight differences 
>>> perhaps.  A difference of 1 mbar to me isn't something to worry too much.  
>>> You're talking 0.1 percent offset.  The sensor itself isn't that precise to 
>>> begin with.
>>>
>>>
>>> -- 
>>> 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/fccfe641-03d1-473f-910a-c1f0d7aa2cabn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Quel temps fait-il à Auffargis  ?
>>
>

-- 
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/c278a6af-f77f-4abc-9610-3d34bdc9a5a1n%40googlegroups.com.

Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[Didier Decoodt]

thank's Florentin, I've just opened a ticket on Davis support, I will give
you the result next week I hope.

Le dim. 22 nov. 2020 à 14:24, flor...@pre-vost.fr  a
écrit :

> Hi,
>
> I'm the author of WLLDriver on Github.
> Yes, I think that *altimeter *is the good value. But I suggest to confirm
> that by directly ask Davis.
>
> Regards,
>
> Le samedi 21 novembre 2020 à 22:31:04 UTC+1, kk44...@gmail.com a écrit :
>
>> I found that additional information at
>> https://www.manula.com/manuals/pws/davis-kb/1/en/topic/barometric-pressure-issues
>> .
>>
>> There they say, that Davis uses different calculations in different
>> devices:
>>
>>- VP2 and envoy consoles: sea-level pressure ("barometer", QFF)
>>- WeatherLinkLive: altimeter pressure ("altimeter", QNH)
>>- Vue consoles: user can choose between the two
>>
>> So it seems, the author of the "weatherlinkliveudp" driver read the
>> documentation most carefully.
>>
>> And to confuse the user or something, in the LOOP data record, Davis
>> calls the value, what we learnt is altimeter, "bar_sea_level".
>>
>> The archive record contains all the three values barometer, altimeter,
>> and pressure (I checked). Since the "weatherlinkliveudp" driver does not
>> provide a value for barometer, may be, WeeWX calculates it by itself.
>>
>> didier@gmail.com schrieb am Samstag, 21. November 2020 um 20:54:45
>> UTC+1:
>>
>>> Thank's a lot
>>> I'm learning a lot of things with you
>>>
>>> Le sam. 21 nov. 2020 à 18:59, vince  a écrit :
>>>
 On Saturday, November 21, 2020 at 9:31:11 AM UTC-8 kk44...@gmail.com
 wrote:

> didier@gmail.com schrieb am Samstag, 21. November 2020 um
> 16:09:22 UTC+1:
>
>> Ooops, after 10 mn the 2 values have diverged (only 1 mbar)
>> The explanation is that weatherlinkliveudp driver uses "altimeter"
>> and WLLDriver uses "barometer" for the station info
>>
>
> That I do not understand. Does the driver only retrieves the readings
> from the hardware, doesn't it? So, which way the driver can influence 
> which
> values is displayed?
>
>

 There are two pressure-related elements provided by the Davis hardware.
One is the pressure as reported by the sensor, the other is the pressure
 corrected to sea-level pressure based on your altitude.The driver code
 defines which sensor values it uses for what generic weewx database element

 Both drivers map 'bar_absolute' from the hardware to weewx 'pressure'
 in the database.

 But...the two drivers map 'bar_sea_level' from the hardware to
 different elements in weewx's database.

- WLLDriver.py   puts the value into 'barometer' in weewx
- weatherlinkliveudp.py  puts the value into 'altimeter' in weewx

 According to
 https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter,
 the correction math differs slightly, so I'd expect slight differences
 perhaps.  A difference of 1 mbar to me isn't something to worry too much.
 You're talking 0.1 percent offset.  The sensor itself isn't that precise to
 begin with.


 --
 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/fccfe641-03d1-473f-910a-c1f0d7aa2cabn%40googlegroups.com
 
 .

>>>
>>>
>>> --
>>> Quel temps fait-il à Auffargis  ?
>>>
>> --
> 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/c278a6af-f77f-4abc-9610-3d34bdc9a5a1n%40googlegroups.com
> 
> .
>


-- 
Quel temps fait-il à Auffargis  ?

-- 
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/CAAvt3%3DQqs2SuLr%2BiLVb2LWy%2ByUG-V8acE8F73G_bJLSyU%3DojYg%40mail.gmail.com.

[weewx-user] Copy webcam image to /var/www/html/weewx/image.jpg

[Rich Strle]

My copy of weewx is running on a Raspberry Pi. I am trying to get an image 
from a webcam on my local network using wget, resizing the image using 
imagemagick, then put it in the /var/www/html/weewx/ folder so it will get 
uploaded to my web host.

wget --user=user --password=user  
http://192.168.254.33/jpg/image.jpg?size=3 -O/var/www/html/weewx/image.jpg

I get a Permission denied error.

>From there my plan was to use imagick to reduced the size of the file and 
include the image in the upload.

I as able to put this in a bash script and run a cron job to do this 
process to my /home/pi/Pictures/image.jpg folder but I can''t figure out 
how to copy the file to the html/weewx directory.

If there is a better way to do what I'm trying to accomplish I'm willing to 
try that.

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/fa466bb2-d58a-42cc-9870-316770563bd7n%40googlegroups.com.

Re: [weewx-user] failed outTemp crashes alarm and "standard" skin

[GBW]

1. Checking for a None value checks that there is a connection, I presume, 
so could I not get false frost alarms? Is it not possible to stop weewx 
crashing completely when "outTemp" is None (as I noticed in the loop)? I 
don't recall that happening before; there was just a gap in the graph, 
which prompted me to change the battery. Should I try the multiple alarm 
example too or are these exclusive under [Alarm]?
2. I notice the loop does report batteryStatus for the sensors, but I have 
never noticed any change to the reported (binary) value. I will try the 
suggested lowBattery module too, thanks. 
3. Before replacing the battery, I first disabled Alarm resulting in the 
mixed report. The report publication reverted fully to my enabled 
"Standard" skin only after I had renewed the battery and rebooted, which 
suggests to me that alone the missing connection caused weewx to use the 
wrong skin until the fault was cleared. That never happened before (as 
there was no other default skin), which suggests to me that any error in 
the functioning of the "Standard" skin enables the default "Seasons" skin. 
Is that intended? 

tke...@gmail.com schrieb am Samstag, 21. November 2020 um 13:25:18 UTC+1:

> How to prevent what happening again? The TypeError? If so, use an 
> expression such as
>
> outTemp is None or outTemp < 3.0
>
>
> Or, do you mean dealing with a bad battery? If so, if the TE923 emits a 
> battery status, use the "lowBattery" module in the examples subdirectory to 
> sense a bad battery.
>
> Or, do you mean the mix of image types? You did not provide any 
> information about your report configuration, but if you changed report 
> types, then got an error, I can see that you'd end up with a mix of image 
> types. Try deleting everything in the HTML directory. They will all be 
> recreated afresh.
>
> -tk
>
> On Sat, Nov 21, 2020 at 12:27 AM GBW  wrote:
>
>> Recently the battery in my outside sensor (TE923 Nexus) providing data 
>> named 'outTemp' gave up. This then appears to have caused the evaluation of 
>> this value outTemp< 3.0 in alarm expression (error:  '<' not supported 
>> between instances of 'NoneType' and 'float' Exiting) to fail and no further 
>> pages were published. I disabled the alarm and restarted, but then at the 
>> next hourly publication, the 'seasons' skins was used, but with a mixture 
>> of images, some as in that skin, others from my 'standard' skin which was 
>> still enabled. Naturally I have now replaced the battery. All is fine but, 
>> how can I prevent that happening again?[image: Screen Shot 11-20-20 at 
>> 09.08 AM.PNG]
>> [image: Screen Shot 11-20-20 at 05.15 PM.PNG] 
>>
>> -- 
>> 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/7557e9b2-6e5f-4ec7-829b-d962604eb763n%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/3ec5d13f-0863-49ef-9135-ca0b4f095b67n%40googlegroups.com.

[weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

[John Burricelli]

I am doing something similar

What I did was run that under www-data user.  First I had to change the 
shell in /etc/passwd to look like this.

www-data:x:1028:33:www-data:/var/www:/bin/bash

once that is done you can sudo su - www-data and add the cron entry.

Another way would be to add the pi user to the www-data group and mess with 
the directory permissions.

On Sunday, November 22, 2020 at 9:06:21 AM UTC-5 Rich Strle wrote:

> My copy of weewx is running on a Raspberry Pi. I am trying to get an image 
> from a webcam on my local network using wget, resizing the image using 
> imagemagick, then put it in the /var/www/html/weewx/ folder so it will get 
> uploaded to my web host.
>
> wget --user=user --password=user  
> http://192.168.254.33/jpg/image.jpg?size=3 -O/var/www/html/weewx/image.jpg
>
> I get a Permission denied error.
>
> From there my plan was to use imagick to reduced the size of the file and 
> include the image in the upload.
>
> I as able to put this in a bash script and run a cron job to do this 
> process to my /home/pi/Pictures/image.jpg folder but I can''t figure out 
> how to copy the file to the html/weewx directory.
>
> If there is a better way to do what I'm trying to accomplish I'm willing 
> to try that.
>
> 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/a8a3f9c1-d971-4b7d-9952-283f5c4a6ebbn%40googlegroups.com.

Re: [weewx-user] failed outTemp crashes alarm and "standard" skin

[Tom Keffer]

1. Depends on what you want. If you just want to keep the program from
crashing when outTemp is None, you could use

outTemp is not None and outTemp < 3


3. There's no magic here. If you enable a skin, it will get processed. If
you don't, it won't. There is no "default" skin. Look in [StdReport]. It's
possible you have more than one skin enabled and they are overwriting each
other.

On Sun, Nov 22, 2020 at 6:11 AM GBW  wrote:

> 1. Checking for a None value checks that there is a connection, I presume,
> so could I not get false frost alarms? Is it not possible to stop weewx
> crashing completely when "outTemp" is None (as I noticed in the loop)? I
> don't recall that happening before; there was just a gap in the graph,
> which prompted me to change the battery. Should I try the multiple alarm
> example too or are these exclusive under [Alarm]?
> 2. I notice the loop does report batteryStatus for the sensors, but I have
> never noticed any change to the reported (binary) value. I will try the
> suggested lowBattery module too, thanks.
> 3. Before replacing the battery, I first disabled Alarm resulting in the
> mixed report. The report publication reverted fully to my enabled
> "Standard" skin only after I had renewed the battery and rebooted, which
> suggests to me that alone the missing connection caused weewx to use the
> wrong skin until the fault was cleared. That never happened before (as
> there was no other default skin), which suggests to me that any error in
> the functioning of the "Standard" skin enables the default "Seasons" skin.
> Is that intended?
>
> tke...@gmail.com schrieb am Samstag, 21. November 2020 um 13:25:18 UTC+1:
>
>> How to prevent what happening again? The TypeError? If so, use an
>> expression such as
>>
>> outTemp is None or outTemp < 3.0
>>
>>
>> Or, do you mean dealing with a bad battery? If so, if the TE923 emits a
>> battery status, use the "lowBattery" module in the examples subdirectory to
>> sense a bad battery.
>>
>> Or, do you mean the mix of image types? You did not provide any
>> information about your report configuration, but if you changed report
>> types, then got an error, I can see that you'd end up with a mix of image
>> types. Try deleting everything in the HTML directory. They will all be
>> recreated afresh.
>>
>> -tk
>>
>> On Sat, Nov 21, 2020 at 12:27 AM GBW  wrote:
>>
>>> Recently the battery in my outside sensor (TE923 Nexus) providing data
>>> named 'outTemp' gave up. This then appears to have caused the evaluation of
>>> this value outTemp< 3.0 in alarm expression (error:  '<' not supported
>>> between instances of 'NoneType' and 'float' Exiting) to fail and no further
>>> pages were published. I disabled the alarm and restarted, but then at the
>>> next hourly publication, the 'seasons' skins was used, but with a mixture
>>> of images, some as in that skin, others from my 'standard' skin which was
>>> still enabled. Naturally I have now replaced the battery. All is fine but,
>>> how can I prevent that happening again?[image: Screen Shot 11-20-20 at
>>> 09.08 AM.PNG]
>>> [image: Screen Shot 11-20-20 at 05.15 PM.PNG]
>>>
>>> --
>>> 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/7557e9b2-6e5f-4ec7-829b-d962604eb763n%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/3ec5d13f-0863-49ef-9135-ca0b4f095b67n%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/CAPq0zEBOCAV3uas029fLtfWoU%2Bx8iRN1ONd5DF06DO6R_6GzCw%40mail.gmail.com.

[weewx-user] Installing WH23xx driver

[harri....@gmail.com]

Hi,
reinstalling the weewx on a Raspberry Pi 1B is not running at all. 
Following all guide lines for installing weewx on an Debian based linux as 
well as Matthew Wall´s guide line on Github - it is just not working. 
One point I am puzzled is that the driver WH23xx is not presented in the 
driver menue shown in wee_config. In weewx.con there is not section for 
WH23xx. Unfortuantely I lost the config file of my older installation.
OS = Raspian OS lite
Python 3.7

Some advice?
Greetings
Harry

-- 
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/0eead838-2b3e-48c6-9e2f-5ccce2c0569an%40googlegroups.com.

[weewx-user] CheetahGenerator - Using multiple tags in one statement?

[Jared]

Hi,

I'm trying to create a table of celestial objects with almanac data.  I 
want to use a for loop to create the table based on an array of chosen 
objects, but it doesn't like how I'm using the tags for some reason.

As an example, I have the following in my template:

#set planets = ['Mercury', 'Venus', 'Mars']

#for planet in planets
  
$planet
$almanac.$planet.rise
$almanac.$planet.transit
$almanac.$planet.set
$almanac.$planet.az
$almanac.$planet.alt
$almanac.$planet.ra
$almanac.$planet.dec
$almanac.$planet.mag
  
#end for

The table prints the planet name as expected, but all the data cells are 
printing with .$planet.rise .$planet.set and so on.

How can I get the CheetahGenerator to use both tags?

-- 
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/05f369da-a262-4913-aeed-0f74698db33bn%40googlegroups.com.

[weewx-user] Re: CheetahGenerator - Using multiple tags in one statement?

[Jared]

I should add that the almanac setup is working fine otherwise.  If I do 
something like $almanac.jupiter.rise, I get the data as expected.  I just 
wanted to keep my post concise :)

On Sunday, November 22, 2020 at 11:23:02 AM UTC-5 Jared wrote:

>
> Hi,
>
> I'm trying to create a table of celestial objects with almanac data.  I 
> want to use a for loop to create the table based on an array of chosen 
> objects, but it doesn't like how I'm using the tags for some reason.
>
> As an example, I have the following in my template:
>
> #set planets = ['Mercury', 'Venus', 'Mars']
>
> #for planet in planets
>   
> $planet
> $almanac.$planet.rise
> $almanac.$planet.transit
> $almanac.$planet.set
> $almanac.$planet.az
> $almanac.$planet.alt
> $almanac.$planet.ra
> $almanac.$planet.dec
> $almanac.$planet.mag
>   
> #end for
>
> The table prints the planet name as expected, but all the data cells are 
> printing with .$planet.rise .$planet.set and so on.
>
> How can I get the CheetahGenerator to use both tags?
>
>

-- 
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/103a4b70-a4a2-4415-b966-e0d106a1ffd3n%40googlegroups.com.

[weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

[Rich Strle]

Thank you John. I have more questions. I'll try and be specific so the next 
person who wants to grab an image, resize it, and include it in the ftp 
process can go it easier.

Looking at my passwrd file I see: 
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin

Would I remove the /nologin?

Can you explain this please? "once that is done you can sudo su - www-data 
and add the cron entry."

My bigger question is, where did weewx set permissions for itself? Does 
that happen in the install process?
On Sunday, November 22, 2020 at 8:18:11 AM UTC-6 john.bu...@gmail.com wrote:

> I am doing something similar
>
> What I did was run that under www-data user.  First I had to change the 
> shell in /etc/passwd to look like this.
>
> www-data:x:1028:33:www-data:/var/www:/bin/bash
>
> once that is done you can sudo su - www-data and add the cron entry.
>
> Another way would be to add the pi user to the www-data group and mess 
> with the directory permissions.
>
> On Sunday, November 22, 2020 at 9:06:21 AM UTC-5 Rich Strle wrote:
>
>> My copy of weewx is running on a Raspberry Pi. I am trying to get an 
>> image from a webcam on my local network using wget, resizing the image 
>> using imagemagick, then put it in the /var/www/html/weewx/ folder so it 
>> will get uploaded to my web host.
>>
>> wget --user=user --password=user  
>> http://192.168.254.33/jpg/image.jpg?size=3 
>> -O/var/www/html/weewx/image.jpg
>>
>> I get a Permission denied error.
>>
>> From there my plan was to use imagick to reduced the size of the file and 
>> include the image in the upload.
>>
>> I as able to put this in a bash script and run a cron job to do this 
>> process to my /home/pi/Pictures/image.jpg folder but I can''t figure out 
>> how to copy the file to the html/weewx directory.
>>
>> If there is a better way to do what I'm trying to accomplish I'm willing 
>> to try that.
>>
>> 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/4a1b1452-f1f6-4c01-8cb2-c0955965168bn%40googlegroups.com.

Re: [weewx-user] Re: CheetahGenerator - Using multiple tags in one statement?

[Tom Keffer]

You're very close. The problem is that an expression like
$almanac.$planet.rise is evaluated when the template is *compiled* not run.
So, you need to defer evaluation of the attribute $planet. Try this (NOT
TESTED):

#set planets = ['Mercury', 'Venus', 'Mars']

#for planet in planets
  
$planet
$getattr($almanac, $planet).rise
$getattr($almanac, $planet).transit
$getattr($almanac, $planet).set
$getattr($almanac, $planet).az
$getattr($almanac, $planet).alt
$getattr($almanac, $planet).ra
$getattr($almanac, $planet).dec
$getattr($almanac, $planet).mag
  
#end for



On Sun, Nov 22, 2020 at 8:35 AM Jared  wrote:

> I should add that the almanac setup is working fine otherwise.  If I do
> something like $almanac.jupiter.rise, I get the data as expected.  I just
> wanted to keep my post concise :)
>
> On Sunday, November 22, 2020 at 11:23:02 AM UTC-5 Jared wrote:
>
>>
>> Hi,
>>
>> I'm trying to create a table of celestial objects with almanac data.  I
>> want to use a for loop to create the table based on an array of chosen
>> objects, but it doesn't like how I'm using the tags for some reason.
>>
>> As an example, I have the following in my template:
>>
>> #set planets = ['Mercury', 'Venus', 'Mars']
>>
>> #for planet in planets
>>   
>> $planet
>> $almanac.$planet.rise
>> $almanac.$planet.transit
>> $almanac.$planet.set
>> $almanac.$planet.az
>> $almanac.$planet.alt
>> $almanac.$planet.ra
>> $almanac.$planet.dec
>> $almanac.$planet.mag
>>   
>> #end for
>>
>> The table prints the planet name as expected, but all the data cells are
>> printing with .$planet.rise .$planet.set and so on.
>>
>> How can I get the CheetahGenerator to use both tags?
>>
>> --
> 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/103a4b70-a4a2-4415-b966-e0d106a1ffd3n%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/CAPq0zECNymvfar1nc6VsuwViL73%3DcFCjr2d4c8FqbAE39cS05Q%40mail.gmail.com.

Re: [weewx-user] Re: CheetahGenerator - Using multiple tags in one statement?

[Jared]

Beautiful, that worked perfectly, thanks Tom!
On Sunday, November 22, 2020 at 11:47:52 AM UTC-5 tke...@gmail.com wrote:

> You're very close. The problem is that an expression like 
> $almanac.$planet.rise is evaluated when the template is *compiled* not 
> run. So, you need to defer evaluation of the attribute $planet. Try this 
> (NOT TESTED):
>
> #set planets = ['Mercury', 'Venus', 'Mars']
>
> #for planet in planets
>   
> $planet
>
> $getattr($almanac, $planet).rise
> $getattr($almanac, $planet).transit
> $getattr($almanac, $planet).set
> $getattr($almanac, $planet).az
> $getattr($almanac, $planet).alt
> $getattr($almanac, $planet).ra
> $getattr($almanac, $planet).dec
> $getattr($almanac, $planet).mag
>   
> #end for
>
>
>
> On Sun, Nov 22, 2020 at 8:35 AM Jared  wrote:
>
>> I should add that the almanac setup is working fine otherwise.  If I do 
>> something like $almanac.jupiter.rise, I get the data as expected.  I 
>> just wanted to keep my post concise :)
>>
>> On Sunday, November 22, 2020 at 11:23:02 AM UTC-5 Jared wrote:
>>
>>>
>>> Hi,
>>>
>>> I'm trying to create a table of celestial objects with almanac data.  I 
>>> want to use a for loop to create the table based on an array of chosen 
>>> objects, but it doesn't like how I'm using the tags for some reason.
>>>
>>> As an example, I have the following in my template:
>>>
>>> #set planets = ['Mercury', 'Venus', 'Mars']
>>>
>>> #for planet in planets
>>>   
>>> $planet
>>> $almanac.$planet.rise
>>> $almanac.$planet.transit
>>> $almanac.$planet.set
>>> $almanac.$planet.az
>>> $almanac.$planet.alt
>>> $almanac.$planet.ra
>>> $almanac.$planet.dec
>>> $almanac.$planet.mag
>>>   
>>> #end for
>>>
>>> The table prints the planet name as expected, but all the data cells are 
>>> printing with .$planet.rise .$planet.set and so on.
>>>
>>> How can I get the CheetahGenerator to use both tags?
>>>
>>> -- 
>> 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/103a4b70-a4a2-4415-b966-e0d106a1ffd3n%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/1fcfbdb3-3110-435b-ab74-41f875a9e91an%40googlegroups.com.

[weewx-user] Re: Bresser 6in1

[Paul Eaton]

Hi Bob,
Just thought you might like to know your ws6in1 driver works just as well 
for the Bresser PC 5 in 1 station (Model No. 7002571). It uses the same 
console as the PC 6 in 1 station but a simpler sensor rig (no UV). I've had 
it running successfully on Lubuntu 18.04 and now on a Raspberry Pi 4b.
Regards, Paul
On Sunday, 8 November 2020 at 14:26:19 UTC pete...@gmail.com wrote:

> Thanks Bob, that worked.
>
> On Wednesday, 4 November 2020 at 18:38:30 UTC Bob Atchley wrote:
>
>> Hi Peter,
>>
>> I recently reinstalled weewx and the WS6in1 driver on a RaspberryPi 4 
>> (previously on a rPi 2) and hit the same problem
>> I solved it by installing the crcmod library via the apt command:
>>
>> $ sudo apt install python3-crcmod
>>
>> Not sure why the pip3 command didn't provide the needed files, this 
>> wasn't needed originally.
>>
>> I am in the process of updating the readme.txt to add this and focus on 
>> python3 installation.
>> As the driver seems stable I'm also going to up it to version 1.0 (but no 
>> code changes from 0.9 other than changing the version number)
>>
>> Hope this helps
>>
>> Bob
>>
>> On Wednesday, 4 November 2020 at 11:07:38 UTC pete...@gmail.com wrote:
>>
>>> Hi Bob, 
>>>
>>> Really appreciate your help building this driver.
>>>
>>> I have the Bresser 7002570 and have  just reinstalled my Pi but have run 
>>> into an issue.
>>>
>>> I followed the instruction using Python 3 and pip3, so "pip3 install 
>>> crcmod"
>>>
>>> After I enter "sudo wee_config --reconfigure" I complete the station 
>>> information then see the station options as follows:
>>>
>>> Installed drivers include:
>>> 0) ? (user.ws6in1) No module named 'crcmod'
>>>
>>>1. AcuRite (weewx.drivers.acurite)
>>>
>>> 
>>>
>>> After selecting 0 and entering the station information I receive the 
>>> following:
>>>
>>> Traceback (most recent call last):
>>>
>>> File "/usr/share/weewx/wee_config", line 123, in
>>> main()
>>> File "/usr/share/weewx/wee_config", line 117, in main
>>> config_mgr.run(args, options)
>>> File "/usr/share/weewx/weecfg/config.py", line 114, in run
>>> stn_info = self.get_stn_info(config_dict, options)
>>> File "/usr/share/weewx/weecfg/config.py", line 155, in get_stn_info
>>> stn_info.update(weecfg.prompt_for_driver_settings(driver, config_dict))
>>> File "/usr/share/weewx/weecfg/*init*.py", line 1685, in 
>>> prompt_for_driver_settings
>>> *import*(driver)
>>> File "/usr/share/weewx/user/ws6in1.py", line 369, in
>>> import crcmod
>>> ModuleNotFoundError: No module named 'crcmod'
>>>
>>> Any help gratefully received.
>>>
>>> Peter.
>>>
>>> On Thursday, 24 September 2020 at 07:45:31 UTC+1 Bob Atchley wrote:
>>>
 Hi Stéphane

 The following are identical:
 Youshiko YC9388
 Bresser PC 6 in 1
 Garni 935PC
 Ventus W835

 I think the Bresser model is the Bresser 7002570 - it should 
 specifically mention the PC data connection.  The WiFi version is not 
 compatible as the USB connection provides power only (no data).

 Hope this helps

 Bob



-- 
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/f97323b1-e875-4576-8cca-99d60e29db83n%40googlegroups.com.

[weewx-user] Re: Bresser 6in1

[Bob Atchley]

Thats a new one !  Thanks Paul.  Maybe I need to rename the driver, WS6in1 
doesn't quite fit any more.  Garni, Ventus and Youshiko (and probably 
others) will probably be selling similar 5 in 1 weather stations

Regards

Bob

-- 
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/19e3805e-4342-44d0-8c12-c94ef0e086bcn%40googlegroups.com.

[weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

[vince]

On Sunday, November 22, 2020 at 8:44:01 AM UTC-8 Rich Strle wrote:

> Looking at my passwrd file I see: 
> www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
> Would I remove the /nologin?
>
>
Please don't do that.

www-data is the owner of the web 'data' and your webserver process likely 
runs as that user.
The nologin there ensures that if anybody/anything breaks security on your 
webserver running process, then they still wouldn't be able to get a shell 
and install/run malware etc.

What you want to do is:

   - put all your processing in a script
   - run that script as the non-privileged user 'pi' and write to scratch 
   directories that pi can write to (/tmp or /var/tmp are likely places)
   - in your script, do the 'privileged' copy of the output file to the 
   /var/www/html directory by prefacing your 'cp' command ala 'sudo cp'
   - and you'll likely want to set the permissions on the file in 
   /var/www/html also with 'sudo chmod' 

(standard suggestion - if you're asking this you need to up your linux-fu a 
little - I always suggest looking at the free edx.org Linux Fundamentals 
course that literally a million folks have taken)

A simple script that grabs Google's logo image as an example would look 
something like:

   #!/bin/bash
  
 
UPSTREAM_URL="https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png";
   SCRATCH_FILE="/tmp/image.jpg"
   FINAL_OUTPUT="/var/www/html/image.jpg"

   # wget the file in quiet mode to a temporary location
   wget -q "${URL}" "${SCRATCH_FILE}"

   # copy it into place and fix up permissions via sudo
   sudo cp "${SCRATCH_FILE}" "${FINAL_OUTPUT}"
   sudo chown www-data "${FINAL_OUTPUT}"
   sudo chmod 644  "${FINAL_OUTPUT}"

This script did the right thing for me, FWIW.  You'll of course have to put 
in the right wget switches to grab your image from the camera, as well as 
doing any processing with ImageMagick etc. before you copy your image into 
the web tree, but this should give you a skeleton to start with that does 
the permission stuff...


-- 
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/ca47e7f4-cdd5-4989-92f1-6af8d1a154dan%40googlegroups.com.

[weewx-user] Re: Belchertown - showerswn error

[vince]

On Saturday, November 21, 2020 at 7:39:04 PM UTC-8 gert.a...@gmail.com 
wrote:

> weewx 4.2.0 and Belchertown skin version 1.2. 
>
> I have been running the system for months with no issues. Suddenly I get 
> this error with:
> "ERROR weewx.reportengine: Caught unrecoverable exception in generator 
> 'weewx.cheetahgenerator.CheetahGenerator'
> ERROR weewx.reportengine:  'showerswn' "
>
>
Are you sure you didn't somehow edit a file and drop a character someplace ?

Looking at the current Belchertown skin, I see no mention of "showerswn" in 
the code.

./skins/Belchertown/js/belchertown.js.tmpl:"showers": "rain",
./skins/Belchertown/js/belchertown.js.tmpl:"showersn": "rain",
./skins/Belchertown/js/belchertown.js.tmpl:"showersw": "rain",
./skins/Belchertown/js/belchertown.js.tmpl:"showersw": "rain",
./skins/Belchertown/js/belchertown.js.tmpl:"snowshowers": "snow",
./skins/Belchertown/js/belchertown.js.tmpl:"snowshowersn": "snow",
./skins/Belchertown/js/belchertown.js.tmpl:"snowshowersw": "snow",
./skins/Belchertown/js/belchertown.js.tmpl:"snowshowerswn": "snow",
./bin/user/belchertown.py:"showers": "rain",
./bin/user/belchertown.py:"showersn": "rain",
./bin/user/belchertown.py:"showersw": "rain",
./bin/user/belchertown.py:"snowshowers": "snow",
./bin/user/belchertown.py:"snowshowersn": "snow",
./bin/user/belchertown.py:"snowshowersw": "snow",
./bin/user/belchertown.py:"snowshowerswn": "snow",

You might want to check your installation to see if it matches.
 

-- 
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/bde79418-ab4f-4417-8b84-7cc15cc6add1n%40googlegroups.com.

Re: [weewx-user] Re: Copy webcam image to /var/www/html/weewx/image.jpg

[Rich Strle]

Thanks very much Vince.

I appreciate your advice on the Linux Fundamentals course.

Rich Strle
309-824-9213

On Sun, Nov 22, 2020 at 12:34 PM vince  wrote:
>
> On Sunday, November 22, 2020 at 8:44:01 AM UTC-8 Rich Strle wrote:
>>
>> Looking at my passwrd file I see: 
>> www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
>> Would I remove the /nologin?
>>
>
> Please don't do that.
>
> www-data is the owner of the web 'data' and your webserver process likely 
> runs as that user.
> The nologin there ensures that if anybody/anything breaks security on your 
> webserver running process, then they still wouldn't be able to get a shell 
> and install/run malware etc.
>
> What you want to do is:
>
> put all your processing in a script
> run that script as the non-privileged user 'pi' and write to scratch 
> directories that pi can write to (/tmp or /var/tmp are likely places)
> in your script, do the 'privileged' copy of the output file to the 
> /var/www/html directory by prefacing your 'cp' command ala 'sudo cp'
> and you'll likely want to set the permissions on the file in /var/www/html 
> also with 'sudo chmod'
>
> (standard suggestion - if you're asking this you need to up your linux-fu a 
> little - I always suggest looking at the free edx.org Linux Fundamentals 
> course that literally a million folks have taken)
>
> A simple script that grabs Google's logo image as an example would look 
> something like:
>
>#!/bin/bash
>
> UPSTREAM_URL="https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png";
>SCRATCH_FILE="/tmp/image.jpg"
>FINAL_OUTPUT="/var/www/html/image.jpg"
>
># wget the file in quiet mode to a temporary location
>wget -q "${URL}" "${SCRATCH_FILE}"
>
># copy it into place and fix up permissions via sudo
>sudo cp "${SCRATCH_FILE}" "${FINAL_OUTPUT}"
>sudo chown www-data "${FINAL_OUTPUT}"
>sudo chmod 644  "${FINAL_OUTPUT}"
>
> This script did the right thing for me, FWIW.  You'll of course have to put 
> in the right wget switches to grab your image from the camera, as well as 
> doing any processing with ImageMagick etc. before you copy your image into 
> the web tree, but this should give you a skeleton to start with that does the 
> permission stuff...
>
>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/979HfPDddwc/unsubscribe.
> To unsubscribe from this group and all its topics, 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/ca47e7f4-cdd5-4989-92f1-6af8d1a154dan%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/CAPdkeQBXV9E8ihWFxXc42W00zK5NX_G-LUANWgFujdzLdWZB0g%40mail.gmail.com.

[weewx-user] Re: Bresser 6in1

[Arend]

Hi Bob,

I found another brand that sells a 5-in-1 clone. But I think CCL 
Electronics is the original developer/manufacturer. They had the 6-in-1 on 
their website in the past, but can't find it anymore. I guess end of life 
production for our 6-in-1 model.

Logia 


CCL Electronics 

Regards, Arend

Op zondag 22 november 2020 om 19:29:05 UTC+1 schreef Bob Atchley:

> Thats a new one !  Thanks Paul.  Maybe I need to rename the driver, WS6in1 
> doesn't quite fit any more.  Garni, Ventus and Youshiko (and probably 
> others) will probably be selling similar 5 in 1 weather stations
>
> Regards
>
> Bob
>
>

-- 
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/9df54dcd-5558-480d-a06e-609cd0fe5215n%40googlegroups.com.

[weewx-user] Re: Belchertown - showerswn error

[gert.a...@gmail.com]

Hi Vince 

Thanks for looking.

My best guess is that 'showerswn' is missing from belchertown.py. If you 
look at belchertown.js.tmpl, you have  "showersw": "rain", twice, maybe it 
should be 'showerswn'. You have also 'snowshowerswn' 'snow'.

After a couple of hours the error disappeared, probably when the condition 
changes.I have now inserted the missing tag in belchertown.py and changed 
the tags in belchertown.js.tmp to:
"showersw": "rain",
 'showerswn": "rain",
to see if it makes any difference the next time the condition appears.

>From belchertown.js.tmpl:
"showers": "rain",
"showersn": "rain",
"showersw": "rain",
"showersw": "rain",
"sleet": "sleet",
"sleetn": "sleet",
"sleetsnow": "sleet",
"sleetsnown": "sleet",
"smoke": "fog",
"smoken": "fog",
"snow": "snow",
"snown": "snow",
"snoww": "snow",
"snowwn": "snow",
"snowshowers": "snow",
"snowshowersn": "snow",
"snowshowersw": "snow",
"snowshowerswn": "snow",

Gert

On Sunday, November 22, 2020 at 7:49:05 PM UTC+1 vince wrote:

> On Saturday, November 21, 2020 at 7:39:04 PM UTC-8 gert.a...@gmail.com 
> wrote:
>
>> weewx 4.2.0 and Belchertown skin version 1.2. 
>>
>> I have been running the system for months with no issues. Suddenly I get 
>> this error with:
>> "ERROR weewx.reportengine: Caught unrecoverable exception in generator 
>> 'weewx.cheetahgenerator.CheetahGenerator'
>> ERROR weewx.reportengine:  'showerswn' "
>>
>>
> Are you sure you didn't somehow edit a file and drop a character someplace 
> ?
>
> Looking at the current Belchertown skin, I see no mention of "showerswn" 
> in the code.
>
> ./skins/Belchertown/js/belchertown.js.tmpl:"showers": "rain",
> ./skins/Belchertown/js/belchertown.js.tmpl:"showersn": "rain",
> ./skins/Belchertown/js/belchertown.js.tmpl:"showersw": "rain",
> ./skins/Belchertown/js/belchertown.js.tmpl:"showersw": "rain",
> ./skins/Belchertown/js/belchertown.js.tmpl:"snowshowers": "snow",
> ./skins/Belchertown/js/belchertown.js.tmpl:"snowshowersn": "snow",
> ./skins/Belchertown/js/belchertown.js.tmpl:"snowshowersw": "snow",
> ./skins/Belchertown/js/belchertown.js.tmpl:"snowshowerswn": "snow",
> ./bin/user/belchertown.py:"showers": "rain",
> ./bin/user/belchertown.py:"showersn": "rain",
> ./bin/user/belchertown.py:"showersw": "rain",
> ./bin/user/belchertown.py:"snowshowers": "snow",
> ./bin/user/belchertown.py:"snowshowersn": "snow",
> ./bin/user/belchertown.py:"snowshowersw": "snow",
> ./bin/user/belchertown.py:"snowshowerswn": "snow",
>
> You might want to check your installation to see if it matches.
>  
>

-- 
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/6a133a9b-54f9-471e-80f8-91aa3eb63889n%40googlegroups.com.

[weewx-user] no luck, no progress on getting weewx on CentOS 7.9

[Rich Painter]

CentOS 7.9 64bit clean install
Directions on http://weewx.com/docs/redhat.htm don't result in a workable
weewx.
Note- those instructions do NOT have a step for wee_config --install
Starting weewx installation over from scratch
Below is a complete transcript. One IMPORTANT thing to notice is the
"installed drivers" output section seems to show there are a LOT of missing
driver components
ALL of these steps are 100% repeatable. Variants using "wee_config
--reconfigure" result in the SAME failures!
Anyone know who the creator of the rpm repo is??
Any help would be appreciated.
thanks
rich


Uninstall and try again:

- yum remove weewx

- rpm --import http://weewx.com/keys.html

- curl -s http://weewx.com/yum/weewx-el7.repo | sudo tee
/etc/yum.repos.d/weewx.repo
[weewx]
name=weewx
baseurl=http://weewx.com/yum/weewx/el7
enabled=1
gpgcheck=0

- yum install weewx
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirror.den01.meanservers.net
 * epel: mirror.oss.ou.edu
 * extras: mirror.den01.meanservers.net
 * updates: mirror.vcu.edu
weewx| 3.0 kB 00:00
Resolving Dependencies
--> Running transaction check
---> Package weewx.noarch 0:4.2.0-1.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved


 Package Arch Version Repository
Size

Installing:
 weewx   noarch   4.2.0-1.el7 weewx
1.3 M

Transaction Summary

Install  1 Package

Total download size: 1.3 M
Installed size: 4.8 M
Is this ok [y/d/N]:
Downloading packages:
weewx-4.2.0-1.el7.noarch.rpm   | 1.3 MB   00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : weewx-4.2.0-1.el7.noarch
1/1
Listing /usr/share/weewx ...
Listing /usr/share/weewx/schemas ...
Listing /usr/share/weewx/user ...
Listing /usr/share/weewx/weecfg ...
Listing /usr/share/weewx/weedb ...
Listing /usr/share/weewx/weeimport ...
Listing /usr/share/weewx/weeplot ...
Listing /usr/share/weewx/weeutil ...
Listing /usr/share/weewx/weewx ...
Listing /usr/share/weewx/weewx/drivers ...
Starting weewx (via systemctl):  [  OK  ]
  Verifying  : weewx-4.2.0-1.el7.noarch
1/1

Installed:
  weewx.noarch 0:4.2.0-1.el7

Complete!

# this next step is NOT in the instructions but elsewhere weewx is supposed
to be stopped before doing the config
# even so, leaving out this step does NOT change anything! The result of
the wee_config is the same failure
- service weewx stop

# Next Configure:
- cd /etc/weewx
- wee_config --debug --verbosity=3 --install
--output=weewx.conf --dist-config=weewx.conf.dist
Enter a brief description of the station, such as its location.  For
example:
Santa's Workshop, North Pole
description [My Little Town, Oregon]: Fremont Comm Site, Salida CO

Specify altitude, with units 'foot' or 'meter'.  For example:
35, foot
12, meter
altitude [700, foot]: 11000, foot

Specify latitude in decimal degrees, negative for south.
latitude [0.00]: 38.446630
Specify longitude in decimal degrees, negative for west.
longitude [0.00]: -106.010750

You can register your station on weewx.com, where it will be included
in a map. You will need a unique URL to identify your station (such as a
website, or WeatherUnderground link).
Include station in the station registry (y/n)? [n]: n

Indicate the preferred units for display: ['us', 'metric']
units [us]:

Installed drivers include:
  0) ?   (weewx.drivers.acurite)   No module named usb
  1) ?   (weewx.drivers.cc3000)No module named serial
  2) ?   (weewx.drivers.fousb) No module named usb
  3) Simulator   (weewx.drivers.simulator)
  4) ?   (weewx.drivers.te923) No module named usb
  5) ?   (weewx.drivers.ultimeter) No module named serial
  6) Vantage (weewx.drivers.vantage)
  7) ?   (weewx.drivers.wmr100)No module named usb
  8) ?   (weewx.drivers.wmr200)No module named usb
  9) ?   (weewx.drivers.wmr300)No module named usb
 10) ?   (weewx.drivers.wmr9x8)No module named serial
 11) WS1 (weewx.drivers.ws1)
 12) WS23xx  (weewx.drivers.ws23xx)
 13) ?   (weewx.drivers.ws28xx)No module named usb
choose a driver [3]: 5
Traceback (most recent call last):
  File "/usr/share/weewx/wee_config", line 123, in 
main()
  File "/usr/share/weewx/wee_config", line 117, in main
config_mgr.run(args, options)
  File "/usr/share/weewx/weecfg/config.py", line 114

[weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[vince]

On Sunday, November 22, 2020 at 1:11:15 PM UTC-8 paint...@gmail.com wrote:

> CentOS 7.9 64bit clean install
> Directions on http://weewx.com/docs/redhat.htm don't result in a workable 
> weewx.
> Note- those instructions do NOT have a step for wee_config --install
> Starting weewx installation over from scratch
> Below is a complete transcript. One IMPORTANT thing to notice is the 
> "installed drivers" output section seems to show there are a LOT of missing 
> driver components
> ALL of these steps are 100% repeatable. Variants using "wee_config 
> --reconfigure" result in the SAME failures!
> Anyone know who the creator of the rpm repo is??
> Any help would be appreciated.
>
>
The rpm comes from the weewx team.

Your 'no module named usb' and 'no module named serial' and the seemingly 
missing things are because you didn't have all the prerequisite python 
modules (rpms) installed.  This is a longstanding known thing that has 
bitten many people over the years.  You have to install the prerequisites. 

Unfortunately CentOS is weird a.  I did a lot of testing of this in the v4 
pre-release timeframe but did most of it using the setup.py (not rpm) 
method of installation.

 If you give me a couple hours I can probably do a quick test in a VM both 
ways to reverify vs. Centos-7.9
 

-- 
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/7f1b816d-8c81-4eb3-8f96-0939384711cdn%40googlegroups.com.

[weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[vince]

ok - tested fine on a current vagrant centos image
 
The rpm is fine - you just probably used the RedHat 8 (python3) 
instructions by mistake rather than the RedHat 7 (python2) instructions...

   sudo rpm --import http://weewx.com/keys.html
   sudo curl -s http://weewx.com/yum/weewx-el7.repo | sudo tee 
/etc/yum.repos.d/weewx.repo
   sudo yum install weewx -y

If you have previously picked the wrong repo, you might need a 'sudo yum 
clean all' before (re)running the above.

On Sunday, November 22, 2020 at 1:33:59 PM UTC-8 vince wrote:

> On Sunday, November 22, 2020 at 1:11:15 PM UTC-8 paint...@gmail.com wrote:
>
>> CentOS 7.9 64bit clean install
>> Directions on http://weewx.com/docs/redhat.htm don't result in a 
>> workable weewx.
>> Note- those instructions do NOT have a step for wee_config --install
>> Starting weewx installation over from scratch
>> Below is a complete transcript. One IMPORTANT thing to notice is the 
>> "installed drivers" output section seems to show there are a LOT of missing 
>> driver components
>> ALL of these steps are 100% repeatable. Variants using "wee_config 
>> --reconfigure" result in the SAME failures!
>> Anyone know who the creator of the rpm repo is??
>> Any help would be appreciated.
>>
>>
> The rpm comes from the weewx team.
>
> Your 'no module named usb' and 'no module named serial' and the seemingly 
> missing things are because you didn't have all the prerequisite python 
> modules (rpms) installed.  This is a longstanding known thing that has 
> bitten many people over the years.  You have to install the prerequisites. 
>
> Unfortunately CentOS is weird a.  I did a lot of testing of this in the v4 
> pre-release timeframe but did most of it using the setup.py (not rpm) 
> method of installation.
>
>  If you give me a couple hours I can probably do a quick test in a VM both 
> ways to reverify vs. Centos-7.9
>  
>

-- 
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/60ff2918-9a84-4de7-95ba-50c0e9ab7793n%40googlegroups.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[Rich Painter]

thanks Vince!

But I'm really confused... IF there are prerequisites then A)  they should
be bolted into the rpm process. that is what rpms are for and B) they
should be part of the WRITTEN instructions at the OFFICIAL weewx
http://weewx.com/docs/redhat.htm for rehat/centos distributions.

I take it from your response that this is clearly a well-known (to some)
weewx problem so why has not the fixes been written into the weewx
http://weewx.com/docs/redhat.htm ??

I'm pleased and excited that you have responded with hope. I'm brand new to
weewx but have used Ubuntu and CentOS for a very long time. I'm a 40-year C
developer but have never known python. I have not been able to get weewx to
run on either U20 or C7 !

thanks!
rich




On Sun, Nov 22, 2020 at 2:34 PM vince  wrote:

> On Sunday, November 22, 2020 at 1:11:15 PM UTC-8 paint...@gmail.com wrote:
>
>> CentOS 7.9 64bit clean install
>> Directions on http://weewx.com/docs/redhat.htm don't result in a
>> workable weewx.
>> Note- those instructions do NOT have a step for wee_config --install
>> Starting weewx installation over from scratch
>> Below is a complete transcript. One IMPORTANT thing to notice is the
>> "installed drivers" output section seems to show there are a LOT of missing
>> driver components
>> ALL of these steps are 100% repeatable. Variants using "wee_config
>> --reconfigure" result in the SAME failures!
>> Anyone know who the creator of the rpm repo is??
>> Any help would be appreciated.
>>
>>
> The rpm comes from the weewx team.
>
> Your 'no module named usb' and 'no module named serial' and the seemingly
> missing things are because you didn't have all the prerequisite python
> modules (rpms) installed.  This is a longstanding known thing that has
> bitten many people over the years.  You have to install the prerequisites.
>
> Unfortunately CentOS is weird a.  I did a lot of testing of this in the v4
> pre-release timeframe but did most of it using the setup.py (not rpm)
> method of installation.
>
>  If you give me a couple hours I can probably do a quick test in a VM both
> ways to reverify vs. Centos-7.9
>
>
> --
> 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/7f1b816d-8c81-4eb3-8f96-0939384711cdn%40googlegroups.com
> 
> .
>


-- 
Richard A. Painter, P.E. Retired

-- 
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/CABh4ZQhnEK_8sNNV9H6MLAo5-HsJLqx8%3DDKTut7aXbW_b27fTA%40mail.gmail.com.

[weewx-user] Re: Belchertown - showerswn error

[vince]

Pat always likes patches and pull requests, so open an issue on his github 
page and I'm sure he'll get to it as time permits...

-- 
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/0cecd284-b48f-47e8-a15f-ab2d36f1c024n%40googlegroups.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[Rich Painter]

Vince,

Nope. I have only ever used the correct version 7 repo I posted the
exact steps in my earlier request which you have restated here exactly
to what I did

Any other suggestions?

thanks
rich

On Sun, Nov 22, 2020 at 2:51 PM vince  wrote:

> ok - tested fine on a current vagrant centos image
>
> The rpm is fine - you just probably used the RedHat 8 (python3)
> instructions by mistake rather than the RedHat 7 (python2) instructions...
>
>sudo rpm --import http://weewx.com/keys.html
>sudo curl -s http://weewx.com/yum/weewx-el7.repo | sudo tee
> /etc/yum.repos.d/weewx.repo
>sudo yum install weewx -y
>
> If you have previously picked the wrong repo, you might need a 'sudo yum
> clean all' before (re)running the above.
>
> On Sunday, November 22, 2020 at 1:33:59 PM UTC-8 vince wrote:
>
>> On Sunday, November 22, 2020 at 1:11:15 PM UTC-8 paint...@gmail.com
>> wrote:
>>
>>> CentOS 7.9 64bit clean install
>>> Directions on http://weewx.com/docs/redhat.htm don't result in a
>>> workable weewx.
>>> Note- those instructions do NOT have a step for wee_config --install
>>> Starting weewx installation over from scratch
>>> Below is a complete transcript. One IMPORTANT thing to notice is the
>>> "installed drivers" output section seems to show there are a LOT of missing
>>> driver components
>>> ALL of these steps are 100% repeatable. Variants using "wee_config
>>> --reconfigure" result in the SAME failures!
>>> Anyone know who the creator of the rpm repo is??
>>> Any help would be appreciated.
>>>
>>>
>> The rpm comes from the weewx team.
>>
>> Your 'no module named usb' and 'no module named serial' and the seemingly
>> missing things are because you didn't have all the prerequisite python
>> modules (rpms) installed.  This is a longstanding known thing that has
>> bitten many people over the years.  You have to install the prerequisites.
>>
>> Unfortunately CentOS is weird a.  I did a lot of testing of this in the
>> v4 pre-release timeframe but did most of it using the setup.py (not rpm)
>> method of installation.
>>
>>  If you give me a couple hours I can probably do a quick test in a VM
>> both ways to reverify vs. Centos-7.9
>>
>>
> --
> 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/60ff2918-9a84-4de7-95ba-50c0e9ab7793n%40googlegroups.com
> 
> .
>


-- 
Richard A. Painter, P.E. Retired

-- 
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/CABh4ZQhzv91cTKx0HztrsfExDEeYZjOksUX%2B36jdOsp%2BZX7-LQ%40mail.gmail.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[bell...@gmail.com]

At the very top of that page I see this
Install pre-requisites
For Redhat 8:
sudo yum install epel-release 
sudo yum install python3-cheetah
For Redhat 7:
sudo pip install pyserial pyusb

On Sunday, 22 November 2020 at 16:51:46 UTC-5 paint...@gmail.com wrote:

> thanks Vince!
>
> But I'm really confused... IF there are prerequisites then A)  they should 
> be bolted into the rpm process. that is what rpms are for and B) they 
> should be part of the WRITTEN instructions at the OFFICIAL weewx 
> http://weewx.com/docs/redhat.htm for rehat/centos distributions.
>
> I take it from your response that this is clearly a well-known (to some) 
> weewx problem so why has not the fixes been written into the weewx 
> http://weewx.com/docs/redhat.htm ??
>
> I'm pleased and excited that you have responded with hope. I'm brand new 
> to weewx but have used Ubuntu and CentOS for a very long time. I'm a 
> 40-year C developer but have never known python. I have not been able to 
> get weewx to run on either U20 or C7 !
>
> thanks!
> rich
>
>
>
>
> On Sun, Nov 22, 2020 at 2:34 PM vince  wrote:
>
>> On Sunday, November 22, 2020 at 1:11:15 PM UTC-8 paint...@gmail.com 
>> wrote:
>>
>>> CentOS 7.9 64bit clean install
>>> Directions on http://weewx.com/docs/redhat.htm don't result in a 
>>> workable weewx.
>>> Note- those instructions do NOT have a step for wee_config --install
>>> Starting weewx installation over from scratch
>>> Below is a complete transcript. One IMPORTANT thing to notice is the 
>>> "installed drivers" output section seems to show there are a LOT of missing 
>>> driver components
>>> ALL of these steps are 100% repeatable. Variants using "wee_config 
>>> --reconfigure" result in the SAME failures!
>>> Anyone know who the creator of the rpm repo is??
>>> Any help would be appreciated.
>>>
>>>
>> The rpm comes from the weewx team.
>>
>> Your 'no module named usb' and 'no module named serial' and the seemingly 
>> missing things are because you didn't have all the prerequisite python 
>> modules (rpms) installed.  This is a longstanding known thing that has 
>> bitten many people over the years.  You have to install the prerequisites. 
>>
>> Unfortunately CentOS is weird a.  I did a lot of testing of this in the 
>> v4 pre-release timeframe but did most of it using the setup.py (not rpm) 
>> method of installation.
>>
>>  If you give me a couple hours I can probably do a quick test in a VM 
>> both ways to reverify vs. Centos-7.9
>>  
>>
>> -- 
>> 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/7f1b816d-8c81-4eb3-8f96-0939384711cdn%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Richard A. Painter, P.E. Retired
>
>
>

-- 
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/1bf910a5-2b25-4119-8d46-70b169101f89n%40googlegroups.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[Rich Painter]

Before posting anything I had already tried this
For Redhat 7:
sudo pip install pyserial pyusb

but CentOS 7.9 has no program pip !! so I had tried this:
[root@CRMG-Fremont weewx]# yum install pip
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirror.den01.meanservers.net
 * epel: mirror.oss.ou.edu
 * extras: mirror.den01.meanservers.net
 * updates: mirror.dal10.us.leaseweb.net
No package pip available.
Error: Nothing to do

So I assumed this was not a step for CentOS Obviously wrong.

What would the corresponding CentOS 7 program be for pip?

thanks
rich

On Sun, Nov 22, 2020 at 2:56 PM bell...@gmail.com 
wrote:

>
> At the very top of that page I see this
> Install pre-requisites
> For Redhat 8:
> sudo yum install epel-release
> sudo yum install python3-cheetah
> For Redhat 7:
> sudo pip install pyserial pyusb
>
> On Sunday, 22 November 2020 at 16:51:46 UTC-5 paint...@gmail.com wrote:
>
>> thanks Vince!
>>
>> But I'm really confused... IF there are prerequisites then A)  they
>> should be bolted into the rpm process. that is what rpms are for and B)
>> they should be part of the WRITTEN instructions at the OFFICIAL weewx
>> http://weewx.com/docs/redhat.htm for rehat/centos distributions.
>>
>> I take it from your response that this is clearly a well-known (to some)
>> weewx problem so why has not the fixes been written into the weewx
>> http://weewx.com/docs/redhat.htm ??
>>
>> I'm pleased and excited that you have responded with hope. I'm brand new
>> to weewx but have used Ubuntu and CentOS for a very long time. I'm a
>> 40-year C developer but have never known python. I have not been able to
>> get weewx to run on either U20 or C7 !
>>
>> thanks!
>> rich
>>
>>
>>
>>
>> On Sun, Nov 22, 2020 at 2:34 PM vince  wrote:
>>
>>> On Sunday, November 22, 2020 at 1:11:15 PM UTC-8 paint...@gmail.com
>>> wrote:
>>>
 CentOS 7.9 64bit clean install
 Directions on http://weewx.com/docs/redhat.htm don't result in a
 workable weewx.
 Note- those instructions do NOT have a step for wee_config --install
 Starting weewx installation over from scratch
 Below is a complete transcript. One IMPORTANT thing to notice is the
 "installed drivers" output section seems to show there are a LOT of missing
 driver components
 ALL of these steps are 100% repeatable. Variants using "wee_config
 --reconfigure" result in the SAME failures!
 Anyone know who the creator of the rpm repo is??
 Any help would be appreciated.


>>> The rpm comes from the weewx team.
>>>
>>> Your 'no module named usb' and 'no module named serial' and the
>>> seemingly missing things are because you didn't have all the prerequisite
>>> python modules (rpms) installed.  This is a longstanding known thing that
>>> has bitten many people over the years.  You have to install the
>>> prerequisites.
>>>
>>> Unfortunately CentOS is weird a.  I did a lot of testing of this in the
>>> v4 pre-release timeframe but did most of it using the setup.py (not rpm)
>>> method of installation.
>>>
>>>  If you give me a couple hours I can probably do a quick test in a VM
>>> both ways to reverify vs. Centos-7.9
>>>
>>>
>>> --
>>> 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/7f1b816d-8c81-4eb3-8f96-0939384711cdn%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Richard A. Painter, P.E. Retired
>>
>>
>> --
> 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/1bf910a5-2b25-4119-8d46-70b169101f89n%40googlegroups.com
> 
> .
>


-- 
Richard A. Painter, P.E. Retired

-- 
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/CABh4ZQhqb47C3AH_uqfEgiKuGPLGvzjYBQn%2Bb3r%2BfWQupfJCXA%40mail.gmail.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[vince]

What's going on is CentOS-7 is weird in general and especially for 
python-related things.

You need to get the pyserial and pyusb and  (optional) python2-pip rpms 
from the EPEL repository.
They are not bundled with CentOS-7 in the os's default repositories. 
 They're extras.

   - sudo yum install epel-release
   - sudo yum install -y pyserial pyusb
   - sudo yum install -y python2-pip

CentOS also names things oddly, and sometimes you need to figure it out via 
 'yum search whatever' 

If you install the pyserial and pyusb corequisites, then wee_config will 
look right.
Installing pip is optional.

Now as for why the weewx rpms don't do this, remember that not all 
RHEL-based operating systems are the same, and our friends at RedHat make 
fascinatingly odd decisions all the time that result in trauma for their 
users.  We can't always explain why it's different or why bundling of 
things change massively sometimes (example - the repo structure in RHEL-8 
is a train wreck).

Sometimes you just gotta deal with craziness from upstream...

-- 
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/49ff6c69-9813-49b3-bb93-f776b5ba80cfn%40googlegroups.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[Rich Painter]

Vince,
roger that.
I had at the start enable the epel-release stuff as part of the CentOS 7.9
install. I have always included the epel in all centos installations.

The pip thing threw me since I never heard of it and it failed to install
when I tried.

Just before you replied with this, I finally after being lead to this point
tried:
yum install pyserial pyusb

and then the wee_config works!

For some reason I didnt need to do the python2-pip likely since centos
doesnt have pip at all...

I have added these steps to my procedure! I hope others can be helped by
this.

thanks
rich

On Sun, Nov 22, 2020 at 3:58 PM vince  wrote:

> What's going on is CentOS-7 is weird in general and especially for
> python-related things.
>
> You need to get the pyserial and pyusb and  (optional) python2-pip rpms
> from the EPEL repository.
> They are not bundled with CentOS-7 in the os's default repositories.
> They're extras.
>
>- sudo yum install epel-release
>- sudo yum install -y pyserial pyusb
>- sudo yum install -y python2-pip
>
> CentOS also names things oddly, and sometimes you need to figure it out
> via  'yum search whatever'
>
> If you install the pyserial and pyusb corequisites, then wee_config will
> look right.
> Installing pip is optional.
>
> Now as for why the weewx rpms don't do this, remember that not all
> RHEL-based operating systems are the same, and our friends at RedHat make
> fascinatingly odd decisions all the time that result in trauma for their
> users.  We can't always explain why it's different or why bundling of
> things change massively sometimes (example - the repo structure in RHEL-8
> is a train wreck).
>
> Sometimes you just gotta deal with craziness from upstream...
>
> --
> 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/49ff6c69-9813-49b3-bb93-f776b5ba80cfn%40googlegroups.com
> 
> .
>


-- 
Richard A. Painter, P.E. Retired

-- 
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/CABh4ZQiNpE0EMrNdGgB57jmGt%2BqaTrcLu32fGk0zSPbYTAE0Ew%40mail.gmail.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[vince]

On Sunday, November 22, 2020 at 4:05:08 PM UTC-8 paint...@gmail.com wrote:

> For some reason I didnt need to do the python2-pip likely since centos 
> doesnt have pip at all...
>
>
You didn't need to install pip because it's optional for weewx.  If you dig 
a bit deeper you'll see you only need it when there's something python that 
isn't packaged in a rpm for your os version.
 
There's no rhyme or reason why RedHat did what they did re: python, or at 
least none that I've ever seen.You basically always need EPEL on rh-7 
based os's.  Things are a bit better with rh-8 based systems in that 
regard, but rh8 has some other nuances that bite some people.

FWIW if it was me setting up a clean centos system, I'd use 8 just to get 
it over with and get more recent software...but 7 will keep working til 
2024 when it goes end of life.
 

-- 
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/839fc6d3-8851-42b4-bd7f-2c490532dbebn%40googlegroups.com.

Re: [weewx-user] Re: no luck, no progress on getting weewx on CentOS 7.9

[Rich Painter]

Vince,

i understand.

Long story... the CentOS 7 is required for an ICOM radio software called
D-STAR ver 3. CO 8 will not work. So, if one is installing new for a system
with D-STAR then CO7 it is regardless of the age. The prior ICOM release
ver 2 required CO 5 !! We STILL have some of these running !!!

Thanks
rich

On Sun, Nov 22, 2020 at 6:02 PM vince  wrote:

>
>
> On Sunday, November 22, 2020 at 4:05:08 PM UTC-8 paint...@gmail.com wrote:
>
>> For some reason I didnt need to do the python2-pip likely since centos
>> doesnt have pip at all...
>>
>>
> You didn't need to install pip because it's optional for weewx.  If you
> dig a bit deeper you'll see you only need it when there's something python
> that isn't packaged in a rpm for your os version.
>
> There's no rhyme or reason why RedHat did what they did re: python, or at
> least none that I've ever seen.You basically always need EPEL on rh-7
> based os's.  Things are a bit better with rh-8 based systems in that
> regard, but rh8 has some other nuances that bite some people.
>
> FWIW if it was me setting up a clean centos system, I'd use 8 just to get
> it over with and get more recent software...but 7 will keep working til
> 2024 when it goes end of life.
>
>
> --
> 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/839fc6d3-8851-42b4-bd7f-2c490532dbebn%40googlegroups.com
> 
> .
>


-- 
Richard A. Painter, P.E. Retired

-- 
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/CABh4ZQjp_mYT0t1nVWy8WqQVRbyvoY0W%2BafOE81FtjugSdOoWQ%40mail.gmail.com.

[weewx-user] Re: Webserver showing default Apache page instead of weewx

[Jimmy Kirk]

OK thanks guys... I'm a bit of a linux noob so I am not sure how to do 
symbolic links. Therefore I opted to change the directory where the web 
pages are living, to:
HTML_ROOT = /var/www/html - This fixed it... but now I have another issue, 
undoubtedly related to the Vantage data corruption issue. I now get the 
correct web server, but the web page shows a date from two days ago and 
does not update. When I try to run wee_device commands I get a permissions 
issue on the USB port. PermissionError: [Errno 13] Permission denied: 
'/dev/ttyUSB0'  How can I get permissions on the USB port? (Remember Linux 
noob)... I can start a new topic about this if necessary.

On Saturday, November 21, 2020 at 3:53:05 PM UTC-6 Greg from Oz wrote:

> I think you should put the weewx.conf into /etc/apache2/sites-available/
> The run sudo a2ensite (this will enable the site)
> Then run: sudo systemctl restart apache2.service
>
> I don't know what system you are running apache on but the above should 
> work with Ubuntu (debian)
>
>
> On Sunday, 22 November 2020 at 06:47:10 UTC+11 vince wrote:
>
>> You always want to look at your logs for both syslog and apache for the 
>> gory details.
>>
>> There are a couple alternate ways to get there
>>
>>- edit weewx.conf to tell it where to write its html to
>>   - at the top of the [[StandardReport]] section in weewx.conf, edit 
>>   HTML_ROOT to point to /var/www/html which is where Apache thinks the 
>> web 
>>   root is (weewx restart required)
>>- or point the apache DOCROOT at weewx's tree
>>   - rename /var/www/html and create a symlink pointing to 
>>   /home/weewx/public_html  (no apache or weewx restarts needed)
>>- or point the weewx's HTML_ROOT at apache's tree
>>   - rename /home/weewx/public_html and create a symlink pointing to 
>>   /var/www/html (weewx restart required)
>>
>> FWIW, I use the second method here but that's just how I chose to do it.
>>
>>

-- 
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/7eb74f8b-8f17-4584-babc-b7d4a30a8b17n%40googlegroups.com.

[weewx-user] Re: Webserver showing default Apache page instead of weewx

[Greg from Oz]

If you run the command and add sudo before the command then it will run as 
root.

 sudo wee_device

If you add the user to the dialout group then that user will have 
permission to use the USB without out having to run sudo.



On Monday, 23 November 2020 at 15:04:40 UTC+11 jd@gmail.com wrote:

> OK thanks guys... I'm a bit of a linux noob so I am not sure how to do 
> symbolic links. Therefore I opted to change the directory where the web 
> pages are living, to:
> HTML_ROOT = /var/www/html - This fixed it... but now I have another 
> issue, undoubtedly related to the Vantage data corruption issue. I now get 
> the correct web server, but the web page shows a date from two days ago and 
> does not update. When I try to run wee_device commands I get a permissions 
> issue on the USB port. PermissionError: [Errno 13] Permission denied: 
> '/dev/ttyUSB0'  How can I get permissions on the USB port? (Remember 
> Linux noob)... I can start a new topic about this if necessary.
>
> On Saturday, November 21, 2020 at 3:53:05 PM UTC-6 Greg from Oz wrote:
>
>> I think you should put the weewx.conf into /etc/apache2/sites-available/
>> The run sudo a2ensite (this will enable the site)
>> Then run: sudo systemctl restart apache2.service
>>
>> I don't know what system you are running apache on but the above should 
>> work with Ubuntu (debian)
>>
>>
>> On Sunday, 22 November 2020 at 06:47:10 UTC+11 vince wrote:
>>
>>> You always want to look at your logs for both syslog and apache for the 
>>> gory details.
>>>
>>> There are a couple alternate ways to get there
>>>
>>>- edit weewx.conf to tell it where to write its html to
>>>   - at the top of the [[StandardReport]] section in weewx.conf, 
>>>   edit HTML_ROOT to point to /var/www/html which is where Apache thinks 
>>> the 
>>>   web root is (weewx restart required)
>>>- or point the apache DOCROOT at weewx's tree
>>>   - rename /var/www/html and create a symlink pointing to 
>>>   /home/weewx/public_html  (no apache or weewx restarts needed)
>>>- or point the weewx's HTML_ROOT at apache's tree
>>>   - rename /home/weewx/public_html and create a symlink pointing to 
>>>   /var/www/html (weewx restart required)
>>>
>>> FWIW, I use the second method here but that's just how I chose to do it.
>>>
>>>

-- 
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/5883fe8c-e56e-427a-adbf-d73d146f9196n%40googlegroups.com.

[weewx-user] Re: Webserver showing default Apache page instead of weewx

[Jimmy Kirk]

Sorry Greg, should have mentioned that I already tried running it with 
sudo, with interesting results. Here's what I get, running without sudo, 
then with sudo...
. . .
weewx@weewx:~ $ wee_device --clear-memory
Using configuration file /home/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in 
open
self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
PermissionError: [Errno 13] Permission denied: '/dev/ttyUSB0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/weewx/bin/wee_device", line 78, in 
main()
  File "/home/weewx/bin/wee_device", line 74, in main
device.configure(config_dict)
  File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
self.do_options(options, parser, config_dict, not options.noprompt)
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 2056, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 512, in __init__
self.port.openPort()
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in openPort
self.serial_port = serial.Serial(self.port, self.baudrate, 
timeout=self.timeout)
  File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in 
__init__
self.open()
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in 
open
raise SerialException(msg.errno, "could not open port {}: 
{}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 13] could not open port 
/dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
. . .
weewx@weewx:~ $ sudo wee_device --clear-memory
[sudo] password for weewx:
sudo: wee_device: command not found

So how do I add the user to the dialout group? Is that like the sudoers 
group? (not sure how to do the sudoers group either).
On Sunday, November 22, 2020 at 10:36:15 PM UTC-6 Greg from Oz wrote:

> If you run the command and add sudo before the command then it will run as 
> root.
>
>  sudo wee_device
>
> If you add the user to the dialout group then that user will have 
> permission to use the USB without out having to run sudo.
>
>
>
> On Monday, 23 November 2020 at 15:04:40 UTC+11 jd@gmail.com wrote:
>
>> OK thanks guys... I'm a bit of a linux noob so I am not sure how to do 
>> symbolic links. Therefore I opted to change the directory where the web 
>> pages are living, to:
>> HTML_ROOT = /var/www/html - This fixed it... but now I have another 
>> issue, undoubtedly related to the Vantage data corruption issue. I now get 
>> the correct web server, but the web page shows a date from two days ago and 
>> does not update. When I try to run wee_device commands I get a permissions 
>> issue on the USB port. PermissionError: [Errno 13] Permission denied: 
>> '/dev/ttyUSB0'  How can I get permissions on the USB port? (Remember 
>> Linux noob)... I can start a new topic about this if necessary.
>>
>> On Saturday, November 21, 2020 at 3:53:05 PM UTC-6 Greg from Oz wrote:
>>
>>> I think you should put the weewx.conf into /etc/apache2/sites-available/
>>> The run sudo a2ensite (this will enable the site)
>>> Then run: sudo systemctl restart apache2.service
>>>
>>> I don't know what system you are running apache on but the above should 
>>> work with Ubuntu (debian)
>>>
>>>
>>> On Sunday, 22 November 2020 at 06:47:10 UTC+11 vince wrote:
>>>
 You always want to look at your logs for both syslog and apache for the 
 gory details.

 There are a couple alternate ways to get there

- edit weewx.conf to tell it where to write its html to
   - at the top of the [[StandardReport]] section in weewx.conf, 
   edit HTML_ROOT to point to /var/www/html which is where Apache 
 thinks the 
   web root is (weewx restart required)
- or point the apache DOCROOT at weewx's tree
   - rename /var/www/html and create a symlink pointing to 
   /home/weewx/public_html  (no apache or weewx restarts needed)
- or point the weewx's HTML_ROOT at apache's tree
   - rename /home/weewx/public_html and create a symlink pointing 
   to /var/www/html (weewx restart required)

 FWIW, I use the second method here but that's just how I chose to do it.



-- 
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/a7fa2529-5ce2-4b95-b5f3-9f37c1a248f2n%40googlegroups.com.

[weewx-user] Re: Webserver showing default Apache page instead of weewx

[Greg from Oz]

It is not like the sudoers. It is just a group.

Look here:
https://www.techrepublic.com/article/how-to-create-users-and-groups-in-linux-from-the-command-line/
It will show you how to add the group to the user.

If the sudo wee_device comes back with command not found then that means it 
is not in the path and then you will have to usr the absolute path to run 
the command.

E.G If the wee_device is in /home/weewx/bin then you would have to run:
sudo  /home/weewx/bin/wee_device



On Monday, 23 November 2020 at 15:59:15 UTC+11 jd@gmail.com wrote:

> Sorry Greg, should have mentioned that I already tried running it with 
> sudo, with interesting results. Here's what I get, running without sudo, 
> then with sudo...
> . . .
> weewx@weewx:~ $ wee_device --clear-memory
> Using configuration file /home/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, 
> in open
> self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | 
> os.O_NONBLOCK)
> PermissionError: [Errno 13] Permission denied: '/dev/ttyUSB0'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_device", line 78, in 
> main()
>   File "/home/weewx/bin/wee_device", line 74, in main
> device.configure(config_dict)
>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
> self.do_options(options, parser, config_dict, not options.noprompt)
>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 2056, in do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 512, in __init__
> self.port.openPort()
>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in openPort
> self.serial_port = serial.Serial(self.port, self.baudrate, 
> timeout=self.timeout)
>   File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in 
> __init__
> self.open()
>   File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, 
> in open
> raise SerialException(msg.errno, "could not open port {}: 
> {}".format(self._port, msg))
> serial.serialutil.SerialException: [Errno 13] could not open port 
> /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
> . . .
> weewx@weewx:~ $ sudo wee_device --clear-memory
> [sudo] password for weewx:
> sudo: wee_device: command not found
>
> So how do I add the user to the dialout group? Is that like the sudoers 
> group? (not sure how to do the sudoers group either).
> On Sunday, November 22, 2020 at 10:36:15 PM UTC-6 Greg from Oz wrote:
>
>> If you run the command and add sudo before the command then it will run 
>> as root.
>>
>>  sudo wee_device
>>
>> If you add the user to the dialout group then that user will have 
>> permission to use the USB without out having to run sudo.
>>
>>
>>
>> On Monday, 23 November 2020 at 15:04:40 UTC+11 jd@gmail.com wrote:
>>
>>> OK thanks guys... I'm a bit of a linux noob so I am not sure how to do 
>>> symbolic links. Therefore I opted to change the directory where the web 
>>> pages are living, to:
>>> HTML_ROOT = /var/www/html - This fixed it... but now I have another 
>>> issue, undoubtedly related to the Vantage data corruption issue. I now get 
>>> the correct web server, but the web page shows a date from two days ago and 
>>> does not update. When I try to run wee_device commands I get a permissions 
>>> issue on the USB port. PermissionError: [Errno 13] Permission denied: 
>>> '/dev/ttyUSB0'  How can I get permissions on the USB port? (Remember 
>>> Linux noob)... I can start a new topic about this if necessary.
>>>
>>> On Saturday, November 21, 2020 at 3:53:05 PM UTC-6 Greg from Oz wrote:
>>>
 I think you should put the weewx.conf into /etc/apache2/sites-available/
 The run sudo a2ensite (this will enable the site)
 Then run: sudo systemctl restart apache2.service

 I don't know what system you are running apache on but the above should 
 work with Ubuntu (debian)


 On Sunday, 22 November 2020 at 06:47:10 UTC+11 vince wrote:

> You always want to look at your logs for both syslog and apache for 
> the gory details.
>
> There are a couple alternate ways to get there
>
>- edit weewx.conf to tell it where to write its html to
>   - at the top of the [[StandardReport]] section in weewx.conf, 
>   edit HTML_ROOT to point to /var/www/html which is where Apache 
> thinks the 
>   web root is (weewx restart required)
>- or point the apache DOCROOT at weewx's tree
>   - rename /var/www/html and create a symlink pointing to 
>   /home/weewx/public_html  (no apache or weewx restarts needed)
>- or point the weewx's HTML_ROOT at apache's tree
>   - rename /home/weewx/public_html and create a sym