Re: [weewx-user] change locale for html.tmpl with weewx 5.0.2

[Juan Antonio Mosquera Casais]

Hi,

Perfect, this works:
*TMP=$current.outTemp.format(localize=False, add_label=False)

Thanks Tom and Karen for your support and patience

El viernes, 12 de abril de 2024 a las 7:21:33 UTC+2, Karen K escribió:

> Juan Antonio Mosquera Casais schrieb am Freitag, 12. April 2024 um 
> 07:03:31 UTC+2:
>
> Oh... works... but, show units, i can delete units??
>
>
> Replace .formatted by .format(add_label=False)
>  
>

-- 
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/6b57a302-ca8d-4a4b-acb0-829c89fa8a83n%40googlegroups.com.

Re: [weewx-user] change locale for html.tmpl with weewx 5.0.2

[Juan Antonio Mosquera Casais]

Oh... works... but, show units, i can delete units??

Before:
*TMP=9,1
*WND=0
*AZI=   N/A
*BAR=1030,8

After:
*TMP=9.0 C
*WND=0 km/h
*AZI=   N/A
*BAR=1030.8 mbar


El jueves, 11 de abril de 2024 a las 21:56:29 UTC+2, Tom Keffer escribió:

> I'm not sure whether it would work, but you could try not localizing the 
> results. For example,
>
> *$monthoutTemp.max.format(localize=False)*
>
> See if that works.
>
>
>
>
> On Thu, Apr 11, 2024 at 10:37 AM Juan Antonio Mosquera Casais <
> juan.antonio.m...@gmail.com> wrote:
>
>> I read doc but i dont know this>
>>
>> I use Belchertown skin, and in skin.conf i generate a 
>> meteoclimatic.html.tmpl >
>>
>> *UPD=$current.dateTime.format("%d-%m-%Y %H:%M")
>> *TMP=$current.outTemp.formatted
>> *WND=$current.windSpeed.formatted
>> *AZI=$current.windDir.formatted
>> *BAR=$current.barometer.formatted
>> *HUM=$current.outHumidity.formatted
>> *SUN=$current.radiation.formatted
>> *UVI=$current.UV.formatted
>> *DHTM=$day.outTemp.max.formatted
>> *DLTM=$day.outTemp.min.formatted
>> *DHHM=$day.outHumidity.max.formatted
>> *DLHM=$day.outHumidity.min.formatted
>> *DHBR=$day.barometer.max.formatted
>> *DLBR=$day.barometer.min.formatted
>> *DGST=$day.windGust.max.formatted
>> *DSUN=$day.radiation.max.formatted
>> *DHUV=$day.UV.max.formatted
>> *DPCP=$day.rain.sum.formatted
>> *WRUN=
>> *MHTM=$month.outTemp.max.formatted
>> *MLTM=$month.outTemp.min.formatted
>> *MHHM=$month.outHumidity.max.formatted
>> *MLHM=$month.outHumidity.min.formatted
>> *MHBR=$month.barometer.max.formatted
>> *MLBR=$month.barometer.min.formatted
>> *MGST=$month.windGust.max.formatted
>> *MSUN=$month.radiation.max.formatted
>> *MHUV=$month.UV.max.formatted
>> *MPCP=$month.rain.sum.formatted
>> *YHTM=$year.outTemp.max.formatted
>> *YLTM=$year.outTemp.min.formatted
>> *YHHM=$year.outHumidity.max.formatted
>> *YLHM=$year.outHumidity.min.formatted
>> *YHBR=$year.barometer.max.formatted
>> *YLBR=$year.barometer.min.formatted
>> *YGST=$year.windGust.max.formatted
>> *YSUN=$year.radiation.max.formatted
>> *YHUV=$year.UV.max.formatted
>> *YPCP=$year.rain.sum.formatted
>> *EOT* 
>>
>> My locale is es_ES but, this meteoclimatic.html.tmpl i want en_US, is 
>> posible?
>>
>> -- 
>> 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/7c828d07-e48f-42e2-a34e-9c21636d3051n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/7c828d07-e48f-42e2-a34e-9c21636d3051n%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/b0f39e00-dd09-42ca-8b06-ea26a1039338n%40googlegroups.com.

[weewx-user] change locale for html.tmpl with weewx 5.0.2

[Juan Antonio Mosquera Casais]

I read doc but i dont know this>

I use Belchertown skin, and in skin.conf i generate a 
meteoclimatic.html.tmpl >

*UPD=$current.dateTime.format("%d-%m-%Y %H:%M")
*TMP=$current.outTemp.formatted
*WND=$current.windSpeed.formatted
*AZI=$current.windDir.formatted
*BAR=$current.barometer.formatted
*HUM=$current.outHumidity.formatted
*SUN=$current.radiation.formatted
*UVI=$current.UV.formatted
*DHTM=$day.outTemp.max.formatted
*DLTM=$day.outTemp.min.formatted
*DHHM=$day.outHumidity.max.formatted
*DLHM=$day.outHumidity.min.formatted
*DHBR=$day.barometer.max.formatted
*DLBR=$day.barometer.min.formatted
*DGST=$day.windGust.max.formatted
*DSUN=$day.radiation.max.formatted
*DHUV=$day.UV.max.formatted
*DPCP=$day.rain.sum.formatted
*WRUN=
*MHTM=$month.outTemp.max.formatted
*MLTM=$month.outTemp.min.formatted
*MHHM=$month.outHumidity.max.formatted
*MLHM=$month.outHumidity.min.formatted
*MHBR=$month.barometer.max.formatted
*MLBR=$month.barometer.min.formatted
*MGST=$month.windGust.max.formatted
*MSUN=$month.radiation.max.formatted
*MHUV=$month.UV.max.formatted
*MPCP=$month.rain.sum.formatted
*YHTM=$year.outTemp.max.formatted
*YLTM=$year.outTemp.min.formatted
*YHHM=$year.outHumidity.max.formatted
*YLHM=$year.outHumidity.min.formatted
*YHBR=$year.barometer.max.formatted
*YLBR=$year.barometer.min.formatted
*YGST=$year.windGust.max.formatted
*YSUN=$year.radiation.max.formatted
*YHUV=$year.UV.max.formatted
*YPCP=$year.rain.sum.formatted
*EOT* 

My locale is es_ES but, this meteoclimatic.html.tmpl i want en_US, is 
posible?

-- 
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/7c828d07-e48f-42e2-a34e-9c21636d3051n%40googlegroups.com.

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Juan Antonio Mosquera Casais]

Yes, i found, thanks

El jueves, 11 de abril de 2024 a las 15:45:43 UTC+2, Juan Antonio Mosquera 
Casais escribió:

> Ok Tom, this is de problem, thanks...
>
> I updated to 5.0.2... but other question, i need modify rsyncupdaload.py, 
> where is now?
>
> Thanks!
>
> El jueves, 11 de abril de 2024 a las 14:20:31 UTC+2, Tom Keffer escribió:
>
>> I suspect this may be a permissions issue. What do you get for the 
>> following commands?
>>
>> *ls -l /home/weewx*
>> *ls -l /home/weewx/examples*
>>
>>
>> Make sure everything in the directory "/home/weewx" is writable by user 
>> "pi". Usually, it's easiest just to have everything under /home/weewx owned 
>> by user "pi":
>>
>> *sudo chown -R pi:pi /home/weewx*
>>
>>
>>
>> On Wed, Apr 10, 2024 at 9:49 PM Juan Antonio Mosquera Casais <
>> juan.antonio.m...@gmail.com> wrote:
>>
>>> Ok, thanks, sorry, this step i reply N, if i reply Y>
>>>
>>> pi@raspberrypi:/home/weewx $  source ~/weewx-venv/bin/activate
>>> (weewx-venv) pi@raspberrypi:/home/weewx $  weectl station upgrade 
>>> --config=/home/weewx/weewx.conf
>>> Using configuration file /home/weewx/weewx.conf
>>>
>>> Upgrade examples, utility files in /home/weewx (Y/n)? 
>>> Removing example directory /home/weewx/examples
>>> Copying examples into /home/weewx/examples
>>> Traceback (most recent call last):
>>>   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
>>> sys.exit(main())
>>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
>>> 66, in main
>>> namespace.func(namespace)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
>>> line 121, in dispatch
>>> namespace.action_func(config_dict, namespace)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", 
>>> line 333, in upgrade_station
>>> weectllib.station_actions.station_upgrade(config_dict=config_dict,
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>>>  
>>> line 802, in station_upgrade
>>> examples_dir = copy_examples(config_dict, 
>>> examples_root=examples_root,
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>>>  
>>> line 618, in copy_examples
>>> shutil.copytree(examples_resources, examples_dir)
>>>   File "/usr/lib/python3.9/shutil.py", line 557, in copytree
>>> return _copytree(entries=entries, src=src, dst=dst, 
>>> symlinks=symlinks,
>>>   File "/usr/lib/python3.9/shutil.py", line 458, in _copytree
>>> os.makedirs(dst, exist_ok=dirs_exist_ok)
>>>   File "/usr/lib/python3.9/os.py", line 225, in makedirs
>>> mkdir(name, mode)
>>> FileExistsError: [Errno 17] File exists: '/home/weewx/examples'
>>>
>>> Thanks.
>>>
>>> El jueves, 11 de abril de 2024 a las 0:12:37 UTC+2, Tom Keffer escribió:
>>>
>>>> Juan, your service file, weewx.service, looks like the old V4.10 
>>>> service file. The new V5.0 file has a few more entries.
>>>>
>>>> Double check that you did step #2: upgrade the old examples and utility 
>>>> files. 
>>>>
>>>> On Wed, Apr 10, 2024 at 12:27 PM Juan Antonio Mosquera Casais <
>>>> juan.antonio.m...@gmail.com> wrote:
>>>>
>>>>> pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
>>>>> # systemd unit configuration file for WeeWX
>>>>> #
>>>>> # For information about running WeeWX under systemd,
>>>>> # be sure to read https://github.com/weewx/weewx/wiki/systemd
>>>>> #
>>>>> [Unit]
>>>>> Description=WeeWX weather system
>>>>> Documentation=https://weewx.com/docs
>>>>>
>>>>> Requires=time-sync.target
>>>>> After=time-sync.target
>>>>> RequiresMountsFor=/home
>>>>>
>>>>> [Service]
>>>>> ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
>>>>> StandardOutput=null
>>>>> # To run as a non-root user, uncomment and set username and group here:
>>>>> #User=weewx
>>>>> #Group=weewx
>>>>>
>>>

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Juan Antonio Mosquera Casais]

Ok Tom, this is de problem, thanks...

I updated to 5.0.2... but other question, i need modify rsyncupdaload.py, 
where is now?

Thanks!

El jueves, 11 de abril de 2024 a las 14:20:31 UTC+2, Tom Keffer escribió:

> I suspect this may be a permissions issue. What do you get for the 
> following commands?
>
> *ls -l /home/weewx*
> *ls -l /home/weewx/examples*
>
>
> Make sure everything in the directory "/home/weewx" is writable by user 
> "pi". Usually, it's easiest just to have everything under /home/weewx owned 
> by user "pi":
>
> *sudo chown -R pi:pi /home/weewx*
>
>
>
> On Wed, Apr 10, 2024 at 9:49 PM Juan Antonio Mosquera Casais <
> juan.antonio.m...@gmail.com> wrote:
>
>> Ok, thanks, sorry, this step i reply N, if i reply Y>
>>
>> pi@raspberrypi:/home/weewx $  source ~/weewx-venv/bin/activate
>> (weewx-venv) pi@raspberrypi:/home/weewx $  weectl station upgrade 
>> --config=/home/weewx/weewx.conf
>> Using configuration file /home/weewx/weewx.conf
>>
>> Upgrade examples, utility files in /home/weewx (Y/n)? 
>> Removing example directory /home/weewx/examples
>> Copying examples into /home/weewx/examples
>> Traceback (most recent call last):
>>   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
>> sys.exit(main())
>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
>> 66, in main
>> namespace.func(namespace)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
>> line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", 
>> line 333, in upgrade_station
>> weectllib.station_actions.station_upgrade(config_dict=config_dict,
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>>  
>> line 802, in station_upgrade
>> examples_dir = copy_examples(config_dict, examples_root=examples_root,
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>>  
>> line 618, in copy_examples
>> shutil.copytree(examples_resources, examples_dir)
>>   File "/usr/lib/python3.9/shutil.py", line 557, in copytree
>> return _copytree(entries=entries, src=src, dst=dst, symlinks=symlinks,
>>   File "/usr/lib/python3.9/shutil.py", line 458, in _copytree
>> os.makedirs(dst, exist_ok=dirs_exist_ok)
>>   File "/usr/lib/python3.9/os.py", line 225, in makedirs
>> mkdir(name, mode)
>> FileExistsError: [Errno 17] File exists: '/home/weewx/examples'
>>
>> Thanks.
>>
>> El jueves, 11 de abril de 2024 a las 0:12:37 UTC+2, Tom Keffer escribió:
>>
>>> Juan, your service file, weewx.service, looks like the old V4.10 service 
>>> file. The new V5.0 file has a few more entries.
>>>
>>> Double check that you did step #2: upgrade the old examples and utility 
>>> files. 
>>>
>>> On Wed, Apr 10, 2024 at 12:27 PM Juan Antonio Mosquera Casais <
>>> juan.antonio.m...@gmail.com> wrote:
>>>
>>>> pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
>>>> # systemd unit configuration file for WeeWX
>>>> #
>>>> # For information about running WeeWX under systemd,
>>>> # be sure to read https://github.com/weewx/weewx/wiki/systemd
>>>> #
>>>> [Unit]
>>>> Description=WeeWX weather system
>>>> Documentation=https://weewx.com/docs
>>>>
>>>> Requires=time-sync.target
>>>> After=time-sync.target
>>>> RequiresMountsFor=/home
>>>>
>>>> [Service]
>>>> ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
>>>> StandardOutput=null
>>>> # To run as a non-root user, uncomment and set username and group here:
>>>> #User=weewx
>>>> #Group=weewx
>>>>
>>>> [Install]
>>>> WantedBy=multi-user.target
>>>>
>>>>
>>>> El miércoles, 10 de abril de 2024 a las 19:46:01 UTC+2, vince escribió:
>>>>
>>>>> Check to see if you have multiple weewx.service files on your system.  
>>>>> It's possible you have one under /etc and a different one under /usr and 
>>>>> systemd is using the old one.
>>>>>
>>>>> If that is not the case, post your /etc/systemd/system/weewx.service 
>>>

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Juan Antonio Mosquera Casais]

Ok, thanks, sorry, this step i reply N, if i reply Y>

pi@raspberrypi:/home/weewx $  source ~/weewx-venv/bin/activate
(weewx-venv) pi@raspberrypi:/home/weewx $  weectl station upgrade 
--config=/home/weewx/weewx.conf
Using configuration file /home/weewx/weewx.conf

Upgrade examples, utility files in /home/weewx (Y/n)? 
Removing example directory /home/weewx/examples
Copying examples into /home/weewx/examples
Traceback (most recent call last):
  File "/home/pi/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", 
line 333, in upgrade_station
weectllib.station_actions.station_upgrade(config_dict=config_dict,
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", 
line 802, in station_upgrade
examples_dir = copy_examples(config_dict, examples_root=examples_root,
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", 
line 618, in copy_examples
shutil.copytree(examples_resources, examples_dir)
  File "/usr/lib/python3.9/shutil.py", line 557, in copytree
return _copytree(entries=entries, src=src, dst=dst, symlinks=symlinks,
  File "/usr/lib/python3.9/shutil.py", line 458, in _copytree
os.makedirs(dst, exist_ok=dirs_exist_ok)
  File "/usr/lib/python3.9/os.py", line 225, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/home/weewx/examples'

Thanks.

El jueves, 11 de abril de 2024 a las 0:12:37 UTC+2, Tom Keffer escribió:

> Juan, your service file, weewx.service, looks like the old V4.10 service 
> file. The new V5.0 file has a few more entries.
>
> Double check that you did step #2: upgrade the old examples and utility 
> files. 
>
> On Wed, Apr 10, 2024 at 12:27 PM Juan Antonio Mosquera Casais <
> juan.antonio.m...@gmail.com> wrote:
>
>> pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
>> # systemd unit configuration file for WeeWX
>> #
>> # For information about running WeeWX under systemd,
>> # be sure to read https://github.com/weewx/weewx/wiki/systemd
>> #
>> [Unit]
>> Description=WeeWX weather system
>> Documentation=https://weewx.com/docs
>>
>> Requires=time-sync.target
>> After=time-sync.target
>> RequiresMountsFor=/home
>>
>> [Service]
>> ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
>> StandardOutput=null
>> # To run as a non-root user, uncomment and set username and group here:
>> #User=weewx
>> #Group=weewx
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>>
>> El miércoles, 10 de abril de 2024 a las 19:46:01 UTC+2, vince escribió:
>>
>>> Check to see if you have multiple weewx.service files on your system.  
>>> It's possible you have one under /etc and a different one under /usr and 
>>> systemd is using the old one.
>>>
>>> If that is not the case, post your /etc/systemd/system/weewx.service 
>>> file please.
>>>
>>> On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera 
>>> Casais wrote:
>>>
>>>> Thanks... but... step 4 done> 
>>>>
>>>> history
>>>>
>>>>  1323  sudo cp /home/weewx/util/systemd/weewx.service 
>>>> /etc/systemd/system
>>>>  1324  sudo systemctl daemon-reload
>>>>  1325  sudo systemctl enable weewx
>>>>  1326  sudo systemctl start weewx
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> El miércoles, 10 de abril de 2024 a las 13:16:55 UTC+2, Tom Keffer 
>>>> escribió:
>>>>
>>>>> You did not update your weewx service file, 
>>>>> /etc/systemd/system/weewx.service. This is step #4 in the instructions. 
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
>>>>> juan.antonio.m...@gmail.com> wrote:
>>>>>
>>>>>> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the 
>>>>>> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but 
>>>>>> when trying to start the service I get this error:
>>>>>>
>>>>>> Apr 10 07:39:51 raspberrypi syste

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Juan Antonio Mosquera Casais]

pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
# systemd unit configuration file for WeeWX
#
# For information about running WeeWX under systemd,
# be sure to read https://github.com/weewx/weewx/wiki/systemd
#
[Unit]
Description=WeeWX weather system
Documentation=https://weewx.com/docs

Requires=time-sync.target
After=time-sync.target
RequiresMountsFor=/home

[Service]
ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
StandardOutput=null
# To run as a non-root user, uncomment and set username and group here:
#User=weewx
#Group=weewx

[Install]
WantedBy=multi-user.target


El miércoles, 10 de abril de 2024 a las 19:46:01 UTC+2, vince escribió:

> Check to see if you have multiple weewx.service files on your system. 
>  It's possible you have one under /etc and a different one under /usr and 
> systemd is using the old one.
>
> If that is not the case, post your /etc/systemd/system/weewx.service file 
> please.
>
> On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera 
> Casais wrote:
>
>> Thanks... but... step 4 done> 
>>
>> history
>>
>>  1323  sudo cp /home/weewx/util/systemd/weewx.service /etc/systemd/system
>>  1324  sudo systemctl daemon-reload
>>  1325  sudo systemctl enable weewx
>>  1326  sudo systemctl start weewx
>>
>>
>>
>>
>>
>> El miércoles, 10 de abril de 2024 a las 13:16:55 UTC+2, Tom Keffer 
>> escribió:
>>
>>> You did not update your weewx service file, 
>>> /etc/systemd/system/weewx.service. This is step #4 in the instructions. 
>>>
>>>
>>>
>>> On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
>>> juan.antonio.m...@gmail.com> wrote:
>>>
>>>> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the 
>>>> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but 
>>>> when trying to start the service I get this error:
>>>>
>>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to 
>>>> locate executable /home/weewx/bin/weewxd: No such file or directory
>>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at 
>>>> step EXEC spawning /home/weewx/bin/weewxd: No such file or directory
>>>> Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
>>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process 
>>>> exited, code=exited, status=203/EXEC
>>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with 
>>>> result 'exit-code'.
>>>>
>>>> It is because in the instructions the bin has to be moved to bin.old, 
>>>> if I put the bin back it works, but with version 4.10.2. How can I update 
>>>> to version 5.0.2 and keep my old configuration? Thank you. 
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to weewx-user+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%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/ccdd2474-9966-482c-9fde-41f66891841en%40googlegroups.com.

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Juan Antonio Mosquera Casais]

Thanks... but... step 4 done> 

history

 1323  sudo cp /home/weewx/util/systemd/weewx.service /etc/systemd/system
 1324  sudo systemctl daemon-reload
 1325  sudo systemctl enable weewx
 1326  sudo systemctl start weewx





El miércoles, 10 de abril de 2024 a las 13:16:55 UTC+2, Tom Keffer escribió:

> You did not update your weewx service file, 
> /etc/systemd/system/weewx.service. This is step #4 in the instructions. 
>
>
>
> On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
> juan.antonio.m...@gmail.com> wrote:
>
>> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the 
>> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but when 
>> trying to start the service I get this error:
>>
>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to 
>> locate executable /home/weewx/bin/weewxd: No such file or directory
>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at step 
>> EXEC spawning /home/weewx/bin/weewxd: No such file or directory
>> Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=203/EXEC
>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>>
>> It is because in the instructions the bin has to be moved to bin.old, if 
>> I put the bin back it works, but with version 4.10.2. How can I update to 
>> version 5.0.2 and keep my old configuration? Thank you. 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%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/44731de8-7a3d-40c8-872b-97d99ffb7f2bn%40googlegroups.com.

[weewx-user] Update 4.10.2 to 5.0.2 failed, not start service

[Juan Antonio Mosquera Casais]

I follow this instructions https://github.com/weewx/weewx/wiki/v5-upgrade
And now, not start service:

Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to locate 
executable /home/weewx/bin/weewxd: No such file or directory
Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at step 
EXEC spawning /home/weewx/bin/weewxd: No such file or directory
Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process exited, 
code=exited, status=203/EXEC
Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit-code'.

Any idea?? thanks!

-- 
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/aee82965-0fe8-4bd5-9cc0-18075b8055a6n%40googlegroups.com.

[weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Juan Antonio Mosquera Casais]

Hello, I have weewx 4.10.2 installed via setup.py, and I followed the 
instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but when 
trying to start the service I get this error:

Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to locate 
executable /home/weewx/bin/weewxd: No such file or directory
Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at step 
EXEC spawning /home/weewx/bin/weewxd: No such file or directory
Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process exited, 
code=exited, status=203/EXEC
Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit-code'.

It is because in the instructions the bin has to be moved to bin.old, if I 
put the bin back it works, but with version 4.10.2. How can I update to 
version 5.0.2 and keep my old configuration? Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com.

Re: [weewx-user] locale FTP template and belchertown theme

[Juan Antonio Mosquera Casais]

Thanks Tom, but it doesn't work. The strange thing is that the first 
generation of the template is correct (en_US) but the second and subsequent 
ones are again es_ES, does the Belchertown configuration somehow prevail 
globally?. I don't understand how the first generation is correct.

El miércoles, 29 de noviembre de 2023 a las 18:16:51 UTC+1, Chuck Rhode 
escribió:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, 29 Nov 2023 08:34:17 -0800
> Tom Keffer  wrote:
>
> > It's a bit of a hack, but one thing you could try is to put something
> > like this at the top of a template (NOT TESTED):
>
> > #import locale
> > #locale.setlocale(locale.LC_ALL, 'es_ES')
>
> > This would set the locale. It will stay set until the next call to
> > setlocale(). Note that this will set the locale for *every* time that
> > the template is used.
>
> My understanding is that the call to locale.setlocale has global
> effect and impacts all running processes, but maybe I'm misinterpreting
> the "not thread safe" warnings. The OP seems to want to run out of two
> locales simultaneously — one for FTP and one for Belchertown. So long
> as these skins are single threaded (one being complete before the other
> begins), then each can call its own locale.setlocale. I'm not sure
> how *weewxd* runs its "services" repertoire, though.
>
> - -- 
> .. Be Seeing You,
> .. Chuck Rhode, Sheboygan, WI, USA
> .. Weather: http://LacusVeris.com/WX
> .. 31° — Wind W 13 mph
>
> -BEGIN PGP SIGNATURE-
>
> iF0EARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCZWdx/AAKCRBg2/xipKOW
> UqyOAJ4jbejtywEIrb6Q5Vwfb1fhVQVtQQCeKGNM4KanMdpiRvRoe1Hdpbs0xYo=
> =+cD5
> -END PGP SIGNATURE-
>

-- 
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/3bb21434-6de5-4ad7-ad29-6541288fb8ffn%40googlegroups.com.

[weewx-user] locale FTP template and belchertown theme

[Juan Antonio Mosquera Casais]

Hello,
I have installed the latest version of stable weewx, belchertown theme on 
Raspberry (raspbian). I have a problem with coding, I want to be able to 
generate templates like FTP with en_US coding and belchertown with es_ES 
coding (the Belchertown configuration allows it). But having installed in 
the system the two locales (en_US and es_ES) with en_US by default. When I 
start weewx, the first generation of the tmpl generates it correctly with 
en_US encoding (with dotted decimal separator) but the following 
generations of the file appear as es_ES. I don't understand what the 
problem is.
thank you

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/594953ce-dca3-4fec-a4c1-949cbb011bd1n%40googlegroups.com.

Re: [weewx-user] Re: FTPS error in WeeWX version 4.0.0

[Juan Antonio Mosquera]

Is it possible that the problem is that the component is waiting to accept 
the certificate? Is it possible to add an option to always accept the 
certificate (trust the certificate always)?

RSYNC is not possible.

Thank you.

O luns, 26 de abril de 2021 á/s 20:45:06 UTC+2, Juan Antonio Mosquera 
escribiu:

> I tried reuse_ssl = True. but... impossible connect... with lftp 
> connects OK with this config:
>
> lftp -u $USER,$PASSWORD ftps://$HOST:$PORT < ssl:verify-certificate no set ftp:ssl-protect-data true put test.txt exit 
> EOF
>
> Weewx logs:
>
> Apr 26 20:41:04 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: ftpgenerator: (0): caught exception ' 'socket.timeout'>': timed out
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   Traceback (most recent call last):
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weewx/reportengine.py", line 331, in run
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   n = ftp_data.run()
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File 
> "/usr/share/weewx/weeutil/ftpupload.py", line 133, in run
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   ftp_server.connect(self.server, 
> self.port)
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
> line 155, in connect
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   self.welcome = self.getresp()
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
> line 236, in getresp
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   resp = self.getmultiline()
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
> line 222, in getmultiline
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   line = self.getline()
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
> line 204, in getline
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   line = 
> self.file.readline(self.maxline + 1)
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine: File "/usr/lib/python3.7/socket.py", 
> line 589, in readinto
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   return self._sock.recv_into(b)
> Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
> weewx.reportengine:   socket.timeout: timed out
>
>
> O mércores, 13 de maio de 2020 á/s 18:51:24 UTC+2, tke...@gmail.com 
> escribiu:
>
>> Stephen and I had an offline conversation and came up with a fix. Commit 
>> 3c81cd2 
>> <https://github.com/weewx/weewx/commit/3c81cd2c1c2d098e060b9d286839654733324bb7>
>> .
>>
>> To use the fix, replace your copy of weewx/reportengine.py 
>> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/reportengine.py>
>> .
>> Same with weeutil/ftpupload.py 
>> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weeutil/ftpupload.py>
>> .
>>
>> Then under [[FTP]] add this option
>>
>>   [[FTP]]
>> ... (as before)
>> reuse_ssl = True
>>
>> The fix will only work with Python >= 3.6. 
>>
>> -tk
>>
>>
>> On Tue, May 12, 2020 at 3:05 PM Stephen  wrote:
>>
>>>
>>>
>>> On Tuesday, 12 May 2020 17:31:10 UTC+1, Tom Keffer wrote:
>>>>
>>>> Does the client have access to any ssh keys? 
>>>>
>>>
>>> No 
>>>
>>> Is there a debug mode for the client where you can watch what it's 
>>>> doing, and see what's different?
>>>>
>>>
>>>  Yes, here is the output.  I'm using lftp.  There are some differences 
>>> so I modified the WeeWX code to make it do the same but it didn't fix it.
>>>
>>> server.myhost.net <--- 220-- Welcome to Pure-FTPd [privsep] 
>>> [TLS] --
>>> serve

Re: [weewx-user] Re: FTPS error in WeeWX version 4.0.0

[Juan Antonio Mosquera]

I tried reuse_ssl = True. but... impossible connect... with lftp 
connects OK with this config:

lftp -u $USER,$PASSWORD ftps://$HOST:$PORT <': timed out
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   Traceback (most recent call last):
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/weewx/reportengine.py", line 331, in run
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   n = ftp_data.run()
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/weeutil/ftpupload.py", line 133, in run
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   ftp_server.connect(self.server, 
self.port)
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
line 155, in connect
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   self.welcome = self.getresp()
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
line 236, in getresp
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   resp = self.getmultiline()
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
line 222, in getmultiline
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   line = self.getline()
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File "/usr/lib/python3.7/ftplib.py", 
line 204, in getline
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   line = 
self.file.readline(self.maxline + 1)
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine: File "/usr/lib/python3.7/socket.py", 
line 589, in readinto
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   return self._sock.recv_into(b)
Apr 26 20:41:05 raspberrypi python3[1399]: weewx[1399] ERROR 
weewx.reportengine:   socket.timeout: timed out


O mércores, 13 de maio de 2020 á/s 18:51:24 UTC+2, tke...@gmail.com 
escribiu:

> Stephen and I had an offline conversation and came up with a fix. Commit 
> 3c81cd2 
> 
> .
>
> To use the fix, replace your copy of weewx/reportengine.py 
> 
> .
> Same with weeutil/ftpupload.py 
> 
> .
>
> Then under [[FTP]] add this option
>
>   [[FTP]]
> ... (as before)
> reuse_ssl = True
>
> The fix will only work with Python >= 3.6. 
>
> -tk
>
>
> On Tue, May 12, 2020 at 3:05 PM Stephen  wrote:
>
>>
>>
>> On Tuesday, 12 May 2020 17:31:10 UTC+1, Tom Keffer wrote:
>>>
>>> Does the client have access to any ssh keys? 
>>>
>>
>> No 
>>
>> Is there a debug mode for the client where you can watch what it's doing, 
>>> and see what's different?
>>>
>>
>>  Yes, here is the output.  I'm using lftp.  There are some differences so 
>> I modified the WeeWX code to make it do the same but it didn't fix it.
>>
>> server.myhost.net <--- 220-- Welcome to Pure-FTPd [privsep] 
>> [TLS] --
>> server.myhost.net <--- 220-You are user number 3 of 50 allowed.
>> server.myhost.net <--- 220-Local time is now 19:53. Server port: 21.
>> server.myhost.net <--- 220-This is a private system - No anonymous login
>> server.myhost.net <--- 220-IPv6 connections are also welcome on this 
>> server.
>> server.myhost.net <--- 220 You will be disconnected after 15 minutes of 
>> inactivity.
>> server.myhost.net ---> FEAT
>> server.myhost.net <--- 211-Extensions supported:
>> server.myhost.net <---  EPRT
>> server.myhost.net <---  IDLE
>> server.myhost.net <---  MDTM
>> server.myhost.net <---  SIZE
>> server.myhost.net <---  MFMT
>> server.myhost.net <---  REST STREAM
>> server.myhost.net <---  MLST 
>> type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
>> server.myhost.net <---  MLSD
>> server.myhost.net <---  AUTH TLS
>> server.myhost.net <---  PBSZ
>> server.myhost.net <---  PROT
>> server.myhost.net <---  UTF8
>> server.myhost.net <---  TVFS
>> server.myhost.net <---  ESTA
>> server.myhost.net <---  PASV
>> server.myhost.net <---  EPSV
>> server.myhost.net <---  SPSV
>> server.myhost.net <---  ESTP
>> server.myhost.net <--- 211 End.
>> server.myhost.net ---> AUTH TLS
>> server.myhost.net <--- 234 AUTH TLS OK.
>> server.myhost.net ---> OPTS UTF8 ON
>> server.myhost.net <--- 200 OK, 

[weewx-user] Re: best way to use weewx with a Davis station

[Juan Antonio Mosquera]

ok ... and with weatherlink cloud weewx gets all current and historical 
data (I have seen that there is a weewx extension for weatherlink live to 
work). QUESTION: can I buy a davis vantage pro2 with weatherlink live and 
have historical data with weewx? (using the extension)

O xoves, 31 de decembro de 2020 á/s 14:59:22 UTC+1, kk44...@gmail.com 
escribiu:

> The adaptors for the console are discontinued. Davis now sells the 
> WeatherLinkLive device, only. 
>
> To use WeatherLinkLive you do not need a console at all. Unfortunately you 
> cannot use the device without setting it up by connecting it to the cloud 
> of Davis.
>
> The drivers for the old adaptors can read data saved in the device. That's 
> why you do not loose data if weewx is down for some time. The drivers for 
> WeatherLinkLive cannot read those data. Davis prevents it.
>
> Juan Antonio Mosquera schrieb am Donnerstag, 31. Dezember 2020 um 10:16:20 
> UTC+1:
>
>>
>> hi, what is the best way to use weewx with a davis vantage vue2 or davis 
>> vantage pro2 ?. weatherlink live? or ... USB console and datalogger?
>>
>> thanks.
>>
>

-- 
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/c6dd29b3-ab79-4358-bd67-ecc2bf646806n%40googlegroups.com.

[weewx-user] best way to use weewx with a Davis station

[Juan Antonio Mosquera]

hi, what is the best way to use weewx with a davis vantage vue2 or davis 
vantage pro2 ?. weatherlink live? or ... USB console and datalogger?

thanks.

-- 
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/94dd207f-421b-4bb3-9c3e-45c8ad3d2563n%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.1 released!

[Juan Antonio Mosquera]

Hello,

thanks, i updated OK.

But... i have a problem with Firefox and Graphs... (www.meteomontaos.es)


El miércoles, 8 de abril de 2020, 20:26:33 (UTC+2), Pat escribió:
>
> As mentioned in this thread 
> , I've 
> released Belchertown skin 1.1. This will be the last skin that uses the 
> DarkSky API for weather conditions and forecasts. I'm going to begin 
> working on 1.2 soon to migrate to OpenWeatherMap. 
>
> Read the entire release details here 
> 
>  which 
> outline the breaking changes, new changes, items removed, etc. 
>
> Always have a backup before you upgrade!
>
> Download:
>
> wget 
> https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.1/weewx-belchertown-release-1.1.tar.gz
>
> Then run:
>
> sudo wee_extension --install weewx-belchertown-release-1.1.tar.gz
>
>
> Restart weewx when finished configuring. 
>
>
> Thanks!
>

-- 
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/3f0ee744-a5fb-45a5-87a4-caa5456b762a%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Juan Antonio Mosquera]

it is possible that a vim swap file was the cause.

sorry!

El lunes, 3 de junio de 2019, 20:55:04 (UTC+2), Pat escribió:
>
> The installation of the skin shouldn't break weewx.conf. What was deleted 
> from your weewx.conf?
>
>
> On Monday, June 3, 2019 at 2:48:18 PM UTC-4, Juan Antonio Mosquera wrote:
>>
>> This problem is in weewx.conf 
>>
>> installation crash this file backup is necesary!
>>
>> Greetings.
>>
>> El lunes, 3 de junio de 2019, 20:35:12 (UTC+2), Juan Antonio Mosquera 
>> escribió:
>>>
>>> Hi...
>>>
>>> rare... i had 1.0 version... i update... and...
>>>
>>> jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
>>> exception in engine:
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most 
>>> recent call last):
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 884, in main
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
>>> engine_class(config_dict)
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>>> self.loadServices(config_dict)
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>>> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 304, in __init__
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>>> target_unit_nickname = config_dict['StdConvert']['target_unit']
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
>>> dict.__getitem__(self, key)
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 
>>> 'StdConvert'
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.
>>>
>>>
>>> what problem¿?
>>>
>>> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>>>
>>>> Belchertown skin 1.0 is released!
>>>>
>>>> This update contains a lot of updates and changes including *an entire 
>>>> rewrite of the Highcharts system* which allows you to make almost any 
>>>> graph you want for almost any time span you want. You can see some 
>>>> examples 
>>>> of the charts you can make on the BelchertownWeather.com website 
>>>> graphs page <https://belchertownweather.com/graphs/?graph=all>.
>>>>
>>>> You can add/remove/change/reorder any chart, change colors, add 
>>>> observation plots, categorize for all time. Almost anything you want to do 
>>>> is available! The skin comes with the standard 4 charts ready to go, but 
>>>> there's extensive Belchertown Charts Documentation 
>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>>>  
>>>> which can help you get started. 
>>>>
>>>> In addition to the Charts there's now a dark mode (which has an 
>>>> auto-switching mode based on sunset/sunrise), more flexibility for 
>>>> translations, user customized station observation table which is updated 
>>>> in 
>>>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>>>> release notes for all the details! 
>>>>
>>>> You can download the latest release here 
>>>> <https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.0/weewx-belchertown-release-1.0.tar.gz>,
>>>>  
>>>> and read all of the details on the changes here: 
>>>> https://github.com/poblabs/weewx-belchertown/releases
>>>>
>>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>>>> uninstall everything and reinstall new. This is due to the Chart system 
>>>> being fully rewritten and the potential for conflicts. Please read 
>>>> this upgrade guide if you are up

[weewx-user] Re: Belchertown skin 1.0 released!

[Juan Antonio Mosquera]

This problem is in weewx.conf 

installation crash this file backup is necesary!

Greetings.

El lunes, 3 de junio de 2019, 20:35:12 (UTC+2), Juan Antonio Mosquera 
escribió:
>
> Hi...
>
> rare... i had 1.0 version... i update... and...
>
> jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
> exception in engine:
> jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
> jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most recent 
> call last):
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 884, in main
> jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
> engine_class(config_dict)
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
> jun 03 20:30:43 meteomontaos weewx[4029]:   
> self.loadServices(config_dict)
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> jun 03 20:30:43 meteomontaos weewx[4029]:   
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 304, in __init__
> jun 03 20:30:43 meteomontaos weewx[4029]:   
> target_unit_nickname = config_dict['StdConvert']['target_unit']
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
> jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
> dict.__getitem__(self, key)
> jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 'StdConvert'
> jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.
>
>
> what problem¿?
>
> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>
>> Belchertown skin 1.0 is released!
>>
>> This update contains a lot of updates and changes including *an entire 
>> rewrite of the Highcharts system* which allows you to make almost any 
>> graph you want for almost any time span you want. You can see some examples 
>> of the charts you can make on the BelchertownWeather.com website graphs 
>> page <https://belchertownweather.com/graphs/?graph=all>.
>>
>> You can add/remove/change/reorder any chart, change colors, add 
>> observation plots, categorize for all time. Almost anything you want to do 
>> is available! The skin comes with the standard 4 charts ready to go, but 
>> there's extensive Belchertown Charts Documentation 
>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>  
>> which can help you get started. 
>>
>> In addition to the Charts there's now a dark mode (which has an 
>> auto-switching mode based on sunset/sunrise), more flexibility for 
>> translations, user customized station observation table which is updated in 
>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>> release notes for all the details! 
>>
>> You can download the latest release here 
>> <https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.0/weewx-belchertown-release-1.0.tar.gz>,
>>  
>> and read all of the details on the changes here: 
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>> uninstall everything and reinstall new. This is due to the Chart system 
>> being fully rewritten and the potential for conflicts. Please read this 
>> upgrade guide if you are upgrading from an older version of Belchertown skin 
>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>> . 
>>
>> Thanks to all the beta testers and translators over the last couple of 
>> months help me iron out all the kinks and shape the skin in a way that can 
>> be translated a little easier! 
>>
>> Attached are some examples of the charts that can be made. If you find 
>> any issues, you can reply here or open an issue on the Belchertown skin 
>> GitHub page <https://github.com/poblabs/weewx-belchertown>. 
>>
>

