[weewx-user] Re: Belchertown skin line graph gaps

2020-01-02 Thread Pat
This is due to your gapSize not matching your archive_interval or something 
else is going on with your weewx not archiving reliably and skipping 
archives. Your log files will know more. 

For starters double check that gapSize 
matches
 
your archive_interval. 

On Thursday, January 2, 2020 at 5:16:48 PM UTC-5, István Hegedűs wrote:
>
> Hi guys! I'm using the great Belchertown skin but I have gaps on today 
> line graphs. These are 5 or 10 minutes long.
> Sometimes (as you can see on the second picture) the data is present but 
> there is no line on the graph.
>
> Weewx 3.9.2 on RPI
> Belchertown skin 1.0.1
> report_timing = */5 * * * *
> archive_interval  = 300 (from hardver)
> default skin and graphs config file
>
> Can you help me?
>
> [image: Screen Shot 2020-01-02 at 11.24.46.png]
> [image: Screen Shot 2020-01-02 at 11.25.06.png]
>
>
>
>
>

-- 
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/453ccc0c-83b0-492c-9cac-3197ca468e19%40googlegroups.com.


Re: [weewx-user] Add picture in header on sofaskin webpage.

2020-01-02 Thread p q
I don't know that skin, but I did something similar for the old standard
skin.

For a single image, you need to add a line to the template (index.html.tmpl
probably) like





I wrote a little bit of javascript to rotate different pictures under the
banner and if you're interested you can find it in the index.html.tmpl
here:
https://github.com/PeterQuinn925/weewx_skin/blob/master/index.html.tmpl

On Thu, Jan 2, 2020 at 12:28 PM Mikael Fredriksson 
wrote:

> Hi!
>
> Can someone explain how to add a picture at the top of a sofaskin web
> page? I only know how to change the color in a .css file, main.css I think
> it was...
> Like it´s done on this page: http://www.limburgweer.com/index_EN.html
>
> /Mikael
>
> --
> 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/a8e8659a-9954-403b-a3ab-a7128a1a7325%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM20ma8f2Dd2dKear9wk6-CXnstURqaQzhF2iQMhpAA%2BiNA%40mail.gmail.com.


[weewx-user] Re: Connecting Froggit WH2600SE to Weewx - Setup always fails :(

2020-01-02 Thread Lars
It is weird 
- I removed that .122 
- hard reset the bridge
- edited the weather bridge software in another browser

and checked the log. And here you go the data is finally reaching weewx.
I have not managed to see the data in the browser at 
http://192.168.1.119///var/www/html/weewx/index.html (port 80 does not 
appear to be used by anything else, not sure why I can not reach it) 
but I guess this will be easier to get it working.

THANK YOU SOOO MUCH!!! :D
Really appreciate your help!!!

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: using 
rain_total 0.0 from yearlyrainin

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: firmware 
WH2600%20V2.2.8: baromin is barometer

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter rainin=0.00

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter monthlyrainin=0.00

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter realtime=1

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter rtfreq=5

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter PASSWORD=XXX

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter ID=StationIDset

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter softwaretype=WH2600%20V2.2.8

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter action=updateraw

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter weeklyrainin=0.00

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: raw 
packet: {'wind_speed': 0.0, 'humidity_in': 67.0, 'temperature_in': 54.7, 
'barometer': 29.9, 'windchill': 72.1, 'dewpoint': 49.1, 'humidity_out': 
44.0, 'uv': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 1578010336, 
'temperature_out': 72.1, 'wind_dir': 105.0, 'rain_total': 0.0, 'usUnits': 
1, 'wind_gust': 0.0}

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: mapped 
packet: {'barometer': 29.9, 'windchill': 72.1, 'dewpoint': 49.1, 
'outHumidity': 44.0, 'UV': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 
1578010336, 'windDir': 105.0, 'outTemp': 72.1, 'windSpeed': 0.0, 
'inHumidity': 67.0, 'inTemp': 54.7, 'windGust': 0.0, 'usUnits': 1}

Jan  3 01:12:27 raspberrypi weewx[425]: interceptor: MainThread: empty queue

