Vince - thanks! I'll take that approach on the imports!
Glenn:
I had hand-transcribed the command entry - i'd entered the correct command
string:
sudo /home/weewx/bin/wee_extension --install
/home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee
/tmp/wee-extension-out.txt
This is the results:
======================
Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
Traceback (most recent call last):
File "/home/weewx/bin/wee_extension", line 88, in <module>
main()
File "/home/weewx/bin/wee_extension", line 80, in main
ext.install_extension(options.install)
File "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension
raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension
'/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.
========================
No info about where to put the tar.gz file. Again, i'd used the "setup.py"
script to install weewx, so all the relevant folders are off "/home".
/David
On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:
> /home/david/Downloads/weewx-belchertown.1.2.tar.gz
>
> Check the filename
>
> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet)
> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at
>
> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>
> note: there are 2 dashes in the correct name.
>
> On 04/03/2021, David Prellwitz <[email protected]> wrote:
> > error trying to install belchertown. my weewx install was using
> setup.py. I
> >
> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads
> folder.
> > I ran the sudo wee-extension command and get "File
> > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension
> > weecfg.extension.InstallError: Extension
> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found.
> > can't find what i did wrong. Should i extract the tar.gz file first? move
> > it to another folder to start install?
> > /David
> >
> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote:
> >
> >> Lightning is difficult because there's no units for 'energy' in the UDP
> >> API. I might also add perhaps don't bother, as lightning is bogus
> anyway.
> >>
> >> It's what your sensor reported, but it is not remotely close to the
> >> crowd-sourced info their web or mobile interfaces provide, of which your
> >> sensor measurements are just a small part of what they aggregate and
> >> display.
> >>
> >> I think the simplest thing to do is map stuff and see what the driver
> puts
> >>
> >> in the db. It's possible the driver forces metric (or not metric) and
> >> does the conversions under the hood before weewx ever sees the assembled
> >> LOOP. Sometimes it's easier to just look at the code or do a little
> >> experimentation.
> >>
> >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 [email protected]
> >> wrote:
> >>
> >>> Vince, if i'm reading your post correctly (and carefully reading the
> >>> links you've provided), weewx.sdb stores all elements in a unit-base
> type
> >>>
> >>> as specified in the usUnits group (*"Each observation type, such
> >>> as outTemp or pressure, is associated with a unit group, such
> >>> as group_temperature or group_pressure. Each unit group is associated
> >>> with
> >>> a unit type such as degree_F or mbar.*" So, as my weewx.conf has an
> >>> entry in [StdConvert] section "target_unit = us " i can assume that all
> >>> weewx.sdb entries conform to the US Group column. further assumption is
> >>> that if WeatherFlow Tempest device provides data in m/b and i spec it
> as
> >>>
> >>> m/b for the LOOP process, it will be converted to inHg as part of the
> UDP
> >>>
> >>> LOOP process. If i import data from WF using the API's i just need to
> >>> spec
> >>> the API page's listing of unit WF will be providing for those fields
> and
> >>>
> >>> wee_import will correct those to the weewx.sdb needed units? If i wish
> >>> to
> >>> have lightning information, i'll need to map to those "signal7/8"
> and/or
> >>>
> >>> "xxx/yyy" fields, and i'll have to figure out what units they use?
> >>> thanks!
> >>>
> >>>
> >>> On Wednesday, March 3, 2021 at 11:34:05 AM UTC-8 David Prellwitz wrote:
> >>>
> >>>> Vince - yea, my way of apologizing for running down some rabbit hole i
> >>>> didn't need to. Thanks for the guidance, I'll map it out and see if it
> >>>> works. I'll try to get a decent mapping setup and forward to you for
> >>>> comment.
> >>>> My next attempt is to install and use Belchertown skins.
> >>>>
> >>>> On Wednesday, March 3, 2021 at 8:31:12 AM UTC-8 vince wrote:
> >>>>
> >>>>> That's a lot of words, but I still think you're possibly
> overthinking.
> >>>>>
> >>>>> Anyway, I'm pretty lost re: what you're actually trying to do.
> >>>>>
> >>>>> - There is a sample mapping of Tempest UDP elements to Weewx
> >>>>> database elements both in the driver code and in the docs on the
> >>>>> github
> >>>>> site for the driver.
> >>>>> - There are a couple forks of the original driver, but they all
> >>>>> have an example looking like (this map)
> >>>>>
> >>>>> <
> https://github.com/jjvdgeer/weatherflow-udp/blob/master/sample_Tempest_sensor_map
> >
> >>>>>
> >>>>> So using outside temperature as an example, you'll see a mapping that
> >>>>> looks like:
> >>>>>
> >>>>> - outTemp = air_temperature.ST-00000025.obs_st
> >>>>>
> >>>>> Which means:
> >>>>>
> >>>>> - map the driver's air_temperature element
> >>>>> - for sensor ST-00000025
> >>>>> - from the obs_st observation type emitted by the WF gear
> >>>>> - to weewx's outTemp database element
> >>>>>
> >>>>> The driver's terminology is in the code around line 211 of the driver
> >>>>> (here)
> >>>>> <
> https://github.com/jjvdgeer/weatherflow-udp/blob/master/bin/user/weatherflowudp.py
> >.
> >>>>>
> >>>>> So why is it different ? Because the driver references the WF UDP
> >>>>> API
> >>>>> (here) <https://weatherflow.github.io/Tempest/api/udp/v143/> which
> >>>>> uses the description 'air temperature' in the obs_st (tempest
> >>>>> observation)
> >>>>> type. The driver is written to reconcile versus the vendor's public
> >>>>> API.
> >>>>> The mapping reconciles that to weewx-speak.
> >>>>>
> >>>>> So what units does outTemp use and how do you figure THAT out ?
> >>>>>
> >>>>> - it's set in your weewx.conf or skin.conf for the item
> >>>>> group_temperature
> >>>>> - which is documented in the Customization Guide
> >>>>> <http://weewx.com/docs/customizing.htm#units> appendix detailing
> >>>>> the units weewx uses for each thing in the database
> >>>>>
> >>>>> So if you want to see the mapping of any database element to units,
> >>>>> just reference the Customization Guide appendix.
> >>>>>
> >>>>> This stuff really is documented in excruciating detail, but it is a
> bit
> >>>>>
> >>>>> of a trail of things to follow to put all the pieces together
> >>>>> notionally.
> >>>>>
> >>>>>
> >
> > --
> > 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 [email protected].
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/weewx-user/98dd7083-29da-4cb3-9679-b5c391df6c65n%40googlegroups.com
> .
> >
>
>
> --
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/d0b259f8-7492-4bbb-aa58-8547f0af0158n%40googlegroups.com.