-- 
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/6ef9c708-32c5-4fab-a281-4060dc2d71b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Juan Antonio Mosquera]

Hi...

rare... i had 1.0 version... i update... and...

jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
exception in engine:
jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most recent 
call last):
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 884, in main
jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
engine_class(config_dict)
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
jun 03 20:30:43 meteomontaos weewx[4029]:   
self.loadServices(config_dict)
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
jun 03 20:30:43 meteomontaos weewx[4029]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 304, in __init__
jun 03 20:30:43 meteomontaos weewx[4029]:   
target_unit_nickname = config_dict['StdConvert']['target_unit']
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
dict.__getitem__(self, key)
jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 'StdConvert'
jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.


what problem¿?

El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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/2dc9c929-26b6-4e6c-8b9b-5e20d38278b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

thanks but it has not worked.

I have found a solution:

I put in the system es_ES and I modified the locale es_ES to put the 
decimal points. I have generated the locale (locale-gen) again and now it 
seems that it works.

Thank you.

El sábado, 25 de mayo de 2019, 17:05:36 (UTC+2), Pat escribió:
>
> Yes, so do the opposite of what I am proposing. Set your server back to 
> ES, and set skin.conf belchertown_locale to en_US.UTF-8
>
> On Saturday, May 25, 2019 at 10:32:27 AM UTC-4, Juan Antonio Mosquera 
> wrote:
>>
>> Yes, it's in the US because I want a decimal point separator. But I want 
>> to configure local ES and decimal separator with points, you understand me?
>>
>> thanks.
>>
>> El sábado, 25 de mayo de 2019, 16:28:24 (UTC+2), Pat escribió:
>>>
>>> I am on mobile right now but I can see that your locale is set to United 
>>> States English based on your weewx_data.json file on your site. You can 
>>> either change the locale on your server to be Spanish (preferred) or change 
>>> the skin.conf locale setting to not be auto and use es_ES.UTF-8. Then 
>>> restart weewx.
>>>
>>> Sent from mobile
>>>
>>> On Sat, May 25, 2019, 9:55 AM Juan Antonio Mosquera <
>>> juananton...@juanantoniomosquera.com> wrote:
>>>
>>>> ok, thanks.
>>>>
>>>> Now 1.0 is running and translate to spanish.
>>>>
>>>> a doubt. Is it possible to configure the belchertown to use a decimal 
>>>> point separator and a locale in Spanish?
>>>>
>>>> Thanks.
>>>>
>>>> El sábado, 25 de mayo de 2019, 14:25:45 (UTC+2), Pat escribió:
>>>>>
>>>>> Here's the instructions on how to upgrade, also in a couple of 
>>>>> languages. 
>>>>> https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0
>>>>>
>>>>> When 1.0 is ready for public release I'll let everyone know. Until 
>>>>> then if you want to help with the testing please raise issues on the 
>>>>> GitHub 
>>>>> page to keep it focused on the skin changes
>>>>>
>>>>> On Saturday, May 25, 2019 at 8:23:57 AM UTC-4, Pat wrote:
>>>>>>
>>>>>> Anyone is welcome to try out the 1.0 beta. There's a few people 
>>>>>> helping with the translations here at 
>>>>>> https://github.com/poblabs/weewx-belchertown/issues/104 with 165 
>>>>>> replies so far. We've made a lot of progress to use the Labels to make 
>>>>>> the 
>>>>>> skin easy to translate. 
>>>>>>
>>>>>> The charts are fully re-done and there's some documentation at 
>>>>>> https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
>>>>>>
>>>>>> I'm trying to get more of the changes documented so if you find 
>>>>>> something, you can open an issue on my GitHub repo and we can work on 
>>>>>> it. 
>>>>>>
>>>>>> You can view progress at 
>>>>>> https://github.com/poblabs/weewx-belchertown/tree/development and 
>>>>>> download with the "Clone or Download" link on that page. 
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>> On Saturday, May 25, 2019 at 6:24:18 AM UTC-4, Juan Antonio Mosquera 
>>>>>> wrote:
>>>>>>>
>>>>>>> No problem...
>>>>>>>
>>>>>>> I compress dev branch and install this beta version.
>>>>>>>
>>>>>>> www.meteomontaos.es
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> El sábado, 25 de mayo de 2019, 11:21:09 (UTC+2), Juan Antonio 
>>>>>>> Mosquera escribió:
>>>>>>>>
>>>>>>>> Where is the zip of version 1.0 beta?
>>>>>>>>
>>>>>>>> El sábado, 18 de mayo de 2019, 14:44:08 (UTC+2), Pat escribió:
>>>>>>>>>
>>>>>>>>> This is a bug which will be fixed in the next version, 1.0. It is 
>>>>>>>>> due to there being no earthquakes in your area and no timestamp being 
>>>>>>>>> available. 
>>>>>>>>>
>>>>>>>>> To fix this, either disable earth

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Yes, it's in the US because I want a decimal point separator. But I want to 
configure local ES and decimal separator with points, you understand me?

thanks.

El sábado, 25 de mayo de 2019, 16:28:24 (UTC+2), Pat escribió:
>
> I am on mobile right now but I can see that your locale is set to United 
> States English based on your weewx_data.json file on your site. You can 
> either change the locale on your server to be Spanish (preferred) or change 
> the skin.conf locale setting to not be auto and use es_ES.UTF-8. Then 
> restart weewx.
>
> Sent from mobile
>
> On Sat, May 25, 2019, 9:55 AM Juan Antonio Mosquera <
> juananton...@juanantoniomosquera.com > wrote:
>
>> ok, thanks.
>>
>> Now 1.0 is running and translate to spanish.
>>
>> a doubt. Is it possible to configure the belchertown to use a decimal 
>> point separator and a locale in Spanish?
>>
>> Thanks.
>>
>> El sábado, 25 de mayo de 2019, 14:25:45 (UTC+2), Pat escribió:
>>>
>>> Here's the instructions on how to upgrade, also in a couple of 
>>> languages. 
>>> https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0
>>>
>>> When 1.0 is ready for public release I'll let everyone know. Until then 
>>> if you want to help with the testing please raise issues on the GitHub page 
>>> to keep it focused on the skin changes
>>>
>>> On Saturday, May 25, 2019 at 8:23:57 AM UTC-4, Pat wrote:
>>>>
>>>> Anyone is welcome to try out the 1.0 beta. There's a few people helping 
>>>> with the translations here at 
>>>> https://github.com/poblabs/weewx-belchertown/issues/104 with 165 
>>>> replies so far. We've made a lot of progress to use the Labels to make the 
>>>> skin easy to translate. 
>>>>
>>>> The charts are fully re-done and there's some documentation at 
>>>> https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
>>>>
>>>> I'm trying to get more of the changes documented so if you find 
>>>> something, you can open an issue on my GitHub repo and we can work on it. 
>>>>
>>>> You can view progress at 
>>>> https://github.com/poblabs/weewx-belchertown/tree/development and 
>>>> download with the "Clone or Download" link on that page. 
>>>>
>>>> Thanks
>>>>
>>>>
>>>> On Saturday, May 25, 2019 at 6:24:18 AM UTC-4, Juan Antonio Mosquera 
>>>> wrote:
>>>>>
>>>>> No problem...
>>>>>
>>>>> I compress dev branch and install this beta version.
>>>>>
>>>>> www.meteomontaos.es
>>>>>
>>>>> Thanks.
>>>>>
>>>>> El sábado, 25 de mayo de 2019, 11:21:09 (UTC+2), Juan Antonio Mosquera 
>>>>> escribió:
>>>>>>
>>>>>> Where is the zip of version 1.0 beta?
>>>>>>
>>>>>> El sábado, 18 de mayo de 2019, 14:44:08 (UTC+2), Pat escribió:
>>>>>>>
>>>>>>> This is a bug which will be fixed in the next version, 1.0. It is 
>>>>>>> due to there being no earthquakes in your area and no timestamp being 
>>>>>>> available. 
>>>>>>>
>>>>>>> To fix this, either disable earthquakes for now by setting 
>>>>>>> earthquake_enabled 
>>>>>>> = 0
>>>>>>>
>>>>>>> Or increase your earthquake radius to something larger than your 
>>>>>>> current one. Example, 2000km. Change setting earthquake_maxradiuskm 
>>>>>>> = 2000
>>>>>>>
>>>>>>> Skin version 1.0 comes with a fully re-written Graph Generator, 
>>>>>>> automatic dark mode and more user customization and translations. If 
>>>>>>> you 
>>>>>>> want to test skin version 1.0, there's a small group of testers helping 
>>>>>>> me 
>>>>>>> test new Graph features and kill bugs. You can follow along on my 
>>>>>>> GitHub <https://github.com/poblabs/weewx-belchertown> under the 
>>>>>>> development 
>>>>>>> branch 
>>>>>>> <https://github.com/poblabs/weewx-belchertown/tree/development>, 
>>>>>>> and because the skin has been almost entirely re-written, there's 
>>>>>>> speci

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

