[weewx-user] Re: Belchertown skin 1.0 released!

2019-09-02 Thread Stefan
Good Morning.
I noticed that the gusts of wind with the meteostick are not always 
automatically updated. I think that this has to do explicitly with the 
meteostick. The gusts of wind are always updated with the set update by 
weewx, but not running. The wind, however, works with the live interval. Has 
anyone else observed and is there a solution? You can see this here: 
https://www.meteo-oberwallis.ch/wetter/eggishorn/user/

Many thanks

Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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/931b360d-50a4-4d6e-bd2c-7116d52ea015%40googlegroups.com.


[weewx-user] Re: MQTT Weewx authentication

2019-09-02 Thread Xant

I went through MAAANY hours in this issue... and the following is what 
works 4me.

WeeWX conf:

[[MQTT]]
#X server_url = mqtt://test.mosquitto.org:1883/
#X server_url = mqtt://broker.hivemq.com:1883/
server_url = mqtt://[user:pw]@localhost:1883/
topic = weather
unit_system = US
binding = archive, loop
aggregation = aggregate

Belchertown skin:

# MQTT Websockets defaults
mqtt_websockets_enabled = 1
#X mqtt_websockets_host = test.mosquitto.org
#X mqtt_websockets_port = 8080
#X mqtt_websockets_host = broker.hivemq.com
#X mqtt_websockets_port = 8000
mqtt_websockets_host = [ur URL]
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = "weather/loop"
#X disconnect_live_website_visitor = 180

Uncomment the above as you wish. Try a free public MQTT (before local), as 
Mosquitto or HiveMQ as the above...

Remember to set your router port forwarding as well...

Xant

-- 
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/69663524-1a65-4058-95e2-a29eecda1a01%40googlegroups.com.


[weewx-user] Re: WeatherFlow - any feedback regarding WeeWX

2019-09-02 Thread Xant
Just got WF... so far, Im impress...

