I *think* I'm interested, too, but I'm not quite sure that I understand how it fits into the whole data stream path...hence, why I asked for the block diagram. Gotta SHOW me...and I ain't even from Missouri.

Think of it as wireless "Wire" that connects the console to the PC...

But, in MY case I have NO wire between my VUE console and my PC; the VUE plugs directly into my router/modem via its WL-IP cable.

My PC is obviously also plugged into the router/modem and I retrieve MY WL data from the DAVIS WeatherLink website via my PC, but with the WL-IP dongle (memory buffer) plugged into the VUE, there is NO WAY to directly connect anything else to the VUE (that I know of).

However, I definitely WOULD like my PC also connected to the VUE if it were possible, but at the moment I don't see that as doable.

About the ONLY way I can envision the WiFi helping me is if it were configured as a " T " where one leg connects to the VUE, the other to the WL-IP and the 3'rd is the WiFi. The SINGLE connection point into the VUE console is the problem.

....My PC is obviously also plugged into the router/modem and I retrieve MY WL data from the DAVIS WeatherLink website via my PC, but with the WL-IP dongle (memory buffer) plugged into the VUE, there is NO WAY to directly connect anything else to the VUE (that I know of)....

Well anything that is pluggable to your router/switch can effectively also communicate with the Vue/WLIP via the network, if it's designed as such. MeteoBridge is one such example

To me, it looks like all the WiFi device would do is eliminate the ethernet CAT cable between the WL-IP dongle and my router/modem; ie: just as SLOweather stated, a "wireless" wire connection. That'd be nice for cases where: (1) the VP2 Console is physically distant from the router/modem so much that the cable length is a problem or (2) the cable cannot be 'fished' through walls, etc. My two devices are literally within two feet of each other.

Our router/modem has built-in WiFi, as does our printer, but until DAVIS™ changes the software in either the VP2 or VUE consoles, I don't see it being useful (to me). I want/need two-way communication, not just one-way data dumping...because...currently everything goes thru that dongle in a single stream down to the router with NO upward communication that I'm aware of. The dongle is memory buffering and IP download only.

The reason it's not useful to you, is that you want to use your WeatherLinkIP.

The device (essentially) replaces a cable (serial or USB) connecting the console to the PC. It does that by allowing a wi-fi connection between the console and "the world" (i.e., the router). Then the PC connects to the console through the router (however it is connected to the router).

Using the WeatherLinkIP is great. It's another way to connect the console to "the world" (i.e., the router), so it performs the same function as the device that's being developed here - PLUS being able to send data to WeatherLink.com.

Network geek speak: A wireless bridge is an arrangement of devices (minimum two) that link two wired network segments, wirelessly. In bridged mode, the access point would not normally accept connections from other wireless devices.

1) this does not currently replace the "always on pc" scenario. It does not have the ability to upload directly to the internet.

2) it could replace the envoy in your situation. By that I mean that a console fitted with this link could remain connected to your PC whatever room it's in.

Dalecoy has the right idea, this may not be of use to anyone with a weatherlink IP. But in the future I may be able to modify the firmware to directly load to the internet, but that is a long way off yet.

OK, but as I noted above, until DAVIS™ does something to the VUE software, in my application, it would only be ONE way data flow...unless there was some 'intelligence' in that device...AND/OR...a "tee'd" input/output.

OK, but as I noted above, until DAVIS™ does something to the VUE software, in my application, it would only be ONE way data flow...

Which way? [That's a serious question, not a snipe - I do not quite understand what you are saying]

On both the VP2 Console and VUE console, the ONLY communication port is thru that WL connector, which *IS* bi-directional when a WL-USB dongle is used. So, MY interest is something that fits BEFORE/AFTER the WL-IP dongle connection into the console allowing access to and use of that bi-directional communication capability. Hence, my continued use of the word "Tee"...as in data-direction splitting.

Because of the "depth" of the memory-buffer, it should/could be possible to interrupt downstream (output to ISP) for "short" periods of time, to allow PC access back up into the console...for time and data parameter "adjustments" which NOW can only be done using the console buttons, but IS possible from a PC when a WL-USB dongle is in use. I have BOTH the WL-ISP and the WL-USB dongles in use now, although connected to two different receivers: VUE console @ WL-IP and Envoy8X @ WL-USB.

WLIP uploads to wl.com are indeed outbound only, as far as anyone knows.

But the IP logger is still obviously receptive to inbound commands, so as dalecoy says the IP interface is bidirectional. There are a number of folk who typically just turn off the wl.com uploads and use the IP logger as an alternative logger type but with an Ethernet interface, when it seems to deliver exactly the same data functionality as eg a USB logger.

I have received the circuit boards now and have built 3 WiFi loggers, using ESP-link as the serial-TCP/IP link. It all seems to work well, and I have had Weatherlink and Cumulus working using my envoy and Vantage pro consoles.

I am working on instructions to enable direct connection and connection over a home network.

Are there any "guinea pigs" that would like to give one of these a try and give me some feedback?