Re: [weewx-user] Re: weewx crashes with error: unpack requires a string of len 104

[Graham Seward]

Thanks Susan
I just set up weewx on an older RPI and that seems to be working fine, though 
still on delay of 15.
I was wondering about the wlan and ip6 messages, thanks for giving me the 
solution. I had assumed it was to do with weewx.
Cheers
Graham

Get Outlook for Android


From: weewx-user@googlegroups.com  on behalf of 
vk3...@gmail.com 
Sent: Thursday, April 12, 2018 4:41:41 AM
To: weewx-user
Subject: [weewx-user] Re: weewx crashes with error: unpack requires a string of 
len 104

Hello Graham,

I've not been able to come up with anything so far but I'm still looking at 
this. It is a real puzzle because there should be log file entries from WeeWx 
if my code was exiting or encountering a fault etc.. Instead there is nothing 
in the log file.

I'm still looking into this

By the way, I noticed a number of messages in your syslog file from wlan0 about 
router advertisements and soliciting an DCHPV6 lease. I used to get a number of 
those as well and I found that it was my system running its own DHCP server 
(dhcpd) on that interface as well as the main DHCP server in my router. I 
stopped the dhcpd service on the system and those all went away. Not what you 
were after but might help in other areas anyway.

Susan

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx crashes with error: unpack requires a string of len 104

[vk3anz]

Hello Graham,

I've not been able to come up with anything so far but I'm still looking at 
this. It is a real puzzle because there should be log file entries from 
WeeWx if my code was exiting or encountering a fault etc.. Instead there is 
nothing in the log file.

I'm still looking into this

By the way, I noticed a number of messages in your syslog file from wlan0 
about router advertisements and soliciting an DCHPV6 lease. I used to get a 
number of those as well and I found that it was my system running its own 
DHCP server (dhcpd) on that interface as well as the main DHCP server in my 
router. I stopped the dhcpd service on the system and those all went away. 
Not what you were after but might help in other areas anyway.

Susan

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

*IT WORKS!*

I added: TIME = dateTime to wxMesh stanza of weewx.conf the stopped and 
restarted WeeWx - waited a few minutes and I now have values showing up in 
/var/www/html/weewx/index.html

Thanks a lot for all of the help!

Now that I have something working I can start experimenting with other 
sensors.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Bill Morrow]

On Wednesday, 11 April 2018 20:56:39 UTC-3, vince wrote:
>
> On Wednesday, April 11, 2018 at 11:54:47 AM UTC-7, Ralph Underwood wrote:
>>
>> Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?
>>
>>
>>
> Thinking not - I think you need:
>
>1. a "SOMETHING = dateTime" mapping in your weewx.conf file so the 
>driver knows what element is secs since the time epoch
>2. a  "SOMETHING: nnn"  key/value pair in your MQTT payload, where nnn 
>= secs_since_the_epoch (or 0 if you want to use the weewx computer 
> dateTime)
>
> Maybe you're just missing the TIME mapping in your weewx.conf label map.
>
> Can you provide:
>
>- your [wxMesh] stanza from weewx.conf
>- an example of the MQTT payload you're sending
>
>
> Ah, Vince may be on to something. This is my weewx.comf, Ralph. Note the 
TIME = dateTime mapping
 
[wxMesh]
driver = user.wxMesh

# MQTT specifics
host = localhost   # MQTT broker hostname
client = *redacted*
username = *redacted*
password = *redacted*
topic = weather  # topic is all weather (indoor and outdoor, 
e.g.)


poll_interval = 10

[[label_map]]
TIME = dateTime
HUMT = outTemp
RHUM = outHumidity
INTE = inTemp
INHU = inHumidity
BARP = barometer
IRRA = radiation
PHOV = supplyVoltage
BATV = consBatteryVoltage
AMBT = extraTemp1
SYST = extraTemp2
WDIR = windDir
WIND = windSpeed





>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Manually adding historical data to weewx database

[Andrew Milner]

if you can massage the data into a suitable format you can always use 
wee_import

http://weewx.com/docs/utilities.htm#wee_import_utility



On Wednesday, 11 April 2018 20:58:21 UTC+3, David Hindley wrote:

> The data has been downloaded to a text file from the WeatherLink software, 
> stores in a txt file on my Windows PC. 
>
> David. 
>
> On Wed, 11 Apr 2018 at 18:05, Andrew Milner  > wrote:
>
>> where is the historical data kept??
>>
>>
>>
>> On Wednesday, 11 April 2018 19:45:19 UTC+3, dhin...@djhindley.com wrote:
>>
>>> Hi
>>>
>>> I have just started using weewx on a Raspberry Pi with a Davis Vantage 
>>> using Weatherlink IP. The weather station has been running for 2 years, but 
>>> I only got weewx working from today. All is working fine, except that since 
>>> I updated my archive record to 5mins immediately prior to the installation, 
>>> weewx only shows the recent records. Does anyone know if there is a way I 
>>> can manually add the historical data to the weewx database, so that the 
>>> full history is shown on my weewx webpage? 
>>>
>>> Thanks
>>>
>> -- 
>> 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/VCwuWaT2kwY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[vince]