Pros:

   - much sensors than any other, at this price point
   - MQTT updates at <3secs (maybe due to wind, but looks like a Davis); I 
   never had MQTT turn-out that quick... besides the 60sec actual loop update 
   timeframe (weewx website seems much quicker than "is"; but that is a 
   good thing... others lag till MQTT "connects")
   - easy to install an NO moving parts (impressive... other "early" 
   sellers were charging $1,000+ (without all this sensors) for the same "no 
   moving feature"
   - splitting in 2 units (actually 3 if you count Hub), it counts for REAL 
   OutTemp, as temp sensor does not have to be exposed in direct Sun (without 
   the need of any "radiator")
   

Cons:

   - NOT Static IP (commo; specially for us WeeWX peps!; it 
   works other-else, but rather have Static)
   - NOT net hard-wire to Hub (as I would prefer, but only WiFi)


As for this post, it seems "I can leave with the Cons, but would appreciate 
even more if addressed.

So far, better than Acurite Atlas, better than Ambient Weather WS-1550-IP 
(with ObserverIP).

Dont get me wrong... Atlas and WS-1550-IP are great price-point for the 
regular Weather Home... but not for the WeeWX geek.


Xant

-- 
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/58782f9d-ffb4-432b-8d5c-a9868aeae2fd%40googlegroups.com.


[weewx-user] Re: Acurite Atlas Help

2019-09-02 Thread Xant
Interceptor Driver by Matthew Wall:

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

Xant

-- 
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/c94ee6d6-497e-4a8c-833a-157f52e665f8%40googlegroups.com.


[weewx-user] Re: Acurite Atlas Help

2019-09-02 Thread Tor rin
You are going to need to give us a lot more information on your setup (what 
is plugged into what, how are you capturing the data), your configuration 
file and logs after you turn on debug in your weewx.cfg file.  

On Monday, September 2, 2019 at 8:07:50 AM UTC-5, Paul Levin wrote:
>
> Hi,
>
> I've been trying unsuccessfully to install weewx on my Raspberry Pi 4.I 
> have an Acurite Atlas and Access.
>
> My problem I believe lies in the is the configuration file entries. I have 
> Weather Station Type = Simulator and device _type = wu-client. I previously 
> tried Acurite-Bridge, but that didn't work either. 
>
> At best, I was able to bring up the simulation web page, but never a page 
> with my own data. Can anyone please help? 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/ce57c25a-5bb4-4981-9600-39cb6803fd2b%40googlegroups.com.


Re: [weewx-user] Re: How do i change the type of aggregation record that is created for a custom data source?

2019-09-02 Thread Thomas Carlin
Just wanted to confirm for any reading this later, After fixing my sensor 
issues, this change did exactly what I needed to do, and I am now seeing 
SUM values instead of average in the archive packets.

Thanks again,

On Sunday, September 1, 2019 at 5:27:27 PM UTC-6, Thomas Carlin wrote:
>
> I think you may be correct... It looks like only half or so of the data 
> was actually pulling from the sensors.  I'll have to figure that issue out, 
> but it doesn't look like the problem was in the config changes we made.  
>
> Thanks again Tom!
>
> On Sunday, September 1, 2019 at 5:04:24 PM UTC-6, Thomas Keffer wrote:
>>
>> Hmmm.
>>
>> If you run weewxd directly from the console command line, what values do 
>> you see go by on the console?
>>
>> On Sun, Sep 1, 2019 at 3:18 PM Thomas Carlin  wrote:
>>
>>> Thanks Tom,
>>>
>>> Thanks for the fast response!  I created the section that you said in 
>>> weewx.conf, see below, and now I don't get any data in the archive table, 
>>> also included below, with previous AVG values for comparison sake.  
>>> Suggestions?
>>>
>>> [Accumulator]
>>> [[kwh]]
>>> extractor = sum
>>> [[IrrigationFlow]]
>>> extractor = sum
>>> sqlite> select datetime, kwh, IrrigationFlow from archive where datetime 
>>> >=1567374900;
>>> dateTime|kwh|IrrigationFlow
>>> 1567374900|0.009349|0.0
>>> 1567375200|0.0100596551724138|0.0
>>> 1567375800||
>>> 1567376100||
>>> sqlite>
>>>
>>>
>>> ?
>>>
>>>
>>>
>>> On Sunday, September 1, 2019 at 3:20:00 PM UTC-6, Thomas Carlin wrote:

 Good afternoon, I hope everyone is enjoying their labor day weekend!

 I have a custom data source that I wrote a driver for, and have 
 recently changed it from pulling data when the archive packet is created, 
 to when the loop packet is received.  This is working well, and everything 
 is pulling correctly, but now I have an issue with the creation of the 
 archive packet.  Previously, the device that I received the data from 
 performed the aggregation, but now it is producing much more frequent 
 information, and the driver/weewx service needs to handle the aggregation. 
  

 Several of my data sources are similar to 'rain' where I want to count 
 the total of something used or collected, and it looks like the archive 
 packet is created using the average.  Based on the documentation, I need 
 to 
 implement genArchiveRecords() for these to specify how the data is 
 aggregated, but I can't find any example code of how this is done.  Could 
 you please point me in the correct direction for modifying this, or to a 
 driver with some example code that I can modify for my needs?

 If this is more fitting for the development group, please move it there.

 Many thanks,

 Thomas

>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/c323ce23-ff42-42fe-988c-14df56e7deb6%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/d015522c-5f7e-4742-8b24-f307adfe7796%40googlegroups.com.


[weewx-user] Re: Changing QoS when publishing to Mosquitto through Weewx

2019-09-02 Thread vince
On Monday, September 2, 2019 at 9:11:01 AM UTC-7, Rui Pinto wrote:
>
> I have a Davis Vantage Pro2 station and i'm using Weewx to publish data to 
> an MQTT broker (Mosquitto).
>
> But i would like to know if it's possible to change the QoS.
>
>
>
My reading of the mqtt extension v0.19 sources vs. some paho-mqtt examples 
says 'no', but if you wanted to hack on your extension a little you might 
try finding the two lines that say mc.publish and add qos=1 (or 2) and see 
if that works. (untested)

 

-- 
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/0b26bd48-a107-443b-b5cb-5805975c8af1%40googlegroups.com.


[weewx-user] Changing QoS when publishing to Mosquitto through Weewx

2019-09-02 Thread Rui Pinto
Hello!!


I have a Davis Vantage Pro2 station and i'm using Weewx to publish data to 
an MQTT broker (Mosquitto).

But i would like to know if it's possible to change the QoS.

Best Regards.

-- 
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/115bc8d5-d7c1-4df4-a61f-72b157a1b599%40googlegroups.com.


Re: [weewx-user] Error in Humidity in Wundergound Post

2019-09-02 Thread Thomas Keffer
Looking at KCAORANG21, the WU is receiving low values for pressure on the
hour, although with the WU, you never really know. But, given that you are
cycling the wifi adapter at exactly the same time, odds are that the
problem is on your end, rather than on the WU end.

I am not familiar with the wmii driver but, looking through its code, it
ignores the checksum, so it's entirely possible it is receiving a bad
packet on the hour, which gets decoded into nonsense values. The many bad
values logged give evidence to this theory. For example,

Sep  1 08:29:17 raspberrypi weewx[425]: engine: 2019-09-01 08:29:17 PDT
(1567351757) LOOP value 'pressure' -29.33 outside limits (24.0, 34.5)
Sep  1 08:29:17 raspberrypi weewx[425]: engine: 2019-09-01 08:29:17 PDT
(1567351757) LOOP value 'outHumidity' 128 outside limits (0.0, 100.0)
Sep  1 08:29:17 raspberrypi weewx[425]: engine: 2019-09-01 08:29:17 PDT
(1567351757) LOOP value 'outTemp' 3276.7 outside limits (-40.0, 120.0)
Sep  1 08:29:18 raspberrypi weewx[425]: engine: 2019-09-01 08:29:18 PDT
(1567351758) LOOP value 'pressure' -29.33 outside limits (24.0, 34.5)
Sep  1 08:29:18 raspberrypi weewx[425]: engine: 2019-09-01 08:29:18 PDT
(1567351758) LOOP value 'outHumidity' 128 outside limits (0.0, 100.0)

So, when weewx calculates the average pressure for the interval, it gets an
off value. Incidentally, you're getting low values for other types, such as
outside temperature. They are probably suffering from the same problem.

You should contact the author of the driver. It really should use the
checksum. Garbage in, garbage out! :-)