Jan  3 01:12:33 raspberrypi weewx[425]: interceptor: ServerThread: GET: 
ID=StationIDset&PASSWORD=&tempf=72.1&humidity=44&dewptf=49.1&windchillf=72.1&winddir=105&windspeedmph=0.00&windgustmph=0.00&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=0.00&yearlyrainin=0.00&solarradiation=0.00&UV=0&indoortempf=54.9&indoorhumidity=67&baromin=29.89&dateutc=2020-01-03%200:12:32&softwaretype=WH2600%20V2.2.8&action=updateraw&realtime=1&rtfreq=5

Jan  3 01:12:33 raspberrypi weewx[425]: interceptor: MainThread: raw data: 
ID=StationIDset&PASSWORD=PassStation&tempf=72.1&humidity=44&dewptf=49.1&windchillf=72.1&winddir=105&windspeedmph=0.00&windgustmph=0.00&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=0.00&yearlyrainin=0.00&solarradiation=0.00&UV=0&indoortempf=54.9&indoorhumidity=67&baromin=29.89&dateutc=2020-01-03%200:12:32&softwaretype=WH2600%20V2.2.8&action=updateraw&realtime=1&rtfreq=5

-- 
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/e088224b-eb9c-4930-9dd9-3add550727a4%40googlegroups.com.


[weewx-user] Re: Connecting Froggit WH2600SE to Weewx - Setup always fails :(

2020-01-02 Thread Lars
It is weird 
- I removed that .122 
- hard reset the bridge
- edited the weather bridge software in another browser

and checked the log. And here you go the data is finally reaching weewx.
I have not managed to see the data in the browser at 
http://192.168.1.119///var/www/html/weewx/index.html (port 80 does not 
appear to be used by anything else, not sure why I can reach it) 
but I guess this will be easier to get it working.

THANK YOU SOOO MUCH!!! :D
Really appreciate your help!!!

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: using 
rain_total 0.0 from yearlyrainin

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: firmware 
WH2600%20V2.2.8: baromin is barometer

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter rainin=0.00

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter monthlyrainin=0.00

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter realtime=1

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter rtfreq=5

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter PASSWORD=XXX

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter ID=StationIDset

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter softwaretype=WH2600%20V2.2.8

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter action=updateraw

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: ignored 
parameter weeklyrainin=0.00

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: raw 
packet: {'wind_speed': 0.0, 'humidity_in': 67.0, 'temperature_in': 54.7, 
'barometer': 29.9, 'windchill': 72.1, 'dewpoint': 49.1, 'humidity_out': 
44.0, 'uv': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 1578010336, 
'temperature_out': 72.1, 'wind_dir': 105.0, 'rain_total': 0.0, 'usUnits': 
1, 'wind_gust': 0.0}

Jan  3 01:12:17 raspberrypi weewx[425]: interceptor: MainThread: mapped 
packet: {'barometer': 29.9, 'windchill': 72.1, 'dewpoint': 49.1, 
'outHumidity': 44.0, 'UV': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 
1578010336, 'windDir': 105.0, 'outTemp': 72.1, 'windSpeed': 0.0, 
'inHumidity': 67.0, 'inTemp': 54.7, 'windGust': 0.0, 'usUnits': 1}

Jan  3 01:12:27 raspberrypi weewx[425]: interceptor: MainThread: empty queue

Jan  3 01:12:33 raspberrypi weewx[425]: interceptor: ServerThread: GET: 
ID=StationIDset&PASSWORD=&tempf=72.1&humidity=44&dewptf=49.1&windchillf=72.1&winddir=105&windspeedmph=0.00&windgustmph=0.00&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=0.00&yearlyrainin=0.00&solarradiation=0.00&UV=0&indoortempf=54.9&indoorhumidity=67&baromin=29.89&dateutc=2020-01-03%200:12:32&softwaretype=WH2600%20V2.2.8&action=updateraw&realtime=1&rtfreq=5

