[weewx-user] Highcharts language

[Christian Gruber]

hello,

where can i translate the name form the month in the x-axis to german?

[image: highcharts.jpg]

-- 
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/7123a353-6eb9-40bb-9837-0fecb03cf399n%40googlegroups.com.

[weewx-user] Re: Belchertown skin - Feels Like Temperature

[Christian Gruber]

that's it, thsw was missing in this file, now its working! 

thanks a lot!

kk44...@gmail.com schrieb am Montag, 14. Juni 2021 um 17:02:14 UTC+2:

> grua schrieb am Montag, 14. Juni 2021 um 14:34:24 UTC+2:
>
>> i have enabled now MQTT, but the thsw temperature isn't showing anymore. 
>> is there anyhting else to adjust for this?
>>
>
> May be, THSW is missing in the template json/weewx_data.json.tmpl
>
> See below and compare to your version of that file.
>
> #encoding UTF-8
> #import datetime
> #errorCatcher Echo
> ## If extended almanac information is available, do extra calculations.
> #if $almanac.hasExtras
>   #set $sun_altitude = $almanac.sun.alt
>   #if $sun_altitude < 0
> #set $sun_None="(%s)" % $obs.label.sun_always_down
> #set $daylight_str = "00:00"
>   #else
> #set $sun_None="(%s)" % $obs.label.sun_always_up
> #set $daylight_str = "24:00"
>   #end if
>   #set $sunrise_ts = $almanac.sun.rise.raw
>   #set $sunset_ts = $almanac.sun.set.raw
>   #if $sunrise_ts and $sunset_ts
> #set $now = $current.dateTime.raw
> #set $today_daylight = $sunset_ts -  $sunrise_ts
> #set $seconds = $today_daylight
> #set $hours = $seconds // 3600
> #set $seconds %= 3600
> #set $minutes = $seconds // 60
> #set $seconds %= 60
> #set $daylight_str = "%d %s, %d %s, %d %s" % ($hours, 
> $obs.label.hour[0] if ( $hours == 1 ) else $obs.label.hour[1], $minutes, 
> $obs.label.minute[0] if ( $minutes == 1 ) else $obs.label.minute[1], 
> $seconds, $obs.label.second[0] if ( $seconds == 1 ) else 
> $obs.label.second[1])
> #set $yesterday = $now - 24*3600
> #set $yesterday_daylight = 
> $almanac($almanac_time=$yesterday).sun.set.raw - 
> $almanac($almanac_time=$yesterday).sun.rise.raw
> #set $difference = $today_daylight - $yesterday_daylight
> #if $difference
>   #set $delta = abs($difference)
>   #set $minute_difference = (int($delta) // 60)
>   #set $minutes_text = $obs.label.minute[0] if ( $minute_difference == 
> 1 ) else $obs.label.minute[1]
>   #set $seconds_text = $obs.label.second[0] if ( int($delta) == 1 ) 
> else $obs.label.second[1]
>   #set $amt_str = "%s%d %s" % (str(int($delta) // 60) + ' ' + 
> $minutes_text + ', ' if ($delta // 60) > 0 else '', $delta % 60 if ($delta 
> // 60) > 0 else $delta, $seconds_text)
>   #if $difference > 0
> #set $delta_str = "%s %s" % ( $amt_str, 
> $obs.label.more_than_yesterday )
>   #else
> #set $delta_str = "%s %s" % ( $amt_str, 
> $obs.label.less_than_yesterday )
>   #end if
>   #set $daylight_str = "%s%s" % ($daylight_str, $delta_str)
> #end if
>   #end if
> #end if
> {
> "site": "$station.location",
> "station_url": "$station.station_url",
> "version": "$station.version",
> "belchertown_version": "$belchertown_version",
> "weewxuptime": "$station.uptime",
> "serveruptime": "$station.os_uptime",
> "serverLocale": "$system_locale",
> "serverLocaleJS": "$system_locale_js",
> "localeEncoding": "$locale_encoding",
> "station": {
> "hardware": "$station.hardware",
> "location": "$station.location",
> "latitude": "$station.latitude[1]' $station.latitude[2]",
> "longitude": "$station.longitude[1]' $station.longitude[2]",
> "latitude_dd": "$station.stn_info.latitude_f",
> "longitude_dd": "$station.stn_info.longitude_f",
> "altitude": "$station.altitude",
> "archive_interval": "#echo $archive_interval_ms / 1000 #",
> "archive_interval_ms": "$archive_interval_ms"
> },
> "extras": {
> "belchertown_theme": "$Extras.theme",
> "theme_toggle_enabled": "$Extras.theme_toggle_enabled",
> "belchertown_locale": "$Extras.belchertown_locale",
> "reload_hook_images": "$Extras.reload_hook_images",
> "reload_images_radar": "$Extras.reload_images_radar",
> "reload_images_hook_asi": "$Extras.reload_images_hook_asi",
> "reload_images_hook_af": "$Extras.reload_images_hook_af",
> "reload_images_hook_as": "$Extras.reload_images_hook_as",
> "reload_images_hook_ac": "$Extras.reload_images_hook_ac",
> "station_observations": "$Extras.station_observations",
> "highcharts_homepage_graphgroup": 
> "$Extras.highcharts_homepage_graphgroup",
> "highcharts_decimal": "$Extras.highcharts_decimal",
> "highcharts_thousands": "$Extras.highcharts_thousands"
> },
> "earthquake": {
> "time": "$earthquake_time",
> "place": "$earthquake_place",
> "latitude": "$earthquake_lat",
> "longitude": "$earthquake_lon",
> "magnitude": "$earthquake_magnitude",
> "url": "$earthquake_url",
> "distance_away": "$earthquake_distance_away",
> "distance_label": "$earthquake_distance_label",
> "bearing": "$earthquake_bearing",
> "bearing_raw": "$earthquake_bearing_raw"
> },
> "station_observations": {
> 

[weewx-user] Re: Belchertown skin - Feels Like Temperature

[Christian Gruber]

hello,

i have an additional question to this. i have enabled now MQTT, but the 
thsw temperature isn't showing anymore.

is there anyhting else to adjust for this?



gary@gmail.com schrieb am Montag, 7. Juni 2021 um 22:16:53 UTC+2:

> Thanks for the suggestion, you were correct.
> Currently, THSW_F is 105.0 and now the Feels like: matches!
>
> On Monday, June 7, 2021 at 11:25:56 AM UTC-4 kk44...@gmail.com wrote:
>
>> Could it be that the observation is called "THSW" instead of "thsw"?
>>
>> If you look at the MQTT broker by a client (like MQTT explorer), is there 
>> a line "thsw_F"? Be careful about uppercase and lowercase characters.
>>
>> gary@gmail.com schrieb am Montag, 7. Juni 2021 um 15:33:25 UTC+2:
>>
>>> I gave this a try and end up with no display of AppTemp or the desired 
>>> thsw value. It's like I didn't choose to display anything.
>>> I edited the two files and since I am in the US, changed the Apparent 
>>> Temperature US lines in  belchertown.js.tmpl to be thsw then again to thsw_F
>>> In index.html.tmpl I changed $current.appTemp to $current.thsw
>>>
>>> There is thsw data sent to and recorded by WeeWX.
>>>
>>> Any ideas?
>>>
>>> [image: Clipboard Image.jpg]
>>> On Friday, February 26, 2021 at 4:36:35 AM UTC-5 kk44...@gmail.com 
>>> wrote:
>>>
 In /etc/weewx/skins/Belchertown/index.html.tmpl, line 192. replace 
 `$current.appTemp` by the desired value. 
 In /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl, line 1547, 
 replace the same, but be aware of the "_C" at the end.

 I hope, that are all occurences of appTemp.

 grua...@gmail.com schrieb am Freitag, 26. Februar 2021 um 10:13:35 
 UTC+1:

> hello,
>
> i want to display here the column "thsw" from the database, can i 
> change this in weewx.conf somehow?
>
> [image: feelslike.JPG]
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7221b8a6-f819-485f-945b-9ff769c9ab74n%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Christian Gruber]

should this still work with weewx 4.5.1 ?

i updated and my full day charts are gone

Manfred Maier schrieb am Montag, 15. Juni 2020 um 11:12:27 UTC+2:

> Thanks, Gary, for this comprehensive explanation.
>
> Based on what you wrote I was now able to plot an entire day.
>
> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>
> The trick is quite simple: I just had to define an aggregation for the 
> daily charts. I.e. adding the following two lines to the graphs.conf:
>
> aggregate_type = max
>
> aggregate_interval = 300
>
>
>
>

-- 
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/3ec51a00-2343-4b9e-81c1-ea4f3ed02a4en%40googlegroups.com.

[weewx-user] Re: weewx crashes after few days running

[Christian Gruber]

hello,

i use this driver, because it can map THSW, is this also possible with the 
other driver? it doesnt look so

belin@gmail.com schrieb am Montag, 5. April 2021 um 10:53:08 UTC+2:

> Try this one, use at home for several months :  
> https://github.com/Drealine/weatherlinklive-driver-weewx
>
> Le lundi 5 avril 2021 à 07:40:14 UTC+2, grua...@gmail.com a écrit :
>
>> hello,
>>
>> after a few days of running weewx crashes, i have to to do "sudo service 
>> weewx restart", then it runs again a few days.
>>
>> i am using the following driver to collect data: 
>> https://github.com/michael-slx/weewx-weatherlink-live
>>
>> this is the error code from syslog:
>>
>> Apr  5 03:15:17 piweewx weewx[2852] INFO user.weatherlink_live: Emitting 
>> push (broadcast) packet
>> Apr  5 03:15:17 piweewx weewx[2852] INFO weewx.engine: Main loop exiting. 
>> Shutting engine down.
>> Apr  5 03:15:18 piweewx weewx[2852] INFO user.weatherlink_live.scheduler: 
>> All tasks cancelled
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: Caught 
>> unrecoverable exception:
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Traceback (most recent call last):
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 214, in run
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> callback(event)
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 617, in check_loop
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> raise BreakLoop
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> weewx.engine.BreakLoop
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   During 
>> handling of the above exception, another exception occurred:
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Traceback (most recent call last):
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 633, in post_loop
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> self._catchup(self.engine.console.genArchiveRecords)
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 677, in _catchup
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   for 
>> record in generator(lastgood_ts):
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/drivers/__init__.py", line 30, in genArchiveRecords
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> raise NotImplementedError("Method 'genArchiveRecords' not implemented")
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> NotImplementedError: Method 'genArchiveRecords' not implemented
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   During 
>> handling of the above exception, another exception occurred:
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> Traceback (most recent call last):
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewxd", line 157, in main
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> engine.run()
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 221, in run
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> callback(event)
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 635, in post_loop
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> self._software_catchup()
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 697, in _software_catchup
>> Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
>> origin='software'))
>> 

