[weewx-user] Re: TE923 failed attempt read data after some time

[Pavel Kocanda]

I found the solution. Not very nice but working. I changed max_tries in 
te923.py from 5 to 10 and now it seems it works.

Dne sobota 25. srpna 2018 11:41:08 UTC+2 Pavel Kocanda napsal(a):
>
> Hello,
> I've installed weewx  and have constant problem.
> Raspberry Pi Zero W./Hideki TE857.
> Pure installation of Raspbian, updated. No software added except needed 
> for weewx.
> NTP installed and running.
> Instalation weewx by setup.py or .deb = the same trouble
> In NTB the same version works correct.
>
> weewx started well but instead of writting LOOPs writes:
> Failed attempt 1 of 5 to read data: Bad header byte: 81 != 5a
> Failed attempt 2 of 5 to read data: Bad header byte: 3e != 5a
> Record is added to database.
> It takes sometimes half hour, sometimes 1 hour.
> Later writes 3 of 5 and then 5 of 5 and ended.
>
> I tried to set init loop true and it continues with
> Failed attempt 5 of 5 to read data: [Errno 110] Operation timed out
> After reboot, reconnect the same.
>
> Can anybody kick me to right solution?
> Thanks.
> Unable to load driver: Read failed after 5 tries
> No records added.
>

-- 
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: TE923 failed attempt read data after some time

[Pavel Kocanda]

Dne sobota 25. srpna 2018 11:41:08 UTC+2 Pavel Kocanda napsal(a):
>
> Hello,
> I've installed weewx  and have constant problem.
> Raspberry Pi Zero W./Hideki TE857.
> Pure installation of Raspbian, updated. No software added except needed 
> for weewx.
> NTP installed and running.
> Instalation weewx by setup.py or .deb = the same trouble
> In NTB the same version works correct.
>
> weewx started well but instead of writting LOOPs writes:
> Failed attempt 1 of 5 to read data: Bad header byte: 81 != 5a
> Failed attempt 2 of 5 to read data: Bad header byte: 3e != 5a
> Record is added to database.
> It takes sometimes half hour, sometimes 1 hour.
> Later writes 3 of 5 and then 5 of 5 and ended.
>
> I tried to set init loop true and it continues with
> Failed attempt 5 of 5 to read data: [Errno 110] Operation timed out
> After reboot, reconnect the same.
>
> Can anybody kick me to right solution?
> Thanks.
> Unable to load driver: Read failed after 5 tries
> No records added.
>

-- 
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: stopping log messages from mesowx raw

[Andrew Milner]

no rush - cos the bastardised change fixed the immediate problem in a very 
crude manner, but a better method would be appreciated!!



On Sunday, 26 August 2018 07:06:54 UTC+3, gjr80 wrote:
>
> Ok, will have a look later and see what I can figure out.
>
> Gary
>
> On Sunday, 26 August 2018 14:04:14 UTC+10, Andrew Milner wrote:
>>
>> Hi Gary
>> Yes, it uses the weewx manager.  I am afraid that the concepts of classes 
>> and subclasses are beyond my comprehension.  I have bastardised weewx by 
>> editing manager.py to only log a message if database is NOT mesowx, which 
>> has at least stopped the log being overrun with 2 second record add 
>> entries!!
>> I would prefer a better method though, since obviously I need to remember 
>> this edit with any weewx upgrades in the future.
>>
>>
>>
>> On Sunday, 26 August 2018 06:59:13 UTC+3, gjr80 wrote:
>>>
>>> Andrew,
>>>
>>> Not familiar with mesowx raw service, is it using the Manager class in 
>>> manager.py to add records using its addRecord method? If so the addRecord 
>>> method supports changing the log level it uses, but it appears that WeeWX 
>>> does not give the user the ability to change this log level without editing 
>>> the WeeWX code. That being said, in in a vanilla WeeWX install it would be 
>>> very easy to subclass StdArchive to make use of this ability to change the 
>>> log level. As for mesowx that really depends on how mesowx is 
>>> structured/operates, it may be just as simple, it may not. Can you post the 
>>> offending log entries, that will give me an idea. Tied up otherwise this 
>>> arvo but can have a dig through mesowx later.
>>>
>>> Gary
>>>
>>> On Sunday, 26 August 2018 13:47:17 UTC+10, Andrew Milner wrote:

 Is there a way to stop log messages from manager when records are added 
 to a database?  The mesowx raw service seems to log every loop record 
 added 
 to the loop database - and whilst this was never a problem with a FO 
 station and a loop record every 53 seconds, it is a huge logging overhead 
 with my new VP2 and 2 second loop intervals!!

>>>

-- 
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: stopping log messages from mesowx raw

[gjr80]

Ok, will have a look later and see what I can figure out.

Gary

On Sunday, 26 August 2018 14:04:14 UTC+10, Andrew Milner wrote:
>
> Hi Gary
> Yes, it uses the weewx manager.  I am afraid that the concepts of classes 
> and subclasses are beyond my comprehension.  I have bastardised weewx by 
> editing manager.py to only log a message if database is NOT mesowx, which 
> has at least stopped the log being overrun with 2 second record add 
> entries!!
> I would prefer a better method though, since obviously I need to remember 
> this edit with any weewx upgrades in the future.
>
>
>
> On Sunday, 26 August 2018 06:59:13 UTC+3, gjr80 wrote:
>>
>> Andrew,
>>
>> Not familiar with mesowx raw service, is it using the Manager class in 
>> manager.py to add records using its addRecord method? If so the addRecord 
>> method supports changing the log level it uses, but it appears that WeeWX 
>> does not give the user the ability to change this log level without editing 
>> the WeeWX code. That being said, in in a vanilla WeeWX install it would be 
>> very easy to subclass StdArchive to make use of this ability to change the 
>> log level. As for mesowx that really depends on how mesowx is 
>> structured/operates, it may be just as simple, it may not. Can you post the 
>> offending log entries, that will give me an idea. Tied up otherwise this 
>> arvo but can have a dig through mesowx later.
>>
>> Gary
>>
>> On Sunday, 26 August 2018 13:47:17 UTC+10, Andrew Milner wrote:
>>>
>>> Is there a way to stop log messages from manager when records are added 
>>> to a database?  The mesowx raw service seems to log every loop record added 
>>> to the loop database - and whilst this was never a problem with a FO 
>>> station and a loop record every 53 seconds, it is a huge logging overhead 
>>> with my new VP2 and 2 second loop intervals!!
>>>
>>

-- 
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: MQTT with Belchertown skin - errors, No module named mqtt

[Colin Larsen]

With a test client I've discovered that CloudMQTT require a username and
password to be sent for the websocket connections (TLS only too so it's a
wss connection) - that needs adding into skin.conf Pat I guess please.

Cheers
Colin

On Sun, Aug 26, 2018 at 2:04 PM Colin Larsen  wrote:

> Now I just have to get the skin.conf to read it back
>
> These are the instance settings at CloudMQTT
>
>
> Instance info
>
> Server m11.cloudmqtt.com
> User
>  Restart
> Password
>  Rotate
> Port 13147
> SSL Port 23147
> Websockets Port (TLS only) 33147
> Connection limit 5
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> And here is the skin.conf section .
>
>
>
> # MQTT Defaults
>
> mqtt_enabled = 1
>
> mqtt_host = "m11.cloudmqtt.com"
>
> mqtt_port = 33147
>
> mqtt_ssl = 0
>
> mqtt_topic = "weather/41south/loop"
>
> disconnect_live_website_visitor = 180
>
>
>
> Not quite sure what is awry - Pat?
>
>
>
>
> On Sun, Aug 26, 2018 at 1:44 PM Colin Larsen 
> wrote:
>
>> Thanks John! I used the installer rather than Pat's manual method and it
>> works great now :)
>>
>> Ignore the data values it's working on Simulator only at the moment
>>
>> weather/41south/loop {"cloudbase_meter": "385.160767033", "outHumidity":
>> "79.9998437932", "pressure_mbar": "1053.16654107", "rain_cm": "0.0",
>> "barometer_mbar": "1053.16654107", "dewpoint_C": "-2.69897261268",
>> "windGust_kph": "5.02780872081e-05", "heatindex_C": "0.341840163469",
>> "dayRain_cm": "0.508", "inDewpoint_C": "-0.511415146209", "altimeter_mbar":
>> "1053.61058559", "windchill_C": "0.341840163469", "appTemp_C":
>> "-2.00597980905", "outTemp_C": "0.341840163469", "windGustDir":
>> "359.999062759", "humidex_C": "0.341840163469", "rain24_cm": "0.508",
>> "inTemp_C": "17.800764", "windSpeed_kph": "4.1898406007e-05",
>> "usUnits": "16.0", "UV": "11.4155207049", "rainRate_cm_per_hour": "0.0",
>> "dateTime": "1535247709.0", "windDir": "359.999062759", "inHumidity":
>> "29.9997917248", "radiation_Wpm2": "815.394336067"}
>>
>> On Sun, Aug 26, 2018 at 1:26 PM John Smith 
>> wrote:
>>
>>>
>>>
>>> On Sunday, 26 August 2018 11:18:40 UTC+10, Colin Larsen wrote:

 Aug 26 13:10:14 raspberrypi weewx[3191]:   ImportError: No
 module named mqtt



>>>
 The mqtt.py file is in /usr/share/weewx/  as per below (I'll change the
 permissions for read-only shortly)



>>> You need to put it in /usr/share/weewx/user/
>>>
>>> --
>>> 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.
>>>
>>

-- 
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: stopping log messages from mesowx raw

[Andrew Milner]

Hi Gary
Yes, it uses the weewx manager.  I am afraid that the concepts of classes 
and subclasses are beyond my comprehension.  I have bastardised weewx by 
editing manager.py to only log a message if database is NOT mesowx, which 
has at least stopped the log being overrun with 2 second record add 
entries!!
I would prefer a better method though, since obviously I need to remember 
this edit with any weewx upgrades in the future.



On Sunday, 26 August 2018 06:59:13 UTC+3, gjr80 wrote:
>
> Andrew,
>
> Not familiar with mesowx raw service, is it using the Manager class in 
> manager.py to add records using its addRecord method? If so the addRecord 
> method supports changing the log level it uses, but it appears that WeeWX 
> does not give the user the ability to change this log level without editing 
> the WeeWX code. That being said, in in a vanilla WeeWX install it would be 
> very easy to subclass StdArchive to make use of this ability to change the 
> log level. As for mesowx that really depends on how mesowx is 
> structured/operates, it may be just as simple, it may not. Can you post the 
> offending log entries, that will give me an idea. Tied up otherwise this 
> arvo but can have a dig through mesowx later.
>
> Gary
>
> On Sunday, 26 August 2018 13:47:17 UTC+10, Andrew Milner wrote:
>>
>> Is there a way to stop log messages from manager when records are added 
>> to a database?  The mesowx raw service seems to log every loop record added 
>> to the loop database - and whilst this was never a problem with a FO 
>> station and a loop record every 53 seconds, it is a huge logging overhead 
>> with my new VP2 and 2 second loop intervals!!
>>
>

-- 
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: stopping log messages from mesowx raw

[gjr80]

Andrew,

Not familiar with mesowx raw service, is it using the Manager class in 
manager.py to add records using its addRecord method? If so the addRecord 
method supports changing the log level it uses, but it appears that WeeWX 
does not give the user the ability to change this log level without editing 
the WeeWX code. That being said, in in a vanilla WeeWX install it would be 
very easy to subclass StdArchive to make use of this ability to change the 
log level. As for mesowx that really depends on how mesowx is 
structured/operates, it may be just as simple, it may not. Can you post the 
offending log entries, that will give me an idea. Tied up otherwise this 
arvo but can have a dig through mesowx later.

Gary

On Sunday, 26 August 2018 13:47:17 UTC+10, Andrew Milner wrote:
>
> Is there a way to stop log messages from manager when records are added to 
> a database?  The mesowx raw service seems to log every loop record added to 
> the loop database - and whilst this was never a problem with a FO station 
> and a loop record every 53 seconds, it is a huge logging overhead with my 
> new VP2 and 2 second loop intervals!!
>

-- 
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] stopping log messages from mesowx raw

[Andrew Milner]

Is there a way to stop log messages from manager when records are added to 
a database?  The mesowx raw service seems to log every loop record added to 
the loop database - and whilst this was never a problem with a FO station 
and a loop record every 53 seconds, it is a huge logging overhead with my 
new VP2 and 2 second loop intervals!!

-- 
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: MQTT with Belchertown skin - errors, No module named mqtt

[Colin Larsen]

Now I just have to get the skin.conf to read it back

These are the instance settings at CloudMQTT


Instance info

Server m11.cloudmqtt.com
User
 Restart
Password
 Rotate
Port 13147
SSL Port 23147
Websockets Port (TLS only) 33147
Connection limit 5






























And here is the skin.conf section .



# MQTT Defaults

mqtt_enabled = 1

mqtt_host = "m11.cloudmqtt.com"

mqtt_port = 33147

mqtt_ssl = 0

mqtt_topic = "weather/41south/loop"

disconnect_live_website_visitor = 180



Not quite sure what is awry - Pat?




On Sun, Aug 26, 2018 at 1:44 PM Colin Larsen  wrote:

> Thanks John! I used the installer rather than Pat's manual method and it
> works great now :)
>
> Ignore the data values it's working on Simulator only at the moment
>
> weather/41south/loop {"cloudbase_meter": "385.160767033", "outHumidity":
> "79.9998437932", "pressure_mbar": "1053.16654107", "rain_cm": "0.0",
> "barometer_mbar": "1053.16654107", "dewpoint_C": "-2.69897261268",
> "windGust_kph": "5.02780872081e-05", "heatindex_C": "0.341840163469",
> "dayRain_cm": "0.508", "inDewpoint_C": "-0.511415146209", "altimeter_mbar":
> "1053.61058559", "windchill_C": "0.341840163469", "appTemp_C":
> "-2.00597980905", "outTemp_C": "0.341840163469", "windGustDir":
> "359.999062759", "humidex_C": "0.341840163469", "rain24_cm": "0.508",
> "inTemp_C": "17.800764", "windSpeed_kph": "4.1898406007e-05",
> "usUnits": "16.0", "UV": "11.4155207049", "rainRate_cm_per_hour": "0.0",
> "dateTime": "1535247709.0", "windDir": "359.999062759", "inHumidity":
> "29.9997917248", "radiation_Wpm2": "815.394336067"}
>
> On Sun, Aug 26, 2018 at 1:26 PM John Smith 
> wrote:
>
>>
>>
>> On Sunday, 26 August 2018 11:18:40 UTC+10, Colin Larsen wrote:
>>>
>>> Aug 26 13:10:14 raspberrypi weewx[3191]:   ImportError: No
>>> module named mqtt
>>>
>>>
>>>
>>
>>> The mqtt.py file is in /usr/share/weewx/  as per below (I'll change the
>>> permissions for read-only shortly)
>>>
>>>
>>>
>> You need to put it in /usr/share/weewx/user/
>>
>> --
>> 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.
>>
>

-- 
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: MQTT with Belchertown skin - errors, No module named mqtt

[Colin Larsen]

Thanks John! I used the installer rather than Pat's manual method and it
works great now :)

Ignore the data values it's working on Simulator only at the moment

weather/41south/loop {"cloudbase_meter": "385.160767033", "outHumidity":
"79.9998437932", "pressure_mbar": "1053.16654107", "rain_cm": "0.0",
"barometer_mbar": "1053.16654107", "dewpoint_C": "-2.69897261268",
"windGust_kph": "5.02780872081e-05", "heatindex_C": "0.341840163469",
"dayRain_cm": "0.508", "inDewpoint_C": "-0.511415146209", "altimeter_mbar":
"1053.61058559", "windchill_C": "0.341840163469", "appTemp_C":
"-2.00597980905", "outTemp_C": "0.341840163469", "windGustDir":
"359.999062759", "humidex_C": "0.341840163469", "rain24_cm": "0.508",
"inTemp_C": "17.800764", "windSpeed_kph": "4.1898406007e-05",
"usUnits": "16.0", "UV": "11.4155207049", "rainRate_cm_per_hour": "0.0",
"dateTime": "1535247709.0", "windDir": "359.999062759", "inHumidity":
"29.9997917248", "radiation_Wpm2": "815.394336067"}

On Sun, Aug 26, 2018 at 1:26 PM John Smith 
wrote:

>
>
> On Sunday, 26 August 2018 11:18:40 UTC+10, Colin Larsen wrote:
>>
>> Aug 26 13:10:14 raspberrypi weewx[3191]:   ImportError: No module
>> named mqtt
>>
>>
>>
>
>> The mqtt.py file is in /usr/share/weewx/  as per below (I'll change the
>> permissions for read-only shortly)
>>
>>
>>
> You need to put it in /usr/share/weewx/user/
>
> --
> 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.
>

-- 
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: MQTT with Belchertown skin - errors, No module named mqtt

[John Smith]

On Sunday, 26 August 2018 11:18:40 UTC+10, Colin Larsen wrote:
>
> Aug 26 13:10:14 raspberrypi weewx[3191]:   ImportError: No module 
> named mqtt
>
>
>  

> The mqtt.py file is in /usr/share/weewx/  as per below (I'll change the 
> permissions for read-only shortly)
>
>
>
You need to put it in /usr/share/weewx/user/ 

-- 
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] MQTT with Belchertown skin - errors, No module named mqtt

[Colin Larsen]

Hi Pat, I think this one may be for you ...


As per the above and below, I get the no module error setting up MQTT. I've
sanitised the the username and password to the MQTT service in the extract
of weewx.conf below, otherwise hopefully it's all as per your Github
instructions.


Aug 26 13:10:14 raspberrypi weewx[3191]: manager: Starting backfill of
daily summaries

Aug 26 13:10:14 raspberrypi weewx[3191]: restx: StationRegistry:
Registration not requested.

Aug 26 13:10:14 raspberrypi weewx[3191]: restx: Wunderground: Posting not
enabled.

Aug 26 13:10:14 raspberrypi weewx[3191]: restx: PWSweather: Posting not
enabled.

Aug 26 13:10:14 raspberrypi weewx[3191]: restx: CWOP: Posting not enabled.

Aug 26 13:10:14 raspberrypi weewx[3191]: restx: WOW: Posting not enabled.

Aug 26 13:10:14 raspberrypi weewx[3191]: restx: AWEKAS: Posting not enabled.

Aug 26 13:10:14 raspberrypi weewx[3191]: engine: Caught unrecoverable
exception in engine:

Aug 26 13:10:14 raspberrypi weewx[3191]:   No module named mqtt

Aug 26 13:10:14 raspberrypi weewx[3191]:   Traceback (most recent
call last):

Aug 26 13:10:14 raspberrypi weewx[3191]: File
"/usr/share/weewx/weewx/engine.py", line 871, in main

Aug 26 13:10:14 raspberrypi weewx[3191]:   engine =
engine_class(config_dict)

Aug 26 13:10:14 raspberrypi weewx[3191]: File
"/usr/share/weewx/weewx/engine.py", line 78, in __init__

Aug 26 13:10:14 raspberrypi weewx[3191]: 
self.loadServices(config_dict)

Aug 26 13:10:14 raspberrypi weewx[3191]: File
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices

Aug 26 13:10:14 raspberrypi weewx[3191]: 
self.service_obj.append(weeutil.weeutil._get_object(svc)(self,
config_dict))

Aug 26 13:10:14 raspberrypi weewx[3191]: File
"/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object

Aug 26 13:10:14 raspberrypi weewx[3191]:   mod =
__import__(module)

Aug 26 13:10:14 raspberrypi weewx[3191]:   ImportError: No module
named mqtt

Aug 26 13:10:14 raspberrypi weewx[3191]:   Exiting.

Aug 26 13:10:37 raspberrypi systemd[1]: Stopping LSB: weewx weather
system...

Aug 26 13:10:37 raspberrypi weewx[3227]: Stopping weewx weather system:
weewx not running

Aug 26 13:10:37 raspberrypi systemd[1]: Stopped LSB: weewx weather system.


The mqtt.py file is in /usr/share/weewx/  as per below (I'll change the
permissions for read-only shortly)


total 192

-rw-r--r-- 1 root root  2886 Aug 17 04:06 daemon.py

-rw-r--r-- 1 root root  2715 Aug 24 16:09 daemon.pyc

-rw-rw-rw- 1 root root 16926 Aug 26 12:14 mqtt.py

drwxr-xr-x 2 root root  4096 Aug 24 16:09 *schemas*

drwxr-xr-x 3 root root  4096 Aug 24 16:20 *user*

drwxr-xr-x 2 root root  4096 Aug 24 16:11 *weecfg*

-rwxr-xr-x 1 root root  5145 Aug 17 04:06 *wee_config*

-rwxr-xr-x 1 root root 36471 Aug 17 04:06 *wee_database*

drwxr-xr-x 2 root root  4096 Aug 24 16:09 *weedb*

