Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[Christian Gruber]

hello,

thank you for this information about schema and UDP.

i use a mikrotik rb4011igs, so i think this should be possible, i will look 
for a solution and post it here.

regards,
chris

mbat...@gmail.com schrieb am Sonntag, 21. Februar 2021 um 03:39:09 UTC+1:

> UDP broadcasts are not routed between subnets, so unless your weewx host 
> has a presence on the weatherlink hub's net, it won't "hear" the hub.
>
> There are a couple of ways (besides "multi-homing" the weewx box) to deal 
> with the problem. Ass u me ing your home firewall / router is a Linux box, 
> and that you have administrative control of it, one solution is to install 
> a UDP replicator (such as this one 
> ) on your home router.  
> Another method (same assumptions) is to use port forwarding, which is 
> described here 
> 
> .
>
> On Saturday, February 20, 2021 at 12:55:10 PM UTC-6 michael.s...@gmail.com 
> wrote:
>
>> should the pi and weatherlink live be on the same subnetwork, because i 
>>> dont get data
>>>
>>
>> Yes, to receive the live 2.5 second push updates (wind, rain) both 
>> devices must be on the same subnet. They work using UDP broadcasts. The 
>> "complete" data set (HTTP) doesn't technically require it, though I haven't 
>> tested whether the driver works fine if it never receives a push update (it 
>> should).
>>
>>
>> why should i switch to WLL schema, i loose specific data, when i dont do 
>>> it?
>>>
>>  
>> The following columns are added in the WLL schema:
>>
>>- dewpoint and heatindex for up to 9 sensors (default only for 2)
>>- wetbulb temperature
>>- THW and THSW index ("feels like" temperature)
>>- indoor heatindex 
>>- "rainCount": how often your rain sensor's spoon got tripped since 
>>the last update
>>- "rainCountRate": the current rate of spoon tripping
>>- "rainSize": the size of the rain sensor spoon *in inches *(as 
>>configured in the WLL app or the WeatherLink.com website)
>>
>> Additionally, daily summaries and units are configured for all new 
>> columns (except the last one).
>>
>>
>> regards, Michael
>>
>

-- 
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/e67d9997-1aa3-42bb-8206-37e69b5cc0cfn%40googlegroups.com.

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[mbat...@gmail.com]

UDP broadcasts are not routed between subnets, so unless your weewx host 
has a presence on the weatherlink hub's net, it won't "hear" the hub.

There are a couple of ways (besides "multi-homing" the weewx box) to deal 
with the problem. Ass u me ing your home firewall / router is a Linux box, 
and that you have administrative control of it, one solution is to install 
a UDP replicator (such as this one 
) on your home router.  
Another method (same assumptions) is to use port forwarding, which is 
described here 

.

On Saturday, February 20, 2021 at 12:55:10 PM UTC-6 michael.s...@gmail.com 
wrote:

> should the pi and weatherlink live be on the same subnetwork, because i 
>> dont get data
>>
>
> Yes, to receive the live 2.5 second push updates (wind, rain) both devices 
> must be on the same subnet. They work using UDP broadcasts. The "complete" 
> data set (HTTP) doesn't technically require it, though I haven't tested 
> whether the driver works fine if it never receives a push update (it 
> should).
>
>
> why should i switch to WLL schema, i loose specific data, when i dont do 
>> it?
>>
>  
> The following columns are added in the WLL schema:
>
>- dewpoint and heatindex for up to 9 sensors (default only for 2)
>- wetbulb temperature
>- THW and THSW index ("feels like" temperature)
>- indoor heatindex 
>- "rainCount": how often your rain sensor's spoon got tripped since 
>the last update
>- "rainCountRate": the current rate of spoon tripping
>- "rainSize": the size of the rain sensor spoon *in inches *(as 
>configured in the WLL app or the WeatherLink.com website)
>
> Additionally, daily summaries and units are configured for all new columns 
> (except the last one).
>
>
> regards, Michael
>

-- 
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/d8044162-1963-423d-9ce5-f39c214f3916n%40googlegroups.com.