On Wednesday, April 11, 2018 at 11:54:47 AM UTC-7, Ralph Underwood wrote:
>
> Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?
>
>
>
Thinking not - I think you need:

   1. a "SOMETHING = dateTime" mapping in your weewx.conf file so the 
   driver knows what element is secs since the time epoch
   2. a  "SOMETHING: nnn"  key/value pair in your MQTT payload, where nnn = 
   secs_since_the_epoch (or 0 if you want to use the weewx computer dateTime)

Maybe you're just missing the TIME mapping in your weewx.conf label map.

Can you provide:

   - your [wxMesh] stanza from weewx.conf
   - an example of the MQTT payload you're sending




 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?

I thought that the TIME sent from mosquitto would be ignored.

I attempted Vince's suggestion and still same.

I'll look it all over again later.

Thanks 

On Wednesday, April 11, 2018 at 11:24:38 AM UTC-7, vince wrote:
>
> On Wednesday, April 11, 2018 at 10:06:22 AM UTC-7, Bill Morrow wrote:
>>
>> Line 308 in wxservices.py is failing:
>> 306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
>> 307 self.latitude, self.longitude, self.altitude_m,
>> 308 data['dateTime'], self.atc)
>>
>>
>>
> I'm wondering if perhaps you have no 'dateTime' in the data[] that you 
> are generating
>
> If you're ok with hacking+slashing in there with a test copy of that file, 
> I'd suggest trying to print 'data' out and see what's in there
>
> Something like (untested):
>
>else:
>try:
>   # the existing stuff on lines 306-308
>except:
>  print data
>
>  
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Bill Morrow]

On Wednesday, 11 April 2018 15:24:38 UTC-3, vince wrote:
>
> On Wednesday, April 11, 2018 at 10:06:22 AM UTC-7, Bill Morrow wrote:
>>
>> Line 308 in wxservices.py is failing:
>> 306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
>> 307 self.latitude, self.longitude, self.altitude_m,
>> 308 data['dateTime'], self.atc)
>>
>>
>>
> I'm wondering if perhaps you have no 'dateTime' in the data[] that you 
> are generating
>
> If you're ok with hacking+slashing in there with a test copy of that file, 
> I'd suggest trying to print 'data' out and see what's in there
>
> Something like (untested):
>
>else:
>try:
>   # the existing stuff on lines 306-308
>except:
>  print data
>
>  
>
>
That's right Vince, there is no dateTime in the incoming record. It 
presumably gets created during processing of the packet, or not in Ralph's 
case. 

I don't have his problem. We are both subscribed to the same type of 
incoming data from the MQTT broker.