ok, thanks.

Now 1.0 is running and translate to spanish.

a doubt. Is it possible to configure the belchertown to use a decimal point 
separator and a locale in Spanish?

Thanks.

El sábado, 25 de mayo de 2019, 14:25:45 (UTC+2), Pat escribió:
>
> Here's the instructions on how to upgrade, also in a couple of languages. 
> https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0
>
> When 1.0 is ready for public release I'll let everyone know. Until then if 
> you want to help with the testing please raise issues on the GitHub page to 
> keep it focused on the skin changes
>
> On Saturday, May 25, 2019 at 8:23:57 AM UTC-4, Pat wrote:
>>
>> Anyone is welcome to try out the 1.0 beta. There's a few people helping 
>> with the translations here at 
>> https://github.com/poblabs/weewx-belchertown/issues/104 with 165 replies 
>> so far. We've made a lot of progress to use the Labels to make the skin 
>> easy to translate. 
>>
>> The charts are fully re-done and there's some documentation at 
>> https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
>>
>> I'm trying to get more of the changes documented so if you find 
>> something, you can open an issue on my GitHub repo and we can work on it. 
>>
>> You can view progress at 
>> https://github.com/poblabs/weewx-belchertown/tree/development and 
>> download with the "Clone or Download" link on that page. 
>>
>> Thanks
>>
>>
>> On Saturday, May 25, 2019 at 6:24:18 AM UTC-4, Juan Antonio Mosquera 
>> wrote:
>>>
>>> No problem...
>>>
>>> I compress dev branch and install this beta version.
>>>
>>> www.meteomontaos.es
>>>
>>> Thanks.
>>>
>>> El sábado, 25 de mayo de 2019, 11:21:09 (UTC+2), Juan Antonio Mosquera 
>>> escribió:
>>>>
>>>> Where is the zip of version 1.0 beta?
>>>>
>>>> El sábado, 18 de mayo de 2019, 14:44:08 (UTC+2), Pat escribió:
>>>>>
>>>>> This is a bug which will be fixed in the next version, 1.0. It is due 
>>>>> to there being no earthquakes in your area and no timestamp being 
>>>>> available. 
>>>>>
>>>>> To fix this, either disable earthquakes for now by setting 
>>>>> earthquake_enabled 
>>>>> = 0
>>>>>
>>>>> Or increase your earthquake radius to something larger than your 
>>>>> current one. Example, 2000km. Change setting earthquake_maxradiuskm = 
>>>>> 2000
>>>>>
>>>>> Skin version 1.0 comes with a fully re-written Graph Generator, 
>>>>> automatic dark mode and more user customization and translations. If you 
>>>>> want to test skin version 1.0, there's a small group of testers helping 
>>>>> me 
>>>>> test new Graph features and kill bugs. You can follow along on my 
>>>>> GitHub <https://github.com/poblabs/weewx-belchertown> under the 
>>>>> development 
>>>>> branch <https://github.com/poblabs/weewx-belchertown/tree/development>, 
>>>>> and because the skin has been almost entirely re-written, there's 
>>>>> specific upgrade instructions here 
>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>>>>> . 
>>>>>
>>>>> Please understand this is a *beta version* and it's being updated 
>>>>> very frequently. Please only install if you're willing to help test the 
>>>>> new 
>>>>> features (so I can fix and document them).
>>>>>
>>>>>
>>>>> On Saturday, May 18, 2019 at 6:53:38 AM UTC-4, WILWetter25 wrote:
>>>>>>
>>>>>> Hey guys,
>>>>>>
>>>>>> I have a problem with the skin: Forecast Earth-Quakes and Graphs 
>>>>>> aren't loading any more. This problem exists only on main page.
>>>>>>
>>>>>> http://www.mosel-wetter.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/6284de7e-a344-4bea-881d-20870497b574%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

No problem...

I compress dev branch and install this beta version.

www.meteomontaos.es

Thanks.

El sábado, 25 de mayo de 2019, 11:21:09 (UTC+2), Juan Antonio Mosquera 
escribió:
>
> Where is the zip of version 1.0 beta?
>
> El sábado, 18 de mayo de 2019, 14:44:08 (UTC+2), Pat escribió:
>>
>> This is a bug which will be fixed in the next version, 1.0. It is due to 
>> there being no earthquakes in your area and no timestamp being available. 
>>
>> To fix this, either disable earthquakes for now by setting 
>> earthquake_enabled 
>> = 0
>>
>> Or increase your earthquake radius to something larger than your current 
>> one. Example, 2000km. Change setting earthquake_maxradiuskm = 2000
>>
>> Skin version 1.0 comes with a fully re-written Graph Generator, automatic 
>> dark mode and more user customization and translations. If you want to test 
>> skin version 1.0, there's a small group of testers helping me test new 
>> Graph features and kill bugs. You can follow along on my GitHub 
>> <https://github.com/poblabs/weewx-belchertown> under the development 
>> branch <https://github.com/poblabs/weewx-belchertown/tree/development>, 
>> and because the skin has been almost entirely re-written, there's 
>> specific upgrade instructions here 
>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>> . 
>>
>> Please understand this is a *beta version* and it's being updated very 
>> frequently. Please only install if you're willing to help test the new 
>> features (so I can fix and document them).
>>
>>
>> On Saturday, May 18, 2019 at 6:53:38 AM UTC-4, WILWetter25 wrote:
>>>
>>> Hey guys,
>>>
>>> I have a problem with the skin: Forecast Earth-Quakes and Graphs aren't 
>>> loading any more. This problem exists only on main page.
>>>
>>> http://www.mosel-wetter.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/55c677bd-c695-4e74-9f15-fdf9d15591a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Where is the zip of version 1.0 beta?

El sábado, 18 de mayo de 2019, 14:44:08 (UTC+2), Pat escribió:
>
> This is a bug which will be fixed in the next version, 1.0. It is due to 
> there being no earthquakes in your area and no timestamp being available. 
>
> To fix this, either disable earthquakes for now by setting earthquake_enabled 
> = 0
>
> Or increase your earthquake radius to something larger than your current 
> one. Example, 2000km. Change setting earthquake_maxradiuskm = 2000
>
> Skin version 1.0 comes with a fully re-written Graph Generator, automatic 
> dark mode and more user customization and translations. If you want to test 
> skin version 1.0, there's a small group of testers helping me test new 
> Graph features and kill bugs. You can follow along on my GitHub 
>  under the development 
> branch , 
> and because the skin has been almost entirely re-written, there's 
> specific upgrade instructions here 
> 
> . 
>
> Please understand this is a *beta version* and it's being updated very 
> frequently. Please only install if you're willing to help test the new 
> features (so I can fix and document them).
>
>
> On Saturday, May 18, 2019 at 6:53:38 AM UTC-4, WILWetter25 wrote:
>>
>> Hey guys,
>>
>> I have a problem with the skin: Forecast Earth-Quakes and Graphs aren't 
>> loading any more. This problem exists only on main page.
>>
>> http://www.mosel-wetter.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/3b2ac1c6-2b52-49f0-b5cd-a9203d6852b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Hello,

I want to try the DEV version of Belchertown at www.meteomontaos.gal
What is the procedure ?.
You could also collaborate in the Spanish and Galician translation 
(https://github.com/juanantoniomosquera/weewx-belchertown)

Greetings.

El sábado, 18 de mayo de 2019, 14:44:08 (UTC+2), Pat escribió:
>
> This is a bug which will be fixed in the next version, 1.0. It is due to 
> there being no earthquakes in your area and no timestamp being available. 
>
> To fix this, either disable earthquakes for now by setting earthquake_enabled 
> = 0
>
> Or increase your earthquake radius to something larger than your current 
> one. Example, 2000km. Change setting earthquake_maxradiuskm = 2000
>
> Skin version 1.0 comes with a fully re-written Graph Generator, automatic 
> dark mode and more user customization and translations. If you want to test 
> skin version 1.0, there's a small group of testers helping me test new 
> Graph features and kill bugs. You can follow along on my GitHub 
>  under the development 
> branch , 
> and because the skin has been almost entirely re-written, there's 
> specific upgrade instructions here 
> 
> . 
>
> Please understand this is a *beta version* and it's being updated very 
> frequently. Please only install if you're willing to help test the new 
> features (so I can fix and document them).
>
>
> On Saturday, May 18, 2019 at 6:53:38 AM UTC-4, WILWetter25 wrote:
>>
>> Hey guys,
>>
>> I have a problem with the skin: Forecast Earth-Quakes and Graphs aren't 
>> loading any more. This problem exists only on main page.
>>
>> http://www.mosel-wetter.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/02c0d9db-4c5b-4fff-b6eb-8ab5248fb36e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: FTPS over TLS problem (time out)

[Juan Antonio Mosquera]

help?

I cant upload to FTPS server...

Thanks.

El martes, 26 de febrero de 2019, 12:49:12 (UTC+1), Juan Antonio Mosquera 
escribió:
>
> Hello,
>
> I'm trying to connect to an FTPS (implicit TLS) and get a time out.
> If I do a test with FileZilla, first I have to accept the certificate and 
> then I can connect without problems.
>
> Set passive mode to 1 and secure_ftp to True. The port indicated 990.
>
> I use a raspberry with raspbian. I have to accept the certificate in some 
> way or I have bad conf.
>
> [[FTP]]
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> skin = Ftp
> 
>
> HTML_ROOT = / var / www / html / weewx / 
>  
>
>
> # If you want to use FTP, set "enable" to "true", then
> # fill out the next four lines.
> # Use quotes around passwords to guard against parsing errors.
> enable = true
> user = 
> password = 
> server = ftp..XX # The ftp server name, e.g, www.myserver.org
> path = / # The destination directory, e.g., / weather
>
> # Set to True for an FTP over TLS (FTPS) connection. Not all 
> servers
> # support this.
> secure_ftp = True
>
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> #HTML_ROOT = / var / www / html / weewx
>
> # Most FTP servers use port 21
> port = 990
>
> # Set to 1 to use passive mode, zero for active mode
> passive = 1
>
> max_tries = 3
>
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b860091f-9e61-4e24-a8c5-98c68113b189%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

hi,

One problem today:

www.meteomontaos.gal

i think... earthquake problem

[image: errorearth.JPG]



Thanks.
  

El domingo, 17 de marzo de 2019, 23:57:11 (UTC+1), Pat escribió:
>
> Thanks I'll look into it
>
> On Sunday, March 17, 2019 at 5:26:17 PM UTC-4, Adnan Mumtaz wrote:
>>
>> https://www.airvisual.com/air-pollution-data-api
>>
>>
>> On Sunday, 17 March 2019 20:54:21 UTC+3, Pat wrote:
>>>
>>> Do you have a source where we can get air quality data?
>>>
>>> On Sunday, March 17, 2019 at 1:03:37 PM UTC-4, Adnan Mumtaz wrote:

 Wow :) I will definitely then wait for 1.0. 

 Will try to use the beta.

 Thanks a million once again. 

 One suggestion, if instead of Earth Quake you can add an option of Air 
 Quality would be great, we have more issues of air quality than earth 
 quakes :)

 On Sunday, 17 March 2019 19:25:09 UTC+3, Pat wrote:
>
> Skin version 1.0 offers an entire new way to customize charts. From 
> re-ordering, to adding custom observations, to multiple yAxis. 
>
> If you're OK with staying on a skin version that works for you, then 
> that would be great. That way I don't have to release a 0.9.2 when 1.0 is 
> only a couple of weeks away. 
>
> If you want to test 1.0 now, you can download the development branch 
> zip file 
>  of 
> the skin. Be warned it's *very beta* with little documentation right 
> now. The only documentation is in skin.conf currently. And I'm pushing 
> updates to the skin daily. If you test it, and find something wrong, let 
> me 
> know so I can update it :)
>
> On Sunday, March 17, 2019 at 12:15:16 PM UTC-4, Adnan Mumtaz wrote:
>>
>> Hi ,
>>
>> Many thanks for your hardwork, I upgraded to the latest Belchertown 
>> template 0.9.1 after upgrading weewx, everything seems working fine, I 
>> can 
>> see intemp showing in temp chart, I tried to disable intemp from the 
>> weewx.conf and after doing that the temp chart goes upside down it shows 
>> years instead of hours and doesnt show graph, i also tried to change the 
>> rainplot to humidity after doing that Rain chart as well as Solar chart 
>> disappeared, I dont see any errors in the syslog, I reverted back all 
>> the 
>> changes though . Mayb you can simulate these in your test environment?
>>
>> thank you,
>> Adnan
>>
>>
>>
>> On Friday, 1 March 2019 03:50:34 UTC+3, Pat wrote:
>>>
>>> I've just released Belchertown skin 0.9. You can read the updates 
>>> and download it here: 
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>> A lot of work went into this release. I've learned a lot through 
>>> feedback on the skin. 
>>>
>>> This release fixes a major bug with the rain charts which were 
>>> taking a very long time to generate. This release also brings a lot of 
>>> updates to locale formats. 
>>>
>>> *There's 1 breaking change if you are upgrading*. Please take 
>>> special note to a few MQTT variable names which have changed to 
>>> mqtt_websockets_. This is to reduce confusion and offer clarity on 
>>> new user installations. 
>>>
>>> Please let me know if you've upgraded and share your site. I'd love 
>>> to see it out there!
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Sorry... 

ES = comma!...

I was thinking of separators of thousands!!. my fault.

El lunes, 4 de marzo de 2019, 21:37:32 (UTC+1), Pat escribió:
>
> My mistake. I thought you wanted comma because when I set my server to 
> es_ES.UTF-8 like yours, I get commas, too. 
>
>
>
>
>
> On Monday, March 4, 2019 at 3:35:28 PM UTC-5, Juan Antonio Mosquera wrote:
>>
>> but wind too... 
>>
>> attach image
>>
>> On Mon, 4 Mar 2019, 21:32 Pat,  wrote:
>>
>>> I am seeing the same thing with DarkSky. You may have to reach out to 
>>> DarkSky through your darksky.net portal and ask them how come it's not 
>>> a comma. They are controlling the data when it's downloaded. 
>>>
>>> I would ask them that you specify "lang=es" but the locale of the units 
>>> is not using commas. 
>>>
>>> On Monday, March 4, 2019 at 3:22:09 PM UTC-5, Juan Antonio Mosquera 
>>> wrote:
>>>>
>>>> Half-solved problem. Now show comma separators. ES locale is dot 
>>>> separation.
>>>>
>>>> thank you.
>>>>
>>>> El lunes, 4 de marzo de 2019, 21:09:57 (UTC+1), Pat escribió:
>>>>>
>>>>> Juan, I think I have this fixed. You can download the file below. I 
>>>>> think this has opened up a couple more issues with locale that I'm 
>>>>> looking 
>>>>> into now, but for your issue it seems this will do it. 
>>>>>
>>>>> Replace skins/Belchertown/index.html.tmpl with this 
>>>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/ff81af12710062ff78236fbc49ea4d9ac1798908/skins/Belchertown/index.html.tmpl
>>>>>
>>>>> Wait for an archive interval and see if it's updated
>>>>>
>>>>> On Monday, March 4, 2019 at 1:54:26 PM UTC-5, Juan Antonio Mosquera 
>>>>> wrote:
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Mon, 4 Mar 2019, 19:52 Pat,  wrote:
>>>>>>
>>>>>>> I will try some testing in a couple of hours to see if I can figure 
>>>>>>> it out
>>>>>>>
>>>>>>> On Monday, March 4, 2019 at 1:51:43 PM UTC-5, Juan Antonio Mosquera 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> hi,
>>>>>>>>
>>>>>>>> locale:
>>>>>>>>
>>>>>>>> pi@meteomontaos:~ $ locale
>>>>>>>> LANG=es_ES.UTF-8
>>>>>>>> LANGUAGE=
>>>>>>>> LC_CTYPE="es_ES.UTF-8"
>>>>>>>> LC_NUMERIC="es_ES.UTF-8"
>>>>>>>> LC_TIME="es_ES.UTF-8"
>>>>>>>> LC_COLLATE="es_ES.UTF-8"
>>>>>>>> LC_MONETARY="es_ES.UTF-8"
>>>>>>>> LC_MESSAGES="es_ES.UTF-8"
>>>>>>>> LC_PAPER="es_ES.UTF-8"
>>>>>>>> LC_NAME="es_ES.UTF-8"
>>>>>>>> LC_ADDRESS="es_ES.UTF-8"
>>>>>>>> LC_TELEPHONE="es_ES.UTF-8"
>>>>>>>> LC_MEASUREMENT="es_ES.UTF-8"
>>>>>>>> LC_IDENTIFICATION="es_ES.UTF-8"
>>>>>>>> LC_ALL=
>>>>>>>>
>>>>>>>>
>>>>>>>> And... my darksky_lang is "es"
>>>>>>>>
>>>>>>>> El lunes, 4 de marzo de 2019, 19:46:12 (UTC+1), Pat escribió:
>>>>>>>>>
>>>>>>>>> Juan, interesting. With Visibility make sure you set darksky_lang 
>>>>>>>>> <https://github.com/poblabs/weewx-belchertown#forecast-options> which 
>>>>>>>>> should match the comma for your language. 
>>>>>>>>>
>>>>>>>>> The Wind Gust should be matching Wind Speed though. I am not sure 
>>>>>>>>> why it is not. 
>>>>>>>>>
>>>>>>>>> On your weewx server, can you type *locale *at command line and 
>>>>>>>>> paste the output?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Monday, March 4, 2019 at 1:40:54 PM UTC-5, Juan Antonio 
>>>>>>>>> Mosquera wrote:
>>>>>>>>>>
&

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Half-solved problem. Now show comma separators. ES locale is dot separation.

thank you.

El lunes, 4 de marzo de 2019, 21:09:57 (UTC+1), Pat escribió:
>
> Juan, I think I have this fixed. You can download the file below. I think 
> this has opened up a couple more issues with locale that I'm looking into 
> now, but for your issue it seems this will do it. 
>
> Replace skins/Belchertown/index.html.tmpl with this 
> https://raw.githubusercontent.com/poblabs/weewx-belchertown/ff81af12710062ff78236fbc49ea4d9ac1798908/skins/Belchertown/index.html.tmpl
>
> Wait for an archive interval and see if it's updated
>
> On Monday, March 4, 2019 at 1:54:26 PM UTC-5, Juan Antonio Mosquera wrote:
>>
>> Thanks!
>>
>> On Mon, 4 Mar 2019, 19:52 Pat,  wrote:
>>
>>> I will try some testing in a couple of hours to see if I can figure it 
>>> out
>>>
>>> On Monday, March 4, 2019 at 1:51:43 PM UTC-5, Juan Antonio Mosquera 
>>> wrote:
>>>>
>>>> hi,
>>>>
>>>> locale:
>>>>
>>>> pi@meteomontaos:~ $ locale
>>>> LANG=es_ES.UTF-8
>>>> LANGUAGE=
>>>> LC_CTYPE="es_ES.UTF-8"
>>>> LC_NUMERIC="es_ES.UTF-8"
>>>> LC_TIME="es_ES.UTF-8"
>>>> LC_COLLATE="es_ES.UTF-8"
>>>> LC_MONETARY="es_ES.UTF-8"
>>>> LC_MESSAGES="es_ES.UTF-8"
>>>> LC_PAPER="es_ES.UTF-8"
>>>> LC_NAME="es_ES.UTF-8"
>>>> LC_ADDRESS="es_ES.UTF-8"
>>>> LC_TELEPHONE="es_ES.UTF-8"
>>>> LC_MEASUREMENT="es_ES.UTF-8"
>>>> LC_IDENTIFICATION="es_ES.UTF-8"
>>>> LC_ALL=
>>>>
>>>>
>>>> And... my darksky_lang is "es"
>>>>
>>>> El lunes, 4 de marzo de 2019, 19:46:12 (UTC+1), Pat escribió:
>>>>>
>>>>> Juan, interesting. With Visibility make sure you set darksky_lang 
>>>>> <https://github.com/poblabs/weewx-belchertown#forecast-options> which 
>>>>> should match the comma for your language. 
>>>>>
>>>>> The Wind Gust should be matching Wind Speed though. I am not sure why 
>>>>> it is not. 
>>>>>
>>>>> On your weewx server, can you type *locale *at command line and paste 
>>>>> the output?
>>>>>
>>>>>
>>>>> On Monday, March 4, 2019 at 1:40:54 PM UTC-5, Juan Antonio Mosquera 
>>>>> wrote:
>>>>>>
>>>>>> Hi...
>>>>>> problem wit units 
>>>>>>
>>>>>> commas and dots...
>>>>>>
>>>>>> How do I unify the decimal separation?
>>>>>>
>>>>>> [image: Captura de pantalla de 2019-03-04 19-39-07.png]
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> El domingo, 3 de marzo de 2019, 22:50:47 (UTC+1), Pat escribió:
>>>>>>>
>>>>>>> Good news thank you
>>>>>>>
>>>>>>> On Sunday, March 3, 2019 at 4:35:49 PM UTC-5, Juan Antonio Mosquera 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> ok,
>>>>>>>>
>>>>>>>> Now works again... with these changes...
>>>>>>>>
>>>>>>>> thanks.
>>>>>>>>
>>>>>>>> El domingo, 3 de marzo de 2019, 21:34:04 (UTC+1), Pat escribió:
>>>>>>>>>
>>>>>>>>> Juan, I made some changes. Can you try this and see if it helps?
>>>>>>>>>
>>>>>>>>> Copy these files and place them in these folders:
>>>>>>>>>
>>>>>>>>> bin/user/belchertown.py ---> 
>>>>>>>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/bin/user/belchertown.py
>>>>>>>>>
>>>>>>>>> skins/Belchertown/js/highcharts-dayplots.js.tmpl ---> 
>>>>>>>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/skins/Belchertown/js/highcharts-dayplots.js.tmpl
>>>>>>>>>
>>>>&

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