Re: [weewx-user] Bootstrap skin update preview

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

In the meantime I've made some enhancements, bugfixes and styling 
improvements.
There is still some testing and documentation to be done, but we're getting 
closer, finishing this :)
Watch it live: 
https://www.kainzbauer.net/weather/Rif-Tempest/index.html
Try it:
https://github.com/brewster76/fuzzy-archer/tree/liveCharts
hobbyl...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 19:08:12 
UTC+1:

> very good work! beautifull skin. looks geat on chromium 88 with arch linux
>
> Στις Πέμπτη, 4 Φεβρουαρίου 2021 στις 5:24:30 μ.μ. UTC+2, ο χρήστης 
> michael.k...@gmx.at έγραψε:
>
>> I didn't change anything in the meantime, so I don't know what caused the 
>> initial error. "Looks great" => thank you very much, hearing this from Mr. 
>> weewx himself, really is delightful :)
>>
>> I forget to mention: The charts and gauges are Apache eCharts. Almost 
>> infinite possibilities!
>> tke...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 13:33:20 
>> UTC+1:
>>
>>> Don't know what happened, but now it works for me with no errors.
>>>
>>> Looks great!
>>>
>>> On Wed, Feb 3, 2021 at 8:48 PM michael.k...@gmx.at  
>>> wrote:
>>>
 Hello Tom,

 The error with the /favicon.ico is a simple one: there is no such file. 
 The other errors I couldn't reproduce, even trying with different browser 
 on different computers and phones. Isn't weewxData.js there, when you try 
 to load it? It's referenced on line 144 of the HTML.
 What browser on what system are you using?
 I got it working with Windows: Firefox, Brave, Edge, Chrome, Raspbian 
 with Chromium, Android 10 Chrome, Brave, Firefox. Android 7.0 Chrome. I've 
 encountered some Problems with the connection to the MQTT broker while 
 using the companies VPN and and some weird rendering of the gauges an 
 images using the edge version 44, pre-chromium) browser that is installed 
 at the companies computer and no displaying of the gauges and charts with 
 the internet explorer (an there are no plans to get this working)
 tke...@gmail.com schrieb am Mittwoch, 3. Februar 2021 um 23:57:25 
 UTC+1:

> Hi, Michael.
>
> I got several errors when I tried to see your live version:
>
> Uncaught SyntaxError: Unexpected end of input
> site.js:1 Uncaught ReferenceError: weewxData is not defined
> at site.js:1
> gauges.js:3 Uncaught ReferenceError: weewxData is not defined
> at gauges.js:3
> charts.js:2 Uncaught ReferenceError: weewxData is not defined
> at charts.js:2
> /favicon.ico:1 Failed to load resource: the server responded with a 
> status of 404 (Not Found)
>
>
> On Wed, Feb 3, 2021 at 1:12 PM michael.k...@gmx.at <
> michael.k...@gmx.at> wrote:
>
>> A couple of weeks ago, I asked Nick, the author of the bootstrap 
>> skin, if he could help me taking his skin, that I am very fond of, to 
>> the 
>> next level. As a first step we developed an optional live view with 
>> browser 
>> rendered gauges and charts, using MQTT for the almost-real-time 
>> rendering. 
>> Everything is still under heavy development, but still, I think time has 
>> come to show a first preview. Whoever wants to check it out, this is the 
>> development branch:
>>
>> https://github.com/brewster76/fuzzy-archer/tree/liveCharts
>>
>> Be careful, not production ready!
>>
>> For those who want to see it in action:
>>
>> https://www.kainzbauer.net/weather/Rif-Tempest/live.html
>>
>> The Weatherflow Tempest is really great for such fancy 
>> almost-realtime sites with it's 3 second wind/windDir update interval.
>>
>> -- 
>> 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/bd8b0eb8-f803-43e9-9f7b-077dc4b79f1dn%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/9ad6d9d4-38d8-4503-ba91-a7adb5652c13n%40googlegroups.com
  
 
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop 

[weewx-user] Re: BaraniDesign MeteoHelix MeteoWind MeteoRain through allMETEO