I tried your suggestion. Added line 309 to wxservices.py, 
299 def calc_maxSolarRad(self, data, data_type):  # @UnusedVariable
300 algo = self.algorithms.get('maxSolarRad', 'RS')
301 if algo == 'Bras':
302 data['maxSolarRad'] = weewx.wxformulas.solar_rad_Bras(
303 self.latitude, self.longitude, self.altitude_m,
304 data['dateTime'], self.nfac)
305 else:
306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
307 self.latitude, self.longitude, self.altitude_m,
308 data['dateTime'], self.atc)
309 syslog.syslog(syslog.LOG_INFO, "calc_maxSolarRad: 
datetime error %s" % ' '.join(str(v)+':'+str(data[v]) for v in data))

changed debug to 1 in weewx.conf, stopped and restarted weewxd, and 
datetime looks OK:

Apr 11 15:44:10 walrus weewx[10068]: wxMesh: Queue of 2 entries
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: Working on queue entry 1 with 
payload : TIME:0,INTE:21.79,INHU:31.38
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: key: TIME value: 1523472250
Apr 11 15:44:10 walrus weewx[10068]: calc_maxSolarRad: datetime error 
barometer:None windchill:None dewpoint:None rainRate:0 heatindex:None 
maxSolarRad:None dateTime:1523472250.0 windDir:None pressure:None inDewpoint
:None altimeter:None usUnits:1 windGustDir:None
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: key: INTE value: 21.79
Apr 11 15:44:10 walrus weewx[10068]: calc_maxSolarRad: datetime error 
barometer:None windchill:None dewpoint:None inDewpoint:None heatindex:None 
rainRate:0 maxSolarRad:None dateTime:1523472250.0 windDir:None pressure:None 
inTemp:71.222 altimeter:None usUnits:1 windGustDir:None
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: key: INHU value: 31.38
Apr 11 15:44:10 walrus weewx[10068]: calc_maxSolarRad: datetime error 
barometer:None windchill:None dewpoint:None inDewpoint:39.3382446966 
heatindex:None rainRate:0 maxSolarRad:None dateTime:1523472250.0 windDir:
None pressure:None inHumidity:31.38 inTemp:71.222 altimeter:None usUnits:1 
windGustDir:None
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: Working on queue entry 0 with 
payload : TIME:0,INTE:21.81,INHU:31.46
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: key: TIME value: 1523472250
Apr 11 15:44:10 walrus weewx[10068]: calc_maxSolarRad: datetime error 
barometer:None windchill:None dewpoint:None rainRate:0 heatindex:None 
maxSolarRad:None dateTime:1523472250.0 windDir:None pressure:None inDewpoint
:None altimeter:None usUnits:1 windGustDir:None
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: key: INTE value: 21.81
Apr 11 15:44:10 walrus weewx[10068]: calc_maxSolarRad: datetime error 
barometer:None windchill:None dewpoint:None inDewpoint:None heatindex:None 
rainRate:0 maxSolarRad:None dateTime:1523472250.0 windDir:None pressure:None 
inTemp:71.258 altimeter:None usUnits:1 windGustDir:None
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: key: INHU value: 31.46
Apr 11 15:44:10 walrus weewx[10068]: calc_maxSolarRad: datetime error 
barometer:None windchill:None dewpoint:None inDewpoint:39.4347791969 
heatindex:None rainRate:0 maxSolarRad:None dateTime:1523472250.0 windDir:
None pressure:None inHumidity:31.46 inTemp:71.258 altimeter:None usUnits:1 
windGustDir:None
Apr 11 15:44:10 walrus weewx[10068]: wxMesh: Sleeping for 20
Apr 11 15:44:14 walrus weewx[10068]: wxMesh: Added to queue of 1 message 
TIME:0,INTE:21.80,INHU:31.46


 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[vince]

On Wednesday, April 11, 2018 at 10:06:22 AM UTC-7, Bill Morrow wrote:
>
> Line 308 in wxservices.py is failing:
> 306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
> 307 self.latitude, self.longitude, self.altitude_m,
> 308 data['dateTime'], self.atc)
>
>
>
I'm wondering if perhaps you have no 'dateTime' in the data[] that you are 
generating

If you're ok with hacking+slashing in there with a test copy of that file, 
I'd suggest trying to print 'data' out and see what's in there

Something like (untested):

   else:
   try:
  # the existing stuff on lines 306-308
   except:
 print data

 

 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Manually adding historical data to weewx database

[David Hindley]

The data has been downloaded to a text file from the WeatherLink software,
stores in a txt file on my Windows PC.

David.

On Wed, 11 Apr 2018 at 18:05, Andrew Milner 
wrote:

> where is the historical data kept??
>
>
>
> On Wednesday, 11 April 2018 19:45:19 UTC+3, dhin...@djhindley.com wrote:
>
>> Hi
>>
>> I have just started using weewx on a Raspberry Pi with a Davis Vantage
>> using Weatherlink IP. The weather station has been running for 2 years, but
>> I only got weewx working from today. All is working fine, except that since
>> I updated my archive record to 5mins immediately prior to the installation,
>> weewx only shows the recent records. Does anyone know if there is a way I
>> can manually add the historical data to the weewx database, so that the
>> full history is shown on my weewx webpage?
>>
>> Thanks
>>
> --
> 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/VCwuWaT2kwY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

I didn't start a discussion on that but I will look for it.  I have been 
searching for a post where (I thought it was mwall) mentions setting the 
dateTime to something to force weewx to use the correct one. Or maybe it 
was a dream :)

Thanks for your help.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

I have this weather station
https://www.ambientweather.com/amws1000wifi.html
I will try to make more loop packages and see what station send.

Dne sreda, 11. april 2018 18.42.13 UTC+2 je oseba Greg Troxel napisala:
>
>
> I did misunderstand, sort of.  I think you are in a situation where 
> either 
>
>   your station is behaving strangely 
>
>   the interceptor driver fo fine offset station does not have support 
>   for decoding UV index, and is just reporting byte values until that's 
>   figured out 
>
>   something else :-) 
>
> So I would recommend recording displayed values vs LOOP packet values, 
> and creating a scatter plot.  I also recommend reading the driver source 
> code to see what it thinks it is doing now.  With any luck the 
> relationship will be clear and reliable, and you can contribute 
> new/improved support to the driver. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Bill Morrow]

Doh! Your system time is right there in front of me:

> Apr 11 08:03:22 mapleleaf weewx[4079]: wxMesh: key: TIME value: 
> 1523459002
>
According to epochconverter:
Conversion results (1523459002)
1523459002 converts to Wednesday April 11, 2018 08:03:22 (am) in time zone 
America/Vancouver 
(PDT)
The offset (difference to Greenwich Time/GMT) is -07:00 or in seconds 
-25200.

So there is no problem with time.

Line 308 in wxservices.py is failing:
299 def calc_maxSolarRad(self, data, data_type):  # @UnusedVariable
300 algo = self.algorithms.get('maxSolarRad', 'RS')
301 if algo == 'Bras':
302 data['maxSolarRad'] = weewx.wxformulas.solar_rad_Bras(
303 self.latitude, self.longitude, self.altitude_m,
304 data['dateTime'], self.nfac)
305 else:
306 data['maxSolarRad'] = weewx.wxformulas.solar_rad_RS(
307 self.latitude, self.longitude, self.altitude_m,
308 data['dateTime'], self.atc)

presumably because dateTime is a bad value, or has not been set. I'm not 
sure where dateTime is calculated. It most certainly is done after wxMesh 
finishes with genLoopPackets. It looks like you have started a discussion 
on that in the development group.



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Manually adding historical data to weewx database

[Andrew Milner]

where is the historical data kept??



On Wednesday, 11 April 2018 19:45:19 UTC+3, dhin...@djhindley.com wrote:

> Hi
>
> I have just started using weewx on a Raspberry Pi with a Davis Vantage 
> using Weatherlink IP. The weather station has been running for 2 years, but 
> I only got weewx working from today. All is working fine, except that since 
> I updated my archive record to 5mins immediately prior to the installation, 
> weewx only shows the recent records. Does anyone know if there is a way I 
> can manually add the historical data to the weewx database, so that the 
> full history is shown on my weewx webpage? 
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Andrew Milner]

matthew has already said tha weewx does not calculate uv index - it merely 
uses the data provided by the station


On Wednesday, 11 April 2018 19:42:13 UTC+3, Greg Troxel wrote:

>
> I did misunderstand, sort of.  I think you are in a situation where 
> either 
>
>   your station is behaving strangely 
>
>   the interceptor driver fo fine offset station does not have support 
>   for decoding UV index, and is just reporting byte values until that's 
>   figured out 
>
>   something else :-) 
>
> So I would recommend recording displayed values vs LOOP packet values, 
> and creating a scatter plot.  I also recommend reading the driver source 
> code to see what it thinks it is doing now.  With any luck the 
> relationship will be clear and reliable, and you can contribute 
> new/improved support to the driver. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

pi@mapleleaf:~ $ date +%s
1523465424
pi@mapleleaf:~ $ date
Wed Apr 11 09:50:28 PDT 2018

appears to match my iMac time.  The Rpi does not have a realtime clock; 
however I have a couple in my parts drawer. I will find a battery and try 
one of them.

I programmed the Huzzah with another Rpi - when I do a date +%s on both of 
them as fast as I can click the  results are 1523465622 and 1523465625  - I 
think that they are pretty close considering I have to change windows and 
click.




-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Manually adding historical data to weewx database

[dhindley]

Hi

I have just started using weewx on a Raspberry Pi with a Davis Vantage 
using Weatherlink IP. The weather station has been running for 2 years, but 
I only got weewx working from today. All is working fine, except that since 
I updated my archive record to 5mins immediately prior to the installation, 
weewx only shows the recent records. Does anyone know if there is a way I 
can manually add the historical data to the weewx database, so that the 
full history is shown on my weewx webpage? 

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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Greg Troxel]

I did misunderstand, sort of.  I think you are in a situation where
either

  your station is behaving strangely

  the interceptor driver fo fine offset station does not have support
  for decoding UV index, and is just reporting byte values until that's
  figured out

  something else :-)

So I would recommend recording displayed values vs LOOP packet values,
and creating a scatter plot.  I also recommend reading the driver source
code to see what it thinks it is doing now.  With any luck the
relationship will be clear and reliable, and you can contribute
new/improved support to the driver.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Bill Morrow]

Comments imbedded

On Wednesday, 11 April 2018 12:17:23 UTC-3, Ralph Underwood wrote:
>
> Hi Bill
>
> I rebuilt my development system, installed Jessie, configured rpi, 
> installed Mosquitto and weewx with the simulator. Attempted to do the 
> extension install of wxMesh, that failed so I manually installed the wxMesh 
> file in /usr/share/weewx/user. Changed the driver to wxMesh and made 
> changes to weewx.conf as described in wxMesh.py.  
>
> Now I am getting this: (my comments are in* blue*)
> ...
>
 

