Re: [weewx-user] PM2_5 no such column errors on weather34

[Chris Alemany]

Hi J D,

Your comment made me try completely removing line 280:

$pm25 = “$span($hour ……

from archviedata.php.tmpl. Previously I had just commented it out.

The archivedata file generates now! Perhaps the other errors are erroneous or, 
because none of those other values are present in the template file, they are 
not preventing the file from generating.

Thank you for the suggestion of deleting the line, at least now there is data 
in the display!  I’ll await Ian’s advice on getting purple air values working.

Cheers
Chris

> On Apr 26, 2020, at 10:41 PM, J D  wrote:
> 
> Hi,
> Ian is the owner of this so I just emailed him. When he gets online later he 
> will help with this.
> I am curious where you got the archivedata.php.tmpl file since the one I am 
> using does not have these fields.?
> You can always make a copy of the file and delete the missing fields from the 
> tmpl file since they really should not be there.
> 
> On Sunday, April 26, 2020 at 9:43:14 PM UTC-7, Chris Alemany wrote:
> Hi all,
> 
> I just updated to a new version of the weather34 skin and am having a problem 
> with the database schema.  I have a purple air station and it is hooked in 
> with the purpleair extension which displays fine in the regular skin here:
> https://www.alberniweather.ca/index.html 
> 
> 
> However weather34 is complaining of a missing column which is preventing the 
> archivedata.php file from being generated.
> 
> default   21:35:26.641849-0700Python  manager: Added record 
> 2020-04-26 21:35:00 PDT (1587962100) to daily summary in 'weewx.sdb'
> error 21:35:32.756817-0700Python  no such column: pm2_5 in "SELECT 
> avg(pm2_5) FROM archive WHERE dateTime > 1587875700 AND dateTime <= 
> 1587962100 AND pm2_5 IS NOT NULL"
> default   21:35:32.756968-0700Python  cheetahgenerator: Generate 
> failed with exception ''
> default   21:35:32.757054-0700Python  cheetahgenerator:  Ignoring 
> template /Users/Shared/weewx/skins/Weather34/archivedata.php.tmpl
> default   21:35:32.757129-0700Python  cheetahgenerator:  Reason: 
> no such column: pm2_5
> error 21:35:32.860069-0700Python  no such column: uva in "SELECT 
> dateTime, uva, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860202-0700Python  no such column: uvb in "SELECT 
> dateTime, uvb, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860348-0700Python  no such column: uvaWm in "SELECT 
> dateTime, uvaWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860419-0700Python  no such column: uvbWm in "SELECT 
> dateTime, uvbWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860481-0700Python  no such column: full_spectrum in 
> "SELECT dateTime, full_spectrum, usUnits, `interval` FROM archive WHERE 
> dateTime >= ? AND dateTime <= ?"
> error 21:35:32.860543-0700Python  no such column: lux in "SELECT 
> dateTime, lux, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860624-0700Python  no such column: infrared in "SELECT 
> dateTime, infrared, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860687-0700Python  no such column: pm2_5 in "SELECT 
> dateTime, pm2_5, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860830-0700Python  no such column: pm10_0 in "SELECT 
> dateTime, pm10_0, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> 
> I've tried temperarily removing mention of pm2.5 from the skin file but it 
> isn't helping.
> 
> Any suggestions greatly appreciated!
> Cheers
> Chris
> 
> -- 
> 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/uVzE9-Ok2eo/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/a6ae8964-054f-48c8-b9fb-bcebc487cf0c%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/78563004-93B2-4BD6-AA88-8E8A9B3489FE%40gmail.com.

[weewx-user] Re: PM2_5 no such column errors on weather34

[J D]

Hi,
Ian is the owner of this so I just emailed him. When he gets online later 
he will help with this.
I am curious where you got the archivedata.php.tmpl file since the one I am 
using does not have these fields.?
You can always make a copy of the file and delete the missing fields from 
the tmpl file since they really should not be there.

On Sunday, April 26, 2020 at 9:43:14 PM UTC-7, Chris Alemany wrote:
>
> Hi all,
>
> I just updated to a new version of the weather34 skin and am having a 
> problem with the database schema.  I have a purple air station and it is 
> hooked in with the purpleair extension which displays fine in the regular 
> skin here:
> https://www.alberniweather.ca/index.html
>
> However weather34 is complaining of a missing column which is preventing 
> the archivedata.php file from being generated.
>
> default   21:35:26.641849-0700Python  manager: Added record 
> 2020-04-26 21:35:00 PDT (1587962100) to daily summary in 'weewx.sdb'
> error 21:35:32.756817-0700 Python no such column: pm2_5 in "SELECT 
> avg(pm2_5) FROM archive WHERE dateTime > 1587875700 AND dateTime <= 
> 1587962100 AND pm2_5 IS NOT NULL"
> default 21:35:32.756968-0700 Python cheetahgenerator: Generate failed 
> with exception ''
> default 21:35:32.757054-0700 Python cheetahgenerator:  Ignoring 
> template /Users/Shared/weewx/skins/Weather34/archivedata.php.tmpl
> default 21:35:32.757129-0700 Python cheetahgenerator:  Reason: no 
> such column: pm2_5
> error 21:35:32.860069-0700 Python no such column: uva in "SELECT 
> dateTime, uva, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860202-0700 Python no such column: uvb in "SELECT 
> dateTime, uvb, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860348-0700 Python no such column: uvaWm in "SELECT 
> dateTime, uvaWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860419-0700 Python no such column: uvbWm in "SELECT 
> dateTime, uvbWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860481-0700 Python no such column: full_spectrum in 
> "SELECT dateTime, full_spectrum, usUnits, `interval` FROM archive WHERE 
> dateTime >= ? AND dateTime <= ?"
> error 21:35:32.860543-0700 Python no such column: lux in "SELECT 
> dateTime, lux, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860624-0700 Python no such column: infrared in "SELECT 
> dateTime, infrared, usUnits, `interval` FROM archive WHERE dateTime >= ? 
> AND dateTime <= ?"
> error 21:35:32.860687-0700 Python no such column: pm2_5 in "SELECT 
> dateTime, pm2_5, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860830-0700 Python no such column: pm10_0 in "SELECT 
> dateTime, pm10_0, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
>
> I've tried temperarily removing mention of pm2.5 from the skin file but it 
> isn't helping.
>
> Any suggestions greatly appreciated!
> Cheers
> Chris
>

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

[weewx-user] PM2_5 no such column errors on weather34

[Chris Alemany]

Hi all,

I just updated to a new version of the weather34 skin and am having a 
problem with the database schema.  I have a purple air station and it is 
hooked in with the purpleair extension which displays fine in the regular 
skin here:
https://www.alberniweather.ca/index.html

However weather34 is complaining of a missing column which is preventing 
the archivedata.php file from being generated.

default   21:35:26.641849-0700Python  manager: Added record 
2020-04-26 21:35:00 PDT (1587962100) to daily summary in 'weewx.sdb'
error 21:35:32.756817-0700 Python no such column: pm2_5 in "SELECT 
avg(pm2_5) FROM archive WHERE dateTime > 1587875700 AND dateTime <= 
1587962100 AND pm2_5 IS NOT NULL"
default 21:35:32.756968-0700 Python cheetahgenerator: Generate failed with 
exception ''
default 21:35:32.757054-0700 Python cheetahgenerator:  Ignoring 
template /Users/Shared/weewx/skins/Weather34/archivedata.php.tmpl
default 21:35:32.757129-0700 Python cheetahgenerator:  Reason: no such 
column: pm2_5
error 21:35:32.860069-0700 Python no such column: uva in "SELECT dateTime, 
uva, usUnits, `interval` FROM archive WHERE dateTime >= ? AND dateTime <= ?"
error 21:35:32.860202-0700 Python no such column: uvb in "SELECT dateTime, 
uvb, usUnits, `interval` FROM archive WHERE dateTime >= ? AND dateTime <= ?"
error 21:35:32.860348-0700 Python no such column: uvaWm in "SELECT 
dateTime, uvaWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
dateTime <= ?"
error 21:35:32.860419-0700 Python no such column: uvbWm in "SELECT 
dateTime, uvbWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
dateTime <= ?"
error 21:35:32.860481-0700 Python no such column: full_spectrum in "SELECT 
dateTime, full_spectrum, usUnits, `interval` FROM archive WHERE dateTime >= 
? AND dateTime <= ?"
error 21:35:32.860543-0700 Python no such column: lux in "SELECT dateTime, 
lux, usUnits, `interval` FROM archive WHERE dateTime >= ? AND dateTime <= ?"
error 21:35:32.860624-0700 Python no such column: infrared in "SELECT 
dateTime, infrared, usUnits, `interval` FROM archive WHERE dateTime >= ? 
AND dateTime <= ?"
error 21:35:32.860687-0700 Python no such column: pm2_5 in "SELECT 
dateTime, pm2_5, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
dateTime <= ?"
error 21:35:32.860830-0700 Python no such column: pm10_0 in "SELECT 
dateTime, pm10_0, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
dateTime <= ?"

I've tried temperarily removing mention of pm2.5 from the skin file but it 
isn't helping.

Any suggestions greatly appreciated!
Cheers
Chris

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3af8e4f6-d85b-4478-9a66-7558dca42578%40googlegroups.com.

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Xant]

On Sunday, April 26, 2020 at 11:25:56 AM UTC-4, Pat wrote:
>
> I've incorporated Aeris Weather into the Belchertown 1.2b2 beta skin. 
> Details can be found here for anyone who wants to try it out: 
> https://github.com/poblabs/weewx-belchertown/tree/development
>>
>>
>
Interesting (will check) so, it's Aeris now your top option for DS 
replacement? 

-- 
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/29a6fc16-f3e0-4279-8fa4-d858d1ddc4fb%40googlegroups.com.

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Xant]