Jan  3 01:12:33 raspberrypi weewx[425]: interceptor: MainThread: raw data: 
ID=StationIDset&PASSWORD=PassStation&tempf=72.1&humidity=44&dewptf=49.1&windchillf=72.1&winddir=105&windspeedmph=0.00&windgustmph=0.00&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=0.00&yearlyrainin=0.00&solarradiation=0.00&UV=0&indoortempf=54.9&indoorhumidity=67&baromin=29.89&dateutc=2020-01-03%200:12:32&softwaretype=WH2600%20V2.2.8&action=updateraw&realtime=1&rtfreq=5

-- 
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/948c1964-ca83-4e10-92c7-498dcd158b71%40googlegroups.com.


[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

2020-01-02 Thread G Hammer


On Thursday, January 2, 2020 at 12:33:15 PM UTC-5, mwall wrote:
>
> On Tuesday, December 31, 2019 at 1:51:42 PM UTC-5, G Hammer wrote:
>>
>> root@weewx1:~# service weewx stop
>> root@weewx1:~# PYTHONPATH=/home/weewx/bin python 
>> /home/weewx/bin/user/interceptor.py --device=fineoffset-bridge --port 8000 
>> --debug
>> raw data: 
>> PASSKEY=D35&stationtype=GW1000B_V1.5.5&dateutc=2019-12-31+18:04:07&tempinf=72.1&humidityin=32&baromrelin=29.577&baromabsin=29.131&tempf=35.8&humidity=92&winddir=96&windspeedmph=0.00&windgustmph=0.00&maxdailygust=10.29&solarradiation=58.48&uv=0&rainratein=0.047&eventrainin=1.150&hourlyrainin=0.051&dailyrainin=0.118&weeklyrainin=1.150&monthlyrainin=3.780&yearlyrainin=6.138&totalrainin=6.138&wh65batt=0&wh26batt=0&freq=915M&model=GW1000_Pro
>
>
> thank you for this.  i have added those field to weewx-interceptor as of 
> 0.48
>
> i've got to focus on some weewx4 issues before i do more work on the 
> weewx-interceptor, so apologies in advance for delays in my response
>
> m 
>

Thanks for the update.

I have installed 0.48 and all seems well. I have complete data, but will 
have to wait until tomorrow to see if UV and solar are being captured as it 
is past sundown here now.

No problem on delayed response. I have been waiting on an updated 
Interceptor to begin testing version 4.

-- 
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/2ce09f28-f07a-428a-8542-8571a287cd0a%40googlegroups.com.


[weewx-user] Re: Graphs/plots

2020-01-02 Thread gjr80
Hi Nigel,

The only way it can be there would be to change the template, doable I am sure 
though the operation of the Seasons page(s) is a little more complex than for 
Standard, so I suspect it will be a little more involved. Also expect any such 
customization will be left to the user though.

Gary

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


[weewx-user] Re: Graphs/plots

2020-01-02 Thread Devonian
Hi Gary,

OK on 'hovering' but I was wondering if it could 'just be there' !!  Never 
mind, it's not a biggie.

Stay safe and Happy New Year ;-)

Nigel.

-- 
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/28e83fa6-c38f-4bb9-a77d-de75eae248a6%40googlegroups.com.


[weewx-user] Re: Graphs/plots

2020-01-02 Thread gjr80
Hi Nigel,

The times are still there, you just need to hover over the max/min concerned 
and it should pop up. If on a touch device just click on the High/Low panel 
title and a Statistics page will display that shows the times.

We are fine here, too close to suburbia plus the vast majority of the fire 
activity has moved to southern NSW an Victoria. Would welcome some ‘wet’ here.

Gary

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


[weewx-user] Re: Graphs/plots

2020-01-02 Thread Devonian
Hi Gary,

Thanks, that got it in one!
I changed the aggregate_type from avg to max for all plots except daily.  
Deleted all the png images and forced weewx to regenerate all images with 
wee_reports

So, one more for you if I may...
In the default daily Seasons page, in the left frame there is High/Low 
section and underneath is the high & low for the various events e.g. 
Outside Temperature with the high and low temp.
In the old Standard skin, it also reported WHEN those observations occurred 
- is it possible to add the time for each event i.e. 11.5C at 11:46 ??

Hope everything is OK with you down under and you are safe from the fires.