> Apr 11 08:03:18 mapleleaf weewx[4079]: wxMesh: Added to queue of 1 message 
> TIME:0,INTE:20.35,INHU:52.23* looks good to me*
>
*Yes, looks good*
 

> Apr 11 08:03:22 mapleleaf weewx[4079]: wxMesh: Working on queue of 1
> Apr 11 08:03:22 mapleleaf weewx[4079]: wxMesh: Working on queue 0 payload 
> : TIME:0,INTE:20.35,INHU:52.23
> Apr 11 08:03:22 mapleleaf weewx[4079]: wxMesh: key: TIME value: 1523459002 
>*what?? *
>
*I replace the time of 0 with the current epoch time within the driver. My 
outdoor hardware can't yet provide reliable time stamps. 1523459002 looks 
right, check at http://epochconverter.com*
 

> Apr 11 08:03:22 mapleleaf weewx[4079]: engine: Main loop exiting. Shutting 
> engine down.
> Apr 11 08:03:22 mapleleaf weewx[4079]: engine: Caught unrecoverable 
> exception in engine:
> Apr 11 08:03:22 mapleleaf weewx[4079]:   'dateTime'
> Apr 11 08:03:22 mapleleaf weewx[4079]:   Traceback (most recent 
> call last):
> Apr 11 08:03:22 mapleleaf weewx[4079]: File 
> "/usr/share/weewx/weewx/engine.py", line 871, in main
> Apr 11 08:03:22 mapleleaf weewx[4079]:   engine.run()
> Apr 11 08:03:22 mapleleaf weewx[4079]: File 
> "/usr/share/weewx/weewx/engine.py", line 190, in run
> Apr 11 08:03:22 mapleleaf weewx[4079]:  
>  self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
> Apr 11 08:03:22 mapleleaf weewx[4079]: File 
> "/usr/share/weewx/weewx/engine.py", line 223, in dispatchEvent
> Apr 11 08:03:22 mapleleaf weewx[4079]:   callback(event)
> Apr 11 08:03:22 mapleleaf weewx[4079]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
> Apr 11 08:03:22 mapleleaf weewx[4079]:  
>  self.calc.do_calculations(event.packet, 'loop')
> Apr 11 08:03:22 mapleleaf weewx[4079]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 191, in do_calculations
> Apr 11 08:03:22 mapleleaf weewx[4079]:   getattr(self, 'calc_' 
> + obs)(data_us, data_type)
> Apr 11 08:03:22 mapleleaf weewx[4079]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 308, in calc_maxSolarRad
> Apr 11 08:03:22 mapleleaf weewx[4079]:   data['dateTime'], 
> self.atc)
> Apr 11 08:03:22 mapleleaf weewx[4079]:   KeyError: 'dateTime'
> Apr 11 08:03:22 mapleleaf weewx[4079]:   Exiting.
>
> I seem to remember seeing a post about setting dateTime somewhere but 
> can't find that post.
>

Possibly your Pi's time is off, which is why the calculation in 
wxservices.py is failing. If you go to a shell prompt, and type these 
commands, what do you get?  

date +%s 
date 

The first command gives you the time in seconds since 1970-01-01 00:00 UTC, 
the "epoch time", the second command in something humanly readable. On my 
raspbian:
> date  +%s
1523463375
> date
Wed 11 Apr 16:16:19 UTC 2018

There's some discussion on getting the time set at boot for raspbian here:
https://raspberrypi.stackexchange.com/questions/8231/how-to-force-ntpd-to-update-date-time-after-boot




-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Using WeeWxMQTT - problems

[Ralph Underwood]

Hi Bill

I rebuilt my development system, installed Jessie, configured rpi, 
installed Mosquitto and weewx with the simulator. Attempted to do the 
extension install of wxMesh, that failed so I manually installed the wxMesh 
file in /usr/share/weewx/user. Changed the driver to wxMesh and made 
changes to weewx.conf as described in wxMesh.py.  

Now I am getting this: (my comments are in* blue*)




