Re: [weewx-user] Re: Lightning Strike issues

[gjr80]

The reason you are seeing such large lightning strike numbers reported by 
WeeWX is that your station reports a cumulative lightning strike count, but 
WeeWX requires a per-period count. As posted earlier, the solution is to 
tell the SDR driver the lightning_strike_count field is a delta that is 
derived from the cumulative strike count. This is done via the highlighted 
lines below that were included in the earlier post:

[SDR]
[[sensors_map]]
strike_total = strike_count.494.AcuriteAtlasPacket
lightning_distance = strike_distance.494.AcuriteAtlasPacket
[[deltas]]
lightning_strike_count = strike_total

Have you included similar lines? Did you restart WeeWX after making the 
changes? Also note that unless you deleted the old cumulative data from 
WeeWX it will likely take an hour for the effects of any old cumulative 
data to disappear from last hour total.

Gary
On Saturday, 17 September 2022 at 08:10:54 UTC+10 dave.sp...@gmail.com 
wrote:

> My acurite sensor is reporting correct lightning data. In the loop data I 
> see 'lightning_distance': 7, 'lightning_strike_count': 296, but on the web 
> page it is saying that strikes are 9768 and the hourly total of approx. 
> 28+. How do I get it to where it shows that current data instead of 
> erroneous values?
>
>  
>
>  
>
>  
>
> I would except to see strikes by at 7
>
>  
>
> Also how do I get a graft to see the distance? I am running the default 
> seasons 4.8.0 skin
>
>  
>
> Thanks
>
> Dave
>
>  
>
> *From:* weewx...@googlegroups.com  *On Behalf 
> Of *vince
> *Sent:* Friday, September 16, 2022 12:53 PM
> *To:* weewx-user 
> *Subject:* [weewx-user] Re: Lightning Strike issues
>
>  
>
> "Is not correct" isn't much to go on. What are you expecting to see ?
>
>  
>
> See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem
>
>  
>
> I don't know about your station in particular, but WeatherFlow stations 
> frequently can show thousands of bogus lightning strikes due to the 
> inexpensive sensor that vendor uses.  Fix there is to rotate the sensor 90 
> degrees which amazingly does work in quieting down erroneous strike 
> readings.  Acurite has a web page on your station at 
> https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning
>  
> if that helps any.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/07aa5e30-cafe-456c-a4a7-3dcb55fa460bn%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/8ddac774-6eab-4bad-820b-46341af2bd35n%40googlegroups.com.

Re: [weewx-user] Re: Weewx and API Integration

[gjr80]

I do not recommend editing the Seasons skin about.inc and replacing the 
$station.hardware tag with whatever text you chose. At best you are 
papering over the cracks, at worst it will be misleading. The 
$station.hardware tag is taken from the hardware_name property of the 
driver being used by WeeWX. In this case if 'Simulator' is being displayed 
that will be because WeeWX is currently using the simulator driver. Doesn't 
matter how many driver stanzas are included in weewx.conf, or what station 
type is selected in weewx.conf; $station.hardware will display the 
hardware_name property for the driver used by the WeeWX instance doing the 
reporting.

After you changed to the interceptor driver did you restart WeeWX? If not 
you need to. If you did what does the WeeWX log say? Details of the driver 
being used by WeeWX is logged during WeeWX startup. Certainly the nonsense 
values you are seeing, such as 0.1C, is indicative of WeeWX using the 
simulator driver rather than the interceptor. The answers will be in the 
log.

Gary
On Saturday, 17 September 2022 at 00:39:24 UTC+10 
sebastian...@googlemail.com wrote:

>
> Sorry for the questions but I don't see the error. I made the following 
> entries in weewx.con, see attachment
> [image: Screenshot 2022-09-16 163527.png]
>
> lang@googlemail.com schrieb am Freitag, 16. September 2022 um 
> 16:28:04 UTC+2:
>
>> That's what I call a "beauty" thing.
>> Look up your parallel post in wxforum.net
>> There you will find a solution of how to replace your "Simulator" entry 
>> by one of your choice
>> Am 16.09.2022 um 15:01 schrieb 'Sebastian Eckelmann' via weewx-user:
>>
>> Another thing that struck me was Hardware Simulator under "about this 
>> station". Even though I installed the interceptor driver. Sorry for the 
>> questions[image: Screenshot 2022-09-16 150006.png]
>>
>> ton...@gmail.com schrieb am Freitag, 16. September 2022 um 09:13:11 
>> UTC+2:
>>
>>> Can the 'faulty' values be traced back to values in the input-files from 
>>> either WU, or from AWEKAS?
>>> If that is the case, it looks like a doubtful data source. 
>>> If no link visible, (*perhaps open door*) have a look in completely 
>>> different direction:
>>> did you properly set the type of PWS (*not* to Simulator)?
>>> Op 15-9-2022 om 21:16 schreef 'Sebastian Eckelmann' via weewx-user:
>>>
>>> Hi, thanks for your help. I am now using the Inceptor driver. Data is 
>>> also retrieved from WU. Under Current Conditions it says Outside Temp: 0.1 C
>>> Inside Temp 17.2 C. Outside 12.9 and Inside 24.1 would be correct.[image: 
>>> Screenshot 2022-09-15 211058.png]
>>>
>>> ton...@gmail.com schrieb am Donnerstag, 15. September 2022 um 20:18:43 
>>> UTC+2:
>>>
 Please describe what you mean with 

 > unfortunately the data is displayed incorrectly 
 Is scaling fitting the units listed in the API-description? 
 Be aware that 
 epoch-times are related to a specific timezone, with an offset relative 
 to UTC as given under 'timeoffset'. 

 Anton 

 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/85690017-9dc7-49f3-a54d-0021288c6186n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> -- 
>>>
>>> ===
>>> Contactinfo voor Anton van Nieuwenhuijzen:
>>> Email= ton...@gmail.com
>>> Fax2Mail = (+31/0)84.8397303 <+31%2084%20839%207303> [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+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/91e8bcbd-71d4-489d-8d87-6e4172a1625bn%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 

Re: [weewx-user] FTP upload Problem

[Steve2Q]

Peter..you are very welcome. I hope I saved you saved some time and 
aggrevation. 

On Friday, September 16, 2022 at 3:58:52 AM UTC-4 PeterGill wrote:

> Steve, it turned out you were right, the problem was at my provider side. 
> Problem solved. Thanks for engaging!
>
> On Thursday, September 15, 2022 at 9:56:04 PM UTC+2 PeterGill wrote:
>
>> Thanks Steve, I´m talking to my provider right now and I´ll update here 
>> if the problem is with them
>>
>>
>> On Thursday, September 15, 2022 at 7:11:29 PM UTC+2 Steve2Q wrote:
>>
>>> Peter..I had the exact same problem with DreamHost. For some reason they 
>>> blocked my IP. They unblocked it yesterday afternoon, and FTP started 
>>> working a few hours later.
>>>
>>>
>>> On Thursday, September 15, 2022 at 9:58:56 AM UTC-4 PeterGill wrote:
>>>
 Thanks for the quick answer. Sorry for a stupid follow up question - 
 how do I make sure the right access permissions are set?


 On Thursday, September 15, 2022 at 3:52:21 PM UTC+2 tke...@gmail.com 
 wrote:

> I don't know why it would have changed, but make sure you have access 
> permissions to whatever directory you are trying to upload to. 
>
> On Thu, Sep 15, 2022 at 6:39 AM PeterGill  wrote:
>
>> Hi,
>>
>> Suddenly and out of the blue my ftp upload stopped working. The html 
>> files are generated as expected in /var/www/html/weewx and the file 
>> "celestial.html" referenced in the log extract below certainly exist in 
>> the 
>> library and opens correctly in Chrome.
>>
>> Of course reboot has been tried.
>>
>> Any help would be highly appreciated!
>>
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weeutil.ftpupload: Failed 
>> uploading /var/www/html/weewx/celestial.html to server ftp.myurl.se. 
>> Reason: '550 Requested action not taken. File unavailable (e.g., file 
>> not 
>> found, no access).'
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine: 
>> ftpgenerator: (2): caught exception '': 550 
>> Requested action not taken. File unavailable (e.g., file not found, no 
>> access).
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     n = ftp_data.run()
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/ftpupload.py", line 178, in run
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     ftp_server.storbinary(stor_cmd, fd)
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/lib/python3.7/ftplib.py", line 504, in storbinary
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     with self.transfercmd(cmd, rest) as conn:
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/lib/python3.7/ftplib.py", line 399, in transfercmd
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     return self.ntransfercmd(cmd, rest)[0]
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/lib/python3.7/ftplib.py", line 365, in ntransfercmd
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     resp = self.sendcmd(cmd)
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/lib/python3.7/ftplib.py", line 273, in sendcmd
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     return self.getresp()
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>   File "/usr/lib/python3.7/ftplib.py", line 246, in getresp
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     raise error_perm(resp)
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>>     ftplib.error_perm: 550 Requested action not taken. File 
>> unavailable 
>> (e.g., file not found, no access).
>> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine: 
>> ftpgenerator: Upload failed
>> Sep 15 14:46:14 Homeserver weewx[573] DEBUG weewx.reportengine: 
>> Report 'RSYNC' not enabled. Skipping.
>> Sep 15 14:46:16 Homeserver weewx[573] DEBUG user.MQTTSubscribe: 
>> (Service) MessageCallbackProvider data-> incoming topic: 
>> Jettystation/Watertemp, QOS: 0, retain: 0, payload: b'14.50'
>> Sep 15 14:46:16 Homeserver weewx[573] DEBUG user.MQTTSubscribe: 
>> (Service) 