hi,

locale:

pi@meteomontaos:~ $ locale
LANG=es_ES.UTF-8
LANGUAGE=
LC_CTYPE="es_ES.UTF-8"
LC_NUMERIC="es_ES.UTF-8"
LC_TIME="es_ES.UTF-8"
LC_COLLATE="es_ES.UTF-8"
LC_MONETARY="es_ES.UTF-8"
LC_MESSAGES="es_ES.UTF-8"
LC_PAPER="es_ES.UTF-8"
LC_NAME="es_ES.UTF-8"
LC_ADDRESS="es_ES.UTF-8"
LC_TELEPHONE="es_ES.UTF-8"
LC_MEASUREMENT="es_ES.UTF-8"
LC_IDENTIFICATION="es_ES.UTF-8"
LC_ALL=


And... my darksky_lang is "es"

El lunes, 4 de marzo de 2019, 19:46:12 (UTC+1), Pat escribió:
>
> Juan, interesting. With Visibility make sure you set darksky_lang 
> <https://github.com/poblabs/weewx-belchertown#forecast-options> which 
> should match the comma for your language. 
>
> The Wind Gust should be matching Wind Speed though. I am not sure why it 
> is not. 
>
> On your weewx server, can you type *locale *at command line and paste the 
> output?
>
>
> On Monday, March 4, 2019 at 1:40:54 PM UTC-5, Juan Antonio Mosquera wrote:
>>
>> Hi...
>> problem wit units 
>>
>> commas and dots...
>>
>> How do I unify the decimal separation?
>>
>> [image: Captura de pantalla de 2019-03-04 19-39-07.png]
>>
>>
>>
>>
>>
>>
>>
>> El domingo, 3 de marzo de 2019, 22:50:47 (UTC+1), Pat escribió:
>>>
>>> Good news thank you
>>>
>>> On Sunday, March 3, 2019 at 4:35:49 PM UTC-5, Juan Antonio Mosquera 
>>> wrote:
>>>>
>>>> ok,
>>>>
>>>> Now works again... with these changes...
>>>>
>>>> thanks.
>>>>
>>>> El domingo, 3 de marzo de 2019, 21:34:04 (UTC+1), Pat escribió:
>>>>>
>>>>> Juan, I made some changes. Can you try this and see if it helps?
>>>>>
>>>>> Copy these files and place them in these folders:
>>>>>
>>>>> bin/user/belchertown.py ---> 
>>>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/bin/user/belchertown.py
>>>>>
>>>>> skins/Belchertown/js/highcharts-dayplots.js.tmpl ---> 
>>>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/skins/Belchertown/js/highcharts-dayplots.js.tmpl
>>>>>
>>>>> Restart weewx and see if the next archive interval shows your graphs?
>>>>>
>>>>> On Sunday, March 3, 2019 at 3:16:19 PM UTC-5, Pat wrote:
>>>>>>
>>>>>> I see now. What is your archive interval from weewx.conf? Looks like 
>>>>>> the new gapSize option isn't working well for you. 
>>>>>>
>>>>>> On Sunday, March 3, 2019 at 3:12:57 PM UTC-5, Juan Antonio Mosquera 
>>>>>> wrote:
>>>>>>>
>>>>>>> Only work windDirection chart.
>>>>>>>
>>>>>>> El domingo, 3 de marzo de 2019, 20:46:50 (UTC+1), Pat escribió:
>>>>>>>>
>>>>>>>> I need more information than that. A website? A post of your config 
>>>>>>>> files?
>>>>>>>>
>>>>>>>> On Sunday, March 3, 2019 at 2:39:13 PM UTC-5, Juan Antonio Mosquera 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Not... graphs not work... no errors in console... 
>>>>>>>>>
>>>>>>>>> El domingo, 3 de marzo de 2019, 20:27:41 (UTC+1), Juan Antonio 
>>>>>>>>> Mosquera escribió:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I updated to 0.9 version and.. not work highcharts graphs 
>>>>>>>>>> (today). week works fine.
>>>>>>>>>>
>>>>>>>>>> conf problem?
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>>>>>>>>>>>
>>>>>>>>>>> I've just released Belchertown skin 0.9. You can read the 
>>>>>>>>>>> updates and download it here: 
>>>>>>>>>>> https://github.com/poblabs/weewx-belchertown/releases
>>>>>>>>>>>
>>>>>>>>>>> A lot of work went into this release. I've learned a lot through 
>>>>>>>>>>> feedback on the skin. 
>>>>>>>>>>>
>>>>>>>>>>> This release fixes a major bug with the rain charts which were 
>>>>>>>>>>> taking a very long time to generate. This release also brings a lot 
>>>>>>>>>>> of 
>>>>>>>>>>> updates to locale formats. 
>>>>>>>>>>>
>>>>>>>>>>> *There's 1 breaking change if you are upgrading*. Please take 
>>>>>>>>>>> special note to a few MQTT variable names which have changed to 
>>>>>>>>>>> mqtt_websockets_. This is to reduce confusion and offer clarity 
>>>>>>>>>>> on new user installations. 
>>>>>>>>>>>
>>>>>>>>>>> Please let me know if you've upgraded and share your site. I'd 
>>>>>>>>>>> love to see it out there!
>>>>>>>>>>>
>>>>>>>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Hi...
problem wit units 

commas and dots...

How do I unify the decimal separation?

[image: Captura de pantalla de 2019-03-04 19-39-07.png]







El domingo, 3 de marzo de 2019, 22:50:47 (UTC+1), Pat escribió:
>
> Good news thank you
>
> On Sunday, March 3, 2019 at 4:35:49 PM UTC-5, Juan Antonio Mosquera wrote:
>>
>> ok,
>>
>> Now works again... with these changes...
>>
>> thanks.
>>
>> El domingo, 3 de marzo de 2019, 21:34:04 (UTC+1), Pat escribió:
>>>
>>> Juan, I made some changes. Can you try this and see if it helps?
>>>
>>> Copy these files and place them in these folders:
>>>
>>> bin/user/belchertown.py ---> 
>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/bin/user/belchertown.py
>>>
>>> skins/Belchertown/js/highcharts-dayplots.js.tmpl ---> 
>>> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/skins/Belchertown/js/highcharts-dayplots.js.tmpl
>>>
>>> Restart weewx and see if the next archive interval shows your graphs?
>>>
>>> On Sunday, March 3, 2019 at 3:16:19 PM UTC-5, Pat wrote:
>>>>
>>>> I see now. What is your archive interval from weewx.conf? Looks like 
>>>> the new gapSize option isn't working well for you. 
>>>>
>>>> On Sunday, March 3, 2019 at 3:12:57 PM UTC-5, Juan Antonio Mosquera 
>>>> wrote:
>>>>>
>>>>> Only work windDirection chart.
>>>>>
>>>>> El domingo, 3 de marzo de 2019, 20:46:50 (UTC+1), Pat escribió:
>>>>>>
>>>>>> I need more information than that. A website? A post of your config 
>>>>>> files?
>>>>>>
>>>>>> On Sunday, March 3, 2019 at 2:39:13 PM UTC-5, Juan Antonio Mosquera 
>>>>>> wrote:
>>>>>>>
>>>>>>> Not... graphs not work... no errors in console... 
>>>>>>>
>>>>>>> El domingo, 3 de marzo de 2019, 20:27:41 (UTC+1), Juan Antonio 
>>>>>>> Mosquera escribió:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I updated to 0.9 version and.. not work highcharts graphs (today). 
>>>>>>>> week works fine.
>>>>>>>>
>>>>>>>> conf problem?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>>>>>>>>>
>>>>>>>>> I've just released Belchertown skin 0.9. You can read the updates 
>>>>>>>>> and download it here: 
>>>>>>>>> https://github.com/poblabs/weewx-belchertown/releases
>>>>>>>>>
>>>>>>>>> A lot of work went into this release. I've learned a lot through 
>>>>>>>>> feedback on the skin. 
>>>>>>>>>
>>>>>>>>> This release fixes a major bug with the rain charts which were 
>>>>>>>>> taking a very long time to generate. This release also brings a lot 
>>>>>>>>> of 
>>>>>>>>> updates to locale formats. 
>>>>>>>>>
>>>>>>>>> *There's 1 breaking change if you are upgrading*. Please take 
>>>>>>>>> special note to a few MQTT variable names which have changed to 
>>>>>>>>> mqtt_websockets_. This is to reduce confusion and offer clarity 
>>>>>>>>> on new user installations. 
>>>>>>>>>
>>>>>>>>> Please let me know if you've upgraded and share your site. I'd 
>>>>>>>>> love to see it out there!
>>>>>>>>>
>>>>>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

ok,

Now works again... with these changes...

thanks.

El domingo, 3 de marzo de 2019, 21:34:04 (UTC+1), Pat escribió:
>
> Juan, I made some changes. Can you try this and see if it helps?
>
> Copy these files and place them in these folders:
>
> bin/user/belchertown.py ---> 
> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/bin/user/belchertown.py
>
> skins/Belchertown/js/highcharts-dayplots.js.tmpl ---> 
> https://raw.githubusercontent.com/poblabs/weewx-belchertown/32b30e6825ede95647f75488b400855a6d2b4a9e/skins/Belchertown/js/highcharts-dayplots.js.tmpl
>
> Restart weewx and see if the next archive interval shows your graphs?
>
> On Sunday, March 3, 2019 at 3:16:19 PM UTC-5, Pat wrote:
>>
>> I see now. What is your archive interval from weewx.conf? Looks like the 
>> new gapSize option isn't working well for you. 
>>
>> On Sunday, March 3, 2019 at 3:12:57 PM UTC-5, Juan Antonio Mosquera wrote:
>>>
>>> Only work windDirection chart.
>>>
>>> El domingo, 3 de marzo de 2019, 20:46:50 (UTC+1), Pat escribió:
>>>>
>>>> I need more information than that. A website? A post of your config 
>>>> files?
>>>>
>>>> On Sunday, March 3, 2019 at 2:39:13 PM UTC-5, Juan Antonio Mosquera 
>>>> wrote:
>>>>>
>>>>> Not... graphs not work... no errors in console... 
>>>>>
>>>>> El domingo, 3 de marzo de 2019, 20:27:41 (UTC+1), Juan Antonio 
>>>>> Mosquera escribió:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I updated to 0.9 version and.. not work highcharts graphs (today). 
>>>>>> week works fine.
>>>>>>
>>>>>> conf problem?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>>>>>>>
>>>>>>> I've just released Belchertown skin 0.9. You can read the updates 
>>>>>>> and download it here: 
>>>>>>> https://github.com/poblabs/weewx-belchertown/releases
>>>>>>>
>>>>>>> A lot of work went into this release. I've learned a lot through 
>>>>>>> feedback on the skin. 
>>>>>>>
>>>>>>> This release fixes a major bug with the rain charts which were 
>>>>>>> taking a very long time to generate. This release also brings a lot of 
>>>>>>> updates to locale formats. 
>>>>>>>
>>>>>>> *There's 1 breaking change if you are upgrading*. Please take 
>>>>>>> special note to a few MQTT variable names which have changed to 
>>>>>>> mqtt_websockets_. This is to reduce confusion and offer clarity on 
>>>>>>> new user installations. 
>>>>>>>
>>>>>>> Please let me know if you've upgraded and share your site. I'd love 
>>>>>>> to see it out there!
>>>>>>>
>>>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

sorry...

my web www.meteomontaos.es


part of weewx.conf

