Your router will have a list of devices on the network. Take a look.
On Fri, Jan 24, 2020, 8:39 PM Bill Butler wrote:
> Q: “what is the ip address of the Weatherlink IP device ?”
> A: I haven’t got the faintest idea. I’ve been following the instructions
> at http://www.weewx.com/docs/debian.htm
Q: “what is the ip address of the Weatherlink IP device ?”
A: I haven’t got the faintest idea. I’ve been following the instructions at
http://www.weewx.com/docs/debian.htm I just copied and pasted the
instructions to the terminal.
As for what is in the config file, I’ll try another install tomor
On Friday, January 24, 2020 at 5:34:14 PM UTC-6, Thomas Keffer wrote:
>
> Could you all do a pull and give it another try? The flow path between
> byte strings and unicode are more controlled now, making the results less
> prone to decode errors.
>
> At least, that's the theory!
>
> -tk
>
My w
Slight edit - of course it is 'type = ' not 'connection_type = '. Sorry
for the typo in the reply above.
--
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-us
On Friday, January 24, 2020 at 6:47:03 PM UTC-8, Bill Butler wrote:
>
> I’ve tried the following experiments.
>
> The install process seems to go thru OK up to the last prompt which is the
> IPv4 address.
>
> I’ve tried running the whole process using:
> 1) The default 192.168.0.10 (Which doesn
On Friday, January 24, 2020 at 1:44:03 PM UTC-8, Bill Butler wrote:
>
> Tried a few experiments - nothing worked. The Vantage Vue still is viable
> on my old Windows 7 computer, so I'll continue to run the reports there.
>
> Purged WeeWX off the Linux computer.
>
>
Whatever makes you happy.
That
Fine for me under both python2 and 3.
Gary
On Saturday, 25 January 2020 09:34:14 UTC+10, Thomas Keffer wrote:
>
> Could you all do a pull and give it another try? The flow path between
> byte strings and unicode are more controlled now, making the results less
> prone to decode errors.
>
> At l
Could you all do a pull and give it another try? The flow path between byte
strings and unicode are more controlled now, making the results less prone
to decode errors.
At least, that's the theory!
-tk
On Thu, Jan 23, 2020 at 8:48 PM P Simmons wrote:
>
> Updated to db1b41e, problem solved.
>
>
Tried a few experiments - nothing worked. The Vantage Vue still is viable
on my old Windows 7 computer, so I'll continue to run the reports there.
Purged WeeWX off the Linux computer.
On Thursday, January 23, 2020 at 5:47:51 PM UTC-7, Bill Butler wrote:
>
> I recently tried to install WeeWX on
http://74.208.29.36/index.php
--
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
ht
I thought I would follow up on my question below in the event any newbies
like me search for this in the future.
So the answer to my question is, yes I need to create my own driver. There
are two guides I am going to use.
http://www.weewx.com/docs/customizing.htm#porting
and..an existi
Good to know! I ordered the GW1000 yesterday - sounds like that's the best
route.
And yes, using interceptor does clearly introduce too many moving parts,
creating a fragile system. Guess I'll just have to be ok with not knowing
what exactly was causing my issue. In any case, silver lining is t
My experience with getting the data using Interceptor is that it's a pain.
I tried the DNS spoofing, setting up an AP on the weewx machine and
sniffing the data (worked best), iptables in my router. None were really
good as there were too many moving parts. I then used the SDR method and it
w
13 matches
Mail list logo