[weewx-development] Re: Advice on a new driver and how to make it available

[DWest]

Hey Mike,

I was wondering if you every got this working with you WS-2902. I followed 
this guide: http://landoflinux.com/linux_raspberry_pi_weather_station.html

Seems to use the driver Susan developed. I get all the way down to 
"Checking connectivity to your weather station" but then it fails with 
"Timed out too many times"

Ultimately, I am hoping to use the realtime.txt file that the Cumulus 
Realtime Plugin generates. I have no wishes to post my data anywhere. The 
information in this .txt file will be used to make decisions in regards to 
my RPi's GPIO.

I apologize in advanced, I realize I most likely posted this in the wrong 
thread. I wasn't aware of all the others in the weewx group. So please let 
me know if I should post this elsewhere.

[weewx-development] Re: Advice on a new driver and how to make it available

[DWest]

Hey Mike,

I was wondering if you ever got your WS-2902 working with weewx? I followed 
this guide http://landoflinux.com/linux_raspberry_pi_weather_station.html

Seems to be the same driver Susan developed. I get all the way down to 
"Checking connectivity to your weather station" but it always fails with 
"Too many failed attempts"


Thanks

DWest

On Monday, September 11, 2017 at 7:37:24 PM UTC-5, Mike Frison wrote:
>
> I've attached a zenmap log of a port scan.  The only port it found open 
> was 45000 with service asmp. The suspected OS (99% accuracy) is NodeMCU 
> firmware. For what it's worth, the hostname is ESP_0BD7E0.
>
> I attempted to telnet to the open port
> telnet 192.168.1.16 45000
> Trying 192.168.1.16...
> Connected to 192.168.1.16.
> Escape character is '^]'.
>
>
> My networking skills are negligible so I have no idea what to do next.
>
> Mike
>
>
> On Monday, September 11, 2017 at 1:08:57 PM UTC-7, mwall wrote:
>>
>> On Monday, September 11, 2017 at 3:50:30 PM UTC-4, Mike Frison wrote:
>>>
>>> Ed at Ambient says the ws-2902 doesn't have a communications protocol. 
>>> ;^)
>>>
>>>
>> you could hit it with a port scanner to see if it is listening for any 
>> network requests
>>
>> then hit it with telnet on any open ports to see it whether it responds
>>
>