Re: [weewx-user] Re: Lightning Strike issues

[an oldman]

the graph have to add to skin.conf this is what i added

[DisplayOptions]

# Some observations display a sum rather than min/max values
obs_type_sum = rain, ET, lightning_strike_count
# This list determines which plots will be shown, as well as the order 
in
# which they will be displayed.  The names refer to the plots defined in
# the ImageGenerator section, without any time span prefix.  For 
example,
# the name 'wind' refers to 'daywind', 'weekwind', 'monthwind', and
# 'yearwind'.
plot_groups = lightning

[ImageGenerator]
[[[daylightning]]]
yscale = None, None, 1
plot_type = bar
lightning_strike_count
aggregate_type = sum
aggregate_interval = hour
label = Lightning Strike (hourly total)
On Friday, September 16, 2022 at 5:10:54 PM UTC-5 dave.sp...@gmail.com 
wrote:

> My acurite sensor is reporting correct lightning data. In the loop data I 
> see 'lightning_distance': 7, 'lightning_strike_count': 296, but on the web 
> page it is saying that strikes are 9768 and the hourly total of approx. 
> 28+. How do I get it to where it shows that current data instead of 
> erroneous values?
>
>  
>
>  
>
>  
>
> I would except to see strikes by at 7
>
>  
>
> Also how do I get a graft to see the distance? I am running the default 
> seasons 4.8.0 skin
>
>  
>
> Thanks
>
> Dave
>
>  
>
> *From:* weewx...@googlegroups.com  *On Behalf 
> Of *vince
> *Sent:* Friday, September 16, 2022 12:53 PM
> *To:* weewx-user 
> *Subject:* [weewx-user] Re: Lightning Strike issues
>
>  
>
> "Is not correct" isn't much to go on. What are you expecting to see ?
>
>  
>
> See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem
>
>  
>
> I don't know about your station in particular, but WeatherFlow stations 
> frequently can show thousands of bogus lightning strikes due to the 
> inexpensive sensor that vendor uses.  Fix there is to rotate the sensor 90 
> degrees which amazingly does work in quieting down erroneous strike 
> readings.  Acurite has a web page on your station at 
> https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning
>  
> if that helps any.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/07aa5e30-cafe-456c-a4a7-3dcb55fa460bn%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/15887031-5ff7-4235-a46d-d0cbd44bb7dbn%40googlegroups.com.

RE: [weewx-user] Re: Lightning Strike issues

[dave.spicer2012]

My acurite sensor is reporting correct lightning data. In the loop data I see 
'lightning_distance': 7, 'lightning_strike_count': 296, but on the web page it 
is saying that strikes are 9768 and the hourly total of approx. 28+. How do 
I get it to where it shows that current data instead of erroneous values?

 

 



 