Not just a matter of wording. Pat, as a Developer, have to consider 
new-users when starting using Belchertown. So API and Service has always to 
be current, and open to new sign-ins.


On Sunday, April 26, 2020 at 2:54:51 PM UTC-4, Xant wrote:
>
> Anton 
>
> "end of 2021 seems ample time"
>
> Not really (as pointed by someone before), "end of 2021" refers to owners 
> of existing APIs, but widget service soon to be cancelled and DarkSky 
> closed to new APIs.
>
> So the search and research for a replacement is On...
>
>

-- 
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/b091835f-3f04-4a62-aa36-660fb0e4b446%40googlegroups.com.

Re: [weewx-user] Aeris forecast not displaying.

[John Kline]

Hi David,

I tried this in my weewx.conf file.  You’ll need to remove the space in the 
location (after the comma) to get this to run.

>> location = "Poway,CA"


I’ll add code to encode the space on my fork (if that solves the issue), but 
you should be in business 3.9.2 by simply removing the space.

> On Apr 26, 2020, at 10:50 AM, John Kline  wrote:
> 
> 
> If you got that failure with weewx using the same forecast.py you used 
> successfully from the command line, that is indeed strange.  Are you really 
> sure you used the same client-id and secret-key in weewx.conf that you used 
> from the command line?
> 
> The other option is that the service was temporarily down.  That’s what a 503 
> is.  It could actually start working for you.
> 
> And of assumes that you are trying this from the same machine where you ran 
> the forecast from the command line.  Also assuming you don’t have 
> intermittent network connectivity problems.
> 
>>> On Apr 26, 2020, at 10:26 AM, David Barto  wrote:
>>> 
>> 
>> Well dang, set it as noted, getting the same failure.
>> 
>> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
>> WUThread: WU: failed attempt 1 to download forecast: HTTP Error 503: Service 
>> Unavailable
>> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
>> AerisThread: Aeris: failed attempt 2 to download forecast: HTTP Error 400: 
>> Bad Request
>> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
>> AerisThread: Aeris: failed attempt 3 to download forecast: HTTP Error 400: 
>> Bad Request
>> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
>> AerisThread: Aeris: failed to download forecast
>> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
>> AerisThread: Aeris: no forecast data for Poway, CA from 
>> http://api.aerisapi.com/forecasts/
>> 
>> I’ll just wait until 4.0 and see if that changes anything.
>> 
>>  David
>> 
>>> On Apr 26, 2020, at 9:50 AM, John Kline  wrote:
>>> 
>>> Add location to the Aeris entry in weewx.conf.
>>> 
>>> [[Aeris]]
>>> client_id = XXX
>>> client_secret = XXX
>>> location = "Poway, CA"
>>> 
> On Apr 26, 2020, at 9:09 AM, David Barto  wrote:
> 
 Brilliant. Now I get the forecast if I set the location to “Poway, CA.” 
 and that works for me.
 Where in the configuration for Aeris would I change the location for 
 getting their forecast for my city?
 
David
 