[Toby]

Hello Bendict,
I also has a MeteoHelix Pro.. Do you have any solution to collect your 
values and see on weewx?

Regards, Toby.

Benedict schrieb am Donnerstag, 26. November 2020 um 16:56:24 UTC+1:

> Oh, before I forget, they have an Open standards structure, so even for 
> developers it should not be too hard to parse its device data;
> https://www.baranidesign.com/meteohelix-message-decoder
> On Thursday, November 26, 2020 at 4:25:18 PM UTC+1 Benedict wrote:
>
>> Not sure if this should be in the dev or in user group. Depends, I guess..
>> I have my own debian server running weewx (currently parsing netatmo 
>> data) and I want it to collect and show data from my barani Pro IoT 
>> devices, which are not in the supported hardware list, and frankly I have 
>> no idea if there are brands that use similar protocols/output, and use the 
>> same sensor descriptors.
>>
>> My barani devices upload data through LoRaWAN via TheThingsNetwork to a 
>> site called allMETEO.com. Here's a couple screenshots so you can see; 
>> https://afluisterland.nl/img/barani/
>> So, as you can see at the allmeteo site I can forward using FTP or HTTP, 
>> in a txt file to a ftp server for example, would that be an option? Can 
>> weewx monitor more than one file or an entire folder for new content and 
>> then parse its values?
>>
>> Another option would be to interface directly through TTN, is there any 
>> of you users that uses TheThingsNetwork to get data visualized on a weewx 
>> site?
>>
>> Thanks in advance for any and all info,
>>
>> Ben
>>
>

-- 
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/28257d38-0c70-4dc3-b650-41c6aad926a4n%40googlegroups.com.

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[Michael Schantl]

>
> should the pi and weatherlink live be on the same subnetwork, because i 
> dont get data
>

Yes, to receive the live 2.5 second push updates (wind, rain) both devices 
must be on the same subnet. They work using UDP broadcasts. The "complete" 
data set (HTTP) doesn't technically require it, though I haven't tested 
whether the driver works fine if it never receives a push update (it 
should).


why should i switch to WLL schema, i loose specific data, when i dont do it?
>
 
The following columns are added in the WLL schema:

   - dewpoint and heatindex for up to 9 sensors (default only for 2)
   - wetbulb temperature
   - THW and THSW index ("feels like" temperature)
   - indoor heatindex 
   - "rainCount": how often your rain sensor's spoon got tripped since the 
   last update
   - "rainCountRate": the current rate of spoon tripping
   - "rainSize": the size of the rain sensor spoon *in inches *(as 
   configured in the WLL app or the WeatherLink.com website)

Additionally, daily summaries and units are configured for all new columns 
(except the last one).


regards, Michael

-- 
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/fe5373ca-f949-4c80-9c1a-c6cf3aa81f25n%40googlegroups.com.

[weewx-user] Re: Grünlandtemperatursumme (GTS), a kind of Growing Degree Days

[Karen K]

The extension provides the following observation types to use in skins and 
diagrams:
- *GTS*: the value of "Grünlandtemperatursumme" itself (example tag: 
$current.GTS)
- *GTSdate*: the date when the GTS value exceeds 200, which is considered 
the beginning of real spring (example tag: $day.GTSdate.last)
- *utcoffsetLMT*: offfset of the local mean time (Ortszeit) at the 
station's location
- *LMTtime*: a string showing the local mean time (Ortszeit) at the 
station's location (can only be used with ".raw", example tag: 
$current.LMTtime.raw)

-- 
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/815c5d63-4bf2-41a5-96cd-6acd727f46a5n%40googlegroups.com.

[weewx-user] Grünlandtemperatursumme (GTS), a kind of Growing Degree Days

[Karen K]

Two of the weather networks I upload data to *) requested to send the 
"Grünlandtemperatursumme" (GTS), a kind of growing degree days, that is 
used in Europe, at least in Germany.

As the value was not provided by WeeWX standard, I tried to write an XType 
extension for that. And now, there is a first result. You find it there:

https://github.com/roe-dl/weewx-GTS


*) Wetternetz Sachsen 
 and 
Regionalwetter 
Sachsen-Anhalt  to be 
exact

-- 
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/a3b76a0b-d8c3-4a84-9ad4-a0ad715d2005n%40googlegroups.com.

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[Christian Gruber]

hello,

thank you, i reinstalled it and it's running now :)

i have a few additional questions:

-) should the pi and weatherlink live be on the same subnetwork, because i 
dont get data

-) why should i switch to WLL schema, i loose specific data, when i dont do 
it?

regards,
chris



tke...@gmail.com schrieb am Samstag, 20. Februar 2021 um 14:16:46 UTC+1:

> You do not need to uninstall weewx first. 
>
> Just follow the install instructions, but use the python3 version instead:
>
>
> *wget -qO - https://weewx.com/apt/weewx- 
> python3.list | sudo tee 
> /etc/apt/sources.list.d/weewx.list*
>
>
> *sudo apt-get updatesudo apt-get install weewx*
>
>
>
> On Sat, Feb 20, 2021 at 3:42 AM Michael Schantl  
> wrote:
>
>>
>> Hi Chris,
>>
>> I guess you followed the documentation for installing on a Pi?
>> http://www.weewx.com/docs/debian.htm
>>
>> In that case first uninstall WeeWX {should keep configuration}:
>>
>>sudo apt remove weewx
>>
>> Also keep in mind that the WLL driver uses the Python *requests* 
>> library. Install it using:
>>
>>sudo apt install python3-requests
>>
>> Then re-install according to the page linked above. In the first section 
>> only run the command that's labeled "*For Debian10 and later, use 
>> python3*". Skip the following line for Python 2.
>> Follow all other sections as usual.
>>
>> grua...@gmail.com schrieb am Samstag, 20. Februar 2021 um 11:52:18 UTC+1:
>>
>>> hello michael,
>>>
>>> you are right - install worked now, but i get an error in syslog.
>>>
>>> how can i tell my pi to use python3 instead of python2?
>>>
>>> regards,
>>> chris 
>>>
>>> michael.s...@gmail.com schrieb am Freitag, 19. Februar 2021 um 20:00:51 
>>> UTC+1:
>>>
 As far as I can see, you are using Python 2 or this problem occurs only 
 with this version.
 However, the plugin is unfortunately only compatible with Python 3, as 
 it also uses some other Py 3-only features.

 regards,
 Michael
 grua...@gmail.com schrieb am Freitag, 19. Februar 2021 um 19:31:26 
 UTC+1:

> thank you, this solved the problem :)
>
> tke...@gmail.com schrieb am Freitag, 19. Februar 2021 um 14:09:18 
> UTC+1:
>
>> The problem is that the extension author used the copyright character 
>> ('©') in the first line of the code for install.py, which is a non-ascii 
>> character. In Python 2.x, the default encoding of source code is ascii. 
>> If 
>> non-ascii characters are going to be used, then the encoding must be 
>> declared, which the author did not do. In Python 3.x, the default 
>> encoding 
>> is utf-8, so the copyright character will work.
>>
>> The fix is to either remove the character, or switch to Python 3.x. 
>> Or, contact the author.
>>
>> On Fri, Feb 19, 2021 at 2:01 AM Christian Gruber  
>> wrote:
>>
>>> hello,
>>>
>>> i am trying to install this extension to use it with my 
>>> weatherlink-live
>>> https://github.com/michael-slx/weewx-weatherlink-live
>>>
>>> it fails with the following error:
>>>
>>> ##
>>> Request to install 'release.zip'
>>> Extracting from zip archive release.zip
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_extension", line 88, in 
>>> main()
>>>   File "/usr/share/weewx/wee_extension", line 80, in main
>>> ext.install_extension(options.install)
>>>   File "/usr/share/weewx/weecfg/extension.py", line 125, in 
>>> install_extension
>>> self.install_from_dir(extension_dir)
>>>   File "/usr/share/weewx/weecfg/extension.py", line 147, in 
>>> install_from_dir
>>> extension_dir)
>>>   File "/usr/share/weewx/weecfg/__init__.py", line 1866, in 
>>> get_extension_installer
>>> __import__('install')
>>>   File "/var/tmp/weewx-weatherlink-live-release/install.py", line 1
>>> SyntaxError: Non-ASCII character '\xc2' in file 
>>> /var/tmp/weewx-weatherlink-live-release/install.py on line 1, but no 
>>> encoding declared; see http://python.oev/peps/pep-0263/ for details
>>> ##
>>>
>>> maybe someone can help me :)
>>>
>>> regards
>>> chris
>>>
>>> -- 
>>> 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/17172c68-ef7b-4d29-a23d-06caf60b4de9n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google 

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[Tom Keffer]