[[Highcharts_Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Highcharts_Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = mbar
group_rain = mm
group_rainrate = mm_per_hour
group_speed = km_per_hour
group_speed2 = km_per_hour2
group_temperature = degree_C

[[Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = mbar
group_rain = mm
group_rainrate = mm_per_hour
group_speed = km_per_hour
group_speed2 = km_per_hour2
group_temperature = degree_C
[[[Extras]]]
logo_image = 
http://www.meteomontaos.es/images/logo_meteomontaos1.png
footer_copyright_text = meteomontaos.es
forecast_enabled = 1
forecast_alert_enabled = 1
darksky_secret_key = XCXXXCC
earthquake_enabled = 1
twitter_enabled = 1
twitter_owner = mosqueracasais
highcharts_enabled = 1
radar_html = https://embed.windy.com/embed2.html?lat=42.771=-7.679=7=surface=rain==truemap=coordinates==43.330=-8.358=km%2Fh=default=-1;
 
frameborder="0">
highcharts_graph_1 = temperatureplot
highcharts_graph_2 = rainplot
highcharts_graph_3 = windplot
highcharts_graph_4 = winddirplot
highcharts_graph_5 = barometerplot
highcharts_graph_6 = humidityplot


El domingo, 3 de marzo de 2019, 20:46:50 (UTC+1), Pat escribió:
>
> I need more information than that. A website? A post of your config files?
>
> On Sunday, March 3, 2019 at 2:39:13 PM UTC-5, Juan Antonio Mosquera wrote:
>>
>> Not... graphs not work... no errors in console... 
>>
>> El domingo, 3 de marzo de 2019, 20:27:41 (UTC+1), Juan Antonio Mosquera 
>> escribió:
>>>
>>> Hi,
>>>
>>> I updated to 0.9 version and.. not work highcharts graphs (today). week 
>>> works fine.
>>>
>>> conf problem?
>>>
>>> Thanks
>>>
>>> El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>>>>
>>>> I've just released Belchertown skin 0.9. You can read the updates and 
>>>> download it here: https://github.com/poblabs/weewx-belchertown/releases
>>>>
>>>> A lot of work went into this release. I've learned a lot through 
>>>> feedback on the skin. 
>>>>
>>>> This release fixes a major bug with the rain charts which were taking a 
>>>> very long time to generate. This release also brings a lot of updates to 
>>>> locale formats. 
>>>>
>>>> *There's 1 breaking change if you are upgrading*. Please take special 
>>>> note to a few MQTT variable names which have changed to 
>>>> mqtt_websockets_. This is to reduce confusion and offer clarity on new 
>>>> user installations. 
>>>>
>>>> Please let me know if you've upgraded and share your site. I'd love to 
>>>> see it out there!
>>>>
>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Sorry...

www.meteomontaos.es



weewx.conf


[[Highcharts_Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Highcharts_Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = mbar
group_rain = mm
group_rainrate = mm_per_hour
group_speed = km_per_hour
group_speed2 = km_per_hour2
group_temperature = degree_C

[[Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = mbar
group_rain = mm
group_rainrate = mm_per_hour
group_speed = km_per_hour
group_speed2 = km_per_hour2
group_temperature = degree_C
[[[Extras]]]
logo_image = 
http://www.meteomontaos.es/images/logo_meteomontaos1.png
footer_copyright_text = meteomontaos.es
forecast_enabled = 1
forecast_alert_enabled = 1
darksky_secret_key = 87b303e052399fc195e9c8be46752fdd
earthquake_enabled = 1
twitter_enabled = 1
twitter_owner = mosqueracasais
highcharts_enabled = 1
radar_html = https://embed.windy.com/embed2.html?lat=42.771=-7.679=7=surface=rain==truemap=coordinates==43.330=-8.358=km%2Fh=default=-1;
 
frameborder="0">
highcharts_graph_1 = temperatureplot
highcharts_graph_2 = rainplot
highcharts_graph_3 = windplot
highcharts_graph_4 = winddirplot
highcharts_graph_5 = barometerplot
highcharts_graph_6 = humidityplot






El domingo, 3 de marzo de 2019, 20:46:50 (UTC+1), Pat escribió:
>
> I need more information than that. A website? A post of your config files?
>
> On Sunday, March 3, 2019 at 2:39:13 PM UTC-5, Juan Antonio Mosquera wrote:
>>
>> Not... graphs not work... no errors in console... 
>>
>> El domingo, 3 de marzo de 2019, 20:27:41 (UTC+1), Juan Antonio Mosquera 
>> escribió:
>>>
>>> Hi,
>>>
>>> I updated to 0.9 version and.. not work highcharts graphs (today). week 
>>> works fine.
>>>
>>> conf problem?
>>>
>>> Thanks
>>>
>>> El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>>>>
>>>> I've just released Belchertown skin 0.9. You can read the updates and 
>>>> download it here: https://github.com/poblabs/weewx-belchertown/releases
>>>>
>>>> A lot of work went into this release. I've learned a lot through 
>>>> feedback on the skin. 
>>>>
>>>> This release fixes a major bug with the rain charts which were taking a 
>>>> very long time to generate. This release also brings a lot of updates to 
>>>> locale formats. 
>>>>
>>>> *There's 1 breaking change if you are upgrading*. Please take special 
>>>> note to a few MQTT variable names which have changed to 
>>>> mqtt_websockets_. This is to reduce confusion and offer clarity on new 
>>>> user installations. 
>>>>
>>>> Please let me know if you've upgraded and share your site. I'd love to 
>>>> see it out there!
>>>>
>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Not... graphs not work... no errors in console... 

El domingo, 3 de marzo de 2019, 20:27:41 (UTC+1), Juan Antonio Mosquera 
escribió:
>
> Hi,
>
> I updated to 0.9 version and.. not work highcharts graphs (today). week 
> works fine.
>
> conf problem?
>
> Thanks
>
> El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>>
>> I've just released Belchertown skin 0.9. You can read the updates and 
>> download it here: https://github.com/poblabs/weewx-belchertown/releases
>>
>> A lot of work went into this release. I've learned a lot through feedback 
>> on the skin. 
>>
>> This release fixes a major bug with the rain charts which were taking a 
>> very long time to generate. This release also brings a lot of updates to 
>> locale formats. 
>>
>> *There's 1 breaking change if you are upgrading*. Please take special 
>> note to a few MQTT variable names which have changed to mqtt_websockets_. 
>> This is to reduce confusion and offer clarity on new user installations. 
>>
>> Please let me know if you've upgraded and share your site. I'd love to 
>> see it out there!
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 0.9 now available

[Juan Antonio Mosquera]

Hi,

I updated to 0.9 version and.. not work highcharts graphs (today). week 
works fine.

conf problem?

Thanks

El viernes, 1 de marzo de 2019, 1:50:34 (UTC+1), Pat escribió:
>
> I've just released Belchertown skin 0.9. You can read the updates and 
> download it here: https://github.com/poblabs/weewx-belchertown/releases
>
> A lot of work went into this release. I've learned a lot through feedback 
> on the skin. 
>
> This release fixes a major bug with the rain charts which were taking a 
> very long time to generate. This release also brings a lot of updates to 
> locale formats. 
>
> *There's 1 breaking change if you are upgrading*. Please take special 
> note to a few MQTT variable names which have changed to mqtt_websockets_. 
> This is to reduce confusion and offer clarity on new user installations. 
>
> Please let me know if you've upgraded and share your site. I'd love to see 
> it out there!
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] FTPS over TLS problem (time out)

[Juan Antonio Mosquera]

Hello,

I'm trying to connect to an FTPS (implicit TLS) and get a time out.
If I do a test with FileZilla, first I have to accept the certificate and 
then I can connect without problems.

Set passive mode to 1 and secure_ftp to True. The port indicated 990.

I use a raspberry with raspbian. I have to accept the certificate in some 
way or I have bad conf.

[[FTP]]
# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
skin = Ftp


HTML_ROOT = / var / www / html / weewx / 
 


# If you want to use FTP, set "enable" to "true", then
# fill out the next four lines.
# Use quotes around passwords to guard against parsing errors.
enable = true
user = 
password = 
server = ftp..XX # The ftp server name, e.g, www.myserver.org
path = / # The destination directory, e.g., / weather

# Set to True for an FTP over TLS (FTPS) connection. Not all servers
# support this.
secure_ftp = True

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
#HTML_ROOT = / var / www / html / weewx

# Most FTP servers use port 21
port = 990

# Set to 1 to use passive mode, zero for active mode
passive = 1

max_tries = 3

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Error changing raspberry

[Juan Antonio Mosquera]

Thanks Thomas,

Clean data and all OK again.

Great work!

El viernes, 22 de febrero de 2019, 21:38:32 (UTC+1), Thomas Keffer escribió:
>
> The bad data point has probably been there all along --- it's just that 
> WeeWX is a little more strict about it.
>
> Try this on your database. *Boldface* is things you type.
>
> # Change directory to where you database is located. Adjust as necessary
> *cd /var/lib/weewx*
> # Make a backup copy of your database:
> *sudo cp weewx.sdb weewx.sdb.backup*
> # Install sqlite3 if you have not already:
> *sudo apt install sqlite3*
> # Run it against the WeeWX database:
> *sudo sqlite3 weewx.sdb*
> # See how many bad records there are:
> sqlite> *select count(dateTime) from archive where interval <= 0;*
> # Get rid of them:
> sqlite> *delete from archive where interval <= 0;*
> sqlite> *.exit*
>
> -tk
>
> On Fri, Feb 22, 2019 at 10:06 AM Juan Antonio Mosquera <
> juananton...@juanantoniomosquera.com > wrote:
>
>> I'm changing the raspberry b + to raspberry 2.
>>
>> I have this problem when I do rebuild of weewx.sdb
>>
>> Feb 22 19:03:20 meteomontaos weewx [15992]: engine: Caught unrecoverable 
>> exception in engine:
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  Non-positive value for 
>> record field 'interval': -40
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  Traceback (most recent 
>> call last):
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/engine.py", line 884, in main
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  engine = engine_class 
>> (config_dict)
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  self.loadServices 
>> (config_dict)
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  self.service_obj.append 
>> (weeutil.weeutil._get_object (svc) (self, config_dict))
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/engine.py", line 500, in __init__
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  self.setup_database 
>> (config_dict)
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/engine.py", line 617, in setup_database
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  _nrecs, _ndays = 
>> dbmanager.backfill_day_summary () # @UnusedVariable
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/manager.py", line 1469, in backfill_day_summary
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  weight = 
>> self._calc_weight (rec)
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
>> "/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  raise ValueError 
>> ("Non-positive value for record field 'interval':% s"% (record 
>> ['interval'],))
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  ValueError: Non-positive 
>> value for record field 'interval': -40
>> Feb 22 19:03:20 meteomontaos weewx [15992]:  Exiting.
>>
>> help?
>>
>> -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Error changing raspberry

[Juan Antonio Mosquera]

I'm changing the raspberry b + to raspberry 2.

I have this problem when I do rebuild of weewx.sdb

Feb 22 19:03:20 meteomontaos weewx [15992]: engine: Caught unrecoverable 
exception in engine:
Feb 22 19:03:20 meteomontaos weewx [15992]:  Non-positive value for 
record field 'interval': -40
Feb 22 19:03:20 meteomontaos weewx [15992]:  Traceback (most recent 
call last):
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/engine.py", line 884, in main
Feb 22 19:03:20 meteomontaos weewx [15992]:  engine = engine_class 
(config_dict)
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
Feb 22 19:03:20 meteomontaos weewx [15992]:  self.loadServices 
(config_dict)
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
Feb 22 19:03:20 meteomontaos weewx [15992]:  self.service_obj.append 
(weeutil.weeutil._get_object (svc) (self, config_dict))
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/engine.py", line 500, in __init__
Feb 22 19:03:20 meteomontaos weewx [15992]:  self.setup_database 
(config_dict)
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/engine.py", line 617, in setup_database
Feb 22 19:03:20 meteomontaos weewx [15992]:  _nrecs, _ndays = 
dbmanager.backfill_day_summary () # @UnusedVariable
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/manager.py", line 1469, in backfill_day_summary
Feb 22 19:03:20 meteomontaos weewx [15992]:  weight = self._calc_weight 
(rec)
Feb 22 19:03:20 meteomontaos weewx [15992]:  File 
"/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight
Feb 22 19:03:20 meteomontaos weewx [15992]:  raise ValueError 
("Non-positive value for record field 'interval':% s"% (record 
['interval'],))
Feb 22 19:03:20 meteomontaos weewx [15992]:  ValueError: Non-positive 
value for record field 'interval': -40
Feb 22 19:03:20 meteomontaos weewx [15992]:  Exiting.

help?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

OK thanks. I will test this driver in weewx 3.9.1 tomorrow.

El domingo, 17 de febrero de 2019, 7:57:54 (UTC+1), Cameron D escribió:
>
> The 3.9.1 driver does not have my changes, but does have some 
> modifications for python 3.  I expect that means the default driver will 
> have the same problems.
>
> I have attached
>wmr300-v19rc6+f5.py   and 
>wmr300x-v19rc6+f5.py
>
> Which are each basically the same as I previously posted, except that 
> these have the python-3 changes to the "except" statements.
>
> Cameron.
>
> On Saturday, 16 February 2019 02:56:07 UTC+10, Juan Antonio Mosquera wrote:
>>
>> Hi,
>>
>> I use this version now:
>>
>> weewx.drivers.wmr300x-v19rc6+f3
>>
>> All ok... but.. in weewx 3.9.1 driver change¿, can i use wmr300 driver 
>> default?
>>
>> thanks.
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

Hi,

I use this version now:

weewx.drivers.wmr300x-v19rc6+f3

All ok... but.. in weewx 3.9.1 driver change¿, can i use wmr300 driver 
default?

thanks.

El jueves, 4 de octubre de 2018, 16:22:22 (UTC+2), Cameron D escribió:
>
> The rc5 and rc6 drivers shjipped with the weewx releases had issues where, 
> after some time (days to weeks) the system would stop reporting any data.
> That was addressed in this update of 24th September 
> <https://groups.google.com/d/topic/weewx-user/jUF4J6tRxPU/discussion>.
>
> At least two users have reported a different problem, where there is only 
> partial loss, for example wind or temperature and humidity.
>
>1. Juan Antonio Mosquera reports wind data missing 
><https://groups.google.com/d/msg/weewx-user/jUF4J6tRxPU/ABecLDR6AQAJ>.
>2. Markus Biewer reports temperature/humidity, and sometimes other data 
>going missing after about a week 
><https://groups.google.com/d/msg/weewx-user/7QUNDdqbHHE/z7Rr5lqZAgAJ>.
>
> Initially it looked like it might have been related to Belchertown skin, 
> but it is reported to also be an issue with the standard skin.
>
> The attached zip file has 3 files:
>
>1. *wmr300-v19rc6+f3.py*  - and updated version of the main wmr300 
>driver - this has a couple of minor bug fixes as well as extra diagnostic 
>code for this problem.
>2. *summ-pkt-data.awk*  -   an awk script to  convert the new 
>diagnostic logfile data into a csv file.
>3. *wmr300x-v19rc6+f3.py* - note the 'x'. This is the experimental 
>driver that uses pyusb 1 and libusb1 if available.  It also contains the 
>extra diagnostics, but is included for the other issue where the pi locks 
>up completely.
>
> *New Diagnostics*:
>
> In your weewx.conf file, enable
>   debug=1
>
> and in the WMR300 section I would suggest the following:
> debug_counts = 1
> debug_decode = 0
> debug_comm = 0
> debug_history = 0
> debug_timing = 1
> debug_rain = 0
>
> The debug_counts setting will output a summary of each packet type read 
> from the USB  in a specified time interval (default 20 seconds) as well as 
> the number of loop packets sent to weewx.
>
> Here is my WMR300 section
>
> ##
>
> [WMR300]
> # This section is for WMR300 weather stations
>
> # The station model, e.g., WMR300A
> model = WMR300
>
> # The driver to use:
> driver = user.wmr300-v19rc6+f3
>
> history_limit = 6
>
> debug_counts = 1
> debug_decode = 0
> debug_comm = 0
> debug_history = 1
> debug_timing = 1
> debug_rain = 0
>
>
> ##
>
> Note that I recommend placing these drivers in the "user" directory of the 
> weewx installation.
> You can also create a similar section named *[WMR300x]* to use the 
> experimental driver, and select between them by editing this line in the 
> *[Station]* section:
>  station_type = WMR300
>
> *Experimental driver:*
> This driver uses the PyUSB version 1 API, which allows it to use libusb1 
> or other usb libraries.
> It will default to libusb1 if possible, but otherwise will fall back to 
> libusb0.
>
> Note that some versions of Ubuntu seemed to ship with a beta version of 
> PyUSB-1 that did not seem to support the full api.  If it reports a version 
> beginning "1.0.0b..." then the driver will use libusb0.
>
> If you enable the experimental version then check the log file when it 
> starts up:
> It will always show pyusb_version, and the experimental driver will print 
> which usb backend library is selected.
>
> grep -i pyusb (your-logfile)
>
> will display both.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AWEKAS stop accepting my posts

[Juan Antonio Mosquera]

110/5000
They have blocked you for some reason. Possibly because of the quality of 
the data. You have to send an email to AWEKAS.

El sábado, 9 de febrero de 2019, 2:02:19 (UTC+1), ted frohling escribió:
>
> I recently became aware that AWEKAS stopped accepting my weewx uploads.  
> The errors I'm getting in the logs  are:
>
> Feb 08 16:15:56 weewx weewx[13603]: restx: AWEKAS: Failed to publish 
> record 2019-02-08 16:10:00 MST (1549667400): server returned 'too many 
> requests - try again later '
> Feb 08 16:15:57 weewx weewx[13603]: restx: AWEKAS: Failed to publish 
> record 2019-02-08 16:15:00 MST (1549667700): server returned 'too many 
> requests - try again later'
>
> Of course, I've restarted weewx many times.  This is running on a Pi 3.  
> All the other uploads are working just fine.
>
> Any thoughts?
>
> Thanks,
>
> ted
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: AWEKAS stop accepting my posts

[Juan Antonio Mosquera]

They have blocked you for some reason. Possibly because of the quality of 
the data. You have to send an email to AWEKAS.


El sábado, 9 de febrero de 2019, 2:02:19 (UTC+1), ted frohling escribió:
>
> I recently became aware that AWEKAS stopped accepting my weewx uploads.  
> The errors I'm getting in the logs  are:
>
> Feb 08 16:15:56 weewx weewx[13603]: restx: AWEKAS: Failed to publish 
> record 2019-02-08 16:10:00 MST (1549667400): server returned 'too many 
> requests - try again later '
> Feb 08 16:15:57 weewx weewx[13603]: restx: AWEKAS: Failed to publish 
> record 2019-02-08 16:15:00 MST (1549667700): server returned 'too many 
> requests - try again later'
>
> Of course, I've restarted weewx many times.  This is running on a Pi 3.  
> All the other uploads are working just fine.
>
> Any thoughts?
>
> Thanks,
>
> ted
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Beta testers for v3.9.0 needed

[Juan Antonio Mosquera]

I upgraded!,

first problem is units!, units default change in my weewx.conf i think... 

I changed units in group and all OK. 

I use Belchertown Skin... and today upgrade 3.9.0 to 3.9.1.

Thanks.

El martes, 22 de enero de 2019, 21:05:24 (UTC+1), Thomas Keffer escribió:
>
> It's been well over a year since the last "dot" release, but the V3.9 
> release is finally in sight!
>
> We have a beta version, and can use some help testing it out. The biggest 
> new feature is the new skin, *Seasons*, to replace the venerable 
> *Standard*, which has shipped since v1.0! Using the new skin is entirely 
> optional.
>
> There have also been some changes in how report options are chosen, the 
> net effect being that you will be able to specify a unit system to be 
> applied to *all* reports, or just to individual reports.
>
> I've been running v3.9 for 6 months on my home machine, so it appears to 
> be very stable. We can just use some help to see if there are any sharp 
> edges left.
>
> You can find the release candidate, v3.9.0b1 is the usual place: 
> http://weewx.com/downloads/development_versions/
>
> Thanks, all!
>
> -tk
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.2 Released

[Juan Antonio Mosquera]

The internationalization would be very interesting. That way we would not 
have to change the code with each update. Thank you for your work.

El sábado, 2 de febrero de 2019, 13:57:13 (UTC+1), Pat escribió:
>
> Thanks. I'm working on skin version 0.9 now which I'm hoping to release 
> soon. Many bug fixes.
>
> To change the chart names, check the files within 
> skins/Highcharts_Belchertown/json
>
> I haven't had a chance to look into internationalization yet. Hopefully 
> soon.
>
>
>
> On Saturday, February 2, 2019 at 7:35:31 AM UTC-5, opc...@gmail.com wrote:
>>
>> Hi Guys!Thank you, Pat, for the great skin! I am about to translate 
>> everything into German. I am currently stuck at renaming the graphs. Where 
>> do I need to change the titles of the diagrams and also the names of the 
>> single lines?
>>
>>
>> Am Donnerstag, 31. Januar 2019 23:07:46 UTC+1 schrieb Pat:
>>>
>>> The skin is showing the alerts that are downloaded from DarkSky. I have 
>>> no more developer notes than that. If there's too many alerts, you can 
>>> reach out to DarkSky themselves to ask about it. 
>>>
>>> On Thursday, January 31, 2019 at 3:32:05 PM UTC-5, mercurystorm wrote:

 I just implemented this skin and its fantastic

 I do however seem to be getting to many weather warnings..

 Currently showing 4 weather warnings for my area.. but there is 
 currently only one active on darksky

 https://stormy.ie/weather/live/
 https://darksky.net/forecast/53.3272,-9.1737/ca12/en
 https://www.met.ie/warnings

 Each time the MET seems to update it.. I get another weather warning on 
 my site.. any ideas?

 On Tuesday, 1 January 2019 12:50:49 UTC, Pat wrote:
>
> I've just released version 0.8.2 of the Belchertown skin which fixes 
> the New Year bug some of you are seeing. It also adds some other 
> features. 
>
>
> Download and install instructions here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
>
> * Fixed an error where the skin would fail when the date rolls to the 
> New Year due to no data being in certain tables in the database yet. 
> * Added the ability to show any weather alerts provided by the DarkSky 
> API. Weather alerts are off by default, use forecast_alert_enabled in 
> weewx.conf skin options to enable it.
> * New option to show cloudbase. You must have your database schema 
> extended for the cloudbase observation to be calculated by weewx. Check 
> the 
> Belchertown skin wiki for details.
> * Fixes an issue where the MQTT updates showed altimeter instead of 
> barometer.
> * Updated Google Analytics page to be in header based on Google 
> recommendations. 
> * Updated Google Analytics to a more recent script block. 
> * Added a Google Analytics page view per MQTT update as per Google 
> Recommendations on background updates. 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Is a extension cable.

https://www.amazon.es/gp/product/B000VN1BXQ/ref=ppx_yo_dt_b_asin_title_o00__o00_s00?ie=UTF8=1

thanks.

El martes, 15 de enero de 2019, 15:06:07 (UTC+1), Cameron D escribió:
>
> Hi Juan Antonio
> I am sure we are all glad the problem has been solved and we can all learn 
> something from it.
>
> I am curious if this was supplied with the original kit or if you added an 
> extension.
> I ask because my wmr300 has no in-line socket - my wind sensor assembly 
> has about 6m of cable hardwired into it, with just the plug at the other 
> end.
> When installing it I was annoyed by having to feed the cable one way all 
> that distance, but after your problems I am glad it is like that.
>
> So was yours an extension cable, or was it an older design that they 
> improved by getting rid of the socket?
> Or is it a newer design where they have added potential problems by making 
> installation more convenient?
>
> Cameron.
>
> On Saturday, 12 January 2019 04:03:16 UTC+10, Juan Antonio Mosquera wrote:
>>
>> Hello,
>>
>> I have found the problem The console showed wind speeds only a few times. 
>> The cause was the cable. The cable was damaged by moisture (attached 
>> photos).
>> I changed the cable and everything works correctly.
>>
>> Sorry for the inconvenience with this problem, I've wasted your time.
>>
>> Greetings and thanks.
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Yes, I think the problem is with someone with a Vantage. Could it be a 
point error of the weewx 3.8. *? Version, which affects some units?

Thank you.

El viernes, 4 de enero de 2019, 9:26:50 (UTC+1), gjr80 escribió:
>
> Hmm, not quite seeing the connection but as far as I can tell everyone in 
> that thread has a Vantage station?
>
> Gary
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Downgrade to 3.7.*

[Juan Antonio Mosquera]

Is it documented how to perform a downgrade of weewx to 3.7. * ?.

I would like to perform this downgrade to test if the problems of wind 
speed measurement are solved.

use Raspberry pi b + and wmr300 (installation with APT).

Greetings and thanks.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Post where they treat this same problem.

https://forum.meteoclimatic.net/index.php/topic,2126.0.html

El jueves, 3 de enero de 2019, 8:07:06 (UTC+1), Juan Antonio Mosquera 
escribió:
>
> Factory reset not work...same problem... no data of wind.
>
> El jueves, 27 de diciembre de 2018, 16:27:37 (UTC+1), Cameron D escribió:
>>
>> Thanks, it is even odder than I expected.
>> The USB block has speeds zero, however at the end there is a section 
>> weewx does not use, which I think is maximum gust today, followed by max 
>> gust this month.
>> The max gust today (2018-12-27 at 00:00 was zero) but max for month was 
>> 1.1 m/s at 2018-12-26 18:44. 
>>
>> This seems a tiny value, but the fact that is it not zero suggests it 
>> might be a scaling error.
>>
>> I think you should connect the Windows software, save the history, and 
>> see what it reports as wind speeds.
>>
>> A factory reset might help.
>>
>> Cameron.
>>
>> On Thursday, 27 December 2018 23:57:17 UTC+10, Juan Antonio Mosquera 
>> wrote:
>>>
>>> ok sorry... my data portion
>>>
>>>
>>>
>>>
>>> Dec 27 14:56:20 meteomontaos weewx[17954]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545918981, 'windDir': 206.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 
>>> 1b 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 
>>> 12 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 
>>> 00 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>>> 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 
>>> 1b 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 
>>> 12 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 
>>> 00 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>>> 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 
>>> 1b 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 
>>> 12 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 
>>> 00 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>>> 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545918985, 'windDir': 206.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 
>>> 1b 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 
>>> 12 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 
>>> 00 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>>> 157.0, 'channel': 1, 'windchill': None}
>>> Dec 27 14:56:25 meteomontaos weewx[17954]: 

[weewx-user] Re: ignore_zero_wind = False --> doesn't work

[Juan Antonio Mosquera]

Hi,

With the option deactivated (False) I can now see the direction of the wind 
always

www.meteomontaos.es

But it does not persist, if I observe the reports it always appears the 
same. (90 degrees)

http://www.meteomontaos.es/reports/

I do not understand this behavior.

Use WMR300 with Belchertown template. I have problems with the wind data 
(the console shows them and a weewx does not seem to arrive). But this is 
already covered in another post.

Greetings and thanks.


El jueves, 27 de diciembre de 2018, 13:58:50 (UTC+1), gjr80 escribió:
>
> In my experience station/weeWX issues that disappear for no apparent 
> reason are not actually fixed, rather some set of conditions/circumstances 
> have transpired that mask the previously seen symptoms. 
>
> The ignore_zero_wind setting is very simple in its operations. if set to 
> True windDirection and windGustDir are forced to None if windSpeed and 
> windGust are zero respectively. This is the default action. If windSpeed 
> and windGust are None then windDir and windGustDir are untouched (note 
> that None and zero are two different values). If ignore_zero_wind is set 
> to False then windDir and windGustDir are untouched irrespective of 
> windSpeed and windGust. 
>
> At the end of the day there are a number of scenarios that could explain 
> what you initially observed; it could be that weeWX received no windDir 
> data and left untouched windDir displayed as N/A, there could be a 
> peculiarity to how your station provides data or there could be some other 
> issue. Without knowing the station type and seeing the loop and archive 
> data from the driver/weeWX (and possibly digging further) it is impossible 
> to narrow down the issue.
>
> I guess we will wait and see if the issue presents itself again in the 
> future.
>
> Gary
>
> On Thursday, 27 December 2018 20:46:55 UTC+10, Christian Nimmervoll wrote:
>>
>>
>> No idea why. But now it works. :)
>>
>> Maybe it just needed time.
>> THX for the help!
>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Factory reset not work...same problem... no data of wind.

El jueves, 27 de diciembre de 2018, 16:27:37 (UTC+1), Cameron D escribió:
>
> Thanks, it is even odder than I expected.
> The USB block has speeds zero, however at the end there is a section weewx 
> does not use, which I think is maximum gust today, followed by max gust 
> this month.
> The max gust today (2018-12-27 at 00:00 was zero) but max for month was 
> 1.1 m/s at 2018-12-26 18:44. 
>
> This seems a tiny value, but the fact that is it not zero suggests it 
> might be a scaling error.
>
> I think you should connect the Windows software, save the history, and see 
> what it reports as wind speeds.
>
> A factory reset might help.
>
> Cameron.
>
> On Thursday, 27 December 2018 23:57:17 UTC+10, Juan Antonio Mosquera wrote:
>>
>> ok sorry... my data portion
>>
>>
>>
>>
>> Dec 27 14:56:20 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918981, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918985, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918986, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: decode: d4

[weewx-user] Re: Belchertown Skin 0.8.2 Released

[Juan Antonio Mosquera]

Updated to 0.8.2 and works fine.

El martes, 1 de enero de 2019, 13:50:49 (UTC+1), Pat escribió:
>
> I've just released version 0.8.2 of the Belchertown skin which fixes the 
> New Year bug some of you are seeing. It also adds some other features. 
>
>
> Download and install instructions here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
>
> * Fixed an error where the skin would fail when the date rolls to the New 
> Year due to no data being in certain tables in the database yet. 
> * Added the ability to show any weather alerts provided by the DarkSky 
> API. Weather alerts are off by default, use forecast_alert_enabled in 
> weewx.conf skin options to enable it.
> * New option to show cloudbase. You must have your database schema 
> extended for the cloudbase observation to be calculated by weewx. Check the 
> Belchertown skin wiki for details.
> * Fixes an issue where the MQTT updates showed altimeter instead of 
> barometer.
> * Updated Google Analytics page to be in header based on Google 
> recommendations. 
> * Updated Google Analytics to a more recent script block. 
> * Added a Google Analytics page view per MQTT update as per Google 
> Recommendations on background updates. 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

me too... i use 0.8.1  since 0:00AM fails.

Jan 01 13:23:05 meteomontaos weewx[6865]: reportengine: Caught 
unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
Jan 01 13:23:05 meteomontaos weewx[6865]:   'NoneType' object 
has no attribute '__getitem__'
Jan 01 13:23:05 meteomontaos weewx[6865]:   Traceback (most 
recent call last):
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Jan 01 13:23:05 meteomontaos weewx[6865]:   obj.start()
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Jan 01 13:23:05 meteomontaos weewx[6865]:   self.run()
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
Jan 01 13:23:05 meteomontaos weewx[6865]:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Jan 01 13:23:05 meteomontaos weewx[6865]:   ngen += 
self.generate(section[subsection], gen_ts)
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Jan 01 13:23:05 meteomontaos weewx[6865]:   ngen += 
self.generate(section[subsection], gen_ts)
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
Jan 01 13:23:05 meteomontaos weewx[6865]:   default_binding)
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
Jan 01 13:23:05 meteomontaos weewx[6865]:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Jan 01 13:23:05 meteomontaos weewx[6865]: File 
"/usr/share/weewx/user/belchertown.py", line 297, in get_extension_list
Jan 01 13:23:05 meteomontaos weewx[6865]:   
year_rainiest_month_tuple = (year_rainiest_month_query[1], rain_unit, 
'group_rain')
Jan 01 13:23:05 meteomontaos weewx[6865]:   TypeError: 
'NoneType' object has no attribute '__getitem__'
Jan 01 13:23:05 meteomontaos weewx[6865]:   Generator terminated


El martes, 1 de enero de 2019, 7:37:34 (UTC+1), Zsolt Máté escribió:
>
> I'm getting the following error. Am I missing a path or something? 
>
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> self.run()
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
> ngen = self.generate(gen_dict[section_name], self.gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> ngen += self.generate(section[subsection], gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> ngen += self.generate(section[subsection], gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
> default_binding)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in 
> _getSearchList
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Ok thanks...

i will try factory reset...

thanks.

El jueves, 27 de diciembre de 2018, 16:27:37 (UTC+1), Cameron D escribió:
>
> Thanks, it is even odder than I expected.
> The USB block has speeds zero, however at the end there is a section weewx 
> does not use, which I think is maximum gust today, followed by max gust 
> this month.
> The max gust today (2018-12-27 at 00:00 was zero) but max for month was 
> 1.1 m/s at 2018-12-26 18:44. 
>
> This seems a tiny value, but the fact that is it not zero suggests it 
> might be a scaling error.
>
> I think you should connect the Windows software, save the history, and see 
> what it reports as wind speeds.
>
> A factory reset might help.
>
> Cameron.
>
> On Thursday, 27 December 2018 23:57:17 UTC+10, Juan Antonio Mosquera wrote:
>>
>> ok sorry... my data portion
>>
>>
>>
>>
>> Dec 27 14:56:20 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918981, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918985, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918986, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

, 'windchill': None}
Dec 27 14:56:28 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918988, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:30 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:30 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:30 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918990, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:30 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:30 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:30 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918991, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:32 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:32 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:32 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918993, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:33 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:33 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:33 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918993, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}


thanks.

El jueves, 27 de diciembre de 2018, 14:32:47 (UTC+1), Cameron D escribió:
>
> Not exactly - you have only enabled debug_packet.
> You need to add the line debug_decode=1, which includes the data fairly 
> directly from the USB buffer, with less processing in the driver.
>
> If the decode also shows zero values for wind in the usb input buffer then 
> your next step should be to plug in a windows PC and run the Oregon Weather 
> OS software to see if it shows correct wind speeds.  This is clutching at 
> straws now, but I suppose the console might possibly have a corrupted 
> calibration factor in what it sends over the USB.
>
> Cameron.
>
> On Thursday, 27 December 2018 22:28:51 UTC+10, Juan Antonio Mosquera wrote:
>>
>> yes... in raw packets windSpeed is Zero... i dont understand... console 
>> show wind speed.
>>
>> El jueves, 27 de diciembre de 2018, 13:16:51 (UTC+1), Andrew Milner 
>> escribió:
>>>
>>> Have you done what Cameron suggested a few posts ago and set 
>>> debug_decode = 1 and 
>>> debug_packet = 1 
>>> in the wmr300 section of weewx.conf?
>>>
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

yes... in raw packets windSpeed is Zero... i dont understand... console 
show wind speed.

El jueves, 27 de diciembre de 2018, 13:16:51 (UTC+1), Andrew Milner 
escribió:
>
> Have you done what Cameron suggested a few posts ago and set 
> debug_decode = 1 and 
> debug_packet = 1 
> in the wmr300 section of weewx.conf?
>
>
>
> On Thursday, 27 December 2018 09:13:48 UTC+2, Juan Antonio Mosquera wrote:
>>
>> Yes, there are speed values in the console. This before changing the 
>> template did not happen. I have activated the flag that you indicate to 
>> have the address at least. What can happen so that weewx does not receive 
>> those values? (I have rebooted the console).
>>
>> Greetings and thanks.
>>
>>
>> El jueves, 27 de diciembre de 2018, 3:45:21 (UTC+1), Andrew Milner 
>> escribió:
>>>
>>> From your logs it looks as though windspeed is not being received 
>>> although wind direction IS being received.
>>>
>>> It looks as though your anemometer which is reading windspeed is not 
>>> providing any output.
>>>
>>> Does your console show a windspeed??
>>>
>>> Weewx will ignore wind direction if windspeed is zero or null
>>>
>>> If you want to see wind direction when windspeed is zero or not 
>>> asvailable then you must set:
>>> [StdWXCalculate]
>>> ...
>>>     ignore_zero_wind = False
>>>
>>> in weewx.conf
>>>
>>> and the wind direction will be preserved by weewx even when windspeed is 
>>> zero or not available.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday, 26 December 2018 18:34:35 UTC+2, Juan Antonio Mosquera 
>>> wrote:
>>>>
>>>> Better info...
>>>>
>>>>
>>>> sudo journalctl -f | grep wind
>>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
>>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
>>>> 212, 
>>>> 'wind_dir': 131.0, 'wind_gust_dir': 121.0, 'channel': 1, 'windchill': None}
>>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
>>>> {'windchill': None, 'dateTime': 1545842019, 'windDir': 131.0, 'windSpeed': 
>>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 121.0}
>>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
>>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
>>>> 212, 
>>>> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
>>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
>>>> {'windchill': None, 'dateTime': 1545842020, 'windDir': 131.0, 'windSpeed': 
>>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
>>>> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: raw packet: 
>>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
>>>> 212, 
>>>> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
>>>> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: converted packet: 
>>>> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
>>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
>>>> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: raw packet: 
>>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
>>>> 212, 
>>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>>> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: converted packet: 
>>>> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
>>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>>> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: raw packet: 
>>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
>>>> 212, 
>>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>>> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: converted packet: 
>>>> {'windchill': None, 'dateTime': 1545842025, 'windDir': 131.0, 'windSpeed': 
>>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>>> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: raw packet: 
>>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
>>>> 212, 
>>>> 'wind_dir': 131.0

[weewx-user] Re: ignore_zero_wind = False --> doesn't work

[Juan Antonio Mosquera]

the problem was that the variable was not well located, now it works ok. 
Thanks and sorry.

El jueves, 27 de diciembre de 2018, 9:58:13 (UTC+1), Juan Antonio Mosquera 
escribió:
>
> Not work, me too.
>
> El jueves, 27 de diciembre de 2018, 9:53:38 (UTC+1), Christian Nimmervoll 
> escribió:
>>
>> Hi,
>>
>> I changed the "ignore_zero_wind" to False but this setting doesn't work.
>> I wanna see the Wind direction also, when the windspeed is zerro. Now i 
>> always see "N/A"
>>
>> In my config File - i have add it as listed below:
>>
>> #
>>
>> #   This section controls the origin of derived values.
>>
>> [StdWXCalculate]
>> 
>> *ignore_zero_wind = False*
>>
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = prefer_hardware
>> heatindex = prefer_hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>>
>> #
>>
>>
>> What have i done wrong?
>> Thx,
>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Yes, there are speed values in the console. This before changing the 
template did not happen. I have activated the flag that you indicate to 
have the address at least. What can happen so that weewx does not receive 
those values? (I have rebooted the console).

Greetings and thanks.


El jueves, 27 de diciembre de 2018, 3:45:21 (UTC+1), Andrew Milner escribió:
>
> From your logs it looks as though windspeed is not being received although 
> wind direction IS being received.
>
> It looks as though your anemometer which is reading windspeed is not 
> providing any output.
>
> Does your console show a windspeed??
>
> Weewx will ignore wind direction if windspeed is zero or null
>
> If you want to see wind direction when windspeed is zero or not asvailable 
> then you must set:
> [StdWXCalculate]
> ...
> ignore_zero_wind = False
>
> in weewx.conf
>
> and the wind direction will be preserved by weewx even when windspeed is 
> zero or not available.
>
>
>
>
>
>
>
> On Wednesday, 26 December 2018 18:34:35 UTC+2, Juan Antonio Mosquera wrote:
>>
>> Better info...
>>
>>
>> sudo journalctl -f | grep wind
>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 121.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842019, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 121.0}
>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842020, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
>> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
>> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842025, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842027, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842029, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545842030, 'windDir': 131.0, 'windSpeed': 
>> 0.0, 'wi

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

 meteomontaos weewx[13518]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545842050, 'windDir': 131.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 125.0}
Dec 26 17:34:11 meteomontaos weewx[13518]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545844140.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 131.0, 'wind_gust_dir': 125.0, 'channel': 1, 'windchill': None}
Dec 26 17:34:11 meteomontaos weewx[13518]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545842052, 'windDir': 131.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 125.0}
Dec 26 17:34:12 meteomontaos weewx[13518]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545844140.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 131.0, 'wind_gust_dir': 118.0, 'channel': 1, 'windchill': None}
Dec 26 17:34:12 meteomontaos weewx[13518]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545842052, 'windDir': 131.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 118.0}
Dec 26 17:34:14 meteomontaos weewx[13518]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545844140.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 131.0, 'wind_gust_dir': 118.0, 'channel': 1, 'windchill': None}
Dec 26 17:34:14 meteomontaos weewx[13518]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545842054, 'windDir': 131.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 118.0}
Dec 26 17:34:14 meteomontaos weewx[13518]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545844140.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 131.0, 'wind_gust_dir': 116.0, 'channel': 1, 'windchill': None}
Dec 26 17:34:14 meteomontaos weewx[13518]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545842055, 'windDir': 131.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 116.0}