Apr 11 08:03:17 mapleleaf systemd[1]: Starting LSB: weewx weather system...
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Initializing weewx version 
3.8.0
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Using Python 2.7.9 (default, 
Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: Locale is 'en_US.UTF-8'
Apr 11 08:03:17 mapleleaf weewx[4075]: engine: pid file is 
/var/run/weewx.pid
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: debug is 1
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Initializing engine
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading station type wxMesh 
(user.wxMesh)
Apr 11 08:03:17 mapleleaf weewx[4065]: Starting weewx weather system: weewx.
Apr 11 08:03:17 mapleleaf systemd[1]: Started LSB: weewx weather system.
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: MQTT host is 10.0.0.161
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: MQTT topic is weather
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: MQTT client is wxclient
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: polling interval is 5.0
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: label map is {'INTE': 
'inTemp', 'INHU': 'outHumidity'}
Apr 11 08:03:17 mapleleaf weewx[4079]: wxMesh: Connected to MQTT   
 *(I edited this message in wxMesh 
while troubleshooting - used to say "Connected)*
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdTimeSynch
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdConvert
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: StdConvert target unit is 0x1
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdConvert
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdCalibrate
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdCalibrate
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdQC
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdQC
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Apr 11 08:03:17 mapleleaf weewx[4079]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr 11 08:03:17 mapleleaf weewx[4079]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.engine.StdArchive
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Archive will use data 
binding wx_binding
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Record generation will be 
attempted in 'hardware'
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Use LOOP data in hi/low 
calculations: 1
Apr 11 08:03:17 mapleleaf weewx[4079]: manager: Daily summary version is 2.0
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Apr 11 08:03:17 mapleleaf weewx[4079]: manager: Starting backfill of daily 
summaries
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.engine.StdArchive
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.restx.StdStationRegistry
Apr 11 08:03:17 mapleleaf weewx[4079]: restx: StationRegistry: Registration 
not requested.
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Loading service 
weewx.restx.StdWunderground
Apr 11 08:03:17 mapleleaf weewx[4079]: restx: Wunderground: Posting not 
enabled.
Apr 11 08:03:17 mapleleaf weewx[4079]: engine: Finished loading service 
weewx.restx.StdWunderground

Re: [weewx-user] Re: UV index

[Andrew Milner]

correction - from the loop data you provided it appears your weather
station is not outputting a UV Index in the UV field, but is instead
outputting some numerical value which you need to try and convert into an
index - which may or may not be possible.  Without knowing more examples of
console UV index value compared to UV loop data output by station we cannot
really offer any more input!!  It is not however a weewx configuration
issue as such, since your station does not appear to be outputting the UV
index itself!!



On 11 April 2018 at 16:20, Damjan Hajsek  wrote:

> Maybe we didn't understand right.
> Station show real value of UV index on my terminal at home.
> But not on my web page by weewx. So it is settings in weewx
>
> Dne sreda, 11. april 2018 15.08.09 UTC+2 je oseba Greg Troxel napisala:
>>
>> Damjan Hajsek  writes:
>>
>> > Anyone know what to use in
>> > [StdCalibrate]
>> >
>> > [[Corrections]]
>> >
>> > to correct UV index? Because now at night it is UV = 15
>>
>> (I don't have any actual experience here, either with weewx calibration
>> or with UV sensors that ever show 15.)
>>
>> Typically, "calibration" involves minor adjustments to a sensor that is
>> basically working ok, like adding 0.7 hPA to pressure.  There is an
>> underlying assumption that the sensor has the right slope but just a
>> small offset.
>>
>> A UV sensor that reports a UV index of 15 at night sounds so seriously
>> off that it seems more likely that something is catastrophically wrong
>> which cannot reasonably be resolved with calibration.  I have not
>> checked calibration on my UV sensor, but it reliably shows 0 at night
>> and patterns that appear to corrrelate well with sunny vs not and sun
>> angle.  I would not be shocked if it reads 3.8 when it should read 4.0;
>> I would have to be far more thorough to figure that out, vs eyeballing
>> graphs and not being suspicious.
>>
>> I would recommend looking at all other ways of observing the sensor
>> value (console?), and see if there are any setup errors.
>>
>> Finally, I would log the data without calibration for a while, and graph
>> that in a scatter plot against UV data from some nearby station that you
>> believe is working ok.  If that turns out to be a line with slope 1 and
>> offset 15, then subtracting 15 is good strategy.  But until you know
>> that such a relationship holds, the assumption that there is a single
>> linear offset seems unwarranted.
>>
>> Greg
>>
> --
> 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/-J1FnAF6v4g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

Maybe we didn't understand right.
Station show real value of UV index on my terminal at home.
But not on my web page by weewx. So it is settings in weewx

Dne sreda, 11. april 2018 15.08.09 UTC+2 je oseba Greg Troxel napisala:
>
> Damjan Hajsek > writes: 
>
> > Anyone know what to use in 
> > [StdCalibrate] 
> > 
> > [[Corrections]] 
> > 
> > to correct UV index? Because now at night it is UV = 15 
>
> (I don't have any actual experience here, either with weewx calibration 
> or with UV sensors that ever show 15.) 
>
> Typically, "calibration" involves minor adjustments to a sensor that is 
> basically working ok, like adding 0.7 hPA to pressure.  There is an 
> underlying assumption that the sensor has the right slope but just a 
> small offset. 
>
> A UV sensor that reports a UV index of 15 at night sounds so seriously 
> off that it seems more likely that something is catastrophically wrong 
> which cannot reasonably be resolved with calibration.  I have not 
> checked calibration on my UV sensor, but it reliably shows 0 at night 
> and patterns that appear to corrrelate well with sunny vs not and sun 
> angle.  I would not be shocked if it reads 3.8 when it should read 4.0; 
> I would have to be far more thorough to figure that out, vs eyeballing 
> graphs and not being suspicious. 
>
> I would recommend looking at all other ways of observing the sensor 
> value (console?), and see if there are any setup errors. 
>
> Finally, I would log the data without calibration for a while, and graph 
> that in a scatter plot against UV data from some nearby station that you 
> believe is working ok.  If that turns out to be a line with slope 1 and 
> offset 15, then subtracting 15 is good strategy.  But until you know 
> that such a relationship holds, the assumption that there is a single 
> linear offset seems unwarranted. 
>
> Greg 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Greg Troxel]

Damjan Hajsek  writes:

> Anyone know what to use in
> [StdCalibrate]
> 
> [[Corrections]]
>
> to correct UV index? Because now at night it is UV = 15

(I don't have any actual experience here, either with weewx calibration
or with UV sensors that ever show 15.)

Typically, "calibration" involves minor adjustments to a sensor that is
basically working ok, like adding 0.7 hPA to pressure.  There is an
underlying assumption that the sensor has the right slope but just a
small offset.

A UV sensor that reports a UV index of 15 at night sounds so seriously
off that it seems more likely that something is catastrophically wrong
which cannot reasonably be resolved with calibration.  I have not
checked calibration on my UV sensor, but it reliably shows 0 at night
and patterns that appear to corrrelate well with sunny vs not and sun
angle.  I would not be shocked if it reads 3.8 when it should read 4.0;
I would have to be far more thorough to figure that out, vs eyeballing
graphs and not being suspicious.

I would recommend looking at all other ways of observing the sensor
value (console?), and see if there are any setup errors.

Finally, I would log the data without calibration for a while, and graph
that in a scatter plot against UV data from some nearby station that you
believe is working ok.  If that turns out to be a line with slope 1 and
offset 15, then subtracting 15 is good strategy.  But until you know
that such a relationship holds, the assumption that there is a single
linear offset seems unwarranted.

Greg

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Confused about how to install Weewx-forecast

[Damjan Hajsek]

I have manage to solve it by myself problem was icons, so I changed apache 
settings and disabled autoindex.conf

Dne sreda, 11. april 2018 11.11.17 UTC+2 je oseba Damjan Hajsek napisala:
>
> Hi
> I have the same problem but I am lost at the end, still doesn't get 
> anything on my index page.
> I have attached my index.html.tmpl file. Can someone help me?
>
>
> Dne torek, 06. februar 2018 10.01.38 UTC+1 je oseba Cycle London napisala:
>>
>> There is one thing that strikes me.  On the temperature scale, the degree 
>> sign and 'C' appears three times.  I'm assuming that this represents a 
>> high, low and actual prediction?   It's not - I think - anything to do with 
>> my installation, as if I check out the 'MIT Sailing Pavillon' live example, 
>> they have it too.. 
>>
>> http://sailing.mit.edu/weather/forecast.html
>>
>> is there a way to include high and low?  
>>
>> And is it possible to limit the number of days forward that the forecast 
>> reaches?  
>>
>> Is there actually a page where the options for the strip are detailed?  
>> So far, I've only seen the HOWTO on the wiki. 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Android weather app for weeWx users

[Bill M]

Tried again this morning and it installed just fine, everything seems to be 
working now that I've fixed my typos!
Thanks for the hard work
Bill

On Tuesday, April 10, 2018 at 9:09:28 PM UTC-5, John Smith wrote:
>
> On Wednesday, 11 April 2018 11:27:31 UTC+10, Bill M wrote:
>>
>> Nope won't install now?
>>
>
> I had the install hang too, I ended up rebooting and it reported that it 
> was installed correctly, no idea what's wrong there.
>
> As for you settings.txt you have a ] at the end of the webcam url
>
> webcam=http://www.sanfordweather.com/camera/camera3.jpg]
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WU Import failed

