Nice work Gary! Matthew Wall has informed me that Gary is considered core
WeeWX developer. I've sent him official GW1000 API documentation to be able
to further refine the driver. This will allow the driver to be ready for
yet unreleased future sensors.
On Thursday, July 23, 2020 at 9:22:23
should know the IP address,
> but the ip address of the GW1000 is local(192.168.xxx.xxx) and can't be
> seen from outside.
>
> Gert
>
> On Thursday, July 23, 2020 at 6:55:45 PM UTC+2, George Alfert wrote:
>>
>> Gert,
>> "How do I set up Ecowitt WsView to send
connection using the API protocol and I got live data
while my laptop was on the Internet using cellular hotspot.
On Thursday, July 23, 2020 at 2:09:26 PM UTC-4, George Alfert wrote:
>
> I have not tested to see if the GW1000 API will work across a WAN
> connection if you open ports. It m
Gert,
"How do I set up Ecowitt WsView to send information to the GW1000 driver?"
answer- you don't do anything in WS View. The beauty of the GW1000 API
driver is that all the magic happens in the API driver. The API driver just
needs to know the IP address of your GW1000 and that is it. The
:55:45 PM UTC-4, George Alfert wrote:
>
> Gert,
> "How do I set up Ecowitt WsView to send information to the GW1000 driver?"
> answer- you don't do anything in WS View. The beauty of the GW1000 API
> driver is that all the magic happens in the API driver. The API driver jus
...etc...do not have this API.
On Thursday, July 23, 2020 at 1:05:53 PM UTC-4, Greg Troxel wrote:
>
> George Alfert > writes:
>
> > I think what people should realize is that there are 3 methods to get
> data
> > from the GW1000.
> >
> > 1. Customized serve
For remote WeeWX server I recommend using the GW1000 Ecowitt upload
protocol "Customized" server upload feature and the WeeWX Interceptor
driver configured for ecowitt-client.
On Thursday, July 23, 2020 at 2:27:11 PM UTC-4, George Alfert wrote:
>
> I just tested a remote WAN
