[weewx-user] Re: WU Import failed
Any news to wee_import? Regards, Andre Am Donnerstag, 5. April 2018 02:12:19 UTC+2 schrieb gjr80: > > Hi, > > The problem appears to be that the radiation data for your station on WU > is recorded as '---' instead of it being blank or a numeric. It is a simple > fix to ignore the '---' but I just need to work through some other parts of > wee_import to make sure I do not introduce some inconsistent behaviour. > Give me a day or 2 and I should have a revised wee_import that will do > the job. > > Gary > > On Wednesday, 4 April 2018 01:16:46 UTC+10, Andre wrote: >> >> Hi, >> >> First I have to say I'm not Linux professional and all my 'know-how' is >> based on reading a lot of tutorials. >> >> My weather station is a Davis Vantage Vue. WeeWX is running on a >> Raspberry Pi 2. This setup is running and all data are fine. >> >> My problem is I can't import any data from WU with wee_import. >> >> ---log--- >> wee_import --import-config=/var/tmp/wu.conf --from=2018-01-01T00:30 --to= >> 2018-01-31T00:00 --dry-run >> Starting wee_import... >> Observation history for Weather Underground station 'INORDERS99' will be >> imported. >> Using database binding 'wx_binding', which is bound to database >> 'weewx.sdb' >> Destination table 'archive' unit system is '0x01' (US). >> Observations timestamped after 2018-01-01 00:30:00 CET (1514763000) and >> up to and >> including 2018-01-31 00:00:00 CET (1517353200) will be imported. >> This is a dry run, imported data will not be saved to archive. >> * radiation: cannot convert '---' to float at timestamp '2018-01-01 >> 00:30:00 CET (1514763000)'.* >> Nothing done, exiting. >> ---log--- >> >> What does it mean "radiation: cannot convert '---' to float at timestamp >> '2018-01-01 00:30:00 CET (1514763000)'? >> Is there data mismatch on WU? What can I do to solv this issue? >> >> Regards, Andre >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Android weather app for weeWx users
On Wednesday, 11 April 2018 11:27:31 UTC+10, Bill M wrote: > > Nope won't install now? > I had the install hang too, I ended up rebooting and it reported that it was installed correctly, no idea what's wrong there. As for you settings.txt you have a ] at the end of the webcam url webcam=http://www.sanfordweather.com/camera/camera3.jpg] -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Android weather app for weeWx users
Nope won't install now? On Tuesday, April 10, 2018 at 8:23:02 PM UTC-5, Bill M wrote: > > For some reason I can't update the app, Android quits and tells me Error > 495! > I'll try to un-install and then reinstall and see if that works > > On Tuesday, April 10, 2018 at 7:36:58 PM UTC-5, Bill M wrote: >> >> Thanks, I'll update and report back if any further problems! >> >> On Tuesday, April 10, 2018 at 6:00:27 PM UTC-5, John Smith wrote: >>> >>> On Wednesday, 11 April 2018 08:01:05 UTC+10, John Smith wrote: It took me a while to figure it out, but there seems to be some characters before data= 0xFE 0xFF >>> >>> After waking up properly, it seems they are utf-8 chars and for what >>> ever reason the method I used to download and parse them isn't working, >>> I'll try to work out a proper fix, but for the time being I just pushed out >>> an update that strips non-ascii chars which then works with your settings >>> file. >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Android weather app for weeWx users
Thanks, I'll update and report back if any further problems! On Tuesday, April 10, 2018 at 6:00:27 PM UTC-5, John Smith wrote: > > On Wednesday, 11 April 2018 08:01:05 UTC+10, John Smith wrote: >> >> It took me a while to figure it out, but there seems to be some >> characters before data= >> >> 0xFE 0xFF >> > > After waking up properly, it seems they are utf-8 chars and for what ever > reason the method I used to download and parse them isn't working, I'll try > to work out a proper fix, but for the time being I just pushed out an > update that strips non-ascii chars which then works with your settings > file. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Android weather app for weeWx users
On Wednesday, 11 April 2018 08:01:05 UTC+10, John Smith wrote: > > It took me a while to figure it out, but there seems to be some characters > before data= > > 0xFE 0xFF > After waking up properly, it seems they are utf-8 chars and for what ever reason the method I used to download and parse them isn't working, I'll try to work out a proper fix, but for the time being I just pushed out an update that strips non-ascii chars which then works with your settings file. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Android weather app for weeWx users
On Wednesday, 11 April 2018 07:18:02 UTC+10, Bill M wrote: > > I have been fighting with this most of the day, I've followed the > instructions and added the bits to weewx, it is generating the data.txt > file just fine but when I enter the URL into the app itself it doesn't seem > to be able to connect??? > > When I copy what I entered into my browser the data appears just fine! > > URL entered into the app is: > http://www.sanfordweather.com/weewx/settings.txt > and the data file is http://www.sanfordweather.com/weewx/data.txt > It took me a while to figure it out, but there seems to be some characters before data= 0xFE 0xFF -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Android weather app for weeWx users
I have been fighting with this most of the day, I've followed the instructions and added the bits to weewx, it is generating the data.txt file just fine but when I enter the URL into the app itself it doesn't seem to be able to connect??? When I copy what I entered into my browser the data appears just fine! URL entered into the app is: http://www.sanfordweather.com/weewx/settings.txt and the data file is http://www.sanfordweather.com/weewx/data.txt Confused! Bill On Tuesday, April 10, 2018 at 4:01:46 AM UTC-5, John Smith wrote: > > Just to give some background I made an android app similar to Pocket PWS. > I liked the app, but it was closed source so I couldn't do anything to add > new features. > > With Tom's blessing I named the app weeWx Weather App and I have published > it to google play > https://play.google.com/store/apps/details?id=com.odiousapps.weewxweather > > To use the app there needs to be some small changes made to weeWx, to > automate some of the steps needed I created a pair of weeWx extensions, one > for metric and one for imperial units. > > I've outlined the installation steps on github: > https://github.com/evilbunny2008/weeWxWeatherApp/wiki#concise-instructions > > All comments and requests about the app should go to github > https://github.com/evilbunny2008/weeWxWeatherApp/issues > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Using WeeWxMQTT - problems
That looks good. The debug messages from the sketch are showing the right message format. I don't think you need my sketch, yours is publishing OK now. Eventually (depending on your mosquitto persistence settings) the bad messages will disappear. Googling will reveal methods to clear them out faster. I'm fairly clueless in this area, but I think if you run mosquitto_sub as the same client as weewx/wxMesh, it will clear them out. It might already be cleared from what I see below. Make sure not to run mosquitto_sub as the same client as weewx when you want data to go to weewx. The other might pick up the subscription first. It looks like mosquitto_sub is picking a client name at random for you? On Tuesday, 10 April 2018 14:35:14 UTC-3, Ralph Underwood wrote: > > I restarted mosquitto and when I use mosquitto_sub -d -t weather I get: > > Client mosqsub|16684-ru-pi sending CONNECT > Client mosqsub|16684-ru-pi received CONNACK > Client mosqsub|16684-ru-pi sending SUBSCRIBE (Mid: 1, Topic: weather, QoS: > 0) > Client mosqsub|16684-ru-pi received SUBACK > Subscribed (mid: 1): 0 > Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r1, m0, 'weather', > ... (11 bytes)) > *temperature* > Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r0, m0, 'weather', > ... (10 bytes)) > INTE:72.50 > Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r0, m0, 'weather', > ... (10 bytes)) > INTE:72.39 > > So I need to figure out how to clear the buffer. > > Don't worry about insulting me. Many have said I know just enough to be > dangerous. I fairly sure that I made the sketch changes. Will verify that. > > With each run of the sketch loop I get something like: > 20.50 > 68.79 > Published: INTE:68.79 > > The first two lines are serial printing the temp in C and then my > converted to F value. > > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Using WeeWxMQTT - problems
Thanks Bill. I have to go to my tax guy. When I get back I will reconfigure my development set up with a clean install and use my Huzzah and HTU21 and your sketch. Thanks again! On Tuesday, April 10, 2018 at 10:14:40 AM UTC-7, Bill Morrow wrote: > > On Tuesday, 10 April 2018 12:44:32 UTC-3, Ralph Underwood wrote: >>> >>> I understand that you are using the HTU21 and think that it might be >>> best if I concentrate on that setup. Can you post the actual sketch you >>> are using? >>> >> > Attached. I use an Adafruit Feather Huzzah, > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Using WeeWxMQTT - problems
I restarted mosquitto and when I use mosquitto_sub -d -t weather I get: Client mosqsub|16684-ru-pi sending CONNECT Client mosqsub|16684-ru-pi received CONNACK Client mosqsub|16684-ru-pi sending SUBSCRIBE (Mid: 1, Topic: weather, QoS: 0) Client mosqsub|16684-ru-pi received SUBACK Subscribed (mid: 1): 0 Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r1, m0, 'weather', ... (11 bytes)) *temperature* Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r0, m0, 'weather', ... (10 bytes)) INTE:72.50 Client mosqsub|16684-ru-pi received PUBLISH (d0, q0, r0, m0, 'weather', ... (10 bytes)) INTE:72.39 So I need to figure out how to clear the buffer. Don't worry about insulting me. Many have said I know just enough to be dangerous. I fairly sure that I made the sketch changes. Will verify that. With each run of the sketch loop I get something like: 20.50 68.79 Published: INTE:68.79 The first two lines are serial printing the temp in C and then my converted to F value. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Using WeeWxMQTT - problems
> > On Tuesday, 10 April 2018 12:44:32 UTC-3, Ralph Underwood wrote: >> >> I understand that you are using the HTU21 and think that it might be best >> if I concentrate on that setup. Can you post the actual sketch you are >> using? >> > Attached. I use an Adafruit Feather Huzzah, -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. wxIndoorHuzzah.ino Description: Binary data
[weewx-user] Re: Using WeeWxMQTT - problems
Hmm, this debug in the log
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Added to queue of 1 message
temperature
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Working on queue 0 payload :
temperature
means that wxMesh is still getting the message "temperature" through its
subscription to:
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT host is 10.0.0.161
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT topic is weather
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT client is wxclient
It's possible that your MQTT broker has a number of those bad messages
buffered? Try restarting it?
Not to be insulting - are you sure your fixed sketch was uploaded? What
does the ESP8266 serial console output for these print statements:
Serial.print("Published: "); Serial.println(charBuf);
On Tuesday, 10 April 2018 12:44:32 UTC-3, Ralph Underwood wrote:
>
> Thanks Bill for the reply.
>
> I am now sending
>
> INTE:68.11
>
> via mqtt
>
> I do note that I do not have TIME in my mqtt message.
>
>
> WeeWx still not happy with this as the log after starting:
>
> Apr 10 08:24:14 ru-pi systemd[1]: Starting LSB: weewx weather system...
> Apr 10 08:24:14 ru-pi weewx[6379]: engine: Initializing weewx version 3.8.0
> Apr 10 08:24:14 ru-pi weewx[6379]: engine: Using Python 2.7.9 (default,
> Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Apr 10 08:24:14 ru-pi weewx[6379]: engine: Platform
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Apr 10 08:24:14 ru-pi weewx[6379]: engine: Locale is 'en_US.UTF-8'
> Apr 10 08:24:14 ru-pi weewx[6379]: engine: pid file is /var/run/weewx.pid
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using configuration file
> /etc/weewx/weewx.conf
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: debug is 1
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Initializing engine
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading station type wxMesh
> (user.wxMesh)
> Apr 10 08:24:14 ru-pi weewx[6369]: Starting weewx weather system: weewx.
> Apr 10 08:24:14 ru-pi systemd[1]: Started LSB: weewx weather system.
> Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT host is 10.0.0.161
> Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT topic is weather
> Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT client is wxclient
> Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: polling interval is 5.0
> Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: label map is {'TIME':
> 'dateTime', 'INTE': 'outTemp', 'INHU': 'inHumidity'}
> Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Connected
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> weewx.engine.StdTimeSynch
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
> weewx.engine.StdTimeSynch
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> user.owfs.OWFSService
> Apr 10 08:24:14 ru-pi weewx[6385]: owfs: service version is 0.21
> Apr 10 08:24:14 ru-pi weewx[6385]: owfs: binding is archive
> Apr 10 08:24:14 ru-pi weewx[6385]: owfs: interface is u
> Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor map is {'extraTemp':
> '/uncached/28.7A06/temperature', 'inTemp':
> '/uncached/28.03CF0806/temperature'}
> Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor type map is {}
> Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor unit system is metric
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
> user.owfs.OWFSService
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> weewx.engine.StdConvert
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: StdConvert target unit is 0x1
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
> weewx.engine.StdConvert
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> weewx.engine.StdCalibrate
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
> weewx.engine.StdCalibrate
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> weewx.engine.StdQC
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
> weewx.engine.StdQC
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> weewx.wxservices.StdWXCalculate
> Apr 10 08:24:14 ru-pi weewx[6385]: wxcalculate: The following values will
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
> dewpoint=prefer_hardware, appTemp=prefer_hardware,
> rainRate=prefer_hardware, windrun=prefer_hardware,
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
> humidex=prefer_hardware, pressure=prefer_hardware,
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
> cloudbase=prefer_hardware
> Apr 10 08:24:14 ru-pi weewx[6385]: wxcalculate: The following algorithms
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
> weewx.wxservices.StdWXCalculate
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
> weewx.engine.StdArchive
> Apr 10 08:24:14 ru-pi weewx[6385]: engine: Archive will use data binding
> wx_binding
> Apr 10 08:24:14 ru-pi weewx[6385]:
[weewx-user] Re: Using WeeWxMQTT - problems
Thanks Bill for the reply.
I am now sending
INTE:68.11
via mqtt
I do note that I do not have TIME in my mqtt message.
WeeWx still not happy with this as the log after starting:
Apr 10 08:24:14 ru-pi systemd[1]: Starting LSB: weewx weather system...
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Initializing weewx version 3.8.0
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Using Python 2.7.9 (default, Sep
17 2016, 20:26:04) #012[GCC 4.9.2]
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Platform
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Apr 10 08:24:14 ru-pi weewx[6379]: engine: Locale is 'en_US.UTF-8'
Apr 10 08:24:14 ru-pi weewx[6379]: engine: pid file is /var/run/weewx.pid
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using configuration file
/etc/weewx/weewx.conf
Apr 10 08:24:14 ru-pi weewx[6385]: engine: debug is 1
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Initializing engine
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading station type wxMesh
(user.wxMesh)
Apr 10 08:24:14 ru-pi weewx[6369]: Starting weewx weather system: weewx.
Apr 10 08:24:14 ru-pi systemd[1]: Started LSB: weewx weather system.
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT host is 10.0.0.161
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT topic is weather
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: MQTT client is wxclient
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: polling interval is 5.0
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: label map is {'TIME':
'dateTime', 'INTE': 'outTemp', 'INHU': 'inHumidity'}
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Connected
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.engine.StdTimeSynch
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.engine.StdTimeSynch
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
user.owfs.OWFSService
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: service version is 0.21
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: binding is archive
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: interface is u
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor map is {'extraTemp':
'/uncached/28.7A06/temperature', 'inTemp':
'/uncached/28.03CF0806/temperature'}
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor type map is {}
Apr 10 08:24:14 ru-pi weewx[6385]: owfs: sensor unit system is metric
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
user.owfs.OWFSService
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.engine.StdConvert
Apr 10 08:24:14 ru-pi weewx[6385]: engine: StdConvert target unit is 0x1
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.engine.StdConvert
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.engine.StdCalibrate
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.engine.StdCalibrate
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.engine.StdQC
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.engine.StdQC
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.wxservices.StdWXCalculate
Apr 10 08:24:14 ru-pi weewx[6385]: wxcalculate: The following values will
be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
dewpoint=prefer_hardware, appTemp=prefer_hardware,
rainRate=prefer_hardware, windrun=prefer_hardware,
heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
humidex=prefer_hardware, pressure=prefer_hardware,
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
cloudbase=prefer_hardware
Apr 10 08:24:14 ru-pi weewx[6385]: wxcalculate: The following algorithms
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.wxservices.StdWXCalculate
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.engine.StdArchive
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Archive will use data binding
wx_binding
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Record generation will be
attempted in 'hardware'
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using archive interval of 300
seconds (specified in weewx configuration)
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Use LOOP data in hi/low
calculations: 1
Apr 10 08:24:14 ru-pi weewx[6385]: wxMesh: Added to queue of 1 message
temperature
Apr 10 08:24:14 ru-pi weewx[6385]: manager: Daily summary version is 2.0
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Using binding 'wx_binding' to
database 'weewx.sdb'
Apr 10 08:24:14 ru-pi weewx[6385]: manager: Starting backfill of daily
summaries
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.engine.StdArchive
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading service
weewx.restx.StdStationRegistry
Apr 10 08:24:14 ru-pi weewx[6385]: restx: StationRegistry: Registration not
requested.
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Finished loading service
weewx.restx.StdStationRegistry
Apr 10 08:24:14 ru-pi weewx[6385]: engine: Loading
[weewx-user] Re: Android weather app for weeWx users
Look forward to trying it out. Thank you for your time and efforts! Doug B. On Tuesday, April 10, 2018 at 2:01:46 AM UTC-7, John Smith wrote: > > Just to give some background I made an android app similar to Pocket PWS. > I liked the app, but it was closed source so I couldn't do anything to add > new features. > > With Tom's blessing I named the app weeWx Weather App and I have published > it to google play > https://play.google.com/store/apps/details?id=com.odiousapps.weewxweather > > To use the app there needs to be some small changes made to weeWx, to > automate some of the steps needed I created a pair of weeWx extensions, one > for metric and one for imperial units. > > I've outlined the installation steps on github: > https://github.com/evilbunny2008/weeWxWeatherApp/wiki#concise-instructions > > All comments and requests about the app should go to github > https://github.com/evilbunny2008/weeWxWeatherApp/issues > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: 'rainBatteryStatus' on TFA Opus
Yeah, the rain sensor talks to the external thermo-hygro sensor, they're no more than 15-20 apart and I've had this station for 4 years now, so it's not a communication/reception problem. The dashes on the console were because the rain sensor batteries were flat, when I measured them they were only ~0.20V, I check the logs regularly and there was no indication. Whereas when the thermo-hygro sensor had low batteries about a month before I replaced the rain batteries there was the "TX battery" symbol on the console and the value in the log was '1', i.e. I replaced them on time before they're too low to show dashes for the external temp and humidity. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Using WeeWxMQTT - problems
Sigh, pushed Post too quickly. The correct suggested change to your
sketch...
There's also some problems with that if block. Try changing dataString to a
> message that wxMesh can parse, for example
>if((temp > -20) && (temp <110))
>{
> char temperatureStr[6];
> dtostrf(temp, 4, 2, temperatureStr); // ESP8266 does not convert
> doubles to Strings
> dataString = String("INTE:") + temperatureStr;
> dataString.toCharArray(charBuf, 150);
> client.publish(topic,charBuf );
> Serial.print("Published: "); Serial.println(charBuf);
>}
On Friday, 6 April 2018 13:27:31 UTC-3, Ralph Underwood wrote:
>
> One station uses a Ultimeter 2100 driver -* can I use WeeWxMQTT as a
> service*?
>
Not yet. There is a discussion about this in the development group.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Using WeeWxMQTT - problems
Ralph, this line in the log file:
Apr 7 18:59:33 ru-pi weewx[19737]: wxMesh: Working on queue 0 payload :
temperature
means that your sketch has published a message of the string "temperature".
Looking at your sketch, it looks like it might have
if((temp > -20) && (temp <110))
dataString = String("{\"temperature\":") + temp + String("}"); <--
not in a format which wxMesh can parse
dataString.toCharArray(charBuf, 150);
{
client.publish(topic,charBuf );
}
There's also some problems with that if block. Try changing dataString to a
message that wxMesh can parse, for example
if((temp > -20) && (temp <110))
{
dataString = String("{\"temperature\":") + temp + String("}");
dataString.toCharArray(charBuf, 150);
client.publish(topic,charBuf );
Serial.print("Published: "); Serial.println(charBuf);
}
Also weewx can do data quality
control: http://weewx.com/docs/usersguide.htm#StdQC. I would recommend
passing whatever you get from the sensor on to weewx, and set it up to
decide if the data are good.
wxMesh does not quite read JSON format, it reads key:value pairs separated
by commas, with the key and value separated by a colon.
Here are the last two publications to my mosquitto broker, which will be
consolidated into weewx by the wxMesh driver.
TIME:0,INTE:20.03,INHU:33.00
TIME:0,AMBT: 0.59,BARP:1022.26,RHUM:64.87,HUMT:
0.57,IRRA:16,BATV:1010,PHOV:383,SYST:32.20,WIND: 0.0,WDIR: 0.0
The first was published by an ESP8266 which is indoors, the second is from
my outside homebrew station, relayed by a 2.4GHz radio to ethernet broker.
I have indefinite plans to change the message format to JSON.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: IndexError: list index out of range
Posted On Thursday, April 5, 2018 at 7:10:20 PM UTC-4, mwall wrote: > > looks like something is wrong with the forecast.html.tmpl file > > please post forecast.html.tmpl, your exfoliation skin.conf, and the > StdReport section of your vantage.conf > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Android weather app for weeWx users
Just to give some background I made an android app similar to Pocket PWS. I liked the app, but it was closed source so I couldn't do anything to add new features. With Tom's blessing I named the app weeWx Weather App and I have published it to google play https://play.google.com/store/apps/details?id=com.odiousapps.weewxweather To use the app there needs to be some small changes made to weeWx, to automate some of the steps needed I created a pair of weeWx extensions, one for metric and one for imperial units. I've outlined the installation steps on github: https://github.com/evilbunny2008/weeWxWeatherApp/wiki#concise-instructions All comments and requests about the app should go to github https://github.com/evilbunny2008/weeWxWeatherApp/issues -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: UV index
Sorry for my extremelly late response. It is still a problem with UV value driver is Interceptor driver = weewx.drivers.acurite LOOP: 2018-04-10 10:16:49 CEST (1523348209) altimeter: 29.728946262, appTemp: 54.3988471307, barometer: 29.7445129684, cloudbase: 1023.64799442, dateTime: 1523348209, dewpoint: 53.24, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.7178464013, radiation: 103.709636, rain: None, rainRate: 0.0, usUnits: 1, UV: 472.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0 LOOP: 2018-04-10 10:17:05 CEST (1523348225) altimeter: 29.728946262, appTemp: 54.3988471307, barometer: 29.7445129684, cloudbase: 1023.64799442, dateTime: 1523348225, dewpoint: 53.24, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.7178464013, radiation: 105.383024, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 487.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0 LOOP: 2018-04-10 10:17:16 CEST (1523348236) altimeter: 29.7350372327, appTemp: 54.3988471307, barometer: 29.7506458577, cloudbase: 1023.64799442, dateTime: 1523348236, dewpoint: 53.24, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.7237676067, radiation: 105.383024, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 487.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0 REC:2018-04-10 10:17:00 CEST (1523348220) altimeter: 29.728946262, appTemp: 54.3988471307, barometer: 29.7445129684, cloudbase: 1023.64799442, dateTime: 1523348220.0, dewpoint: 53.24, ET: 5.55883840061e-05, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, interval: 1, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.7178464013, radiation: 103.709636, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 472.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0 LOOP: 2018-04-10 10:17:21 CEST (1523348241) altimeter: 29.7350372327, appTemp: 54.3988471307, barometer: 29.7506458577, cloudbase: 1023.64799442, dateTime: 1523348241, dewpoint: 53.24, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.7237676067, radiation: 107.3910896, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 503.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0 LOOP: 2018-04-10 10:25:21 CEST (1523348721) altimeter: 29.7319917482, appTemp: 54.3988471307, barometer: 29.747579413, cloudbase: 1023.64799442, dateTime: 1523348721, dewpoint: 53.24, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.720807004, radiation: 150.8991776, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 796.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0 REC:2018-04-10 10:25:00 CEST (1523348700) altimeter: 29.7319917482, appTemp: 54.3988471307, barometer: 29.747579413, cloudbase: 1023.64799442, dateTime: 1523348700.0, dewpoint: 53.24, ET: 5.95042263045e-05, heatindex: 53.42, humidex: 57.2526191519, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, interval: 1, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.42, pressure: 28.720807004, radiation: 145.1166924, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 754.0, windchill: 53.42, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0 LOOP: 2018-04-10 10:25:37 CEST (1523348737) altimeter: 29.7319917482, appTemp: 54.6328953667, barometer: 29.7472129727, cloudbase: 1023.69795672, dateTime: 1523348737, dewpoint: 53.42, heatindex: 53.6, humidex: 57.5251059501, inDewpoint: 56.3317947215, inHumidity: 59.0, inTemp: 71.42, maxSolarRad: None, outHumidity: 99.0, outTemp: 53.6, pressure: 28.720807004, radiation: 152.6283452, rain: 0.0, rainRate: 0.0, usUnits: 1, UV: 806.0, windchill: 53.6, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0 debug wee_debug --info Using verbosity=1, displaying most info wee_debug output will be sent to stdout(console) Using configuration file /etc/weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_mysql' System info Platform: Linux-3.10.0-693.21.1.el7.x86_64-x86_64-with-centos-7.4.1708-Core Python Version:
