wlan0 shows UP, so that's odd. Have you tried restarting the Pi? Also, this has run far from the thread topic. Open a new thread for further setup questions.
On Wednesday, January 2, 2019 at 8:01:04 AM UTC-5, Scott Grayban wrote: > > On the PI running weewx > # ifconfig > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.0.4 netmask 255.255.255.0 broadcast 192.168.0.255 > inet6 2001:470:1f00:3480::2 prefixlen 64 scopeid 0x0<global> > inet6 fe80::ba27:ebff:febb:1a44 prefixlen 64 scopeid 0x20<link> > ether b8:27:eb:bb:1a:44 txqueuelen 1000 (Ethernet) > RX packets 66790 bytes 29042616 (27.6 MiB) > RX errors 0 dropped 1378 overruns 0 frame 0 > TX packets 21027 bytes 4829399 (4.6 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 1000 (Local Loopback) > RX packets 8060 bytes 475705 (464.5 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 8060 bytes 475705 (464.5 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > On the PI running RaspAP > > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.0.36 netmask 255.255.255.0 broadcast 192.168.0.255 > inet6 fe80::abf0:3ba2:3065:d02e prefixlen 64 scopeid 0x20<link> > inet6 2602:3f:e686:a600:bb58:3afe:8b5f:1567 prefixlen 64 scopeid > 0x0<global> > inet6 fd00::f2f1:5e67:5f6a:1cee prefixlen 64 scopeid 0x0<global> > inet6 2602:3f:e686:a600:f18d:81e3:8118:214c prefixlen 64 scopeid > 0x0<global> > inet6 fd00::fff:43f6:90d4:c8d8 prefixlen 64 scopeid 0x0<global> > ether b8:27:eb:21:f1:98 txqueuelen 1000 (Ethernet) > RX packets 39861 bytes 20878633 (19.9 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 3634 bytes 2689800 (2.5 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 1000 (Local Loopback) > RX packets 93 bytes 179941 (175.7 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 93 bytes 179941 (175.7 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 10.3.141.1 netmask 255.255.255.0 broadcast 10.3.141.255 > inet6 fe80::e7af:2847:23b3:c7c8 prefixlen 64 scopeid 0x20<link> > ether 32:9c:a0:48:75:29 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 60 bytes 8395 (8.1 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > On Wednesday, January 2, 2019 at 4:58:29 AM UTC-8, G Hammer wrote: >> >> ifconfig command >> See what you have both for a name of the interface and the IP assigned to >> it. >> >> On Wed, Jan 2, 2019 at 7:55 AM Scott Grayban <[email protected]> wrote: >> >>> I got it....... Now I got a new problem >>> >>> Jan 2 04:52:57 raspberrypi weewx[9586]: interceptor: MainThread: driver >>> version is 0.45 >>> Jan 2 04:52:57 raspberrypi weewx[9586]: interceptor: MainThread: device >>> type: observer >>> Jan 2 04:52:57 raspberrypi weewx[9586]: interceptor: MainThread: sensor >>> map: None >>> Jan 2 04:52:57 raspberrypi weewx[9586]: interceptor: MainThread: mode >>> is sniff >>> Jan 2 04:52:57 raspberrypi weewx[9586]: interceptor: MainThread: sniff >>> iface=wlan0 promiscuous=0 >>> Jan 2 04:52:57 raspberrypi weewx[9586]: interceptor: MainThread: sniff >>> filter 'src 10.3.141.62 and dst port 80' >>> Jan 2 04:52:57 raspberrypi weewx[9586]: import of driver failed: wlan0: >>> That device is not up (<type 'exceptions.Exception'>) >>> Jan 2 04:52:57 raspberrypi weewx[9586]: engine: Unable to load driver: >>> wlan0: That device is not up >>> >>> I guess the pi that is running weewx can't connect to 10.3.141.62 - the >>> RaspAP is running on a different PI >>> On Wednesday, January 2, 2019 at 4:49:43 AM UTC-8, G Hammer wrote: >>>> >>>> Touch Wind and Alarm and keep touching them until it beeps and flashes >>>> M-B >>>> >>>> On Wed, Jan 2, 2019 at 7:47 AM Scott Grayban <[email protected]> wrote: >>>> >>>>> I did that but M-B never showed. All I see is M-A and there is nothing >>>>> I can find to get that to M-B >>>>> >>>>> On Wednesday, January 2, 2019 at 4:25:53 AM UTC-8, WILWetter25 wrote: >>>>>> >>>>>> 1. Connect to the New Network with your Mobile Phone. >>>>>> 2. Press Wind and Alarm -> the WiFi Symbol should start flash. >>>>>> 3. Open Ambient Tool >>>>>> -> Add Device -> Next -> Next -> Add Router -> Press Add -> and >>>>>> thats it :) >>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "weewx-user" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/weewx-user/6ihvgtwnEGo/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "weewx-user" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/weewx-user/6ihvgtwnEGo/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