El miércoles, 26 de diciembre de 2018, 17:26:44 (UTC+1), Juan Antonio 
Mosquera escribió:
>
> Data today...
>
> exist wind dir and wind gust... but not represent in template now.
>
> ec 26 17:25:24 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'extraHeatindex5': None, 'extraDewpoint5': None, 'dateTime': 1545841525, 
> 'extraHumid5': None, 'extraTemp5': None, 'usUnits': 17}
> Dec 26 17:25:24 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'dewpoint_7': None, 'humidity_7': None, 'temperature_7': None, 'ts': 
> 1545843600.0, 'packet_type': 211, 'heatindex_7': None, 'channel': 7}
> Dec 26 17:25:24 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'extraDewpoint6': None, 'extraHeatindex6': None, 'dateTime': 1545841525, 
> 'extraHumid6': None, 'extraTemp6': None, 'usUnits': 17}
> Dec 26 17:25:25 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'temperature_8': None, 'humidity_8': None, 'ts': 1545843600.0, 
> 'dewpoint_8': None, 'packet_type': 211, 'heatindex_8': None, 'channel': 8}
> Dec 26 17:25:25 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'extraHeatindex7': None, 'extraDewpoint7': None, 'dateTime': 1545841525, 
> 'extraHumid7': None, 'extraTemp7': None, 'usUnits': 17}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'temperature_0': 19.402, 'humidity_0': 52.0, 'dewpoint_0': 
> 9.0, 'ts': 1545843600.0, 'heatindex_0': None, 'packet_type': 211, 
> 'channel': 0}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'inHumidity': 52.0, 'inTemp': 19.402, 'usUnits': 17, 
> 'dateTime': 1545841526}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'temperature_2': None, 'humidity_2': None, 'dewpoint_2': None, 'ts': 
> 1545843600.0, 'heatindex_2': None, 'packet_type': 211, 'channel': 2}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'extraHeatindex1': None, 'extraDewpoint1': None, 'dateTime': 1545841526, 
> 'extraHumid1': None, 'usUnits': 17, 'extraTemp1': None}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'temperature_3': None, 'dewpoint_3': None, 'humidity_3': None, 'ts': 
> 1545843600.0, 'heatindex_3': None, 'packet_type': 211, 'channel': 3}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'extraDewpoint2': None, 'extraHeatindex2': None, 'dateTime': 1545841526, 
> 'extraHumid2': None, 'extraTemp2': None, 'usUnits': 17}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'barometer': 1023.30001, 'altitude': 310.0, 'ts': 1545843600.0, 
> 'pressure': 988.6, 'packet_type': 214, 'channel': 0}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'pressure': 988.6, 'barometer': 1023.30001, 'usUnits': 17, 
> 'dateTime': 1545841526}
> Dec 26 17:25:26 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'humidity_4': None, 'dewpoint_4': None, 'temperature_4': None, 'ts': 
> 1545843600.0, 'packet_t

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

}
Dec 26 17:25:28 meteomontaos weewx[13518]: wmr300: converted packet: 
{'extraDewpoint6': None, 'extraHeatindex6': None, 'dateTime': 1545841529, 
'extraHumid6': None, 'extraTemp6': None, 'usUnits': 17}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545843600.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 131.0, 'wind_gust_dir': 109.0, 'channel': 1, 'windchill': None}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545841529, 'windDir': 131.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 109.0}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: raw packet: 
{'temperature_8': None, 'humidity_8': None, 'ts': 1545843600.0, 
'dewpoint_8': None, 'packet_type': 211, 'heatindex_8': None, 'channel': 8}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: converted packet: 
{'extraHeatindex7': None, 'extraDewpoint7': None, 'dateTime': 1545841529, 
'extraHumid7': None, 'extraTemp7': None, 'usUnits': 17}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: raw packet: 
{'rain_hour': 0.0, 'rain_24_hour': 0.254, 'rain_rate': 0.0, 'ts': 
1545843600.0, 'rain_start_dateTime': 1545746400.0, 'packet_type': 213, 
'rain_total': 0.254, 'channel': 1}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: converted packet: 
{'rainRate': 0.0, 'rain': 0.0, 'usUnits': 17, 'dateTime': 1545841529}
Dec 26 17:25:29 meteomontaos weewx[13518]: wmr300: raw packet: 
{'temperature_1': 13.3, 'dewpoint_1': 8.0, 'humidity_1': 68.0, 'ts': 
1545843600.0, 'heatindex_1': None, 'packet_type': 211, 'channel': 1}


El miércoles, 26 de diciembre de 2018, 15:13:01 (UTC+1), Cameron D escribió:
>
> When the wind speed is zero then the direction is deliberately set to 
> None, so you can only check direction when there is some wind.  That rule 
> applies both to average and to gust readings.
>
> When you set debug=1 you also need to check which debug suboptions are set 
> in the wmr300 section of the config file...
> You  should set:
> debug_decode=1
> debug_packet=1
>
> All the other suboptions  should be zero for your testing.(simply to avoid 
> clutter)
>
> Cameron.
>
>
> On Wednesday, 26 December 2018 01:01:26 UTC+10, Juan Antonio Mosquera 
> wrote:
>>
>> At this time there is no wind, but I do have wind direction data in the 
>> console. As soon as I can debug assets and show you the information you 
>> request.
>>
>> Thank you.
>>
>> El martes, 25 de diciembre de 2018, 14:51:12 (UTC+1), Andrew Milner 
>> escribió:
>>>
>>> if you stop weewx, set debug = 1, restart weewx I think you should get 
>>> the raw packets from the interceptor driver.  Do the raw packets give any 
>>> wind data??  If they do then the issue is in the mapping.
>>>
>>>
>>>
>>> On Tuesday, 25 December 2018 15:32:12 UTC+2, kutz...@gmail.com wrote:
>>>>
>>>> The loop data (at least the ones I looked at in the file you 
>>>> downloaded) are reporting windSpeed as 0.0. Is the console showing 
>>>> something different? If the console shows 0.0 for windSpeed also (and it 
>>>> is 
>>>> windy :-)), then maybe there is an issue with the anemometer or the wind 
>>>> sensor in the weatherstation.
>>>> phil
>>>>
>>>> On Tuesday, December 25, 2018 at 6:58:02 AM UTC-5, Juan Antonio 
>>>> Mosquera wrote:
>>>>>
>>>>> Attach data...
>>>>>
>>>>>
>>>>> No wind data :(
>>>>>
>>>>> Standard weewx pages without windData too.
>>>>>
>>>>> Problem with statation console ¿
>>>>>
>>>>> Thanks...
>>>>>
>>>>>
>>>>>
>>>>> El lunes, 24 de diciembre de 2018, 11:43:26 (UTC+1), Andrew Milner 
>>>>> escribió:
>>>>>>
>>>>>> Can you run weewx directly to get the LOOP and REC records on the 
>>>>>> screen do you get wind readings??  Can you show us the result of running 
>>>>>> weewx directly??
>>>>>>
>>>>>> Do the standard weewx pages give wind values??
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Monday, 24 December 2018 10:10:06 UTC+2, Juan Antonio Mosquera 
>>>>>> wrote:
>>>>>>>
>>>>>>> I have updated belchertown to its version 0.8.0 and now to its 
>>>>>>> version 0.8.1. I do not understand what happens. Even with the old 
>>>>>>> theme, 
>>>>>

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

At this time there is no wind, but I do have wind direction data in the 
console. As soon as I can debug assets and show you the information you 
request.

Thank you.

El martes, 25 de diciembre de 2018, 14:51:12 (UTC+1), Andrew Milner 
escribió:
>
> if you stop weewx, set debug = 1, restart weewx I think you should get the 
> raw packets from the interceptor driver.  Do the raw packets give any wind 
> data??  If they do then the issue is in the mapping.
>
>
>
> On Tuesday, 25 December 2018 15:32:12 UTC+2, kutz...@gmail.com wrote:
>>
>> The loop data (at least the ones I looked at in the file you downloaded) 
>> are reporting windSpeed as 0.0. Is the console showing something different? 
>> If the console shows 0.0 for windSpeed also (and it is windy :-)), then 
>> maybe there is an issue with the anemometer or the wind sensor in the 
>> weatherstation.
>> phil
>>
>> On Tuesday, December 25, 2018 at 6:58:02 AM UTC-5, Juan Antonio Mosquera 
>> wrote:
>>>
>>> Attach data...
>>>
>>>
>>> No wind data :(
>>>
>>> Standard weewx pages without windData too.
>>>
>>> Problem with statation console ¿
>>>
>>> Thanks...
>>>
>>>
>>>
>>> El lunes, 24 de diciembre de 2018, 11:43:26 (UTC+1), Andrew Milner 
>>> escribió:
>>>>
>>>> Can you run weewx directly to get the LOOP and REC records on the 
>>>> screen do you get wind readings??  Can you show us the result of running 
>>>> weewx directly??
>>>>
>>>> Do the standard weewx pages give wind values??
>>>>
>>>>
>>>>
>>>>
>>>> On Monday, 24 December 2018 10:10:06 UTC+2, Juan Antonio Mosquera wrote:
>>>>>
>>>>> I have updated belchertown to its version 0.8.0 and now to its version 
>>>>> 0.8.1. I do not understand what happens. Even with the old theme, it does 
>>>>> not show the wind data either.
>>>>>
>>>>> Belchertown:
>>>>> www.meteomontaos.es
>>>>>
>>>>> Sofaskin:
>>>>> www.meteomontaos2.ga
>>>>>
>>>>> Greetings and thanks.
>>>>>
>>>>> El lunes, 24 de diciembre de 2018, 3:26:01 (UTC+1), Andrew Milner 
>>>>> escribió:
>>>>>>
>>>>>> In your other thread you reported that wind speed and direction were 
>>>>>> correctly being downloaded to weewx from the wmr300.  What happened to 
>>>>>> make 
>>>>>> you lose the wind data again??
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sunday, 23 December 2018 21:52:35 UTC+2, Juan Antonio Mosquera 
>>>>>> wrote:
>>>>>>>
>>>>>>> For months I have observed that I have problems in the measurement 
>>>>>>> of wind speed and direction. Even though I have data in the console, 
>>>>>>> they 
>>>>>>> do not reach weewx. I am using the driver:
>>>>>>>
>>>>>>> wmr300-v19rc6 + f3
>>>>>>>
>>>>>>> They have tried to help me in other posts but now it has been 
>>>>>>> several weeks without any wind data.
>>>>>>>
>>>>>>> Greetings and thanks.
>>>>>>>
>>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Attach data...


No wind data :(

Standard weewx pages without windData too.

Problem with statation console ¿

Thanks...



El lunes, 24 de diciembre de 2018, 11:43:26 (UTC+1), Andrew Milner escribió:
>
> Can you run weewx directly to get the LOOP and REC records on the screen 
> do you get wind readings??  Can you show us the result of running weewx 
> directly??
>
> Do the standard weewx pages give wind values??
>
>
>
>
> On Monday, 24 December 2018 10:10:06 UTC+2, Juan Antonio Mosquera wrote:
>>
>> I have updated belchertown to its version 0.8.0 and now to its version 
>> 0.8.1. I do not understand what happens. Even with the old theme, it does 
>> not show the wind data either.
>>
>> Belchertown:
>> www.meteomontaos.es
>>
>> Sofaskin:
>> www.meteomontaos2.ga
>>
>> Greetings and thanks.
>>
>> El lunes, 24 de diciembre de 2018, 3:26:01 (UTC+1), Andrew Milner 
>> escribió:
>>>
>>> In your other thread you reported that wind speed and direction were 
>>> correctly being downloaded to weewx from the wmr300.  What happened to make 
>>> you lose the wind data again??
>>>
>>>
>>>
>>>
>>> On Sunday, 23 December 2018 21:52:35 UTC+2, Juan Antonio Mosquera wrote:
>>>>
>>>> For months I have observed that I have problems in the measurement of 
>>>> wind speed and direction. Even though I have data in the console, they do 
>>>> not reach weewx. I am using the driver:
>>>>
>>>> wmr300-v19rc6 + f3
>>>>
>>>> They have tried to help me in other posts but now it has been several 
>>>> weeks without any wind data.
>>>>
>>>> Greetings and thanks.
>>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.


loop_weewx_without_windData
Description: Binary data

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

I have updated belchertown to its version 0.8.0 and now to its version 
0.8.1. I do not understand what happens. Even with the old theme, it does 
not show the wind data either.

Belchertown:
www.meteomontaos.es

Sofaskin:
www.meteomontaos2.ga

Greetings and thanks.

El lunes, 24 de diciembre de 2018, 3:26:01 (UTC+1), Andrew Milner escribió:
>
> In your other thread you reported that wind speed and direction were 
> correctly being downloaded to weewx from the wmr300.  What happened to make 
> you lose the wind data again??
>
>
>
>
> On Sunday, 23 December 2018 21:52:35 UTC+2, Juan Antonio Mosquera wrote:
>>
>> For months I have observed that I have problems in the measurement of 
>> wind speed and direction. Even though I have data in the console, they do 
>> not reach weewx. I am using the driver:
>>
>> wmr300-v19rc6 + f3
>>
>> They have tried to help me in other posts but now it has been several 
>> weeks without any wind data.
>>
>> Greetings and thanks.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] problem with wind in WMR300

[Juan Antonio Mosquera]

For months I have observed that I have problems in the measurement of wind 
speed and direction. Even though I have data in the console, they do not 
reach weewx. I am using the driver:

wmr300-v19rc6 + f3

They have tried to help me in other posts but now it has been several weeks 
without any wind data.

Greetings and thanks.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

NO, i dont use MQTT.

El miércoles, 5 de diciembre de 2018, 14:52:08 (UTC+1), Pat escribió:
>
> I guess I am assuming you are using MQTT. 
>
> I should ask, are you using MQTT for real time updates?
>
>
> On Wednesday, December 5, 2018 at 8:50:10 AM UTC-5, Pat wrote:
>
> I will have to think about this one in a way that makes sense and doesn't 
> break anything. 
>
> Since I show everything from MQTT exactly, I do not cache data when using 
> real time updating. 
>
>
>
> On Wednesday, December 5, 2018 at 8:45:30 AM UTC-5, Juan Antonio Mosquera 
> wrote:
>
> attached image...
>
> [image: windNoData.JPG]
> thanks.
>
> El miércoles, 5 de diciembre de 2018, 14:37:00 (UTC+1), Pat escribió:
>
> I will have to see if I can do this since I show the data from MQTT 
> directly. 
>
> When you do not have wind data, what does it show?
>
>
> On Wednesday, December 5, 2018 at 4:21:57 AM UTC-5, Juan Antonio Mosquera 
> wrote:
>
> A suggestion.
>
> With the driver of the WMR300 it seems that there are times when it does 
> not send wind data. In this case it would be interesting if the template 
> always shows the last data so that wind direction and burst data always 
> appear, how do you see Pat?
>
> Greetings and thanks.
>
> El lunes, 3 de diciembre de 2018, 0:20:53 (UTC+1), Pat escribió:
>
> Some more thoughts on troubleshooting:
>
> 1) Is your error log the full output of the error section?
> 2) 
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

attached image...

[image: windNoData.JPG]
thanks.

El miércoles, 5 de diciembre de 2018, 14:37:00 (UTC+1), Pat escribió:
>
> I will have to see if I can do this since I show the data from MQTT 
> directly. 
>
> When you do not have wind data, what does it show?
>
>
> On Wednesday, December 5, 2018 at 4:21:57 AM UTC-5, Juan Antonio Mosquera 
> wrote:
>
> A suggestion.
>
> With the driver of the WMR300 it seems that there are times when it does 
> not send wind data. In this case it would be interesting if the template 
> always shows the last data so that wind direction and burst data always 
> appear, how do you see Pat?
>
> Greetings and thanks.
>
> El lunes, 3 de diciembre de 2018, 0:20:53 (UTC+1), Pat escribió:
>
> Some more thoughts on troubleshooting:
>
> 1) Is your error log the full output of the error section?
> 2) Based on this comment in one of the GitHub issues 
> <https://github.com/poblabs/weewx-belchertown/issues/20#issuecomment-434405445>,
>  
> if you open skins/Belchertown/skin.conf and change NONE = 0 (instead of 
> "N/A") in *[[StringFormats]]*
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

A suggestion.

With the driver of the WMR300 it seems that there are times when it does 
not send wind data. In this case it would be interesting if the template 
always shows the last data so that wind direction and burst data always 
appear, how do you see Pat?

Greetings and thanks.

El lunes, 3 de diciembre de 2018, 0:20:53 (UTC+1), Pat escribió:
>
> Some more thoughts on troubleshooting:
>
> 1) Is your error log the full output of the error section?
> 2) Based on this comment in one of the GitHub issues 
> ,
>  
> if you open skins/Belchertown/skin.conf and change NONE = 0 (instead of 
> "N/A") in *[[StringFormats]]* does it fix your issue?
>
> If so, I'd like to do more testing since I haven't been able to replicate 
> this issue.
>
> Is your database sqlite?
>
>
>
> On Sunday, December 2, 2018 at 5:55:23 PM UTC-5, Chris Plant wrote:
>
> Well i reimaged my pi to start from scratch and im still getting the 
> errors.  I ran a db check for Nulls and it didnt find any.
>
> pi@raspberrypi:~/Downloads $ wee_database --check
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to dat
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

I update to 0.8 and...

Dec 02 18:20:26 meteomontaos weewx[29477]: cheetahgenerator: Generated 4 
files for report Highcharts_Belchertown in 404.18 seconds


www.meteomontaos.es

Greetings.

El domingo, 2 de diciembre de 2018, 17:19:55 (UTC+1), Pat escribió:
>
> All, 
>
> Belchertown Skin 0.8 is released! A lot of new features and bug fixes!
>
> Feel free to upgrade and report issues here or on the GitHub page. 
>
> Details can be found here: 
> https://github.com/poblabs/weewx-belchertown/releases
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

