Well not being clairvoyant it is impossible in the absence of any 
information for anyone to guess what you actually installed, nor how, nor 
what you see... so it is equally impossible for anybody to help.

I would suggest you start with 
https://www.ministryoftesting.com/articles/11b82aee?s_id=15060040 
as a random ‘how to report an issue’ howto…

On Sunday, May 17, 2026 at 5:34:57 PM UTC-7 WeatheredScientist wrote:

> I feel like I am getting close but not quite seeing the big picture. I'm 
> able to see the transmitter, but am having trouble decoding its output, let 
> alone parsing it into a database file of some kind. Github is not my 
> strength, but I am willing to learn. What's the best way for me to pick up 
> what I need to know without being too much of a pain on other community 
> members?
>
> On Saturday, May 16, 2026 at 8:30:22 PM UTC-4 Vince Skahan wrote:
>
>> Moved a few months ago to https://github.com/weewx-contrib/weewx-rtldavis
>>
>> On Saturday, May 16, 2026 at 3:31:38 PM UTC-7 WeatheredScientist wrote:
>>
>>> The github link above is dead: does anyone know where to find this today?
>>>
>>> On Monday, February 10, 2025 at 4:29:18 PM UTC-5 Wayne wrote:
>>>
>>>> I think I have answered my own question in that weewx-rtldavis IS the 
>>>> correct weewx driver for me to use. Additionally, the following install 
>>>> script should make the task even easier as it describes how to use an 
>>>> earlier golang version which builds a working rtldavis binary (the actual 
>>>> SDR software for the Davis protocol). 
>>>>
>>>> https://github.com/vinceskahan/weewx-rtldavis 
>>>>
>>>> My sincere thanks to Vince for the above assist. Thanks for the 
>>>> bandwidth... 
>>>>
>>>> Wayne 
>>>>
>>>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/75c8159b-44a6-4626-9ceb-9dd9ad531ce3n%40googlegroups.com.

Reply via email to