[Andre]

Gary, I wish you a speedy recovery.
I know that as well. Unfortunately.

Regards, Andre

Am Dienstag, 3. April 2018 17:16:46 UTC+2 schrieb Andre:
>
> Hi,
>
> First I have to say I'm not Linux professional and all my 'know-how' is 
> based on reading a lot of tutorials.
>
> My weather station is a Davis Vantage Vue. WeeWX is running on a Raspberry 
> Pi 2. This setup is running and all data are fine.
>
> My problem is I can't import any data from WU with wee_import.
>
> ---log---
> wee_import --import-config=/var/tmp/wu.conf --from=2018-01-01T00:30 --to=
> 2018-01-31T00:00 --dry-run
> Starting wee_import...
> Observation history for Weather Underground station 'INORDERS99' will be 
> imported.
> Using database binding 'wx_binding', which is bound to database 
> 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Observations timestamped after 2018-01-01 00:30:00 CET (1514763000) and 
> up to and
> including 2018-01-31 00:00:00 CET (1517353200) will be imported.
> This is a dry run, imported data will not be saved to archive.
> * radiation: cannot convert '---' to float at timestamp '2018-01-01 
> 00:30:00 CET (1514763000)'.*
>  Nothing done, exiting.
> ---log---
>
> What does it mean "radiation: cannot convert '---' to float at timestamp 
> '2018-01-01 00:30:00 CET (1514763000)'?
> Is there data mismatch on WU? What can I do to solv this issue?
>
> Regards, Andre
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WU Import failed

