Re: [weewx-user] Re: Multiple stations on one host [3]

[Chotechai Piyavongsiri]

Just to update because it is working now.
It has nothing to do with weewx multi which setups are fine. The issue is 
on weatherflowudp plugin which listens to udp port 50222 to grab sensors' 
data. I have my other single weewx instance running on another test server. 
When I run two-instance weewx on my production server, the one using 
weatherflowudp plugin cannot listen to udp port 50222 even the port is set 
as shared in both test and production server's weewx config. Once I stop 
weewx instance on my test server, the weewx second instance on my 
production server can grab data from udp port 50222 and produce updated 
HTML data.

I don't know why udp port 50222 cannot be shared; but that's another 
problem not relating to this topic.

Thank you.

On Tuesday, 5 October 2021 at 14:11:31 UTC+7 lang@googlemail.com wrote:

> When both your instances have/use identical skin.conf, index.html.tmpl 
> etc. settings for the Belchertown skin, they don't need to be separated. 
> But if you want to "individualize" the skins for each instance, then each 
> one would need their own one.
>
> On 05.10.2021 05:15, Chotechai Piyavongsiri wrote:
>
> Thank you for your detailed explanation. 
>
> I have two configs (weewx.conf, tempest.conf), two separated database 
> (weewx.sdb, tempest.sdb) in /var/lib/weewx, two separated HTML roots 
> (/var/html/weewx, var/html/tempest). I saw the second instance write 
> somethings in the /var/html/tempest directory; but not completed because of 
> errors along the process. However I have only one forecast.sdb. Could you 
> tell me more how to identify a specific forecast_tempest.sdb in the weewx 
> config?
>
> For belchertown skin, I'm not sure why we need two separated skins because 
> I understand that both instances are supposed to "read" the skin only?
>
> On Monday, 4 October 2021 at 17:39:24 UTC+7 lang@googlemail.com wrote:
>
>> You have probably not disabled the belchertown skin completely for the 
>> Cheetah Generator.
>>
>> What you have to make sure with two (or more) instances on the same 
>> server is:
>>
>> with two weewx instances on one and the same server you need two 
>> different weewx.conf
>> e.g. tempest.conf and 2ndstation.conf
>> and possibly also two different skin directories with a dedicated 
>> skin.conf (if both instances are using the same skin - one instance can use 
>> different skins at the same time, but when two instances share the same 
>> skin.conf everything must be identical).
>>
>> You will need to have a separate (sub-)directory for your html output 
>> (HTML_ROOT) for each instance (and each skin used by the instance) and you 
>> better have two separate directories for your databases (in case both use a 
>> database with the same name - or you rename one of them).
>>
>> Your issue looks to me that you may have not thoroughly and consequently 
>> assigned different names (and paths/directories) to the HTML_ROOTs, 
>> database bindings,databases etc. 
>>
>> When both instances run properly on both servers, there's no reason why 
>> they shouldn't run properly together on one server.
>>
>> I have separated in my installation the skins directory (i.e. created one 
>> for each instance - now each instance has its own, independent skin.conf 
>> for each skin it uses - e.g. /etc/weewx/inst1/skins and 
>> /etc/weewx/inst2/skins) and have the HTML_ROOT of each instance's 
>> weewx.conf point to there, and my databases carry the names of the instance 
>> in its name (even though that is not necessary if you separate them with 
>> directories, but with such a naming "convention" you sort of implicitly 
>> document where they belong to )
>>
>> If in your use case both of your instances need a forecast.sdb then you 
>> have to rename at least one of them - or place them in a different 
>> directory) - if you include the name of your instance, it could be 
>> forecast-inst1.sdb and forecast-inst2.sdb and they can both remain/stay in 
>> /var/lib/weewx. Then it's also easy to tell who/what belongs to where.
>>
>>
>> On 04.10.2021 11:00, Chotechai Piyavongsiri wrote:
>>
>> Even I disabled forecast from the bechertown skin (latest version), it 
>> still produces the error 
>> Oct  4 15:53:05 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
>> weewx.manager: Daily summary version is 4.0
>> Oct  4 15:53:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
>> MQTT: Published record 2021-10-04 15:53:12 +07 (167592)
>> Oct  4 15:55:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
>> MQTT: Published record 2021-10-04 15:55:12 +07 (167712

Re: [weewx-user] Re: Multiple stations on one host [2]

[Chotechai Piyavongsiri]

Thank you very much for your detailed explanation. 

I can confirm you that I have separated HTML root directories, weewx 
configs (named weewx.conf and tempest.conf), weewx.sdb and tempest.sdb 
(both  in /var/lib/weewx directory). However, I have only one forecast.sdb. 
Both instances use shared Belchertown skin directory.

I will try separated forecast.sdb; but I wonder why we need separated skin 
because both instances are supposed to "read" the skin only?

On Monday, 4 October 2021 at 17:39:24 UTC+7 lang@googlemail.com wrote:

> You have probably not disabled the belchertown skin completely for the 
> Cheetah Generator.
>
> What you have to make sure with two (or more) instances on the same server 
> is:
>
> with two weewx instances on one and the same server you need two different 
> weewx.conf
> e.g. tempest.conf and 2ndstation.conf
> and possibly also two different skin directories with a dedicated 
> skin.conf (if both instances are using the same skin - one instance can use 
> different skins at the same time, but when two instances share the same 
> skin.conf everything must be identical).
>
> You will need to have a separate (sub-)directory for your html output 
> (HTML_ROOT) for each instance (and each skin used by the instance) and you 
> better have two separate directories for your databases (in case both use a 
> database with the same name - or you rename one of them).
>
> Your issue looks to me that you may have not thoroughly and consequently 
> assigned different names (and paths/directories) to the HTML_ROOTs, 
> database bindings,databases etc. 
>
> When both instances run properly on both servers, there's no reason why 
> they shouldn't run properly together on one server.
>
> I have separated in my installation the skins directory (i.e. created one 
> for each instance - now each instance has its own, independent skin.conf 
> for each skin it uses - e.g. /etc/weewx/inst1/skins and 
> /etc/weewx/inst2/skins) and have the HTML_ROOT of each instance's 
> weewx.conf point to there, and my databases carry the names of the instance 
> in its name (even though that is not necessary if you separate them with 
> directories, but with such a naming "convention" you sort of implicitly 
> document where they belong to )
>
> If in your use case both of your instances need a forecast.sdb then you 
> have to rename at least one of them - or place them in a different 
> directory) - if you include the name of your instance, it could be 
> forecast-inst1.sdb and forecast-inst2.sdb and they can both remain/stay in 
> /var/lib/weewx. Then it's also easy to tell who/what belongs to where.
>
>
> On 04.10.2021 11:00, Chotechai Piyavongsiri wrote:
>
> Even I disabled forecast from the bechertown skin (latest version), it 
> still produces the error 
> Oct  4 15:53:05 bthoven-AP34-PRO weewx-tempest[20798] DEBUG weewx.manager: 
> Daily summary version is 4.0
> Oct  4 15:53:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:53:12 +07 (167592)
> Oct  4 15:55:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:55:12 +07 (167712)
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:56:12 +07 (167772)
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.manager: 
> Added record 2021-10-04 15:55:00 +07 (167700) to database 'tempest.sdb'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.manager: 
> Added record 2021-10-04 15:55:00 +07 (167700) to daily summary in 
> 'tempest.sdb'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Running reports for latest time in the database.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Running report 'Belchertown'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Found configuration file 
> /etc/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:55:00 +07 (16770

Re: [weewx-user] Re: Multiple stations on one host [2]

[Chotechai Piyavongsiri]

Thank you for your detailed explanation.

I have two configs (weewx.conf, tempest.conf), two separated database 
(weewx.sdb, tempest.sdb) in /var/lib/weewx, two separated HTML roots 
(/var/html/weewx, var/html/tempest). I saw the second instance write 
somethings in the /var/html/tempest directory; but not completed because of 
errors along the process. However I have only one forecast.sdb. Could you 
tell me more how to identify a specific forecast_tempest.sdb in the weewx 
config?

For belchertown skin, I'm not sure why we need two separated skins because 
I understand that both instances are supposed to "read" the skin only?

On Monday, 4 October 2021 at 17:39:24 UTC+7 lang@googlemail.com wrote:

> You have probably not disabled the belchertown skin completely for the 
> Cheetah Generator.
>
> What you have to make sure with two (or more) instances on the same server 
> is:
>
> with two weewx instances on one and the same server you need two different 
> weewx.conf
> e.g. tempest.conf and 2ndstation.conf
> and possibly also two different skin directories with a dedicated 
> skin.conf (if both instances are using the same skin - one instance can use 
> different skins at the same time, but when two instances share the same 
> skin.conf everything must be identical).
>
> You will need to have a separate (sub-)directory for your html output 
> (HTML_ROOT) for each instance (and each skin used by the instance) and you 
> better have two separate directories for your databases (in case both use a 
> database with the same name - or you rename one of them).
>
> Your issue looks to me that you may have not thoroughly and consequently 
> assigned different names (and paths/directories) to the HTML_ROOTs, 
> database bindings,databases etc. 
>
> When both instances run properly on both servers, there's no reason why 
> they shouldn't run properly together on one server.
>
> I have separated in my installation the skins directory (i.e. created one 
> for each instance - now each instance has its own, independent skin.conf 
> for each skin it uses - e.g. /etc/weewx/inst1/skins and 
> /etc/weewx/inst2/skins) and have the HTML_ROOT of each instance's 
> weewx.conf point to there, and my databases carry the names of the instance 
> in its name (even though that is not necessary if you separate them with 
> directories, but with such a naming "convention" you sort of implicitly 
> document where they belong to )
>
> If in your use case both of your instances need a forecast.sdb then you 
> have to rename at least one of them - or place them in a different 
> directory) - if you include the name of your instance, it could be 
> forecast-inst1.sdb and forecast-inst2.sdb and they can both remain/stay in 
> /var/lib/weewx. Then it's also easy to tell who/what belongs to where.
>
>
> On 04.10.2021 11:00, Chotechai Piyavongsiri wrote:
>
> Even I disabled forecast from the bechertown skin (latest version), it 
> still produces the error 
> Oct  4 15:53:05 bthoven-AP34-PRO weewx-tempest[20798] DEBUG weewx.manager: 
> Daily summary version is 4.0
> Oct  4 15:53:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:53:12 +07 (167592)
> Oct  4 15:55:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:55:12 +07 (167712)
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:56:12 +07 (167772)
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.manager: 
> Added record 2021-10-04 15:55:00 +07 (167700) to database 'tempest.sdb'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.manager: 
> Added record 2021-10-04 15:55:00 +07 (167700) to daily summary in 
> 'tempest.sdb'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Running reports for latest time in the database.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Running report 'Belchertown'
> Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
> weewx.reportengine: Found configuration file 
> /etc/weewx/skins/Belchertown/skin.conf for rep