You do not need to uninstall weewx first.

Just follow the install instructions, but use the python3 version instead:


*wget -qO - https://weewx.com/apt/weewx-
python3.list | sudo tee
/etc/apt/sources.list.d/weewx.list*


*sudo apt-get updatesudo apt-get install weewx*



On Sat, Feb 20, 2021 at 3:42 AM Michael Schantl <
michael.schantl...@gmail.com> wrote:

>
> Hi Chris,
>
> I guess you followed the documentation for installing on a Pi?
> http://www.weewx.com/docs/debian.htm
>
> In that case first uninstall WeeWX {should keep configuration}:
>
>sudo apt remove weewx
>
> Also keep in mind that the WLL driver uses the Python *requests* library.
> Install it using:
>
>sudo apt install python3-requests
>
> Then re-install according to the page linked above. In the first section
> only run the command that's labeled "*For Debian10 and later, use python3*".
> Skip the following line for Python 2.
> Follow all other sections as usual.
>
> grua...@gmail.com schrieb am Samstag, 20. Februar 2021 um 11:52:18 UTC+1:
>
>> hello michael,
>>
>> you are right - install worked now, but i get an error in syslog.
>>
>> how can i tell my pi to use python3 instead of python2?
>>
>> regards,
>> chris
>>
>> michael.s...@gmail.com schrieb am Freitag, 19. Februar 2021 um 20:00:51
>> UTC+1:
>>
>>> As far as I can see, you are using Python 2 or this problem occurs only
>>> with this version.
>>> However, the plugin is unfortunately only compatible with Python 3, as
>>> it also uses some other Py 3-only features.
>>>
>>> regards,
>>> Michael
>>> grua...@gmail.com schrieb am Freitag, 19. Februar 2021 um 19:31:26
>>> UTC+1:
>>>
 thank you, this solved the problem :)

 tke...@gmail.com schrieb am Freitag, 19. Februar 2021 um 14:09:18
 UTC+1:

> The problem is that the extension author used the copyright character
> ('©') in the first line of the code for install.py, which is a non-ascii
> character. In Python 2.x, the default encoding of source code is ascii. If
> non-ascii characters are going to be used, then the encoding must be
> declared, which the author did not do. In Python 3.x, the default encoding
> is utf-8, so the copyright character will work.
>
> The fix is to either remove the character, or switch to Python 3.x.
> Or, contact the author.
>
> On Fri, Feb 19, 2021 at 2:01 AM Christian Gruber 
> wrote:
>
>> hello,
>>
>> i am trying to install this extension to use it with my
>> weatherlink-live
>> https://github.com/michael-slx/weewx-weatherlink-live
>>
>> it fails with the following error:
>>
>> ##
>> Request to install 'release.zip'
>> Extracting from zip archive release.zip
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_extension", line 88, in 
>> main()
>>   File "/usr/share/weewx/wee_extension", line 80, in main
>> ext.install_extension(options.install)
>>   File "/usr/share/weewx/weecfg/extension.py", line 125, in
>> install_extension
>> self.install_from_dir(extension_dir)
>>   File "/usr/share/weewx/weecfg/extension.py", line 147, in
>> install_from_dir
>> extension_dir)
>>   File "/usr/share/weewx/weecfg/__init__.py", line 1866, in
>> get_extension_installer
>> __import__('install')
>>   File "/var/tmp/weewx-weatherlink-live-release/install.py", line 1
>> SyntaxError: Non-ASCII character '\xc2' in file
>> /var/tmp/weewx-weatherlink-live-release/install.py on line 1, but no
>> encoding declared; see http://python.oev/peps/pep-0263/ for details
>> ##
>>
>> maybe someone can help me :)
>>
>> regards
>> chris
>>
>> --
>> 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/17172c68-ef7b-4d29-a23d-06caf60b4de9n%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/1a992758-a708-4422-9d89-2a1ef1d1289an%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google 

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[Michael Schantl]

