I just got the new 6313 console, and it does respond on port 22222 and 
seems to return the same data that my Envoy did. Additionally, you can go 
to http://<console ip>/loop.json to get the current values. 

Philip

On Wednesday, August 9, 2023 at 12:21:56 PM UTC-4 michael.k...@gmx.at wrote:

>
> Certainly an interesting spin-off discussion: developing a platform to 
> ensure our data will remain our data. A first approach could be designing a 
> console. Many stations out there, modular or not, use wireless sensors that 
> only transmit their readings unencrypted and simplex. It should be possible 
> to design a console that receives the popular sensors out there and 
> provides data on the (W)LAN they are connected to. An internal storage with 
> a REST interface for data access and a GUI for maintaining settings and 
> there you go. The idea isn't new, doesn't sound too complicated but would 
> be a long way to go, if the goal is to provide something that deserves the 
> label "product". Anyway, I'd be on board. :D 
> gary....@gmail.com schrieb am Mittwoch, 9. August 2023 um 15:36:52 UTC+2:
>
>> I have had good luck with the Davis WLL, though it is not my data source 
>> for my primary weewx instance. I use it to feed my in home tablet displays.
>> I have run a SDR setup in the past and while it is NOT the easiest to 
>> configure, it did work well once all the pieces were in place. I did need 
>> to get a separate device (BMP380) to provide the barometer though. If you 
>> run on a Pi, no problem doing that. I run off a PC with Proxmox, so I had 
>> to add the Pi to have barometer.
>>
>> If I were the OP, I'd get the additional hardware to do SDR.
>> Ecowitt may be cheaper, but it certainly isn't a Davis.
>>
>> On Wednesday, August 9, 2023 at 1:14:43 AM UTC-4 Graham Eddy wrote:
>>
>>> swap vantage to ecowitt and you lose the data logger (stored in local 
>>> hardware) → one day you lose critical data
>>>
>>> ecowitt already have a ‘regularly call home' to china built in that adds 
>>> no value to customer, only a dependency on ecowitt company. if ecowitt turn 
>>> off their ‘ok’ response, everyone’s stations will reboot continually. i 
>>> expect them to introduce paid-only access - but they are clever not to 
>>> restrict the data but to disable the devices. (you might want to be wary of 
>>> accepting their firmware upgrades in future, for existing devices.)
>>>
>>> it is like the printer market - they flog you a printer really cheap but 
>>> 'charge like a wounded bull' for the ink. ditto future weather stations: 
>>> cheap hardware, but lock you into constant revenue stream for service. as 
>>> the weather station vendors try to lock down into paid-only services, i 
>>> plan to migrate to open lorawan devices (because i want COTS or public 
>>> domain products rather than build my own - more effective use of my time)
>>>
>>> but i do like my current setup, with vantage providing core weather data 
>>> and ecowitt lots of other inexpensive nearby sensors augmenting it, plus 
>>> lorawan for some more distant and more complex sensors than ecowitt 
>>> provides. 
>>> *⊣GE⊢*
>>>
>>> On 9 Aug 2023, at 1:35 pm, Bob Rose <rose0...@gmail.com> wrote:
>>>
>>> I have been using the Ecowitt on my home weather station going on three 
>>> years now. I can not say anything bad about it. The Davis 6313 I am dealing 
>>> with is for an organization I belong to. It replaced the failing VP2. They 
>>> are really bummed that they spent so much money for something that does not 
>>> have accessible archives. I have even thought about sneaking an Ecowitt 
>>> system out there and telling them “I got it working”. 
>>>
>>> On Tuesday, August 8, 2023 at 8:05:51 PM UTC-7 Colin Larsen wrote:
>>>
>>>> Strangely enough I just replaced all my DIY hardware (weatherduino) 
>>>> with an Ecowitt setup and it's excellent for the money
>>>>
>>>> Colin
>>>>
>>>> On Wed, 9 Aug 2023 at 14:35, vince <vince...@gmail.com> wrote:
>>>>
>>>>> rtl_davis driver can help somewhat at a higher complexity level FWIW
>>>>>
>>>>>
>>>>> -- 
>>>>> 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 weewx-user+...@googlegroups.com.
>>>>>
>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/72f7c54d-ed55-4631-8eeb-0339cbf93588n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/72f7c54d-ed55-4631-8eeb-0339cbf93588n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
>>> -- 
>>> 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 weewx-user+...@googlegroups.com.
>>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/3bbbaaf3-61b5-4574-8078-91992aca8ad4n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/3bbbaaf3-61b5-4574-8078-91992aca8ad4n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
>>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c45c0847-0831-4616-9159-efaaf8dffe31n%40googlegroups.com.

Reply via email to