-tk

On Mon, Sep 2, 2019 at 8:14 AM William Webb  wrote:

> You are correct I somehow got fixated on Humidity.  The issue is
> pressure.  My station is KCAORANG21.  My log is attached.
>
> On Monday, September 2, 2019 at 7:27:05 AM UTC-7, Thomas Keffer wrote:
>>
>> I'm not sure what we're looking at here. It looks more a plot of
>> barometric pressure, rather than humidity.
>>
>> Or, is the issue the plot on the top (which is always zero)?
>>
>> Your WU station ID would be helpful. And, of course, the log. See the
>> wiki article *Help! Posting to weewx-user
>> *.
>>
>> In short, you're not giving us much information.
>>
>>
>>
>>
>> On Mon, Sep 2, 2019 at 7:00 AM William Webb  wrote:
>>
>>> This is a perplexing problem.  I don't know enough about the structure
>>> of weewx code or the Davis Monitor II driver to hazard a guess.  My
>>> station, a Davis Monitor II, running on a Raspberry PI B+ appears to be
>>> working fine without drama.  The PI has an IP assigned outside of DHCP on a
>>> Spectrum Gateway router. I have always had stability issues between PIs and
>>> Spectrum.  I have avoided the random disconnects by running this on the
>>> hour as a chron task.
>>>
>>> #!/bin/bash
>>>
>>> sudo ifconfig wlan0 down
>>>
>>> sudo ifconfig wlan0 up
>>>
>>> sudo service networking restart
>>>
>>>
>>>  I let the setup run several days before enabling posting to
>>> Wundergound.  My data when views on the web site locally looked fine.  When
>>> I looked at my data on WundergroundI discovered an anomaly with humidity.
>>> After the chron task ran the humidity read low for one reading.
>>>
>>> [image: Wu_report.jpg]
>>>
>>>
>>> This is beyond weird. Only humidity is off and it is only the first
>>> reading after the network reconnect.  What could be wrong?  Have I
>>> discovered some really subtle bug?  If you folks think so, I can repost on
>>> the development forum.
>>>
>>>
>>> Bill - AB6OR
>>>
>>>
>>>
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/1b8556bc-ea98-4b1c-b97d-06a95d075631%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/7a219d4b-07d1-4757-8511-e1314619be57%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] Error in Humidity in Wundergound Post

2019-09-02 Thread William Webb
P.S for now I shut down the Chron task.

Bill

On Monday, September 2, 2019 at 8:14:43 AM UTC-7, William Webb wrote:
>
> You are correct I somehow got fixated on Humidity.  The issue is 
> pressure.  My station is KCAORANG21.  My log is attached.
>
> On Monday, September 2, 2019 at 7:27:05 AM UTC-7, Thomas Keffer wrote:
>>
>> I'm not sure what we're looking at here. It looks more a plot of 
>> barometric pressure, rather than humidity.
>>
>> Or, is the issue the plot on the top (which is always zero)?
>>
>> Your WU station ID would be helpful. And, of course, the log. See the 
>> wiki article *Help! Posting to weewx-user 
>> *.
>>
>> In short, you're not giving us much information.
>>
>>
>>
>>
>> On Mon, Sep 2, 2019 at 7:00 AM William Webb  wrote:
>>
>>> This is a perplexing problem.  I don't know enough about the structure 
>>> of weewx code or the Davis Monitor II driver to hazard a guess.  My 
>>> station, a Davis Monitor II, running on a Raspberry PI B+ appears to be 
>>> working fine without drama.  The PI has an IP assigned outside of DHCP on a 
>>> Spectrum Gateway router. I have always had stability issues between PIs and 
>>> Spectrum.  I have avoided the random disconnects by running this on the 
>>> hour as a chron task.
>>>
>>> #!/bin/bash
>>>
>>> sudo ifconfig wlan0 down
>>>
>>> sudo ifconfig wlan0 up
>>>
>>> sudo service networking restart
>>>
>>>  
>>>  I let the setup run several days before enabling posting to 
>>> Wundergound.  My data when views on the web site locally looked fine.  When 
>>> I looked at my data on WundergroundI discovered an anomaly with humidity.  
>>> After the chron task ran the humidity read low for one reading.
>>>
>>> [image: Wu_report.jpg]
>>>
>>>
>>> This is beyond weird. Only humidity is off and it is only the first 
>>> reading after the network reconnect.  What could be wrong?  Have I 
>>> discovered some really subtle bug?  If you folks think so, I can repost on 
>>> the development forum.
>>>
>>>
>>> Bill - AB6OR
>>>
>>>
>>>
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/1b8556bc-ea98-4b1c-b97d-06a95d075631%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/08df3f9c-a97f-47ff-9867-21b4c33a125c%40googlegroups.com.