No, I do not have news ... I think the creator of the extension is on 
vacation, as soon as he returns and follows the development he will release 
new versions. Greetings.

El domingo, 28 de octubre de 2018, 2:55:02 (UTC+1), Gabe escribió:
>
> Did you have a workaround? I have the same error.
>
> On Wednesday, October 17, 2018 at 12:41:56 PM UTC-4, Juan Antonio Mosquera 
> wrote:
>>
>> I have detected that this problem is due to when a data does not meet the 
>> quality data (StdQC), so this value must be missing and that causes it to 
>> fail. This should be corrected.
>>
>> Greetings.
>>
>> El miércoles, 17 de octubre de 2018, 8:30:06 (UTC+2), Juan Antonio 
>> Mosquera escribió:
>>
>> Hi,
>>
>>
>> from one moment to another without modifying any configuration now does 
>> not generate the index template.
>>
>>
>>
>>
>> Oct 17 08:25:16 meteomontaos weewx[29275]: copygenerator: copied 0 files 
>> to /var/www/html/weewx/belchertown
>> Oct 17 08:25:16 meteomontaos weewx[29275]: Belchertown Extension: version 
>> 0.7
>> Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator: Generate 
>> failed with exception ''
>> Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator:  
>> Ignoring template /etc/weewx/skins/Belchertown/index.html.tmpl
>> Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator:
>>
>> ...
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

I have detected that this problem is due to when a data does not meet the 
quality data (StdQC), so this value must be missing and that causes it to 
fail. This should be corrected.

Greetings.

El miércoles, 17 de octubre de 2018, 8:30:06 (UTC+2), Juan Antonio Mosquera 
escribió:
>
> Hi,
>
>
> from one moment to another without modifying any configuration now does 
> not generate the index template.
>
>
>
>
> Oct 17 08:25:16 meteomontaos weewx[29275]: copygenerator: copied 0 files 
> to /var/www/html/weewx/belchertown
> Oct 17 08:25:16 meteomontaos weewx[29275]: Belchertown Extension: version 
> 0.7
> Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator: Generate 
> failed with exception ''
> Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Belchertown/index.html.tmpl
> Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator:  Reason: 
> could not convert string to float: N/A
> Oct 17 08:26:26 meteomontaos weewx[29275]:   Traceback (most recent 
> call last):
> Oct 17 08:26:26 meteomontaos weewx[29275]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
> Oct 17 08:26:26 meteomontaos weewx[29275]:   print >> _file, 
> compiled_template
> Oct 17 08:26:26 meteomontaos weewx[29275]: File "/usr/l
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Hi,


from one moment to another without modifying any configuration now does not 
generate the index template.




Oct 17 08:25:16 meteomontaos weewx[29275]: copygenerator: copied 0 files to 
/var/www/html/weewx/belchertown
Oct 17 08:25:16 meteomontaos weewx[29275]: Belchertown Extension: version 
0.7
Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator: Generate 
failed with exception ''
Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Belchertown/index.html.tmpl
Oct 17 08:26:26 meteomontaos weewx[29275]: cheetahgenerator:  Reason: 
could not convert string to float: N/A
Oct 17 08:26:26 meteomontaos weewx[29275]:   Traceback (most recent 
call last):
Oct 17 08:26:26 meteomontaos weewx[29275]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
Oct 17 08:26:26 meteomontaos weewx[29275]:   print >> _file, 
compiled_template
Oct 17 08:26:26 meteomontaos weewx[29275]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Oct 17 08:26:26 meteomontaos weewx[29275]:   rc = getattr(self, 
mainMethName)()
Oct 17 08:26:26 meteomontaos weewx[29275]: File 
"_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 1378, in respond
Oct 17 08:26:26 meteomontaos weewx[29275]:   ValueError: could not 
convert string to float: N/A
Oct 17 08:26:36 meteomontaos weewx[29275]: cheetahgenerator: Generated 11 
files for report Belchertown in 80.42 seconds



Greetings.

El martes, 16 de octubre de 2018, 18:57:29 (UTC+2), Philip Kutzenco 
escribió:
>
> I think that version 0.7 is the most recent complete release. Pat has 
> issued commits for updates to some files, mostly to address those using 
> Metric units. So, individual files can be downloaded to implement those. I 
> don't think he has yet packaged them all into a later version.
> phil
>
> On Tuesday, October 16, 2018 at 10:40:12 AM UTC-4, Paul Lacatus wrote:
>>
>> Is there a procedure to update the running belchertown skin 0.7 to the 
>> last version on the github ? 
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Hi,

I am using the latest release (0.7). I have not added the changes of the 
last commits (I'm waiting for release 0.8)

Greetings and thanks.

El martes, 16 de octubre de 2018, 11:21:44 (UTC+2), Praveen Chandrasekaran 
escribió:
>
> Also did you take in the latest commits of all the files? Not the latest 
> release of the skin as  a package but individual files. Pat has made many 
> fixes for Metric mode.
>
> On Tue, 16 Oct 2018 at 14:44, Andrew Milner  > wrote:
>
> The graph does not really say anything!!
>
> IF the scale is indeed in mm as it appears to be, remember that one bucket 
> tip will likely be 0.3 mm, so on a scale of 0 - 7.5 mm the rainfall per 
> hour (which I think the blue bumps are) will be very small indeed.
>
> I think the graph is probably correct but is made harder to read by having 
> both total rainfall and hourly rainfall on the same graph.  Try and create 
> two separate graphs to get better resolution of the hourly totals (or do 
> not show them at all)
>
>
>
> On Tuesday, 16 October 2018 10:46:32 UTC+3, Juan Antonio Mosquera wrote:
>
> Not work... 
>
> attach screenshot.
>
> El martes, 16 de octubre de 2018, 8:12:17 (UTC+2), Praveen Chandrasekaran 
> escribió:
>
> [StdRestful]
> ...
> [[MQTT]]
> server_url = mqtt://username:password@localhost:1883/
> topic = weather
> unit_system = METRIC
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Okay,

If you compare the data of the graph and the NOAA data (in mm) you can see 
how 39 mm in the NOAA report is translated in the graph as cm. This will be 
caused by the general configuration (weewx.conf) that I have in METRIC 
(target_unit).

Graphic: http://www.meteomontaos.es/
NOAA: http://www.meteomontaos.es/reports/

I was just asking if it is possible to change the scale of this graph so 
that it does not take into account the general target_unit and show the 
data (as in the NOAA reports).

Greetings and thanks.

El martes, 16 de octubre de 2018, 11:14:43 (UTC+2), Andrew Milner escribió:
>
> The graph does not really say anything!!
>
> IF the scale is indeed in mm as it appears to be, remember that one bucket 
> tip will likely be 0.3 mm, so on a scale of 0 - 7.5 mm the rainfall per 
> hour (which I think the blue bumps are) will be very small indeed.
>
> I think the graph is probably correct but is made harder to read by having 
> both total rainfall and hourly rainfall on the same graph.  Try and create 
> two separate graphs to get better resolution of the hourly totals (or do 
> not show them at all)
>
>
>
> On Tuesday, 16 October 2018 10:46:32 UTC+3, Juan Antonio Mosquera wrote:
>
> Not work... 
>
> attach screenshot.
>
> El martes, 16 de octubre de 2018, 8:12:17 (UTC+2), Praveen Chandrasekaran 
> escribió:
>
> [StdRestful]
> ...
> [[MQTT]]
> server_url = mqtt://username:password@localhost:1883/
> topic = weather
> unit_system = METRIC
>
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Not work... 

attach screenshot.

El martes, 16 de octubre de 2018, 8:12:17 (UTC+2), Praveen Chandrasekaran 
escribió:
>
> [StdRestful]
> ...
> [[MQTT]]
> server_url = mqtt://username:password@localhost:1883/
> topic = weather
> unit_system = METRIC
>
>
> Change this to METRICWX.
>
>
> On Tue, 16 Oct 2018 at 11:37, Juan Antonio Mosquera <
> juananton...@juanantoniomosquera.com > wrote:
>
>
> I changed group_rain in weewx.conf, in the github documentation I do not 
> see where the target unit for mqtt is configured. How is it done? Thank you.
>
> El martes, 16 de octubre de 2018, 5:22:32 (UTC+2), Praveen Chandrasekaran 
> escribió:
>
> Change units to METRICWX in mqtt settings
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

I changed group_rain in weewx.conf, in the github documentation I do not 
see where the target unit for mqtt is configured. How is it done? Thank you.

El martes, 16 de octubre de 2018, 5:22:32 (UTC+2), Praveen Chandrasekaran 
escribió:
>
> Change units to METRICWX in mqtt settings
>
> On Tue, 16 Oct 2018, 01:04 Juan Antonio Mosquera, <
> juananton...@juanantoniomosquera.com > wrote:
>
> Hi. Another thing, I have configured to use the METRIC target unit, so the 
> rain data is in mm. But I see that in the graphics it appears in cm. Can 
> this be changed without modifying target_unit section?
>
> Greetings and thanks.
>
> El martes, 21 de agosto de 2018, 20:45:13 (UTC+2), Pat escribió:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub <https://github.com/poblabs/weewx-belchertown> for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick inst
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Hi. Another thing, I have configured to use the METRIC target unit, so the 
rain data is in mm. But I see that in the graphics it appears in cm. Can 
this be changed without modifying target_unit section?

Greetings and thanks.

El martes, 21 de agosto de 2018, 20:45:13 (UTC+2), Pat escribió:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick install:
>
> wget https://
> github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> sudo wee_extension --install weewx-belchertown-0.1.tar.gz
>
> Configure weewx.conf with your options
>
> Restart weewx
>
> Out of the box, it is a very basic theme. Make sure to check out the readme 
> for all options available !
>
>
> This is my first skin, and I've done all I could to test it out in various 
> environments to iron out any initial bugs. If you do find something that's 
> a little off, or room for improvement, please let me know!
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] redownload data from station

[Juan Antonio Mosquera]

Hi, Cameron. Thanks, but it's not the reason you think. Now weewx wind data 
correctly downloads the WMR300, with your new driver (wmr300-v19rc6 + 
f3.py).
But I have another problem, one day this month there has been no rainfall 
data and it has rained a lot.
I have backed up the database, I deleted all the data for this month and it 
was reinserted when we started weewx.
Still I have data loss so I have to check the rain gauge.

Greetings and thanks.


El sábado, 13 de octubre de 2018, 3:04:30 (UTC+2), Cameron D escribió:
>
> Juan,
> I presume you are referring to the WMR300 and missing wind speed.
> If you have a 5-minute archive period then the console storage will 
> increase by close to 1% per day.
>
> If you use the default history clear at 20% then you have *up to* 20 
> days, however it is not possible to *partially *clear the history, so 
> depending when the buffer was cleared, you might or might not have much 
> data.
>
> I tend to set it at 6% and I am not certain which setting you are using.  
> To be more sure of saving archive/history you could set the parameter:
> history_limit = 90
>
> My rule would be - if the live data is working well then use a low 
> percentage for:
>
>1. to leave an empty buffer in case the computer goes down for a long 
>time
>2. each clear is shorter and less interruption to live data flow
>
> but use a high percentage if:
>
>1. your live data is unreliable and you need to go back over some days 
>worth of data.
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] redownload data from station

[Juan Antonio Mosquera]

I understand, thanks!

O 03:45, Ven., 12 de out. de 2018, gjr80  escribiu:

> Hi,
>
> The answer depends. If and only if your driver supports backfilling from
> the station then on startup WeeWX will try to backfill any records
> timestamped after the latest record in the WeeWX archive. So if the last
> record in your archive is time stamped 9:20am 11 October 2018, WeeWX would
> try to download any records from your station that at time stamped after
> 9:20am 11 October 2018. If WeeWX cannot get any records after this
> timestamp nothing is changed, if WeeWX can only get some records after
> 9:20am 11 October 2018 then only those records that were downloaded are
> saved to archive.
>
> So if you want to re-download records from your station for a given time
> onwards you should delete all records from your archive from that given
> time onwards and then restart WeeWX. You can monitor what WeeWX does (did)
> by monitoring the log during startup.
>
> There are some caveats. If you want to re-download records from too far in
> the past there is the possibility that your station may not have all those
> records in memory and you may end up with a gap in your data. Also note
> that the backfill occurs from the last timestamp in the WeeWX archive, so
> if you want to re-download a specific period you must delete delete all
> records from the start of that period onwards, not just those in the period
> concerned.
>
> As you will be performing some destructive actions on your data I would
> make sure you backup your database first so you can revert to your old data
> if things go wrong.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/-LQKMxYvnzs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] redownload data from station

[Juan Antonio Mosquera]

Hi, I suspect that the correct data from the station have not been saved in 
weewx.sdb. How can I force the download of the data again?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

This dawn, without doing anything has begun to receive wind data, I do not know 
how long it will last. I am using the experimental driver with libusb1. Today 
in the afternoon I'm going to restart the console and change the USB port.

Thank you.


El martes, 9 de octubre de 2018, 14:33:06 (UTC+2), Cameron D escribió:
>
> OK, this is not the symptom that this thread applies to - it might be more 
> relevant to the hanging thread - I'll explain why at the end.
>
> The logs are demonstrating total loss of data - this is similar to the 
> previous problem, where the data stops, and my driver update detects this 
> and resends the initialisation command.
> Where this is different is the restart command seems to have no effect. 
> The wmr300 console resolutely stops sending data.
> Even restarting weewx is not enough to make it wake up.
>
> There are 3 possibilities I can think of.
>
>1. hardware fault in USB
>2. kernel driver fault in USB code
>3. WMR300 USB code is very touchy and liable to deadlock - which I 
>discovered when trying to modify the code. It gets upset if both sides try 
>to read or write at the same time.
>
> for point 3, I have tried to put lots of workarounds to try to ensure it 
> does not happen, but there might be hardware timing differences between 
> systems causing problems on one setup and not another.
> for point 2, this gets back to the kernel version differences.  Maybe this 
> is how my experimental driver responds to the same problem that locks up 
> under libusb0. Which kernel is this happening on?
> for point 1 - not a lot I can do there, wait to see if other people 
> replicate it.
>
> The next steps would be:
>
>- try the other kernel
>- try another USB port, if available
>- when it happens next time, see what happens if you simply unplug the 
>USB for a few seconds. This will reset the WMR300 console comms, it should 
>also reset the kernel.driver code.
>
> Cameron.
>
>
> On Tuesday, 9 October 2018 05:58:39 UTC+10, Ruben Navarro Huedo wrote:
>>
>> raspberry did not hung... only stopped receibing data from wmr300.
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

more info:

http://weather.oregonscientific.com/update.html

El domingo, 7 de octubre de 2018, 19:35:25 (UTC+2), Ruben Navarro Huedo 
escribió:
>
> I think:
>
> All the consoles have the same firmware? 
> Is possible his console is using another firmware / protocol?
>
> El domingo, 7 de octubre de 2018, 14:32:23 (UTC+2), Cameron D escribió:
>>
>> Every wind reading seems to be zero. Interestingly, the gust direction is 
>> changing, as you would expect.
>>
>> All I can think of is maybe the console is confused about units. I am 
>> lost... Some random suggestions...
>>
>>1. Try cycling through the units on the console display (this should 
>>not change the units used for transmission to the computer.
>>2. Try a console reset.
>>3. Try connecting with the Windows software and see if it records 
>>wind properly - check both the history records from when it starts up and 
>>the live update
>>
>> Also, when you post long logs, it is easier for me to handle a 
>> zipped/gzipped  attachment, rather than embedding it in-line.
>>
>> Cameron.
>>
>>
>> On Sunday, 7 October 2018 19:30:22 UTC+10, Juan Antonio Mosquera wrote:
>>>
>>> Thanks, results:
>>>
>>>
>>> ...
>>> Oct 07 11:29:22 meteomontaos weewx[22943]: wmr300x: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1538904540.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 30.0, 'wind_gust_dir': 26.0, 'channel': 1, 'windchill': None}
>>> Oct 07 11:29:22 meteomontaos weewx[22943]: wmr300x: converted packet: 
>>> {'windchill': None, 'dateTime': 1538904562, 'windDir': 30.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 26.0}...
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

When I checked the console it seemed all right. These problems only happen 
to me since version 3.8.2 and since I tried Belchertown extension.
Cameron, could you send me the WMR300 driver used in weewx 3.8.2?

Ruben: I do not know if there are several firmware, is it possible to 
update the firmware with the windows application of the Oregon?

Greetings and thanks.

El domingo, 7 de octubre de 2018, 14:32:23 (UTC+2), Cameron D escribió:
>
> Every wind reading seems to be zero. Interestingly, the gust direction is 
> changing, as you would expect.
>
> All I can think of is maybe the console is confused about units. I am 
> lost... Some random suggestions...
>
>1. Try cycling through the units on the console display (this should 
>not change the units used for transmission to the computer.
>2. Try a console reset.
>3. Try connecting with the Windows software and see if it records wind 
>properly - check both the history records from when it starts up and the 
>live update
>
> Also, when you post long logs, it is easier for me to handle a 
> zipped/gzipped  attachment, rather than embedding it in-line.
>
> Cameron.
>
>
> On Sunday, 7 October 2018 19:30:22 UTC+10, Juan Antonio Mosquera wrote:
>>
>> Thanks, results:
>>
>>
>> ...
>> Oct 07 11:29:22 meteomontaos weewx[22943]: wmr300x: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1538904540.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 30.0, 'wind_gust_dir': 26.0, 'channel': 1, 'windchill': None}
>> Oct 07 11:29:22 meteomontaos weewx[22943]: wmr300x: converted packet: 
>> {'windchill': None, 'dateTime': 1538904562, 'windDir': 30.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 26.0}...
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

It's weird, it seems that wind data does read no?


Oct 06 11:17:13 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 135; 
TH_0: 11; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 12; rain: 12; wind: 16; x57: 1
Oct 06 11:17:13 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:17:33 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 135; 
TH_0: 10; TH_1: 16; TH_2: 11; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
Oct 06 11:17:33 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:17:53 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 134; 
TH_0: 10; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
Oct 06 11:17:53 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:18:14 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 135; 
TH_0: 10; TH_1: 16; TH_2: 10; TH_3: 11; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16
Oct 06 11:18:14 meteomontaos weewx[10621]: wmr300x: write counts;
Oct 06 11:18:34 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 136; 
TH_0: 11; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 11; TH_5: 10; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
Oct 06 11:18:34 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:18:54 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 135; 
TH_0: 10; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 11; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
Oct 06 11:18:54 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:19:14 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 135; 
TH_0: 10; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 11; TH_7: 
10; TH_8: 10; barom: 10; forecast: 11; rain: 12; wind: 16; x57: 1
Oct 06 11:19:14 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:19:34 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 134; 
TH_0: 10; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 
10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
Oct 06 11:19:34 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
Oct 06 11:19:54 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 135; 
TH_0: 10; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 
11; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
Oct 06 11:19:54 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1


Thanks.


El jueves, 4 de octubre de 2018, 16:22:22 (UTC+2), Cameron D escribió:
>
> The rc5 and rc6 drivers shjipped with the weewx releases had issues where, 
> after some time (days to weeks) the system would stop reporting any data.
> That was addressed in this update of 24th September 
> <https://groups.google.com/d/topic/weewx-user/jUF4J6tRxPU/discussion>.
>
> At least two users have reported a different problem, where there is only 
> partial loss, for example wind or temperature and humidity.
>
>1. Juan Antonio Mosquera reports wind data missing 
><https://groups.google.com/d/msg/weewx-user/jUF4J6tRxPU/ABecLDR6AQAJ>.
>2. Markus Biewer reports temperature/humidity, and sometimes other data 
>going missing after about a week 
><https://groups.google.com/d/msg/weewx-user/7QUNDdqbHHE/z7Rr5lqZAgAJ>.
>
> Initially it looked like it might have been related to Belchertown skin, 
> but it is reported to also be an issue with the standard skin.
>
> The attached zip file has 3 files:
>
>1. *wmr300-v19rc6+f3.py*  - and updated version of the main wmr300 
>driver - this has a couple of minor bug fixes as well as extra diagnostic 
>code for this problem.
>2. *summ-pkt-data.awk*  -   an awk script to  convert the new 
>diagnostic logfile data into a csv file.
>3. *wmr300x-v19rc6+f3.py* - note the 'x'. This is the experimental 
>driver that uses pyusb 1 and libusb1 if available.  It also contains the 
>extra diagnostics, but is included for the other issue where the pi locks 
>up completely.
>
> *New Diagnostics*:
>
> In your weewx.conf file, enable
>   debug=1
>
> and in the WMR300 section I would suggest the following:
> debug_counts = 1
> debug_decode = 0
> debug_comm = 0
> debug_history = 0
> debug_timing = 1
> debug_rain = 0
>
> The debug_counts setting will output a summary of each packet type read 
> from the USB  in a specified time interval (default 20 seconds) as well as 
> the number of loop packets sent to weewx.
>
> Here is my WMR300 section
>
> ##
&g

