Alrighty!

I figured out how to create config stanzas and file stanzas BUT I have a 
few questions.  Note that I tried reading through the source for 
wee_extension to see if I could sort this out myself but I'm a bit baffled 
still.

   - Is there a way to replace a config value via the stanza without 
   writing custom code?  I.e. I see some fairly complex custom code to break 
   out and do custom things in some of the more complicated drivers/skins but 
   I'm trying to avoid that if I can.  I specifically want to replace the 
   station_type stanza to reflect the driver I just installed.
   - Is there a way to "place" the config_dict values.  By default they are 
   going to the end of the file which is OK but also forces the user to dig to 
   enter some of the values like the API token and device ID.  Alternately I 
   suppose these could be prompted for if I write some custom code?


Many thanks

Billy

On Friday, July 1, 2022 at 6:44:26 PM UTC-7 [email protected] wrote:

> Take a look at just about any skin or driver at this point.   If you want 
> to see a big one, look at the Belchertown skin which has some things in 
> there to embed a lot of comments into the right section in weewx.conf as it 
> installs, hopefully to make things a little easier to configure for folks 
> since that one is so configurable.
>
> On Friday, July 1, 2022 at 12:06:19 PM UTC-7 [email protected] wrote:
>
>> Got it,
>>
>> I'll check out the examples section and see what I can learn there.
>>
>> Billy
>>
>> On Friday, July 1, 2022 at 10:44:56 AM UTC-7 Tom Keffer wrote:
>>
>>> Unfortunately, there is no step-by-step guide on how to package an 
>>> extension. The best we have is a set of examples in the examples 
>>> subdirectory.
>>>
>>> A very worthy project (and learning experience) would be to write a wiki 
>>> article about how to do it. 
>>>
>>> -tk
>>>
>>> On Fri, Jul 1, 2022 at 9:54 AM Billy Jackson <[email protected]> wrote:
>>>
>>>> Howdy,
>>>>
>>>> I wrote a new driver to utilize my WeatherFlow Tempest's REST API 
>>>> rather then the local UDP API.  The use case for me is running weewx in 
>>>> the 
>>>> cloud and not having to utilize a local network broadcast etc....
>>>>
>>>> I have it running in a test instance at http://54.191.34.110/ and it 
>>>> mostly seems to be behaving right now so I'd like to package it up for 
>>>> wee_extension for installation if folks would like to give it a whirl but 
>>>> I 
>>>> can't seem to find a good reference on how to do this.  
>>>>
>>>> I'm wondering if anyone can point me in the right direction?
>>>>
>>>> One option is to copy the work that captain-coredump did on his 
>>>> weatherflowudp driver but I'd like to actually understand the 
>>>> options/syntax etc....
>>>>
>>>> Many thanks!
>>>>
>>>> Billy
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-development" 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-development/4ef7675c-c331-4ab1-9b13-bc2dc64d1a9an%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-development/4ef7675c-c331-4ab1-9b13-bc2dc64d1a9an%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" 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-development/641a5292-a1c2-4c0a-87e3-f06b13527ae3n%40googlegroups.com.

Reply via email to