|
Post by sawalker1234 on Mar 16, 2021 17:29:58 GMT -8
I have the sky camera, and the rest of weather rack (thermometer, wind, rain) ,but no air quality sensor.
|
|
|
Post by Jason on Mar 17, 2021 2:28:37 GMT -8
How close is the radio antenna/RPi to the weather rack? Anything blocking line of sight between them?
Jason
|
|
|
Post by SDL on Mar 17, 2021 8:55:32 GMT -8
I agree with Jason. This appears to be a range issue. BTW, don't get the WeatherRack2 too close to the SDR antenna either. You will saturate the receiver. 1-2 meters away should be good,
Range is always dependent on what is between you and the weatherrack2. More stuff? Less range.
BP
|
|
|
Post by sawalker1234 on Mar 17, 2021 9:36:23 GMT -8
I have moved the SDR antenna to 3 meters away with line of site behind a glass window...giving me the same behavior. It did work at this distance before the upgrade...
|
|
|
Post by SDL on Mar 20, 2021 10:52:53 GMT -8
OK. Would you run "sudo python3 testWirelessSensors.py" and print the results?
I think this has something to do with the rtl_433 install.
BP
|
|
|
Post by sawalker1234 on Mar 22, 2021 21:29:13 GMT -8
sure, here are the results: pi@SwitchDocLabs:~/SDL_Pi_SkyWeather2 $ sudo python3 testWirelessSensors.py Starting Wireless Read rtl_433 version 20.11-92-g7fe3bafa branch master at 202103142228 inputs file rtl_tcp RTL-SDR with TLS Use -h for usage help and see triq.org/ for documentation. Trying conf file at "rtl_433.conf"... Trying conf file at "/root/.config/rtl_433/rtl_433.conf"... Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"... Trying conf file at "/etc/rtl_433/rtl_433.conf"... quiet option (-q) is default and deprecated. See -v to increase verbosity Registered 5 out of 182 device decoding protocols [ 146-148 150-151 ] Found Rafael Micro R820T tuner Exact sample rate is: 250000.000414 Hz [R82XX] PLL not locked! Sample rate set to 250000 S/s. Tuner gain set to Auto. Tuned to 433.920MHz. Allocating 15 zero-copy buffers If I did something wrong installing the rtl-433 directory I can try to repeat the process and see if anything changes...
|
|
|
Post by SDL on Mar 24, 2021 9:12:59 GMT -8
So, you aren't reading anything. It just sits there? even if you leave it for 15 minutes?
I may be repeating myself, but do you have batteries in the WeatherRack2 and/or any Indoor T/H sensors?
The light underneath the WeatherRack2 will blink after you put new batteries in or hit reset.
Check that before you reinstall. This looks right.
Is your antenna plugged into the USB SDR Dongle all the way?
BP
|
|
|
Post by sawalker1234 on Mar 28, 2021 19:12:18 GMT -8
I went and bought another SD card with the original system image on it. I reconfigured the system as in the instructions and have it working with the
sudo python3 testWirelessSensors.py
command.
Also the SkyWeather2.py apears to work also. My only problem now is that I have been trying to set up the Blynk app (that is why I tried to upgrade to the latest version). I have bought the Blynk app and generated an auth key which I emailed and pasted into the SkyWeatherConfig server. However, the Blynk portion of the weatherstation remains offline...Not sure how to fix this...
With debug on I get this when trying to access the blynk server:
./SkyWeather2.JSON File exists
########################################################## SkyWeather2 Weather Station Version 024 - SwitchDoc Labs
Program Started at:2021-03-28 19:58:14 ##########################################################
b'' ---------------------- BMP280: Present SkyCam: Present OLED: Not Present SunAirPlus/SunControl: Not Present SolarMAX: Not Present DustSensor: Not Present
UseBlynk: Enabled UseWSLIGHTNING: Disabled UseWSAQI: Disabled UseWSSKYCAM: Disabled UseMySQL: Enabled UseMQTT: Disabled Check WLAN: Present WeatherUnderground: Not Present UseWeatherStem: Present ---------------------- exception in blynkTerminalUpdate HTTPConnectionPool(host='blynk-cloud.com', port=80): Max retries exceeded with url: /nPvtTCRX4fNsfGqR17sWrklp7ww4WiWr/update/V32 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x74e51070>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')) exception in blynkEventUpdate HTTPConnectionPool(host='blynk-cloud.com', port=80): Max retries exceeded with url: /nPvtTCRX4fNsfGqR17sWrklp7ww4WiWr/update/V31 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x74135150>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')) exception in blynkTerminalUpdate HTTPConnectionPool(host='blynk-cloud.com', port=80): Max retries exceeded with url: /nPvtTCRX4fNsfGqR17sWrklp7ww4WiWr/update/V32 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x74135070>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')) exception in blynkInit HTTPConnectionPool(host='blynk-cloud.com', port=80): Max retries exceeded with url: /nPvtTCRX4fNsfGqR17sWrklp7ww4WiWr/update/V5?value=0 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x737d7390>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
I've done my best to have an accurate auth code pasted into the config program. Not sure what else I can do, or how I may have messed it up...
Thanks for any help.
|
|
|
Post by doxidad on Mar 29, 2021 3:10:53 GMT -8
Looks like your PI can't see the blynk server. There is a problem resolving (converting the name to an IP address) blynk-cloud.com.
Are you connected to the network via wire or wireless?
What does the command netstat -ar show for the gateway?
example: pi@WPI2:~ $ netstat -ar Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface default WincCom.lan 0.0.0.0 UG 0 0 0 wlan0 192.168.200.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
Your numbers displayed will be different - the gateway on the first line should be your router (mine is WincCom.lan) and I am connected vi wifi (wlan0).
|
|
|
Post by SDL on Mar 29, 2021 13:22:19 GMT -8
sawalker1234,
Yes to what doxidad suggests. Also do the following two commands and post the results:
ping blynk-cloud.com
traceroute blynk-cloud.com
BP
|
|
|
Post by sawalker1234 on Mar 30, 2021 0:01:53 GMT -8
I am connected via wireless on a dual frequency router at 2.4 Ghz. Here is my routing info:
pi@SwitchDocLabs:~ $ netstat -ar Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
pi@SwitchDocLabs:~ $ ping blynk-cloud.com PING blynk-cloud.com (45.55.96.146) 56(84) bytes of data. 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=1 ttl=32 time=140 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=2 ttl=32 time=186 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=3 ttl=32 time=448 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=4 ttl=32 time=248 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=5 ttl=32 time=494 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=6 ttl=32 time=117 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=7 ttl=32 time=103 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=8 ttl=32 time=201 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=9 ttl=32 time=108 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=10 ttl=32 time=404 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=11 ttl=32 time=96.4 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=12 ttl=32 time=448 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=13 ttl=32 time=161 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=14 ttl=32 time=495 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=15 ttl=32 time=107 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=16 ttl=32 time=105 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=17 ttl=32 time=104 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=18 ttl=32 time=124 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=19 ttl=32 time=403 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=20 ttl=32 time=96.1 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=21 ttl=32 time=455 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=22 ttl=32 time=95.5 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=23 ttl=32 time=496 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=24 ttl=32 time=126 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=25 ttl=32 time=103 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=26 ttl=32 time=96.3 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=27 ttl=32 time=124 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=28 ttl=32 time=405 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=29 ttl=32 time=107 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=30 ttl=32 time=450 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=31 ttl=32 time=102 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=32 ttl=32 time=498 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=33 ttl=32 time=96.2 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=34 ttl=32 time=95.9 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=35 ttl=32 time=111 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=36 ttl=32 time=138 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=37 ttl=32 time=408 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=38 ttl=32 time=95.2 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=39 ttl=32 time=454 ms ^C --- blynk-cloud.com ping statistics --- 39 packets transmitted, 39 received, 0% packet loss, time 61ms rtt min/avg/max/mdev = 95.223/231.866/497.703/158.943 ms
pi@SwitchDocLabs:~ $ traceroute blynk-cloud.com traceroute to blynk-cloud.com (45.55.96.146), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 1.980 ms 3.477 ms 3.519 ms 2 10.0.0.1 (10.0.0.1) 5.177 ms 5.399 ms 5.453 ms 3 96.120.100.189 (96.120.100.189) 19.307 ms 19.572 ms 19.598 ms 4 96.110.251.137 (96.110.251.137) 17.851 ms 18.305 ms 18.606 ms 5 68.86.96.149 (68.86.96.149) 17.713 ms 18.743 ms 18.766 ms 6 24.124.128.253 (24.124.128.253) 23.072 ms 13.422 ms * 7 lag-39.ear2.Seattle1.Level3.net (4.68.37.129) 412.203 ms 411.993 ms 411.777 ms 8 * * * 9 4.14.218.30 (4.14.218.30) 411.651 ms 4.14.218.22 (4.14.218.22) 411.644 ms 412.253 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * pi@SwitchDocLabs:~ $
|
|
|
Post by SDL on Mar 30, 2021 18:06:28 GMT -8
Hmm. Everything looks just fine. Especially the ping. The delays are long.
I note in your trace route that you are going through two NAT routers. 192.168.1.1 and 10.0.0.1. Do you have any idea why you are doing that?
BP
|
|
|
Post by sawalker1234 on Mar 30, 2021 19:27:49 GMT -8
I have a cable modem through my cable provider which sends signal to a router which runs the wifi and dns, maybe thats the reason? 192.168.1.1 is the router. I'm assuming 10.0.0.1 would be the cable modem.
|
|
|
Post by SDL on Mar 31, 2021 10:57:01 GMT -8
Well, maybe. I have a Wifi connected by wire to a router and here is what I get:
pi@SwitchDocLabs:~/SDL_Pi_WeatherSense $ traceroute blynk-cloud.com traceroute to blynk-cloud.com (45.55.96.146), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 3.347 ms 3.490 ms 3.401 ms 2 96.120.103.17 (96.120.103.17) 20.348 ms 20.825 ms 20.765 ms 3 68.86.97.253 (68.86.97.253) 22.459 ms 21.990 ms 22.254 ms 4 po-2-rur02.spokane.wa.seattle.comcast.net (69.139.160.126) 20.726 ms 21.395 ms 21.324 ms 5 24.124.128.189 (24.124.128.189) 21.264 ms 21.119 ms 21.506 ms 6 be-37-ar01.seattle.wa.seattle.comcast.net (68.86.96.5) 25.202 ms 27.077 ms 26.880 ms
Now notice that I pop through 192.168.1.1 and then out to normal routable IP numbers.
So that is a difference.
BP
|
|
|
Post by doxidad on Mar 31, 2021 13:17:06 GMT -8
Looks like the cable modem is not in bridge mode and is running its own NAT. In other words public IP -> Modem <private 10.0> Router <private 192.168>
It should look like this: public IP -> Modem <public IP> Router <private 192.68>
Call your cable provider support and have them put the modem into bridge mode - you normally can't do this since it is in the config file downloaded to the modem when it boots.
Once that is done, power off your router, reboot the modem and then power up your router - it should be fixed.
I don't think this is the problem though - you connects to blynk are timing out.
It could be the couple of 1/2 second responses from the upstream lvl3 routers.
|
|