> On Apr 25, 2020, at 5:20 PM, John Kline  wrote:
> 
> Yikes.  Forgot the diff.  The line numbers won’t match, but this should 
> be easy to apply to your current forecast.py.
> 
> diff --git a/bin/user/forecast.py b/bin/user/forecast.py
> index d947fb3..2254fed 100644
> --- a/bin/user/forecast.py
> +++ b/bin/user/forecast.py
> @@ -5033,9 +5033,9 @@ if __name__ == "__main__":
>help="specify the location")
>  parser.add_option("--api-key", dest="api_key", type=str, 
> metavar="KEY",
>help="specify the api key")
> -parser.add_option("--client-id", dest="client-id", type=str,
> +parser.add_option("--client-id", dest="client_id", type=str,
>metavar="ID", help="specify the client id")
> -parser.add_option("--client-secret", dest="client-secret", 
> type=str,
> +parser.add_option("--client-secret", dest="client_secret", 
> type=str,
>metavar="SECRET", help="specify the client 
> secret")
>  parser.add_option("--filename", dest="filename", 
> metavar="FILENAME",
>help="file that contains forecast data",
> @@ -5078,6 +5078,9 @@ if __name__ == "__main__":
>  fcast = AerisForecast.download(
>  options.client_id, options.client_secret, 
> options.loc)
>  print(fcast)
> +elif options.method.lower() == 'aeris':
> +fcast = AerisForecast.download(options.client_id, 
> options.client_secret, options.loc)
> +print(fcast)
>  elif options.method.lower() == 'wwo':
>  fcast = WWOForecast.download(options.api_key, 
> options.loc)
>  print(fcast)
> 
>>> On Apr 25, 2020, at 4:59 PM, John Kline  wrote:
>>> 
>> 
>> Here’s a diff showing the changes I had to make so that the command 
>> below will run.
>> 
>> Please make those changes and then run the command again pointing to 
>> your changed file.  You don’t even have to update the forecast.py that 
>> weewx is using.  This is just so that you don’t get the method not 
>> supported error below when running directly.
>> 
>> Of course, you also need to plug in your client-I’d and secret-key.

Re: [weewx-user] Re: How to Sniff Packets Going to a Single Host?

[Greg Troxel]

ch...@chrismaness.com writes:

> All these packets are no shows, but if it works on the first go it does
> show up.  I had 6 go through in a row, and now these fails.  I wonder if
> the PI itself has issues with overheating or something.  When I use it
> as a hotspot, it seems fine at first, but then gets crappy and slow
> connections.  However, there seems to be an issue with WeeWx or CWOP
> re-negotiating connections if the first attempt fails.

I would suggest using tcpdump with the -w option to save a trace, and
then go back over the data to analyze the messages, particularly the
ones that didn't make it.  Just run tcpdump with -w, no filters,
because half the point is to see the packets you don't know you are
looking for.

-- 
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/rmizhaxvln2.fsf%40s1.lexort.com.

Re: [weewx-user] Re: How to Sniff Packets Going to a Single Host?

[chris]

On 4/26/20 4:25 PM, Tom Keffer wrote:
> Looks normal to me.
>
> Chris: the CWOP code has been working for over 10 years on thousands
of stations worldwide. It's possible there is an issue with it, but very
unlikely.
>
> Far more likely is that you have a network configuration issue. Does
your router allow port 14580 to pass?

Yes, I tested it with the telnet command.  It connected to 14580 just
fine.  This Raspberry PI tends to have weird connectivity issues if I
use it like a hotspot.  I see my packet does not show up if there are
any timeout warnings.  The odd thing is it seems to make it on the
retry, but if my there was a retry the packet never shows up on APRS.fi
or findu.  Here is some log data:

chris@raspberrypi:~ $ sudo tail -f /var/log/syslog | grep CWOP
Apr 26 16:25:23 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 16:25:00 PDT (1587943500)
Apr 26 16:30:19 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262330z3401.26N/11718.84W_287/007g021t094r000p000P000b10139h24L455.weewx-3.9.2-Interceptor#015
Apr 26 16:30:39 raspberrypi weewx[12666]: restx: CWOP: Attempt 1 to
cwop.aprs.net:23. Connection error: timed out
Apr 26 16:30:39 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 16:31:00 raspberrypi weewx[12666]: restx: CWOP: Exception  (timed out) when looking for response to packet packet
Apr 26 16:31:00 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 16:30:00 PDT (1587943800)
Apr 26 16:35:25 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 16:35:00 PDT (1587944100)
Apr 26 16:40:31 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262340z3401.26N/11718.84W_265/008g019t094r000p000P000b10140h23L404.weewx-3.9.2-Interceptor#015
Apr 26 16:40:31 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 16:40:51 raspberrypi weewx[12666]: restx: CWOP: Exception  (timed out) when looking for response to packet packet
Apr 26 16:40:51 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 16:40:00 PDT (1587944400)

All these packets are no shows, but if it works on the first go it does
show up.  I had 6 go through in a row, and now these fails.  I wonder if
the PI itself has issues with overheating or something.  When I use it
as a hotspot, it seems fine at first, but then gets crappy and slow
connections.  However, there seems to be an issue with WeeWx or CWOP
re-negotiating connections if the first attempt fails.


Thanks,

Chris KQ6UP

-- 
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/73facf53-8c9c-35e7-a72a-f72c4c74c7fc%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Re: How to Sniff Packets Going to a Single Host?

[Tom Keffer]

Looks normal to me.

Chris: the CWOP code has been working for over 10 years on thousands of
stations worldwide. It's possible there is an issue with it, but very
unlikely.

Far more likely is that you have a network configuration issue. Does your
router allow port 14580 to pass?

On Sun, Apr 26, 2020 at 4:13 PM Chris Maness 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
>
> Hash: SHA256
>
>
> Poop, 16:00 did not post.  Here is the packet.  Any issues with it?
>
>
> Apr 26 16:00:16 raspberrypi weewx[12666]: restx: CWOP: packet:
> KQ6UP>APRS,TCPIP*:@262300z3401.26N/11718.84W_313/007g015t096r000p000P000b10143h24L488.weewx-3.9.2-Interceptor#015
>
>
> Chris KQ6UP
>
> -BEGIN PGP SIGNATURE-
>
>
> iQJKBAEBCAA0FiEEHDQAmr+JUZpC9koAp9HNPRAPZfoFAl6mFQYWHGNocmlzQGNo
>
> cmlzbWFuZXNzLmNvbQAKCRCn0c09EA9l+sjXD/9rYRrIG6HO0oD4ipP52SwFDAAb
>
> 4r96rjvEhovnLlDaW9xikg1Uz8aeQniWVehxIMi2a+URX3zc3bKXDndPrMv7iwmN
>
> nrL4JVvPFcbTRafvEOx/aYQ0kDvLmd1C4Yg/tnxAoZi3ZYOI9kilwzFf1ogLc2nW
>
> cvvm8IHtrcsTCjfdwaBG2SUxb004FOye5zh9tOA0MykDDuxrpHeFdza2DOAjoDOI
>
> 5cXpwlQFSrfMveNWNYpD2E9F+gbFOREvtPfacqlyJaF2joDjq/ezf+RJ5qpMG5LU
>
> wbmSxziSZvtPWd7yy3/XXBUQtQB+sxG58oTWSH2lfUUzOZWqwXexRSlwyC5MyXg0
>
> qRkXf+b7MouiugoVT0cXHqn6lK0e2PwcQl1sT1SlcgVhAOOm0YdKoGVShOMwLidV
>
> oSo80tW+Lxs2S6e3FgIPis93nIRfwH/UIYMWN6NNPJUf5KJ+jeRZDjSUxHYZ+Mnb
>
> SFtLn5uVEw6AAFaCJF7w/mjnzeYIsrN4sXAWAKi1ZcLCp8r9qvQa8mxAx8k5L5aQ
>
> 1gSJXskWJoxQKFAP9vMrFSHwN/BBcJcQFLaQSogqz8sMLXKxD08JG8vYNmBS0U1a
>
> Ma3nPAncPzhkV7/pWRWbCTgsKeJpjYFiMfCUd8v4+4upLqVLA1ZQpJEZ2WmpEvCl
>
> h5siLMcS6MtZ3gCgBQ==
>
> =tsi3
>
> -END PGP SIGNATURE-
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/5b72fe57-ec36-4d79-9878-8bc43546e693%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECDLCrwDfMZQzQo-cz4Lj3UqNKCUm%3DtXS3%2B-K1j1iRwNQ%40mail.gmail.com.

Re: [weewx-user] Re: How to Sniff Packets Going to a Single Host?

[chris]

On 4/26/20 4:13 PM, Chris Maness wrote:
>
> Hash: SHA256
>
>
> Poop, 16:00 did not post.  Here is the packet.  Any issues with it?
>
>
> Apr 26 16:00:16 raspberrypi weewx[12666]: restx: CWOP: packet:
> KQ6UP>APRS,TCPIP*:@262300z3401.26N/11718.84W_313/007g015t096r000p000P000b10143h24L488.weewx-3.9.2-Interceptor#015
>
>
> Chris KQ6UP
>
I should say they posted, but did not show up on the APRS network (findu
or APRS.fi).

Chris KQ6UP

-- 
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/daea4388-074a-1537-b3e3-d966d2eec111%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Re: How to Sniff Packets Going to a Single Host?

[Chris Maness]

-BEGIN PGP SIGNED MESSAGE-

Hash: SHA256


Poop, 16:00 did not post.  Here is the packet.  Any issues with it?


Apr 26 16:00:16 raspberrypi weewx[12666]: restx: CWOP: packet: 
KQ6UP>APRS,TCPIP*:@262300z3401.26N/11718.84W_313/007g015t096r000p000P000b10143h24L488.weewx-3.9.2-Interceptor#015


Chris KQ6UP

-BEGIN PGP SIGNATURE-


iQJKBAEBCAA0FiEEHDQAmr+JUZpC9koAp9HNPRAPZfoFAl6mFQYWHGNocmlzQGNo

cmlzbWFuZXNzLmNvbQAKCRCn0c09EA9l+sjXD/9rYRrIG6HO0oD4ipP52SwFDAAb

4r96rjvEhovnLlDaW9xikg1Uz8aeQniWVehxIMi2a+URX3zc3bKXDndPrMv7iwmN

nrL4JVvPFcbTRafvEOx/aYQ0kDvLmd1C4Yg/tnxAoZi3ZYOI9kilwzFf1ogLc2nW

cvvm8IHtrcsTCjfdwaBG2SUxb004FOye5zh9tOA0MykDDuxrpHeFdza2DOAjoDOI

5cXpwlQFSrfMveNWNYpD2E9F+gbFOREvtPfacqlyJaF2joDjq/ezf+RJ5qpMG5LU

wbmSxziSZvtPWd7yy3/XXBUQtQB+sxG58oTWSH2lfUUzOZWqwXexRSlwyC5MyXg0

qRkXf+b7MouiugoVT0cXHqn6lK0e2PwcQl1sT1SlcgVhAOOm0YdKoGVShOMwLidV

oSo80tW+Lxs2S6e3FgIPis93nIRfwH/UIYMWN6NNPJUf5KJ+jeRZDjSUxHYZ+Mnb

SFtLn5uVEw6AAFaCJF7w/mjnzeYIsrN4sXAWAKi1ZcLCp8r9qvQa8mxAx8k5L5aQ

1gSJXskWJoxQKFAP9vMrFSHwN/BBcJcQFLaQSogqz8sMLXKxD08JG8vYNmBS0U1a

Ma3nPAncPzhkV7/pWRWbCTgsKeJpjYFiMfCUd8v4+4upLqVLA1ZQpJEZ2WmpEvCl

h5siLMcS6MtZ3gCgBQ==

=tsi3

-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5b72fe57-ec36-4d79-9878-8bc43546e693%40googlegroups.com.

Re: [weewx-user] Re: How to Sniff Packets Going to a Single Host?

[chris]

On 4/26/20 3:45 PM, gjr80 wrote:
> You already have it in your log:
>
> |
> Apr2614:10:27raspberrypi
> weewx[12666]:restx:CWOP:packet:KQ6UP>APRS,TCPIP*:@262110z3401.26N/11718.84W_241/007g017t098r000p000P000b10150h22L774.weewx-3.9.2-Interceptor#015
>
> Apr2614:10:28raspberrypi weewx[12666]:restx:CWOP:Connectedto server
> cwop.aprs.net:23 
> |
>
> 
> Gary 

Could you look over those and see if they are malformed?  Not sure why
the always seemed to get accepted, but don't wind up on Findu-> KQ6UP. 
I have several successfully posted for the past hour using the single
server cwop.aprs.net:23.  Let's cross our fingers and hope it keeps it
up.  However, it is not very satisfying to never figure out what was
actually messing up.

Thanks,

Chris KQ6UP

-- 
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/d4dbf243-c9ec-2f01-9c78-eced73fa2689%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

[weewx-user] Re: How to Sniff Packets Going to a Single Host?

[gjr80]

You already have it in your log:

Apr 26 14:10:27 raspberrypi weewx[12666]: restx: CWOP: packet: KQ6UP>APRS,
TCPIP*:@262110z3401.26N/11718.84W_241/
007g017t098r000p000P000b10150h22L774.weewx-3.9.2-Interceptor#015 
Apr 26 14:10:28 raspberrypi weewx[12666]: restx: CWOP: Connected to server 
cwop.aprs.net:23


Gary


On Monday, 27 April 2020 08:33:36 UTC+10, ch...@chrismaness.com wrote:
>
> Ok, in my effort to trouble shoot the hit/miss issue of my server.  I am 
>
> now suspecting that the packets that it passes are sometimes malformed.  
> Unless other people have issues with their packets not showing up.  I 
> would like to record whole packets going to cwop.aprs.net:23 and only 
> those packets.  What command can I use to capture the all of the packets 
> with all of their payloads? 
>
>
> Thanks, 
>
> Chris KQ6UP 
>

-- 
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/4f66cde5-44cf-4b63-9ba2-337352a7a6e2%40googlegroups.com.

[weewx-user] How to Sniff Packets Going to a Single Host?

[chris]

Ok, in my effort to trouble shoot the hit/miss issue of my server.  I am

now suspecting that the packets that it passes are sometimes malformed. 
Unless other people have issues with their packets not showing up.  I
would like to record whole packets going to cwop.aprs.net:23 and only
those packets.  What command can I use to capture the all of the packets
with all of their payloads?


Thanks,

Chris KQ6UP

-- 
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/9aead735-5101-fb03-fc68-3099010e1803%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[weather list]

That did it, thanks Gary. I had missed that step.

> On 26Apr, 2020, at 17:14, gjr80  wrote:
> 
> Have you created and logged into your AerisWeather account before submitting 
> details via that link? I had a similar problem until I read the following 
> line near the top of the page:
> 
> Log in to your AerisWeather account and return to this page to continue the 
> signup process.
> 
> I created an AerisWeather account taking up their free trial. I then went to 
> the pws contributor link that has been posted and it worked fine. When I 
> checked my AerisWeather account I now see a pws contributor service (not sure 
> exactly what it was called, don’t have login details to hand) has been added 
> to my AerisWeather account. Mind you I am yet to use the AerisWeather account 
> to access the API.
> 
> 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/f527c526-b587-4178-b049-0ffbcc17df50%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/FA20644A-FC9E-4FAA-8B0C-C003004C1AC8%40gmail.com.

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

grepped all the whole syslog for relevant lines.  It looks like the
packets are getting posted, but not consistently showing up on the
network.  That is really weird.  Here they are:

Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Failed to publish
record 2020-04-26 12:45:00 PDT (1587930300): Tried 13 servers 3 times each
Apr 26 12:50:16 raspberrypi weewx[11493]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 12:50:00 PDT (1587930600)
Apr 26 12:54:54 raspberrypi weewx[11493]: restx: Shut down CWOP thread.
Apr 26 12:55:00 raspberrypi weewx[11862]: engine: Loading service
weewx.restx.StdCWOP
Apr 26 12:55:00 raspberrypi weewx[11862]: restx: CWOP: Data for station
KQ6UP will be posted
Apr 26 12:55:00 raspberrypi weewx[11862]: engine: Finished loading
service weewx.restx.StdCWOP
Apr 26 13:00:28 raspberrypi weewx[11862]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262000z3401.26N/11718.84W_002/002g010t095r000p000P000b10154h22L861.weewx-3.9.2-Interceptor#015
Apr 26 13:00:29 raspberrypi weewx[11862]: restx: CWOP: Connected to
server cwop.aprs.net:14580
Apr 26 13:00:49 raspberrypi weewx[11862]: restx: CWOP: Exception  (timed out) when looking for response to packet packet
Apr 26 13:00:49 raspberrypi weewx[11862]: restx: CWOP: Published record
2020-04-26 13:00:00 PDT (1587931200)
Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:05:00 PDT (1587931500)
Apr 26 13:10:40 raspberrypi weewx[11862]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262010z3401.26N/11718.84W_271/002g013t096r000p000P000b10154h22L752.weewx-3.9.2-Interceptor#015
Apr 26 13:10:40 raspberrypi weewx[11862]: restx: CWOP: Connected to
server cwop.aprs.net:14580
Apr 26 13:11:01 raspberrypi weewx[11862]: restx: CWOP: Exception  (timed out) when looking for response to packet packet
Apr 26 13:11:01 raspberrypi weewx[11862]: restx: CWOP: Published record
2020-04-26 13:10:00 PDT (1587931800)
Apr 26 13:15:29 raspberrypi weewx[11862]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:15:00 PDT (1587932100)
Apr 26 13:20:16 raspberrypi weewx[11862]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262020z3401.26N/11718.84W_310/006g013t096r000p000P000b10152h21L868.weewx-3.9.2-Interceptor#015
Apr 26 13:20:17 raspberrypi weewx[11862]: restx: CWOP: Connected to
server cwop.aprs.net:14580
Apr 26 13:20:37 raspberrypi weewx[11862]: restx: CWOP: Exception  (timed out) when looking for response to packet packet
Apr 26 13:20:37 raspberrypi weewx[11862]: restx: CWOP: Published record
2020-04-26 13:20:00 PDT (1587932400)
Apr 26 13:22:08 raspberrypi weewx[11862]: restx: Shut down CWOP thread.
Apr 26 13:22:14 raspberrypi weewx[12252]: engine: Loading service
weewx.restx.StdCWOP
Apr 26 13:22:14 raspberrypi weewx[12252]: restx: CWOP: Data for station
KQ6UP will be posted
Apr 26 13:22:14 raspberrypi weewx[12252]: engine: Finished loading
service weewx.restx.StdCWOP
Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262025z3401.26N/11718.84W_352/006g011t096r000p000P000b10153h21L796.weewx-3.9.2-Interceptor#015
Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:25:22 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:25:00 PDT (1587932700)
Apr 26 13:30:26 raspberrypi weewx[12252]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:30:00 PDT (1587933000)
Apr 26 13:35:19 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262035z3401.26N/11718.84W_261/006g015t097r000p000P000b10152h20L850.weewx-3.9.2-Interceptor#015
Apr 26 13:35:20 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:35:20 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:35:00 PDT (1587933300)
Apr 26 13:40:25 raspberrypi weewx[12252]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:40:00 PDT (1587933600)
Apr 26 13:45:31 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262045z3401.26N/11718.84W_297/006g017t097r000p000P000b10151h20L805.weewx-3.9.2-Interceptor#015
Apr 26 13:45:32 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:45:32 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:45:00 PDT (1587933900)
Apr 26 13:50:20 raspberrypi weewx[12252]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:50:00 PDT (1587934200)
Apr 26 13:55:26 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262055z3401.26N/11718.84W_291/001g011t097r000p000P000b10151h21L822.weewx-3.9.2-Interceptor#015
Apr 26 13:55:26 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:55:27 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:55:00 PDT (1587934500)
Apr 26 13:58:02 raspberrypi weewx[12252]: restx: Shut down CWOP thread.

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

On 4/26/20 1:16 PM, Dave Webb KB1PVH wrote:
> Chris,
>
>  I find it odd that if you make your CWOP section like mine that weewx
> falls on it's face unless something is funky when you copy and paste. 
>
>
> [[CWOP]]
>         # This section is for configuring posts to CWOP.
>
>         # If you wish to do this, set the option 'enable' to true,
>         # and specify the station ID (e.g., CW1234).
>         enable = true
>         station = KB1PVH-13
>         post_interval = 600
>         log_success = True
>         log_failure = True
>         server_list = rotate.aprs.net:14580
> , rotate.aprs2.net:14580
> , cwop.aprs.net:14580
> , cwop.aprs.net:23 
>         passcode = xx
>
>
>
> Dave-KB1PVH


I am starting to suspect I am having issues out of my network with port
14580.  I tried cwop.aprs.net:23  for a single
server, and it seems to be working.

When I tried rotate.aprs.net:14580 all by itself I got a:

Apr 26 00:25:30 raspberrypi weewx[1834]: restx: CWOP: Attempt 1 to
rotate.aprs.net:14580. Connection error: [Errno 111] Connection refused

Thanks,

Chris KQ6UP

-- 
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/7ad71e42-43c3-0dd3-3741-2eedb26762b4%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[gjr80]

Have you created and logged into your AerisWeather account before submitting 
details via that link? I had a similar problem until I read the following line 
near the top of the page:

Log in to your AerisWeather account and return to this page to continue the 
signup process.

I created an AerisWeather account taking up their free trial. I then went to 
the pws contributor link that has been posted and it worked fine. When I 
checked my AerisWeather account I now see a pws contributor service (not sure 
exactly what it was called, don’t have login details to hand) has been added to 
my AerisWeather account. Mind you I am yet to use the AerisWeather account to 
access the API.

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/f527c526-b587-4178-b049-0ffbcc17df50%40googlegroups.com.

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

It looks like its posting, but not showing up on the network:

Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262025z3401.26N/11718.84W_352/006g011t096r000p000P000b10153h21L796.weewx-3.9.2-Interceptor#015
Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:25:22 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:25:00 PDT (1587932700)

On 4/26/20 1:16 PM, Dave Webb KB1PVH wrote:
> Chris,
>
>  I find it odd that if you make your CWOP section like mine that weewx
> falls on it's face unless something is funky when you copy and paste. 
>
>
> [[CWOP]]
>         # This section is for configuring posts to CWOP.
>
>         # If you wish to do this, set the option 'enable' to true,
>         # and specify the station ID (e.g., CW1234).
>         enable = true
>         station = KB1PVH-13
>         post_interval = 600
>         log_success = True
>         log_failure = True
>         server_list = rotate.aprs.net:14580
> , rotate.aprs2.net:14580
> , cwop.aprs.net:14580
> , cwop.aprs.net:23 
>         passcode = xx
>
>
>
> Dave-KB1PVH
>
>
> On Sun, Apr 26, 2020 at 4:09 PM  > wrote:
>
>
> On 4/26/20 1:05 PM, gjr80 wrote:
> > The problem when using a single entry in the server_list for
> CWOP uploads is a known issue
> https://github.com/weewx/weewx/issues/520 refers. It will be fixed
> in 4.0, in the interim a work around exists, simply place a comma
> (,) immediately after the last character of the server_list entry.
> >
> > Gary
> >
> I will try that.  Here is another interesting line:
>
>
> Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
> (300 < 600) has not passed for record 2020-04-26 13:05:00 PDT
> (1587931500)
>
>
> Because of my error I have not had a successful post in a couple
> hours. 
> It saying I have not waited long enough.
>
>
> H
>
> Chris KQ6UP
>
> -- 
> 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/c964c99d-f6e4-2ce1-b237-d3a289b7c917%40gmail.com.
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAEMY9Fdi71osZsGbaFYrz_r3emvPWt7oXef3Y88G7S_Epxs0Pw%40mail.gmail.com
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ec685211-17a8-38d6-d2bd-b15fc4cf90d4%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[weather list]

Has anyone made this link work? I have a valid, working PWS login but it fails 
everytime I try that ink with this message: “Something went wrong, please try 
submitting again"



> On 23Apr, 2020, at 13:25, galfert  wrote:
> 
> Aeris Weather seems to be a replacement for Dark Sky that people are going 
> with. If you upload to PWSweather then you can get a free API key to Aeris 
> Weather.
> https://www.aerisweather.com/signup/pws/
> 
> 
> -- 
> 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/6013e83f-0778-437d-9870-82d2a0f39a61%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/AC96096E-2FAB-4612-B466-172462BB8DDD%40gmail.com.

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

According to Gary, I needed a comma after the single entry.  I did post
that line below exactly as you had it but with my personals.  It did not
work.  Just having the basic lines that it comes with seems to work, but
hit/miss fashion.

Chris KQ6UP

On 4/26/20 1:16 PM, Dave Webb KB1PVH wrote:
> Chris,
>
>  I find it odd that if you make your CWOP section like mine that weewx
> falls on it's face unless something is funky when you copy and paste. 
>
>
> [[CWOP]]
>         # This section is for configuring posts to CWOP.
>
>         # If you wish to do this, set the option 'enable' to true,
>         # and specify the station ID (e.g., CW1234).
>         enable = true
>         station = KB1PVH-13
>         post_interval = 600
>         log_success = True
>         log_failure = True
>         server_list = rotate.aprs.net:14580
> , rotate.aprs2.net:14580
> , cwop.aprs.net:14580
> , cwop.aprs.net:23 
>         passcode = xx
>
>
>
> Dave-KB1PVH
>
>
> On Sun, Apr 26, 2020 at 4:09 PM  > wrote:
>
>
> On 4/26/20 1:05 PM, gjr80 wrote:
> > The problem when using a single entry in the server_list for
> CWOP uploads is a known issue
> https://github.com/weewx/weewx/issues/520 refers. It will be fixed
> in 4.0, in the interim a work around exists, simply place a comma
> (,) immediately after the last character of the server_list entry.
> >
> > Gary
> >
> I will try that.  Here is another interesting line:
>
>
> Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
> (300 < 600) has not passed for record 2020-04-26 13:05:00 PDT
> (1587931500)
>
>
> Because of my error I have not had a successful post in a couple
> hours. 
> It saying I have not waited long enough.
>
>
> H
>
> Chris KQ6UP
>
> -- 
> 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/c964c99d-f6e4-2ce1-b237-d3a289b7c917%40gmail.com.
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAEMY9Fdi71osZsGbaFYrz_r3emvPWt7oXef3Y88G7S_Epxs0Pw%40mail.gmail.com
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2581351d-6777-6911-7887-49bb38f97b77%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] CWOP Broke After Upgrade

[gjr80]

I understand posts to CWOP are to be made no more frequently than every 10 
minutes so WeeWX checks before making a post to see if 10 minutes have elapsed 
since it last made a post. That’s fine, but when coupled with the lack of a 
documented formal acknowledgment of a post (and hence WeeWX assuming all posts 
are successful) you can end up in the situation where posts are skipped even 
though there have been no previous successful posts.

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/ba07417c-12f4-4d20-8dd2-428dbaf8fcbf%40googlegroups.com.

Re: [weewx-user] CWOP Broke After Upgrade

[Dave Webb KB1PVH]

Chris,

 I find it odd that if you make your CWOP section like mine that weewx
falls on it's face unless something is funky when you copy and paste.


[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = KB1PVH-13
post_interval = 600
log_success = True
log_failure = True
server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580,
cwop.aprs.net:14580, cwop.aprs.net:23
passcode = xx



Dave-KB1PVH


On Sun, Apr 26, 2020 at 4:09 PM  wrote:

>
> On 4/26/20 1:05 PM, gjr80 wrote:
> > The problem when using a single entry in the server_list for CWOP
> uploads is a known issue https://github.com/weewx/weewx/issues/520
> refers. It will be fixed in 4.0, in the interim a work around exists,
> simply place a comma (,) immediately after the last character of the
> server_list entry.
> >
> > Gary
> >
> I will try that.  Here is another interesting line:
>
>
> Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
> (300 < 600) has not passed for record 2020-04-26 13:05:00 PDT (1587931500)
>
>
> Because of my error I have not had a successful post in a couple hours.
> It saying I have not waited long enough.
>
>
> H
>
> Chris KQ6UP
>
> --
> 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/c964c99d-f6e4-2ce1-b237-d3a289b7c917%40gmail.com
> .
>

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

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

On 4/26/20 1:05 PM, gjr80 wrote:
> The problem when using a single entry in the server_list for CWOP uploads is 
> a known issue https://github.com/weewx/weewx/issues/520 refers. It will be 
> fixed in 4.0, in the interim a work around exists, simply place a comma (,) 
> immediately after the last character of the server_list entry.
>
> Gary
>
I will try that.  Here is another interesting line:


Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:05:00 PDT (1587931500)


Because of my error I have not had a successful post in a couple hours. 
It saying I have not waited long enough.


H

Chris KQ6UP

-- 
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/c964c99d-f6e4-2ce1-b237-d3a289b7c917%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] CWOP Broke After Upgrade

[gjr80]

The problem when using a single entry in the server_list for CWOP uploads is a 
known issue https://github.com/weewx/weewx/issues/520 refers. It will be fixed 
in 4.0, in the interim a work around exists, simply place a comma (,) 
immediately after the last character of the server_list entry.

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/b8cb4e3e-28be-4f1e-95ce-8a9b26756064%40googlegroups.com.

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

On 4/26/20 10:56 AM, Dave Webb KB1PVH wrote:
> Using the rotate servers spreads the load and that's why they
> recommend that hams using callsign and passcode use that as opposed to
> the standard server that is getting hammered by all the other weather
> stations. 
>
> Dave-KB1PVH


It does NOT like that line.  It is treating every character as a new
server.  I am using nano and cutting and pasting from my mac if that
makes any difference.  The text looks 100% normal in the ascii file.


Chris KQ6UP


Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@261945z3401.26N/11718.84W_253/006g015t094r000p000P000b10156h24L835.weewx-3.9.2-Interceptor#015
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'c'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'w'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'o'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'p'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: '.'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'a'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'p'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'r'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 's'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: '.'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'n'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'e'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 't'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Failed to publish
record 2020-04-26 12:45:00 PDT (1587930300): Tried 13 servers 3 times each

-- 
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/720b5437-09bb-f36a-b4b8-381f8814441f%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Xant]

Anton 

"end of 2021 seems ample time"

Not really (as pointed by someone before), "end of 2021" refers to owners 
of existing APIs, but widget service soon to be cancelled and DarkSky 
closed to new APIs.

So the search and research for a replacement is On...

-- 
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/5b6ce47b-e714-4b3c-a0e6-2d2c8ebbe56f%40googlegroups.com.

[weewx-user] Re: Peet Bros Ultimeter 2100 - Humidity Pad

[vince]

On Sunday, April 26, 2020 at 10:20:42 AM UTC-7, Steve2Q wrote:
>
> If I go to the main CWOP site and try to find data from myself there, 
> there is none. Perhaps I have a misunderstanding on what shows and what 
> doesn't. I received the following email on Friday (which I replied to) so 
> maybe the "registration" process for CWOP takes some time.??
>
>
>
Well considering the email to you was sent at 3pm on a Friday, I'd guess 
that your later reply will be processed perhaps when people get back to 
work on Monday. 

-- 
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/cebba5dc-b633-4c24-ae25-9b7b8a3fe59f%40googlegroups.com.

Re: [weewx-user] Aeris forecast not displaying.

[John Kline]

If you got that failure with weewx using the same forecast.py you used 
successfully from the command line, that is indeed strange.  Are you really 
sure you used the same client-id and secret-key in weewx.conf that you used 
from the command line?

The other option is that the service was temporarily down.  That’s what a 503 
is.  It could actually start working for you.

And of assumes that you are trying this from the same machine where you ran the 
forecast from the command line.  Also assuming you don’t have intermittent 
network connectivity problems.

> On Apr 26, 2020, at 10:26 AM, David Barto  wrote:
> 
> 
> Well dang, set it as noted, getting the same failure.
> 
> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
> WUThread: WU: failed attempt 1 to download forecast: HTTP Error 503: Service 
> Unavailable
> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
> AerisThread: Aeris: failed attempt 2 to download forecast: HTTP Error 400: 
> Bad Request
> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
> AerisThread: Aeris: failed attempt 3 to download forecast: HTTP Error 400: 
> Bad Request
> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
> AerisThread: Aeris: failed to download forecast
> /var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
> AerisThread: Aeris: no forecast data for Poway, CA from 
> http://api.aerisapi.com/forecasts/
> 
> I’ll just wait until 4.0 and see if that changes anything.
> 
>   David
> 
>> On Apr 26, 2020, at 9:50 AM, John Kline  wrote:
>> 
>> Add location to the Aeris entry in weewx.conf.
>> 
>> [[Aeris]]
>> client_id = XXX
>> client_secret = XXX
>> location = "Poway, CA"
>> 
 On Apr 26, 2020, at 9:09 AM, David Barto  wrote:
 
>>> Brilliant. Now I get the forecast if I set the location to “Poway, CA.” 
>>> and that works for me.
>>> Where in the configuration for Aeris would I change the location for 
>>> getting their forecast for my city?
>>> 
>>> David
>>> 
 On Apr 25, 2020, at 5:20 PM, John Kline  wrote:
 
 Yikes.  Forgot the diff.  The line numbers won’t match, but this should be 
 easy to apply to your current forecast.py.
 
 diff --git a/bin/user/forecast.py b/bin/user/forecast.py
 index d947fb3..2254fed 100644
 --- a/bin/user/forecast.py
 +++ b/bin/user/forecast.py
 @@ -5033,9 +5033,9 @@ if __name__ == "__main__":
help="specify the location")
  parser.add_option("--api-key", dest="api_key", type=str, 
 metavar="KEY",
help="specify the api key")
 -parser.add_option("--client-id", dest="client-id", type=str,
 +parser.add_option("--client-id", dest="client_id", type=str,
metavar="ID", help="specify the client id")
 -parser.add_option("--client-secret", dest="client-secret", 
 type=str,
 +parser.add_option("--client-secret", dest="client_secret", 
 type=str,
metavar="SECRET", help="specify the client 
 secret")
  parser.add_option("--filename", dest="filename", 
 metavar="FILENAME",
help="file that contains forecast data",
 @@ -5078,6 +5078,9 @@ if __name__ == "__main__":
  fcast = AerisForecast.download(
  options.client_id, options.client_secret, options.loc)
  print(fcast)
 +elif options.method.lower() == 'aeris':
 +fcast = AerisForecast.download(options.client_id, 
 options.client_secret, options.loc)
 +print(fcast)
  elif options.method.lower() == 'wwo':
  fcast = WWOForecast.download(options.api_key, options.loc)
  print(fcast)
 
>> On Apr 25, 2020, at 4:59 PM, John Kline  wrote:
>> 
> 
> Here’s a diff showing the changes I had to make so that the command below 
> will run.
> 
> Please make those changes and then run the command again pointing to your 
> changed file.  You don’t even have to update the forecast.py that weewx 
> is using.  This is just so that you don’t get the method not supported 
> error below when running directly.
> 
> Of course, you also need to plug in your client-I’d and secret-key.
> 
> BTW, you didn’t have to send me this error.  I told you it wouldn’t work 
> without modifying the code.
> 
>>> On Apr 25, 2020, at 4:51 PM, David Barto  wrote:
>>> 
>> Running Weewx 3.9.2.
>> Forecast skins/forecast/skin.conf:version = 3.3.2
>> 
>> 
>> Magrathea:weewx-installed katherinebarto$ 
>> PYTHONPATH=/Users/shared/weewx/bin python bin/user/forecast.py --method 
>> Aeris --action download --client-id XXX --client-secret 

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

On 4/26/20 10:17 AM, Dave Webb KB1PVH wrote:
> Chris,
> 
> Have you tried leaving all the existing info and just change the APRS
> server to rotate.aprs.net:14580/ 
> 
> Dave-KB1PVH
> 

I will give that a shot.

Chris KQ6UP

-- 
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/279350be-f263-8e23-46c1-44c2739ef293%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Aeris forecast not displaying.

[David Barto]

Well dang, set it as noted, getting the same failure.

/var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: WUThread: 
WU: failed attempt 1 to download forecast: HTTP Error 503: Service Unavailable
/var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
AerisThread: Aeris: failed attempt 2 to download forecast: HTTP Error 400: Bad 
Request
/var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
AerisThread: Aeris: failed attempt 3 to download forecast: HTTP Error 400: Bad 
Request
/var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
AerisThread: Aeris: failed to download forecast
/var/log/system.log:Apr 26 10:16:16 Magrathea weewx[51991]: forecast: 
AerisThread: Aeris: no forecast data for Poway, CA from 
http://api.aerisapi.com/forecasts/

I’ll just wait until 4.0 and see if that changes anything.

David

> On Apr 26, 2020, at 9:50 AM, John Kline  wrote:
> 
> Add location to the Aeris entry in weewx.conf.
> 
> [[Aeris]]
> client_id = XXX
> client_secret = XXX
> location = "Poway, CA"
> 
>> On Apr 26, 2020, at 9:09 AM, David Barto  wrote:
>> 
>> Brilliant. Now I get the forecast if I set the location to “Poway, CA.” and 
>> that works for me.
>> Where in the configuration for Aeris would I change the location for getting 
>> their forecast for my city?
>> 
>>  David
>> 
>>> On Apr 25, 2020, at 5:20 PM, John Kline >> > wrote:
>>> 
>>> Yikes.  Forgot the diff.  The line numbers won’t match, but this should be 
>>> easy to apply to your current forecast.py.
>>> 
>>> diff --git a/bin/user/forecast.py b/bin/user/forecast.py
>>> index d947fb3..2254fed 100644
>>> --- a/bin/user/forecast.py
>>> +++ b/bin/user/forecast.py
>>> @@ -5033,9 +5033,9 @@ if __name__ == "__main__":
>>>help="specify the location")
>>>  parser.add_option("--api-key", dest="api_key", type=str, 
>>> metavar="KEY",
>>>help="specify the api key")
>>> -parser.add_option("--client-id", dest="client-id", type=str,
>>> +parser.add_option("--client-id", dest="client_id", type=str,
>>>metavar="ID", help="specify the client id")
>>> -parser.add_option("--client-secret", dest="client-secret", 
>>> type=str,
>>> +parser.add_option("--client-secret", dest="client_secret", 
>>> type=str,
>>>metavar="SECRET", help="specify the client 
>>> secret")
>>>  parser.add_option("--filename", dest="filename", 
>>> metavar="FILENAME",
>>>help="file that contains forecast data",
>>> @@ -5078,6 +5078,9 @@ if __name__ == "__main__":
>>>  fcast = AerisForecast.download(
>>>  options.client_id, options.client_secret, options.loc)
>>>  print(fcast)
>>> +elif options.method.lower() == 'aeris':
>>> +fcast = AerisForecast.download(options.client_id, 
>>> options.client_secret, options.loc)
>>> +print(fcast)
>>>  elif options.method.lower() == 'wwo':
>>>  fcast = WWOForecast.download(options.api_key, options.loc)
>>>  print(fcast)
>>> 
 On Apr 25, 2020, at 4:59 PM, John Kline >>> > wrote:
 
 
 Here’s a diff showing the changes I had to make so that the command below 
 will run.
 
 Please make those changes and then run the command again pointing to your 
 changed file.  You don’t even have to update the forecast.py that weewx is 
 using.  This is just so that you don’t get the method not supported error 
 below when running directly.
 
 Of course, you also need to plug in your client-I’d and secret-key.
 
 BTW, you didn’t have to send me this error.  I told you it wouldn’t work 
 without modifying the code.
 
> On Apr 25, 2020, at 4:51 PM, David Barto  > wrote:
> 
> Running Weewx 3.9.2.
> Forecast skins/forecast/skin.conf:version = 3.3.2
> 
> 
> Magrathea:weewx-installed katherinebarto$ 
> PYTHONPATH=/Users/shared/weewx/bin python bin/user/forecast.py --method 
> Aeris --action download --client-id XXX --client-secret YYY --loc 
> “32.98265 -117.0405"
> 
> Returns:
> unsupported forecast method Aeris
> 
>> On Apr 25, 2020, at 2:48 PM, John Kline > > wrote:
>> 
>> I switched from my free trial Aeris to a free one based on the thread 
>> you mention.  I got back the same client ID and secret.  It continues to 
>> work for me.
>> 
>> You should be able to do something like the following to test:
>> 
>> PYTHONPATH=/home/weewx/bin python3 bin/user/forecast.py --method Aeris 
>> --action download --client-id XXX --client-secret XXX--loc 
>> "37.431495,-122.110937"
>> 

[weewx-user] Re: Peet Bros Ultimeter 2100 - Humidity Pad

[Steve2Q]

Burt...apparently my data is being sent to CWOP, but it only shows up 
here:  http://www.findu.com/cgi-bin/wxpage.cgi?call=FW7312

If I go to the main CWOP site and try to find data from myself there, there 
is none. Perhaps I have a misunderstanding on what shows and what doesn't. 
I received the following email on Friday (which I replied to) so maybe the 
"registration" process for CWOP takes some time.??

cwop-supp...@noaa.gov 
[image: Attachments]Apr 24, 2020, 2:53 PM (2 days ago)


to leigh.k.cheatwood, me 
Our records indicate that your site is sending weather data to Findu at 
http://www.findu.com/cgi-bin/find.cgi?call=FW7312 but is not yet registered 
within CWOP. Registering with CWOP allows distribution of your weather data 
to institutions like NOAA. This is what we currently have for your site's 
location information: CWOP Call Sign/Site ID: FW7312, Latitude: 26.51400, 
Longitude: -80.15500, Elevation (meters): 4.46. Please verify this 
information is correct by replying to this email so that we may register 
your site. Thanks, CWOP-Support

-- 
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/968e5b69-c5cb-4371-9de7-e1542682f02a%40googlegroups.com.

[weewx-user] Re: Peet Bros Ultimeter 2100 - Humidity Pad

[Steve2Q]

Hi Burt..I did not have the line:  post_interval = 300I added that, but 
left off the passcode as I do not have APRS capability. I will see what 
happens now.

Thanks, Steve  N2QLQ

-- 
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/302cb03a-9337-4170-9269-93d1be0df50f%40googlegroups.com.

Re: [weewx-user] Aeris forecast not displaying.

[John Kline]

Add location to the Aeris entry in weewx.conf.

[[Aeris]]
client_id = XXX
client_secret = XXX
location = "Poway, CA"

>> On Apr 26, 2020, at 9:09 AM, David Barto  wrote:
> Brilliant. Now I get the forecast if I set the location to “Poway, CA.” and 
> that works for me.
> Where in the configuration for Aeris would I change the location for getting 
> their forecast for my city?
> 
>   David
> 
>> On Apr 25, 2020, at 5:20 PM, John Kline  wrote:
>> 
>> Yikes.  Forgot the diff.  The line numbers won’t match, but this should be 
>> easy to apply to your current forecast.py.
>> 
>> diff --git a/bin/user/forecast.py b/bin/user/forecast.py
>> index d947fb3..2254fed 100644
>> --- a/bin/user/forecast.py
>> +++ b/bin/user/forecast.py
>> @@ -5033,9 +5033,9 @@ if __name__ == "__main__":
>>help="specify the location")
>>  parser.add_option("--api-key", dest="api_key", type=str, 
>> metavar="KEY",
>>help="specify the api key")
>> -parser.add_option("--client-id", dest="client-id", type=str,
>> +parser.add_option("--client-id", dest="client_id", type=str,
>>metavar="ID", help="specify the client id")
>> -parser.add_option("--client-secret", dest="client-secret", type=str,
>> +parser.add_option("--client-secret", dest="client_secret", type=str,
>>metavar="SECRET", help="specify the client 
>> secret")
>>  parser.add_option("--filename", dest="filename", metavar="FILENAME",
>>help="file that contains forecast data",
>> @@ -5078,6 +5078,9 @@ if __name__ == "__main__":
>>  fcast = AerisForecast.download(
>>  options.client_id, options.client_secret, options.loc)
>>  print(fcast)
>> +elif options.method.lower() == 'aeris':
>> +fcast = AerisForecast.download(options.client_id, 
>> options.client_secret, options.loc)
>> +print(fcast)
>>  elif options.method.lower() == 'wwo':
>>  fcast = WWOForecast.download(options.api_key, options.loc)
>>  print(fcast)
>> 
 On Apr 25, 2020, at 4:59 PM, John Kline  wrote:
>>> 
>>> Here’s a diff showing the changes I had to make so that the command below 
>>> will run.
>>> 
>>> Please make those changes and then run the command again pointing to your 
>>> changed file.  You don’t even have to update the forecast.py that weewx is 
>>> using.  This is just so that you don’t get the method not supported error 
>>> below when running directly.
>>> 
>>> Of course, you also need to plug in your client-I’d and secret-key.
>>> 
>>> BTW, you didn’t have to send me this error.  I told you it wouldn’t work 
>>> without modifying the code.
>>> 
> On Apr 25, 2020, at 4:51 PM, David Barto  wrote:
 Running Weewx 3.9.2.
 Forecast skins/forecast/skin.conf:version = 3.3.2
 
 
 Magrathea:weewx-installed katherinebarto$ 
 PYTHONPATH=/Users/shared/weewx/bin python bin/user/forecast.py --method 
 Aeris --action download --client-id XXX --client-secret YYY --loc 
 “32.98265 -117.0405"
 
 Returns:
 unsupported forecast method Aeris
 
> On Apr 25, 2020, at 2:48 PM, John Kline  wrote:
> 
> I switched from my free trial Aeris to a free one based on the thread you 
> mention.  I got back the same client ID and secret.  It continues to work 
> for me.
> 
> You should be able to do something like the following to test:
> 
> PYTHONPATH=/home/weewx/bin python3 bin/user/forecast.py --method Aeris 
> --action download --client-id XXX --client-secret XXX--loc 
> "37.431495,-122.110937"
> 
> If you could do that, you could quickly see wether the issue is that no 
> forecast is available for the location you requested.
> 
> Alas, I notice that Aeris isn’t supported when running as main.  I added 
> the support to do that and fixed some bugs WRT command line arguments.  I 
> will add it to my fork, but I will need to test more.
> 
> What version of WeeWX and the forecast plugin are you running?
> 
> ALSO, PLEASE REPLY ON THE LIST RATHER THAN DIRECTLY TO ME.
> 
> 
>>> On Apr 25, 2020, at 12:23 PM, David Barto  wrote:
>> 
>> galfert posted that you can get free Aeris forecasting:
>> 
>> The free Aeris Weather account is not advertised. You have to use the 
>> link I provided to get in on the special "Contributor account" only for 
>> those that contribute with their station to PWSweather.com.
>> 
>> This link: https://www.aerisweather.com/signup/pws/
>> 
>> -
>> So I signed up for Aeris through the pws, and got my 2 hashes.
>> 
>> I added the Aeris data to weewx.conf and restarted.
>> The forecast page doesn't show any forecast for Aeris, while the
>> NWS 

Re: [weewx-user] Aeris forecast not displaying.

[David Barto]

Brilliant. Now I get the forecast if I set the location to “Poway, CA.” and 
that works for me.
Where in the configuration for Aeris would I change the location for getting 
their forecast for my city?

David

> On Apr 25, 2020, at 5:20 PM, John Kline  wrote:
> 
> Yikes.  Forgot the diff.  The line numbers won’t match, but this should be 
> easy to apply to your current forecast.py.
> 
> diff --git a/bin/user/forecast.py b/bin/user/forecast.py
> index d947fb3..2254fed 100644
> --- a/bin/user/forecast.py
> +++ b/bin/user/forecast.py
> @@ -5033,9 +5033,9 @@ if __name__ == "__main__":
>help="specify the location")
>  parser.add_option("--api-key", dest="api_key", type=str, 
> metavar="KEY",
>help="specify the api key")
> -parser.add_option("--client-id", dest="client-id", type=str,
> +parser.add_option("--client-id", dest="client_id", type=str,
>metavar="ID", help="specify the client id")
> -parser.add_option("--client-secret", dest="client-secret", type=str,
> +parser.add_option("--client-secret", dest="client_secret", type=str,
>metavar="SECRET", help="specify the client secret")
>  parser.add_option("--filename", dest="filename", metavar="FILENAME",
>help="file that contains forecast data",
> @@ -5078,6 +5078,9 @@ if __name__ == "__main__":
>  fcast = AerisForecast.download(
>  options.client_id, options.client_secret, options.loc)
>  print(fcast)
> +elif options.method.lower() == 'aeris':
> +fcast = AerisForecast.download(options.client_id, 
> options.client_secret, options.loc)
> +print(fcast)
>  elif options.method.lower() == 'wwo':
>  fcast = WWOForecast.download(options.api_key, options.loc)
>  print(fcast)
> 
>> On Apr 25, 2020, at 4:59 PM, John Kline  wrote:
>> 
>> 
>> Here’s a diff showing the changes I had to make so that the command below 
>> will run.
>> 
>> Please make those changes and then run the command again pointing to your 
>> changed file.  You don’t even have to update the forecast.py that weewx is 
>> using.  This is just so that you don’t get the method not supported error 
>> below when running directly.
>> 
>> Of course, you also need to plug in your client-I’d and secret-key.
>> 
>> BTW, you didn’t have to send me this error.  I told you it wouldn’t work 
>> without modifying the code.
>> 
>>> On Apr 25, 2020, at 4:51 PM, David Barto  wrote:
>>> 
>>> Running Weewx 3.9.2.
>>> Forecast skins/forecast/skin.conf:version = 3.3.2
>>> 
>>> 
>>> Magrathea:weewx-installed katherinebarto$ 
>>> PYTHONPATH=/Users/shared/weewx/bin python bin/user/forecast.py --method 
>>> Aeris --action download --client-id XXX --client-secret YYY --loc “32.98265 
>>> -117.0405"
>>> 
>>> Returns:
>>> unsupported forecast method Aeris
>>> 
 On Apr 25, 2020, at 2:48 PM, John Kline >>> > wrote:
 
 I switched from my free trial Aeris to a free one based on the thread you 
 mention.  I got back the same client ID and secret.  It continues to work 
 for me.
 
 You should be able to do something like the following to test:
 
 PYTHONPATH=/home/weewx/bin python3 bin/user/forecast.py --method Aeris 
 --action download --client-id XXX --client-secret XXX--loc 
 "37.431495,-122.110937"
 
 If you could do that, you could quickly see wether the issue is that no 
 forecast is available for the location you requested.
 
 Alas, I notice that Aeris isn’t supported when running as main.  I added 
 the support to do that and fixed some bugs WRT command line arguments.  I 
 will add it to my fork, but I will need to test more.
 
 What version of WeeWX and the forecast plugin are you running?
 
 ALSO, PLEASE REPLY ON THE LIST RATHER THAN DIRECTLY TO ME.
 
 
> On Apr 25, 2020, at 12:23 PM, David Barto  > wrote:
> 
> 
> galfert posted that you can get free Aeris forecasting:
> 
> The free Aeris Weather account is not advertised. You have to use the 
> link I provided to get in on the special "Contributor account" only for 
> those that contribute with their station to PWSweather.com 
> .
> 
> This link: https://www.aerisweather.com/signup/pws/ 
> 
> 
> -
> So I signed up for Aeris through the pws, and got my 2 hashes.
> 
> I added the Aeris data to weewx.conf and restarted.
> The forecast page doesn't show any forecast for Aeris, while the
> NWS does show up.
> 
> https://www.kdbarto.org/weather/forecast/multiple-tables.html 
> 

[weewx-user] Re: Weather station GARNI 935PC - compatibility with Weewx?

[Bob Atchley]

Hi Pavel,

Quite good timing, I have a new version of the WS6in1 driver working on my 
system.  I want to let it run for 24 hours or so on my system to make sure 
it is stable before I release it

I will write a changelog but basically the changes are:

1) setTime implemented.  This is run from the driver on startup and once 
every 24 hours

2) Implemented decoding for the 7 extra sensors.  I do not have an extra 
sensor so my testing has been limited

Bob

-- 
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/c6662916-bcf2-4f03-87de-68fba806d1e4%40googlegroups.com.

Re: [weewx-user] CWOP Broke After Upgrade

[chris]

On 4/25/20 6:02 PM, Dave Webb KB1PVH wrote:
> Hey Chris,
> 
>  It's actually suggested that us radio geeks use the rotate servers. Try
> something like this
> 
> [[CWOP]]
>         # This section is for configuring posts to CWOP.
> 
>         # If you wish to do this, set the option 'enable' to true,
>         # and specify the station ID (e.g., CW1234).
>         enable = true
>         station = KB1PVH-13
>         post_interval = 600
>         log_success = True
>         log_failure = True
>         server_list = rotate.aprs.net:14580
> , rotate.aprs2.net:14580
> , cwop.aprs.net:14580
> , cwop.aprs.net:23 
>         passcode = your_passcode_here
> 
> Dave-KB1PVH

Adding those lines broke it.  I did put my correct password.  I have
since changed it back to my previous configuration, and it has started
to work again.

Chris KQ6UP

-- 
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/3a008a48-bce3-7a8f-7139-50793f1dab88%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Anton vanNwnhzn@GMail]

'End of 2021' seems ample time to find an alternative solution for the API.

Op 8-4-2020 om 3:12 schreef Xant:


To note, this is not an "usual" social forum (profanity not allowed). 
All constructive and educated points are welcome, in benefit of the 
whole WX developers and enthusiasts.


DarkSky was indeed a good service. Now, we search for a replacement.

X
--
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/0d416cab-015b-4eff-9ffb-41553e8e5db4%40googlegroups.com 
.


--

===
Contactinfo voor Anton van Nieuwenhuijzen:
Email= tonv...@gmail.com
Fax2Mail = (+31/0)84.8397303 [ook Voice2Mail]
===
Deze E-mail en eventuele aanhangende files zijn
alleen bestemd voor de geadresseerde(n).
Als je deze E-mail ten onrechte hebt ontvangen,
dan aub verwijderen en de afzender informeren.

--
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/c3a6c11b-4a73-0109-53b1-35c02e635437%40gmail.com.

[weewx-user] Re: Cheetah Rounding Values

[rich T]

Thanks everyone who provided suggestions. Using Gary's suggestion and it 
finally works.

#set Daily_Max = $day.outTemp.max
#set Departure_Temp_Max = $Daily_Max.raw - 
$day.outTemp.historical_max_avg.raw
#set Departure_Temp_Max = round($Departure_Temp_Max, 1)



On Sunday, April 26, 2020 at 12:54:54 AM UTC-4, gjr80 wrote:
>
> Rich,
>
> How you format data in a Cheetah generated report really depends on the 
> source of the data. If you are using a WeeWX generated tag, eg 
> $current.outTemp, then you have all the formatting and unit conversion 
> options of a WeeWX tag available to you (as linked by Tom). If the data 
> comes from some inline python in your Cheetah template then you are 
> responsible for formatting the data, for example, if your template had the 
> following:
>
> #set $pie_temperature = 22/7
>
> and you wanted to use $pie_temperature in your template then you would be 
> responsible for formatting the output, you might do something like:
>
> #set $pie_temperature_2d = round($pie_temperature, 2)
>
> and then use $pie_temperature_2d to display $pie_temperature to two 
> decimal places (or you might just have used #set $pie_temperature = 
> round(22/7, 2) up front). Bottom line is, formatting/unit conversion etc 
> is your problem, not WeeWX'
>
> If your data comes from a Search List Extension (SLE) then it depends on 
> what the SLE provides. Let's say the SLE provides a tag $pie_temp that is 
> a temperature. If $pie_temp is just a number then just like 
> $pie_temperature you need to format it yourself. However, is the SLE is a 
> little more sophisticated and provides $pie_temp as a special WeeWX 
> object known as a ValueHelper, then $pie_temp has all of the formatting 
> and unit conversion abilities of a WeeWX tag such as $current.outTemp. 
> Generally speaking it is quite easy to have a SLE return a ValueHelper(), 
> whilst it does make the SLE code a little more complex it provides for a 
> much more flexible output. 
>
> At the end of the day a SLE does not allow formatting per se, rather it is 
> the type of output from a SLE that determines what formatting/unit 
> conversion is available. Have a read of the section Defining new tags 
>  in the 
> Customization Guide, it covers ValueHelpers and SLEs with examples.
>
> Gary
>
> On Sunday, 26 April 2020 14:29:11 UTC+10, rich T wrote:
>>
>> Thanks I tried your suggestions, but still does not round to the decimal 
>> point. I did create a new tag. Do I need to create a new search list 
>> extension to allow formatting?
>>
>> Thanks 
>> Rich
>>
>>
>>

-- 
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/7817c450-d99f-47b6-b0d8-58dc258bb1e6%40googlegroups.com.

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Pat]

I've incorporated Aeris Weather into the Belchertown 1.2b2 beta skin. 
Details can be found here for anyone who wants to try it 
out: https://github.com/poblabs/weewx-belchertown/tree/development

Be sure to read the readme on settings and getting Aeris setup. 

On Friday, April 24, 2020 at 2:05:44 PM UTC-4, galfert wrote:
>
> The free Aeris Weather account is not advertised. You have to use the link 
> I provided to get in on the special "Contributor account" only for those 
> that contribute with their station to PWSweather.com.
>
> This link:
> https://www.aerisweather.com/signup/pws/ 
> 
>
>
>
> On Friday, April 24, 2020 at 1:11:49 PM UTC-4, Philip Kutzenco wrote:
>>
>> Hmm. I think galfert is correct. I believe as long as your weewx 
>> implementation is sending "quality data to pwsweather.com monthly, use 
>> of the API is free. Sorry for the false alarm.
>>
>> On Friday, April 24, 2020 at 12:49:03 PM UTC-4, Philip Kutzenco wrote:
>>>
>>> I signed up. However, it looks to me that having a PWSweather account 
>>> lets you get an Aeris Weather account (which is linked), but when I go to 
>>> the API site with that account, they only offer a 30 day free trial. After 
>>> that there is a monthly or annual cost.for the API subscription. Am I 
>>> missing something?
>>>
>>> On Thursday, April 23, 2020 at 1:25:18 PM UTC-4, galfert wrote:

 Aeris Weather seems to be a replacement for Dark Sky that people are 
 going with. If you upload to PWSweather then you can get a free API key to 
 Aeris Weather.
 https://www.aerisweather.com/signup/pws/ 
 



-- 
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/e67d2f65-b3c6-4d1e-a678-2562f2dca2f5%40googlegroups.com.

Re: [weewx-user] CWOP Broke After Upgrade

[Christopher Maness]

On 4/26/20 5:05 AM, Tom Keffer wrote:
> Normally, CWOP returns a confirmation after posting the TNC packet,
> which looks something like: "# logresp KQ6UP unverified, server CWOP-5"
> 
> However, according to the CWOP documentation
> , there is no formal acknowledgement of a
> successful post, hence the WeeWX code does not actually check for any
> confirmation.
> 
> Looking through your raw packet stream
> , you are missing a lot
> of records. Has your weather station been up the whole time?
> 
> -tk
> 

It was down for about a week without my knowledge, and since I am home
bored with COVID-19, I have been tinkering with upgrades.  That has
taken it offline sporadically.  Since I changed some lines in the CWOP
entry for the .conf file, it has not reported.  I am going to change it
back and see if at least it works sporadically again.

Regards,
Chris KQ6UP

-- 
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/53598a23-5ddc-4dc0-445a-32225857cfbb%40gmail.com.


0x163643459E5CF84C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [weewx-user] CWOP Broke After Upgrade

[Tom Keffer]

Normally, CWOP returns a confirmation after posting the TNC packet, which
looks something like: "# logresp KQ6UP unverified, server CWOP-5"

However, according to the CWOP documentation ,
there is no formal acknowledgement of a successful post, hence the WeeWX
code does not actually check for any confirmation.

Looking through your raw packet stream
, you are missing a lot of
records. Has your weather station been up the whole time?

-tk

On Sat, Apr 25, 2020 at 5:38 PM  wrote:

>
>
> On 4/25/20 4:34 PM, Tom Keffer wrote:
> > You log runs from 15:37:31 to 15:43:10, with a single CWOP post at
> > 15:42:20. Looks pretty normal to me.
> >
> > If you want even more debug information, you can set debug=2 to have the
> > log include the TNC packets that are sent to the CWOP server.
> >
> > On Sat, Apr 25, 2020 at 3:47 PM  > > wrote:
> >
>
> Tom, it looks my connections to the CWOP server may be timing out.  Can
> you have a look?
>
> Here is my debug=2 log:
>
> https://pastebin.com/TkQweD3a
>
> Regards,
> Chris KQ6UP
>

-- 
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/CAPq0zECc%2BinxEM-k5pmo58JPq0gF4rPGrR4j%3DmdBHRPQhLwHOg%40mail.gmail.com.

[weewx-user] Re: Weather station GARNI 935PC - compatibility with Weewx?

[Pavel Pavlik]

Hi Bob,

How are you? I would like to ask you if you have any news for me.

Thanks a lot & have a nice day.

Pavel



Dne pondělí 13. dubna 2020 22:31:05 UTC+2 Bob Atchley napsal(a):
>
> Hi Pavel,
>
> I have written a setTime function (not yet tested).  I then looked in the 
> weewx engine to see how this is invoked ... and we have a problem.  The 
> engine calls the getTime function first, so that also needs writing.  I 
> know how to write this but unfortunately the ws6in1 protocol only provides 
> the time to the minute so will always be between 0 and 59 seconds out from 
> the correct time.  So it seems a bit pointless to write it.  Instead I 'm 
> thinking of automatically setting the time once every 24 hours (i.e. 
> ignoring the engine).  Just not yet quite comfortable with that.  So more 
> thinking time 
>
> The setTime also poses 2 problems:
> 1) I have no idea how it deals with time zones.  This is not a problem for 
> me I have my rpi2 set at permanent UTC time (no summer time correction) - 
> but maybe for others (so please let me know if this causes a problem)
> 2) The evidence I have shows that when setting the date and time the crc 
> checksum bytes are sent the wrong way around.  It could be because of a 
> defect in the console, or a defect in the official software and the console 
> doesn't actually check the crc checksum.  Initially I'm sending the bytes 
> in the correct order - once I test the updated driver I will know  the 
> answer
>
> So work in progress, but I'm confident I can provide both setting the 
> console time and the 7 extra sensor data that you are after
>
> Bob 
>

-- 
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/7c4f1903-4e08-40ff-a558-5f90740c68c5%40googlegroups.com.

[weewx-user] Re: Cheetah Rounding Values

[Andrew Milner]

If you are using weewx tags it would be something like
$current.outTemp.format("%.1f") for one decimal place

On Sunday, 26 April 2020 07:54:54 UTC+3, gjr80 wrote:
>
> Rich,
>
> How you format data in a Cheetah generated report really depends on the 
> source of the data. If you are using a WeeWX generated tag, eg 
> $current.outTemp, then you have all the formatting and unit conversion 
> options of a WeeWX tag available to you (as linked by Tom). If the data 
> comes from some inline python in your Cheetah template then you are 
> responsible for formatting the data, for example, if your template had the 
> following:
>
> #set $pie_temperature = 22/7
>
> and you wanted to use $pie_temperature in your template then you would be 
> responsible for formatting the output, you might do something like:
>
> #set $pie_temperature_2d = round($pie_temperature, 2)
>
> and then use $pie_temperature_2d to display $pie_temperature to two 
> decimal places (or you might just have used #set $pie_temperature = 
> round(22/7, 2) up front). Bottom line is, formatting/unit conversion etc 
> is your problem, not WeeWX'
>
> If your data comes from a Search List Extension (SLE) then it depends on 
> what the SLE provides. Let's say the SLE provides a tag $pie_temp that is 
> a temperature. If $pie_temp is just a number then just like 
> $pie_temperature you need to format it yourself. However, is the SLE is a 
> little more sophisticated and provides $pie_temp as a special WeeWX 
> object known as a ValueHelper, then $pie_temp has all of the formatting 
> and unit conversion abilities of a WeeWX tag such as $current.outTemp. 
> Generally speaking it is quite easy to have a SLE return a ValueHelper(), 
> whilst it does make the SLE code a little more complex it provides for a 
> much more flexible output. 
>
> At the end of the day a SLE does not allow formatting per se, rather it is 
> the type of output from a SLE that determines what formatting/unit 
> conversion is available. Have a read of the section Defining new tags 
>  in the 
> Customization Guide, it covers ValueHelpers and SLEs with examples.
>
> Gary
>
> On Sunday, 26 April 2020 14:29:11 UTC+10, rich T wrote:
>>
>> Thanks I tried your suggestions, but still does not round to the decimal 
>> point. I did create a new tag. Do I need to create a new search list 
>> extension to allow formatting?
>>
>> Thanks 
>> Rich
>>
>>
>>

-- 
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/d198e5e0-dca1-4c2b-b5eb-eda02b5316e9%40googlegroups.com.