Re: [weewx-user] Re: Upgraded to 5.0.1, DB is updating but not reflecting

[Matt Johnson]

Tom - Fantastic! It was a permissions issue, and your solution resolved it. 
That actually crossed my mind but wasn't sure how to resolve it. I am 
adding this to my notes for future reference. These notes certainly saved 
me when reinstalling, I remember the initial config of this and doing it 
all self hosted behind a reverse proxy took days!

On Monday, March 11, 2024 at 9:02:09 AM UTC-4 Tom Keffer wrote:

> If I'm understanding correctly, you wish to publish to /var/www/html 
> directly, not /var/www/html/weewx. Without a log, it's hard to say what the 
> problem is, but I would guess it's  a permissions issue. On the theory that 
> it is, try this:
>
> 1. You've asked the report engine to generate *both* SeasonsReport *and* 
> Belchertown. 
> I doubt this is what you want. Disable the Seasons skin by setting 
> "enable=false" under [[SeasonsReport]].
>
> 2. Under [Belchertown], set
>
> HTML=/var/www/html
>
> 3. Change permissions. By default, user 'weewx' owns /var/www/html/weewx, 
> *not* /var/www/html. To change:
>
> *sudo chown -R weewx:weewx /var/www/html*
>
> 4. Restart weewx
>
> If that doesn't work, you will have to include a log. See the wiki article 
> *Help! 
> Posting to weewx-user 
> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>* for 
> how to get a good log.
>
> On Sun, Mar 10, 2024 at 8:15 PM Matt Johnson  wrote:
>
>> Ok, update. I did a clean install of weewx 5.0.2 on new hardware, as it 
>> was time and if I am going to set this up for several more years of trouble 
>> free service this is the right way to do it. 
>>
>> Anyway, I have everything working with Belchertown and mqtt EXCEPT I 
>> can't get WeeWx to publish Belchertown skin to var/www/html so it is 
>> accessible on port 80 for my website. For http://shakerweather.com I 
>> just get the NGINX confirmation page, which is in that folder as well as 
>> the weewx folder that has belchertown. 
>>
>> I followed Pat's instructions to modify the weewx.conf so that HTML_ROOT 
>> = var/www/html but it simply won't generate the files there. In fact, I'm 
>> not sure where it publishes when I change the HTML_ROOT to var/www/html. 
>> According to Pat's instructions they should just generate at the next 
>> archive interval. When I make this change the directory at 
>> /weewx/belchertown stops updating as well unless I put the HTML_ROOT = 
>> var/www/html/weex/belchertown
>>
>> The only way I can see everything is by going to 
>> http://shakerweather.com/weewx/belchertown
>>
>> There must be something simple I am missing here. Anyone have any ideas?
>>
>> Here is my weewx conf that works publishing to 
>> http://shakerweather.com/weewx/belchertown. Again, if I make Pat's 
>> modifications to set the Belchertown HTML_ROOT to /var/www/html/ nothing 
>> happens.
>>
>>
>> --
>> #   This section specifies what reports, using which skins, to generate.
>>
>> [StdReport]
>> 
>> # Where the skins reside, relative to WEEWX_ROOT
>> SKIN_ROOT = skins
>> 
>> # Where the generated reports should go, relative to WEEWX_ROOT
>> HTML_ROOT = /var/www/html/weewx
>> 
>> # Uncomment and change to override logging for reports.
>> # log_success = True
>> # log_failure = True
>> 
>> # The database binding indicates which data should be used in reports.
>> data_binding = wx_binding
>> 
>> # Each of the following subsections defines a report that will be run.
>> # See the customizing guide to change the units, plot types and line
>> # colors, modify the fonts, display additional sensor data, and other
>> # customizations. Many of those changes can be made here by overriding
>> # parameters, or by modifying templates within the skin itself.
>> 
>> [[SeasonsReport]]
>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>> # images, templates and plots for the report.
>> skin = Seasons
>> enable = true
>> 
>> [[SmartphoneReport]]
>> # The SmartphoneReport uses the 'Smartphone' skin, and the images 
>> and
>> # files are placed in a dedicated subdirectory.
>> skin = Smartphone
>> enable = false
>> HTML_ROOT = /var/www/html/weewx/smartphone
>> 
>> [[MobileReport]]
>> # The MobileReport uses the 'Mobile' skin, and the images and 
>> files
>> # are placed in a dedicated subdirectory.
>> skin = Mobile
>>

[weewx-user] Re: Upgraded to 5.0.1, DB is updating but not reflecting

[Matt Johnson]

Ok, update. I did a clean install of weewx 5.0.2 on new hardware, as it was 
time and if I am going to set this up for several more years of trouble 
free service this is the right way to do it. 

Anyway, I have everything working with Belchertown and mqtt EXCEPT I can't 
get WeeWx to publish Belchertown skin to var/www/html so it is accessible 
on port 80 for my website. For http://shakerweather.com I just get the 
NGINX confirmation page, which is in that folder as well as the weewx 
folder that has belchertown. 

I followed Pat's instructions to modify the weewx.conf so that HTML_ROOT = 
var/www/html but it simply won't generate the files there. In fact, I'm not 
sure where it publishes when I change the HTML_ROOT to var/www/html. 
According to Pat's instructions they should just generate at the next 
archive interval. When I make this change the directory at 
/weewx/belchertown stops updating as well unless I put the HTML_ROOT = 
var/www/html/weex/belchertown

The only way I can see everything is by going to 
http://shakerweather.com/weewx/belchertown

There must be something simple I am missing here. Anyone have any ideas?

Here is my weewx conf that works publishing 
to http://shakerweather.com/weewx/belchertown. Again, if I make Pat's 
modifications to set the Belchertown HTML_ROOT to /var/www/html/ nothing 
happens.


--
#   This section specifies what reports, using which skins, to generate.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# Uncomment and change to override logging for reports.
# log_success = True
# log_failure = True

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
skin = Seasons
enable = true

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
skin = Smartphone
enable = false
HTML_ROOT = /var/www/html/weewx/smartphone

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
skin = Mobile
enable = false
HTML_ROOT = /var/www/html/weewx/mobile

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
skin = Standard
enable = false