I would except to see strikes by at 7

 

Also how do I get a graft to see the distance? I am running the default seasons 
4.8.0 skin

 

Thanks

Dave

 

From: weewx-user@googlegroups.com  On Behalf Of 
vince
Sent: Friday, September 16, 2022 12:53 PM
To: weewx-user 
Subject: [weewx-user] Re: Lightning Strike issues

 

"Is not correct" isn't much to go on. What are you expecting to see ?

 

See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

 

I don't know about your station in particular, but WeatherFlow stations 
frequently can show thousands of bogus lightning strikes due to the inexpensive 
sensor that vendor uses.  Fix there is to rotate the sensor 90 degrees which 
amazingly does work in quieting down erroneous strike readings.  Acurite has a 
web page on your station at 
https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning
 if that helps any.

-- 
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/07aa5e30-cafe-456c-a4a7-3dcb55fa460bn%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/028201d8ca19%242def72d0%2489ce5870%24%40gmail.com.

[weewx-user] Re: Lightning Strike issues

[an oldman]

the atlas and lightning sensors have a running count for strikes
i have a atlas and lightning sensor and i use this in weewx.conf
under sdr in sensor map
[SDR]
[[sensors_map]]
strike_total = strike_count.494.AcuriteAtlasPacket
lightning_distance = strike_distance.494.AcuriteAtlasPacket
[[deltas]]
lightning_strike_count = strike_total

then add accumulators section to weewx.conf
[Accumulator]
[[lightning_distance]]
extractor = last

then in stdcalibrate
[StdCalibrate]
[[Corrections]]
lightning_distance = lightning_distance if lightning_strike_count > 
0 else None
hope this helps
On Friday, September 16, 2022 at 1:53:23 PM UTC-5 vince wrote:

> "Is not correct" isn't much to go on. What are you expecting to see ?
>
> See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem
>
> I don't know about your station in particular, but WeatherFlow stations 
> frequently can show thousands of bogus lightning strikes due to the 
> inexpensive sensor that vendor uses.  Fix there is to rotate the sensor 90 
> degrees which amazingly does work in quieting down erroneous strike 
> readings.  Acurite has a web page on your station at 
> https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning
>  
> if that helps any.
>

-- 
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/20b16255-1a64-45f3-9d06-edf628a7dd3fn%40googlegroups.com.

[weewx-user] Re: Lightning Strike issues

[vince]

"Is not correct" isn't much to go on. What are you expecting to see ?

See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

I don't know about your station in particular, but WeatherFlow stations 
frequently can show thousands of bogus lightning strikes due to the 
inexpensive sensor that vendor uses.  Fix there is to rotate the sensor 90 
degrees which amazingly does work in quieting down erroneous strike 
readings.  Acurite has a web page on your station 
at 
https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning
 
if that helps any.

-- 
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/07aa5e30-cafe-456c-a4a7-3dcb55fa460bn%40googlegroups.com.

[weewx-user] Lightning Strike issues

[dave.spicer2012]

Good morning all, I am having a small issue with the lightning strikes. I
have an Acurite 7-n-1 sensors. On the weewx web page the lightning strikes
are not correct. Here is what the web page is showing:

 



 

 



 

 

When I tail the logs, here is just the part on lightning:
'lightning_distance': 7, 'lightning_strike_count': 296

 

Weewx.conf:

 

[SDR]

# This section is for the software-defined radio driver.

 

# The driver to use

driver = user.sdr

log_unknown_sensors = True

log_unmapped_sensors = True

cmd = sudo rtl_433 -M utc -F json

 

[[sensor_map]]

outTemp = temperature.0010.AcuriteAtlasPacket

outHumidity = humidity.0010.AcuriteAtlasPacket

windSpeed = wind_speed.0010.AcuriteAtlasPacket

windDir = wind_dir.0010.AcuriteAtlasPacket

UV = uv.0010.AcuriteAtlasPacket

rain_total = rain_total.0010.AcuriteAtlasPacket

radiation = lux.0010.AcuriteAtlasPacket

outTempBatteryStatus = battery.0010.AcuriteAtlasPacket