Hi Chris,

I guess you followed the documentation for installing on a Pi?
http://www.weewx.com/docs/debian.htm

In that case first uninstall WeeWX {should keep configuration}:

   sudo apt remove weewx

Also keep in mind that the WLL driver uses the Python *requests* library. 
Install it using:

   sudo apt install python3-requests

Then re-install according to the page linked above. In the first section 
only run the command that's labeled "*For Debian10 and later, use python3*". 
Skip the following line for Python 2.
Follow all other sections as usual.

grua...@gmail.com schrieb am Samstag, 20. Februar 2021 um 11:52:18 UTC+1:

> hello michael,
>
> you are right - install worked now, but i get an error in syslog.
>
> how can i tell my pi to use python3 instead of python2?
>
> regards,
> chris 
>
> michael.s...@gmail.com schrieb am Freitag, 19. Februar 2021 um 20:00:51 
> UTC+1:
>
>> As far as I can see, you are using Python 2 or this problem occurs only 
>> with this version.
>> However, the plugin is unfortunately only compatible with Python 3, as it 
>> also uses some other Py 3-only features.
>>
>> regards,
>> Michael
>> grua...@gmail.com schrieb am Freitag, 19. Februar 2021 um 19:31:26 UTC+1:
>>
>>> thank you, this solved the problem :)
>>>
>>> tke...@gmail.com schrieb am Freitag, 19. Februar 2021 um 14:09:18 UTC+1:
>>>
 The problem is that the extension author used the copyright character 
 ('©') in the first line of the code for install.py, which is a non-ascii 
 character. In Python 2.x, the default encoding of source code is ascii. If 
 non-ascii characters are going to be used, then the encoding must be 
 declared, which the author did not do. In Python 3.x, the default encoding 
 is utf-8, so the copyright character will work.

 The fix is to either remove the character, or switch to Python 3.x. Or, 
 contact the author.

 On Fri, Feb 19, 2021 at 2:01 AM Christian Gruber  
 wrote:

> hello,
>
> i am trying to install this extension to use it with my 
> weatherlink-live
> https://github.com/michael-slx/weewx-weatherlink-live
>
> it fails with the following error:
>
> ##
> Request to install 'release.zip'
> Extracting from zip archive release.zip
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_extension", line 88, in 
> main()
>   File "/usr/share/weewx/wee_extension", line 80, in main
> ext.install_extension(options.install)
>   File "/usr/share/weewx/weecfg/extension.py", line 125, in 
> install_extension
> self.install_from_dir(extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 147, in 
> install_from_dir
> extension_dir)
>   File "/usr/share/weewx/weecfg/__init__.py", line 1866, in 
> get_extension_installer
> __import__('install')
>   File "/var/tmp/weewx-weatherlink-live-release/install.py", line 1
> SyntaxError: Non-ASCII character '\xc2' in file 
> /var/tmp/weewx-weatherlink-live-release/install.py on line 1, but no 
> encoding declared; see http://python.oev/peps/pep-0263/ for details
> ##
>
> maybe someone can help me :)
>
> regards
> chris
>
> -- 
> 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/17172c68-ef7b-4d29-a23d-06caf60b4de9n%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/1a992758-a708-4422-9d89-2a1ef1d1289an%40googlegroups.com.

[weewx-user] Sky Cover data to pwsweather.com

[Bruce Chapman]