Nigel (in a wet and miserable south west UK)

-- 
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/2f825ab8-6cc7-4e8c-910f-92760fd8ddd9%40googlegroups.com.


[weewx-user] Add picture in header on sofaskin webpage.

2020-01-02 Thread Mikael Fredriksson
Hi!

Can someone explain how to add a picture at the top of a sofaskin web page? 
I only know how to change the color in a .css file, main.css I think it 
was...
Like it´s done on this page: http://www.limburgweer.com/index_EN.html

/Mikael

-- 
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/a8e8659a-9954-403b-a3ab-a7128a1a7325%40googlegroups.com.


[weewx-user] Graphs/plots

2020-01-02 Thread gjr80
Nigel,

Indeed by the default the Seasons yearly plots plot daily average values, 
though rain plots a weekly sum and wind plots daily max. You might want to try 
either changing the default behaviour to plot the daily max value or override 
individual plots to plot the daily max. In the Seasons skin.conf locate the 
[ImageGenerator] stanza and under [[year_images]] either change the 
aggregate_type setting from avg to max (to set the default for all year plots) 
or under the individual plots set aggregate_type = max to override individual 
plots. Save skin.conf, no need to restart but unless you want to wait for up to 
a day for the plots to re-generate it’s best to the delete the plot image files 
to force regeneration on the next report cycle.

Gary

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


[weewx-user] Graphs/plots

2020-01-02 Thread Devonian
I have a VP2 with solar and UV sensors and would like to see the actual max 
figures in the plots.
I am using the Seasons skin and the daily/weekly/monthly plots all look 
good, however, the yearly plots look like an averaged figure (or an error?)
Take a look for yourself and you'll see what I mean:
http://www.nthead.co.uk/weewx/

I would like my plots to show the actual max observations, especially for 
the year plots as I am attempting to show a local club the radiation levels 
for a solar panels installation.
Is it an easy job to have the plots show the actual recordings?

Nigel.

-- 
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/2b792bd8-70e1-4d3e-8c78-5f6a558d0ba4%40googlegroups.com.


[weewx-user] Install skin Rabenwetter-template

2020-01-02 Thread engelbert Jan
Hi,
I'm new here. 
Is there anyone who has install the Rabenwetter-template. I have some trouble 
with it.
The install path is still no good.
Can you explain it to me.

Thanks Engelbert
https://www.weerstationbijdetoren.nl

-- 
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/8b1844e5-52e1-4e5e-8186-7e168d784bba%40googlegroups.com.


[weewx-user] Re: Issue Conversion with sdr driver and wind sensor WGR800

2020-01-02 Thread mwall
hello olivier,

this looks like a bug in the weewx-sdr driver.  for the OSWGR800 sensor, 
the text parser uses unit system of METRICWX, but the JSON parser users a 
unit system of METRIC.

you can fix your weewx-sdr driver by changing this:

pkt['usUnits'] = weewx.METRIC

to this:

pkt['usUnits'] = weewx.METRICWX

in sdr.py at function OSWGR800Packet.parse_json (should be line 2097 in the 
latest sdr.py)

or just download the latest sdr.py.

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/333de94d-021c-42f2-acee-42139662f305%40googlegroups.com.