[weewx-user] Re: Multiple stations on one host

[Chotechai Piyavongsiri]

gine:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/user/belchertown.py", line 636, in get_extension_list
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   eqdata = json.load( read_file )
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine: File 
"/usr/lib/python2.7/json/__init__.py", line 291, in load
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   **kw)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine: File 
"/usr/lib/python2.7/json/__init__.py", line 339, in loads
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   return _default_decoder.decode(s)
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine: File 
"/usr/lib/python2.7/json/decoder.py", line 364, in decode
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   obj, end = self.raw_decode(s, 
idx=_w(s, 0).end())
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine: File 
"/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   raise ValueError("No JSON object 
could be decoded")
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   ValueError: No JSON object could be 
decoded
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] ERROR 
weewx.reportengine:   Generator terminated
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] INFO 
weewx.reportengine: Copied 31 files to /var/www/bthofen.com/tempest
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG weewx.manager: 
Daily summary version is 4.0
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Report 'FTP' not enabled. Skipping.
Oct  4 15:56:16 bthoven-AP34-PRO weewx-tempest[20798] DEBUG 
weewx.reportengine: Report 'RSYNC' not enabled. Skipping.
Oct  4 15:57:16 bthoven-AP34-PRO weewx-tempest[20798] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:57:12 +07 (167832)


On Monday, 4 October 2021 at 15:49:03 UTC+7 Chotechai Piyavongsiri wrote:

> I just found out I can run more than one weewx instance from this thread. 
> I have two outdoor weather stations (weatherslueth and weatherflow 
> tempest). I already run weewx separately on two physical servers and both 
> are running fine. After I implement two instances on one of the server (one 
> that already hosts weatherslueth instance) with instance named weewx and 
> tempest. The former instance remains running fine without problem; but the 
> newly added instance for Tempest can start running and can't produce 
> webpages. I've checked /var/lib/weewx, it has forecast.sdb, weewx.sdb, 
> tempest.sdb, and weewxwd.sdb. I'm not sure the one forecast.sdb is supposed 
> to cater for both instances?
> The syslog for tempest instance, with debug on in tempest.conf:
>
> Oct  4 15:22:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:22:14 +07 (165734)
> Oct  4 15:23:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:23:14 +07 (165794)
> Oct  4 15:24:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:24:14 +07 (165854)
> Oct  4 15:25:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:25:14 +07 (165914)
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
> MQTT: Published record 2021-10-04 15:26:13 +07 (165973)
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.manager: 
> Added record 2021-10-04 15:25:00 +07 (165900) to database 'tempest.sdb'
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.manager: 
> Added record 2021-10-04 15:25:00 +07 (165900) to daily summary in 
> 'tempest.sdb'
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
> weewx.reportengine: Running reports for latest time in the database.
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
> weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
> weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
> Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
> weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
> Oct  4 15:26

[weewx-user] Re: Multiple stations on one host

[Chotechai Piyavongsiri]