Gary,  Thanks for your research on this.  I didn't know it there was some way 
of calculating this data in weewx and posting that I was missing.  I'm 
attempting to like the AerisPulse app but when the conditions they report to me 
are ~15 degrees different, it's difficult to do.  On the morning of January 
30th, my station was reporting a current temp of -15.2, Aeris was reporting -2 
for the same zip code.  It's hard to support or recommend an app with that much 
error.

And thanks for the explaination on the missing posts.  I kept getting a message 
that the post was deleted as soon as I posted it.  I ended up sending it 
through email.   …and again…same thing.

-- 
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/0aaa4f6a-9085-4884-bb7e-e7b0223c3374%40Spark.

[weewx-user] Re: Sky Cover data to pwsweather.com

[bchap...@gmail.com]

Gary,  Thanks for your research on this.  I didn't know it there was some 
way of calculating this data in weewx and posting that I was missing.  I'm 
attempting to like the AerisPulse app but when the conditions they report 
to me are ~15 degrees different, it's difficult to do.  On the morning of 
January 30th, my station was reporting a current temp of -15.2, Aeris was 
reporting -2 for the same zip code.  It's hard to support or recommend an 
app with that much error.

And thanks for the explaination on the missing posts.  I kept getting a 
message that the post was deleted as soon as I posted it.  I ended up 
sending it through email.


On Thursday, February 18, 2021 at 11:39:41 PM UTC-5 gjr80 wrote:

> Oh, and I forgot to mention. Your missing six messages found their way 
> into the spam folder, Groups seems to have a habit of randomly doing this 
> sometimes. I don't know why, especially when your seventh attempt worked! 
> In any case I deleted them, could not see the point of letting them through 
> now.
>
> Gary
>
>
> On Friday, 19 February 2021 at 14:36:18 UTC+10 gjr80 wrote:
>
>> So the question started as why you weren't seeing your data on an Aeris 
>> app and the answer was that only those stations that provide sky coverage 
>> were showing their data on the Aeris app. Subsequently, your question to us 
>> was how to I submit sky coverage data to PWS Weather. Fair question given 
>> the AerisWeather response, but as explained earlier this is not possible. 
>> The issue of a missing link raised by subsequent posts I suspect is largely 
>> irrelevant, the context of that para from AerisWeather Support was that as 
>> a PWS contributor you have free access to your data via the AerisWeather 
>> API. Somehow I don't think that was intended as a solution to getting your 
>> data to appear on the Aeris app but rather giving you a means to access 
>> your data (just like the WeatherUnderground API gives you access to your 
>> data) once you register on AerisWeather and link to your PWS account.
>>
>> In terms of sky coverage I did a bit of browsing on the PWS Weather 
>> station map last night and found that when looking at the METAR station at 
>> our international airport there was indeed a sky coverage plot. When I 
>> looked at PWS stations nearby the airport they too had a sky coverage plot 
>> and it was identical in every respect to the METAR sky coverage plot. 
>> However, once I was too far away from the METAR station (some 15-20km as 
>> the crow flies) the PWS stations all had no sky coverage plot. I think this 
>> tends to indicate that PWS stations on the station map are in fact 
>> obtaining sky coverage by virtue of their proximity to a METAR station 
>> rather than providing the data themselves. PWS Weather/Aeris may well 
>> mention this somewhere but I am yet to find it. 
>>
>> I think in terms of WeeWX and PWS Weather there is nothing further to be 
>> done. The WeeWX PWS Weather uploader uploads the correct data, albeit with 
>> no data in the 'weather' field (if someone comes along with an extension to 
>> WeeWX that includes suitable data for the 'weather' field then we can 
>> certainly extend the PWS Weather uploader to include that data). 
>>
>> Gary
>> On Thursday, 18 February 2021 at 20:41:18 UTC+10 bchap...@gmail.com 
>> wrote:
>>
>>> This is the response I got from Aeris when I asked them why I wasn't 
>>> seeing my own data in "Current Conditions" in the AerisPulse app:
>>>
>>> *
>>> 
>>> Nate Flohrs (AerisWeather Support)
>>> Feb 1, 2021, 9:40 AM CST
>>>
>>> Hi Bruce,
>>>
>>> Thanks for reaching out to AerisWeather!  For the purposes of providing 
>>> complete weather data, the Aeris Pulse app is currently designed to only 
>>> return stations that provide sky coverage information.  In your location, 
>>> the nearest station that provides those details is several miles away, 
>>> which is why you are seeing those results.  
>>>
>>> If you haven't already, you may want to go to settings > data options 
>>> and select "All" as the observations source.  This will ensure that the 
>>> closest station that provides sky data will be utilized.  
>>>
>>> There is an alternative solution that may help you access the data 
>>> coming specifically from your station.  Because you are a PWS contributor, 
>>> you are eligible for the contributor plan from AerisWeather.  It allows you 
>>> to access weather data through our API for no cost while your station is 
>>> sending information to our servers.  You can find more details here.  
>>>
>>> Hopefully that helps to explain the behavior you are seeing!  If you 
>>> have any additional questions, please let me know.  
>>> Thanks,
>>> Nate
>>> AerisWeather Support Team
>>> https://support.aerisweather.com
>>>
>>> On Wednesday, February 17, 2021 at 10:11:44 PM UTC-5 gjr80 wrote:
>>>
 I should add my comments re METAR is my supposition; the observation 
 related fields 

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[Christian Gruber]