Re: [weewx-user] Re: What is the data structured published to the MQTT broker with Weewx stdRESTful service

2019-09-02 Thread Greg Troxel
Rui Pinto  writes:

> Another curiosity question:
>
> - Why all the variables are published in floats?

Because that is the natural computer represntation for the underlying
data, except alarms, and maybe dates.

Keep in mind that mqtt publishes octect sequences, not objects with
types.

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


Re: [weewx-user] What is the data structured published to the MQTT broker with Weewx stdRESTful service

2019-09-02 Thread Greg Troxel
Rui Pinto  writes:

> I have a Davis Vantage Pro2 station and i'm using Weewx to publish data to 
> an MQTT broker (Mosquitto) and i would like to know if the data that i'm 
> pusblishing to a specific topic is structured in JSON?

I just updated the wiki page a bit.   Basically:

  aggregrate publishes json to $TOPIC/loop
  individual publishes plain values (I think) to $TOPIC/dewpoint_F
  (etc.)

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

But, if it is being published, use mosquitto_sub or something like that
and look at what you are publishing.

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


[weewx-user] Re: Error in Humidity in Wundergound Post

2019-09-02 Thread William Webb


On Monday, September 2, 2019 at 7:00:33 AM UTC-7, William Webb wrote:
>
> This is a perplexing problem.  I don't know enough about the structure of 
> weewx code or the Davis Monitor II driver to hazard a guess.  My station, a 
> Davis Monitor II, running on a Raspberry PI B+ appears to be working fine 
> without drama.  The PI has an IP assigned outside of DHCP on a Spectrum 
> Gateway router. I have always had stability issues between PIs and 
> Spectrum.  I have avoided the random disconnects by running this on the 
> hour as a chron task.
>
> #!/bin/bash
>
> sudo ifconfig wlan0 down
>
> sudo ifconfig wlan0 up
>
> sudo service networking restart
>
>  
>  I let the setup run several days before enabling posting to Wundergound.  
> My data when views on the web site locally looked fine.  When I looked at 
> my data on WundergroundI discovered an anomaly with humidity.  After the 
> chron task ran the humidity read low for one reading.
>
> [image: Wu_report.jpg]
>
>
> This is beyond weird. Only pressure is off and it is only the first 
> reading after the network reconnect.  What could be wrong?  Have I 
> discovered some really subtle bug?  If you folks think so, I can repost on 
> the development forum.
>
>
> Bill - AB6OR
>
>
>
>
>

-- 
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/b15bef49-b1e0-4f30-9df5-e490b8c33834%40googlegroups.com.


[weewx-user] Re: What is the data structured published to the MQTT broker with Weewx stdRESTful service

2019-09-02 Thread Rui Pinto
Another curiosity question:

- Why all the variables are published in floats?

-- 
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/731a6792-b211-4e49-b986-8e3b91afe204%40googlegroups.com.


[weewx-user] What is the data structured published to the MQTT broker with Weewx stdRESTful service

2019-09-02 Thread Rui Pinto
Hello!!

I have a Davis Vantage Pro2 station and i'm using Weewx to publish data to 
an MQTT broker (Mosquitto) and i would like to know if the data that i'm 
pusblishing to a specific topic is structured in JSON?


Best Regards.

-- 
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/d3e0cdf6-1e3d-4384-af9b-cf610e0b10b3%40googlegroups.com.


Re: [weewx-user] Error in Humidity in Wundergound Post

2019-09-02 Thread Thomas Keffer
I'm not sure what we're looking at here. It looks more a plot of barometric
pressure, rather than humidity.

Or, is the issue the plot on the top (which is always zero)?

Your WU station ID would be helpful. And, of course, the log. See the wiki
article *Help! Posting to weewx-user
*.

In short, you're not giving us much information.




On Mon, Sep 2, 2019 at 7:00 AM William Webb  wrote:

> This is a perplexing problem.  I don't know enough about the structure of
> weewx code or the Davis Monitor II driver to hazard a guess.  My station, a
> Davis Monitor II, running on a Raspberry PI B+ appears to be working fine
> without drama.  The PI has an IP assigned outside of DHCP on a Spectrum
> Gateway router. I have always had stability issues between PIs and
> Spectrum.  I have avoided the random disconnects by running this on the
> hour as a chron task.
>
> #!/bin/bash
>
> sudo ifconfig wlan0 down
>
> sudo ifconfig wlan0 up
>
> sudo service networking restart
>
>
>  I let the setup run several days before enabling posting to Wundergound.
> My data when views on the web site locally looked fine.  When I looked at
> my data on WundergroundI discovered an anomaly with humidity.  After the
> chron task ran the humidity read low for one reading.
>
> [image: Wu_report.jpg]
>
>
> This is beyond weird. Only humidity is off and it is only the first
> reading after the network reconnect.  What could be wrong?  Have I
> discovered some really subtle bug?  If you folks think so, I can repost on
> the development forum.
>
>
> Bill - AB6OR
>
>
>
>
> --
> 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/1b8556bc-ea98-4b1c-b97d-06a95d075631%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/CAPq0zEB%3Dn%2B_V5i_gf040tNpsq%2BvwxTb-zAVPC1F6H4wtZ%2BT09Q%40mail.gmail.com.


[weewx-user] Re: MQTT Weewx authentication

2019-09-02 Thread Rui Pinto
Thank you very much for the help!!


Another question:

- Is it possible to change the QoS of the MQTT client (weewx)?

quinta-feira, 29 de Agosto de 2019 às 12:08:13 UTC+1, Rui Pinto escreveu:
>
> Hello!!
>
> I'm trying to publish data to a topic in the Mosquitto broker through 
> authentication. 
> I succedd without authentication but i wanted to publish data with 
> authentication.
>
> I successfully changed the user and password in the mosquitto 
> configurations, but i don't know where do i put the username and password 
> in the Weewx configurations.
>
> I don't know if i have to put the username and password in the weew.conf 
> file...
> Here's my configuration of MQTT in Weewx.conf: 
>
> [StdRESTful]
> [[MQTT]]
>server_url = mqtt://localhost:1883/
>topic = weewx/default/default/VantagePro2
>unit_system = METRIC
>

-- 
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/cc0c2211-faf7-4e73-99f6-633d49f29f76%40googlegroups.com.


Re: [weewx-user] Looking for sample weewx.conf file that includes two sensor sources for Vantage Pro

2019-09-02 Thread Jacques Terrettaz
Is your VP2 console communicating wirelessly with the ISS ?  If this is the 
case, you could configure your VP2 console to receive temp/hum/rain date 
from ISS (id=1) and wind data  from the anemometer transmitter (id=2). No 
need to have a separate Envoy to capture wind data, and no need to change 
weewx configuration. 

Le samedi 31 août 2019 01:43:25 UTC+2, Bob Borzelleri a écrit :
>
> Thanks.  The data logger in the Envoy is collecting wind data from the 
> separate station, it's just not showing up in Weewx.  It does show up in 
> WeatherLink 6.0.3.  
>
>>
>>
>>

-- 
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/6eafd5c3-a8d6-42ab-bae4-6988c63c9645%40googlegroups.com.


[weewx-user] Error in Humidity in Wundergound Post

2019-09-02 Thread William Webb
This is a perplexing problem.  I don't know enough about the structure of 
weewx code or the Davis Monitor II driver to hazard a guess.  My station, a 
Davis Monitor II, running on a Raspberry PI B+ appears to be working fine 
without drama.  The PI has an IP assigned outside of DHCP on a Spectrum 
Gateway router. I have always had stability issues between PIs and 
Spectrum.  I have avoided the random disconnects by running this on the 
hour as a chron task.

#!/bin/bash

sudo ifconfig wlan0 down

sudo ifconfig wlan0 up

sudo service networking restart

 
 I let the setup run several days before enabling posting to Wundergound.  
My data when views on the web site locally looked fine.  When I looked at 
my data on WundergroundI discovered an anomaly with humidity.  After the 
chron task ran the humidity read low for one reading.

[image: Wu_report.jpg]


This is beyond weird. Only humidity is off and it is only the first reading 
after the network reconnect.  What could be wrong?  Have I discovered some 
really subtle bug?  If you folks think so, I can repost on the development 
forum.


Bill - AB6OR




-- 
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/1b8556bc-ea98-4b1c-b97d-06a95d075631%40googlegroups.com.


[weewx-user] Re: Belchertown skin 1.0 released!

2019-09-02 Thread Pat
That's one option, so I'm glad it's working. 

The other option is to change the StringFormats float value km_per_hour in 
weewx.conf (then restart weewx once changes). The skin should be using this 
value, so changing it here will update it without changing the code in the 
skin. (something to keep in mind for future skin updates in case it reverts 
back)

