Thank you, guys, for all your responses. Based on overall discussion we 
will buy the following and give it a shot:


   1. *WeatherLink Live (6100)*:
      - A viable alternative that offers *local API access* over your 
      network.
      - Supports live data retrieval via TCP/IP or UDP and can be easily 
      integrated with WeeWX.
   

On Wednesday, October 23, 2024 at 5:13:55 PM UTC-4 vince wrote:

> I think it is (4) - there is no Davis API to get any data from the new 
> tablet-style console directly.
>
> See https://weatherlink.github.io/v2-api/ for the gory details for how to 
> get the data from Davis servers, assuming you send your data there first. 
>  A quick read says you can get your current conditions for free but need to 
> subscribe (pay) for querying historical data.
>
> There are many (many!) complaints about this new console being crippled 
> relative to the old ones if you do some google and wxforum.net searches. 
>  It's also pretty crippled re: how long it will stay running off battery if 
> you have a power outage and seems to have many other misfeatures vs. the 
> old consoles.
>
> Re: options, Karen already answered that.   Longer discussion with more 
> details is at https://www.wxforum.net/index.php?topic=47548.0
>
> On Wednesday, October 23, 2024 at 10:20:19 AM UTC-7 Brent Musat wrote:
>
>> Jey,
>>
>> I do not have a WeatherLink Console, I have the smaller (no screen) 
>> device WeatherLink Live (WLL: 
>> https://www.davisinstruments.com/pages/weatherlink-live) so take 
>> everything below with a big grain of salt..  ymmv.
>> I'm not sure how the Console works but I assume it's using the same 
>> protocols and the WLL.   I gather data from the WLL on my network on port 
>> 22222 into weewx over UDP.   I'm using a Docker container to run weewx, but 
>> you running a VM with Ubuntu is basically the same thing. 
>>
>> One thing that sticks out to me is that your VM might be blocking the 
>> data.  Ensure that your VM running weewx does NOT have a firewall 
>> running..  Try disabling the Ubuntu Firewall first (or opening port 22222, 
>> or both) and see if it can connect to your WeatherLink Console (
>> 10.100.0.184:22222).  If port 22222 is blocked from the VM/weewx then 
>> the data can not get thru.
>>
>> Davis has API documentation here (
>> https://weatherlink.github.io/weatherlink-live-local-api/) and there are 
>> some python programs at the end of that post which should help you debug 
>> (if you are a Python person)..  running the "real-time UDP Broadcast 
>> Request" Python programs (edited to the IP address of your WeatherLink 
>> Console) from the Ubuntu VM should yield some streaming data.  If you still 
>> don't see data then one of these things is wrong:
>>   1) your VM is not on the same network (i.e. same IP subnet) as the 
>> WeatherLink Console, which is required for the UDP packets
>>   2) Port 22222 is still blocked, which is what the UDP packets stream 
>> over, so port 22222 needs to be open and accessible (debug using the API 
>> guide above using curl and the standalone python program which should be 
>> able to see the streaming data)
>>   3) the WeatherLink driver you are using in weewx is not configured 
>> properly or broken.  Note: there are different WeatherLink Live drivers and 
>> each of them seem to work but require different configurations as far as I 
>> can remember..  try a different one... I made a post about it a couple 
>> years ago:  https://groups.google.com/g/weewx-user/c/MN96wXLlYNo
>>   4) the WeatherLink Console works differently than the WeatherLink Live 
>> device (which I think probably is not the case, but you never know)
>>
>> that's a lot of info, but give those things a shot.   If I had a 
>> WeatherLink Console I could debug it on my home system to see if it works.  
>> I would be surprised if Console works much differently than the WLL 
>> device.  
>>
>> good luck,
>> brent...
>>
>> On Wednesday, October 23, 2024 at 7:00:06 AM UTC-5 Jey Riabchuk wrote:
>>
>>> Thanks for the answer, Vince!
>>> Any suggestion which hardware has been proven with easy-to-connect 
>>> programming API connection to it? We're still evaluating options...
>>>
>>> On Tuesday, October 22, 2024 at 5:52:14 PM UTC-4 vince wrote:
>>>
>>>> I'm not aware of any way to get data from the new tablet-looking Davis 
>>>> console. No programming API to it.   No hardware interfaces to it.
>>>>
>>>> You could get your 'outside' data wirelessly from the sensors with a 
>>>> RTL-SDR dongle and antenna and run the rtl-davis driver and weewx, but you 
>>>> would not have any inside t+h+p data because that comes from the 
>>>> (unreachable) console.
>>>>
>>>> On Tuesday, October 22, 2024 at 2:45:32 PM UTC-7 Jey Riabchuk wrote:
>>>>
>>>>> We're using this one:  6242 Davis Vantage Vue Wireless Weather 
>>>>> Station w/WeatherLink Console 
>>>>> <https://www.scientificsales.com/6242-Davis-Vantage-Vue-Wireless-Weather-Station-p/6242.htm>.
>>>>>  
>>>>> What would be the right way to connect and driver to install here?
>>>>>
>>>>> On Tuesday, October 22, 2024 at 12:27:45 PM UTC-4 Karen K wrote:
>>>>>
>>>>>> Option 1: weewx.drivers.vantage is for the adapters, that are put 
>>>>>> into the console only (6510SER, 6510USB, 6555IP).
>>>>>>
>>>>>> Option2: That should work together with WeatherLink Live 6100. The 
>>>>>> computer running WeeWX and the WeatherLink Live must be in the same 
>>>>>> network. That means, their IPs must start with the same numbers.
>>>>>>
>>>>>> The drivers referenced in the links are alternatives. You cannot use 
>>>>>> both of them.
>>>>>>
>>>>>> If you want people provide more detailed information, please refer Help! 
>>>>>> Posting to weewx user 
>>>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> and 
>>>>>> provide the information mentioned there.
>>>>>>
>>>>>

-- 
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/e34824f5-bb80-403f-9352-e001a688dc56n%40googlegroups.com.

Reply via email to