[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

[Juan Antonio Mosquera]

In the first tests with the WMR300 and WMR300x driver neither of them 
obtains the wind data.

Greetings and thanks.

El jueves, 4 de octubre de 2018, 16:22:22 (UTC+2), Cameron D escribió:
>
> The rc5 and rc6 drivers shjipped with the weewx releases had issues where, 
> after some time (days to weeks) the system would stop reporting any data.
> That was addressed in this update of 24th September 
> <https://groups.google.com/d/topic/weewx-user/jUF4J6tRxPU/discussion>.
>
> At least two users have reported a different problem, where there is only 
> partial loss, for example wind or temperature and humidity.
>
>1. Juan Antonio Mosquera reports wind data missing 
><https://groups.google.com/d/msg/weewx-user/jUF4J6tRxPU/ABecLDR6AQAJ>.
>2. Markus Biewer reports temperature/humidity, and sometimes other data 
>going missing after about a week 
><https://groups.google.com/d/msg/weewx-user/7QUNDdqbHHE/z7Rr5lqZAgAJ>.
>
> Initially it looked like it might have been related to Belchertown skin, 
> but it is reported to also be an issue with the standard skin.
>
> The attached zip file has 3 files:
>
>1. *wmr300-v19rc6+f3.py*  - and updated version of the main wmr300 
>driver - this has a couple of minor bug fixes as well as extra diagnostic 
>code for this problem.
>2. *summ-pkt-data.awk*  -   an awk script to  convert the new 
>diagnostic logfile data into a csv file.
>3. *wmr300x-v19rc6+f3.py* - note the 'x'. This is the experimental 
>driver that uses pyusb 1 and libusb1 if available.  It also contains the 
>extra diagnostics, but is included for the other issue where the pi locks 
>up completely.
>
> *New Diagnostics*:
>
> In your weewx.conf file, enable
>   debug=1
>
> and in the WMR300 section I would suggest the following:
> debug_counts = 1
> debug_decode = 0
> debug_comm = 0
> debug_history = 0
> debug_timing = 1
> debug_rain = 0
>
> The debug_counts setting will output a summary of each packet type read 
> from the USB  in a specified time interval (default 20 seconds) as well as 
> the number of loop packets sent to weewx.
>
> Here is my WMR300 section
>
> ##
>
> [WMR300]
> # This section is for WMR300 weather stations
>
> # The station model, e.g., WMR300A
> model = WMR300
>
> # The driver to use:
> driver = user.wmr300-v19rc6+f3
>
> history_limit = 6
>
> debug_counts = 1
> debug_decode = 0
> debug_comm = 0
> debug_history = 1
> debug_timing = 1
> debug_rain = 0
>
>
> ##
>
> Note that I recommend placing these drivers in the "user" directory of the 
> weewx installation.
> You can also create a similar section named *[WMR300x]* to use the 
> experimental driver, and select between them by editing this line in the 
> *[Station]* section:
>  station_type = WMR300
>
> *Experimental driver:*
> This driver uses the PyUSB version 1 API, which allows it to use libusb1 
> or other usb libraries.
> It will default to libusb1 if possible, but otherwise will fall back to 
> libusb0.
>
> Note that some versions of Ubuntu seemed to ship with a beta version of 
> PyUSB-1 that did not seem to support the full api.  If it reports a version 
> beginning "1.0.0b..." then the driver will use libusb0.
>
> If you enable the experimental version then check the log file when it 
> starts up:
> It will always show pyusb_version, and the experimental driver will print 
> which usb backend library is selected.
>
> grep -i pyusb (your-logfile)
>
> will display both.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

the problem with the kernel happens to me with previous versions of weewx 
and the wmr300 driver.

El miércoles, 3 de octubre de 2018, 4:15:37 (UTC+2), Cameron D escribió:
>
> Sounds bad.  I guess the most likely issue is that they have changed the 
> USB kernel code in some way.
> I doubt that there is much I can do by way of debugging, as it seems 
> specifically tied to your kernel. Have you checked for other people 
> reporting USB issues with this version?
>
> All I can offer is you could try my experimental driver based on libusb1, 
> since that is the library that interacts most directly with the kernel usb 
> code.
> It will stay experimental, as Matthew has reasons for not complicating the 
> main driver.
> I have an updated version from what I posted last year, which is keeping 
> parallel with Matthew's changes.
>
> On Wednesday, 3 October 2018 00:48:02 UTC+10, Ruben Navarro Huedo wrote:
>>
>> It hang raspberry totally 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

Ok, no hay problema, te envío un correo.

El miércoles, 3 de octubre de 2018, 21:45:48 (UTC+2), Ruben Navarro Huedo 
escribió:
>
> Juan Antonio: Con el fin de intentar ver la causa del problema.
> ¿Sería posible ponerme en contacto contigo por privado?
>
> Mi email es runahue en gmail punto com
>
> Gracias
>
> El miércoles, 3 de octubre de 2018, 7:51:20 (UTC+2), Juan Antonio Mosquera 
> escribió:
>>
>> I have had the same problem, I have tried the following kernels and the 
>> one that I detected that does not cause the raspberry to turn off is the 
>> one I show at the end. total 64K drwxr-xr-x 16 root root 4.0K Sep 24 17:48. 
>> drwxr-xr-x 18 root root 4.0K Sep 22 12:04 .. drwxr-xr-x 3 root root 4.0K 
>> Sep 22 11:15 4.14.70+ drwxr-xr-x 3 root root 4.0K Sep 22 11:15 4.14.70-v7 + 
>> drwxr-xr-x 3 root root 4.0K Sep 22 10:39 4.14.71+ drwxr-xr-x 3 root root 
>> 4.0K Sep 22 10:39 4.14.71-v7 + drwxr-xr-x 3 root root 4.0K Sep 25 09:54 
>> 4.4.48+ drwxr-xr-x 3 root root 4.0K Sep 25 09:54 4.4.48-v7 + drwxr-xr-x 3 
>> root root 4.0K Jun 24 2017 4.9.33+ drwxr-xr-x 3 root root 4.0K Jun 24 2017 
>> 4.9.33-v7 + drwxr-xr-x 3 root root 4.0K Jul 23 2017 4.9.39+ drwxr-xr-x 3 
>> root root 4.0K Jul 23 2017 4.9.39-v7 + drwxr-xr-x 3 root root 4.0K Sep 24 
>> 17:49 4.9.51+ drwxr-xr-x 3 root root 4.0K Sep 24 17:49 4.9.51-v7 + 
>> drwxr-xr-x 3 root root 4.0K Sep 24 3:00 PM 4.9.80+ drwxr-xr-x 3 root root 
>> 4.0K Sep 24 15:00 4.9.80-v7 + pi @ meteomontaos: / lib / modules $ sudo 
>> uname -r 4.4.48+
>>
>> El miércoles, 3 de octubre de 2018, 4:15:37 (UTC+2), Cameron D escribió:
>>>
>>> Sounds bad.  I guess the most likely issue is that they have changed the 
>>> USB kernel code in some way.
>>> I doubt that there is much I can do by way of debugging, as it seems 
>>> specifically tied to your kernel. Have you checked for other people 
>>> reporting USB issues with this version?
>>>
>>> All I can offer is you could try my experimental driver based on 
>>> libusb1, since that is the library that interacts most directly with the 
>>> kernel usb code.
>>> It will stay experimental, as Matthew has reasons for not complicating 
>>> the main driver.
>>> I have an updated version from what I posted last year, which is keeping 
>>> parallel with Matthew's changes.
>>>
>>> On Wednesday, 3 October 2018 00:48:02 UTC+10, Ruben Navarro Huedo wrote:
>>>>
>>>> It hang raspberry totally 
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

The panel shows wind data, the anemometer moves, I have tried unplugging 
and plugging, everything works correctly. I have disabled Belchertown 
extension and it does not work either. Everything points to a bug in the 
driver.

Thank you.

El martes, 2 de octubre de 2018, 11:22:08 (UTC+2), Cameron D escribió:
>
> OK, I can see you have recorded zero wind reading for today. What does the 
> WMR300 console display?
> Do you have wind chill and heat index configured for hardware or software?
> If you have not changed the default from "prefer_hardware" then it 
> suggests that the console is also seeing zero wind speed, because (if I 
> translate the Spanish OK) then these values are tracking the temperature 
> exactly.
>
> Can you see the anemometer rotating?
>
> Cameron.
>
> On Tuesday, 2 October 2018 16:04:34 UTC+10, Juan Antonio Mosquera wrote:
>>
>> I have problems again, at a certain moment weewx stops receiving wind 
>> data. You can see it at www.meteomontaos.es
>> Greetings and thanks
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

I have had the same problem, I have tried the following kernels and the one 
that I detected that does not cause the raspberry to turn off is the one I 
show at the end. total 64K drwxr-xr-x 16 root root 4.0K Sep 24 17:48. 
drwxr-xr-x 18 root root 4.0K Sep 22 12:04 .. drwxr-xr-x 3 root root 4.0K 
Sep 22 11:15 4.14.70+ drwxr-xr-x 3 root root 4.0K Sep 22 11:15 4.14.70-v7 + 
drwxr-xr-x 3 root root 4.0K Sep 22 10:39 4.14.71+ drwxr-xr-x 3 root root 
4.0K Sep 22 10:39 4.14.71-v7 + drwxr-xr-x 3 root root 4.0K Sep 25 09:54 
4.4.48+ drwxr-xr-x 3 root root 4.0K Sep 25 09:54 4.4.48-v7 + drwxr-xr-x 3 
root root 4.0K Jun 24 2017 4.9.33+ drwxr-xr-x 3 root root 4.0K Jun 24 2017 
4.9.33-v7 + drwxr-xr-x 3 root root 4.0K Jul 23 2017 4.9.39+ drwxr-xr-x 3 
root root 4.0K Jul 23 2017 4.9.39-v7 + drwxr-xr-x 3 root root 4.0K Sep 24 
17:49 4.9.51+ drwxr-xr-x 3 root root 4.0K Sep 24 17:49 4.9.51-v7 + 
drwxr-xr-x 3 root root 4.0K Sep 24 3:00 PM 4.9.80+ drwxr-xr-x 3 root root 
4.0K Sep 24 15:00 4.9.80-v7 + pi @ meteomontaos: / lib / modules $ sudo 
uname -r 4.4.48+

El miércoles, 3 de octubre de 2018, 4:15:37 (UTC+2), Cameron D escribió:
>
> Sounds bad.  I guess the most likely issue is that they have changed the 
> USB kernel code in some way.
> I doubt that there is much I can do by way of debugging, as it seems 
> specifically tied to your kernel. Have you checked for other people 
> reporting USB issues with this version?
>
> All I can offer is you could try my experimental driver based on libusb1, 
> since that is the library that interacts most directly with the kernel usb 
> code.
> It will stay experimental, as Matthew has reasons for not complicating the 
> main driver.
> I have an updated version from what I posted last year, which is keeping 
> parallel with Matthew's changes.
>
> On Wednesday, 3 October 2018 00:48:02 UTC+10, Ruben Navarro Huedo wrote:
>>
>> It hang raspberry totally 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

I have problems again, at a certain moment weewx stops receiving wind data. 
You can see it at www.meteomontaos.es
Greetings and thanks

El lunes, 24 de septiembre de 2018, 3:03:37 (UTC+2), Cameron D escribió:
>
> I have attached an updated WMR300 driver, based on v19rc6 from v3.8.2
>
> The history clear has been reinstated, and an issue with the console 
> stopping data transmission has been fixed.
> This is done simply by identifying when no data has been received for a 
> minute and issuing an instruction to restart sending data.
>
> To install:
> Either:
>  * A.* you could rename it and overwrite the wmr300.py file in 
> weewx/drivers (having first made a backup)
> or
>   *B*. (safer)
>   1. copy the file into the "user" folder of the installation folder.
>   2. edit the weewx.conf file to point to the new driver: in the [WMR300] 
> section, change
> "driver = weewx.drivers.wmr300"
> to "driver = user.wmr300-v19rc6+fix"
>
> 
> the driver has extra options that you can enable if necessary:
> debug_history = 1
> debug_timing = 1
> 
> This code has been working continuously under weewx 3.8.0 for 6 months 
> with no hangs and many instances where it needed to restart the console.
> I have a 1 minute history interval and clear at 6%, which means the 
> history clear runs approx every 32 hours.
>
> Cameron
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

231/5000
I have an incidence that I do not know if it is due to the skin or to the 
driver of the WMR300 station, when it does not show wind data and when a 
few hours pass, it returns to show them. You can see it at 
http://www.meteomontaos.es/

Greetings.

El martes, 21 de agosto de 2018, 20:45:13 (UTC+2), Pat escribió:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick install:
>
> wget https://
> github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> sudo wee_extension --install weewx-belchertown-0.1.tar.gz
>
> Configure weewx.conf with your options
>
> Restart weewx
>
> Out of the box, it is a very basic theme. Make sure to check out the readme 
> for all options available !
>
>
> This is my first skin, and I've done all I could to test it out in various 
> environments to iron out any initial bugs. If you do find something that's 
> a little off, or room for improvement, please let me know!
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

Hola,

Curiosamente desde que he publicado el mensaje tengo datos continuamente... 

Gracias, saludos.

El miércoles, 26 de septiembre de 2018, 23:11:21 (UTC+2), Ruben Navarro 
Huedo escribió:
>
> Juan Antonio: Prueba un skin "normal" a ver que resultado tienes.
> Yo no he observado eso.
>
> El miércoles, 26 de septiembre de 2018, 21:33:51 (UTC+2), Juan Antonio 
> Mosquera escribió:
>>
>> I have detected a problem that I do not know if it is the driver or the 
>> skin (Belchertown). There are spaces in time that I do not have wind data, 
>> it can be seen in the capture that I attach.
>>
>> [image: Captura de pantalla de 2018-09-26 21-32-23.png]
>>
>>
>> Thank you.
>>
>> El lunes, 24 de septiembre de 2018, 3:03:37 (UTC+2), Cameron D escribió:
>>>
>>> I have attached an updated WMR300 driver, based on v19rc6 from v3.8.2
>>>
>>> The history clear has been reinstated, and an issue with the console 
>>> stopping data transmission has been fixed.
>>> This is done simply by identifying when no data has been received for a 
>>> minute and issuing an instruction to restart sending data.
>>>
>>> To install:
>>> Either:
>>>  * A.* you could rename it and overwrite the wmr300.py file in 
>>> weewx/drivers (having first made a backup)
>>> or
>>>   *B*. (safer)
>>>   1. copy the file into the "user" folder of the installation folder.
>>>   2. edit the weewx.conf file to point to the new driver: in the 
>>> [WMR300] section, change
>>> "driver = weewx.drivers.wmr300"
>>> to "driver = user.wmr300-v19rc6+fix"
>>>
>>> 
>>> the driver has extra options that you can enable if necessary:
>>> debug_history = 1
>>> debug_timing = 1
>>> 
>>> This code has been working continuously under weewx 3.8.0 for 6 months 
>>> with no hangs and many instances where it needed to restart the console.
>>> I have a 1 minute history interval and clear at 6%, which means the 
>>> history clear runs approx every 32 hours.
>>>
>>> Cameron
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

all info in:

https://github.com/poblabs/weewx-belchertown

El miércoles, 26 de septiembre de 2018, 22:00:42 (UTC+2), Thomas Sch 
escribió:
>
> Is there any manual? I dont know how to change it there...
>
> Am Mittwoch, 26. September 2018 21:49:27 UTC+2 schrieb Juan Antonio 
> Mosquera:
>>
>> yesss
>>
>> On Wed, Sep 26, 2018, 21:43 Thomas Sch  wrote:
>>
>>> Thanks for the answer :) How do I do this? in weewx.conf ?
>>>
>>> Am Mittwoch, 26. September 2018 21:31:46 UTC+2 schrieb Juan Antonio 
>>> Mosquera:
>>>>
>>>> Set station_url OK for css routes.
>>>>
>>>> Hi.
>>>>
>>>> El miércoles, 26 de septiembre de 2018, 21:14:18 (UTC+2), Thomas Sch 
>>>> escribió:
>>>>>
>>>>>
>>>>>>
>>>>> Hey I installed the beautiful skin. But my generated website is not 
>>>>> very looking good. Is there a solution? I hope anyone can help me :D
>>>>>
>>>>>  http://wilwetter.bplaced.net/wetterdaten/screenshot1.png
>>>>>
>>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

http://www.weewx.com/docs/usersguide.htm

station_url

El miércoles, 26 de septiembre de 2018, 22:00:42 (UTC+2), Thomas Sch 
escribió:
>
> Is there any manual? I dont know how to change it there...
>
> Am Mittwoch, 26. September 2018 21:49:27 UTC+2 schrieb Juan Antonio 
> Mosquera:
>>
>> yesss
>>
>> On Wed, Sep 26, 2018, 21:43 Thomas Sch  wrote:
>>
>>> Thanks for the answer :) How do I do this? in weewx.conf ?
>>>
>>> Am Mittwoch, 26. September 2018 21:31:46 UTC+2 schrieb Juan Antonio 
>>> Mosquera:
>>>>
>>>> Set station_url OK for css routes.
>>>>
>>>> Hi.
>>>>
>>>> El miércoles, 26 de septiembre de 2018, 21:14:18 (UTC+2), Thomas Sch 
>>>> escribió:
>>>>>
>>>>>
>>>>>>
>>>>> Hey I installed the beautiful skin. But my generated website is not 
>>>>> very looking good. Is there a solution? I hope anyone can help me :D
>>>>>
>>>>>  http://wilwetter.bplaced.net/wetterdaten/screenshot1.png
>>>>>
>>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

yesss

On Wed, Sep 26, 2018, 21:43 Thomas Sch  wrote:

> Thanks for the answer :) How do I do this? in weewx.conf ?
>
> Am Mittwoch, 26. September 2018 21:31:46 UTC+2 schrieb Juan Antonio
> Mosquera:
>>
>> Set station_url OK for css routes.
>>
>> Hi.
>>
>> El miércoles, 26 de septiembre de 2018, 21:14:18 (UTC+2), Thomas Sch
>> escribió:
>>>
>>>
>>>>
>>> Hey I installed the beautiful skin. But my generated website is not very
>>> looking good. Is there a solution? I hope anyone can help me :D
>>>
>>>  http://wilwetter.bplaced.net/wetterdaten/screenshot1.png
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

I have detected a problem that I do not know if it is the driver or the 
skin (Belchertown). There are spaces in time that I do not have wind data, 
it can be seen in the capture that I attach.

[image: Captura de pantalla de 2018-09-26 21-32-23.png]


Thank you.

El lunes, 24 de septiembre de 2018, 3:03:37 (UTC+2), Cameron D escribió:
>
> I have attached an updated WMR300 driver, based on v19rc6 from v3.8.2
>
> The history clear has been reinstated, and an issue with the console 
> stopping data transmission has been fixed.
> This is done simply by identifying when no data has been received for a 
> minute and issuing an instruction to restart sending data.
>
> To install:
> Either:
>  * A.* you could rename it and overwrite the wmr300.py file in 
> weewx/drivers (having first made a backup)
> or
>   *B*. (safer)
>   1. copy the file into the "user" folder of the installation folder.
>   2. edit the weewx.conf file to point to the new driver: in the [WMR300] 
> section, change
> "driver = weewx.drivers.wmr300"
> to "driver = user.wmr300-v19rc6+fix"
>
> 
> the driver has extra options that you can enable if necessary:
> debug_history = 1
> debug_timing = 1
> 
> This code has been working continuously under weewx 3.8.0 for 6 months 
> with no hangs and many instances where it needed to restart the console.
> I have a 1 minute history interval and clear at 6%, which means the 
> history clear runs approx every 32 hours.
>
> Cameron
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Set station_url OK for css routes.

Hi.

El miércoles, 26 de septiembre de 2018, 21:14:18 (UTC+2), Thomas Sch 
escribió:
>
>
>>
> Hey I installed the beautiful skin. But my generated website is not very 
> looking good. Is there a solution? I hope anyone can help me :D
>
>  http://wilwetter.bplaced.net/wetterdaten/screenshot1.png
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

It would also be interesting to activate and deactivate the graphics to be 
displayed. For example for stations that do not measure solar radiation. Thank 
you.


El viernes, 21 de septiembre de 2018, 20:17:39 (UTC+2), Juan Antonio 
Mosquera escribió:
>
> *ok ... I'm sorry, I had not noticed. But, another thing, it would be 
> interesting to be able to configure the texts to be displayed in the 
> weather forecast, the "Partly cloud" texts ... in this part of the code.*
>
>
>
>
>
>
> condition_text = ""
> if daily_data["icon"] == "clear-day":
> condition_text = "Despejado"
> elif daily_data["icon"] == "clear-night":
> condition_text = "Despejado"
> elif daily_data["icon"] == "rain":
> condition_text = "Lluvioso"
> elif daily_data["icon"] == "snow":
> condition_text = "Nevado"
> elif daily_data["icon"] == "sleet":
> condition_text = "Aguanieve"
> elif daily_data["icon"] == "wind":
> condition_text = "Ventoso"
> elif daily_data["icon"] == "fog":
> condition_text = "Niebla"
> elif daily_data["icon"] == "cloudy":
> condition_text = "Nublado"
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown extension + WMR300 stop data received.

[Juan Antonio Mosquera]

It seems that with the new driver everything is OK. I will inform you. 
Thank you!

El lunes, 24 de septiembre de 2018, 2:19:15 (UTC+2), Cameron D escribió:
>
> I will post the modified driver separately, but first, can you check 
> before and after the system stops working: there is a USB symbol in the 
> bottom left of the "today" window on the console display. Does it stay the 
> same?
>
> Cameron.
>
>
>
> On Sunday, 23 September 2018 17:43:49 UTC+10, Juan Antonio Mosquera wrote:
>>
>> Where can I find the corrected driver code ?. and how do I make the 
>> change?
>>
>> thanks
>>
>> El sábado, 22 de septiembre de 2018, 17:15:47 (UTC+2), Cameron D escribió:
>>>
>>> Hi,
>>> I can interpret the log, but I do not understand what it has to do with 
>>> the extension being active or not.
>>> Every 20 seconds you write an "a6" packet to the wmr300 console. This is 
>>> the heartbeat that keeps it transmitting.
>>> The console replies with a status packet "57"
>>> Then, at 09:56:58, the driver sends the a6 but there is no reply - the 
>>> console stops responding to the a6 packets and after 60 seconds stops 
>>> transmitting.
>>>
>>> I do not remember seeing this problem, but I think my driver fix posted 
>>> last April might correct it. It tries harder to restart the console loop.
>>>
>>> I ported my fix into rc6 and am just now testing it with 3.8.2. I will 
>>> post it in a day or so.
>>>
>>> However, I do not like the fact that the console apparently ignores 3 
>>> heartbeats in a row - it is like something is blocking the usb transmission 
>>> to the console.
>>>
>>> Cameron
>>>
>>>
>>> On Saturday, 22 September 2018 18:27:02 UTC+10, Juan Antonio Mosquera 
>>> wrote:
>>>>
>>>> ok, then I do not understand anything. Why turning off the extension is 
>>>> all good ?.
>>>> Can anyone interpret the debug comm log to identify the error?
>>>>
>>>> greetings and thanks.
>>>>
>>>> El sábado, 22 de septiembre de 2018, 10:19:09 (UTC+2), Paul Lacatus 
>>>> escribió:
>>>>>
>>>>> Hi Juan ,
>>>>>
>>>>> For me Raspberry Pi debian stretch , weewx 3.8.2 wmr300 driver and 
>>>>> Belchertown extension looks like being stable.  The messages with dump 
>>>>> history disabled appears in the logs
>>>>>
>>>>> Paul
>>>>>
>>>>> Sent from my iPad
>>>>>
>>>>> On 22 Sep 2018, at 10:49, Juan Antonio Mosquera <
>>>>> juananton...@juanantoniomosquera.com> wrote:
>>>>>
>>>>> I have deleted all the memory of the station and now it does not show 
>>>>> the message: *wmr300: dump history is disabled*, but at approximately 
>>>>> 3 hours the station stops sending data to weewx. If I deactivate 
>>>>> extension 
>>>>> everything works correctly.
>>>>>
>>>>> Greetings.
>>>>>
>>>>> El viernes, 21 de septiembre de 2018, 14:26:29 (UTC+2), Juan Antonio 
>>>>> Mosquera escribió:
>>>>>>
>>>>>> attach again...
>>>>>>
>>>>>>
>>>>>>
>>>>>> El viernes, 21 de septiembre de 2018, 14:24:48 (UTC+2), Juan Antonio 
>>>>>> Mosquera escribió:
>>>>>>>
>>>>>>>
>>>>>>> When I activate the Belchertown WMR300 extension to send data at 3 
>>>>>>> o'clock (random). Attached log with debug_comm activated.
>>>>>>>
>>>>>> -- 
>>>>> 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.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 driver update

[Juan Antonio Mosquera]

It seems that with the new driver everything is OK. I will inform you. 
Thank you!

El lunes, 24 de septiembre de 2018, 3:03:37 (UTC+2), Cameron D escribió:
>
> I have attached an updated WMR300 driver, based on v19rc6 from v3.8.2
>
> The history clear has been reinstated, and an issue with the console 
> stopping data transmission has been fixed.
> This is done simply by identifying when no data has been received for a 
> minute and issuing an instruction to restart sending data.
>
> To install:
> Either:
>  * A.* you could rename it and overwrite the wmr300.py file in 
> weewx/drivers (having first made a backup)
> or
>   *B*. (safer)
>   1. copy the file into the "user" folder of the installation folder.
>   2. edit the weewx.conf file to point to the new driver: in the [WMR300] 
> section, change
> "driver = weewx.drivers.wmr300"
> to "driver = user.wmr300-v19rc6+fix"
>
> 
> the driver has extra options that you can enable if necessary:
> debug_history = 1
> debug_timing = 1
> 
> This code has been working continuously under weewx 3.8.0 for 6 months 
> with no hangs and many instances where it needed to restart the console.
> I have a 1 minute history interval and clear at 6%, which means the 
> history clear runs approx every 32 hours.
>
> Cameron
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.