lightning_distance = strike_distance.0010.AcuriteAtlasPacket

lightning_strike_count = strike_count.0010.AcuriteAtlasPacket

luminosity = lux.0010.AcuriteAtlasPacket

 

[[deltas]]

rain = rain_total

 

 

Hardware:

Weewx version 4.8.0

Running SDR

 

Any help in getting the lightning info would be great.

Thanks

Dave

-- 
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/022e01d8c9f2%2409b11b20%241d135160%24%40gmail.com.

Re: [weewx-user] Re: Weewx and API Integration

['Rainer Lang' via weewx-user]

That's what I call a "beauty" thing.
Look up your parallel post in wxforum.net
There you will find a solution of how to replace your "Simulator" entry 
by one of your choice


Am 16.09.2022 um 15:01 schrieb 'Sebastian Eckelmann' via weewx-user:
Another thing that struck me was Hardware Simulator under "about this 
station". Even though I installed the interceptor driver. Sorry for 
the questionsScreenshot 2022-09-16 150006.png


ton...@gmail.com schrieb am Freitag, 16. September 2022 um 09:13:11 UTC+2:

Can the 'faulty' values be traced back to values in the
input-files from either WU, or from AWEKAS?
If that is the case, it looks like a doubtful data source.
If no link visible, (/perhaps open door/) have a look in
completely different direction:
did you properly set the type of PWS (_not_ to Simulator)?

Op 15-9-2022 om 21:16 schreef 'Sebastian Eckelmann' via weewx-user:

Hi, thanks for your help. I am now using the Inceptor driver.
Data is also retrieved from WU. Under Current Conditions it says
Outside Temp: 0.1 C
Inside Temp 17.2 C. Outside 12.9 and Inside 24.1 would be
correct.Screenshot 2022-09-15 211058.png

ton...@gmail.com schrieb am Donnerstag, 15. September 2022 um
20:18:43 UTC+2:

Please describe what you mean with

> unfortunately the data is displayed incorrectly
Is scaling fitting the units listed in the API-description?
Be aware that
epoch-times are related to a specific timezone, with an
offset relative
to UTC as given under 'timeoffset'.

Anton

-- 
You received this message because you are subscribed to the

Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/85690017-9dc7-49f3-a54d-0021288c6186n%40googlegroups.com

.


-- 


===
Contactinfo voor Anton van Nieuwenhuijzen:
Email=ton...@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/91e8bcbd-71d4-489d-8d87-6e4172a1625bn%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/6c8d9027-cd88-36d5-065a-6b605f26cd8c%40gmail.com.

Re: [weewx-user] Bresser 7 in 1

[Andrey Mihaylov]

Hello,

SDR is a good option I've used since last year.

matthewwall/weewx-sdr: weewx driver for software-defined radio (github.com)


regards,
AM.

На пн, 12.09.2022 г. в 19:30 ч. 'Sebastian Eckelmann' via weewx-user <
weewx-user@googlegroups.com> написа:

> Hello everyone, I use the station bresser 7 in 1 ClearView 7002586. Is
> there a way to connect it to Weewx? Many Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/10e9f96a-075b-4005-ab28-1d386d6e99f5n%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/CAObD2BT1RH58uD55hyn8Eia0jVA0RqaW7wJzPytywuzuG%2Bdn-Q%40mail.gmail.com.

Re: [weewx-user] FTP upload Problem

[PeterGill]

Steve, it turned out you were right, the problem was at my provider side. 
Problem solved. Thanks for engaging!

On Thursday, September 15, 2022 at 9:56:04 PM UTC+2 PeterGill wrote:

> Thanks Steve, I´m talking to my provider right now and I´ll update here if 
> the problem is with them
>
>
> On Thursday, September 15, 2022 at 7:11:29 PM UTC+2 Steve2Q wrote:
>
>> Peter..I had the exact same problem with DreamHost. For some reason they 
>> blocked my IP. They unblocked it yesterday afternoon, and FTP started 
>> working a few hours later.
>>
>>
>> On Thursday, September 15, 2022 at 9:58:56 AM UTC-4 PeterGill wrote:
>>
>>> Thanks for the quick answer. Sorry for a stupid follow up question - how 
>>> do I make sure the right access permissions are set?
>>>
>>>
>>> On Thursday, September 15, 2022 at 3:52:21 PM UTC+2 tke...@gmail.com 
>>> wrote:
>>>
 I don't know why it would have changed, but make sure you have access 
 permissions to whatever directory you are trying to upload to. 

 On Thu, Sep 15, 2022 at 6:39 AM PeterGill  wrote:

> Hi,
>
> Suddenly and out of the blue my ftp upload stopped working. The html 
> files are generated as expected in /var/www/html/weewx and the file 
> "celestial.html" referenced in the log extract below certainly exist in 
> the 
> library and opens correctly in Chrome.
>
> Of course reboot has been tried.
>
> Any help would be highly appreciated!
>
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weeutil.ftpupload: Failed 
> uploading /var/www/html/weewx/celestial.html to server ftp.myurl.se. 
> Reason: '550 Requested action not taken. File unavailable (e.g., file not 
> found, no access).'
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine: 
> ftpgenerator: (2): caught exception '': 550 
> Requested action not taken. File unavailable (e.g., file not found, no 
> access).
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     Traceback (most recent call last):
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     n = ftp_data.run()
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weeutil/ftpupload.py", line 178, in run
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     ftp_server.storbinary(stor_cmd, fd)
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/lib/python3.7/ftplib.py", line 504, in storbinary
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     with self.transfercmd(cmd, rest) as conn:
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/lib/python3.7/ftplib.py", line 399, in transfercmd
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     return self.ntransfercmd(cmd, rest)[0]
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/lib/python3.7/ftplib.py", line 365, in ntransfercmd
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     resp = self.sendcmd(cmd)
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/lib/python3.7/ftplib.py", line 273, in sendcmd
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     return self.getresp()
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>   File "/usr/lib/python3.7/ftplib.py", line 246, in getresp
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     raise error_perm(resp)
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine:   
>     ftplib.error_perm: 550 Requested action not taken. File 
> unavailable 
> (e.g., file not found, no access).
> Sep 15 14:46:14 Homeserver weewx[573] ERROR weewx.reportengine: 
> ftpgenerator: Upload failed
> Sep 15 14:46:14 Homeserver weewx[573] DEBUG weewx.reportengine: Report 
> 'RSYNC' not enabled. Skipping.
> Sep 15 14:46:16 Homeserver weewx[573] DEBUG user.MQTTSubscribe: 
> (Service) MessageCallbackProvider data-> incoming topic: 
> Jettystation/Watertemp, QOS: 0, retain: 0, payload: b'14.50'
> Sep 15 14:46:16 Homeserver weewx[573] DEBUG user.MQTTSubscribe: 
> (Service) TopicManager data-> incoming Jettystation/Watertemp: 
> extraTemp1: 
> 14.5
>
>
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and 

Re: [weewx-user] Re: Weewx and API Integration

[Anton vanNwnhzn@GMail]

Can the 'faulty' values be traced back to values in the input-files from 
either WU, or from AWEKAS?

If that is the case, it looks like a doubtful data source.
If no link visible, (/perhaps open door/) have a look in completely 
different direction:

did you properly set the type of PWS (_not_ to Simulator)?

Op 15-9-2022 om 21:16 schreef 'Sebastian Eckelmann' via weewx-user:
Hi, thanks for your help. I am now using the Inceptor driver. Data is 
also retrieved from WU. Under Current Conditions it says Outside Temp: 
0.1 C
Inside Temp 17.2 C. Outside 12.9 and Inside 24.1 would be 
correct.Screenshot 2022-09-15 211058.png


ton...@gmail.com schrieb am Donnerstag, 15. September 2022 um 20:18:43 
UTC+2:


Please describe what you mean with

> unfortunately the data is displayed incorrectly
Is scaling fitting the units listed in the API-description?
Be aware that
epoch-times are related to a specific timezone, with an offset
relative
to UTC as given under 'timeoffset'.

Anton

--
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/85690017-9dc7-49f3-a54d-0021288c6186n%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/23d29ef9-7877-fff8-95f9-c1375218708c%40gmail.com.