On Monday, September 2, 2019 at 7:39:45 AM UTC-4, Stefan wrote:
>
> Hello Andrew.
>
> That`s Works. Thank You very much :-D
>
> Am Montag, 2. September 2019 08:12:20 UTC+2 schrieb Andrew Milner:
>>
>> in the code you edited - have you tried changing maximumfractiondigits 
>> and minimumfractiondigits from 1 to 0?  It seems to me - without having the 
>> skin - that this should do what you want  If it does not do the trick 
>> then put it back to 1 and wait for Pat!!
>>
>>
>>
>> On Monday, 2 September 2019 09:04:07 UTC+3, Stefan wrote:
>>>
>>> Hello.
>>> I wanted to ask if the wind values (in the live view) could be displayed 
>>> as a whole, without them? I mean that. Currently, the values are always 
>>> displayed with 3.2 km/h, but more interesting would be 3 km/h. Is that 
>>> possible?
>>>
>>> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:

 Belchertown skin 1.0 is released!

 This update contains a lot of updates and changes including *an entire 
 rewrite of the Highcharts system* which allows you to make almost any 
 graph you want for almost any time span you want. You can see some 
 examples 
 of the charts you can make on the BelchertownWeather.com website 
 graphs page .

 You can add/remove/change/reorder any chart, change colors, add 
 observation plots, categorize for all time. Almost anything you want to do 
 is available! The skin comes with the standard 4 charts ready to go, but 
 there's extensive Belchertown Charts Documentation 
 
  
 which can help you get started. 

 In addition to the Charts there's now a dark mode (which has an 
 auto-switching mode based on sunset/sunrise), more flexibility for 
 translations, user customized station observation table which is updated 
 in 
 real time if the MQTT Websockets are enabled, and a lot more. Check the 
 release notes for all the details! 

 You can download the latest release here 
 ,
  
 and read all of the details on the changes here: 
 https://github.com/poblabs/weewx-belchertown/releases

 *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
 uninstall everything and reinstall new. This is due to the Chart system 
 being fully rewritten and the potential for conflicts. Please read 
 this upgrade guide if you are upgrading from an older version of 
 Belchertown skin 
 
 . 

 Thanks to all the beta testers and translators over the last couple of 
 months help me iron out all the kinks and shape the skin in a way that can 
 be translated a little easier! 

 Attached are some examples of the charts that can be made. If you find 
 any issues, you can reply here or open an issue on the Belchertown 
 skin GitHub page . 

>>>

-- 
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/10f6c74d-7eca-4028-9f20-b69f4b8206a2%40googlegroups.com.


[weewx-user] Acurite Atlas Help

2019-09-02 Thread Paul Levin
Hi,

I've been trying unsuccessfully to install weewx on my Raspberry Pi 4.I 
have an Acurite Atlas and Access.

My problem I believe lies in the is the configuration file entries. I have 
Weather Station Type = Simulator and device _type = wu-client. I previously 
tried Acurite-Bridge, but that didn't work either. 

At best, I was able to bring up the simulation web page, but never a page 
with my own data. Can anyone please help? 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/cbced64f-e30a-4f35-ac1d-b8d40e29bdaf%40googlegroups.com.


[weewx-user] Re: Belchertown skin 1.0 released!

2019-09-02 Thread Stefan
Hello Andrew.

That`s Works. Thank You very much :-D

Am Montag, 2. September 2019 08:12:20 UTC+2 schrieb Andrew Milner:
>
> in the code you edited - have you tried changing maximumfractiondigits and 
> minimumfractiondigits from 1 to 0?  It seems to me - without having the 
> skin - that this should do what you want  If it does not do the trick 
> then put it back to 1 and wait for Pat!!
>
>
>
> On Monday, 2 September 2019 09:04:07 UTC+3, Stefan wrote:
>>
>> Hello.
>> I wanted to ask if the wind values (in the live view) could be displayed 
>> as a whole, without them? I mean that. Currently, the values are always 
>> displayed with 3.2 km/h, but more interesting would be 3 km/h. Is that 
>> possible?
>>
>> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>>>
>>> Belchertown skin 1.0 is released!
>>>
>>> This update contains a lot of updates and changes including *an entire 
>>> rewrite of the Highcharts system* which allows you to make almost any 
>>> graph you want for almost any time span you want. You can see some examples 
>>> of the charts you can make on the BelchertownWeather.com website graphs 
>>> page .
>>>
>>> You can add/remove/change/reorder any chart, change colors, add 
>>> observation plots, categorize for all time. Almost anything you want to do 
>>> is available! The skin comes with the standard 4 charts ready to go, but 
>>> there's extensive Belchertown Charts Documentation 
>>> 
>>>  
>>> which can help you get started. 
>>>
>>> In addition to the Charts there's now a dark mode (which has an 
>>> auto-switching mode based on sunset/sunrise), more flexibility for 
>>> translations, user customized station observation table which is updated in 
>>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>>> release notes for all the details! 
>>>
>>> You can download the latest release here 
>>> ,
>>>  
>>> and read all of the details on the changes here: 
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>>> uninstall everything and reinstall new. This is due to the Chart system 
>>> being fully rewritten and the potential for conflicts. Please read this 
>>> upgrade guide if you are upgrading from an older version of Belchertown 
>>> skin 
>>> 
>>> . 
>>>
>>> Thanks to all the beta testers and translators over the last couple of 
>>> months help me iron out all the kinks and shape the skin in a way that can 
>>> be translated a little easier! 
>>>
>>> Attached are some examples of the charts that can be made. If you find 
>>> any issues, you can reply here or open an issue on the Belchertown skin 
>>> GitHub page . 
>>>
>>