hello michael,

you are right - install worked now, but i get an error in syslog.

how can i tell my pi to use python3 instead of python2?

regards,
chris 

michael.s...@gmail.com schrieb am Freitag, 19. Februar 2021 um 20:00:51 
UTC+1:

> As far as I can see, you are using Python 2 or this problem occurs only 
> with this version.
> However, the plugin is unfortunately only compatible with Python 3, as it 
> also uses some other Py 3-only features.
>
> regards,
> Michael
> grua...@gmail.com schrieb am Freitag, 19. Februar 2021 um 19:31:26 UTC+1:
>
>> thank you, this solved the problem :)
>>
>> tke...@gmail.com schrieb am Freitag, 19. Februar 2021 um 14:09:18 UTC+1:
>>
>>> The problem is that the extension author used the copyright character 
>>> ('©') in the first line of the code for install.py, which is a non-ascii 
>>> character. In Python 2.x, the default encoding of source code is ascii. If 
>>> non-ascii characters are going to be used, then the encoding must be 
>>> declared, which the author did not do. In Python 3.x, the default encoding 
>>> is utf-8, so the copyright character will work.
>>>
>>> The fix is to either remove the character, or switch to Python 3.x. Or, 
>>> contact the author.
>>>
>>> On Fri, Feb 19, 2021 at 2:01 AM Christian Gruber  
>>> wrote:
>>>
 hello,

 i am trying to install this extension to use it with my weatherlink-live
 https://github.com/michael-slx/weewx-weatherlink-live

 it fails with the following error:

 ##
 Request to install 'release.zip'
 Extracting from zip archive release.zip
 Traceback (most recent call last):
   File "/usr/share/weewx/wee_extension", line 88, in 
 main()
   File "/usr/share/weewx/wee_extension", line 80, in main
 ext.install_extension(options.install)
   File "/usr/share/weewx/weecfg/extension.py", line 125, in 
 install_extension
 self.install_from_dir(extension_dir)
   File "/usr/share/weewx/weecfg/extension.py", line 147, in 
 install_from_dir
 extension_dir)
   File "/usr/share/weewx/weecfg/__init__.py", line 1866, in 
 get_extension_installer
 __import__('install')
   File "/var/tmp/weewx-weatherlink-live-release/install.py", line 1
 SyntaxError: Non-ASCII character '\xc2' in file 
 /var/tmp/weewx-weatherlink-live-release/install.py on line 1, but no 
 encoding declared; see http://python.oev/peps/pep-0263/ for details
 ##

 maybe someone can help me :)

 regards
 chris

 -- 
 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/17172c68-ef7b-4d29-a23d-06caf60b4de9n%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/c25c62d1-15b2-4834-bf02-48c215f51208n%40googlegroups.com.