-rwxr-xr-x 1 root root 16207 Aug 17 04:06 *wee_debug*

-rwxr-xr-x 1 root root  1681 Aug 17 04:06 *wee_device*

-rwxr-xr-x 1 root root  3118 Aug 17 04:06 *wee_extension*

drwxr-xr-x 2 root root  4096 Aug 24 16:09 *weeimport*

-rwxr-xr-x 1 root root 31159 Aug 17 04:06 *wee_import*

drwxr-xr-x 2 root root  4096 Aug 24 16:10 *weeplot*

-rwxr-xr-x 1 root root  2171 Aug 17 04:06 *wee_reports*

drwxr-xr-x 2 root root  4096 Aug 24 16:10 *weeutil*

drwxr-xr-x 3 root root  4096 Aug 24 16:10 *weewx*

-rwxr-xr-x 1 root root  2565 Aug 17 04:06 *weewxd*

-rwxr-xr-x 1 root root 20788 Aug 17 04:06 *wunderfixer*


[StdRESTful] .


[[MQTT]]

#This section is for the MQTT service setup

server_url = mqtt://user:passw...@m11.cloudmqtt.com:13147/

topic = weather/41south

unit_system = Metric

binding = archive, loop

aggregation = aggregate



[Engine]


[[Services]]



restful_services = .. weewx.restx.StdAWEKAS, user.mqtt.MQTT



What did I miss??


Thanks

Colin

-- 
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: Automatic Update to 3.8.2 Multiple Issues [SOLVED]

[G Hammer]

Same issue I had.

https://groups.google.com/d/msg/weewx-user/THW9dDxbioA/cHuTusr7BgAJ

-- 
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: Forecast and earthquake problems in Belchertown skin

[Colin Larsen]

You should probably use version 0.4 now.

Did you follow all of Pat's instructions on GitHub for doing a manual
installation?

Colin

On Sun, 26 Aug 2018, 07:26 John Clark,  wrote:

> If it makes any difference (although I don't think it does on this case) I
> did the python install and the command I use to start is sudo
> /etc/init.d/weewx start. Also, since *sudo wee_extension --install
> weewx-belchertown-0.1.tar.gz*  didn't work I just copied the contents to
> the skin directory
>
>
>
>
> On 8/25/2018 6:49 AM, gjr80 wrote:
>
> The issue has nothing to do with permissions, if you look at the error 
> message carefully you will see that the file being written includes a 
> relative path, but relative to what? Just as you were confused about what it 
> was referring to so to is python confused. What ever python is using as the 
> current directory does not have a public_html/json directory so the error is 
> thrown. Pat will need to look at his code, I suspect he needs to make sure 
> his path is relative to WEEWX_ROOT.
>
> As an aside, a default weeWX install sees the weeWX daemon run as root so in 
> such cases permissions are rarely an issue. Running weeWX directly may cause 
> permission issues unless sudo or other privileged access is used.
>
> Gary
>
>
>
> --
> *John Clark *
>
> --
> 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.
>

-- 
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: Forecast and earthquake problems in Belchertown skin

[John Clark]

If it makes any difference (although I don't think it does on this case) 
I did the python install and the command I use to start is sudo 
/etc/init.d/weewx start. Also, since /*|sudo wee_extension --install 
weewx-belchertown-0.1.tar.gz|*//**/ didn't work I just copied the 
contents to the skin directory






On 8/25/2018 6:49 AM, gjr80 wrote:

The issue has nothing to do with permissions, if you look at the error message 
carefully you will see that the file being written includes a relative path, 
but relative to what? Just as you were confused about what it was referring to 
so to is python confused. What ever python is using as the current directory 
does not have a public_html/json directory so the error is thrown. Pat will 
need to look at his code, I suspect he needs to make sure his path is relative 
to WEEWX_ROOT.

As an aside, a default weeWX install sees the weeWX daemon run as root so in 
such cases permissions are rarely an issue. Running weeWX directly may cause 
permission issues unless sudo or other privileged access is used.

Gary



--
*/John Clark /*

--
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: WS-3000

[Peter Grefges]

I have 5 sensors, but for a first start 2 would be fine (1x outdoor, 1x indoor).

-- 
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: Forecast and earthquake problems in Belchertown skin

[Pat]

If you leave HTML_ROOT as "belchertown", weewx will do the rest to put it 
into a sub directory of the StdReport's HTML_ROOT. 

Earthquake and Forecasts use these settings:
earthquake_file = self.generator.skin_dict['HTML_ROOT'] + "
/json/earthquake.json"

forecast_file = self.generator.skin_dict['HTML_ROOT'] + "
/json/darksky_forecast.json"


John, I'm wondering if within weewx.conf, what do you have under 
[[Belchertown]] for HTML_ROOT = public_html?


On Saturday, August 25, 2018 at 7:55:37 AM UTC-4, Andrew Milner wrote:
>
> tx Gary - yea I missed the relative bit - so Pat needs to either be 
> relative to WEEWX_ROOT (or change the path if he is relative to HTML_ROOT) 
> I guess.
>
>
>
> On Saturday, 25 August 2018 14:49:31 UTC+3, gjr80 wrote:
>>
>> The issue has nothing to do with permissions, if you look at the error 
>> message carefully you will see that the file being written includes a 
>> relative path, but relative to what? Just as you were confused about what 
>> it was referring to so to is python confused. What ever python is using as 
>> the current directory does not have a public_html/json directory so the 
>> error is thrown. Pat will need to look at his code, I suspect he needs to 
>> make sure his path is relative to WEEWX_ROOT.
>>
>> As an aside, a default weeWX install sees the weeWX daemon run as root so 
>> in such cases permissions are rarely an issue. Running weeWX directly may 
>> cause permission issues unless sudo or other privileged access is used.
>>
>> 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.

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

[Pat]

What do you have listed for the skin options within weewx.conf? 
Specifically the HTML_ROOT option?

Andrew's also right. Looks like everything else is updating and FTP'ing 
fine, just the skin isn't being processed. 

On Saturday, August 25, 2018 at 2:28:17 AM UTC-4, John Clark wrote:
>
> My problem is, as follows.
>
> Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: Found station at bus=002 
> device=006
> Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: next read in 12 seconds
> Aug 25 01:10:24 OptiPlex weewx[23765]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown.getAllStats', 'user.belchertown.getForecast', 
> 'user.belchertown.getEarthquake', 'user.belchertown.getNOAAdata', 
> 'user.belchertown.getSocialShare', 
> 'user.belchertown_highchartsSearchX.highchartsDay', 
> 'user.belchertown_highchartsSearchX.highchartsWeek', 
> 'user.belchertown_highchartsSearchX.highchartsMonth', 
> 'user.belchertown_highchartsSearchX.highchartsYear']
> Aug 25 01:10:24 OptiPlex weewx[23765]: manager: Daily summary version is 
> 2.0
> Aug 25 01:10:24 OptiPlex weewx[23765]: restx: Wunderground-PWS: Published 
> record 2018-08-25 01:10:00 CDT (1535177400)
> Aug 25 01:10:24 OptiPlex weewx[23765]: restx: PWSWeather: Published record 
> 2018-08-25 01:10:00 CDT (1535177400)
> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Caught unrecoverable 
> exception in generator weewx.cheetahgenerator.CheetahGenerator
> Aug 25 01:10:24 OptiPlex weewx[23765]:   Error writing 
> forecast info to public_html/json/darksky_forecast.json. Reason: [Errno 2] 
> No such file or directory: 'public_html/json/darksky_forecast.json'
> Aug 25 01:10:24 OptiPlex weewx[23765]:   Traceback (most 
> recent call last):
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
> Aug 25 01:10:24 OptiPlex weewx[23765]:   obj.start()
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
> Aug 25 01:10:24 OptiPlex weewx[23765]:   self.run()
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen = 
> self.generate(gen_dict[section_name], self.gen_ts)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
> Aug 25 01:10:24 OptiPlex weewx[23765]:   default_binding)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in _getSearchList
> Aug 25 01:10:24 OptiPlex weewx[23765]:   searchList += 
> obj.get_extension_list(timespan, db_lookup)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/user/belchertown.py", line 311, in get_extension_list
> Aug 25 01:10:24 OptiPlex weewx[23765]:   raise ValueError( 
> "Error writing forecast info to %s. Reason: %s" % ( forecast_file, e) )
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ValueError: Error 
> writing forecast info to public_html/json/darksky_forecast.json. Reason: 
> [Errno 2] No such file or directory: 
> 'public_html/json/darksky_forecast.json'
> Aug 25 01:10:24 OptiPlex weewx[23765]:   Generator terminated
> Aug 25 01:10:24 OptiPlex weewx[23765]: copygenerator: copied 1 files to 
> /home/weewx/public_html
> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Running report FTP
> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Found configuration 
> file /home/weewx/skins/Ftp/skin.conf for report FTP
> Aug 25 01:10:24 OptiPlex weewx[23765]: ftpupload: Attempting connection to 
> ftp.w0avq.org
> Aug 25 01:10:25 OptiPlex weewx[23765]: ftpupload: Connected to 
> ftp.w0avq.org
> Aug 25 01:10:26 OptiPlex weewx[23765]: ftpupload: Uploaded file 
> /weather/style.css
> Aug 25 01:10:27 OptiPlex weewx[23765]: ftpupload: Made directory 
> /weather/json/darksky_forecast.json
> Aug 25 01:10:28 OptiPlex weewx[23765]: ftpgenerator: ftp'd 1 files in 3.64 
> seconds
> Aug 25 01:10:28 OptiPlex weewx[23765]: reportengine: Running report RSYNC
> Aug 25 01:10:28 

Re: [weewx-user] Re: Forecast and earthquake problems in Belchertown skin

[Andrew Milner]

tx Gary - yea I missed the relative bit - so Pat needs to either be 
relative to WEEWX_ROOT (or change the path if he is relative to HTML_ROOT) 
I guess.



On Saturday, 25 August 2018 14:49:31 UTC+3, gjr80 wrote:
>
> The issue has nothing to do with permissions, if you look at the error 
> message carefully you will see that the file being written includes a 
> relative path, but relative to what? Just as you were confused about what 
> it was referring to so to is python confused. What ever python is using as 
> the current directory does not have a public_html/json directory so the 
> error is thrown. Pat will need to look at his code, I suspect he needs to 
> make sure his path is relative to WEEWX_ROOT.
>
> As an aside, a default weeWX install sees the weeWX daemon run as root so 
> in such cases permissions are rarely an issue. Running weeWX directly may 
> cause permission issues unless sudo or other privileged access is used.
>
> 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.

Re: [weewx-user] Re: Forecast and earthquake problems in Belchertown skin

[gjr80]

The issue has nothing to do with permissions, if you look at the error message 
carefully you will see that the file being written includes a relative path, 
but relative to what? Just as you were confused about what it was referring to 
so to is python confused. What ever python is using as the current directory 
does not have a public_html/json directory so the error is thrown. Pat will 
need to look at his code, I suspect he needs to make sure his path is relative 
to WEEWX_ROOT.

As an aside, a default weeWX install sees the weeWX daemon run as root so in 
such cases permissions are rarely an issue. Running weeWX directly may cause 
permission issues unless sudo or other privileged access is used.

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.

Re: [weewx-user] Re: Forecast and earthquake problems in Belchertown skin

[John Clark]

p.ublic_html, json, and darksky_forecast.json all show /*Mode: 
drwxrwxrwx (0777)*/


/*weewx shows Mode: drwxr_xr_x (0755) */This, I assume, is supposed to 
be on my computer, not the web server?



On 8/25/2018 3:45 AM, Andrew Milner wrote:

also permissions on the json directory



On Saturday, 25 August 2018 11:01:30 UTC+3, John Clark wrote:

/*(sorry for dupe message, forgot to reply to group)*/

BTW, if both the dark sky and earthquake settings are disabled in
Belchertown/skin.conf  all runs well.

Checked (and modified) permissions to ensure write permissions  on

/home /weewx/public_html/json/darksky_forecast.json and the error
messages are unchanged.


On 8/25/2018 1:58 AM, Andrew Milner wrote:

I suspect it may be a permissions issue - check the permissions
for the directory and file to ensure they are correct.

FYI weewx has not locked up - it still appears to be running
doing whatever tasks it can even though the cheetah generator has
exited - which will result in a lack of updated reports of course.



On Saturday, 25 August 2018 09:28:17 UTC+3, John Clark wrote:

My problem is, as follows.

Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: Found station
at bus=002 device=006
Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: next read in
12 seconds
Aug 25 01:10:24 OptiPlex weewx[23765]: cheetahgenerator:
using search list ['weewx.cheetahgenerator.Almanac',
'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current',
'weewx.cheetahgenerator.Stats',
'weewx.cheetahgenerator.UnitInfo',
'weewx.cheetahgenerator.Extras',
'user.belchertown.getAllStats',
'user.belchertown.getForecast',
'user.belchertown.getEarthquake',
'user.belchertown.getNOAAdata',
'user.belchertown.getSocialShare',
'user.belchertown_highchartsSearchX.highchartsDay',
'user.belchertown_highchartsSearchX.highchartsWeek',
'user.belchertown_highchartsSearchX.highchartsMonth',
'user.belchertown_highchartsSearchX.highchartsYear']
Aug 25 01:10:24 OptiPlex weewx[23765]: manager: Daily summary
version is 2.0
Aug 25 01:10:24 OptiPlex weewx[23765]: restx:
Wunderground-PWS: Published record 2018-08-25 01:10:00 CDT
(1535177400)
Aug 25 01:10:24 OptiPlex weewx[23765]: restx: PWSWeather:
Published record 2018-08-25 01:10:00 CDT (1535177400)
Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Caught
unrecoverable exception in generator
weewx.cheetahgenerator.CheetahGenerator
Aug 25 01:10:24 OptiPlex weewx[23765]:   Error writing
forecast info to public_html/json/darksky_forecast.json.
Reason: [Errno 2] No such file or directory:
'public_html/json/darksky_forecast.json'
Aug 25 01:10:24 OptiPlex weewx[23765]:   Traceback (most
recent call last):
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/reportengine.py", line 239, in run
Aug 25 01:10:24 OptiPlex weewx[23765]:   obj.start()
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/reportengine.py", line 273, in start
Aug 25 01:10:24 OptiPlex weewx[23765]:   self.run()
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen =
self.generate(gen_dict[section_name], self.gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in
generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen +=
self.generate(section[subsection], gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in
generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen +=
self.generate(section[subsection], gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in
generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   default_binding)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in
_getSearchList
Aug 25 01:10:24 OptiPlex weewx[23765]:   searchList
+= obj.get_extension_list(timespan, db_lookup)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File
"/home/weewx/bin/user/belchertown.py", line 311, in
get_extension_list
Aug 25 01:10:24 OptiPlex weewx[23765]:   raise
ValueError( "Error writing forecast info to %s. Reason: %s" %
( forecast_file, e) )
Aug 25 01:10:24 

[weewx-user] Re: Automatic Update to 3.8.2 Multiple Issues [SOLVED]

[Frank Frommelt]

Hi,

same "issue" on rapberry pi with raspbian.

Update was automatically performed from 3.8.0 to 3.8.2.
weewx.conf was backed up to weewx.conf.dpkg-old and a new weewx.conf was 
created that contained parts of my original customized weewx.conf (e.g. 
location, station name etc. was preserved but things like ftp, wunderground 
etc. were set to defaults).

Warm regards

Frank 

Am Donnerstag, 23. August 2018 21:27:08 UTC+2 schrieb mwall:
>
> On Thursday, August 23, 2018 at 1:31:50 PM UTC-4, john hutchison wrote:
>>
>>
>> The automatic update also did not import existing configuration changes 
>> from weewx.conf and instead performed a backup of the existing config file 
>> and replaced weewx.conf with the stock .dist version.
>>
>
> john,
>
> could you clarify what 'automatic update' means?  was this a debian 
> installation?  redhat?  how was the update initiated?
>
> m 
>

-- 
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: Forecast and earthquake problems in Belchertown skin

[Andrew Milner]

also permissions on the json directory



On Saturday, 25 August 2018 11:01:30 UTC+3, John Clark wrote:
>
> *(sorry for dupe message, forgot to reply to group)*
>
> BTW, if both the dark sky and earthquake settings are disabled in 
> Belchertown/skin.conf  all runs well.
>
> Checked (and modified) permissions to ensure write permissions  on 
>
> /home /weewx/public_html/json/darksky_forecast.json and the error 
> messages are unchanged. 
>
> On 8/25/2018 1:58 AM, Andrew Milner wrote:
>
> I suspect it may be a permissions issue - check the permissions for the 
> directory and file to ensure they are correct.
>
> FYI weewx has not locked up - it still appears to be running doing 
> whatever tasks it can even though the cheetah generator has exited - which 
> will result in a lack of updated reports of course.
>
>
>
> On Saturday, 25 August 2018 09:28:17 UTC+3, John Clark wrote: 
>>
>> My problem is, as follows.
>>
>> Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: Found station at bus=002 
>> device=006
>> Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: next read in 12 seconds
>> Aug 25 01:10:24 OptiPlex weewx[23765]: cheetahgenerator: using search 
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
>> 'user.belchertown.getAllStats', 'user.belchertown.getForecast', 
>> 'user.belchertown.getEarthquake', 'user.belchertown.getNOAAdata', 
>> 'user.belchertown.getSocialShare', 
>> 'user.belchertown_highchartsSearchX.highchartsDay', 
>> 'user.belchertown_highchartsSearchX.highchartsWeek', 
>> 'user.belchertown_highchartsSearchX.highchartsMonth', 
>> 'user.belchertown_highchartsSearchX.highchartsYear']
>> Aug 25 01:10:24 OptiPlex weewx[23765]: manager: Daily summary version is 
>> 2.0
>> Aug 25 01:10:24 OptiPlex weewx[23765]: restx: Wunderground-PWS: Published 
>> record 2018-08-25 01:10:00 CDT (1535177400)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: restx: PWSWeather: Published 
>> record 2018-08-25 01:10:00 CDT (1535177400)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Caught unrecoverable 
>> exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   Error writing 
>> forecast info to public_html/json/darksky_forecast.json. Reason: [Errno 2] 
>> No such file or directory: 'public_html/json/darksky_forecast.json'
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   Traceback (most 
>> recent call last):
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   obj.start()
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   self.run()
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen = 
>> self.generate(gen_dict[section_name], self.gen_ts)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
>> self.generate(section[subsection], gen_ts)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
>> self.generate(section[subsection], gen_ts)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   default_binding)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in _getSearchList
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   searchList += 
>> obj.get_extension_list(timespan, db_lookup)
>> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
>> "/home/weewx/bin/user/belchertown.py", line 311, in get_extension_list
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   raise 
>> ValueError( "Error writing forecast info to %s. Reason: %s" % ( 
>> forecast_file, e) )
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   ValueError: Error 
>> writing forecast info to public_html/json/darksky_forecast.json. Reason: 
>> [Errno 2] No such file or directory: 
>> 'public_html/json/darksky_forecast.json'
>> Aug 25 01:10:24 OptiPlex weewx[23765]:   Generator terminated
>> Aug 25 01:10:24 OptiPlex weewx[23765]: copygenerator: copied 1 files to 
>> /home/weewx/public_html
>> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Running report FTP
>> Aug 25 

[weewx-user] Forecast and earthquake problems in Belchertown skin

[John Clark]

/*(sorry for dupe message, forgot to reply to group)*/

BTW, if both the dark sky and earthquake settings are disabled in 
Belchertown/skin.conf  all runs well.


Checked (and modified) permissions to ensure write permissions on

/home /weewx/public_html/json/darksky_forecast.json and the error 
messages are unchanged.



On 8/25/2018 1:58 AM, Andrew Milner wrote:
I suspect it may be a permissions issue - check the permissions for 
the directory and file to ensure they are correct.


FYI weewx has not locked up - it still appears to be running doing 
whatever tasks it can even though the cheetah generator has exited - 
which will result in a lack of updated reports of course.




On Saturday, 25 August 2018 09:28:17 UTC+3, John Clark wrote:

My problem is, as follows.

Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: Found station at
bus=002 device=006
Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: next read in 12
seconds
Aug 25 01:10:24 OptiPlex weewx[23765]: cheetahgenerator: using
search list ['weewx.cheetahgenerator.Almanac',
'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
'weewx.cheetahgenerator.UnitInfo',
'weewx.cheetahgenerator.Extras', 'user.belchertown.getAllStats',
'user.belchertown.getForecast', 'user.belchertown.getEarthquake',
'user.belchertown.getNOAAdata', 'user.belchertown.getSocialShare',
'user.belchertown_highchartsSearchX.highchartsDay',
'user.belchertown_highchartsSearchX.highchartsWeek',
'user.belchertown_highchartsSearchX.highchartsMonth',
'user.belchertown_highchartsSearchX.highchartsYear']
Aug 25 01:10:24 OptiPlex weewx[23765]: manager: Daily summary
version is 2.0
Aug 25 01:10:24 OptiPlex weewx[23765]: restx: Wunderground-PWS:
Published record 2018-08-25 01:10:00 CDT (1535177400)
Aug 25 01:10:24 OptiPlex weewx[23765]: restx: PWSWeather:
Published record 2018-08-25 01:10:00 CDT (1535177400)
Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Caught
unrecoverable exception in generator
weewx.cheetahgenerator.CheetahGenerator
Aug 25 01:10:24 OptiPlex weewx[23765]:  Error writing
forecast info to public_html/json/darksky_forecast.json. Reason:
[Errno 2] No such file or directory:
'public_html/json/darksky_forecast.json'
Aug 25 01:10:24 OptiPlex weewx[23765]:  Traceback
(most recent call last):
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/reportengine.py", line 239, in run
Aug 25 01:10:24 OptiPlex weewx[23765]:   obj.start()
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/reportengine.py", line 273, in start
Aug 25 01:10:24 OptiPlex weewx[23765]:   self.run()
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen =
self.generate(gen_dict[section_name], self.gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen +=
self.generate(section[subsection], gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen +=
self.generate(section[subsection], gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   default_binding)
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in
_getSearchList
Aug 25 01:10:24 OptiPlex weewx[23765]:   searchList +=
obj.get_extension_list(timespan, db_lookup)
Aug 25 01:10:24 OptiPlex weewx[23765]:  File
"/home/weewx/bin/user/belchertown.py", line 311, in get_extension_list
Aug 25 01:10:24 OptiPlex weewx[23765]:   raise ValueError(
"Error writing forecast info to %s. Reason: %s" % ( forecast_file,
e) )
Aug 25 01:10:24 OptiPlex weewx[23765]:  ValueError:
Error writing forecast info to
public_html/json/darksky_forecast.json. Reason: [Errno 2] No such
file or directory: 'public_html/json/darksky_forecast.json'
Aug 25 01:10:24 OptiPlex weewx[23765]:  Generator
terminated
Aug 25 01:10:24 OptiPlex weewx[23765]: copygenerator: copied 1
files to /home/weewx/public_html
Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Running
report FTP
Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Found
configuration file /home/weewx/skins/Ftp/skin.conf for report FTP
Aug 25 01:10:24 OptiPlex weewx[23765]: ftpupload: 

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

[Andrew Milner]

I suspect it may be a permissions issue - check the permissions for the 
directory and file to ensure they are correct.

FYI weewx has not locked up - it still appears to be running doing whatever 
tasks it can even though the cheetah generator has exited - which will 
result in a lack of updated reports of course.



On Saturday, 25 August 2018 09:28:17 UTC+3, John Clark wrote:
>
> My problem is, as follows.
>
> Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: Found station at bus=002 
> device=006
> Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: next read in 12 seconds
> Aug 25 01:10:24 OptiPlex weewx[23765]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown.getAllStats', 'user.belchertown.getForecast', 
> 'user.belchertown.getEarthquake', 'user.belchertown.getNOAAdata', 
> 'user.belchertown.getSocialShare', 
> 'user.belchertown_highchartsSearchX.highchartsDay', 
> 'user.belchertown_highchartsSearchX.highchartsWeek', 
> 'user.belchertown_highchartsSearchX.highchartsMonth', 
> 'user.belchertown_highchartsSearchX.highchartsYear']
> Aug 25 01:10:24 OptiPlex weewx[23765]: manager: Daily summary version is 
> 2.0
> Aug 25 01:10:24 OptiPlex weewx[23765]: restx: Wunderground-PWS: Published 
> record 2018-08-25 01:10:00 CDT (1535177400)
> Aug 25 01:10:24 OptiPlex weewx[23765]: restx: PWSWeather: Published record 
> 2018-08-25 01:10:00 CDT (1535177400)
> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Caught unrecoverable 
> exception in generator weewx.cheetahgenerator.CheetahGenerator
> Aug 25 01:10:24 OptiPlex weewx[23765]:   Error writing 
> forecast info to public_html/json/darksky_forecast.json. Reason: [Errno 2] 
> No such file or directory: 'public_html/json/darksky_forecast.json'
> Aug 25 01:10:24 OptiPlex weewx[23765]:   Traceback (most 
> recent call last):
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
> Aug 25 01:10:24 OptiPlex weewx[23765]:   obj.start()
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
> Aug 25 01:10:24 OptiPlex weewx[23765]:   self.run()
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen = 
> self.generate(gen_dict[section_name], self.gen_ts)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
> Aug 25 01:10:24 OptiPlex weewx[23765]:   default_binding)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in _getSearchList
> Aug 25 01:10:24 OptiPlex weewx[23765]:   searchList += 
> obj.get_extension_list(timespan, db_lookup)
> Aug 25 01:10:24 OptiPlex weewx[23765]: File 
> "/home/weewx/bin/user/belchertown.py", line 311, in get_extension_list
> Aug 25 01:10:24 OptiPlex weewx[23765]:   raise ValueError( 
> "Error writing forecast info to %s. Reason: %s" % ( forecast_file, e) )
> Aug 25 01:10:24 OptiPlex weewx[23765]:   ValueError: Error 
> writing forecast info to public_html/json/darksky_forecast.json. Reason: 
> [Errno 2] No such file or directory: 
> 'public_html/json/darksky_forecast.json'
> Aug 25 01:10:24 OptiPlex weewx[23765]:   Generator terminated
> Aug 25 01:10:24 OptiPlex weewx[23765]: copygenerator: copied 1 files to 
> /home/weewx/public_html
> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Running report FTP
> Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Found configuration 
> file /home/weewx/skins/Ftp/skin.conf for report FTP
> Aug 25 01:10:24 OptiPlex weewx[23765]: ftpupload: Attempting connection to 
> ftp.w0avq.org
> Aug 25 01:10:25 OptiPlex weewx[23765]: ftpupload: Connected to 
> ftp.w0avq.org
> Aug 25 01:10:26 OptiPlex weewx[23765]: ftpupload: Uploaded file 
> /weather/style.css
> Aug 25 01:10:27 OptiPlex weewx[23765]: ftpupload: Made directory 
> /weather/json/darksky_forecast.json
> Aug 25 01:10:28 OptiPlex weewx[23765]: ftpgenerator: ftp'd 1 files in 3.64 
> seconds
> Aug 

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

[John Clark]

My problem is, as follows.

Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: Found station at bus=002 
device=006

Aug 25 01:10:24 OptiPlex weewx[23765]: acurite: next read in 12 seconds
Aug 25 01:10:24 OptiPlex weewx[23765]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getAllStats', 
'user.belchertown.getForecast', 'user.belchertown.getEarthquake', 
'user.belchertown.getNOAAdata', 'user.belchertown.getSocialShare', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']

Aug 25 01:10:24 OptiPlex weewx[23765]: manager: Daily summary version is 2.0
Aug 25 01:10:24 OptiPlex weewx[23765]: restx: Wunderground-PWS: 
Published record 2018-08-25 01:10:00 CDT (1535177400)
Aug 25 01:10:24 OptiPlex weewx[23765]: restx: PWSWeather: Published 
record 2018-08-25 01:10:00 CDT (1535177400)
Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Caught 
unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
Aug 25 01:10:24 OptiPlex weewx[23765]:   Error writing 
forecast info to public_html/json/darksky_forecast.json. Reason: [Errno 
2] No such file or directory: 'public_html/json/darksky_forecast.json'
Aug 25 01:10:24 OptiPlex weewx[23765]:   Traceback (most 
recent call last):
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/reportengine.py", line 239, in run

Aug 25 01:10:24 OptiPlex weewx[23765]:  obj.start()
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/reportengine.py", line 273, in start

Aug 25 01:10:24 OptiPlex weewx[23765]:  self.run()
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
Aug 25 01:10:24 OptiPlex weewx[23765]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate

Aug 25 01:10:24 OptiPlex weewx[23765]:  default_binding)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in _getSearchList
Aug 25 01:10:24 OptiPlex weewx[23765]:  searchList += 
obj.get_extension_list(timespan, db_lookup)
Aug 25 01:10:24 OptiPlex weewx[23765]:     File 
"/home/weewx/bin/user/belchertown.py", line 311, in get_extension_list
Aug 25 01:10:24 OptiPlex weewx[23765]:   raise 
ValueError( "Error writing forecast info to %s. Reason: %s" % ( 
forecast_file, e) )
Aug 25 01:10:24 OptiPlex weewx[23765]:   ValueError: Error 
writing forecast info to public_html/json/darksky_forecast.json. Reason: 
[Errno 2] No such file or directory: 
'public_html/json/darksky_forecast.json'

Aug 25 01:10:24 OptiPlex weewx[23765]:   Generator terminated
Aug 25 01:10:24 OptiPlex weewx[23765]: copygenerator: copied 1 files to 
/home/weewx/public_html

Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Running report FTP
Aug 25 01:10:24 OptiPlex weewx[23765]: reportengine: Found configuration 
file /home/weewx/skins/Ftp/skin.conf for report FTP
Aug 25 01:10:24 OptiPlex weewx[23765]: ftpupload: Attempting connection 
to ftp.w0avq.org

Aug 25 01:10:25 OptiPlex weewx[23765]: ftpupload: Connected to ftp.w0avq.org
Aug 25 01:10:26 OptiPlex weewx[23765]: ftpupload: Uploaded file 
/weather/style.css
Aug 25 01:10:27 OptiPlex weewx[23765]: ftpupload: Made directory 
/weather/json/darksky_forecast.json
Aug 25 01:10:28 OptiPlex weewx[23765]: ftpgenerator: ftp'd 1 files in 
3.64 seconds

Aug 25 01:10:28 OptiPlex weewx[23765]: reportengine: Running report RSYNC
Aug 25 01:10:28 OptiPlex weewx[23765]: reportengine: Found configuration 
file /home/weewx/skins/Rsync/skin.conf for report RSYNC
Aug 25 01:10:28 OptiPlex weewx[23765]: rsyncgenerator: rsync upload not 
requested. Skipped.
Aug 25 01:10:36 OptiPlex weewx[23765]: acurite: Found station at bus=002 
device=006


I could be wrong in my assessment, but my weewx locks up and doesn't 
update. I am assuming that what is meant by 
public_html/json/darksky_forecast.json is referring to

[weewx-user] Re: weewx_wd

[Kalli]

Hallo Gary
ich muss dich nochmal stören.

die Aktuelle Condition mit Wunderground und WD stimmen nicht Überein.
Wunderground zeigt = Partly Cloudy   und WD zeigt = cloudy
da kann doch was nicht stimmen, Wunderground ist richtig.
kannst du da nochmal drüber schauen..

cu. Kalli




Am Freitag, 24. August 2018 16:41:40 UTC+2 schrieb gjr80:
>
> Hallo Kalli,
>
> Die aktuellen Bedingungen werden von WeatherUnderground in festen 
> Intervallen erhalten. Eine Standardinstallation verwendet ein 
> 30-Minuten-Intervall. Sie können dieses Intervall nach oben oder nach 
> unten ändern, auch wenn es keinen Sinn hat, es kürzer als Ihre 
> Senderarchivierungszeit zu haben. Um den Standardwert zu ändern, fügen 
> Sie in der Datei weewx.conf die Option conditions_interval config unter 
> [Weewx-WD] 
> [[Supplementary]] [[[WU]]] wie folgt hinzu:
>
> [Weewx-WD]
> 
> 
> [[Supplementary]]
> 
> 
> [[[WU]]]
> 
> conditions_interval = xxx
>
> Wobei xxx das gewünschte Intervall in Sekunden ist (Standard ist 1800). Sie 
> müssen WeeWX neu laden oder neu starten, damit die Änderung wirksam wird. 
> Wenn 
> Sie im Logbuch des WeeWX-Startup genau hinsehen, sollten Sie einen Eintrag 
> sehen, der angibt, welche Intervalle verwendet werden (es gibt drei; 
> 'conditions', 'forecast' und 'almanac').
>
> Eine Sache, die wir im Hinterkopf behalten sollten, ist letztendlich, dass 
> WeatherUnderground weiß, wie oft und auf welcher Basis sie ihre aktuellen 
> Daten aktualisieren.
>
> The current conditions are obtained from WeatherUnderground at fixed 
> intervals. A default install uses a 30 minute interval. You can change this 
> interval up or down, though there is no point having it any shorter than 
> your station archive period. To change the default add a 
> conditions_interval config option under [Weewx-WD] [[Supplementary]] 
> [[[WU]]] in weewx.conf as follows:
>
> [Weewx-WD]
> 
> 
> [[Supplementary]]
> 
> 
> [[[WU]]]
> 
> conditions_interval = xxx
>
> where xxx is the interval you want in seconds (default is 1800). You will 
> need to do a config reload or restart WeeWX for the change to take effect. 
> If you look carefully in the log at the WeeWX startup you should see an 
> entry that indicates what intervals are in use (there are three; 
> conditions, forecast and almanac).
>
> One thing to keep in mind, ultimately we are at the whim of 
> WeatherUnderground as to how often and on what basis they update their 
> current conditions data.
>
>
> Gruß
>
> Gary
>
> On Friday, 24 August 2018 18:34:40 UTC+10, Kalli wrote:
>>
>> Hallo Gir80
>> ich habe festgestellt, das die Anzeige für das Aktuelle Wetter sehr lange 
>> dauert bis diese sich ändert.
>> Von Sonne nach Regen dauert sehr lange oder ändert sich garnicht, da 
>> sollte noch mal was gemacht werden.
>> denn wenn es Regnet sollte auch Aktuell: Regen da stehen.
>>
>> mfg. Kalli
>>
>> Am Donnerstag, 22. Februar 2018 22:07:13 UTC+1 schrieb Kalli:
>>>
>>> hallo
>>>
>>> ich benutze WD-Live 
>>> da wird aber leider die Mondphase nicht angezeigt. 
>>> muss da noch was eingesellt werden.
>>>
>>>
>>>
>>> Hello
>>>
>>> I use WD-Live
>>> but unfortunately the moon phase is not displayed.
>>> there must be something else set up.
>>>
>>> cu. Kalli
>>>
>>>

-- 
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.