[gjr80]

Hi Andre,

Unfortunately some back and neck problems over the last week have kept me from 
the compter, only using the iPad now and then. Hopefully the physio will have 
things fixed soon and I can get back to weeWX.

Gary 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Confused about how to install Weewx-forecast

[Damjan Hajsek]

Hi
I have the same problem but I am lost at the end, still doesn't get 
anything on my index page.
I have attached my index.html.tmpl file. Can someone help me?


Dne torek, 06. februar 2018 10.01.38 UTC+1 je oseba Cycle London napisala:
>
> There is one thing that strikes me.  On the temperature scale, the degree 
> sign and 'C' appears three times.  I'm assuming that this represents a 
> high, low and actual prediction?   It's not - I think - anything to do with 
> my installation, as if I check out the 'MIT Sailing Pavillon' live example, 
> they have it too.. 
>
> http://sailing.mit.edu/weather/forecast.html
>
> is there a way to include high and low?  
>
> And is it possible to limit the number of days forward that the forecast 
> reaches?  
>
> Is there actually a page where the options for the strip are detailed?  So 
> far, I've only seen the HOWTO on the wiki. 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


index.html.tmpl
Description: Binary data

[weewx-user] Re: UV index

[Damjan Hajsek]

Thank you I already tried that but didn't use capital letters for UV i use 
uv and weewx complain when I restarted it, now I will chck console and 
create formula to get right value.

Dne sreda, 11. april 2018 09.34.18 UTC+2 je oseba Andrew Milner napisala:
>
> I doubt if it can be done by a simple change as it appears to depend on 
> ozone thickness, cloud thickness, time of year and station elevation.
>
> However, if you know what it should read then provided it is a value sent 
> raw from the station, and is not derived within weewx, you can just say UV 
> = UV - 15 (if you want to just subtract 15 from the value supplied) or UV = 
> UV / 15 if you want to divide the value by 15 - going to your original post 
> maybe it should be UV = UV / 256 - which would probably give 0 at night (if 
> weewx is reporting 15)
>
>
> Guess you should give some examples of UV on console and UV in weewx to be 
> able to derive a calibration formula
>
>
>
> On Wednesday, 11 April 2018 10:04:26 UTC+3, Damjan Hajsek wrote:
>
>> Anyone know what to use in
>> [StdCalibrate]
>> 
>> [[Corrections]]
>>
>> to correct UV index? Because now at night it is UV = 15
>>
>>
>>
>> Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> What is relation with UV index and radiation?
>>> Because sometimes radiation is already 0 but UV index is still about 80 
>>> or 50.
>>> Doesn't that be also 0 when radiation is 0?
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Andrew Milner]

I doubt if it can be done by a simple change as it appears to depend on 
ozone thickness, cloud thickness, time of year and station elevation.

However, if you know what it should read then provided it is a value sent 
raw from the station, and is not derived within weewx, you can just say UV 
= UV - 15 (if you want to just subtract 15 from the value supplied) or UV = 
UV / 15 if you want to divide the value by 15 - going to your original post 
maybe it should be UV = UV / 256 - which would probably give 0 at night (if 
weewx is reporting 15)


Guess you should give some examples of UV on console and UV in weewx to be 
able to derive a calibration formula



On Wednesday, 11 April 2018 10:04:26 UTC+3, Damjan Hajsek wrote:

> Anyone know what to use in
> [StdCalibrate]
> 
> [[Corrections]]
>
> to correct UV index? Because now at night it is UV = 15
>
>
>
> Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek 
> napisala:
>>
>> What is relation with UV index and radiation?
>> Because sometimes radiation is already 0 but UV index is still about 80 
>> or 50.
>> Doesn't that be also 0 when radiation is 0?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

Anyone know what to use in
[StdCalibrate]

[[Corrections]]

to correct UV index? Because now at night it is UV = 15



Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 0?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.