-- 
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/c9d7a9df-9dcf-45bb-b0ca-7120e220a03e%40googlegroups.com.


[weewx-user] Re: Caught unrecoverable exception in engine

2019-09-02 Thread Jan Sundström
Solved, I had a space after decimal. Removed it and now its not abending.
Thanks

Den måndag 2 september 2019 kl. 11:32:49 UTC+2 skrev Jan Sundström:
>
> Weatherstation is a Eurochron EFWS2900 (WH2900). The goal is to have Weewx 
> running on the local network and nothing in cloud, ie *I want WEEWX to 
> take the information directly from the weatherstation.*
>
> Installed WEEWX, Interceptor and HP1000. Have tried different settings but 
> no luck.
>
> Dont know for sure that what I am trying i doable, but I have found 
> examples with similar weatherstations.
>
>  
>
>  
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Using configuration file 
> /etc/weewx/weewx.conf
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Debug is 1
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Initializing engine
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Loading station type 
> HP1000 (user.HP1000)
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: HP1000 Starting
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Using user-defined 
> broadcast mask - 192.168.1.7
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Address Mask = 192.168.1.7
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Retry count = 5.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Socket timeout = 5.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Loop delay = 15.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Retry Wait = 5.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Max Retry = 3.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Caught unrecoverable 
> exception in engine:
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  float() argument must be a 
> string or a number
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  Traceback (most recent call 
> last):
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/engine.py", line 888, in main
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  engine = 
> engine_class(config_dict)
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  
> self.preLoadServices(config_dict)
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/engine.py", line 116, in preLoadServices
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  self.stn_info = 
> weewx.station.StationInfo(self.console, **config_dict['Station'])
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/station.py", line 49, in __init__
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  self.latitude_f = 
> float(stn_dict['latitude'])
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  TypeError: float() argument 
> must be a string or a number
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  Exiting.
>
>  
>

-- 
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/c159be86-4b49-4664-94c2-3223d1230d09%40googlegroups.com.


[weewx-user] Re: Caught unrecoverable exception in engine

2019-09-02 Thread Andrew Milner
the error you have posted is saying that latitude (which is weewx.conf) has 
not been specified correctly.

should be specified in decimal degrees.

see [Station] section of 
http://weewx.com/docs/usersguide.htm#Option_hierarchy



On Monday, 2 September 2019 12:32:49 UTC+3, Jan Sundström wrote:
>
> Weatherstation is a Eurochron EFWS2900 (WH2900). The goal is to have Weewx 
> running on the local network and nothing in cloud, ie *I want WEEWX to 
> take the information directly from the weatherstation.*
>
> Installed WEEWX, Interceptor and HP1000. Have tried different settings but 
> no luck.
>
> Dont know for sure that what I am trying i doable, but I have found 
> examples with similar weatherstations.
>
>  
>
>  
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Using configuration file 
> /etc/weewx/weewx.conf
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Debug is 1
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Initializing engine
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Loading station type 
> HP1000 (user.HP1000)
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: HP1000 Starting
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Using user-defined 
> broadcast mask - 192.168.1.7
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Address Mask = 192.168.1.7
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Retry count = 5.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Socket timeout = 5.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Loop delay = 15.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Retry Wait = 5.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Max Retry = 3.00
>
> Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Caught unrecoverable 
> exception in engine:
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  float() argument must be a 
> string or a number
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  Traceback (most recent call 
> last):
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/engine.py", line 888, in main
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  engine = 
> engine_class(config_dict)
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  
> self.preLoadServices(config_dict)
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/engine.py", line 116, in preLoadServices
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  self.stn_info = 
> weewx.station.StationInfo(self.console, **config_dict['Station'])
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
> "/usr/share/weewx/weewx/station.py", line 49, in __init__
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  self.latitude_f = 
> float(stn_dict['latitude'])
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  TypeError: float() argument 
> must be a string or a number
>
> Sep 1 19:31:11 raspberrypi weewx[2387]:  Exiting.
>
>  
>

-- 
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/b46ee380-01f0-4559-ad0d-19e40d9b9c01%40googlegroups.com.


[weewx-user] Caught unrecoverable exception in engine

2019-09-02 Thread Jan Sundström
 

Weatherstation is a Eurochron EFWS2900 (WH2900). The goal is to have Weewx 
running on the local network and nothing in cloud, ie *I want WEEWX to take 
the information directly from the weatherstation.*