[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
enable = true




On Wednesday, March 6, 2024 at 7:02:35 AM UTC-5 Matt Johnson wrote:

> So 12 hours later it seems my site's <http://shakerweather.com> 
> Belchertown skin is not updating any of the data, it is all stuck in time 
> at 6:20pm last night when I did the update - forecast, almanac, charts all 
> frozen there. MQTT shows real time data for some elements. Database is 
> still updating leading me to believe the skin is simply not reflecting any 
> updates. I'll generate a log to see if it helps.
>
> On Tuesday, March 5, 2024 at 11:40:14 PM UTC-5 gjr80 wrote:
>
>> The first thing to do is to post a log extract so we can see exactly what 
>> is/is not going on. This wiki page 
>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#include-the-log>
>>  
>> will help you to get a good log extract to post here.
>>
>> Gary
>>
>> On Wednesday 6 March 2024 at 14:08:51 UTC+10 illini...@gmail.com wrote:
>>
>>> I've been at this hours. I updated my WeeWx from 4.10.2 to 5.0.1. I am 
>>> running Belchertown and have MQTT setup. That is all working. 
>>>
>>> The issue is I don't see the archive data updating the charts or 
>>> reflecting when you refresh the page. The database file itself does appear 
>>> to be updated every 5 minutes as the modified date is updating every 5 
>>> minutes.
>>>
>>> Any ideas to troubleshoot?
>>>
>>

-- 
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/96db740a-3462-46a9-b50f-5fcc71047964n%40googlegroups.com.

[weewx-user] Re: Upgraded to 5.0.1, DB is updating but not reflecting

[Matt Johnson]

So 12 hours later it seems my site's  Belchertown 
skin is not updating any of the data, it is all stuck in time at 6:20pm 
last night when I did the update - forecast, almanac, charts all frozen 
there. MQTT shows real time data for some elements. Database is still 
updating leading me to believe the skin is simply not reflecting any 
updates. I'll generate a log to see if it helps.

On Tuesday, March 5, 2024 at 11:40:14 PM UTC-5 gjr80 wrote:

> The first thing to do is to post a log extract so we can see exactly what 
> is/is not going on. This wiki page 
> 
>  
> will help you to get a good log extract to post here.
>
> Gary
>
> On Wednesday 6 March 2024 at 14:08:51 UTC+10 illini...@gmail.com wrote:
>
>> I've been at this hours. I updated my WeeWx from 4.10.2 to 5.0.1. I am 
>> running Belchertown and have MQTT setup. That is all working. 
>>
>> The issue is I don't see the archive data updating the charts or 
>> reflecting when you refresh the page. The database file itself does appear 
>> to be updated every 5 minutes as the modified date is updating every 5 
>> minutes.
>>
>> Any ideas to troubleshoot?
>>
>

-- 
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/efe011c1-8467-48dd-81f8-4f25217d70fen%40googlegroups.com.

[weewx-user] Upgraded to 5.0.1, DB is updating but not reflecting

[Matt Johnson]

I've been at this hours. I updated my WeeWx from 4.10.2 to 5.0.1. I am 
running Belchertown and have MQTT setup. That is all working. 

The issue is I don't see the archive data updating the charts or reflecting 
when you refresh the page. The database file itself does appear to be 
updated every 5 minutes as the modified date is updating every 5 minutes.

Any ideas to troubleshoot?

-- 
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/555c68cb-269e-4a98-a4ec-cf6fcb38e4cfn%40googlegroups.com.

[weewx-user] Re: Belchertown UV Index and Solar Radiation

[Matt Johnson]

I figured it out. Since I am using WeatherLink Live (WLL) to feed WeeWx 
using the parameters for the custom driver 
(https://github.com/michael-slx/weewx-weatherlink-live)

I needed to add uv and solar to the mapping in weewx.config: mapping = 
th:1, th_indoor, baro, rain:1, wind:1, uv:1, solar:1, thw:1, thsw:1, 
windchill:1. Belchertown is now reflecting 0 UV and 0w (it's night) instead 
of N/A with the same config as my original message.

On Thursday, July 29, 2021 at 4:37:31 PM UTC-4 Matt Johnson wrote:

>
> I recently added UV and Solar sensors to my Davis VP2 and have them up and 
> running reporting to my Davis console, WeatherLink Live, etc. All is 
> working there.
>
> I've been reading through the docs for WeeWx and Belchertown and there 
> isn't a lot I am coming across other than the 'UV' and 'radiation' 
> variables being where this data is captured. A search here turns up some 
> charting and custom hook integrations but not so much as to getting the 
> data to appear.
>
> I attempted to get UV and Solar Radiation to appear on the skin for my 
> website (shakerweather.com) by adding the variables to the conf as 
> follows:
>
> station_observations = "barometer", "cloudbase", "cloud_cover", 
> "dewpoint", "outHumidity", "UV", "radiation", "rainWithRainRate"
>
> The placeholders for UV and radiation do appear now, but have values of 
> N/A. 
>
> Surely I am missing a config or using the wrong variables somewhere?
>
>

-- 
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/ea6870fc-1685-48e7-9786-af0ef2857684n%40googlegroups.com.

[weewx-user] Belchertown UV Index and Solar Radiation

[Matt Johnson]

I recently added UV and Solar sensors to my Davis VP2 and have them up and 
running reporting to my Davis console, WeatherLink Live, etc. All is 
working there.

I've been reading through the docs for WeeWx and Belchertown and there 
isn't a lot I am coming across other than the 'UV' and 'radiation' 
variables being where this data is captured. A search here turns up some 
charting and custom hook integrations but not so much as to getting the 
data to appear.

I attempted to get UV and Solar Radiation to appear on the skin for my 
website (shakerweather.com) by adding the variables to the conf as follows:

station_observations = "barometer", "cloudbase", "cloud_cover", "dewpoint", 
"outHumidity", "UV", "radiation", "rainWithRainRate"

The placeholders for UV and radiation do appear now, but have values of 
N/A. 

Surely I am missing a config or using the wrong variables somewhere?

-- 
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/477d4316-9a64-4051-89e1-510222ed204fn%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

Vince,

I'd be happy to pull it all into one doc with some supporting notes so it 
makes sense. This was a frustrating (at times) yet rewarding experience to 
figure this all out and I know many others will want to achieve a similar 
website and control of their data.

Matt

On Monday, July 26, 2021 at 12:27:51 PM UTC-4 vince wrote:

> Given the long back+forth on this one, it would be really helpful if you 
> could capture your entire setup someplace for the next person/victim who 
> tries to do the same thing.  You have quite a lot of moving parts and it 
> would be great to capture everything you did to set it up so it works both 
> LAN and WAN.
>
>

-- 
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/dd10f515-d693-4cf2-813f-bf4e7b3437f2n%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

Holy cow, no sooner did I send that did I see the glorious sight of 
"connected to weather station live" !!

Not sure what happened, maybe it just took a few minutes for Cloudflare to 
propagate the changes? In any case it is working and tested on LAN and WAN. 
I am so grateful for your support Doug

On Monday, July 26, 2021 at 10:46:10 AM UTC-4 Matt Johnson wrote:

> Doug,
>
> I went through your doc and updated everything at Cloudflare, my Nginx 
> Proxy Server and conf files and not working still...not sure what else it 
> could be.
>
> On Sunday, July 25, 2021 at 7:05:19 PM UTC-4 ln77 wrote:
>
>> Ah, ok thanks. I’m running the web server unencrypted as well, for the 
>> same reason.  
>>
>>   -Les
>>
>>
>> On Jul 25, 2021, at 4:14 AM, Karen K  wrote:
>>
>> ln77 schrieb am Sonntag, 25. Juli 2021 um 03:35:38 UTC+2:
>>
>>> I don’t see the point of SSL on the websockets connection from the 
>>> browser. The data is all public, there’s nothing sensitive sent by the 
>>> client, and if someone spoofs the mqtt broker, who really cares?
>>>
>>
>> The web browser cares. If it receives the website by HTTPS (SSL 
>> encrypted), then it refuses to connect to an unencrypted websockets server.
>>  
>>
>>>  
>>>
>> -- 
>>
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/08aa26d4-d986-4916-9c82-4c895c8b8fddn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/08aa26d4-d986-4916-9c82-4c895c8b8fddn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>

-- 
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/37e583e6-2cf2-445b-a0e9-9330653368den%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

Doug,

I went through your doc and updated everything at Cloudflare, my Nginx 
Proxy Server and conf files and not working still...not sure what else it 
could be.

On Sunday, July 25, 2021 at 7:05:19 PM UTC-4 ln77 wrote:

> Ah, ok thanks. I’m running the web server unencrypted as well, for the 
> same reason.  
>
>   -Les
>
>
> On Jul 25, 2021, at 4:14 AM, Karen K  wrote:
>
> ln77 schrieb am Sonntag, 25. Juli 2021 um 03:35:38 UTC+2:
>
>> I don’t see the point of SSL on the websockets connection from the 
>> browser. The data is all public, there’s nothing sensitive sent by the 
>> client, and if someone spoofs the mqtt broker, who really cares?
>>
>
> The web browser cares. If it receives the website by HTTPS (SSL 
> encrypted), then it refuses to connect to an unencrypted websockets server.
>  
>
>>  
>>
> -- 
>
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/08aa26d4-d986-4916-9c82-4c895c8b8fddn%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/f15908cf-536e-4e0e-ad5c-0e43b72f16cfn%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

Thanks for this detail Doug, I will try again. Your analysis is spot on as 
I did disable SSL temporarily to see if the websockets would in fact work 
that way confiming it is an SSL issue. If you go to unsecured http (
http://shakerweather.com) you should see it temporarily working with 
unsecured websocket updates (until I go back in and try to fix it the 
correct way with SSL this afternoon)

Light at the end of the tunnel. I will post later today when I either reach 
success or get stuck again.


On Saturday, July 24, 2021 at 1:05:12 PM UTC-4 do...@dougjenkins.com wrote:

> I just checked your site in edge and pulled up the dev console. I see the 
> main issue is that the client (me) is trying to access a non-secure 
> websocket (your server) while the rest of the content is coming from the 
> https stream:
>
> *paho-mqtt.min.js:37 Mixed Content: The page at 
> 'https://shakerweather.com/ <https://shakerweather.com/>' was loaded over 
> HTTPS, but attempted to connect to the insecure WebSocket endpoint 
> 'ws://mqtt.shakerweather.com:9001/mqtt 
> <http://mqtt.shakerweather.com:9001/mqtt>'. This request has been blocked; 
> this endpoint must be available over WSS.*
>
> I had this problem before and what I to solve it was to have CloudFlare to 
> translate all my traffic to SSL. 
>
> Here is my Cloudflare and NGINX Proxy Manager setup that I use for 
> largoweather.com. Essentially if you check my SSL Cert, it is provided by 
> Cloudflare. Cloudflare pushes all http traffic as https to my internal 
> server. I have firewall rules to route all incoming 80/443 traffic to my 
> internal server in which that is properly routed to my NGINX Proxy Manager 
> instance.
>
> NGINX Proxy manager proxies that traffic to the correct webserver (in my 
> case container) that hosts my weewx website. I did issue a LetsEncrypt SSL 
> within NGINX Proxy manager to get that to work.
>
> They trick with LetsEncrypt is that you need to expose (just for a second) 
> your public IP Address in Cloudflare (assuming that is your name server of 
> the domain) for the SSL Certificate to be created correctly. Once you do 
> that, you can setup Proxy again to protect your public IP.
>
> Once this is setup, you will immediately see the live updates working. 
>
> On Saturday, July 24, 2021 at 12:36:18 PM UTC-4 Doug Jenkins wrote:
>
>> Matt:
>>
>> I am looking into the issue now. I think you need to offload the SSL to 
>> Cloudflare with NGNIX Proxy. I am capturing screenshots of my setup to see 
>> if that will help you.
>>
>> Doug Jenkins
>>
>> On Saturday, July 24, 2021 at 12:33:22 PM UTC-4 mattjo...@gmail.com 
>> wrote:
>>
>>> Doing more trouble shooting. I have narrowed it down to a SSL issue. 
>>>
>>> To confirm this I disabled SSL at cloudflare and disabled force SSL for 
>>> shakerweather.com with my NGINX reverse proxy server and ran with this 
>>> setup:
>>>
>>> *weewx.config*
>>> [[MQTT]]
>>> server_url = mqtt://usr:p...@mqtt.shakerweather.com:1883/
>>>
>>> topic = weather
>>> unit_system = US
>>> binding = archive, loop 
>>> aggregation = aggregate
>>>
>>> *skin.conf*
>>># MQTT Websockets defaults
>>> mqtt_websockets_enabled = 1
>>> mqtt_websockets_host = "mqtt.shakerweather.com"
>>> mqtt_websockets_port = 9001
>>> mqtt_websockets_ssl = 0
>>> mqtt_websockets_topic = "weather/loop"
>>> disconnect_live_website_visitor = 180
>>>
>>> *mosquitto.conf*
>>> persistence false
>>>
>>> # mqtt
>>> listener 1883
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>> acl_file /etc/mosquitto/acl
>>>
>>>
>>> I am able to see the real time websocket updates internally and 
>>> externally at http://shakerweather.com (I'll leave it up for a short 
>>> time so if it doesn't work if you click on it that could be why)
>>>
>>> So at least I have narrowed down the issue. Still not sure how to 
>>> resolve to ensure all is secured with SSL
>>> On Saturday, July 24, 2021 at 10:23:03 AM UTC-4 Matt Johnson wrote:
>>>
>>>> Your setup seems similar to mine so I went for it. Still not working. 
>>>>
>>>> I went ahead and added a mqtt CNAME record to the shakerweather.com 
>>>> cloudflare setup. I al

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

Thanks for this detail Doug, I will try again. Your analysis is spot on as 
I did disable SSL temporarily to see if the websockets would in fact work 
that way confiming it is an SSL issue. If you go to unsecured http 
(http://shakerweather.com) you should see it all working with websocket 
updates (until I go back in and try to fix it the correct way with SSL this 
afternoon)

Light at the end of the tunnel. I will post later today when I either reach 
success or get stuck again.
On Saturday, July 24, 2021 at 1:05:12 PM UTC-4 do...@dougjenkins.com wrote:

> I just checked your site in edge and pulled up the dev console. I see the 
> main issue is that the client (me) is trying to access a non-secure 
> websocket (your server) while the rest of the content is coming from the 
> https stream:
>
> *paho-mqtt.min.js:37 Mixed Content: The page at 
> 'https://shakerweather.com/ <https://shakerweather.com/>' was loaded over 
> HTTPS, but attempted to connect to the insecure WebSocket endpoint 
> 'ws://mqtt.shakerweather.com:9001/mqtt 
> <http://mqtt.shakerweather.com:9001/mqtt>'. This request has been blocked; 
> this endpoint must be available over WSS.*
>
> I had this problem before and what I to solve it was to have CloudFlare to 
> translate all my traffic to SSL. 
>
> Here is my Cloudflare and NGINX Proxy Manager setup that I use for 
> largoweather.com. Essentially if you check my SSL Cert, it is provided by 
> Cloudflare. Cloudflare pushes all http traffic as https to my internal 
> server. I have firewall rules to route all incoming 80/443 traffic to my 
> internal server in which that is properly routed to my NGINX Proxy Manager 
> instance.
>
> NGINX Proxy manager proxies that traffic to the correct webserver (in my 
> case container) that hosts my weewx website. I did issue a LetsEncrypt SSL 
> within NGINX Proxy manager to get that to work.
>
> They trick with LetsEncrypt is that you need to expose (just for a second) 
> your public IP Address in Cloudflare (assuming that is your name server of 
> the domain) for the SSL Certificate to be created correctly. Once you do 
> that, you can setup Proxy again to protect your public IP.
>
> Once this is setup, you will immediately see the live updates working. 
>
> On Saturday, July 24, 2021 at 12:36:18 PM UTC-4 Doug Jenkins wrote:
>
>> Matt:
>>
>> I am looking into the issue now. I think you need to offload the SSL to 
>> Cloudflare with NGNIX Proxy. I am capturing screenshots of my setup to see 
>> if that will help you.
>>
>> Doug Jenkins
>>
>> On Saturday, July 24, 2021 at 12:33:22 PM UTC-4 mattjo...@gmail.com 
>> wrote:
>>
>>> Doing more trouble shooting. I have narrowed it down to a SSL issue. 
>>>
>>> To confirm this I disabled SSL at cloudflare and disabled force SSL for 
>>> shakerweather.com with my NGINX reverse proxy server and ran with this 
>>> setup:
>>>
>>> *weewx.config*
>>> [[MQTT]]
>>> server_url = mqtt://usr:p...@mqtt.shakerweather.com:1883/
>>>
>>> topic = weather
>>> unit_system = US
>>> binding = archive, loop 
>>> aggregation = aggregate
>>>
>>> *skin.conf*
>>># MQTT Websockets defaults
>>> mqtt_websockets_enabled = 1
>>> mqtt_websockets_host = "mqtt.shakerweather.com"
>>> mqtt_websockets_port = 9001
>>> mqtt_websockets_ssl = 0
>>> mqtt_websockets_topic = "weather/loop"
>>> disconnect_live_website_visitor = 180
>>>
>>> *mosquitto.conf*
>>> persistence false
>>>
>>> # mqtt
>>> listener 1883
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>> acl_file /etc/mosquitto/acl
>>>
>>>
>>> I am able to see the real time websocket updates internally and 
>>> externally at http://shakerweather.com (I'll leave it up for a short 
>>> time so if it doesn't work if you click on it that could be why)
>>>
>>> So at least I have narrowed down the issue. Still not sure how to 
>>> resolve to ensure all is secured with SSL
>>> On Saturday, July 24, 2021 at 10:23:03 AM UTC-4 Matt Johnson wrote:
>>>
>>>> Your setup seems similar to mine so I went for it. Still not working. 
>>>>
>>>> I went ahead and added a mqtt CNAME record to the shakerweather.com 
>>>> cloudflare setup. I also added mqtt.shakerweather.c

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

gt;> focus on locally hosting (my first setup) over the cloud broker. I have a 
>> robust homelab and really like to keep things in house.
>>
>> *think the first configuration, with the local mqtt broker  isn’t going 
>> to work because mqtt_websockets_host is set to localhost, which will only 
>> resolve to the weewx/mqtt server when the web browser is running on that 
>> server.  You need to set something here that will resolve to the weewx/mqtt 
>> server from any client that you want to get realtime updates.  *
>>
>> This makes sense. I initially was on this path and changed the 
>> mqtt_websockets host to the ip address of the weewx/mqtt server. This did 
>> not work for other clients on the LAN which seemed strange given how I have 
>> lots of locally running services on a few different servers in my home lab 
>> and I access them all via device IP and port, with a few that are 
>> accessible externally via reverse proxy. 
>>
>>
>> *You need a DNS name that will resolve to your firewall and get 
>> port-forwarded (for port 8083) to the weewx/mqtt server, 
>> for mqtt_websockets_host. That should enable external access.  *
>>
>> I can use my mqtt.beldenserver.com DNS name I have setup at cloudflare 
>> for this. I am running OPNSense for my firewall so I should be able to do 
>> anything. Right now I have a firewall rule setup to send port 80/443 
>> traffic to my NGINX Reverse Proxy where I have several DNS addresses 
>> pointing to different services on different servers. One of these takes 
>> shakerweather.com through 80/443 and through the reverse proxy and 
>> points to the weewx/mqtt server to return the webpage (which is working 
>> fine)
>>
>> So you are saying I just need to add a rule to forward external port 8083 
>> requests to the weewx/mqtt server IP and port?
>>
>> *And, if your firewall will do hairpinning, it should work internally as 
>> well. It may take some magic with forwarding/masquerading rules on the 
>> firewall to get hairpinning to work.  (The alternative for internal access 
>> is to have an internal DNS server that resolves that hostname directly to 
>> the internal IP of the weewx/mqtt server for clients on the internal 
>> network.)*
>>
>> My OPNSense firewall should be able to do hairpinning. I read on that 
>> briefly as I have only heard of the term and not too familiar with it. 
>>
>>
>>
>>
>> On Saturday, July 24, 2021 at 2:24:32 AM UTC-4 ln77 wrote:
>>
>>> I think the first configuration, with the local mqtt broker  isn’t going 
>>> to work because mqtt_websockets_host is set to localhost, which will only 
>>> resolve to the weewx/mqtt server when the web browser is running on that 
>>> server.  You need to set something here that will resolve to the weewx/mqtt 
>>> server from any client that you want to get realtime updates.  
>>>
>>> Not sure why the second config, with the cloud mqtt broker, isn’t 
>>> working. Are you sure the mqtt broker is configured for SSL on port 8883? 
>>>  You might put “log_success = true” in the weewx [[MQTT]] config and see if 
>>> the log messages tell you anything useful.  
>>>
>>> Or forget about the cloud server and go back to getting the first config 
>>> working.  You need a DNS name that will resolve to your firewall and get 
>>> port-forwarded (for port 8083) to the weewx/mqtt server, 
>>> for mqtt_websockets_host. That should enable external access.  And, if your 
>>> firewall will do hairpinning, it should work internally as well. It may 
>>> take some magic with forwarding/masquerading rules on the firewall to get 
>>> hairpinning to work.  (The alternative for internal access is to have an 
>>> internal DNS server that resolves that hostname directly to the internal IP 
>>> of the weewx/mqtt server for clients on the internal network.)
>>>
>>>   -Les
>>>
>>>
>>>
>>> On 23 Jul 2021, at 21:05, Matt Johnson  wrote:
>>>
>>> I've been trouble shooting getting the Belchertown skin MQTT Websocket 
>>> real time updates to work on my site shakerweather.com for a lot of 
>>> this week. 
>>>
>>> I have WeeWx installed on a dedicated thin client on Ubuntu 20.04 LTS 
>>> and have Mosquitto and NGINX installed on the same machine. Running bare 
>>> metal, no docker or VMs here.
>>>
>>> External access to WeeWx website is handled via NGINX reverse proxy 
>>> manager with SSL certs on a different server via do

Re: [weewx-user] Belchertown MQTT Issues

[Matt Johnson]

Thanks Les. I think you have helped clear some things up. For the sake of 
clarity and getting to the end state I desire and your suggestion let's 
focus on locally hosting (my first setup) over the cloud broker. I have a 
robust homelab and really like to keep things in house.

*think the first configuration, with the local mqtt broker  isn’t going to 
work because mqtt_websockets_host is set to localhost, which will only 
resolve to the weewx/mqtt server when the web browser is running on that 
server.  You need to set something here that will resolve to the weewx/mqtt 
server from any client that you want to get realtime updates.  *

This makes sense. I initially was on this path and changed the 
mqtt_websockets host to the ip address of the weewx/mqtt server. This did 
not work for other clients on the LAN which seemed strange given how I have 
lots of locally running services on a few different servers in my home lab 
and I access them all via device IP and port, with a few that are 
accessible externally via reverse proxy. 


*You need a DNS name that will resolve to your firewall and get 
port-forwarded (for port 8083) to the weewx/mqtt server, 
for mqtt_websockets_host. That should enable external access.  *

I can use my mqtt.beldenserver.com DNS name I have setup at cloudflare for 
this. I am running OPNSense for my firewall so I should be able to do 
anything. Right now I have a firewall rule setup to send port 80/443 
traffic to my NGINX Reverse Proxy where I have several DNS addresses 
pointing to different services on different servers. One of these takes 
shakerweather.com through 80/443 and through the reverse proxy and points 
to the weewx/mqtt server to return the webpage (which is working fine)

So you are saying I just need to add a rule to forward external port 8083 
requests to the weewx/mqtt server IP and port?

*And, if your firewall will do hairpinning, it should work internally as 
well. It may take some magic with forwarding/masquerading rules on the 
firewall to get hairpinning to work.  (The alternative for internal access 
is to have an internal DNS server that resolves that hostname directly to 
the internal IP of the weewx/mqtt server for clients on the internal 
network.)*

My OPNSense firewall should be able to do hairpinning. I read on that 
briefly as I have only heard of the term and not too familiar with it. 




On Saturday, July 24, 2021 at 2:24:32 AM UTC-4 ln77 wrote:

> I think the first configuration, with the local mqtt broker  isn’t going 
> to work because mqtt_websockets_host is set to localhost, which will only 
> resolve to the weewx/mqtt server when the web browser is running on that 
> server.  You need to set something here that will resolve to the weewx/mqtt 
> server from any client that you want to get realtime updates.  
>
> Not sure why the second config, with the cloud mqtt broker, isn’t working. 
> Are you sure the mqtt broker is configured for SSL on port 8883?  You might 
> put “log_success = true” in the weewx [[MQTT]] config and see if the log 
> messages tell you anything useful.  
>
> Or forget about the cloud server and go back to getting the first config 
> working.  You need a DNS name that will resolve to your firewall and get 
> port-forwarded (for port 8083) to the weewx/mqtt server, 
> for mqtt_websockets_host. That should enable external access.  And, if your 
> firewall will do hairpinning, it should work internally as well. It may 
> take some magic with forwarding/masquerading rules on the firewall to get 
> hairpinning to work.  (The alternative for internal access is to have an 
> internal DNS server that resolves that hostname directly to the internal IP 
> of the weewx/mqtt server for clients on the internal network.)
>
>   -Les
>
>
>
> On 23 Jul 2021, at 21:05, Matt Johnson  wrote:
>
> I've been trouble shooting getting the Belchertown skin MQTT Websocket 
> real time updates to work on my site shakerweather.com for a lot of this 
> week. 
>
> I have WeeWx installed on a dedicated thin client on Ubuntu 20.04 LTS and 
> have Mosquitto and NGINX installed on the same machine. Running bare metal, 
> no docker or VMs here.
>
> External access to WeeWx website is handled via NGINX reverse proxy 
> manager with SSL certs on a different server via docker. Requests to 
> shakerweather.com are sent to the proxy server and then to the WeeWx 
> machine.
>
> With this setup, the site is served up fine internally and externally with 
> the updates at archive intervals every 5 minutes. 
>
> I know that the weewx-mqtt extension is installed correctly as I have been 
> able to test it locally and get the websocket updates to work perfectly 
> with the following configs:
>
> *weewx.conf*
> [[MQTT]]
> server_url = mqtt://user:pw@localhost:8883/
> topi

Re: [weewx-user] Re: 4.4.0 bug?

[Matt Hannan]

Never mind. I am a dope. It is mm/dd, not mm/yy. And it may have felt like
I've been trapped in the house for 20 years, but I really haven't been.


On Tue, Mar 30, 2021 at 4:57 PM gjr80  wrote:

> OK, I’ll bite, and the bug is?
>
> Gary
> On Wednesday, 31 March 2021 at 06:47:46 UTC+10 matth...@gmail.com wrote:
>
>> I was just looking at my sensor's web page and switched to Year. I
>> noticed that the X axis has a bug in the labels. Not sure if anyone has
>> seen this or not. This is my first time posting here.
>> [image: weewx_bug.png]
>> 2020 was a doozie for sure, but I am not sure if it is WeeWX's place to
>> whitewash it out of the history books! AHHAHAAHHAA
>> All the charts display the same.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/mR0cwPr0_rw/unsubscribe.
> To unsubscribe from this group and all its topics, 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/63e9ae6c-eb68-40b0-9a26-4d9c03b3ec15n%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/CAO3F_fVWHgU2b83eJwoYzEoDK7Nj-oKLuZWjfte4EXNGZxQ%3DsQ%40mail.gmail.com.

[weewx-user] 4.4.0 bug?

[Matt Hannan]

I was just looking at my sensor's web page and switched to Year. I noticed 
that the X axis has a bug in the labels. Not sure if anyone has seen this 
or not. This is my first time posting here.
[image: weewx_bug.png] 
2020 was a doozie for sure, but I am not sure if it is WeeWX's place to 
whitewash it out of the history books! AHHAHAAHHAA
All the charts display the same.

-- 
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/0208b7cb-aa06-4c3e-9480-d6c063cf2464n%40googlegroups.com.

[weewx-user] Multiple Weather Stations w/Fedora

[Matt R]

Hi all, wondering if anyone has been able to get multiple weather stations 
running using a RedHat based distro (CentOS, Fedora, etc)?

I've been able to successfully run multiple with a Debian distro leveraging 
Matthew Wall's weewx-multi script here:  
https://github.com/weewx/weewx/wiki/weewx-multi.

I've been working my way through making adjustments as necessary.  However, 
before I get too far down the rabbit hole I thought I'd check to see if 
anyone has come out the other side with a working script or knows this'd be 
a dead end endeavor.

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/e0ef6e9d-fb8d-4e69-9425-b8007598055fn%40googlegroups.com.

RE: [weewx-user] Enabling historical data collection on new install

[Matt C]

Exactly the same as my previous reply.  It appears to be adding a record to the DB on each loop but there’s no log entry for historical data. From: steeple ianSent: 07 September 2020 09:25To: weewx-user@googlegroups.comSubject: Re: [weewx-user] Enabling historical data collection on new install what is your syslog showing? On Mon, 7 Sep 2020 at 09:18, icoj...@gmail.com <icojo...@gmail.com> wrote:Still nothing...On Friday, 4 September 2020 at 12:30:07 UTC+1 steep...@gmail.com wrote:Patience is a virtue:-) On Fri, 4 Sep 2020 at 12:22, icoj...@gmail.com  wrote:Hi, It's a aercus badged device.  I have looked at the syslog periodically since it's been up and running and I'm only seeing writes to the database on each current loop, shown below, there are no log records of any other database activity. Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record 2020-09-04 12:20:00 BST (1599218400) to database 'weewx.sdb'Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record 2020-09-04 12:20:00 BST (1599218400) to daily summary in 'weewx.sdb' Thanks for your help On Friday, 4 September 2020 at 12:10:29 UTC+1 steep...@gmail.com wrote:I assume yours is a Maplin badged device? From what I remember when I had the same model it took nearly a day to download a couple of years’ worth of data. Have you looked into the syslog to see what is happening in real time? From the command line run to watch the progress: - sudo tail -f /var/log/syslog  On Fri, 4 Sep 2020 at 11:58, Matt C  wrote:Hi, I think I’ve got about 4-5 years worth but the issue is I’m not seeing any of that yet, I don’t see any data prior to yesterday, so I don’t think the process has even started.   Regards From: steeple ianSent: 04 September 2020 11:53To: weewx...@googlegroups.comSubject: Re: [weewx-user] Enabling historical data collection on new install Matt,From previous experience using an HP1000 it takes a long time to download the data stored on your device. How many years worth? -im On Fri, 4 Sep 2020 at 10:13, icoj...@gmail.com  wrote:Hi, When I first installed weewx a year ago I noticed that it went through a process of adding all the historical data over the course of the first few days.  This then gave me a good historical picture for trend analysis. I've done a fresh install of 4.1.1 on a separate RPi this week and after 2 days I cannot see any historical data.  Is there something I need to do? Many thanks-- You received this message because you are subscribed to the Google Groups "weewx-user" group.To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dbc86e88-e951-482e-92fc-bf086a21c783n%40googlegroups.com.-- You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/RovNaHpvlJs/unsubscribe.To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CADASSaRQ_Y4f1NQJEkDk5zg9PFcYm%3DWmJJwW2jxg%2BksxzjrZAA%40mail.gmail.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+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2310EA5B-2C2F-4904-A8CE-AAEF21E23E70%40hxcore.ol. -- You received this message because you are subscribed to the Google Groups "weewx-user" group.To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5b96f3f1-09a9-4e7d-8e02-5f81fa6d1e13n%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/e80cba1f-3faa-4573-9cb5-43a751d8fdcan%40googlegroups.com.-- You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/RovNaHpvlJs/unsubscribe.To unsubscribe from this group and all its topics, 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/CADASSaQ7Kup6Ki9R4Kh%3DYaMABGxzpN634w3962a-KuwPj8fApw%40mail.gmail.com. 



-- 
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscri

RE: [weewx-user] Enabling historical data collection on new install

[Matt C]

Hi, I think I’ve got about 4-5 years worth but the issue is I’m not seeing any of that yet, I don’t see any data prior to yesterday, so I don’t think the process has even started.   Regards From: steeple ianSent: 04 September 2020 11:53To: weewx-user@googlegroups.comSubject: Re: [weewx-user] Enabling historical data collection on new install Matt,From previous experience using an HP1000 it takes a long time to download the data stored on your device. How many years worth? -im On Fri, 4 Sep 2020 at 10:13, icoj...@gmail.com <icojo...@gmail.com> wrote:Hi, When I first installed weewx a year ago I noticed that it went through a process of adding all the historical data over the course of the first few days.  This then gave me a good historical picture for trend analysis. I've done a fresh install of 4.1.1 on a separate RPi this week and after 2 days I cannot see any historical data.  Is there something I need to do? Many thanks-- You received this message because you are subscribed to the Google Groups "weewx-user" group.To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dbc86e88-e951-482e-92fc-bf086a21c783n%40googlegroups.com.-- You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/RovNaHpvlJs/unsubscribe.To unsubscribe from this group and all its topics, 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/CADASSaRQ_Y4f1NQJEkDk5zg9PFcYm%3DWmJJwW2jxg%2BksxzjrZAA%40mail.gmail.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/2310EA5B-2C2F-4904-A8CE-AAEF21E23E70%40hxcore.ol.

RE: [weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt C]

Ok, thank you for confirming.  I shall wait patiently. From: Susan MackaySent: 03 September 2020 07:17To: weewx-userSubject: Re: [weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed It's not been updated and should not be used with Python 3. This is something I have on my 'to do' list but I must admit it is not the top priority. On the other hand, the source is there if anyone else wants to have a go. Susan (HP1000 driver author)On Thursday, September 3, 2020 at 8:19:07 AM UTC+10, steeple ian wrote:Matt, Are you using Python2 or 3. The driver was last updated 11months ok and may not be compatible with Python3 im. On Wed, 2 Sep 2020 at 23:08, icoj...@gmail.com <icoj...@gmail.com> wrote:This is what I'm seeing...  pi@raspitest:~ $ cd /home/weewx/bin/userpi@raspitest:/home/weewx/bin/user $ dirextensions.py  HP1000.py  __init__.py  installer  __pycache__pi@raspitest:/home/weewx/bin/user $ sudo nano HP1000.py ##    Copyright (c) 2017 Susan Mackay#       acknowledging that this driver code originated from and#       is structured in a similar way to the Weewx 'Simulator' driver code#       that carries the following line:#    ##"""hp1000 driver for the weewx weather system This driver communicates with the HP1000/WS1001/XC0422 and whatever other cloneweather stations respond over the LAN to the 'easyweather' protocol. Communication starts with a UDP IP broadcast on the local subnet to port 6000 tosee if the weather station responds. The broadcast packet is structured as: Offset  Value           Structure       Comment0x00    PC2000          8 byte string   Identifies the calling station0x08    SEARCH          8 byte string   Command On Wednesday, 2 September 2020 at 23:03:15 UTC+1 icoj...@gmail.com wrote:Hi Gary, Yes to both questions. Thanks for your helpOn Wednesday, 2 September 2020 at 22:28:23 UTC+1 gjr80 wrote:OK, let’s start with the obvious. Is HP1000.py in /home/weewx/bin/user and if you view the contents of the file is it legible code? GaryOn Thursday, 3 September 2020 at 07:08:58 UTC+10 icoj...@gmail.com wrote:this is what i'm seeing pi@raspitest:/var/tmp $ sudo /home/weewx/bin/wee_extension --install=/var/tmp/HP1000-master/HP1000.tar.gzRequest to install '/var/tmp/HP1000-master/HP1000.tar.gz'Extracting from tar archive /var/tmp/HP1000-master/HP1000.tar.gzSaving installer file to /home/weewx/bin/user/installer/HP1000Finished installing extension '/var/tmp/HP1000-master/HP1000.tar.gz'pi@raspitest:/var/tmp $ /home/weewx/bin/wee_config --list-driversModule name Driver name Version Statusweewx.drivers.acurite AcuRite 0.4weewx.drivers.cc3000 CC3000 0.40weewx.drivers.fousb FineOffsetUSB 1.20weewx.drivers.simulator Simulator 3.2weewx.drivers.te923 TE923 0.41weewx.drivers.ultimeter Ultimeter 0.41weewx.drivers.vantage Vantage 3.2.1weewx.drivers.wmr100 WMR100 3.5.0weewx.drivers.wmr200 WMR200 3.5.0weewx.drivers.wmr300 WMR300 0.33weewx.drivers.wmr9x8 WMR9x8 3.4.1weewx.drivers.ws1 WS1 0.41weewx.drivers.ws23xx WS23xx 0.41weewx.drivers.ws28xx WS28xx 0.51On Wednesday, 2 September 2020 at 21:59:38 UTC+1 icoj...@gmail.com wrote:Apologies for resurrecting an old thread but I'm trying to do a fresh install using the commands listed above, using Weewx 4.1.1 and the HP1000 driver is not appearing in the list so it cannot be chosen.  Has anything fundamental changes between the previous and current weewx versions? ThanksOn Tuesday, 15 October 2019 at 19:50:53 UTC+1 icoj...@gmail.com wrote:Finally, it's working.  Thanks all for your help.On Tuesday, 15 October 2019 12:51:24 UTC+1, Matt wrote:Hi All, First post. I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I saw that it was posting data but last night most of the data was incorrect (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided to leave it and went to bed.  Today I am seeing better values but all readings appear to be summing/appending to the previous reading.  For example, the temperature has risen from 0 to around 21 degrees very uniformly.  The actual temperature is around 13 degrees. I have an Aercus station, identical to Fine Offset HP1000.  I have set Weewx driver to both 'simulator' and 'Fine Offset' with no change in data. I read somewhere about an HP1000 driver written by aussie susan but editing the daemon file was beyond my capabilities so I couldn't proceed with it. My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html# I appreciate that I will need to provide logs etc, but I am work at the moment and will upload logs later.  I just wanted to get the post up to see if anyone had experienced anything similar or has any advice for a newbie. I love the functionality of weewx and look forward to using it. Many thanks in advance. Matt-- You received this message because you are subscribed to the Google Groups "weewx-user" group.To unsubscribe from this group and stop receiving emails 

[weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Hi again all,

I am seeing connection issues again after turning off MQTT for a while and 
then turning it back on.  I have not changed any configuration yet I am 
seeing "Connected. Waiting for data." constantly.  To summarise, my config 
is as follows:

Belchertown skin.conf:


# MQTT Websockets defaults
mqtt_websockets_enabled = 1
mqtt_websockets_host = 192.168.86.55
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/loop
disconnect_live_website_visitor = 180


weewx.conf:


# [[MQTT]]
server_url = mqtt://pi:***@192.168.86.55:1883/
topic = weather
unit_system = METRIC
binding = archive, loop
aggregation = aggregate
log_failure = true
# log_success = true
[[[inputs]]]
windSpeed
name = windSpeed_mph
units = mile_per_hour
windGust
name = windGust_mph
units = mile_per_hour


I cannot see anything wrong, as I haven't changed the config.

For info, the mosquitto log shows some errors as below, but I don't know 
enough to troubleshoot.  Can anyone suggest anything please?

1591698145: mosquitto version 1.5.7 starting
1591698145: Config loaded from /etc/mosquitto/mosquitto.conf.
1591698145: Opening ipv4 listen socket on port 1883.
1591698145: Opening ipv6 listen socket on port 1883.
1591698145: Opening websockets listen socket on port 9001.
1591698150: New client connected from 192.168.86.36 as website73629308 (c1, 
k60$
1591698177: New connection from 192.168.86.22 on port 1883.
1591698177: New client connected from 192.168.86.22 as 
97f80dbc-e5e5-45c0-8094-$
1591698951: Socket error on client website73629308, disconnecting.
1591698954: New client connected from 192.168.86.36 as website930898639 
(c1, k6$
1591699117: Socket error on client website930898639, disconnecting.
1591699120: New client connected from 192.168.86.36 as website720925838 
(c1, k6$
1591699176: Socket error on client website720925838, disconnecting.
1591699178: New client connected from 192.168.86.36 as website566978445 
(c1, k6$
1591699606: Socket error on client website566978445, disconnecting.
1591699609: New client connected from 192.168.86.36 as website141237067 
(c1, k6$
1591699867: Socket error on client website141237067, disconnecting.
1591699869: New client connected from 192.168.86.36 as website51912235 (c1, 
k60$
1591699933: New client connected from 192.168.86.20 as website271702027 
(c1, k6$
1591699936: Socket error on client website271702027, disconnecting.
1591699939: New client connected from 192.168.86.20 as website286918525 
(c1, k6$
1591699967: Socket error on client website286918525, disconnecting.


Many thanks,

Matt

On Friday, 25 October 2019 19:57:45 UTC+1, Matt wrote:
>
> Hi,
>
> I followed the instructions in 
> https://github.com/poblabs/weewx-belchertown to install an MQTT broker 
> and subscribe to the weather data.  It's working according to the logs...
>
> Weewx syslog
>
> Oct 25 19:49:13 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:49:13 BST (1572029353)
> Oct 25 19:49:29 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:49:29 BST (1572029369)
> Oct 25 19:49:44 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:49:44 BST (1572029384)
> Oct 25 19:50:01 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:50:00 BST (1572029400)
> Oct 25 19:50:17 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:50:16 BST (1572029416)
>
> Mosquitto log
>
> 1572029465: New connection from ::1 on port 1883.
> 1572029465: New client connected from ::1
>  as weewx_7f9ef501 (c1, k60, u'pi').
> 1572029465: Client weewx_7f9ef501 disconnected.
> 1572029481: New connection from ::1 on port 1883.
> 1572029481: New client connected from ::1
>  as weewx_65035d79 (c1, k60, u'pi').
> 1572029481: Client weewx_65035d79 disconnected.
> 1572029497: New connection from ::1 on port 1883.
> 1572029497: New client connected from ::1
>  as weewx_29b0c150 (c1, k60, u'pi').
> 1572029497: Client weewx_29b0c150 disconnected.
> 1572029513: New connection from ::1 on port 1883.
>
> weewx.conf
>
> [[MQTT]]
> server_url = mqtt://pi:xxx@localhost:1883
> topic = weather
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> log_failure = true
> log_success = true
>
> skin.conf
>
> # MQTT Websockets defaults
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = localhost
> mqtt_websockets_port = 1883
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = weather
> disconnect_live_website_visitor = 180
>
> But the webpage cons

[weewx-user] Re: OurWeather by SwitchDoc

[Matt Pitts]

Hi there, did you ever this working with our weather? 

-- 
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/420c4901-abe2-427c-83c6-b74961845500%40googlegroups.com.

[weewx-user] Import weather data generated as Json

[Matt Pitts]

Hi There, 

I have a basic weather station which publishes its data using Rest in a 
JSON format.  
http://www.switchdoc.com/2016/06/ourweather-rest-interface-interface-raspberry-pi/
 

Does anyone know if it's possible and relatively straight forward to get 
this data flowing into WeeWX?  

I'd really appreciate if someone could point me in the right direction?

Cheers

Matt

-- 
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/e3080d03-b652-41f5-9a3e-0ef005c2eae7%40googlegroups.com.

Re: [weewx-user] Re: Generate: Ignoring template /etc/weewx/skins/exfoliation/forecast.html.tmpl: Reason: 'U'

[Matt]

Hi,

I've changed UKMO to , WU, 'UKMO' and it's still failing with exactly 
the same error.  I've attached the forecast template.  I believe it 
produces a forecast page, like the one at 
http://sailing.mit.edu/weather/forecast.html.

Regards,

Matt

On Sunday, 27 October 2019 15:14:54 UTC, p q wrote:
>
> What's in forecast.html.tmpl? 
>
> I'm guessing it doesn't like 
>current_forecast_source = UKMO
>
> If you comment that out or change it to something different, do you get 
> the same error? Try changing it to some nonsense like  and see what 
> happens.
>
>
>
>
> On Sun, Oct 27, 2019 at 7:18 AM Matt > 
> wrote:
>
>> HI Gary,
>>
>> Thank you for your response.  I have attached everything requested.  Let 
>> me know if there is anything else needed.
>>
>> I have changed some of the URLs for the weather gifs and images.  They 
>> are the only changes i've made.
>>
>> Thanks,
>>
>> Matt
>>
>> On Saturday, 26 October 2019 01:40:51 UTC+1, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> These sorts of errors can be particularly challenging to track down, the 
>>> main reason being the line numbers reported are generally meaningless as 
>>> the line numbers refer to a temporary file used by Cheetah that 
>>> unfortunately we do not have access to. Sometimes the best approach is to 
>>> remove portions of the template until you identify the line(s) causing the 
>>> error, though this doe snot work well for complex templates. I know you 
>>> have looked in weewx.conf and the exfoliation skin.conf, but we have 
>>> not nor do we have any idea of your config. Could you please post both. 
>>> Careful with weewx.conf as it may contain sensitive info such as 
>>> usernames, password, keys etc. You can use wee_debug 
>>> <http://weewx.com/docs/utilities.htm#wee_debug_utility> to produce a 
>>> report and post the report, wee_debug should obfuscate most sensitive 
>>> info but check first just in case.
>>>
>>> Can you also post a startup debug log. Edit weewx.conf, set debug = 1, 
>>> save weewx.conf and restart WeeWX. Post the log from WeeWX startup 
>>> through until the error trace is complete, don't edit or skip anything, it 
>>> is important to see the complete startup.
>>>
>>> Have you made any changes, no matter how inconsequential, to any of the 
>>> exfoliation skin files? If so broadly speaking what did you change? Also, 
>>> has the template ever worked or has it always failed?
>>>
>>> Gary
>>>
>>> On Saturday, 26 October 2019 02:24:05 UTC+10, Matt wrote:
>>>>
>>>> Hi,
>>>>
>>>> I've searched the group and the internet generally for this but cannot 
>>>> find any guidance.  I've set up the exfoliation skin but I'm getting an 
>>>> error that I simply can't work out...
>>>>
>>>>
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator: Generate 
>>>> failed with exception ''
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Ignoring 
>>>> template /etc/weewx/skins/exfoliation/forecast.html.tmpl
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Reason: 
>>>> 'U'
>>>> Oct 25 17:20:30 weatherpi weewx[2455]:   Traceback (most recent 
>>>> call last):
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
>>>> Oct 25 17:20:30 weatherpi weewx[2455]:   
>>>> fd.write(str(compiled_template))
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>>>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
>>>> __str__
>>>> Oct 25 17:20:30 weatherpi weewx[2455]:   rc = getattr(self, 
>>>> mainMethName)()
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>>>> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 336, in respond
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>>>> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 113, in 
>>>> __errorCatcher7
>>>> Oct 25 17:20:30 weatherpi weewx[2455]: File "", line 1, 
>>>> in 
>>>> Oct 25 17:20:30 weatherpi weewx[2455]:   KeyError: 'U'
>>>>
>>>>
>>>> I've checked my weewx.conf and skin.conf but I can't put my f

[weewx-user] Re: Generate: Ignoring template /etc/weewx/skins/exfoliation/forecast.html.tmpl: Reason: 'U'

[Matt]

HI Gary,

Thank you for your response.  I have attached everything requested.  Let me 
know if there is anything else needed.

I have changed some of the URLs for the weather gifs and images.  They are 
the only changes i've made.

Thanks,

Matt

On Saturday, 26 October 2019 01:40:51 UTC+1, gjr80 wrote:
>
> Hi,
>
> These sorts of errors can be particularly challenging to track down, the 
> main reason being the line numbers reported are generally meaningless as 
> the line numbers refer to a temporary file used by Cheetah that 
> unfortunately we do not have access to. Sometimes the best approach is to 
> remove portions of the template until you identify the line(s) causing the 
> error, though this doe snot work well for complex templates. I know you 
> have looked in weewx.conf and the exfoliation skin.conf, but we have not 
> nor do we have any idea of your config. Could you please post both. Careful 
> with weewx.conf as it may contain sensitive info such as usernames, 
> password, keys etc. You can use wee_debug 
> <http://weewx.com/docs/utilities.htm#wee_debug_utility> to produce a 
> report and post the report, wee_debug should obfuscate most sensitive 
> info but check first just in case.
>
> Can you also post a startup debug log. Edit weewx.conf, set debug = 1, 
> save weewx.conf and restart WeeWX. Post the log from WeeWX startup 
> through until the error trace is complete, don't edit or skip anything, it 
> is important to see the complete startup.
>
> Have you made any changes, no matter how inconsequential, to any of the 
> exfoliation skin files? If so broadly speaking what did you change? Also, 
> has the template ever worked or has it always failed?
>
> Gary
>
> On Saturday, 26 October 2019 02:24:05 UTC+10, Matt wrote:
>>
>> Hi,
>>
>> I've searched the group and the internet generally for this but cannot 
>> find any guidance.  I've set up the exfoliation skin but I'm getting an 
>> error that I simply can't work out...
>>
>>
>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator: Generate failed 
>> with exception ''
>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Ignoring 
>> template /etc/weewx/skins/exfoliation/forecast.html.tmpl
>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Reason: 'U'
>> Oct 25 17:20:30 weatherpi weewx[2455]:   Traceback (most recent call 
>> last):
>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
>> Oct 25 17:20:30 weatherpi weewx[2455]:   
>> fd.write(str(compiled_template))
>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
>> __str__
>> Oct 25 17:20:30 weatherpi weewx[2455]:   rc = getattr(self, 
>> mainMethName)()
>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 336, in respond
>> Oct 25 17:20:30 weatherpi weewx[2455]: File 
>> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 113, in 
>> __errorCatcher7
>> Oct 25 17:20:30 weatherpi weewx[2455]: File "", line 1, 
>> in 
>> Oct 25 17:20:30 weatherpi weewx[2455]:   KeyError: 'U'
>>
>>
>> I've checked my weewx.conf and skin.conf but I can't put my finger on 
>> anything.  
>>
>> Can anyone point me in the right direction please?
>>
>> Many thanks,
>>
>> Matt
>>
>

-- 
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/7f2a51b6-0b40-40a7-8c65-4368e4d2f153%40googlegroups.com.


weewx.debug
Description: Binary data
# configuration file for the exfoliation skin
# $Id: skin.conf 1779 2017-12-10 22:04:07Z mwall $
# The exfoliation-for-weewx skin was created by Matthew Wall.
#
# This skin can be copied, modified, and distributed as long as this notice
# is included in any derivative work.

[Extras]
version = 0.45

# If you have a Google Analytics ID, specify it here:
# googleAnalyticsId = UA-12345678-1

# which blocks should be displayed on the 'current' page?
current_show_inside = true
current_show_celestial = true
current_show_tides = true
current_show_radar = true
current_show_forecast_summary = true
current_show_forecast_table = true
# which forecast data should be displayed inline on the 'curr

Re: [weewx-user] weewx keeps crashing

[Matt Frost]

It's looking like the issue is resolved. Still no crash so far. Thanks 
again for the help.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b2f6c8ec-de54-42e3-86ff-a171a5903e9c%40googlegroups.com.

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Thank you very much for your help.  I've got it working now...the config I 
had to add is...

[[[inputs]]]
   windSpeed
   name = windSpeed_mph
   units = mile_per_hour
   windGust
   name = windGust_mph
   units = mile_per_hour



On Saturday, 26 October 2019 13:44:27 UTC+1, Pat wrote:
>
> Ah, sorry, my mistake. I mis-read your question. 
>
> You'll want to configure the MQTT extension to send the units you want. So 
> you'd want something like shown in this question 
> <https://github.com/poblabs/weewx-belchertown/issues/23#issuecomment-440529099>
> .
>
> [[MQTT]]
> ... your other mqtt config options here ...
> [[[inputs]]]
> windSpeed
> name = windSpeed_mph
> units = mile_per_hour
>
>
> The mqtt extension documentation 
> <https://github.com/weewx/weewx/wiki/mqtt#examples> has more info too.
>
>
> On Saturday, October 26, 2019 at 8:38:22 AM UTC-4, Pat wrote:
>>
>> A lot of these items are covered in the documentation 
>> <https://github.com/poblabs/weewx-belchertown#table-of-contents>. Check 
>> out this section 
>> <https://github.com/poblabs/weewx-belchertown#using-metric>. 
>>
>>
>> On Saturday, October 26, 2019 at 8:36:24 AM UTC-4, Matt wrote:
>>>
>>> Superb! That worked. Thank you very much.  I am in the UK and use 
>>> degrees Celcius and Miles per hour.  What should I set unit_system to 
>>> (METRIC gives me celcius but kmh, US gives me fahrenheit and miles per 
>>> hour)?
>>>
>>> On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>>>>
>>>> Try changing mqtt_websockets_topic to weather/loop
>>>
>>>

-- 
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/c4c5553d-52c5-423d-bd0b-1a8e0e4ad1a3%40googlegroups.com.

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Thank you very much for your help.  I've got it working now...the config I 
had to add is...

[[[inputs]]]
   windSpeed
   name = windSpeed_mph
   units = mile_per_hour
   windGust
   name = windGust_mph
   units = mile_per_hour



On Saturday, 26 October 2019 13:44:27 UTC+1, Pat wrote:
>
> Ah, sorry, my mistake. I mis-read your question. 
>
> You'll want to configure the MQTT extension to send the units you want. So 
> you'd want something like shown in this question 
> <https://github.com/poblabs/weewx-belchertown/issues/23#issuecomment-440529099>
> .
>
> [[MQTT]]
> ... your other mqtt config options here ...
> [[[inputs]]]
> windSpeed
> name = windSpeed_mph
> units = mile_per_hour
>
>
> The mqtt extension documentation 
> <https://github.com/weewx/weewx/wiki/mqtt#examples> has more info too.
>
>
> On Saturday, October 26, 2019 at 8:38:22 AM UTC-4, Pat wrote:
>>
>> A lot of these items are covered in the documentation 
>> <https://github.com/poblabs/weewx-belchertown#table-of-contents>. Check 
>> out this section 
>> <https://github.com/poblabs/weewx-belchertown#using-metric>. 
>>
>>
>> On Saturday, October 26, 2019 at 8:36:24 AM UTC-4, Matt wrote:
>>>
>>> Superb! That worked. Thank you very much.  I am in the UK and use 
>>> degrees Celcius and Miles per hour.  What should I set unit_system to 
>>> (METRIC gives me celcius but kmh, US gives me fahrenheit and miles per 
>>> hour)?
>>>
>>> On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>>>>
>>>> Try changing mqtt_websockets_topic to weather/loop
>>>
>>>

-- 
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/8e9686ba-c143-405b-9f59-7abdd2732a91%40googlegroups.com.

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Yes, I realise that, but my weewx.conf is the same as the section you 
highlight but I'm still not seeing celcius and mph...

This is my current weewx.conf

[[Defaults]]
   
   [[[Units]]]
   
   # The following section sets what unit to use for each unit 
group.
   # NB: The unit is always in the singular. I.e., 'mile_per_hour',
   # NOT 'miles_per_hour'
   Groups
   
   group_altitude = foot# Options are 'foot' or 'meter'
   group_degree_day = degree_C_day# Options are 
'degree_F_day' or 'degree_C_day'
   group_pressure = mbar# Options are 'inHg', 'mmHg', 
'mbar', or 'hPa'
   group_rain = mm# Options are 'inch', 'cm', or 'mm'
   group_rainrate = mm_per_hour# Options are 
'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
   group_speed = mile_per_hour# Options are 
'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
   group_speed2 = mile_per_hour2# Options are 
'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
   group_temperature = degree_C# Options are 'degree_F' or 
'degree_C'


On Saturday, 26 October 2019 13:38:22 UTC+1, Pat wrote:
>
> A lot of these items are covered in the documentation 
> <https://github.com/poblabs/weewx-belchertown#table-of-contents>. Check 
> out this section 
> <https://github.com/poblabs/weewx-belchertown#using-metric>. 
>
>
> On Saturday, October 26, 2019 at 8:36:24 AM UTC-4, Matt wrote:
>>
>> Superb! That worked. Thank you very much.  I am in the UK and use degrees 
>> Celcius and Miles per hour.  What should I set unit_system to (METRIC gives 
>> me celcius but kmh, US gives me fahrenheit and miles per hour)?
>>
>> On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>>>
>>> Try changing mqtt_websockets_topic to weather/loop
>>
>>

-- 
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/632fdd34-1224-4ad9-a30a-028f27a31d84%40googlegroups.com.

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Superb! That worked. Thank you very much.  I am in the UK and use degrees 
Celcius and Miles per hour.  What should I set unit_system to (METRIC gives 
me celcius but kmh, US gives me fahrenheit and miles per hour)?

On Saturday, 26 October 2019 12:22:41 UTC+1, Pat wrote:
>
> Try changing mqtt_websockets_topic to weather/loop

-- 
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/97c78447-2199-4eeb-8988-33a84900eed1%40googlegroups.com.

Re: [weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Thank you, that's progress. Now it says 'Connected. Waiting for data' but
doesn't change. Again, the logs look ok (to a novice).

On Sat, 26 Oct 2019, 02:07 Pat,  wrote:

> Your host needs to be the IP of your broker. Not localhost.
>
>
> On Friday, October 25, 2019 at 3:57:10 PM UTC-4, Matt wrote:
>>
>> I noticed a typo myself...now changed the websockets port and put the
>> host and topic in quotes, but still not connecting...
>>
>> # MQTT Websockets defaults
>>mqtt_websockets_enabled = 1
>>mqtt_websockets_host = "localhost"
>>mqtt_websockets_port = 9001
>>mqtt_websockets_ssl = 0
>>mqtt_websockets_topic = "weather"
>>    disconnect_live_website_visitor = 180
>>
>>
>>
>> On Friday, 25 October 2019 19:57:45 UTC+1, Matt wrote:
>>>
>>> Hi,
>>>
>>> I followed the instructions in
>>> https://github.com/poblabs/weewx-belchertown to install an MQTT broker
>>> and subscribe to the weather data.  It's working according to the logs...
>>>
>>> Weewx syslog
>>>
>>> Oct 25 19:49:13 weatherpi weewx[3082]: restx: MQTT: Published record
>>> 2019-10-25 19:49:13 BST (1572029353)
>>> Oct 25 19:49:29 weatherpi weewx[3082]: restx: MQTT: Published record
>>> 2019-10-25 19:49:29 BST (1572029369)
>>> Oct 25 19:49:44 weatherpi weewx[3082]: restx: MQTT: Published record
>>> 2019-10-25 19:49:44 BST (1572029384)
>>> Oct 25 19:50:01 weatherpi weewx[3082]: restx: MQTT: Published record
>>> 2019-10-25 19:50:00 BST (1572029400)
>>> Oct 25 19:50:17 weatherpi weewx[3082]: restx: MQTT: Published record
>>> 2019-10-25 19:50:16 BST (1572029416)
>>>
>>> Mosquitto log
>>>
>>> 1572029465: New connection from ::1 on port 1883.
>>> 1572029465: New client connected from ::1
>>>  as weewx_7f9ef501 (c1, k60, u'pi').
>>> 1572029465: Client weewx_7f9ef501 disconnected.
>>> 1572029481: New connection from ::1 on port 1883.
>>> 1572029481: New client connected from ::1
>>>  as weewx_65035d79 (c1, k60, u'pi').
>>> 1572029481: Client weewx_65035d79 disconnected.
>>> 1572029497: New connection from ::1 on port 1883.
>>> 1572029497: New client connected from ::1
>>>  as weewx_29b0c150 (c1, k60, u'pi').
>>> 1572029497: Client weewx_29b0c150 disconnected.
>>> 1572029513: New connection from ::1 on port 1883.
>>>
>>> weewx.conf
>>>
>>> [[MQTT]]
>>> server_url = mqtt://pi:xxx@localhost:1883
>>> topic = weather
>>> unit_system = METRIC
>>> binding = archive, loop
>>> aggregation = aggregate
>>> log_failure = true
>>> log_success = true
>>>
>>> skin.conf
>>>
>>> # MQTT Websockets defaults
>>> mqtt_websockets_enabled = 1
>>> mqtt_websockets_host = localhost
>>> mqtt_websockets_port = 1883
>>> mqtt_websockets_ssl = 0
>>> mqtt_websockets_topic = weather
>>> disconnect_live_website_visitor = 180
>>>
>>> But the webpage constantly says...
>>>
>>> [image: Untitled.png]
>>>
>>> I've been over and over the config, re-writing, adding quotes, you name
>>> it I've tried it but still no success.  Can any bright spark see something
>>> obvious that's wrong...please!!
>>>
>>> Many thanks,
>>>
>>> Matt
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/ykgQYOFGH8I/unsubscribe.
> To unsubscribe from this group and all its topics, 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/b0004563-6cdb-480a-a8e4-64e86f65784e%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/b0004563-6cdb-480a-a8e4-64e86f65784e%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAMz6Xq7ONvvxkaLTV6yhc2dSnGYrVkcmRPFe7FpPPmeW2u0__Q%40mail.gmail.com.

Re: [weewx-user] weewx keeps crashing

[Matt Frost]

OK I'm back up and running. I'll update tomorrow if I see the initial 
problem again or not. 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/0c5832cf-71e5-43bf-8430-96f7dcede4b6%40googlegroups.com.

Re: [weewx-user] weewx keeps crashing

[Matt Frost]

OK I made that change. Now I'm getting this. This errors out much quicker 
than before.

Oct 25 20:15:15 weather weewx[783]: File 
"/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
Oct 25 20:15:15 weather weewx[783]:   
_day_summary.addRecord(record, weight=_weight)
Oct 25 20:15:15 weather weewx[783]: File 
"/usr/share/weewx/weewx/accum.py", line 260, in addRecord
Oct 25 20:15:15 weather weewx[783]:   func(self, record, obs_type, 
add_hilo, weight)
Oct 25 20:15:15 weather weewx[783]: File 
"/usr/share/weewx/weewx/accum.py", line 319, in add_value
Oct 25 20:15:15 weather weewx[783]:   self[obs_type].addSum(val, 
weight=weight)
Oct 25 20:15:15 weather weewx[783]: File 
"/usr/share/weewx/weewx/accum.py", line 95, in addSum
Oct 25 20:15:15 weather weewx[783]:   "got type '%s' ('%s')" % 
(type(val), val))
Oct 25 20:15:15 weather weewx[783]:   ValueError: accum: 
ScalarStats.addSum expected float or int, got type '' 
('3840714016')
Oct 25 20:15:15 weather weewx[783]:   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/db4aeed6-10d3-46ab-9c2f-023289b78180%40googlegroups.com.

Re: [weewx-user] weewx keeps crashing

[Matt Frost]

I have not but will try that next and let you know the results.

>
>>

-- 
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/7fb7e1d1-008d-463b-8c81-15e11c31e9f6%40googlegroups.com.

Re: [weewx-user] weewx keeps crashing

[Matt Frost]

I have not had any luck finding the bad data. Unfortunately it takes 
several hours for it to crash when running normally. I left weewx running 
from command line since last evening but it is still running. I assumed it 
would terminate if it found a bad value again but maybe that was not a 
valid assumption.

-- 
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/9a366392-b353-4c23-80bb-5f5f98fbdf89%40googlegroups.com.

[weewx-user] Re: MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

I noticed a typo myself...now changed the websockets port and put the host 
and topic in quotes, but still not connecting...

# MQTT Websockets defaults
   mqtt_websockets_enabled = 1
   mqtt_websockets_host = "localhost"
   mqtt_websockets_port = 9001
   mqtt_websockets_ssl = 0
   mqtt_websockets_topic = "weather"
   disconnect_live_website_visitor = 180



On Friday, 25 October 2019 19:57:45 UTC+1, Matt wrote:
>
> Hi,
>
> I followed the instructions in 
> https://github.com/poblabs/weewx-belchertown to install an MQTT broker 
> and subscribe to the weather data.  It's working according to the logs...
>
> Weewx syslog
>
> Oct 25 19:49:13 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:49:13 BST (1572029353)
> Oct 25 19:49:29 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:49:29 BST (1572029369)
> Oct 25 19:49:44 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:49:44 BST (1572029384)
> Oct 25 19:50:01 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:50:00 BST (1572029400)
> Oct 25 19:50:17 weatherpi weewx[3082]: restx: MQTT: Published record 
> 2019-10-25 19:50:16 BST (1572029416)
>
> Mosquitto log
>
> 1572029465: New connection from ::1 on port 1883.
> 1572029465: New client connected from ::1
>  as weewx_7f9ef501 (c1, k60, u'pi').
> 1572029465: Client weewx_7f9ef501 disconnected.
> 1572029481: New connection from ::1 on port 1883.
> 1572029481: New client connected from ::1
>  as weewx_65035d79 (c1, k60, u'pi').
> 1572029481: Client weewx_65035d79 disconnected.
> 1572029497: New connection from ::1 on port 1883.
> 1572029497: New client connected from ::1
>  as weewx_29b0c150 (c1, k60, u'pi').
> 1572029497: Client weewx_29b0c150 disconnected.
> 1572029513: New connection from ::1 on port 1883.
>
> weewx.conf
>
> [[MQTT]]
> server_url = mqtt://pi:xxx@localhost:1883
> topic = weather
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> log_failure = true
> log_success = true
>
> skin.conf
>
> # MQTT Websockets defaults
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = localhost
> mqtt_websockets_port = 1883
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = weather
> disconnect_live_website_visitor = 180
>
> But the webpage constantly says...
>
> [image: Untitled.png]
>
> I've been over and over the config, re-writing, adding quotes, you name it 
> I've tried it but still no success.  Can any bright spark see something 
> obvious that's wrong...please!!
>
> Many thanks,
>
> Matt
>

-- 
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/6c3ecc4d-a55f-436a-a84e-5c1999147c55%40googlegroups.com.

[weewx-user] MQTT working but Belchertown skin 'Failed connecting to weather station'

[Matt]

Hi,

I followed the instructions in https://github.com/poblabs/weewx-belchertown to 
install an MQTT broker and subscribe to the weather data.  It's working 
according to the logs...

Weewx syslog

Oct 25 19:49:13 weatherpi weewx[3082]: restx: MQTT: Published record 
2019-10-25 19:49:13 BST (1572029353)
Oct 25 19:49:29 weatherpi weewx[3082]: restx: MQTT: Published record 
2019-10-25 19:49:29 BST (1572029369)
Oct 25 19:49:44 weatherpi weewx[3082]: restx: MQTT: Published record 
2019-10-25 19:49:44 BST (1572029384)
Oct 25 19:50:01 weatherpi weewx[3082]: restx: MQTT: Published record 
2019-10-25 19:50:00 BST (1572029400)
Oct 25 19:50:17 weatherpi weewx[3082]: restx: MQTT: Published record 
2019-10-25 19:50:16 BST (1572029416)

Mosquitto log

1572029465: New connection from ::1 on port 1883.
1572029465: New client connected from ::1
 as weewx_7f9ef501 (c1, k60, u'pi').
1572029465: Client weewx_7f9ef501 disconnected.
1572029481: New connection from ::1 on port 1883.
1572029481: New client connected from ::1
 as weewx_65035d79 (c1, k60, u'pi').
1572029481: Client weewx_65035d79 disconnected.
1572029497: New connection from ::1 on port 1883.
1572029497: New client connected from ::1
 as weewx_29b0c150 (c1, k60, u'pi').
1572029497: Client weewx_29b0c150 disconnected.
1572029513: New connection from ::1 on port 1883.

weewx.conf

[[MQTT]]
server_url = mqtt://pi:xxx@localhost:1883
topic = weather
unit_system = METRIC
binding = archive, loop
aggregation = aggregate
log_failure = true
log_success = true

skin.conf

# MQTT Websockets defaults
mqtt_websockets_enabled = 1
mqtt_websockets_host = localhost
mqtt_websockets_port = 1883
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather
disconnect_live_website_visitor = 180

But the webpage constantly says...

[image: Untitled.png]

I've been over and over the config, re-writing, adding quotes, you name it 
I've tried it but still no success.  Can any bright spark see something 
obvious that's wrong...please!!

Many thanks,

Matt

-- 
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/7994f809-5072-468d-b25d-6d5815b4ca08%40googlegroups.com.

[weewx-user] Re: Generate: Ignoring template /etc/weewx/skins/exfoliation/forecast.html.tmpl: Reason: 'U'

[Matt]

Hi,

I've retyped the lines with UTF-8, I've re-written the META tags per 
W3SCHOOLS convention and I've even deleted them but each time I am getting 
this same error.  Thoroughly confused.

Anyone know what this could be?

Thanks,

Matt

On Friday, 25 October 2019 17:24:05 UTC+1, Matt wrote:
>
> Hi,
>
> I've searched the group and the internet generally for this but cannot 
> find any guidance.  I've set up the exfoliation skin but I'm getting an 
> error that I simply can't work out...
>
>
> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator: Generate failed 
> with exception ''
> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/exfoliation/forecast.html.tmpl
> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Reason: 'U'
> Oct 25 17:20:30 weatherpi weewx[2455]:   Traceback (most recent call 
> last):
> Oct 25 17:20:30 weatherpi weewx[2455]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
> Oct 25 17:20:30 weatherpi weewx[2455]:   
> fd.write(str(compiled_template))
> Oct 25 17:20:30 weatherpi weewx[2455]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
> __str__
> Oct 25 17:20:30 weatherpi weewx[2455]:   rc = getattr(self, 
> mainMethName)()
> Oct 25 17:20:30 weatherpi weewx[2455]: File 
> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 336, in respond
> Oct 25 17:20:30 weatherpi weewx[2455]: File 
> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 113, in 
> __errorCatcher7
> Oct 25 17:20:30 weatherpi weewx[2455]: File "", line 1, in 
> 
> Oct 25 17:20:30 weatherpi weewx[2455]:   KeyError: 'U'
>
>
> I've checked my weewx.conf and skin.conf but I can't put my finger on 
> anything.  
>
> Can anyone point me in the right direction please?
>
> Many thanks,
>
> Matt
>

-- 
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/808cef4f-da6a-41b1-84b1-214fb2451e9c%40googlegroups.com.

Re: [weewx-user] Re: Generate: Ignoring template /etc/weewx/skins/exfoliation/forecast.html.tmpl: Reason: 'U'

[Matt]

Thank you for the response and please forgive my ignorance but which file,
the template file?

On Fri, 25 Oct 2019, 17:32 Andrew Milner, 
wrote:

> the fact that it is line 1 throwing the error makes me suspect a line
> trying to say the encoding is UTF-8 which has acquired a typo of some
> kind.  If indeed there is a UTF8 directive at the top of the file try and
> delete it and retype the line - making sure to use a text editor like nano
> for the editing.
>
>
>
>
> On Friday, 25 October 2019 19:24:05 UTC+3, Matt wrote:
>>
>> Hi,
>>
>> I've searched the group and the internet generally for this but cannot
>> find any guidance.  I've set up the exfoliation skin but I'm getting an
>> error that I simply can't work out...
>>
>>
>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator: Generate failed
>> with exception ''
>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Ignoring
>> template /etc/weewx/skins/exfoliation/forecast.html.tmpl
>> Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Reason: 'U'
>> Oct 25 17:20:30 weatherpi weewx[2455]:   Traceback (most recent call
>> last):
>> Oct 25 17:20:30 weatherpi weewx[2455]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
>> Oct 25 17:20:30 weatherpi weewx[2455]: 
>> fd.write(str(compiled_template))
>> Oct 25 17:20:30 weatherpi weewx[2455]: File
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in
>> __str__
>> Oct 25 17:20:30 weatherpi weewx[2455]:   rc = getattr(self,
>> mainMethName)()
>> Oct 25 17:20:30 weatherpi weewx[2455]: File
>> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 336, in respond
>> Oct 25 17:20:30 weatherpi weewx[2455]: File
>> "_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 113, in
>> __errorCatcher7
>> Oct 25 17:20:30 weatherpi weewx[2455]: File "", line 1,
>> in 
>> Oct 25 17:20:30 weatherpi weewx[2455]:   KeyError: 'U'
>>
>>
>> I've checked my weewx.conf and skin.conf but I can't put my finger on
>> anything.
>>
>> Can anyone point me in the right direction please?
>>
>> Many thanks,
>>
>> Matt
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/rYgFqb3jRhI/unsubscribe.
> To unsubscribe from this group and all its topics, 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/26f88e7f-4314-4fef-af34-0259f8db4327%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/26f88e7f-4314-4fef-af34-0259f8db4327%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAMz6Xq5i3r4Vi9ERQKm7Ysjh%3DgO9w6Dq6fCLYzKS%2Bj9bVmZ2Rw%40mail.gmail.com.

[weewx-user] Generate: Ignoring template /etc/weewx/skins/exfoliation/forecast.html.tmpl: Reason: 'U'

[Matt]

Hi,

I've searched the group and the internet generally for this but cannot find 
any guidance.  I've set up the exfoliation skin but I'm getting an error 
that I simply can't work out...


Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator: Generate failed 
with exception ''
Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/exfoliation/forecast.html.tmpl
Oct 25 17:20:30 weatherpi weewx[2455]: cheetahgenerator:  Reason: 'U'
Oct 25 17:20:30 weatherpi weewx[2455]:   Traceback (most recent call 
last):
Oct 25 17:20:30 weatherpi weewx[2455]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
Oct 25 17:20:30 weatherpi weewx[2455]:   
fd.write(str(compiled_template))
Oct 25 17:20:30 weatherpi weewx[2455]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
__str__
Oct 25 17:20:30 weatherpi weewx[2455]:   rc = getattr(self, 
mainMethName)()
Oct 25 17:20:30 weatherpi weewx[2455]: File 
"_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 336, in respond
Oct 25 17:20:30 weatherpi weewx[2455]: File 
"_etc_weewx_skins_exfoliation_forecast_html_tmpl.py", line 113, in 
__errorCatcher7
Oct 25 17:20:30 weatherpi weewx[2455]: File "", line 1, in 

Oct 25 17:20:30 weatherpi weewx[2455]:   KeyError: 'U'


I've checked my weewx.conf and skin.conf but I can't put my finger on 
anything.  

Can anyone point me in the right direction please?

Many thanks,

Matt

-- 
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/168b4c56-aba0-49bf-975a-ab9bb10a2764%40googlegroups.com.

[weewx-user] weewx keeps crashing

[Matt Frost]

I upgraded to weewx 3.9.2 a few months back. Everything was fine for awhile 
but then several weeks ago weewx started crashing. Here is what I currently 
see:

pi@weather:~ $ sudo /etc/init.d/weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (exited) since Wed 2019-10-23 17:27:22 CDT; 24h ago
  Process: 425 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
Oct 24 09:05:15 weather weewx[758]: File 
"/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
Oct 24 09:05:15 weather weewx[758]:   
_day_summary.addRecord(record, weight=_weight)
Oct 24 09:05:15 weather weewx[758]: File 
"/usr/share/weewx/weewx/accum.py", line 260, in addRecord
Oct 24 09:05:15 weather weewx[758]:   func(self, record, obs_type, 
add_hilo, weight)
Oct 24 09:05:15 weather weewx[758]: File 
"/usr/share/weewx/weewx/accum.py", line 318, in add_value
Oct 24 09:05:15 weather weewx[758]:   self[obs_type].addHiLo(val, 
record['dateTime'])
Oct 24 09:05:15 weather weewx[758]: File 
"/usr/share/weewx/weewx/accum.py", line 78, in addHiLo
Oct 24 09:05:15 weather weewx[758]:   "got type '%s' ('%s')" % 
(type(val), val))
Oct 24 09:05:15 weather weewx[758]:   ValueError: accum: 
ScalarStats.addHiLo expected float or int, got type '' 
('3840714016')
Oct 24 09:05:15 weather weewx[758]:   Exiting.
pi@weather:~ $

I found a couple of posts online regarding an issue in cmon that sounded 
like the same issue I am seeing and applied these fixes:

456 if k in self.last_net[iface]:
457 x = int(values[i]) - 
self.last_net[iface][k]
458 if x < 0:
459 maxcnt = 0x1 # 32-bit 
counter
460 if x + maxcnt < 0:
461 maxcnt = 0x1 # 
64-bit counter
462 x += maxcnt
463 if x > 2147483648:
464 x = 2147483648
465 record['net_' + iface + '_' + k] = 
int(x)

Unfortunately I still have the same issue. weewx will run for a few hours 
and crash again. Restarting weewx does not work I have to reboot my pi to 
get weewx to start again and run for a few more hours.

Any help is appreciated.

-- 
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/6fda9f5c-cf54-44e0-b5a3-547eede77d94%40googlegroups.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Matt]

Looks perfect!

Thank you Susan

On Wed, 23 Oct 2019, 02:36 Susan Mackay,  wrote:

> After a bit of trial and error, I've managed to find the incantation that
> lets Github display the installation lines correctly from the 'readme.md'
> file.
> Hopefully this should stop the problems for others in the future.
> Susan
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/BwZstE2zi6Y/unsubscribe.
> To unsubscribe from this group and all its topics, 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/f14267a9-3f81-43c3-aeec-307be5c95b66%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/CAMz6Xq4LYRdfLhMbyubWqbNv_hYZtuEGtCDnvmpygT76qSo2Ow%40mail.gmail.com.

RE: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Matt]

Thanks Susan.  But please don’t feel the need to apologize.  I appreciate your 
efforts and without people like you the lesser able people like me wouldn’t be 
able to learn and enjoy these things!

From: Susan Mackay
Sent: 18 October 2019 02:51
To: weewx-user
Subject: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

The lack of a 'new line' before the 2nd 'sudo' has something to do with the 
formatting of the 'markdown' file I created as it is begin displayed in GitHub 
and my lack of experience in doing these things - sorry.
I'll try to get it sorted out once I work out why that part does not work 
whereas it does in other places in the same file.
Susan

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/BwZstE2zi6Y/unsubscribe.
To unsubscribe from this group and all its topics, 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/0a796fc9-fb34-41cc-a326-fc87df16abbc%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/5da95e09.1c69fb81.41808.5f2a%40mx.google.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Matt]

Hi Susan,

I added a post about the struggles I faced a few days ago called " 

New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports 
show values being appended/summed
", this gives a potted history of things.

What I did to get it working is contained in one of the replies on that 
post but essentially:

I'm making progress.  I managed to install the driver using a number of 
different sources and lots of trial and error.  For anyone else seeing 
problems, what I did was:

wget -P /var/tmp weewx-hp1000.zip 
https://github.com/AussieSusan/HP1000/archive/master.zip
cd var/tmp
unzip master.zip
sudo ./wee_extension --install=/var/tmp/HP1000-master/hp1000.tar.gz
sudo ./wee_config --reconfigure

Chose the number next to HP1000 then restarted weewx.

It's fantastic now it's working and I'm hoping to end up with something 
like Ian has got eventually.

On Thursday, 17 October 2019 03:47:05 UTC+1, Susan Mackay wrote:

> Could you elaborate a bit more for the sake of others trying to do the 
> same? (Also for me - lets me know what problems others have overcome 
> if/when I come to update the code.)
> Susan
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d4c996cf-d494-41c2-8b91-cf381cbf6966%40googlegroups.com.

Re: [weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Matt]

Thanks Susan. I managed to get it working using Ian's suggestions and a bit
of trial and error.  It's great by the way!

On Wed, 16 Oct 2019, 02:48 Susan Mackay,  wrote:

> Hi Matt,
>
> I have not tried the driver on anything but Rasbian Stretch and against
> V3.6.2. (Still on the 'to do' list as is re-writing for Python 3.)
>
> Perhaps Ian Rich can provide some details of what he did as he seems to
> have this configuration working.
>
> Having said that the "sudo" should be the first part of each command.
>
> Susan
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d213d203-41ab-4725-8cbd-9c5bddd10954%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/d213d203-41ab-4725-8cbd-9c5bddd10954%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAMz6Xq59%2B48YDDUNm8UawaD5q5PEAW_w%3D1gxdDk4Nn47tZgLXg%40mail.gmail.com.

[weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Finally, it's working. 

Thanks all for your help.

On Tuesday, 15 October 2019 12:51:24 UTC+1, Matt wrote:
>
> Hi All,
>
> First post.
>
> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I saw 
> that it was posting data but last night most of the data was incorrect 
> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided 
> to leave it and went to bed.  Today I am seeing better values but all 
> readings appear to be summing/appending to the previous reading.  For 
> example, the temperature has risen from 0 to around 21 degrees very 
> uniformly.  The actual temperature is around 13 degrees.
>
> I have an Aercus station, identical to Fine Offset HP1000.  I have set 
> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>
> I read somewhere about an HP1000 driver written by aussie susan but 
> editing the daemon file was beyond my capabilities so I couldn't proceed 
> with it.
>
> My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html#
>
> I appreciate that I will need to provide logs etc, but I am work at the 
> moment and will upload logs later.  I just wanted to get the post up to see 
> if anyone had experienced anything similar or has any advice for a newbie.
>
> I love the functionality of weewx and look forward to using it.
>
> Many thanks in advance.
>
> Matt
>

-- 
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/b9fd7665-fec9-493d-913d-b189a3c8f54f%40googlegroups.com.

[weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Looks good so far...

Oct 15 19:35:05 raspberrypi weewx[2957]: HP1000: Connected to address 
('192.168.1.255', 61184)
Oct 15 19:35:06 raspberrypi weewx[2957]: HP1000: Established contact at 
15/10/19 19:35:06
Oct 15 19:35:06 raspberrypi weewx[2957]: HP1000: Retrieving startup records

Now, I'm waiting...I'd like to add 'patiently', but I can't!

On Tuesday, 15 October 2019 12:51:24 UTC+1, Matt wrote:
>
> Hi All,
>
> First post.
>
> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I saw 
> that it was posting data but last night most of the data was incorrect 
> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided 
> to leave it and went to bed.  Today I am seeing better values but all 
> readings appear to be summing/appending to the previous reading.  For 
> example, the temperature has risen from 0 to around 21 degrees very 
> uniformly.  The actual temperature is around 13 degrees.
>
> I have an Aercus station, identical to Fine Offset HP1000.  I have set 
> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>
> I read somewhere about an HP1000 driver written by aussie susan but 
> editing the daemon file was beyond my capabilities so I couldn't proceed 
> with it.
>
> My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html#
>
> I appreciate that I will need to provide logs etc, but I am work at the 
> moment and will upload logs later.  I just wanted to get the post up to see 
> if anyone had experienced anything similar or has any advice for a newbie.
>
> I love the functionality of weewx and look forward to using it.
>
> Many thanks in advance.
>
> Matt
>

-- 
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/71d9e9d1-922b-4951-b0db-7c6d865b444a%40googlegroups.com.

[weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

The ip_address_mask which is the IP address of the weather station, goes in 
the HP1000 section of the weewx.conf file as follows:

ip_address_mask = "192.168.1.255"


On Tuesday, 15 October 2019 12:51:24 UTC+1, Matt wrote:
>
> Hi All,
>
> First post.
>
> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I saw 
> that it was posting data but last night most of the data was incorrect 
> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided 
> to leave it and went to bed.  Today I am seeing better values but all 
> readings appear to be summing/appending to the previous reading.  For 
> example, the temperature has risen from 0 to around 21 degrees very 
> uniformly.  The actual temperature is around 13 degrees.
>
> I have an Aercus station, identical to Fine Offset HP1000.  I have set 
> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>
> I read somewhere about an HP1000 driver written by aussie susan but 
> editing the daemon file was beyond my capabilities so I couldn't proceed 
> with it.
>
> My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html#
>
> I appreciate that I will need to provide logs etc, but I am work at the 
> moment and will upload logs later.  I just wanted to get the post up to see 
> if anyone had experienced anything similar or has any advice for a newbie.
>
> I love the functionality of weewx and look forward to using it.
>
> Many thanks in advance.
>
> Matt
>

-- 
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/cd53417c-a524-4f66-b6db-34f60f63db48%40googlegroups.com.

[weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Hi,

I'm making progress.  I managed to install the driver using a number of 
different sources and lots of trial and error.  For anyone else seeing 
problems, what I did was:

wget -P /var/tmp weewx-hp1000.zip 
https://github.com/AussieSusan/HP1000/archive/master.zip
cd var/tmp
unzip master.zip
sudo ./wee_extension --install=/var/tmp/HP1000-master/hp1000.tar.gz
sudo ./wee_config --reconfigure

Chose the number next to HP1000 then restarted weewx.

Now, next issue is that there appear to be some settings I've got to set.

The log says:

/home/weewx $ tail -f /var/log/syslog
Oct 15 19:19:09 raspberrypi weewx[2874]: engine: Locale is 'en_GB.UTF-8'
Oct 15 19:19:09 raspberrypi weewx[2874]: engine: pid file is 
/var/run/weewx.pid
Oct 15 19:19:09 raspberrypi weewx[2878]: engine: Using configuration file 
/home/weewx/weewx.conf
Oct 15 19:19:09 raspberrypi weewx[2878]: engine: Loading station type 
HP1000 (user.HP1000)
Oct 15 19:19:09 raspberrypi weewx[2864]: Starting weewx weather system: 
weewx.
Oct 15 19:19:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
Oct 15 19:19:09 raspberrypi weewx[2878]: HP1000: HP1000 Starting
Oct 15 19:19:09 raspberrypi weewx[2878]: engine: Import of driver failed: 
Required parameter 'ip_address_mask' 
has not been specified or could not be determined  
   ()
Oct 15 19:19:09 raspberrypi weewx[2878]: engine: Unable to load driver: 
Required parameter 'ip_address_mask' 
has not been specified or could not be determined
Oct 15 19:19:09 raspberrypi weewx[2878]:   Exiting...

I'm trying to find out where I need to specify the ip_address_mask now.

Cheers,

Matt

On Tuesday, 15 October 2019 12:51:24 UTC+1, Matt wrote:
>
> Hi All,
>
> First post.
>
> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I saw 
> that it was posting data but last night most of the data was incorrect 
> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided 
> to leave it and went to bed.  Today I am seeing better values but all 
> readings appear to be summing/appending to the previous reading.  For 
> example, the temperature has risen from 0 to around 21 degrees very 
> uniformly.  The actual temperature is around 13 degrees.
>
> I have an Aercus station, identical to Fine Offset HP1000.  I have set 
> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>
> I read somewhere about an HP1000 driver written by aussie susan but 
> editing the daemon file was beyond my capabilities so I couldn't proceed 
> with it.
>
> My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html#
>
> I appreciate that I will need to provide logs etc, but I am work at the 
> moment and will upload logs later.  I just wanted to get the post up to see 
> if anyone had experienced anything similar or has any advice for a newbie.
>
> I love the functionality of weewx and look forward to using it.
>
> Many thanks in advance.
>
> Matt
>

-- 
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/001fe144-3071-43b4-a87b-9302ff6fb163%40googlegroups.com.

Re: [weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Understood.  Thank you.

On Tuesday, 15 October 2019 18:06:40 UTC+1, steeple ian wrote:
>
> Matt,
> Yes the syntax is incorrect. I can’t give you a full answer for an hour or 
> so as I am rather occupied at the moment. Have a look at other driver 
> install instructions and follow the same logic. Check back later if you are 
> still having trouble and I will walk you through the installation.
> Ian
>
> On Tue, 15 Oct 2019 at 17:58, Matt > 
> wrote:
>
>> Thank you. I think I realise that now however I'm unable to install the 
>> HP1000 driver as the instructions on its GitHub page aren't working for me.
>>
>> Still investigating...
>>
>> On Tue, 15 Oct 2019, 15:56 steeple ian, > 
>> wrote:
>>
>>> Matt,
>>> You need to use the HP1000 driver or Interceptor driver for this device 
>>> not the Fine Offset one. If my memory serves me correctly the FO driver is 
>>> for a USB device where as the HP1000 is a wireless device.
>>> Ian
>>>
>>> Sent from my iPhone
>>>
>>> On 15 Oct 2019, at 15:27, Matt > wrote:
>>>
>>> 
>>> Thank you, that makes perfect sense.  I'm sure I followed instructions 
>>> which said to select 'Simulator'.  I'll change to Fine Offset when I get 
>>> home, after I've retrieved the logs.  I'll also try to find out more about 
>>> how to install the driver for HP1000 but google wasn't too helpful last 
>>> night!
>>>
>>> On Tuesday, 15 October 2019 15:13:04 UTC+1, Andrew Milner wrote:
>>>>
>>>> the chances are that your uniform incrementing values are the simulator 
>>>> data whic I hthink looks like a sine wave!!
>>>>
>>>> chances are that you are set on simulator and are not reading any data 
>>>> from the station.  
>>>>
>>>> Only the log will provide the answer.  the simulator does exactly what 
>>>> it says, it simulates A weather station (Not a specific type) and 
>>>> generates 
>>>> data to be put in the database which can then be used to generate reports. 
>>>>  
>>>> It is not simulating your specific station!!
>>>>
>>>> when you post the log post from before starting weewx until at keast 
>>>> one archive interval has passed - the length of the interval is whatever 
>>>> you have specified in weewx.conf
>>>>
>>>>
>>>>
>>>> On Tuesday, 15 October 2019 14:51:24 UTC+3, Matt wrote:
>>>>>
>>>>> Hi All,
>>>>>
>>>>> First post.
>>>>>
>>>>> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I 
>>>>> saw that it was posting data but last night most of the data was 
>>>>> incorrect 
>>>>> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I 
>>>>> decided 
>>>>> to leave it and went to bed.  Today I am seeing better values but all 
>>>>> readings appear to be summing/appending to the previous reading.  For 
>>>>> example, the temperature has risen from 0 to around 21 degrees very 
>>>>> uniformly.  The actual temperature is around 13 degrees.
>>>>>
>>>>> I have an Aercus station, identical to Fine Offset HP1000.  I have set 
>>>>> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>>>>>
>>>>> I read somewhere about an HP1000 driver written by aussie susan but 
>>>>> editing the daemon file was beyond my capabilities so I couldn't proceed 
>>>>> with it.
>>>>>
>>>>> My station can be seen at: 
>>>>> https://www.pwsweather.com/obs/ILITTLEW9.html#
>>>>>
>>>>> I appreciate that I will need to provide logs etc, but I am work at 
>>>>> the moment and will upload logs later.  I just wanted to get the post up 
>>>>> to 
>>>>> see if anyone had experienced anything similar or has any advice for a 
>>>>> newbie.
>>>>>
>>>>> I love the functionality of weewx and look forward to using it.
>>>>>
>>>>> Many thanks in advance.
>>>>>
>>>>> Matt
>>>>>
>>>> -- 
>>> 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 weew

Re: [weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Thank you. I think I realise that now however I'm unable to install the
HP1000 driver as the instructions on its GitHub page aren't working for me.

Still investigating...

On Tue, 15 Oct 2019, 15:56 steeple ian,  wrote:

> Matt,
> You need to use the HP1000 driver or Interceptor driver for this device
> not the Fine Offset one. If my memory serves me correctly the FO driver is
> for a USB device where as the HP1000 is a wireless device.
> Ian
>
> Sent from my iPhone
>
> On 15 Oct 2019, at 15:27, Matt  wrote:
>
> 
> Thank you, that makes perfect sense.  I'm sure I followed instructions
> which said to select 'Simulator'.  I'll change to Fine Offset when I get
> home, after I've retrieved the logs.  I'll also try to find out more about
> how to install the driver for HP1000 but google wasn't too helpful last
> night!
>
> On Tuesday, 15 October 2019 15:13:04 UTC+1, Andrew Milner wrote:
>>
>> the chances are that your uniform incrementing values are the simulator
>> data whic I hthink looks like a sine wave!!
>>
>> chances are that you are set on simulator and are not reading any data
>> from the station.
>>
>> Only the log will provide the answer.  the simulator does exactly what it
>> says, it simulates A weather station (Not a specific type) and generates
>> data to be put in the database which can then be used to generate reports.
>> It is not simulating your specific station!!
>>
>> when you post the log post from before starting weewx until at keast one
>> archive interval has passed - the length of the interval is whatever you
>> have specified in weewx.conf
>>
>>
>>
>> On Tuesday, 15 October 2019 14:51:24 UTC+3, Matt wrote:
>>>
>>> Hi All,
>>>
>>> First post.
>>>
>>> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I
>>> saw that it was posting data but last night most of the data was incorrect
>>> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided
>>> to leave it and went to bed.  Today I am seeing better values but all
>>> readings appear to be summing/appending to the previous reading.  For
>>> example, the temperature has risen from 0 to around 21 degrees very
>>> uniformly.  The actual temperature is around 13 degrees.
>>>
>>> I have an Aercus station, identical to Fine Offset HP1000.  I have set
>>> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>>>
>>> I read somewhere about an HP1000 driver written by aussie susan but
>>> editing the daemon file was beyond my capabilities so I couldn't proceed
>>> with it.
>>>
>>> My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html
>>> #
>>>
>>> I appreciate that I will need to provide logs etc, but I am work at the
>>> moment and will upload logs later.  I just wanted to get the post up to see
>>> if anyone had experienced anything similar or has any advice for a newbie.
>>>
>>> I love the functionality of weewx and look forward to using it.
>>>
>>> Many thanks in advance.
>>>
>>> Matt
>>>
>> --
> 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/a350f353-ffa0-4410-9256-6bbac88444ae%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/a350f353-ffa0-4410-9256-6bbac88444ae%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> --
> 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/18C42336-65BB-409B-BC1B-2C231927FFB3%40gmail.com
> <https://groups.google.com/d/msgid/weewx-user/18C42336-65BB-409B-BC1B-2C231927FFB3%40gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAMz6Xq51ZY%2Bcv5Mw6H7U7-VkC74JT8CwNYHQVBJ7%3Dt8mD2sm%2Bg%40mail.gmail.com.

[weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Matt]

Hi Susan,

I'm trying to get the HP1000 driver installed and everything I'm trying 
(following your instructions on github) is failing.

Is this command correct?  "sudo cd sudo python ./bin/wee_extension 
--install /HP1000 sudo python ./bin/wee_config --reconfigure"

Is it one command or many?  None of them work for me.  I'm tearing my hair 
out as I'm not a coder and it's CLI is not intuitive to me.

I've also tried downloading the tar.gz file and unzipping it in my 
raspberry pi but i get "tarfile.ReadError: file could not be opened 
successfully
"

Please help!!

On Tuesday, 13 August 2019 04:05:50 UTC+1, Susan Mackay wrote:
>
> Blush!
>
> On Sunday, August 11, 2019 at 5:56:30 AM UTC+10, Ian Rich wrote:
>>
>>  (contributed by Aussie Susan, which is fantastic btw!) 
>>
>

-- 
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/3feeb01a-963a-4388-9c85-c878d15a9c4c%40googlegroups.com.

[weewx-user] Re: New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Thank you, that makes perfect sense.  I'm sure I followed instructions 
which said to select 'Simulator'.  I'll change to Fine Offset when I get 
home, after I've retrieved the logs.  I'll also try to find out more about 
how to install the driver for HP1000 but google wasn't too helpful last 
night!

On Tuesday, 15 October 2019 15:13:04 UTC+1, Andrew Milner wrote:
>
> the chances are that your uniform incrementing values are the simulator 
> data whic I hthink looks like a sine wave!!
>
> chances are that you are set on simulator and are not reading any data 
> from the station.  
>
> Only the log will provide the answer.  the simulator does exactly what it 
> says, it simulates A weather station (Not a specific type) and generates 
> data to be put in the database which can then be used to generate reports.  
> It is not simulating your specific station!!
>
> when you post the log post from before starting weewx until at keast one 
> archive interval has passed - the length of the interval is whatever you 
> have specified in weewx.conf
>
>
>
> On Tuesday, 15 October 2019 14:51:24 UTC+3, Matt wrote:
>>
>> Hi All,
>>
>> First post.
>>
>> I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I 
>> saw that it was posting data but last night most of the data was incorrect 
>> (e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided 
>> to leave it and went to bed.  Today I am seeing better values but all 
>> readings appear to be summing/appending to the previous reading.  For 
>> example, the temperature has risen from 0 to around 21 degrees very 
>> uniformly.  The actual temperature is around 13 degrees.
>>
>> I have an Aercus station, identical to Fine Offset HP1000.  I have set 
>> Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.
>>
>> I read somewhere about an HP1000 driver written by aussie susan but 
>> editing the daemon file was beyond my capabilities so I couldn't proceed 
>> with it.
>>
>> My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html#
>>
>> I appreciate that I will need to provide logs etc, but I am work at the 
>> moment and will upload logs later.  I just wanted to get the post up to see 
>> if anyone had experienced anything similar or has any advice for a newbie.
>>
>> I love the functionality of weewx and look forward to using it.
>>
>> Many thanks in advance.
>>
>> Matt
>>
>

-- 
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/a350f353-ffa0-4410-9256-6bbac88444ae%40googlegroups.com.

[weewx-user] New User Setup issues - Raspberry Pi, Fine Offset HP1000 - weather reports show values being appended/summed

[Matt]

Hi All,

First post.

I got Weewx set up on a brand new Raspberry Pi 3 model B yesterday.  I saw 
that it was posting data but last night most of the data was incorrect 
(e.g. outside temp 0 degrees C when it was actually 10 degrees).  I decided 
to leave it and went to bed.  Today I am seeing better values but all 
readings appear to be summing/appending to the previous reading.  For 
example, the temperature has risen from 0 to around 21 degrees very 
uniformly.  The actual temperature is around 13 degrees.

I have an Aercus station, identical to Fine Offset HP1000.  I have set 
Weewx driver to both 'simulator' and 'Fine Offset' with no change in data.

I read somewhere about an HP1000 driver written by aussie susan but editing 
the daemon file was beyond my capabilities so I couldn't proceed with it.

My station can be seen at: https://www.pwsweather.com/obs/ILITTLEW9.html#

I appreciate that I will need to provide logs etc, but I am work at the 
moment and will upload logs later.  I just wanted to get the post up to see 
if anyone had experienced anything similar or has any advice for a newbie.

I love the functionality of weewx and look forward to using it.

Many thanks in advance.

Matt

-- 
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/968885c3-4381-4120-9db0-d656953e2144%40googlegroups.com.

Re: [weewx-user] Re: WeeWx SDR Crashing

[Matt Gordon]

What hardware is this running on ?  the SDR radios are quite power hungry 
and a marginal power supply may cause this and also a bad SDR. 

Thanks

On Monday, March 4, 2019 at 7:49:38 AM UTC-5, miso wrote:
>
> Yes, i have installed it recently. also the Weather Station running the 
> latest firmware
>
> miso
>
>
> po 4. 3. 2019 o 13:40 Andy > napísal(a):
>
>> https://github.com/matthewwall/weewx-sdr/issues/45
>>
>> Are you using the latest weeex sdr driver?
>>
>> Andy
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

[weewx-user] Re: New setup on Pi w/bme280 and Acurite 5-in-1 via SDR

[Matt Gordon]

>
> please post your code for collecting data from the bme280 and for 
> converting the resulting units. 
>
> the SDR generates packets with different unit systems, depending on the 
> sensors (and depending on the format - for example, for the 5n1 the old 
> line format is METRIC whereas the JSON format is US).  in fact, the 5n1 
> JSON packets are US, but the tower packets (is that what you mean by 
> "2-in-1"?) are METRIC.
>
> so if your bme280 code does not adapt to the unit system in each packet, 
> then you will have problems such as those you report.
>
> m
>

Ah, this makes sense now, a great explanation of how SDR was crafting 
packets - thank you!  So when weewx was receiving the 5n1 packets it would 
combine with the temp and pressure data resulting in a unit mismatch. But 
with the 2in1 it was a happy potato.  

I had attempted to create a python script to dynamically create loop 
packets however my coding skills are a bit rusty so i went with pond.py and 
this script I crafted - nothing identifies the what units are in the loop 
packet.  That will be a project for a rainy day.

sensorread.py: called via cron every 5 mins
#import syslog
#import weewx
import bme280
import smbus2
#import time
log_file = open("/var/ramdisk/bmelog.txt", "w")
port = 1
address = 0x76
bus = smbus2.SMBus(port)
calibration_params = bme280.load_calibration_params(bus, address)
data = bme280.sample(bus, address, calibration_params)
data.pressure = (data.pressure * 0.029529980164712)
data.temperature = ((data.temperature*1.8)+32)
log_file.write("inTemp=%f\r\n" % data.temperature)
log_file.write("pressure=%f\r\n" % data.pressure)
log_file.close()
#print (data.pressure)
#print (data.temperature)

and pond.py:

import syslogimport weewxfrom weewx.wxengine import StdService
class PondService(StdService):
def __init__(self, engine, config_dict):
super(PondService, self).__init__(engine, config_dict)  
d = config_dict.get('PondService', {})
self.filename = d.get('filename', '/var/tmp/pond.txt')
syslog.syslog(syslog.LOG_INFO, "pond: using %s" % self.filename)
self.bind(weewx.NEW_ARCHIVE_RECORD, self.read_file)

def read_file(self, event):
try:
with open(self.filename) as f:
value = f.read()
syslog.syslog(syslog.LOG_DEBUG, "pond: found value of %s" % value)
event.record['extraTemp1'] = float(value)
except Exception as e:
syslog.syslog(syslog.LOG_ERR, "pond: cannot read value: %s" % e)




 

-- 
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: New setup on Pi w/bme280 and Acurite 5-in-1 via SDR

[Matt Gordon]

As a follow up to this, it would appear that the SDR driver does not play 
nice when using two acurite sensors. in my case i was reading 
wind/precipitation from the 5-in-1 and temp and humidity from the 2-in-1. 
 As soon as i commented out the readings from the 2-in-1 and then converted 
the units from the bme280 over to imperial everything behaved normally.

-- 
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] New setup on Pi w/bme280 and Acurite 5-in-1 via SDR

[Matt Gordon]

Setup:
Raspberry Pi Model B
Acurite 5-in-1 - via SDR
BME280 via direct connect (i2c)
Noelec SDR usb receiver
pond.py script to read BME280 from cronjob that creates a text file with 
pressure and inside temperature
target units : C


Hi folks, I just setup this station last week with an acurite 2-in-1 and 
bme280.  after mucking around with the scripts to generate data from the 
bme280 i had it running for a couple of days.  Today I received my acurite 
5-in-1 and added it into the SDR configuration.

Since then, i'm noticing the following in /var/log/syslog:

LOOP value 'pressure' 1007.0 outside limits (24.0, 34.5)


As soon as i disable the 5-in-1 i have no issue with it and the 2-in-1

here is one of the data packets i captured from rtl_433:

"time" : "2019-02-27 17:28:55", "model" : "Acurite 5n1 sensor", "sensor_id" 
: 27, "channel" : "C", "sequence_num" : 2, "battery" : "OK", "message_type" 
: 56, "wind_speed_kph" : 0.000, "temperature_F" : 29.800, "humidity" : 53}

The only difference I can see here is that the temperature on the new unit 
is being reported in F vs my old 2-in-1 being reported in C.

The output from the BME280 is coming in metric using mbar and C, which 
wasn't an issue with the old sensor.  I have a feeling weewx was happily 
converting both over to imperial for the DB and now is confused in 
receiving both imperial and metric data in the loop packet.  


Here is the loop packet with the 5-in-1 and pond.py enabled:

LOOP:   2019-02-27 15:48:52 EST (1551300532) altimeter: 30.0591082669, 
barometer: 30.0943117592, cloudbase: 1289.90616161, dateTime: 1551300532, 
dewpoint: 16.5069359108, heatindex: 20.84, humidex: 20.84, inTemp: 
71.0218886, maxSolarRad: None, outBatteryStatus: 0, outHumidity: 83.0, 
outTemp: 20.84, pressure: 29.738159265, rainRate: 0, usUnits: 1LOOP:   2019-
02-27 15:48:56 EST (1551300536) altimeter: None, dateTime: 1551300536, 
inTemp: 21.678827, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 
1, windSpeed: 1.65036598854




Here is the loop packet with just the 5-in-1:

LOOP:   2019-02-27 15:50:48 EST (1551300648) dateTime: 1551300648, 
maxSolarRad: None, rainRate: 0, usUnits: 1, windSpeed: 2.16424124175
LOOP:   2019-02-27 15:50:48 EST (1551300648) cloudbase: 1289.90616161, 
dateTime: 1551300648, dewpoint: 16.5069359108, heatindex: 20.84, humidex: 
20.84, maxSolarRad: None, outBatteryStatus: 0, outHumidity: 83.0, outTemp: 
20.84, rainRate: 0, usUnits: 1



Any thoughts?  I tried converting the output from my BME280 over to 
imperial however that produced even stranger values 

Thanks!


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

Re: [weewx-user] Re: WeeWx changing time on Davis Vantage Vue Console?

[Matt]

Gary,
I think you're right.  I don't have a local time set.  After some digging 
I'm stuck at a bigger problem.  

I first did a 

pi@raspberrypi:~ $ sudo raspi-config
received an error when trying to set the timezone through the gui

tried this too, no luck .  I've also tried updating libraries and 
dependencies and started all over and get the same errors. Thoughts?

pi@raspberrypi:~ $ sudo dpkg-reconfigure tzdata
Use of uninitialized value $value in substitution (s///) at 
/usr/share/perl5/Debconf/Format/822.pm line 65, <__ANONIO__> line 1.
Use of uninitialized value $item in hash element at 
/usr/share/perl5/Debconf/DbDriver/File.pm line 85, <__ANONIO__> chunk 1.
dpkg-query: package 'tzdata' is not installed and no information is 
available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
/usr/sbin/dpkg-reconfigure: tzdata is not installed


On Wednesday, March 28, 2018 at 3:14:08 PM UTC-7, gjr80 wrote:
>
> This sounds like a timezone issue to me. You wouldn't happen to be 7 hours 
> behind GMT would you? What timezone is running on your RPi and what 
> timezone are you putting in the console? Judging by the log something is 
> running on GMT (UTC).
>
> Gary
>

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

Re: [weewx-user] Re: WeeWx changing time on Davis Vantage Vue Console?

[Matt]

After the initial error with a large time difference the Davis console is 
"corrected" to the time of the Pi/weewx.  I still get time adjustments, but 
they are much smaller.  It's screwing up how data is viewed on the console 
with references to midnight: time of max/min T,  Daily rainfall etc.

On Thursday, March 22, 2018 at 5:58:01 AM UTC-7, Tom Keffer wrote:
>
> What happens after 60 seconds? Does the same error occur?
>
> -tk
>
> On Thu, Mar 22, 2018 at 5:35 AM, Matt <matt...@gmail.com > 
> wrote:
>
>> I set the correct time on my Davis then restarted my weewx
>>
>> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: StationRegistry: 
>> Registration not requested.
>> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: Wunderground-PWS: Data 
>> for station KCAMARIN10 will be posted
>> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: PWSweather: Posting not 
>> enabled.
>> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: CWOP: Data for station 
>> EW will be posted
>> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: WOW: Posting not enabled.
>> Mar 21 23:29:10 raspberrypi weewx[1746]: restx: AWEKAS: Posting not 
>> enabled.
>> Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Starting up weewx 
>> version 3.6.2
>> Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Clock error is -25228.35 
>> seconds (positive is fast)
>> Mar 21 23:29:10 raspberrypi weewx[1746]: vantage: Clock set to 2018-03-21 
>> 23:29:11 UTC (1521674951)
>> Mar 21 23:29:11 raspberrypi weewx[1746]: engine: Starting main packet 
>> loop.
>> Mar 21 23:29:15 raspberrypi weewx[1746]: vantage: LOOP try #1; error: 
>> Expected to read 99 chars; got 0 instead
>> Mar 21 23:29:20 raspberrypi weewx[1746]: vantage: LOOP try #2; error: 
>> Expected to read 99 chars; got 0 instead
>> Mar 21 23:29:30 raspberrypi weewx[1746]: vantage: LOOP try #3; error: 
>> Expected to read 99 chars; got 0 instead
>> Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP try #4; error: 
>> Expected to read 99 chars; got 0 instead
>> Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP max tries (4) 
>> exceeded.
>> Mar 21 23:29:38 raspberrypi weewx[1746]: engine: Caught WeeWxIOError: Max 
>> tries exceeded while getting LOOP data.
>> Mar 21 23:29:38 raspberrypi weewx[1746]:   Waiting 60 seconds 
>> then retrying...
>>
>>
>> On Tuesday, March 20, 2018 at 5:35:36 PM UTC-7, Matt wrote:
>>>
>>> Hi All,
>>> I did a search on this forum regarding time problems, but didn't see any 
>>> answers to my question.
>>>
>>> Is it possible that WeeWx is changing the time on my Davis console?  If 
>>> so, do I need to change one of the time sync settings or Vantage driver?  
>>> My weather data is making it to the web just fine, but my console time 
>>> keeps getting messed up.
>>>
>>> Thanks in advance
>>> Matt
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [weewx-user] WeeWx changing time on Davis Vantage Vue Console?

[Matt]

I set the correct time on my Davis and then started weewx.  Here is my log.

Mar 21 23:29:10 raspberrypi weewx[1746]: restx: StationRegistry: 
Registration not requested.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: Wunderground-PWS: Data for 
station KCAMARIN10 will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: PWSweather: Posting not 
enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: CWOP: Data for station 
EW will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: WOW: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: AWEKAS: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Starting up weewx version 
3.6.2
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Clock error is -25228.35 
seconds (positive is fast)
Mar 21 23:29:10 raspberrypi weewx[1746]: vantage: Clock set to 2018-03-21 
23:29:11 UTC (1521674951)
Mar 21 23:29:11 raspberrypi weewx[1746]: engine: Starting main packet loop.
Mar 21 23:29:15 raspberrypi weewx[1746]: vantage: LOOP try #1; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:20 raspberrypi weewx[1746]: vantage: LOOP try #2; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:30 raspberrypi weewx[1746]: vantage: LOOP try #3; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP try #4; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP max tries (4) 
exceeded.
Mar 21 23:29:38 raspberrypi weewx[1746]: engine: Caught WeeWxIOError: Max 
tries exceeded while getting LOOP data.
Mar 21 23:29:38 raspberrypi weewx[1746]:   Waiting 60 seconds then 
retrying...


On Tuesday, March 20, 2018 at 5:51:36 PM UTC-7, Tom Keffer wrote:
>
> I did. It syncs every 4 hours. Thanks, Gary!
>
> On Tue, Mar 20, 2018 at 5:48 PM, gjr80  
> wrote:
>
>> You didn't lose a zero there somewhere did you Tom? :)
>>
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [weewx-user] WeeWx changing time on Davis Vantage Vue Console?

[Matt]

I set the time correctly on my Davis and then I did a restart of weewx and 
here is my log

Mar 21 23:29:10 raspberrypi weewx[1746]: restx: StationRegistry: 
Registration not requested.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: Wunderground-PWS: Data for 
station KCAMARIN10 will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: PWSweather: Posting not 
enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: CWOP: Data for station 
EW will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: WOW: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: AWEKAS: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Starting up weewx version 
3.6.2
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Clock error is -25228.35 
seconds (positive is fast)
Mar 21 23:29:10 raspberrypi weewx[1746]: vantage: Clock set to 2018-03-21 
23:29:11 UTC (1521674951)
Mar 21 23:29:11 raspberrypi weewx[1746]: engine: Starting main packet loop.
Mar 21 23:29:15 raspberrypi weewx[1746]: vantage: LOOP try #1; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:20 raspberrypi weewx[1746]: vantage: LOOP try #2; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:30 raspberrypi weewx[1746]: vantage: LOOP try #3; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP try #4; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP max tries (4) 
exceeded.
Mar 21 23:29:38 raspberrypi weewx[1746]: engine: Caught WeeWxIOError: Max 
tries exceeded while getting LOOP data.
Mar 21 23:29:38 raspberrypi weewx[1746]:   Waiting 60 seconds then 
retrying...


On Tuesday, March 20, 2018 at 5:51:36 PM UTC-7, Tom Keffer wrote:
>
> I did. It syncs every 4 hours. Thanks, Gary!
>
> On Tue, Mar 20, 2018 at 5:48 PM, gjr80  
> wrote:
>
>> You didn't lose a zero there somewhere did you Tom? :)
>>
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [weewx-user] WeeWx changing time on Davis Vantage Vue Console?

[Matt]

Here is my log.  I set the time correctly on the Davis then started WeeWx 
and got the clock error.  Now I'm not posting to the web.   Not sure what's 
going on.


Mar 21 23:29:10 raspberrypi weewx[1746]: restx: StationRegistry: 
Registration not requested.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: Wunderground-PWS: Data for 
station KCAMARIN10 will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: PWSweather: Posting not 
enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: CWOP: Data for station 
EW will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: WOW: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: AWEKAS: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Starting up weewx version 
3.6.2
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Clock error is -25228.35 
seconds (positive is fast)
Mar 21 23:29:10 raspberrypi weewx[1746]: vantage: Clock set to 2018-03-21 
23:29:11 UTC (1521674951)
Mar 21 23:29:11 raspberrypi weewx[1746]: engine: Starting main packet loop.
Mar 21 23:29:15 raspberrypi weewx[1746]: vantage: LOOP try #1; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:20 raspberrypi weewx[1746]: vantage: LOOP try #2; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:30 raspberrypi weewx[1746]: vantage: LOOP try #3; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP try #4; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP max tries (4) 
exceeded.
Mar 21 23:29:38 raspberrypi weewx[1746]: engine: Caught WeeWxIOError: Max 
tries exceeded while getting LOOP data.
Mar 21 23:29:38 raspberrypi weewx[1746]:   Waiting 60 seconds then 
retrying...


On Tuesday, March 20, 2018 at 5:45:07 PM UTC-7, Tom Keffer wrote:
>
> WeeWX will automatically sync up the time on the console with the time on 
> the computer every 24 minutes. It logs this, so you can look in your system 
> log to see what it's doing. 
>
> It's hard to say what's going on without more details. What, specifically, 
> is the problem? A log excerpt would help.
>
> -tk
>
>
>
>
> On Tue, Mar 20, 2018 at 5:35 PM, Matt <matt...@gmail.com > 
> wrote:
>
>> Hi All,
>> I did a search on this forum regarding time problems, but didn't see any 
>> answers to my question.
>>
>> Is it possible that WeeWx is changing the time on my Davis console?  If 
>> so, do I need to change one of the time sync settings or Vantage driver?  
>> My weather data is making it to the web just fine, but my console time 
>> keeps getting messed up.
>>
>> Thanks in advance
>> Matt
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

[weewx-user] Re: WeeWx changing time on Davis Vantage Vue Console?

[Matt]

I set the correct time on my Davis then restarted my weewx

Mar 21 23:29:10 raspberrypi weewx[1746]: restx: StationRegistry: 
Registration not requested.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: Wunderground-PWS: Data for 
station KCAMARIN10 will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: PWSweather: Posting not 
enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: CWOP: Data for station 
EW will be posted
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: WOW: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: restx: AWEKAS: Posting not enabled.
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Starting up weewx version 
3.6.2
Mar 21 23:29:10 raspberrypi weewx[1746]: engine: Clock error is -25228.35 
seconds (positive is fast)
Mar 21 23:29:10 raspberrypi weewx[1746]: vantage: Clock set to 2018-03-21 
23:29:11 UTC (1521674951)
Mar 21 23:29:11 raspberrypi weewx[1746]: engine: Starting main packet loop.
Mar 21 23:29:15 raspberrypi weewx[1746]: vantage: LOOP try #1; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:20 raspberrypi weewx[1746]: vantage: LOOP try #2; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:30 raspberrypi weewx[1746]: vantage: LOOP try #3; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP try #4; error: 
Expected to read 99 chars; got 0 instead
Mar 21 23:29:38 raspberrypi weewx[1746]: vantage: LOOP max tries (4) 
exceeded.
Mar 21 23:29:38 raspberrypi weewx[1746]: engine: Caught WeeWxIOError: Max 
tries exceeded while getting LOOP data.
Mar 21 23:29:38 raspberrypi weewx[1746]:   Waiting 60 seconds then 
retrying...


On Tuesday, March 20, 2018 at 5:35:36 PM UTC-7, Matt wrote:
>
> Hi All,
> I did a search on this forum regarding time problems, but didn't see any 
> answers to my question.
>
> Is it possible that WeeWx is changing the time on my Davis console?  If 
> so, do I need to change one of the time sync settings or Vantage driver?  
> My weather data is making it to the web just fine, but my console time 
> keeps getting messed up.
>
> Thanks in advance
> Matt
>

-- 
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] WeeWx changing time on Davis Vantage Vue Console?

[Matt]

Hi All,
I did a search on this forum regarding time problems, but didn't see any 
answers to my question.

Is it possible that WeeWx is changing the time on my Davis console?  If so, 
do I need to change one of the time sync settings or Vantage driver?  My 
weather data is making it to the web just fine, but my console time keeps 
getting messed up.

Thanks in advance
Matt

-- 
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: Regenerate NOAA Tables

[Matt T]

ok - I answered my own question: add a sudo to  wee_database weewx.conf 
--rebuild-daily

On Thursday, July 13, 2017 at 1:13:04 PM UTC-7, Matt T wrote:
>
> I've recently cleaned my bad data 2016 and 2015 data from my database. 
>  I've followed the procedure to remove the bad data from the weewx 
> database, below. It appears the data is fixed (based on sql queries). 
>  However the NOAA tables still regenerate with the old data.  Is the a way 
> to force them to regenerate with the new database values? I've tried 
> deleting them and restarting weewx, but they are regenerated with the old 
> data. 
>
> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data
>
> Using: weewx v3.7.1 installed with deb package on a Raspberry Pi, with 
> Acurite Hardware
>

-- 
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] Regenerate NOAA Tables

[Matt T]

I've recently cleaned my bad data 2016 and 2015 data from my database. 
 I've followed the procedure to remove the bad data from the weewx 
database, below. It appears the data is fixed (based on sql queries). 
 However the NOAA tables still regenerate with the old data.  Is the a way 
to force them to regenerate with the new database values? I've tried 
deleting them and restarting weewx, but they are regenerated with the old 
data. 

https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data

Using: weewx v3.7.1 installed with deb package on a Raspberry Pi, with 
Acurite Hardware

-- 
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: Regenerate NOAA tables

[Matt T]

Using : weewx v3.7.1 on a Raspberry Pi, with Acurite Hardware

On Thursday, July 13, 2017 at 11:38:20 AM UTC-7, Matt T wrote:
>
> I've recently cleaned my bad data 2016 and 2015 data from my database. 
>  I've followed the procedure to remove the bad data from the weewx 
> database, below. It appears the data is fixed (based on sql queries). 
>  However the NOAA tables still regenerate with the old data.  Is the a way 
> to force them to regenerate with the new database values? I've tried 
> deleting them and restarting weewx, but they are regenerated with the old 
> data. 
>
> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data
>
> Thanks,
>
> Matt
>

-- 
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] Regenerate NOAA tables

[Matt T]

I've recently cleaned my bad data 2016 and 2015 data from my database. 
 I've followed the procedure to remove the bad data from the weewx 
database, below. It appears the data is fixed (based on sql queries). 
 However the NOAA tables still regenerate with the old data.  Is the a way 
to force them to regenerate with the new database values? I've tried 
deleting them and restarting weewx, but they are regenerated with the old 
data. 

https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data

Thanks,

Matt

-- 
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] Since midnight and This Week rain totals do not match graphs

[Matt Frost]

I just noticed that my Since Midnight and This week rainfall totals do not 
match what the graphs are showing. For example the hourly rainfall graph 
shows that I have had a total of 0.14 inches of rain since midnight. 
However the Since Midnight total shows 0.06 inches. The This Week \Total 
also shows 0.06 but should also read 0.14. The This Month Total is correct 
and shows 0.14. How do I correct this?

-- 
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: Formatting issue with weewx-forecast

[Matt Frost]

Thanks. I finally figured that out. I was putting the forecast into a 
container that was center aligned and that was messing things up. I ended 
up creating a new container for the forecast and that solved most of my 
problems. The only issue I have left is the sunrise/sunset information is 
showing in hh:mm:ss format instead of just hh:mm and that is causing the 
last couple of icons in the legend to be out of alignment.

On Saturday, January 7, 2017 at 8:45:57 PM UTC-6, mwall wrote:
>
> On Friday, January 6, 2017 at 6:23:27 PM UTC-5, Matt Frost wrote:
>>
>> I have a newly installed VP2 running weewx 3.6.2. I installed 
>> weewx-forecast 3.2.9 and have it mostly working. The issue I'm having is 
>> with the formatting of the single table. The single table sample page looks 
>> fine but when I add it to the standard skin index.html.tmpl the columns get 
>> all spread out. I'm guessing something is overriding the formatting but I 
>> can't figure it out.
>>
>> Any ideas?
>>
>
> hi matt!
>
> chances are the table width is being influenced by the container in which 
> it is included.
>
> i find that the best way to diagnose css issues is to mess around directly 
> using the developer tools built in to firefox or chrome.
>
> with dev tools you can identify html (dom) components and modify css 
> parameters directly, then put your changes into your .tmpl or .css file 
> once you have everything figured out.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Formatting issue with weewx-forecast

[Matt Frost]

On Friday, January 6, 2017 at 5:23:27 PM UTC-6, Matt Frost wrote:
>
> I have a newly installed VP2 running weewx 3.6.2. I installed 
> weewx-forecast 3.2.9 and have it mostly working. The issue I'm having is 
> with the formatting of the single table. The single table sample page looks 
> fine but when I add it to the standard skin index.html.tmpl the columns get 
> all spread out. I'm guessing something is overriding the formatting but I 
> can't figure it out.
>
> Any ideas?
>
> Thanks!
>

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

[weewx-user] Formatting issue with weewx-forecast

[Matt Frost]

I have a newly installed VP2 running weewx 3.6.2. I installed 
weewx-forecast 3.2.9 and have it mostly working. The issue I'm having is 
with the formatting of the single table. The single table sample page looks 
fine but when I add it to the standard skin index.html.tmpl the columns get 
all spread out. I'm guessing something is overriding the formatting but I 
can't figure it out.

Any ideas?

Thanks!

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

[weewx-user] Re: Upgrade to Mint 17.3 Rosa

[Matt VanGiesen]

2032 in mode 4

But, when verifying the weewx.conf, I found typo in the model number...I 
believe when I re-installed after the upgrade weewx used an archived .conf 
file that was incorrect. I'm vetting it now for more errors..
Thanks for the great support and awesome program!

On Thursday, December 8, 2016 at 1:16:02 PM UTC-8, mwall wrote:
>
> On Thursday, December 8, 2016 at 4:10:34 PM UTC-5, Matt VanGiesen wrote:
>>
>> I upgraded to 17.3 and lost ability to collect pool...was working OK 
>> until then, though slow to sync with pool sometimes. This has been cycling 
>> for 5+ hours now after rebooting and resetting weather station. Keep it 
>> simple, cause I'm stupid...or new to Linux (but loving and learning)!
>>
>
> what model of acurite console is it?
>
> is the console in usb mode 4?
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Upgrade to Mint 17.3 Rosa

[Matt VanGiesen]

I upgraded to 17.3 and lost ability to collect pool...was working OK until 
then, though slow to sync with pool sometimes. This has been cycling for 5+ 
hours now after rebooting and resetting weather station. Keep it simple, 
cause I'm stupid...or new to Linux (but loving and learning)!

Log file:
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: retrying...
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Using configuration 
file /etc/weewx/weewx.conf
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Initializing engine
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading station 
type AcuRite (weewx.drivers.acurite)
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: acurite: driver version is 
0.24
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: acurite: R2 will be decoded 
using sensor constants
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.engine.StdTimeSynch
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.engine.StdTimeSynch
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.engine.StdConvert
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: StdConvert target 
unit is 0x1
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.engine.StdConvert
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.engine.StdCalibrate
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.engine.StdCalibrate
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.engine.StdQC
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.engine.StdQC
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: 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
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.engine.StdArchive
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Archive will use 
data binding wx_binding
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Record generation 
will be attempted in 'hardware'
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Use LOOP data in 
hi/low calculations: 1
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: manager: Starting backfill 
of daily summaries
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: manager: Daily summaries up 
to date
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.engine.StdArchive
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.restx.StdStationRegistry
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: restx: StationRegistry: 
Registration not requested.
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.restx.StdStationRegistry
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.restx.StdWunderground
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: restx: Wunderground-PWS: 
Data for station KWAOAKHA61 will be posted
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.restx.StdWunderground
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.restx.StdPWSweather
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: restx: PWSweather: Posting 
not enabled.
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.restx.StdPWSweather
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.restx.StdCWOP
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: restx: CWOP: Posting not 
enabled.
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.restx.StdCWOP
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Loading service 
weewx.restx.StdWOW
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: restx: WOW: Posting not 
enabled.
Dec  8 12:56:30 matt-Inspiron-1750 weewx[1937]: engine: Finished loading 
service weewx.restx.StdWOW

[weewx-user] Re: Daylight Saving and Primary Key error

[Matt]

missed a piece of the syslog

Nov 10 19:49:53 weatherstation weewx[2795]: restx: Wunderground-PWS: 
Published record 2016-11-06 01:05:00 PDT (1478419500)
Nov 10 19:50:00 weatherstation weewx[2795]: restx: CWOP: record 2016-11-06 
01:10:00 PDT (1478419800) is stale (416400 > 1800).
Nov 10 19:50:00 weatherstation weewx[2795]: restx: Wunderground-PWS: 
Published record 2016-11-06 01:10:00 PDT (1478419800)
Nov 10 19:50:20 weatherstation weewx[2795]: vantage: Unable to pass CRC16 
check while getting data
Nov 10 19:50:20 weatherstation weewx[2795]: restx: Shut down CWOP thread.
Nov 10 19:50:20 weatherstation weewx[2795]: restx: Shut down 
Wunderground-PWS thread.
Nov 10 19:50:20 weatherstation weewx[2795]: vantage: successfully woke up 
console
Nov 10 19:50:20 weatherstation weewx[2795]: engine: Caught WeeWxIOError: 
Unable to pass CRC16 check while getting data
Nov 10 19:50:20 weatherstation weewx[2795]:   Waiting 60 seconds 
then retrying...
Nov 10 19:51:21 weatherstation weewx[2795]: engine: retrying...

-- 
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] Daylight Saving and Primary Key error

[Matt]

Hi All,
looks like DST switch blew up my weewx.  I have a Davis Vue.  From 
searching this forum it's a known error. In fact I had it happen last year, 
but can't remember the fix I made.  In short, I've tried several solutions 
listed here on the forum (reboots, stop/start, dump, backfill daily), but 
none of them are working.  Weewx won't go past this error.  I haven't 
reported since Nov 6th.  

Thoughts?  Thanks in advance.


Syslog below

Nov 10 19:41:52 weatherstation weewx[2795]: engine: Finished loading 
service weewx.engine.StdQC
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Loading service 
weewx.engine.StdArchive
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Archive will use data 
binding wx_binding
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Record generation will 
be attempted in 'hardware'
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Using archive interval 
of 300 seconds
Nov 10 19:41:52 weatherstation weewx[2795]: engine: Use LOOP data in hi/low 
calculations: 1
Nov 10 19:41:53 weatherstation weewx[2795]: engine: Using binding 
'wx_binding' to database 'archive/weewx.sdb'
Nov 10 19:41:53 weatherstation weewx[2795]: engine: Starting backfill of 
daily summaries
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Processed 14 records to 
backfill 1 day summaries in 8.30 seconds
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.engine.StdArchive
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.restx.StdStationRegistry
Nov 10 19:42:01 weatherstation weewx[2795]: restx: StationRegistry: Data 
will not be posted. Missing option 'station_url'
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.restx.StdStationRegistry
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.restx.StdWunderground
Nov 10 19:42:01 weatherstation weewx[2795]: restx: Wunderground-PWS: Data 
for station ###  will be posted
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.restx.StdWunderground
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.restx.StdPWSweather
Nov 10 19:42:01 weatherstation weewx[2795]: restx: PWSWeather: Data will 
not be posted: Missing option 'station'
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.restx.StdPWSweather
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.restx.StdCWOP
Nov 10 19:42:01 weatherstation weewx[2795]: restx: CWOP: Data for station 
###  will be posted
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.restx.StdCWOP
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.restx.StdWOW
Nov 10 19:42:01 weatherstation weewx[2795]: restx: WOW: Data will not be 
posted: Missing option 'station'
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.restx.StdWOW
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.restx.StdAWEKAS
Nov 10 19:42:01 weatherstation weewx[2795]: restx: AWEKAS: Data will not be 
posted: Missing option 'username'
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.restx.StdAWEKAS
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.engine.StdPrint
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.engine.StdPrint
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Loading service 
weewx.engine.StdReport
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Finished loading 
service weewx.engine.StdReport
Nov 10 19:42:01 weatherstation weewx[2795]: engine: Starting up weewx 
version 3.0.1
Nov 10 19:42:02 weatherstation weewx[2795]: vantage: successfully woke up 
console
Nov 10 19:42:02 weatherstation weewx[2795]: engine: Clock error is -1.38 
seconds (positive is fast)
Nov 10 19:42:02 weatherstation weewx[2795]: vantage: Getting archive 
packets since 2016-11-06 01:55:00 PST (1478426100)
Nov 10 19:42:02 weatherstation weewx[2795]: vantage: successfully woke up 
console
Nov 10 19:42:03 weatherstation weewx[2795]: vantage: Retrieving 274 
page(s); starting index= 2
Nov 10 19:42:03 weatherstation weewx[2795]: manager: unable to add record 
2016-11-06 01:00:00 PST (1478422800) to database 'archive/weewx.sdb': 
PRIMARY KEY must be unique
Nov 10 19:42:04 weatherstation weewx[2795]: manager: added record 
2016-11-06 01:00:00 PST (1478422800) to daily summary in 'archive/weewx.sdb'
Nov 10 19:42:10 weatherstation weewx[2795]: restx: CWOP: record 2016-11-06 
01:00:00 PST (1478422800) is stale (412930 > 1800).
Nov 10 19:42:10 weatherstation weewx[2795]: manager: unable to add record 
2016-11-06 01:05:00 PDT