[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

2020-01-02 Thread mwall
On Tuesday, December 31, 2019 at 1:51:42 PM UTC-5, G Hammer wrote:
>
> root@weewx1:~# service weewx stop
> root@weewx1:~# PYTHONPATH=/home/weewx/bin python 
> /home/weewx/bin/user/interceptor.py --device=fineoffset-bridge --port 8000 
> --debug
> raw data: 
> PASSKEY=D35&stationtype=GW1000B_V1.5.5&dateutc=2019-12-31+18:04:07&tempinf=72.1&humidityin=32&baromrelin=29.577&baromabsin=29.131&tempf=35.8&humidity=92&winddir=96&windspeedmph=0.00&windgustmph=0.00&maxdailygust=10.29&solarradiation=58.48&uv=0&rainratein=0.047&eventrainin=1.150&hourlyrainin=0.051&dailyrainin=0.118&weeklyrainin=1.150&monthlyrainin=3.780&yearlyrainin=6.138&totalrainin=6.138&wh65batt=0&wh26batt=0&freq=915M&model=GW1000_Pro


thank you for this.  i have added those field to weewx-interceptor as of 
0.48

i've got to focus on some weewx4 issues before i do more work on the 
weewx-interceptor, so apologies in advance for delays in my response

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/be4fec63-dc5a-447b-b805-7c8c6a9726f1%40googlegroups.com.


[weewx-user] Re: Connecting Froggit WH2600SE to Weewx - Setup always fails :(

2020-01-02 Thread mwall
as gábor pointed out, you do not need to specify the address parameter.  
that parameter is only necessary if you want to force the interceptor to 
listen on a specific network interface, and in that case the address must 
be a valid address for the computer on which weewx-interceptor is running.  
this is useful if the computer on which weewx-interceptor is running has 
multiple interfaces, for example wired and wireless, and you are using it 
as a network bridge.

in your case, the pi is 192.168.1.119.  so when you specify 
"address=192.168.1.122" the driver will fail, because that address is not 
available on the pi - only .119 is available.

for the froggit WH2600 (a fine offset device) there are two different 
drivers you could use:  the weewx-interceptor, or the observer driver by 
aussie susan. 

https://github.com/matthewwall/weewx-interceptor

https://github.com/AussieSusan/HP1000

they use two very different mechanisms to get data from the station.  the 
interceptor receives data transmitted by the observer - the observer thinks 
that the computer running weewx is a 'cloud' service.  the driver by susan 
uses the API of the observer itself, so that weewx can query the station 
for data.

here is some history about how these devices were reverse engineered:

https://github.com/weewx/weewx/wiki/observer

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/9ef749ba-fe7a-41bb-8427-0de883d3987a%40googlegroups.com.


[weewx-user] Re: ELV Mobile Alerts gateway MA 10000

2020-01-02 Thread mwall


On Thursday, January 2, 2020 at 11:27:20 AM UTC-5, Stefanie Drucker wrote:
>
> Update:
>
>- The Mobile Alerts REST API only supports some of their sensors - 
>most of my temp/hum sensors are not supported by the API.
>- I think the easiest way to gain sensor data is to parse the 
>measurements from a website that is provided by Mobile Alerts. There's no 
>password protection, all you need are the IDs of your weather station 
>('PhoneID') and the sensors, or even better the unique URLs showing the 
>last measurements for each sensor. For sorry these are HTML tables only, 
> no 
>XML format. But still should be no problem to parse the values.
>
> So sniffing is not required, just HTML parsing.
> I think then the interceptor is the wrong driver, right?
>

if you use tcpdump or some other tool to capture the tcp/ip traffic between 
your station and mobile alerts servers, then it would be possible to extend 
the weewx-interceptor driver to recognize that protocol.  or just create a 
standalone driver just for that protocol.

you could scrape and parse html from the mobile alerts web site, but that 
approach has many problems of its own.

it might be possible to write a driver that uses the mobile alerts API to 
get data from mobile alerts, but if mobile alerts does not support all of 
the sensors, then that does not seem like time well spent.

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/f85db606-4413-4ce3-98ca-b7a8c7835534%40googlegroups.com.


Re: [weewx-user] Mapping to proper USB-serial port - MacO/VantagePro2

2020-01-02 Thread David Bach
Thanks again! 

I started with *sudo pip install Cheetah --ignore-installed*

And the rest continued without incident. I updated weewx.config and the 
standard report and weewx has been running since I started it. The site is 
at letusgarden.org/weewx/.

I can't say how much I appreciate your prompt and helpful assistance! Does 
weewx.com have a way for donations?

So many times I encounter a hard stop that I don't know how to deal with it 
and when I can't find simple answers on the Internet I give up. 
Fortunately, for my pride and self confidence you were here to help.

So congratulations on an excellent software system! 

David


On Tuesday, December 31, 2019 at 2:58:54 PM UTC-8, Thomas Keffer wrote:
>
> Your version of setuptools, v1.1.6, is extremely old (the current version 
> is v43.0.0!) It looks like Cheetah needs version 36 or greater, so it's 
> trying an upgrade, but is unable to do so.
>
> The reason why is that pip is attempting to uninstall the old version of 
> setuptools, which is located under /System/Library, which is protected by 
> the Mac's "System Integrity Protection" (SIP). Even though you are running 
> as root, SIP won't let pip uninstall the old version. 
>
> What to do? You can try the option --ignore-installed. This will cause 
> pip to just go ahead with the install, and not try to uninstall the old 
> version. Because pip installs to /Library/Python, which is not protected by 
> SIP, it will succeed. 
>
> *sudo pip --install Cheetah --ignore-installed.*
>
>
> If you're uneasy about doing that, there are a few other options:
>
> 1. Install python by using brew. This will install a brand new version of 
> python in /usr/local, which is not protected by SIP. Then, using that 
> version of python, use pip to install the prerequisites. They will install 
> to /usr/local/lib.
>
> 2. Install python by using pyenv (this is what I do). This will install 
> python in ~/.pyenv, which, of course, is not protected.  An added benefit 
> is that pyenv allows you to manage many different versions of python. If 
> you run as a daemon, just use a direct path to the python executable. It 
> will automatically find the libraries installed by pip using that version 
> of python.
>
> 3. Install using pip, but use the --user flag. This will install in 
> ~/.local. No root privilege required. However, if you run as a daemon, you 
> will have to specify the library directory as a PYTHONPATH.
>
> Probably option #1 is easiest and safest.
>
> -tk
>
>
>
>
>
>
>
>
> On Tue, Dec 31, 2019 at 12:07 PM David Bach  > wrote:
>
>> thanks for the reply.
>>
>> here's the command-line output
>>
>> WeatherMini:~ dsbach$ sudo pip install Cheetah
>> DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 
>> 2020. Please upgrade your Python as Python 2.7 won't be maintained after 
>> that date. A future version of pip will drop support for Python 2.7. More 
>> details about Python 2 support in pip, can be found at 
>> https://pip.pypa.io/en/latest/development/release-process/#python-2-support
>> Processing 
>> ./Library/Caches/pip/wheels/27/8d/d0/7cee58a5a59f3c305cb1117416530229231440293e565030ff/Cheetah-2.4.4-cp27-cp27m-macosx_10_11_intel.whl
>> Collecting Markdown>=2.0.1
>>   Using cached 
>> https://files.pythonhosted.org/packages/c0/4e/fd492e91abdc2d2fcb70ef453064d980688762079397f779758e055f6575/Markdown-3.1.1-py2.py3-none-any.whl
>> Collecting setuptools>=36
>>   Using cached 
>> https://files.pythonhosted.org/packages/91/af/18d58ed8a8e7e6b91d71b0367034faf8ea41e1004018811388ed07a7f2d6/setuptools-43.0.0-py2.py3-none-any.whl
>> Installing collected packages: setuptools, Markdown, Cheetah
>>   Found existing installation: setuptools 1.1.6
>> Uninstalling setuptools-1.1.6:
>> ERROR: Could not install packages due to an EnvironmentError: 
>> [('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/_markerlib/__init__.py',
>>  
>> '/private/tmp/pip-uninstall-uEpSVa/__init__.py', "[Errno 1] Operation not 
>> permitted: '/private/tmp/pip-uninstall-uEpSVa/__init__.py'"), 
>> ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/_markerlib/__init__.pyc',
>>  
>> '/private/tmp/pip-uninstall-uEpSVa/__init__.pyc', "[Errno 1] Operation not 
>> permitted: '/private/tmp/pip-uninstall-uEpSVa/__init__.pyc'"), 
>> ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/_markerlib/markers.py',
>>  
>> '/private/tmp/pip-uninstall-uEpSVa/markers.py', "[Errno 1] Operation not 
>> permitted: '/private/tmp/pip-uninstall-uEpSVa/markers.py'"), 
>> ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/_markerlib/markers.pyc',
>>  
>> '/private/tmp/pip-uninstall-uEpSVa/markers.pyc', "[Errno 1] Operation not 
>> permitted: '/private/tmp/pip-uninstall-uEpSVa/markers.pyc'"), 
>> ('/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/_markerlib',
>>  
>> '/private/tmp/pip-uninstall-uEpSVa', "[Errno 1] Operation not 

[weewx-user] Re: ELV Mobile Alerts gateway MA 10000

2020-01-02 Thread Stefanie Drucker
Update:

   - The Mobile Alerts REST API only supports some of their sensors - most 
   of my temp/hum sensors are not supported by the API.
   - I think the easiest way to gain sensor data is to parse the 
   measurements from a website that is provided by Mobile Alerts. There's no 
   password protection, all you need are the IDs of your weather station 
   ('PhoneID') and the sensors, or even better the unique URLs showing the 
   last measurements for each sensor. For sorry these are HTML tables only, no 
   XML format. But still should be no problem to parse the values.

So sniffing is not required, just HTML parsing.
I think then the interceptor is the wrong driver, right?


Am Donnerstag, 2. Januar 2020 12:06:54 UTC+1 schrieb Stefanie Drucker:
>
> Thanks for the quick reply!
> I've already installed the interceptor and tried to receive data from my 
> weather station through it, but so far it didn't work...
> First, maybe it's not possible to connect the gateway to the weewx server 
> as it works with the GW-1000U.
> And second, the protocol is different.
>
> I think it's not necessary to reroute all the traffic to go only to weewx 
> any more instead of the Mobile Alerts cloud server. There is a REST API 
> they provide that allows to request the latest measurement data.
>
> And it also works with the Conrad Connect  
> service, where you can connect the station and use the data. That's nice 
> because you can build your own dashboards there and even connect with other 
> IFTT hardware.
> But it's not built to be a weather dashboard only, so I'm not satisfied 
> with the possibilities there - and some services have to be paid monthly...
>
>
> Am Donnerstag, 2. Januar 2020 01:00:56 UTC+1 schrieb mwall:
>>
>>
>>
>> On Wednesday, January 1, 2020 at 5:30:33 PM UTC-5, Stefanie Drucker wrote:
>>>
>>> Hi,
>>>
>>> I've bought a Mobile Alerts gateway and various sensors recently and 
>>> want to use it with weewx.
>>>
>>> This gateway is an European version of the LaCrosse GW-1000U. It looks 
>>> exactly the same, but obviously is different (see 
>>> https://github.com/sarnau/obileAlerts/blob/master/MobileAlertsELVvsLaCrosse.markdown
>>> ).
>>>
>>> Anyone has the same weather station and managed to set up weewx 
>>> receiving data from it?
>>>
>>
>> you can try the weewx-interceptor driver:
>>
>> https://github.com/matthewwall/weewx-interceptor
>>
>> set the device_type=lacrosse-bridge
>>
>> the lacross bridge has a rather complicated protocol.  try to configure 
>> as much as you can with the vendor's GAS program - at the very least you 
>> must tell the GW1000 to communicate with the computer that is running weewx 
>> (there is no passive sniffing mode for the lacross GW1000U).  and please 
>> read the comments about GW1000U in the interceptor.py file.  it is a bit 
>> technical, but you will probably have to tweak the serial number.
>>
>> finally, do not confuse the lacross GW1000U with the fine offset GW1000.  
>> froggit, ecowitt (and soon others?) sell the fine offset GW1000B and 
>> GW1000BU - 915MHz, the GW1000A - 868MHz, and the GW1000 - 433MHz.
>>
>> 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/401b7d5d-e746-43a5-920d-ab88455decf7%40googlegroups.com.


[weewx-user] Connecting Froggit WH2600SE to Weewx - Setup always fails :(

2020-01-02 Thread Gábor Szabados
Hi,

Try to remove address = 192.168.1.122. If it is still not working, then set the 
observerIP back to the default port and remove the port settings from the weewx 
config too.

If you read the interceptor manuals, you can see that interceptor can be run 
without weewx for testing too. Then you can see what is the right settings. 
https://github.com/matthewwall/weewx-interceptor/blob/master/readme

I guess you have installed interceptor and not just weewx.

Otherwise the wifi and ethernet config is the same. Both uses the same network 
protocol TCP/IP. No difference. You can read those topics.

Best Regards, 

Gabor Szabados 

-- 
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/8bc7c970-cd82-49b5-b6fa-159de59fcf30%40googlegroups.com.


[weewx-user] Re: ELV Mobile Alerts gateway MA 10000

2020-01-02 Thread Stefanie Drucker
Thanks for the quick reply!
I've already installed the interceptor and tried to receive data from my 
weather station through it, but so far it didn't work...
First, maybe it's not possible to connect the gateway to the weewx server 
as it works with the GW-1000U.
And second, the protocol is different.

I think it's not necessary to reroute all the traffic to go only to weewx 
any more instead of the Mobile Alerts cloud server. There is a REST API 
they provide that allows to request the latest measurement data.

And it also works with the Conrad Connect  
service, where you can connect the station and use the data. That's nice 
because you can build your own dashboards there and even connect with other 
IFTT hardware.
But it's not built to be a weather dashboard only, so I'm not satisfied 
with the possibilities there - and some services have to be paid monthly...


Am Donnerstag, 2. Januar 2020 01:00:56 UTC+1 schrieb mwall:
>
>
>
> On Wednesday, January 1, 2020 at 5:30:33 PM UTC-5, Stefanie Drucker wrote:
>>
>> Hi,
>>
>> I've bought a Mobile Alerts gateway and various sensors recently and want 
>> to use it with weewx.
>>
>> This gateway is an European version of the LaCrosse GW-1000U. It looks 
>> exactly the same, but obviously is different (see 
>> https://github.com/sarnau/obileAlerts/blob/master/MobileAlertsELVvsLaCrosse.markdown
>> ).
>>
>> Anyone has the same weather station and managed to set up weewx receiving 
>> data from it?
>>
>
> you can try the weewx-interceptor driver:
>
> https://github.com/matthewwall/weewx-interceptor
>
> set the device_type=lacrosse-bridge
>
> the lacross bridge has a rather complicated protocol.  try to configure as 
> much as you can with the vendor's GAS program - at the very least you must 
> tell the GW1000 to communicate with the computer that is running weewx 
> (there is no passive sniffing mode for the lacross GW1000U).  and please 
> read the comments about GW1000U in the interceptor.py file.  it is a bit 
> technical, but you will probably have to tweak the serial number.
>
> finally, do not confuse the lacross GW1000U with the fine offset GW1000.  
> froggit, ecowitt (and soon others?) sell the fine offset GW1000B and 
> GW1000BU - 915MHz, the GW1000A - 868MHz, and the GW1000 - 433MHz.
>
> 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/46274158-b376-4e81-8262-ea0b5fdf6e46%40googlegroups.com.


[weewx-user] Belchertown Weather Status Icon

2020-01-02 Thread 'Johannes Ebner' via weewx-user
Hi,

I have a funny issue with Weex and the Belchertown Skin.

I had the following Setup:
*) RPi Zero W
*) Raspbian Jessy Lite
*) Weewx 3.9.2
*) Belchertown Skin latest Beta

So far everything works fine, but I noticed from time to time that the 
current weather status icon is not shown.
Normaly you see the icon and if you check the link it looks like 
"/images/clear-day.png"

But from time to time I see no icon and on the default browser error icon I 
can see the following url: "/images/"

First I thought it is maybe due to the RPi Zero and to low performance so I 
took out the CFCard and moved it to a RPi 3 B+.
As this didnt solve the issue I cleaned up the Weewx Config (removed some 
extensions which I didnt need anymore). Now I have only the MQTT and 
Belchertown Extension installed.
Also the cleanup of the config didnt solve my issue. I was also not able to 
see any error messages in the logs.

Now I have setup a complete new installation on a RPi 4+. I only took over 
the settings for Belchertown to weewx.conf and the graphs.conf for the 
Skin. At the moment I am using this setup with the simulator driver.
The setup works basically except again the Weather Icon. This time it is 
never aperaing correctly... 

Any ideas or hints?

Best Regards,
Johannes

-- 
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/8373c911-4447-4b4f-ac7e-b43d2f2ad777%40googlegroups.com.