I just found out I can run more than one weewx instance from this thread. I 
have two outdoor weather stations (weatherslueth and weatherflow tempest). 
I already run weewx separately on two physical servers and both are running 
fine. After I implement two instances on one of the server (one that 
already hosts weatherslueth instance) with instance named weewx and 
tempest. The former instance remains running fine without problem; but the 
newly added instance for Tempest can start running and can't produce 
webpages. I've checked /var/lib/weewx, it has forecast.sdb, weewx.sdb, 
tempest.sdb, and weewxwd.sdb. I'm not sure the one forecast.sdb is supposed 
to cater for both instances?
The syslog for tempest instance, with debug on in tempest.conf:

Oct  4 15:22:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:22:14 +07 (165734)
Oct  4 15:23:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:23:14 +07 (165794)
Oct  4 15:24:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:24:14 +07 (165854)
Oct  4 15:25:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:25:14 +07 (165914)
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:26:13 +07 (165973)
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.manager: 
Added record 2021-10-04 15:25:00 +07 (165900) to database 'tempest.sdb'
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.manager: 
Added record 2021-10-04 15:25:00 +07 (165900) to daily summary in 
'tempest.sdb'
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Running reports for latest time in the database.
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Running report 'Belchertown'
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.reportengine: Found configuration file 
/etc/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG 
weewx.cheetahgenerator: Using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'weewx.cheetahgenerator.JSONHelpers', u'user.belchertown.getData']
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] INFO weewx.restx: 
MQTT: Published record 2021-10-04 15:25:00 +07 (165900)
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] DEBUG weewx.manager: 
Daily summary version is 4.0
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine: Caught unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine:   Error downloading forecast data. Check 
the URL in your configuration and try again. You are trying to use URL: 
https://api.darksky.net/forecast//13.717268,100.590727?units=auto=en, 
and the error is: 
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine:   Traceback (most recent call last):
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/weewx/reportengine.py", line 196, in run
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine:   obj.start()
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/weewx/reportengine.py", line 281, in start
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine:   self.run()
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 152, in run
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 222, in generate
Oct  4 15:26:16 bthoven-AP34-PRO weewx-tempest[9908] ERROR 
weewx.reportengine:   ngen += 

[weewx-user] My WH24 wind cup stops moving

[Chotechai Piyavongsiri]

The wind cup stops moving. Is there any way to fix it? Thanks

What kind of screw for the wind cup? I can't find a suitable screwdriver.

-- 
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/6dcdc664-aeb2-47e0-afb5-11c715f94c14n%40googlegroups.com.

[weewx-user] Integrating internal temp/humidity sensors to Weatherflow Tempest, possible?

[Chotechai Piyavongsiri]

I'm now using WH24 as my external all-in-one sensors which sends data to my 
Ecowitt GW1000. It has been working well with my weewx. Lately, the 
humidity sensor in WH24 reported erratic values, so I purchased Ecowitt 
external sensor WH32 to replace temp/humidity values reported from WH24, 
via Ecowitt GW1000.

I also install Weatherflow Tempest for a few months now running on a 
testing server with a separate weewx.

If I'm going to retire my WH24 and use my Tempest as my main external 
sensors, my questions are:
- can I integrate the GW1000 indoor temp/humidity sensors data with Tempest 
so that I still have internal temp/humidity reported on my weewx
- if not, any indoor sensor I could use with Tempest.
- what weewx driver will allow my weewx to display both Tempest and indoor 
data in real time (or, say 16s, interval).

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/e45ffc19-b166-44aa-b149-72cdf7ea0a87n%40googlegroups.com.

Re: [weewx-user] Weewx to generate a customized text file every archival period?

[Chotechai Piyavongsiri]

Thanks.

On Wednesday, 26 August 2020 at 19:50:00 UTC+7 tke...@gmail.com wrote:

> The pressure values and times are easy. Something like 
> $yesteray.barometer.min $yesterday.barometer.mintime, etc.
>
> The histogram of wind directions does not exist. You'd have to write a search 
> list extension 
> <http://www.weewx.com/docs/customizing.htm#defining_new_tags> to do that. 
>
> -tk
>
> On Wed, Aug 26, 2020 at 1:43 AM Chotechai Piyavongsiri  
> wrote:
>
>> I've been running Weewx 4.x with Belchertown skin for quite some time.
>>
>> I intend to use Weewx, if possible, to generate a text file containing 
>> one row of summary data from weewx database. The output file will be 
>> replaced every archival period, e.g. every 5 minute:
>> *Sample data (1 row):*
>> 1005,2 00:02 1009,9 23:31 1009,5 02:38 1010,8 08:14 
>> 316.8,4.3,83.5,0.0,82.8,12.6,795.2,22.7,2132.6,182.9,2091.2,93.6,1901.9,60.5,1058.8,50.8
>>  
>> 20
>>
>> *Values description:*
>> *Pressure max/min: yesterday and today, each value separated by one 
>> space:*
>> yesterday lowest pressure value: .9
>> yesterday lowest pressure time: hh:mm
>> yesterday highest pressure value: .9
>> yesterday lowest pressure time: hh:mm
>> today lowest pressure value: .9
>> today lowest pressure time: hh:mm
>> today highest pressure value: .9
>> today lowest pressure time: hh:mm
>> Wind: direction, each value separated by comma (frequency of 16 wind 
>> directions in the last 24 hours
>> Each wind direction encompass 22.5 degrees (360 degree / 16 = 22.5 degree)
>> North (N) frequency  (wind direction value between 348.75-11.25 degree)
>> NNE frequency (wind direction value between 11.25-33.75 degree)
>> NE frequency (wind direction value between 33.75-56.25 degree)
>> ENE frequency.
>> E frequency.
>> ESE frequency
>> SE frequency
>> SSE frequency
>> S frequency
>> SSW
>> SW
>> WSW...
>> W
>> WNW
>> NW
>> NNW(wind direction value between 326.25 to 348.75)
>>
>> Can it be done by creating Weewx template; or I have to write some kind 
>> of coding to achieve it?
>>
>> 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/256759ee-e5d2-43cc-968b-b6167c3e375bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/256759ee-e5d2-43cc-968b-b6167c3e375bn%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/4665e86f-ccd4-4945-abd2-a5f92f4d31c9n%40googlegroups.com.

[weewx-user] Weewx to generate a customized text file every archival period?

[Chotechai Piyavongsiri]

I've been running Weewx 4.x with Belchertown skin for quite some time.

I intend to use Weewx, if possible, to generate a text file containing one 
row of summary data from weewx database. The output file will be replaced 
every archival period, e.g. every 5 minute:
*Sample data (1 row):*
1005,2 00:02 1009,9 23:31 1009,5 02:38 1010,8 08:14 
316.8,4.3,83.5,0.0,82.8,12.6,795.2,22.7,2132.6,182.9,2091.2,93.6,1901.9,60.5,1058.8,50.8
 
20

*Values description:*
*Pressure max/min: yesterday and today, each value separated by one space:*
yesterday lowest pressure value: .9
yesterday lowest pressure time: hh:mm
yesterday highest pressure value: .9
yesterday lowest pressure time: hh:mm
today lowest pressure value: .9
today lowest pressure time: hh:mm
today highest pressure value: .9
today lowest pressure time: hh:mm
Wind: direction, each value separated by comma (frequency of 16 wind 
directions in the last 24 hours
Each wind direction encompass 22.5 degrees (360 degree / 16 = 22.5 degree)
North (N) frequency  (wind direction value between 348.75-11.25 degree)
NNE frequency (wind direction value between 11.25-33.75 degree)
NE frequency (wind direction value between 33.75-56.25 degree)
ENE frequency.
E frequency.
ESE frequency
SE frequency
SSE frequency
S frequency
SSW
SW
WSW...
W
WNW
NW
NNW(wind direction value between 326.25 to 348.75)

Can it be done by creating Weewx template; or I have to write some kind of 
coding to achieve it?

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/256759ee-e5d2-43cc-968b-b6167c3e375bn%40googlegroups.com.

[weewx-user] Re: NULL data for some values with Cumulus Real-Time plugin

[Chotechai Piyavongsiri]

.So one would need to build a realtime file with the first full 
observation write the realtime file, update the current observation with 
the wind value, write another file and when it receives the next 
observation update every other values. Looping light that would make a more 
realtime file.

I'm looking forwards to this option too. Hope someone could have done this.

On Thursday, 6 August 2020 at 03:46:56 UTC+7 Hyrules wrote:

> I can confirm this as well I have the Weatherflow Tempest with the UDP 
> driver as well as the cumulus realtime service.  The station broadcast 
> packet on a time base. This makes a few different packet types. Wind, Obs 
> and Strikes as well as others. The only way to fix this is to bind the crt 
> plugin to the archive packet instead of the loop. It will generate a full 
> realtime.txt value without NULL values. The problem with this is that it's 
> not really realtime for the wind. I might try myself at creating a service 
> for a realtime tempest file. I have a few idea on how to do it. This is not 
> a bad thing in itself because you get data values faster this way for the 
> wind and realtime lightning strike events.
>
> Packet I see are the following : rapid_wind, hub_status, obs_st, 
> device_status, strike_evt
>
> Wind packet is emitted every 3 seconds
> Hub status packet every 10 seconds
> Observations every 60 seconds.
> Strikes are on event 
>
> So one would need to build a realtime file with the first full observation 
> write the realtime file, update the current observation with the wind 
> value, write another file and when it receives the next observation update 
> every other values. Looping light that would make a more realtime file.
>

-- 
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/3588a9c4-7c8e-4ec3-ab9c-6291b188f1afn%40googlegroups.com.

Re: [weewx-user] Re: Belchertown Skin, Websockets, Firefox Fail to Connect

[Chotechai Piyavongsiri]

With or without openvpn, all works fine for all browsers, except MS Edge, 
Chromium, developer edition not working if having openvpn connected. 
Strange.

On Wednesday, 5 August 2020 at 17:21:51 UTC+7 gary@gmail.com wrote:

> Odd that one browser for each of us refuses to connect.
> I'm not using a VPN, so yours works fine without the VPN but fails when 
> you use it?
>
>
>
> On 8/4/2020 11:55 PM, Chotechai Piyavongsiri wrote:
>
> I mean Microsoft Edge chromium.
>
> On Wednesday, 5 August 2020 at 10:54:10 UTC+7 Chotechai Piyavongsiri wrote:
>
>> I have no problem with any browsers, including Firefox. I'm using secured 
>> websockets. 
>> The only problem I have is with Microsoft Edge, WS will not work when I 
>> connect my OpenVPN, same message as you got (Firefox works). I still don't 
>> know the reason.
>>
>> On Tuesday, 4 August 2020 at 23:11:56 UTC+7 gary@gmail.com wrote:
>>
>>> I have a curious issue here. 
>>> I normally use Edge from Windows 10 to browse. All is working fine.
>>> I use Firefox in troubleshooting and browsed to my weather page.
>>> No connection to the websocket feed.
>>> Open Edge, no problem. Chrome from my phone, no problem. Safari from my 
>>> wife's iPhone, no problem.
>>>
>>> Disabled all plugins in Firefox, still get  Failed connecting to the 
>>> weather station. Please try again later! 
>>>
>>> Tried from a Linux machine using Firefox, same result.
>>>
>>> Any ideas?
>>>
>> -- 
> 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/nwHdhPVd5o0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/0c145e3e-1e5f-4cea-ba00-fc09059a60edn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/0c145e3e-1e5f-4cea-ba00-fc09059a60edn%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/745a2b9c-8adb-42b6-b35b-9377e8e88b2dn%40googlegroups.com.

[weewx-user] Re: Belchertown Skin, Websockets, Firefox Fail to Connect

[Chotechai Piyavongsiri]

I mean Microsoft Edge chromium.

On Wednesday, 5 August 2020 at 10:54:10 UTC+7 Chotechai Piyavongsiri wrote:

> I have no problem with any browsers, including Firefox. I'm using secured 
> websockets.
> The only problem I have is with Microsoft Edge, WS will not work when I 
> connect my OpenVPN, same message as you got (Firefox works). I still don't 
> know the reason.
>
> On Tuesday, 4 August 2020 at 23:11:56 UTC+7 gary@gmail.com wrote:
>
>> I have a curious issue here.
>> I normally use Edge from Windows 10 to browse. All is working fine.
>> I use Firefox in troubleshooting and browsed to my weather page.
>> No connection to the websocket feed.
>> Open Edge, no problem. Chrome from my phone, no problem. Safari from my 
>> wife's iPhone, no problem.
>>
>> Disabled all plugins in Firefox, still get  Failed connecting to the 
>> weather station. Please try again later! 
>>
>> Tried from a Linux machine using Firefox, same result.
>>
>> Any ideas?
>>
>

-- 
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/0c145e3e-1e5f-4cea-ba00-fc09059a60edn%40googlegroups.com.

[weewx-user] Re: Belchertown Skin, Websockets, Firefox Fail to Connect

[Chotechai Piyavongsiri]

I have no problem with any browsers, including Firefox. I'm using secured 
websockets.
The only problem I have is with Microsoft Edge, WS will not work when I 
connect my OpenVPN, same message as you got (Firefox works). I still don't 
know the reason.

On Tuesday, 4 August 2020 at 23:11:56 UTC+7 gary@gmail.com wrote:

> I have a curious issue here.
> I normally use Edge from Windows 10 to browse. All is working fine.
> I use Firefox in troubleshooting and browsed to my weather page.
> No connection to the websocket feed.
> Open Edge, no problem. Chrome from my phone, no problem. Safari from my 
> wife's iPhone, no problem.
>
> Disabled all plugins in Firefox, still get  Failed connecting to the 
> weather station. Please try again later! 
>
> Tried from a Linux machine using Firefox, same result.
>
> Any ideas?
>

-- 
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/4f0d6579-0c6d-45da-be48-c66618040951n%40googlegroups.com.

[weewx-user] Re: crt extension has been updated

[Chotechai Piyavongsiri]

Hi Mattany chance you could help to add realmore.txt file?...thanks

On Friday, 17 January 2020 at 08:39:33 UTC+7 Chotechai Piyavongsiri wrote:

> The bigger screenshot is here: Realmore.txt raw data and wind rose 
> <https://photos.app.goo.gl/TW6T59uFexH6enTw5>
>

-- 
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/3c1f8c0f-8b29-4af6-8cf6-5a130a604542n%40googlegroups.com.

[weewx-user] Re: weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

Adding windrose is now working. I did something wrong in the graphs.conf. 
I've started over by adding windRose again to the original graphs template 
and saved as graphs.conf.

Thank you everyone for taking time to help.

On Sunday, 2 August 2020 at 14:30:45 UTC+7 Chotechai Piyavongsiri wrote:

> I found that I made some mistakes in the graphs.conf file. If I use its 
> default graphs template. There is no more errors. What I customized to the 
> default graphs config was to add windRose graph. Not sure why it causes 
> errors.
>
> On Sunday, 2 August 2020 at 09:05:32 UTC+7 Chotechai Piyavongsiri wrote:
>
>> It still produces the same errors.
>>
>> When I look at mqtt data, it gives two different data formats at 
>> different frequency. The shorter format is for wind data which refreshes 
>> more frequently; while the other format is a more complete data including 
>> temp, humidity, uv...which comes every minute. The weewx database contains 
>> same consistent data in data fields on all records. I'm not sure the errors 
>> are due to the two different formats mqtt spits out?
>>
>

-- 
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/690ba3bd-b282-4a4b-bf63-6f6e49449a6en%40googlegroups.com.

[weewx-user] Re: weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

I found that I made some mistakes in the graphs.conf file. If I use its 
default graphs template. There is no more errors. What I customized to the 
default graphs config was to add windRose graph. Not sure why it causes 
errors.

On Sunday, 2 August 2020 at 09:05:32 UTC+7 Chotechai Piyavongsiri wrote:

> It still produces the same errors.
>
> When I look at mqtt data, it gives two different data formats at different 
> frequency. The shorter format is for wind data which refreshes more 
> frequently; while the other format is a more complete data including temp, 
> humidity, uv...which comes every minute. The weewx database contains same 
> consistent data in data fields on all records. I'm not sure the errors are 
> due to the two different formats mqtt spits out?
>

-- 
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/9614de35-c4f5-466a-9cb5-a6eb2495a151n%40googlegroups.com.

[weewx-user] Re: weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

It still produces the same errors.

When I look at mqtt data, it gives two different data formats at different 
frequency. The shorter format is for wind data which refreshes more frequently; 
while the other format is a more complete data including temp, humidity, 
uv...which comes every minute. The weewx database contains same consistent data 
in data fields on all records. I'm not sure the errors are due to the two 
different formats mqtt spits out?

-- 
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/5e510661-5274-4123-be43-5ee20db7d92eo%40googlegroups.com.

[weewx-user] Re: weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

Thanks Vince. I took that line out, it did not help.

On Saturday, 1 August 2020 at 22:13:38 UTC+7 vince wrote:

> On Saturday, August 1, 2020 at 1:24:35 AM UTC-7, gjr80 wrote:
>>
>> The error in your original post relates to an error parsing a config 
>> file. There are only two config files involved; weewx.conf and the 
>> Belchertown skin.conf. As per my previous post I suggest you look in the 
>> Belchertown skin.conf file.
>>
>>
>>
> Look at the line saying:
> powered_by: "Observations are powered by a  https://bthofen.com/aqi;>Misol WS-1400-IP
>
> Your quotes are incorrect. 
>

-- 
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/39c96cd0-579e-43d6-9c20-4189c70688f5n%40googlegroups.com.

[weewx-user] Re: weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

I really can't find what causes the error. To sum up my running platform:
Ubuntu 20.04, python3.8.2, Weewx 4.1.1 (using installation guide for 
debian), latest Weatherflow UDP driver, latest Weewx mqtt extension, 
Weatherflow Tempest.

Belows are the configuration parts relating to my the above, in weewx.conf. 
As mentioned earlier, the standard Season webpage was generated fine; but 
it dies during working on the Belchertown skin. Anyone who has very similar 
setup and found no problem, please let me know...thanks.
It generated only these files, see attached photo, in the Belchertown 
output folder:



[[MQTT]]
server_url = mqtt://bthoven:mosquitto1234@localhost:1883/
#server_url = mqtt://bthoven:mosquitto1234@192.168.2.14:1883/
topic = weewx
unit_system = METRIC
binding = archive, loop
#binding = archive
aggregation = aggregate



[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
[[[Extras]]]
#belchertown_root_url = https://bthofen.com/weewx
belchertown_root_url = http://192.168.2.91/weewx/belchertown
home_page_header = Europa Cafe Weather Conditions
logo_image = https://bthofen.com/europacafe_logo.png
site_title = Europa Cafe Observatory
manifest_name = bthoven weather station
footer_copyright_text = BelchertownWeather.com
# station_observations = barometer, dewpoint, outHumidity, 
inTemp, inHumidity, radiation, UV, cloudbase, rainWithRainRate
station_observations = barometer, dewpoint, outHumidity, 
radiation, UV, cloudbase, rainWithRainRate, windBatteryStatus
forecast_enabled = 1
darksky_secret_key = f6176977330eacf99c08705ec9c87e0c
forecast_alert_enabled = 1
earthquake_enabled = 1
twitter_enabled = 1
twitter_owner = chotechai
facebook_enabled = 1
mqtt_websockets_enabled = 1
reload_hook_images = 1
reload_images_hook_as = 300
reload_images_hook_ac = 900
theme = auto
darksky_units = ca
webpage_autorefresh = 0
powered_by: "Observations are powered by a https://bthofen.com/aqi;>Misol WS-1400-IP
mqtt_websockets_host = 192.168.2.91
mqtt_websockets_port = 8083
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weewx/loop
disconnect_live_website_visitor = 0
show_cloudbase = 1
show_apptemp = 1
belchertown_debug = 1

 [WeatherFlowUDP]
driver = user.weatherflowudp
log_raw_packets = False
udp_address = 
# udp_address = 0.0.0.0
# udp_address = 255.255.255.255
udp_port = 50222
udp_timeout = 90
share_socket = True

[[sensor_map]]
outTemp = air_temperature.ST-2496.obs_st
outHumidity = relative_humidity.ST-2496.obs_st
pressure = station_pressure.ST-2496.obs_st
#lightning_strikes =  lightning_strike_count.ST-2496.obs_st
#avg_distance =  lightning_strike_avg_distance.ST-2496.obs_st
outTempBatteryStatus = battery.ST-2496.obs_st
windSpeed = wind_speed.ST-2496.rapid_wind
windDir = wind_direction.ST-2496.rapid_wind
#luxXXX = illuminance.ST-2496.obs_st
UV = uv.ST-2496.obs_st
rain = rain_accumulated.ST-2496.obs_st
windBatteryStatus = battery.ST-2496.obs_st
radiation = solar_radiation.ST-2496.obs_st
#lightningXXX = distance.ST-2496.evt_strike
#lightningYYY = energy.ST-2496.evt_strike


On Wednesday, 29 July 2020 at 11:15:41 UTC+7 gjr80 wrote:

> I would say that line 71 in the Belchertown skin.conf might be a good 
> place to start.
>
> Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:  
> Parsing failed with several errors.#012First error at line 71.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5925219f-d2ec-4bbe-907c-6f9f744d4aebn%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT live stats problem

[Chotechai Piyavongsiri]

So it could be something changed on the public mqtt end.

On Wednesday, 29 July 2020 at 11:18:21 UTC+7 Chotechai Piyavongsiri wrote:

> Running fine with local mqtt broker, with or without encryption.
>
> On Wednesday, 29 July 2020 at 03:10:28 UTC+7 vince wrote:
>
>> On Tuesday, July 28, 2020 at 1:07:05 PM UTC-7, Scott Grayban wrote:
>>>
>>> I opened a issue ticket at 
>>> https://github.com/poblabs/weewx-belchertown/issues/344
>>>
>>>
>> I did a clean install on weewx v4 and belchertown latest, both with 
>> python3.
>> Live stats works just fine for me, without MQTT encryption being enabled.
>>
>>

-- 
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/ab123d4e-3e2c-45f1-9724-397962a5fc62n%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT live stats problem

[Chotechai Piyavongsiri]

Running fine with local mqtt broker, with or without encryption.

On Wednesday, 29 July 2020 at 03:10:28 UTC+7 vince wrote:

> On Tuesday, July 28, 2020 at 1:07:05 PM UTC-7, Scott Grayban wrote:
>>
>> I opened a issue ticket at 
>> https://github.com/poblabs/weewx-belchertown/issues/344
>>
>>
> I did a clean install on weewx v4 and belchertown latest, both with 
> python3.
> Live stats works just fine for me, without MQTT encryption being enabled.
>
>

-- 
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/4ffb64a0-52be-4830-ac0e-d0cbc9f65ce1n%40googlegroups.com.

[weewx-user] weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

I've been running weewx 3.xx and the excellent Belchertown skin on my 
ubuntu 18.04 without any problem. My source sensors is Aercus Weathersleuth 
equivalent (Misol brand) sending data to Ecowitt GW1000.

I've set up another Ubuntu 20.04 server for some other testing and now I 
get the Weatherflow Tempest. I installed weewx latest 4.1.1, python3, 
Belchertown skin, and the latest Weewx UDP driver for Weatherflow. Weewx 
can generate standard reports without any issues; but the Belchertown skin 
generates a lot of errors. The weewx config on the Belchertown part is more 
or less the same (except the website root directory). Data in weewx.sdb 
seems populated fine.

This is the errors generated:

Jul 29 10:50:10 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:07 +07 (1595994607)
Jul 29 10:50:16 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:13 +07 (1595994613)
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:16 +07 (1595994616)
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.manager: Added record 
2020-07-29 10:50:00 +07 (1595994600) to database 'weewx.sdb'
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.manager: Added record 
2020-07-29 10:50:00 +07 (1595994600) to daily summary in 'weewx.sdb'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: 
Running reports for latest time in the database.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: 
Running report 'SeasonsReport'
Jul 29 10:50:19 bthoven-3020M /weewxd: weatherflowudp: MainThread: 
Listening for UDP broadcasts to IP address  on port 50222, with 
timeout 90 and share_socket True...
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.cheetahgenerator: 
Using search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:00 +07 (1595994600)
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.manager: Daily 
summary version is 2.0
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 0.23 seconds
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.manager: Daily 
summary version is 2.0
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 0.17 seconds
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.reportengine: Copied 
0 files to /var/www/html/weewx
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: 
Running report 'Belchertown'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
'Belchertown'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.cheetahgenerator: 
Using search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getData']
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.manager: Daily 
summary version is 2.0
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   Parsing failed with several errors.#012First error at line 71.
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   Traceback (most recent call last):
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   obj.start()
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 280, in start
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   self.run()
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 150, in run
Jul 29 

[weewx-user] Re: crt extension has been updated

[Chotechai Piyavongsiri]

The bigger screenshot is here: Realmore.txt raw data and wind rose 


-- 
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/ea05dd40-851d-4927-9cb5-b3a237b90116%40googlegroups.com.

[weewx-user] Re: EPHEM and Almanac

[Chotechai Piyavongsiri]

I'm using NewWX template for my weewx. It produces similar info from ephem. 
You may download it and have a look at their codes.
https://neoground.com/portfolio/neowx/

my weather page using neowx http://bthoven.dyndns.biz:802/weewx/
you click the "more" button at the top right corner of the page to see the 
almanac.

On Monday, 13 May 2019 07:07:06 UTC+7, Joe Brockway wrote:
>
> Hello,
>
> I have installed EPHEM and would like the Almanac page to display more 
> information about the moon and sun. The issue I am having is I do not know 
> what file to edit or what script I need to add. I would l to emulate this 
> page https://sailing.mit.edu/weather/almanac.html
>
> Thank you in advance for your help.
>
> Joe B 
> http://73.14.239.17:32983/weewx 
> 
>

-- 
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/ab04e264-4d7d-4fb6-ab5c-e2b2f76c8c78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: rtl_sdr/weewx and crt extension - incomplete data in realtime.txt

[Chotechai Piyavongsiri]

Thanks. I got it.

On Sunday, 21 April 2019 17:48:20 UTC+7, mwall wrote:
>
>
>
> On Sunday, April 21, 2019 at 6:24:18 AM UTC-4, Chotechai Piyavongsiri 
> wrote:
>>
>> Wow..great. It works.
>>
>> Could you explain the differences between loop and archive. I wish to 
>> know why archive works.
>>
>
> see the section "loop packets vs archive records" in the weewx 
> customization guide:
>
>
> http://weewx.com/docs/customizing.htm#_LOOP_packets_vs._archive_records_
>
> 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: rtl_sdr/weewx and crt extension - incomplete data in realtime.txt

[Chotechai Piyavongsiri]

Wow..great. It works.

Could you explain the differences between loop and archive. I wish to know 
why archive works.

Thanks a lot.

On Sunday, 21 April 2019 17:11:06 UTC+7, mwall wrote:
>
>
>
> On Sunday, April 21, 2019 at 4:37:42 AM UTC-4, Chotechai Piyavongsiri 
> wrote:
>>
>> *How to make the realtime.txt stores the right vaues in all data fields 
>> every time?*
>>
>
> in your weewx configuration file, set the binding to archive instead of 
> loop.  for example:
>
> [CRT]
> binding = archive
>
> 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.

Re: [weewx-user] Re: Interceptor setup

[Chotechai Piyavongsiri]

 My 'live' weewx server ip is 192.168.2.3 (via wifi), my ObserverIP is 
192.168.2.122 (wired connect to router) and its destination server is 
192.168.2.3 port 55. Interceptor setting in weewx.conf:[Interceptor]
    # This section is for the network traffic interceptor driver.
    
    # The driver to use:
    driver = user.interceptor
    
    # Specify the hardware device to capture.  Options include:
    #   acurite-bridge - acurite internet bridge
    #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
    #   lw30x - oregon scientific LW301/LW302
    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
    device_type = observer
    port = 55
It has been working flawlessly.
My test weewx server ip is 192.168.2.11, wifi to router. I'm not sure with this 
kind of setup, how can I use Interceptor to sniff data from my ObserverIP (or 
from my live weewx server?).
Thanks
On ‎Friday‎, ‎5‎ ‎April‎ ‎2019‎ ‎02‎:‎51‎:‎57‎ ‎AM‎ ‎+07, Scott Grayban 
 wrote:  
 
 Post your settings.

On Thursday, April 4, 2019 at 3:48:06 AM UTC-7, bthoven wrote:
Hi m,That was what I have been trying to do, the sniff, without success. Could 
you suggest how should I set the sniff thing.
Now my ObserverIP has local ip 192.168.2.122. It directs the data to my live 
weewx 192.168.2.3 port 55 which runs Interceptor in listening mode.
Thanks
On Thu, 4 Apr 2019, 16:54 mwall,  wrote:

On Thursday, April 4, 2019 at 1:12:22 AM UTC-4, Chotechai Piyavongsiri wrote:
As I'm setting up and testing another weewx server and would like to receive 
live data from the same IP Observer without changing the destination IP/port, 
do you think your approach would allow two weewx servers to receive same live 
data transmitted from the same IP Observer?






you cannot have two instances of the interceptor in listen mode to the same 
station - the station can only talk to one server, whether it is wu or 
weewx-interceptor
however, you could have one weewx-interceptor instance in listen mode, then a 
second weewx-interceptor in sniff mode
the station communications with the first instance as it would to any server, 
and the second instance eavesdrops on the conversation
m 


-- 
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/bks8RhOINP4/ unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx...@ 
googlegroups.com.
For more options, visit https://groups.google.com/d/ optout.




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

Re: [weewx-user] Re: Interceptor setup

[Chotechai Piyavongsiri]

Hi Scott,

I've been running weewx on ubuntu for a few years using Interceptor 
(listening mode) to receive data direct from my IP Observer (the firmware 
still allows me to specify the destination server IP and Port).

As I'm setting up and testing another weewx server and would like to 
receive live data from the same IP Observer without changing the 
destination IP/port, do you think your approach would allow two weewx 
servers to receive same live data transmitted from the same IP Observer?

Could you also explain me in layman term the concept of your 
'hostpapd-wifi…." approach.

Thank you.

On Friday, 4 January 2019 03:39:06 UTC+7, Scott Grayban wrote:
>
> Created 
> https://github.com/weewx/weewx/wiki/hostapd-WiFi-setup-for-Interceptor-driver
>
> On Thursday, January 3, 2019 at 10:10:53 AM UTC-8, G Hammer wrote:
>>
>> The wiki
>>
>

-- 
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 with Dark Sky API

[Chotechai Piyavongsiri]

mwall...thanks for looking into this.

On Tuesday, 2 April 2019 23:43:02 UTC+7, mwall wrote:
>
> On Tuesday, April 2, 2019 at 12:14:40 PM UTC-4, ABZ wrote:
>>
>> Upgraded to weewx 3.9.1.  NWS & OWM forecasts work, but WU and DS don't 
>> work
>>
>> The log contains this error message:
>>
>> forecast: DSThread: DS: forecast failure: initial_value must be unicode 
>> or None, not str
>>
>> This might account for the lack of DS data; not sure about WU (for which 
>> I just got my new key).
>>
>
> support for new wu forecasts is not yet released.  working on it...
>  
> the fixes for the empty DS data handling are in weewx-forecast-4.0rc1 
> (also not yet released)
>
>

-- 
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: WeeWX CRT Extension - Lancet.mit.edu out of order

[Chotechai Piyavongsiri]

Here it is. Not sure it is the latest version, though it works with latest 
weewx.

On Tuesday, 2 April 2019 14:44:28 UTC+7, bruno...@orange.fr wrote:
>
> Hi everybody,
>
> I am a noob and just started to install weeWX. I am verry happy with this. 
> Thanks to all persons who participate to bring this projet to us and keep 
> it update and alive. 
>
> I would like to install the Weather34 Skin. For this, I need to install 
> the CRT extension to generate the realtime.txt file. Unfortunately, the 
> lancet.mit.edu is no longer awake. The domain is unreachable. I sent an 
> eMail to the Network manager at MIT, founded on whois contacts.
>
> Is there another solution that I can follow to go forward in Weather34 
> skin install ? Is there somone who can provide me the archive file for CRT 
> extension ? Where can I download it ? 
>
> The original link on the weeWX wiki is : 
> http://lancet.mit.edu/mwall/projects/weather/releases/weewx-crt-0.18.tgz
>
> Thanks for your help,
>
> Bruno from France.
>

-- 
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-crt-0.18.tgz
Description: GNU Unix tar archive

[weewx-user] Re: Installing WeatherCloud Extension - Error

[Chotechai Piyavongsiri]

It is v.0.11 (know by peeking inside the tar file)

On Tuesday, 2 April 2019 10:02:35 UTC+7, Chotechai Piyavongsiri wrote:
>
> Here it is. Not sure what version it is.
>
> On Monday, 1 April 2019 16:45:15 UTC+7, Dave McCreath wrote:
>>
>> Has anyone got a copy of the tarball?
>>
>> Just asking, you never know.
>>
>> Dave
>>
>> On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>>>
>>> Thanks for getting back to me.  Looks like the link is down so unable to 
>>> download it!
>>>
>>> Regards
>>>
>>> Dave
>>>
>>> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>>>>
>>>> Hi,
>>>>
>>>> You need to replace x.y in the command you are using to install with 
>>>> the version number in the install file you downloaded. The current version 
>>>> appears to be 0.11 so try:
>>>>
>>>> $ wee_extension --install weewx-wcloud-0.11.tgz
>>>>
>>>> Using x.y or x.y.z is a common shorthand used to indicate you need to 
>>>> replace the letters with the version you are using. Saves a bit of work 
>>>> continually updating (and may be getting them out of date) instructions.
>>>>
>>>> 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] Re: Installing WeatherCloud Extension - Error

[Chotechai Piyavongsiri]

Here it is. Not sure what version it is.

On Monday, 1 April 2019 16:45:15 UTC+7, Dave McCreath wrote:
>
> Has anyone got a copy of the tarball?
>
> Just asking, you never know.
>
> Dave
>
> On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>>
>> Thanks for getting back to me.  Looks like the link is down so unable to 
>> download it!
>>
>> Regards
>>
>> Dave
>>
>> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> You need to replace x.y in the command you are using to install with the 
>>> version number in the install file you downloaded. The current version 
>>> appears to be 0.11 so try:
>>>
>>> $ wee_extension --install weewx-wcloud-0.11.tgz
>>>
>>> Using x.y or x.y.z is a common shorthand used to indicate you need to 
>>> replace the letters with the version you are using. Saves a bit of work 
>>> continually updating (and may be getting them out of date) instructions.
>>>
>>> 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-wcloud-x.y.tgz
Description: GNU Unix tar archive

[weewx-user] Re: Can two weewx servers receive data from one IP Observer?

[Chotechai Piyavongsiri]

Hi Chris,

Interesting; but both servers are using wifi communication.

On Monday, 1 April 2019 20:12:29 UTC+7, tomn...@frontier.com wrote:
>
> There are slightly fancier ethernet switches that can do port mirroring 
> that might do the trick.  I suppose of you had
> an ethernet hub  (not a switch), that would work also.
>
> 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] Can two weewx servers receive data from one IP Observer?

[Chotechai Piyavongsiri]

I'm now running weewx on my Android tv-turned-Ubuntu box and use 
interceptor extension from https://github.com/matthewwall/weewx-interceptor

My IP Observer web ui still allows me to specify my Ubuntu box as the 
destination server.

Now I'm testing weewx on another ubuntu server and want to receive weather 
data from the same IP Observer I have. I do not want to interrupt data 
reception on my 'live' weewx during my testing on another weewx server; but 
I also need the live data for my test weewx.

My question is would it be possible that both weewx servers can receive 
live weather data from the same IP Observer? 

Thanks in advance for any 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: crt extension has been updated

[Chotechai Piyavongsiri]

Mathew, Gary...thanks a lot

-- 
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: crt extension has been updated

[Chotechai Piyavongsiri]

mwall...thanks a lot for this useful extensions. Do you have any idea about 
producing a realmore.txt file mentioned in this forum?
http://sandaysoft.com/forum/viewtopic.php?f=26=16398

On Wednesday, April 13, 2016 at 2:30:17 PM UTC+7, mwall wrote:
>
> the cumulus realtime (crt) extension has been around awhile, but recently 
> received a major update:
>
> https://github.com/weewx/weewx/wiki/crt
>
> this extension should make it trivial to use weewx with any weather 
> template that gets its data from a cumulus 'realtime.txt' file.  that 
> includes meteotemplate, leuven, saratoga, and weatherbyyou.
>
> thanks to gary for extensive testing.
>
> we thought about an extension that would output weather display 
> 'customXXX' files, but pretty much anything that works with wd customXXX 
> works with cumulus realtime.
>
> from the changelog:
>
> 0.18 10apr2016
> * graceful recovery when no forecast binding defined
> * refactor unit conversions to support per-observation unit specifications
> * more fixes from gary for better unit conversions and cumulus compliance
>
> 0.17 28mar2016
> * lots of fixes from gary roderick:
> * Introduced StrictVersion to more easily compare weewx version numbers.
> * crt now requires weewx 3.2.0 or later.
> * Fixed UNITS_RAIN typo, weewx rain unit is 'inch' not 'in'.
> * Added UNITS_ALT to facilitate cloudbase units lookup.
> * Replaced knottoBeaufort() with call to weewx.wxformulas.beaufort().
> * cloudbase, maxSolarRad, humidex, appTemp and heatindex are now included 
> in
>   weewx loop packets so removed manual calculations of these obs.
> * Side benefit of using maxSolarRad from loop packet means crt no longer
>   crashes if pyephem is not installed.
> * Reworked calcDaylightHours() to use Almanac objects
>   rather than Sun object calcs so that additional accuracy of pyephem can 
> be
>   taken advantage of if installed.
> * Weewx is now windrun aware though windrun is not included in loop 
> packets.
> * Reworked windrun unit conversions to make use of weewx API.
> * Sunshine hours calculations remain flawed but it now uses an Almanac
>   object as the basis for its calculation.
> * radiation had no formatting applied resulting in numerous decimal places
>   in realtime.txt, reduced that to 1 decimal place (probably only an issue
>   with simulator).
> * Minor changes to some packet names to reflect new fields now in weewx 
> loop
>   packet eg cloud_base v cloudbase.
> * Found that crt would fail if used with an empty archive (could not get db
>   US units to do conversion so _cvt() method would cause a failure). Was a
>   vicious circle; if used with an empty archive crt would cause weewx to 
> fail
>   and because weewx failed you could never get any records into the 
> archive.
>   The only work around was to not install/run crt on an empty archive. I
>   reworked the _cvt() method to return None is the archive has no records,
>   gives a lot of NULLs in the output until you get records in the archive 
> then
>   it operates as normal.
> * Did some further comparison of Cumulus realtime.txt wiki page and Cumulus
>   Webtags wiki page. By cross referencing the Webtags between the wiki 
> pages
>   it was possible to confirm details of a number of realtime.txt fields:
>- field 6 (wind avg speed)and field 47 (wind avg dir). Averaging period 
> is
>  not mentioned directly although the corresponding Webtags use 10 
> minute
>  averages by default. This confirms current crt settings.
>- field 52 (avg_wind_dir). This is the compass direction of the 10 min
>  average wind bearing, changed code to reflect this.
>- Cumulus uses wind direction of 0+ to 360 with 0 indicating calm.
> * Reworked calcAvgWindDir() and calc10MinAvgWindDir() to return None or
>   0+ to 360 rather than None or 0 to 360-.
> * Given the way Cumulus represents wind direction introduced
>   data['cumulus_windDir'] mainly to differentiate from/not overwrite
>   data['windDir']
> * Confirmed that month and year rain are month to date and year to date
>   values from 1st of month and year respectively. Removed 2 related FIXME
>   comments.
> * field 11 is listed as in the realtime.txt wiki page as 'barometer (The
>   sea level pressure)' with the equivalent webtag of #press. #press is 
> listed
>   in the webtags wiki page as 'The sea level pressure'. These are 
> completely
>   consistent with using weewx 'barometer'. Removed the comment re 
> uncertainty
>   over what pressure is specified in realtime.txt.
> * Observed a number of real world live realtime.txt files and confirmed 
> that:
>- realtime.txt uses local time. Reworked date/time to use local time
>  throughout.
>- None/NULL handling is not specified in Cumulus realtime.txt wiki but
>  observation of a number of realtime sites showed that when there is no
>  wind, wind speeds are set to 0 not NULL. Introduced 'none' setting in
>  weewx.conf[CumulusRealTime] to allow user specification of what
>