[weewx-user] Re: NOAA report with dust sensor
Just by way of background up until v4.3.0 WeeWX shipped with strict_ascii encoding for NOAA reports. v4.4.0 changed that to utf8 but for new installs only, upgrades or earlier versions need to be changed manually. Gary On Wednesday, 3 February 2021 at 16:27:31 UTC+10 calo@gmail.com wrote: > Hi Gary, > > thanks again. Works now. > [image: DustPM10.png] > > On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote: > >> Hi Gary, >> >> thanks. Yes, you are right. Got this in my skins.conf and it is even >> written in the explanation. Will change and report back. >> >> >> [CheetahGenerator] >> >> # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii' >> encoding = html_entities >> >> [[SummaryByMonth]] >> # Reports that summarize "by month" >> [[[NOAA_month]]] >> encoding = strict_ascii >> template = NOAA/NOAA-%Y-%m.txt.tmpl >> >> [[SummaryByYear]] >> # Reports that summarize "by year" >> [[[NOAA_year]]] >> encoding = strict_ascii >> template = NOAA/NOAA-%Y.txt.tmpl >> >> On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote: >> >>> Hi, >>> >>> What encoding are you using for the NOAA format reports in your >>> skin.conf? If you have the old encoding = strict_ascii then no you won’t >>> see the mu character, you should see it though if you have encoding = utf8. >>> >>> Gary >>> >>> On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com >>> wrote: >>> Hi, I added my SDS011 data (which I read-in using file-pile) however the unit in the header is not shows as microgramm per cubic meter. I changed the unit in units.py to see if it also is adapted in the report and was working however using the default pm10_0 unit shows as g/m This is my entry in .tmpl DUST PM10 ($unit.label.SDS011_PM10.strip()) [image: NOAA Dust PM10.png] Any idea? >>> -- 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/a6d09609-2cc5-40e8-84d5-a0bdc56b71a8n%40googlegroups.com.
[weewx-user] Re: NOAA report with dust sensor
Hi Gary, thanks again. Works now. [image: DustPM10.png] On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote: > Hi Gary, > > thanks. Yes, you are right. Got this in my skins.conf and it is even > written in the explanation. Will change and report back. > > > [CheetahGenerator] > > # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii' > encoding = html_entities > > [[SummaryByMonth]] > # Reports that summarize "by month" > [[[NOAA_month]]] > encoding = strict_ascii > template = NOAA/NOAA-%Y-%m.txt.tmpl > > [[SummaryByYear]] > # Reports that summarize "by year" > [[[NOAA_year]]] > encoding = strict_ascii > template = NOAA/NOAA-%Y.txt.tmpl > > On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote: > >> Hi, >> >> What encoding are you using for the NOAA format reports in your >> skin.conf? If you have the old encoding = strict_ascii then no you won’t >> see the mu character, you should see it though if you have encoding = utf8. >> >> Gary >> >> On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com >> wrote: >> >>> Hi, I added my SDS011 data (which I read-in using file-pile) however the >>> unit in the header is not shows as microgramm per cubic meter. I changed >>> the unit in units.py to see if it also is adapted in the report and was >>> working however using the default pm10_0 unit shows as g/m >>> This is my entry in .tmpl >>> DUST PM10 ($unit.label.SDS011_PM10.strip()) >>> >>> >>> [image: NOAA Dust PM10.png] >>> >>> Any idea? >>> >> -- 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/83b98240-92d3-4caa-9a1d-fef0eba6390dn%40googlegroups.com.
[weewx-user] Re: NOAA report with dust sensor
Hi Gary, thanks. Yes, you are right. Got this in my skins.conf and it is even written in the explanation. Will change and report back. [CheetahGenerator] # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii' encoding = html_entities [[SummaryByMonth]] # Reports that summarize "by month" [[[NOAA_month]]] encoding = strict_ascii template = NOAA/NOAA-%Y-%m.txt.tmpl [[SummaryByYear]] # Reports that summarize "by year" [[[NOAA_year]]] encoding = strict_ascii template = NOAA/NOAA-%Y.txt.tmpl On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote: > Hi, > > What encoding are you using for the NOAA format reports in your skin.conf? > If you have the old encoding = strict_ascii then no you won’t see the mu > character, you should see it though if you have encoding = utf8. > > Gary > > On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com wrote: > >> Hi, I added my SDS011 data (which I read-in using file-pile) however the >> unit in the header is not shows as microgramm per cubic meter. I changed >> the unit in units.py to see if it also is adapted in the report and was >> working however using the default pm10_0 unit shows as g/m >> This is my entry in .tmpl >> DUST PM10 ($unit.label.SDS011_PM10.strip()) >> >> >> [image: NOAA Dust PM10.png] >> >> Any idea? >> > -- 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/4dcbfd7c-9fbd-4113-b806-59ed30376bf0n%40googlegroups.com.
[weewx-user] Re: NOAA report with dust sensor
Hi, What encoding are you using for the NOAA format reports in your skin.conf? If you have the old encoding = strict_ascii then no you won’t see the mu character, you should see it though if you have encoding = utf8. Gary On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com wrote: > Hi, I added my SDS011 data (which I read-in using file-pile) however the > unit in the header is not shows as microgramm per cubic meter. I changed > the unit in units.py to see if it also is adapted in the report and was > working however using the default pm10_0 unit shows as g/m > This is my entry in .tmpl > DUST PM10 ($unit.label.SDS011_PM10.strip()) > > > [image: NOAA Dust PM10.png] > > Any idea? > -- 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/4bbbe103-125f-4c02-9a6a-432cc583cf39n%40googlegroups.com.
[weewx-user] Re: NOAA report with dust sensor
Maybe good to mention that I added SDS011_PM10 for the dust concentration pm10_0. It is added in units.py and just works in my graphs and displays the unit correctly in all views (current, statistics..). [image: High low.png] On Wednesday, February 3, 2021 at 7:00:13 AM UTC+1 Calo Geyer wrote: > Hi, I added my SDS011 data (which I read-in using file-pile) however the > unit in the header is not shows as microgramm per cubic meter. I changed > the unit in units.py to see if it also is adapted in the report and was > working however using the default pm10_0 unit shows as g/m > This is my entry in .tmpl > DUST PM10 ($unit.label.SDS011_PM10.strip()) > > > [image: NOAA Dust PM10.png] > > Any idea? > -- 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/c7308d92-2fdc-4298-b59c-074ae821f05bn%40googlegroups.com.
[weewx-user] NOAA report with dust sensor
Hi, I added my SDS011 data (which I read-in using file-pile) however the unit in the header is not shows as microgramm per cubic meter. I changed the unit in units.py to see if it also is adapted in the report and was working however using the default pm10_0 unit shows as g/m This is my entry in .tmpl DUST PM10 ($unit.label.SDS011_PM10.strip()) [image: NOAA Dust PM10.png] Any idea? -- 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/5dc0bd7e-3376-4967-8a4f-31f39477a6f5n%40googlegroups.com.
[weewx-user] Re: Multiple stations on one host
weewx-multi works fine under WeeWX 4. I am am running a dual instance under raspberry Pi OS and have had no problems at all. Gary On Wednesday, 3 February 2021 at 06:27:55 UTC+10 michael.k...@gmx.at wrote: > I have the same question: is the script still valid with weewx4? > > When I try to run weewx-multi following the guide at > https://github.com/weewx/weewx/wiki/weewx-multi I get: > > Feb 02 21:25:22 raspberrypi3B systemd[1]: Starting LSB: weewx-multi... > -- Subject: A start job for unit weewx.service has begun execution > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit weewx.service has begun execution. > -- > -- The job identifier is 1362. > Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service: Failed to > execute command: No such file or directory > Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service: Failed at step > EXEC spawning /etc/init.d/weewx: No such file or directory > -- Subject: Process /etc/init.d/weewx could not be executed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- The process /etc/init.d/weewx could not be executed and failed. > -- > -- The error number returned by this process is ERRNO. > Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service: Control process > exited, code=exited, status=203/EXEC > -- Subject: Unit process exited > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- An ExecStart= process belonging to unit weewx.service has exited. > -- > -- The process' exit code is 'exited' and its exit status is 203. > Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service: Failed with > result 'exit-code'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- The unit weewx.service has entered the 'failed' state with result > 'exit-code'. > Feb 02 21:25:22 raspberrypi3B systemd[1]: Failed to start LSB: weewx-multi. > -- Subject: A start job for unit weewx.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit weewx.service has finished with a failure. > -- > -- The job identifier is 1362 and the job result is failed. > > > gert.a...@gmail.com schrieb am Mittwoch, 13. Mai 2020 um 10:50:24 UTC+2: > >> Hi >> Is this script still valid using Weewx 4? >> >> Basically , I want to have 3 WeeWx instances pointing to 3 different >> domains on 1 computer, each domain with different configuration. All 3 >> instances should read from the same mqtt subscription port and using >> Interceptor. Can all 3 Interceptor extensions listen to the same port or >> must Interceptor listen to a unique ports, say 8001, 8002 and 8003. >> >> I'll be using Belchertown and mqtt for all 3 domains. More or less the >> same question here with Mosquitto. Can I use the same ports(1883 for mqtt >> and 9001 for sockets) for all domains or should I setup different ports for >> each domain. >> >> Thanks >> Gert >> >> >> On Friday, January 6, 2017 at 2:17:16 AM UTC+1, mwall wrote: >>> >>> On Thursday, January 5, 2017 at 7:36:48 PM UTC-5, tomnykds wrote: Best I can tell, you can run only one weather station per weewx process instance, but is there any reason multiple instances can't be run on the same host from per-station directories (installs and configs of weewx)? To further complicate things, can all the archive data be hosted on a single MySQL process as long at the database names are unique? >>> >>> chris, >>> >>> just to be clear: you can run any number of weewx instances from a >>> single weewx installation on a single computer. each instance must have >>> its own config file, database, and reports directory (if the instance emits >>> any html/text/images). >>> >>> no need to modify the weewx-multi init script - just put the list of >>> instance names in /etc/default/weewx-multi >>> >>> m >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a08e542a-e318-41c6-9e50-234944c36525n%40googlegroups.com.
[weewx-user] Re: Multiple stations on one host
I have the same question: is the script still valid with weewx4? When I try to run weewx-multi following the guide at https://github.com/weewx/weewx/wiki/weewx-multi I get: Feb 02 21:25:22 raspberrypi3B systemd[1]: Starting LSB: weewx-multi... -- Subject: A start job for unit weewx.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit weewx.service has begun execution. -- -- The job identifier is 1362. Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service: Failed to execute command: No such file or directory Feb 02 21:25:22 raspberrypi3B systemd[3728]: weewx.service: Failed at step EXEC spawning /etc/init.d/weewx: No such file or directory -- Subject: Process /etc/init.d/weewx could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /etc/init.d/weewx could not be executed and failed. -- -- The error number returned by this process is ERRNO. Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service: Control process exited, code=exited, status=203/EXEC -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit weewx.service has exited. -- -- The process' exit code is 'exited' and its exit status is 203. Feb 02 21:25:22 raspberrypi3B systemd[1]: weewx.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit weewx.service has entered the 'failed' state with result 'exit-code'. Feb 02 21:25:22 raspberrypi3B systemd[1]: Failed to start LSB: weewx-multi. -- Subject: A start job for unit weewx.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit weewx.service has finished with a failure. -- -- The job identifier is 1362 and the job result is failed. gert.a...@gmail.com schrieb am Mittwoch, 13. Mai 2020 um 10:50:24 UTC+2: > Hi > Is this script still valid using Weewx 4? > > Basically , I want to have 3 WeeWx instances pointing to 3 different > domains on 1 computer, each domain with different configuration. All 3 > instances should read from the same mqtt subscription port and using > Interceptor. Can all 3 Interceptor extensions listen to the same port or > must Interceptor listen to a unique ports, say 8001, 8002 and 8003. > > I'll be using Belchertown and mqtt for all 3 domains. More or less the > same question here with Mosquitto. Can I use the same ports(1883 for mqtt > and 9001 for sockets) for all domains or should I setup different ports for > each domain. > > Thanks > Gert > > > On Friday, January 6, 2017 at 2:17:16 AM UTC+1, mwall wrote: >> >> On Thursday, January 5, 2017 at 7:36:48 PM UTC-5, tomnykds wrote: >>> >>> Best I can tell, you can run only one weather station per weewx process >>> instance, but is there any reason multiple instances can't be run on the >>> same host from per-station directories (installs and configs of weewx)? To >>> further complicate things, can all the archive data be hosted on a single >>> MySQL process as long at the database names are unique? >>> >> >> chris, >> >> just to be clear: you can run any number of weewx instances from a single >> weewx installation on a single computer. each instance must have its own >> config file, database, and reports directory (if the instance emits any >> html/text/images). >> >> no need to modify the weewx-multi init script - just put the list of >> instance names in /etc/default/weewx-multi >> >> m >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d0c9c931-596e-4b61-8eb9-8435819a467an%40googlegroups.com.
Re: [weewx-user] Re: missing data: MQTT -> weewx
Hi, now it's actually starting to get weird. Systemd-timesyncd is already active on all the devices involved. However, the settings in the configuration file were commented out everywhere. I now have the same settings everywhere. Now I just have to wait for rain and hope that everything is configured correctly and works. Many thanks to you for the tips Michael -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0ee5b558-56cd-4e9c-915e-af3e0b078942n%40googlegroups.com.
[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent
I looked at it again, and I think, I found something.
This is a list of the archive records, and whether the MQTT data are
included or not:
15:15:14 included
15:10 missing
15:05:16 included
15:00:14 included
14:55 missing
14:50:16 included
15:45:14 included
15:40 missing
14:35:16 included
14:30:14 included
14:25 missing
14:20:16 included
14:15:14 included
14:10 missing
14:05:16 included
14:00:16 included
13:55 missing
13:50:16 included
13:45:16 included
13:40 missing
13:35:16 included
The MQTT message is published within the minute after a full quarter of the
hour.
So maybe, it is cached for 10 minutes, only, irrespective of the setting.
Does that make sense to you?
Karen K schrieb am Montag, 1. Februar 2021 um 21:42:33 UTC+1:
> I looked for all messages that contain self.cached_fields.
>
> /var/log/syslog.2.gz:Jan 30 16:51:45 LokalWiki weewx[1003818] DEBUG
> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {}
> /var/log/syslog.2.gz:Jan 30 17:07:40 LokalWiki weewx[1004756] DEBUG
> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {}
> /var/log/syslog.2.gz:Jan 30 17:32:18 LokalWiki weewx[1005876] DEBUG
> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {}
> /var/log/syslog:Feb 1 21:15:42 LokalWiki weewx[1121713] DEBUG
> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is
> {'pegel/566055/W_cm': {'expires_after': 4000.0}, 'pegel/566055/Q':
> {'expires_after': 4000.0}, 'pegel/567470/W_cm': {'expires_after': 4000.0},
> 'pegel/567470/Q': {'expires_after': 4000.0}}
>
> I guess the only difference in configuration is setting that
> use_topic_as_fieldname option.
>
> Much more occurences are for archive_field_cache_dict is None:
>
> /var/log/syslog:Feb 1 17:11:37 LokalWiki weewx[752] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog:Feb 1 17:57:17 LokalWiki weewx[1113838] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog:Feb 1 21:15:42 LokalWiki weewx[1121713] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.1:Jan 31 18:51:39 LokalWiki weewx[1062223] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 11:41:20 LokalWiki weewx[991980] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 16:22:32 LokalWiki weewx[1002371] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 16:37:01 LokalWiki weewx[1002967] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 16:48:04 LokalWiki weewx[1003591] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 16:51:45 LokalWiki weewx[1003818] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 16:52:35 LokalWiki weewx[1003948] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 16:56:06 LokalWiki weewx[1004173] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 17:01:36 LokalWiki weewx[1004468] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 17:07:40 LokalWiki weewx[1004756] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 17:09:27 LokalWiki weewx[1004999] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 17:32:18 LokalWiki weewx[1005876] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.2.gz:Jan 30 17:32:58 LokalWiki weewx[1005993] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.4.gz:Jan 28 18:25:57 LokalWiki weewx[900457] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.4.gz:Jan 28 18:45:57 LokalWiki weewx[901356] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.4.gz:Jan 28 20:52:33 LokalWiki weewx[906158] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.4.gz:Jan 28 20:53:26 LokalWiki weewx[906292] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.4.gz:Jan 28 21:10:49 LokalWiki weewx[907158] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.6.gz:Jan 26 18:09:00 LokalWiki weewx[781417] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.7.gz:Jan 25 20:14:15 LokalWiki weewx[731916] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is None
> /var/log/syslog.7.gz:Jan 25 20:28:52 LokalWiki weewx[732569] INFO
> user.MQTTSubscribe: (Service) archive_field_cache_dict is No
[weewx-user] Re: MQTT - Min/Max values ?
Just bouncing my own message - if anyone has any hints on how to add Max/Min values to the MQTT output that would be great Andy On Tuesday, 3 March 2020 at 16:48:18 UTC andyhud...@googlemail.com wrote: > Just wondering if its possible to add Min/Max tags for the day to topics - > so Min / Max temperature etc. > > > It would mean i could use MQTT for all my outputs, rather than just the > current live ones.. i have had a look and cant work out if its possible, > > > Hope thats ok to ask, > > > Andy > -- 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/03f6dde5-95b0-4063-b5ea-cd598cd052b2n%40googlegroups.com.
[weewx-user] Display earthquakes using RENASS network
Hi
Today in Belchertown skin, we can display USGS and GEONET earthquakes.
I would like to add RENASS network.
Renass can be reached by a url and gives a json answer, exemple:
https://renass.unistra.fr/fdsnws/event/1/query?latitude=46.6&longitude=1.9&maxradius=9&minmagnitude=1&orderby=time&starttime=2021-01-18&format=json
and result is :
{ "bbox": [ -3.621, 41.399, 9.87, 49.682 ], "features": [ { "geometry": {
"coordinates": [ 6.953, 44.888, -10 ], "type": "Point" }, "id":
"6018e3eb6dc5b1490661b451", "properties": { "description": "S\u00e9isme de
magnitude 1.3 \u00e0 31km de Pinerolo", "evaluationMode": "manual", "mag":
1.3, "magType": "MLv", "place": "FRANCE", "time":
"2021-02-02T05:30:08.834000Z", "type": "earthquake", "url":
"https://renass.unistra.fr/evenements/6018e3eb6dc5b1490661b451"; }, "type":
"Feature" }, { "geometry": { "coordinates": [ 4.436, 47.195, 0 ], "type":
"Point" }, "id": "6018079d2d270784e6057f05",
...
As I am not a strong programmer, is somebody can add this option?
Many thanks for your help
Didier
--
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/8df4c98b-8053-4887-8342-43c44e29567an%40googlegroups.com.
Re: [weewx-user] Belchertown AQI error from Aeris weather
Hi
I had this problem, closest parameter does not work...
You can change by
https://api.aerisapi.com/airquality/55.008637,14.960125?&format=json&radius=50mi&limit=1&client_id=..
..
Conversation
https://groups.google.com/g/weewx-user/c/9BNEC_103wY/m/FOxwW_IYBwAJ already
open but no reply
Didier
Le mar. 2 févr. 2021 à 09:49, gert.a...@gmail.com
a écrit :
> Hi
>
> Anyone who knows how to get rid of this error:
>
> ERROR user.belchertown: Error getting AQI from Aeris weather. The error
> was:#012list index out of range#012The response from the Aeris AQI server
> was:#012[{'success': True, 'error': {'code': 'warn_no_data',
> 'description': 'Valid request.
> No results available based on your query parameters.'}, 'response':
> []}]#012
> The URL being used is:#012
> https://api.aerisapi.com/airquality/closest?p=55.008637,14.960125&format=json&radius=50mi&limit=1&client_id=
> &client_secret=
>
> message repeated 10 times: [ ERROR user.belchertown: Error getting AQI
> from Aeris weather.
> The error was:#012list index out of range#012The response from the Aeris
> AQI server was:#012[{'success': True, 'error': {'code': 'warn_no_data',
> 'description': 'Valid request.
> No results available based on your query parameters.'}, 'response':
> []}]#012The URL being used is:#012
> https://api.aerisapi.com/airquality/closest?p=55.008637,14.960125&format=json&radius=50mi&limit=1&client_id=
> &client_secret=]
>
> I have this in weewx.conf:
> # Air Quality
> aqi_enabled = 0
> aqi_location_enabled = 0
>
> I'm running weewx 4.4.0 and the latest version of Belchertown
>
> Thanks
>
> Rgds
> Gert
>
> --
> 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/c08cd1bb-5aea-41da-a3bd-4c4b54dbf245n%40googlegroups.com
>
> .
>
--
Quel temps fait-il à Auffargis ?
--
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/CAAvt3%3DSfMekWf_2T0hLyVX%2BVezyM3ZJE%3DcHfVJG4jEsFFOQqfg%40mail.gmail.com.
[weewx-user] Belchertown AQI error from Aeris weather
Hi
Anyone who knows how to get rid of this error:
ERROR user.belchertown: Error getting AQI from Aeris weather. The error
was:#012list index out of range#012The response from the Aeris AQI server
was:#012[{'success': True, 'error': {'code': 'warn_no_data', 'description':
'Valid request.
No results available based on your query parameters.'}, 'response': []}]#012
The URL being used
is:#012https://api.aerisapi.com/airquality/closest?p=55.008637,14.960125&format=json&radius=50mi&limit=1&client_id=&client_secret=
message repeated 10 times: [ ERROR user.belchertown: Error getting AQI from
Aeris weather.
The error was:#012list index out of range#012The response from the Aeris
AQI server was:#012[{'success': True, 'error': {'code': 'warn_no_data',
'description': 'Valid request.
No results available based on your query parameters.'}, 'response':
[]}]#012The URL being used
is:#012https://api.aerisapi.com/airquality/closest?p=55.008637,14.960125&format=json&radius=50mi&limit=1&client_id=&client_secret=]
I have this in weewx.conf:
# Air Quality
aqi_enabled = 0
aqi_location_enabled = 0
I'm running weewx 4.4.0 and the latest version of Belchertown
Thanks
Rgds
Gert
--
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/c08cd1bb-5aea-41da-a3bd-4c4b54dbf245n%40googlegroups.com.