[weewx-user] weewx crashes after few days running

[Christian Gruber]

hello,

after a few days of running weewx crashes, i have to to do "sudo service 
weewx restart", then it runs again a few days.

i am using the following driver to collect 
data: https://github.com/michael-slx/weewx-weatherlink-live

this is the error code from syslog:

Apr  5 03:15:17 piweewx weewx[2852] INFO user.weatherlink_live: Emitting 
push (broadcast) packet
Apr  5 03:15:17 piweewx weewx[2852] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Apr  5 03:15:18 piweewx weewx[2852] INFO user.weatherlink_live.scheduler: 
All tasks cancelled
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: Caught unrecoverable 
exception:
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   Traceback 
(most recent call last):
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 214, in run
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
callback(event)
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 617, in check_loop
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   raise 
BreakLoop
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
weewx.engine.BreakLoop
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   During 
handling of the above exception, another exception occurred:
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   Traceback 
(most recent call last):
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 633, in post_loop
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
self._catchup(self.engine.console.genArchiveRecords)
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 677, in _catchup
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   for 
record in generator(lastgood_ts):
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/drivers/__init__.py", line 30, in genArchiveRecords
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   raise 
NotImplementedError("Method 'genArchiveRecords' not implemented")
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
NotImplementedError: Method 'genArchiveRecords' not implemented
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   During 
handling of the above exception, another exception occurred:
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   Traceback 
(most recent call last):
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 157, in main
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
engine.run()
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 221, in run
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
callback(event)
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 635, in post_loop
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
self._software_catchup()
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 697, in _software_catchup
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
origin='software'))
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
callback(event)
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 658, in new_archive_record
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__:   
dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
Apr  5 03:15:19 piweewx weewx[2852] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 

[weewx-user] Re: Belchertown - MQTT with webhosting

[Christian Gruber]

ok i think i didn't do the first extension with extension.py because mine 
is empty :-)

i changed schema in weewx.config and recreated the database, then i got the 
new fields

i am a bit confused now what to do :-)

[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.manager.DaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = user.weatherlink_live.schema

Manfred Maier schrieb am Freitag, 12. März 2021 um 09:53:59 UTC+1:

> I've also extended my database scheme a second time - without any issues.
>
> Here's my extensions.py
> I've just added the additional three fields to the already extended scheme.
>
> grua...@gmail.com schrieb am Freitag, 12. März 2021 um 08:42:17 UTC+1:
>
>> got it, thank you manfred!
>>
>> now a question about radiationhours: i have extended the schema already 
>> one time for the weatherlink-driver: 
>> https://github.com/michael-slx/weewx-weatherlink-live
>>
>> whats the correct way to extend the schema a second time? i tried it one 
>> time, but then i lost the additional fields from the weatherlink-driver
>>
>> Manfred Maier schrieb am Donnerstag, 11. März 2021 um 19:28:55 UTC+1:
>>
>>> Yes, you are correct. If the page is using https, all components need to 
>>> have a ssl certificate.
>>>
>>> grua...@gmail.com schrieb am Donnerstag, 11. März 2021 um 10:00:07 
>>> UTC+1:
>>>
 hi,

 thanks for this file, i will try it after mqtt-setup :-)

 i always get failed connecting on my website and i think it's because 
 my site is using https

 the test here is working fine, i get the live data 
 http://www.hivemq.com/demos/websocket-client/

 do i have to run my local mosquitto installation also with ssl/tls or 
 is there another way to get it working?

 regards,
 chris

 Manfred Maier schrieb am Mittwoch, 10. März 2021 um 20:44:02 UTC+1:

> I'm using the attached file, which I found somewhere here in this user 
> forum. 
> I've slightly adapted it to bette fit my needs. 
>
> Don't get confused by the filed name 'EmptyReal'. That was just a 
> spare field I had in my database.
>
> The calculation of the theoretical radiation level is not 100% 
> perfect, but it does the job.
>
>
> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 20:05:55 
> UTC+1:
>
>> ok, i will try it locally before, but vserver is also a good (cheap) 
>> option :-)
>>
>> another question to you: how do you calculate sun hours on your site, 
>> is it from here? https://github.com/gjr80/weewx-weewx-wd
>>
>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 19:23:40 UTC+1:
>>
>>> No, I didn't.
>>>
>>> I'm (unfortunately) sitting behind fiberglass without a static IPv4. 
>>> So I anyway had to rent a vServer for running my own tunneling 
>>> solution for my local webcam.
>>>
>>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 19:12:12 
>>> UTC+1:
>>>
 hi manfred,

 did you try to run the broker locally before? 

 i have a static ip with symmetric bandwidth. or are there other 
 reasons why it doesnt work?

 regards,
 chris

 Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:

> Hi Chris,
> I've been in a similar situation to you.
> My web hosting service didn't allow me to run a MQTT broker and 
> the (free) public brokers didn't perform very well. The majority of 
> MQTT 
> packages got lost and were not delivered to the web client.
> So in the end I've decided to rent an additional vServer and run 
> my own MQTT broker. The setup was really easy, but there's a server 
> cost of 
> approx. 2€ per month.
>
> Manfred  
>
> kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 
> UTC+1:
>
>> You need a publicly available MQTT broker. Either you install one 
>> on your webhoster's webspace (if possible), or you use a public 
>> broker like 
>> test.mosquitto.org.
>>
>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 
>> UTC+1:
>>
>>> hello,
>>>
>>> i am uploading the reports via FTP to my webhoster. can i use 
>>> mqtt then for live data oder do i need a locally webserver?
>>>
>>> regards,
>>> chris

[weewx-user] Re: Belchertown - MQTT with webhosting

[Christian Gruber]

got it, thank you manfred!

now a question about radiationhours: i have extended the schema already one 
time for the 
weatherlink-driver: https://github.com/michael-slx/weewx-weatherlink-live

whats the correct way to extend the schema a second time? i tried it one 
time, but then i lost the additional fields from the weatherlink-driver

Manfred Maier schrieb am Donnerstag, 11. März 2021 um 19:28:55 UTC+1:

> Yes, you are correct. If the page is using https, all components need to 
> have a ssl certificate.
>
> grua...@gmail.com schrieb am Donnerstag, 11. März 2021 um 10:00:07 UTC+1:
>
>> hi,
>>
>> thanks for this file, i will try it after mqtt-setup :-)
>>
>> i always get failed connecting on my website and i think it's because my 
>> site is using https
>>
>> the test here is working fine, i get the live data 
>> http://www.hivemq.com/demos/websocket-client/
>>
>> do i have to run my local mosquitto installation also with ssl/tls or is 
>> there another way to get it working?
>>
>> regards,
>> chris
>>
>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 20:44:02 UTC+1:
>>
>>> I'm using the attached file, which I found somewhere here in this user 
>>> forum. 
>>> I've slightly adapted it to bette fit my needs. 
>>>
>>> Don't get confused by the filed name 'EmptyReal'. That was just a spare 
>>> field I had in my database.
>>>
>>> The calculation of the theoretical radiation level is not 100% perfect, 
>>> but it does the job.
>>>
>>>
>>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 20:05:55 UTC+1:
>>>
 ok, i will try it locally before, but vserver is also a good (cheap) 
 option :-)

 another question to you: how do you calculate sun hours on your site, 
 is it from here? https://github.com/gjr80/weewx-weewx-wd

 Manfred Maier schrieb am Mittwoch, 10. März 2021 um 19:23:40 UTC+1:

> No, I didn't.
>
> I'm (unfortunately) sitting behind fiberglass without a static IPv4. 
> So I anyway had to rent a vServer for running my own tunneling 
> solution for my local webcam.
>
> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 19:12:12 
> UTC+1:
>
>> hi manfred,
>>
>> did you try to run the broker locally before? 
>>
>> i have a static ip with symmetric bandwidth. or are there other 
>> reasons why it doesnt work?
>>
>> regards,
>> chris
>>
>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:
>>
>>> Hi Chris,
>>> I've been in a similar situation to you.
>>> My web hosting service didn't allow me to run a MQTT broker and the 
>>> (free) public brokers didn't perform very well. The majority of MQTT 
>>> packages got lost and were not delivered to the web client.
>>> So in the end I've decided to rent an additional vServer and run my 
>>> own MQTT broker. The setup was really easy, but there's a server cost 
>>> of 
>>> approx. 2€ per month.
>>>
>>> Manfred  
>>>
>>> kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 
>>> UTC+1:
>>>
 You need a publicly available MQTT broker. Either you install one 
 on your webhoster's webspace (if possible), or you use a public broker 
 like 
 test.mosquitto.org.

 grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 
 UTC+1:

> hello,
>
> i am uploading the reports via FTP to my webhoster. can i use mqtt 
> then for live data oder do i need a locally webserver?
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5e740158-31f0-436b-99b5-73059e208a38n%40googlegroups.com.

[weewx-user] Re: Belchertown - MQTT with webhosting

[Christian Gruber]

hi,

thanks for this file, i will try it after mqtt-setup :-)

i always get failed connecting on my website and i think it's because my 
site is using https

the test here is working fine, i get the live 
data http://www.hivemq.com/demos/websocket-client/

do i have to run my local mosquitto installation also with ssl/tls or is 
there another way to get it working?

regards,
chris

Manfred Maier schrieb am Mittwoch, 10. März 2021 um 20:44:02 UTC+1:

> I'm using the attached file, which I found somewhere here in this user 
> forum. 
> I've slightly adapted it to bette fit my needs. 
>
> Don't get confused by the filed name 'EmptyReal'. That was just a spare 
> field I had in my database.
>
> The calculation of the theoretical radiation level is not 100% perfect, 
> but it does the job.
>
>
> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 20:05:55 UTC+1:
>
>> ok, i will try it locally before, but vserver is also a good (cheap) 
>> option :-)
>>
>> another question to you: how do you calculate sun hours on your site, is 
>> it from here? https://github.com/gjr80/weewx-weewx-wd
>>
>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 19:23:40 UTC+1:
>>
>>> No, I didn't.
>>>
>>> I'm (unfortunately) sitting behind fiberglass without a static IPv4. 
>>> So I anyway had to rent a vServer for running my own tunneling solution 
>>> for my local webcam.
>>>
>>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 19:12:12 UTC+1:
>>>
 hi manfred,

 did you try to run the broker locally before? 

 i have a static ip with symmetric bandwidth. or are there other reasons 
 why it doesnt work?

 regards,
 chris

 Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:

> Hi Chris,
> I've been in a similar situation to you.
> My web hosting service didn't allow me to run a MQTT broker and the 
> (free) public brokers didn't perform very well. The majority of MQTT 
> packages got lost and were not delivered to the web client.
> So in the end I've decided to rent an additional vServer and run my 
> own MQTT broker. The setup was really easy, but there's a server cost of 
> approx. 2€ per month.
>
> Manfred  
>
> kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 
> UTC+1:
>
>> You need a publicly available MQTT broker. Either you install one on 
>> your webhoster's webspace (if possible), or you use a public broker like 
>> test.mosquitto.org.
>>
>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 
>> UTC+1:
>>
>>> hello,
>>>
>>> i am uploading the reports via FTP to my webhoster. can i use mqtt 
>>> then for live data oder do i need a locally webserver?
>>>
>>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a08e60af-c62f-4785-a0ab-001c70abfc0an%40googlegroups.com.

[weewx-user] Re: Belchertown - MQTT with webhosting

[Christian Gruber]

ok, i will try it locally before, but vserver is also a good (cheap) option 
:-)

another question to you: how do you calculate sun hours on your site, is it 
from here? https://github.com/gjr80/weewx-weewx-wd

Manfred Maier schrieb am Mittwoch, 10. März 2021 um 19:23:40 UTC+1:

> No, I didn't.
>
> I'm (unfortunately) sitting behind fiberglass without a static IPv4. 
> So I anyway had to rent a vServer for running my own tunneling solution 
> for my local webcam.
>
> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 19:12:12 UTC+1:
>
>> hi manfred,
>>
>> did you try to run the broker locally before? 
>>
>> i have a static ip with symmetric bandwidth. or are there other reasons 
>> why it doesnt work?
>>
>> regards,
>> chris
>>
>> Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:
>>
>>> Hi Chris,
>>> I've been in a similar situation to you.
>>> My web hosting service didn't allow me to run a MQTT broker and the 
>>> (free) public brokers didn't perform very well. The majority of MQTT 
>>> packages got lost and were not delivered to the web client.
>>> So in the end I've decided to rent an additional vServer and run my own 
>>> MQTT broker. The setup was really easy, but there's a server cost of 
>>> approx. 2€ per month.
>>>
>>> Manfred  
>>>
>>> kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 UTC+1:
>>>
 You need a publicly available MQTT broker. Either you install one on 
 your webhoster's webspace (if possible), or you use a public broker like 
 test.mosquitto.org.

 grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 UTC+1:

> hello,
>
> i am uploading the reports via FTP to my webhoster. can i use mqtt 
> then for live data oder do i need a locally webserver?
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c37787f3-bd64-41e6-a744-c8778b263549n%40googlegroups.com.

[weewx-user] Re: Belchertown - MQTT with webhosting

[Christian Gruber]

hi manfred,

did you try to run the broker locally before? 

i have a static ip with symmetric bandwidth. or are there other reasons why 
it doesnt work?

regards,
chris

Manfred Maier schrieb am Mittwoch, 10. März 2021 um 15:16:35 UTC+1:

> Hi Chris,
> I've been in a similar situation to you.
> My web hosting service didn't allow me to run a MQTT broker and the (free) 
> public brokers didn't perform very well. The majority of MQTT packages got 
> lost and were not delivered to the web client.
> So in the end I've decided to rent an additional vServer and run my own 
> MQTT broker. The setup was really easy, but there's a server cost of 
> approx. 2€ per month.
>
> Manfred  
>
> kk44...@gmail.com schrieb am Mittwoch, 10. März 2021 um 11:59:33 UTC+1:
>
>> You need a publicly available MQTT broker. Either you install one on your 
>> webhoster's webspace (if possible), or you use a public broker like 
>> test.mosquitto.org.
>>
>> grua...@gmail.com schrieb am Mittwoch, 10. März 2021 um 07:46:52 UTC+1:
>>
>>> hello,
>>>
>>> i am uploading the reports via FTP to my webhoster. can i use mqtt then 
>>> for live data oder do i need a locally webserver?
>>>
>>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e8dfe94c-c8ba-4c3c-a390-b6536982c97bn%40googlegroups.com.

[weewx-user] Belchertown - MQTT with webhosting

[Christian Gruber]

hello,

i am uploading the reports via FTP to my webhoster. can i use mqtt then for 
live data oder do i need a locally webserver?

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/79484328-9d39-4e9e-a8e6-dab848e2e206n%40googlegroups.com.

[weewx-user] Re: Belchertown skin - Feels Like Temperature

[Christian Gruber]

great, its working, thx a lot!

kk44...@gmail.com schrieb am Freitag, 26. Februar 2021 um 11:28:35 UTC+1:

> "current" is needed. If the value is called "thsw" within the database, 
> the tag would be `$current.thsw`
>
> grua...@gmail.com schrieb am Freitag, 26. Februar 2021 um 11:19:19 UTC+1:
>
>> tried now to replace it just with the column-name, but this doesnt work - 
>> the column-name is just displayed then
>>
>> how can i find out the name from the value i want to use? in database 
>> it's called "thsw"
>> kk44...@gmail.com schrieb am Freitag, 26. Februar 2021 um 10:36:35 UTC+1:
>>
>>> In /etc/weewx/skins/Belchertown/index.html.tmpl, line 192. replace 
>>> `$current.appTemp` by the desired value. 
>>> In /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl, line 1547, 
>>> replace the same, but be aware of the "_C" at the end.
>>>
>>> I hope, that are all occurences of appTemp.
>>>
>>> grua...@gmail.com schrieb am Freitag, 26. Februar 2021 um 10:13:35 
>>> UTC+1:
>>>
 hello,

 i want to display here the column "thsw" from the database, can i 
 change this in weewx.conf somehow?

 [image: feelslike.JPG]
 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6bd5929b-764b-48df-8a79-8935e625ea96n%40googlegroups.com.

[weewx-user] Re: Belchertown skin - Feels Like Temperature

[Christian Gruber]

tried now to replace it just with the column-name, but this doesnt work - 
the column-name is just displayed then

how can i find out the name from the value i want to use? in database it's 
called "thsw"
kk44...@gmail.com schrieb am Freitag, 26. Februar 2021 um 10:36:35 UTC+1:

> In /etc/weewx/skins/Belchertown/index.html.tmpl, line 192. replace 
> `$current.appTemp` by the desired value. 
> In /etc/weewx/skins/Belchertown/js/belchertown.js.tmpl, line 1547, replace 
> the same, but be aware of the "_C" at the end.
>
> I hope, that are all occurences of appTemp.
>
> grua...@gmail.com schrieb am Freitag, 26. Februar 2021 um 10:13:35 UTC+1:
>
>> hello,
>>
>> i want to display here the column "thsw" from the database, can i change 
>> this in weewx.conf somehow?
>>
>> [image: feelslike.JPG]
>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ecd887fb-dae7-4e4b-8984-564b61554b97n%40googlegroups.com.

[weewx-user] Belchertown skin - Feels Like Temperature

[Christian Gruber]

hello,

i want to display here the column "thsw" from the database, can i change 
this in weewx.conf somehow?

[image: feelslike.JPG]
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b966b2dd-23f8-412d-96c0-49df762d8cdfn%40googlegroups.com.

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

[Christian Gruber]

thx michael, works fine now :)

michael.s...@gmail.com schrieb am Dienstag, 23. Februar 2021 um 14:23:11 
UTC+1:

> Yes, a new db needs to be created. You could also configure a second db 
> manually, let WeeWX populate the schema and then transfer all data using 
> wee_database 
> --transfer
> But the effort is mostly the same either way, so it's easier to just 
> follow the documentation.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c5b42dbc-7658-43c8-baf3-8d48e8d6ddd5n%40googlegroups.com.

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

[Christian Gruber]

hello,

put my RPI now to the same subnet, and i get data.

i also switched schema in weewx.conf to user.weatherlink_live.schema and 
restarted the service

do i have to create a new database then, like its written 
here http://www.weewx.com/docs/customizing.htm#archive_database 
or is this not necessary?

regards,
chris

Christian Gruber schrieb am Sonntag, 21. Februar 2021 um 08:46:12 UTC+1:

> 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 
>> <https://github.com/thomseddon/udp-replicator>) on your home router.  
>> Another method (same assumptions) is to use port forwarding, which is 
>> described here 
>> <https://www.digitalocean.com/community/tutorials/how-to-forward-ports-through-a-linux-gateway-with-iptables>
>> .
>>
>> 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/8cf02db6-eb61-47d5-9d88-455e9b83470bn%40googlegroups.com.

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)

[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- 
> <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
&

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
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/17172c68-ef7b-4d29-a23d-06caf60b4de9n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c25c62d1-15b2-4834-bf02-48c215f51208n%40googlegroups.com.

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

[Christian Gruber]

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
>>  
>> <https://groups.google.com/d/msgid/weewx-user/17172c68-ef7b-4d29-a23d-06caf60b4de9n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c6037437-fe02-40ca-931c-fc998041a872n%40googlegroups.com.

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

[Christian Gruber]

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+unsubscr...@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.