BloomSky SKY2+STORM - No Pressure?

41 views
Skip to first unread message

Rick M0LEP

unread,
May 27, 2019, 6:06:29 AM5/27/19
to weewx...@googlegroups.com
I've recently switched my system over to getting data from a BloomSky
SKY2, and all seems to work fine except the pressure, which shows as N/A
(or null) in all the readings I can see in weewx. Looking atthe raw data
from the BloomSky, the pressure is being reported, so I'm guessing
someting in the driver is somehow missing it. Any ideas?

--
73, Rick, M0LEP

Rick M0LEP

unread,
May 27, 2019, 6:17:56 AM5/27/19
to weewx...@googlegroups.com
I think I found what was missing. The release of the BloomSky driver I
was using came from:

https://github.com/gjr80/weewx-bloomsky/releases/download/v0.1.0/bloomsky-0.1.0.tar.gz

However, the git repository contains a more up-to-date driver that
doesn't seem to have made it into the release yet. Getting the latest
copy of bloomsky.py from https://github.com/gjr80/weewx-bloomsky and
installing it manually has cured the problem.

gjr80

unread,
May 28, 2019, 11:01:39 PM5/28/19
to weewx-user
My apologies, committed the fix but never came back to issue the release. Fixed now in release 0.1.1.

Gary

Rick M0LEP

unread,
May 29, 2019, 5:56:12 PM5/29/19
to weewx...@googlegroups.com
On Wed 29 May gjr80 wrote:
> My apologies, committed the fix but never came back to issue the release.
> Fixed now in release 0.1.1
> <https://github.com/gjr80/weewx-bloomsky/releases>.

Thanks. :)

--
73, Rick, M0LEP

gjr80

unread,
May 29, 2019, 6:28:32 PM5/29/19
to weewx-user
Just one more thing, when testing the 0.1.1 release I noticed the default polling interval was 60 seconds as per the setup instructions, but the driver was coded with a 120 second default. I changed this to 60 seconds in the 0.1.1 release. Will not have any noticeable affect if you install 0.1.1 and you have poll_interval set under [Bloomsky]; however, if you install 0.1.1 and don't have poll_interval set there will be a change of polling interval from 120 seconds to 60 seconds. Easily fixed by explicitly setting poll_interval.

Gary

Reply all
Reply to author
Forward
0 new messages