Installed WEEWX, Interceptor and HP1000. Have tried different settings but 
no luck.

Dont know for sure that what I am trying i doable, but I have found 
examples with similar weatherstations.

 

 

Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Using configuration file 
/etc/weewx/weewx.conf

Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Debug is 1

Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Initializing engine

Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Loading station type HP1000 
(user.HP1000)

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: HP1000 Starting

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Using user-defined 
broadcast mask - 192.168.1.7

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Address Mask = 192.168.1.7

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Retry count = 5.00

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Socket timeout = 5.00

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Loop delay = 15.00

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Retry Wait = 5.00

Sep 1 19:31:11 raspberrypi weewx[2387]: HP1000: Max Retry = 3.00

Sep 1 19:31:11 raspberrypi weewx[2387]: engine: Caught unrecoverable 
exception in engine:

Sep 1 19:31:11 raspberrypi weewx[2387]:  float() argument must be a 
string or a number

Sep 1 19:31:11 raspberrypi weewx[2387]:  Traceback (most recent call 
last):

Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
"/usr/share/weewx/weewx/engine.py", line 888, in main

Sep 1 19:31:11 raspberrypi weewx[2387]:  engine = 
engine_class(config_dict)

Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

Sep 1 19:31:11 raspberrypi weewx[2387]:  
self.preLoadServices(config_dict)

Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
"/usr/share/weewx/weewx/engine.py", line 116, in preLoadServices

Sep 1 19:31:11 raspberrypi weewx[2387]:  self.stn_info = 
weewx.station.StationInfo(self.console, **config_dict['Station'])

Sep 1 19:31:11 raspberrypi weewx[2387]:  File 
"/usr/share/weewx/weewx/station.py", line 49, in __init__

Sep 1 19:31:11 raspberrypi weewx[2387]:  self.latitude_f = 
float(stn_dict['latitude'])

Sep 1 19:31:11 raspberrypi weewx[2387]:  TypeError: float() argument 
must be a string or a number

Sep 1 19:31:11 raspberrypi weewx[2387]:  Exiting.

 

-- 
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/cbf76247-ad89-4fd0-b1e1-8a8b3c496b7c%40googlegroups.com.


[weewx-user] Re: Belchertown skin 1.0 released!

2019-09-02 Thread Andrew Milner
in the code you edited - have you tried changing maximumfractiondigits and 
minimumfractiondigits from 1 to 0?  It seems to me - without having the 
skin - that this should do what you want  If it does not do the trick 
then put it back to 1 and wait for Pat!!



On Monday, 2 September 2019 09:04:07 UTC+3, Stefan wrote:
>
> Hello.
> I wanted to ask if the wind values (in the live view) could be displayed 
> as a whole, without them? I mean that. Currently, the values are always 
> displayed with 3.2 km/h, but more interesting would be 3 km/h. Is that 
> possible?
>
> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>>
>> Belchertown skin 1.0 is released!
>>
>> This update contains a lot of updates and changes including *an entire 
>> rewrite of the Highcharts system* which allows you to make almost any 
>> graph you want for almost any time span you want. You can see some examples 
>> of the charts you can make on the BelchertownWeather.com website graphs 
>> page .
>>
>> You can add/remove/change/reorder any chart, change colors, add 
>> observation plots, categorize for all time. Almost anything you want to do 
>> is available! The skin comes with the standard 4 charts ready to go, but 
>> there's extensive Belchertown Charts Documentation 
>> 
>>  
>> which can help you get started. 
>>
>> In addition to the Charts there's now a dark mode (which has an 
>> auto-switching mode based on sunset/sunrise), more flexibility for 
>> translations, user customized station observation table which is updated in 
>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>> release notes for all the details! 
>>
>> You can download the latest release here 
>> ,
>>  
>> and read all of the details on the changes here: 
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>> uninstall everything and reinstall new. This is due to the Chart system 
>> being fully rewritten and the potential for conflicts. Please read this 
>> upgrade guide if you are upgrading from an older version of Belchertown skin 
>> 
>> . 
>>
>> Thanks to all the beta testers and translators over the last couple of 
>> months help me iron out all the kinks and shape the skin in a way that can 
>> be translated a little easier! 
>>
>> Attached are some examples of the charts that can be made. If you find 
>> any issues, you can reply here or open an issue on the Belchertown skin 
>> GitHub page . 
>>
>

-- 
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/0167f80b-c4bf-4315-ac52-ffe78b4c2a8d%40googlegroups.com.


[weewx-user] Re: Belchertown skin 1.0 released!

2019-09-02 Thread Stefan
Hello.
I wanted to ask if the wind values (in the live view) could be displayed as 
a whole, without them? I mean that. Currently, the values are always 
displayed with 3.2 km/h, but more interesting would be 3 km/h. Is that 
possible?

Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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/cdeefde9-c6a1-44da-82d9-876001f36d13%40googlegroups.com.