|
Post by doxidad on Jun 9, 2022 3:48:27 GMT -8
Try this -
sudo pip install apscheduler
NOTE the spelling of apscheduler er not ar
|
|
|
Post by doxidad on May 30, 2022 6:57:24 GMT -8
Just ignoring the picture doesn't save power. W Yep you're correct - not sure what I was thinking.
Actually what I was thinking is how not to store images in the database or on disk. Not sure about anybody else, but watching a composite 24 hr video with 8-14hrs of dark is not that exciting.
Looking at the code on the PI, I have a scheme that I'm going to try. If it works I'll publish the code - doesn't look like there is much needed.
|
|
|
Post by doxidad on May 26, 2022 6:59:46 GMT -8
Just ignoring the picture doesn't save power. W Yep you're correct - not sure what I was thinking.
|
|
|
Post by doxidad on May 24, 2022 15:46:28 GMT -8
W, why not just let the camera transmit every minute and when the picture is received check the time and don't store it in the database if it is the time frame you don't want recorded. I have not looked at the mechanics of implementing this, but you may want to explore it.
|
|
|
Post by doxidad on May 23, 2022 9:15:27 GMT -8
These all look like errors connecting to blynk. The first errors say it can't resolve the blynk server to make a connection.
Try pinging blynk-cloud.com to see if you can resolve the name to address.
pi@WPI2:~/SDL_Pi_SkyWeather2 $ ping -c4 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=48 time=27.2 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=2 ttl=48 time=25.6 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=3 ttl=48 time=25.9 ms 64 bytes from 45.55.96.146 (45.55.96.146): icmp_seq=4 ttl=48 time=23.8 ms
--- blynk-cloud.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 9ms rtt min/avg/max/mdev = 23.801/25.618/27.202/1.211 ms
|
|
|
Post by doxidad on May 23, 2022 4:00:55 GMT -8
You can modify testSkyCameRemote.py
Look for this section in the code: 157 158 # what ID to test 159 cameraID = "C939" <--- Make sure your cameraID is correct 160 #cameraID = "3BAD" 161 #cameraID = "F329" 162 #cameraID = "26FD" 163 #cameraID = "+" #sends to all cameras 164 # this command will be sent after an INFO messagetype 4 from cameraID 165 #sendWhatCommand = MQTTERASEMEMORY 166 #sendWhatCommand = MQTTCYCLECHANGE 167 #sendWhatCommand = MQTTBLINKXTIMES 168 #sendWhatCommand = MQTTRESOLUTION 169 #sendWhatCommand = MQTTBLINKXTIMES 170 #sendWhatCommand = MQTTUPDATEPARAM 171 #sendWhatCommand = MQTTSTARTDELAY 172 #sendWhatCommand = MQTTREBOOT 173 sendWhatCommand = MQTTTURNOFFBLINK <--- comment out all the commands and uncomment this one
Run the prrogram - sudo python testSkyCamRemote.py
You can use this program to set/change any of the available parameters See the SkyCamAssemblyAndTestManual. The settings and how to set them are near the end of the document.
|
|
|
Post by doxidad on May 16, 2022 3:37:01 GMT -8
Which LED? The one that flashes when a picture is taken or ?
|
|
|
Post by doxidad on May 5, 2022 8:56:20 GMT -8
Install cmake
sudo apt install cmake
|
|
|
Post by doxidad on Apr 24, 2022 8:51:10 GMT -8
Turn off your router and wait about 5 or so minutes and then power up the SkyCam. You should see the camera show up as an access point and you can make your changes. Once they are done and saved, turn you router back on. After the router is up, you may have to power cycle the SkyCam.
The bottom line is if the camera can't make a connection to your Wifi it goes into access point/setup mode.
|
|
|
Post by doxidad on Apr 11, 2022 4:15:09 GMT -8
I'm seeing the same thing with 1.3
| 2022-04-10 10:49:56 | 33308 | | 2022-04-10 11:04:56 | 33803 | | 2022-04-10 11:19:56 | 74305 | | 2022-04-10 11:34:56 | 67395 | | 2022-04-10 11:49:56 | 101399 | | 2022-04-10 12:04:56 | 2147480000 | | 2022-04-10 12:19:56 | 21163 | | 2022-04-10 12:34:56 | 46394 | | 2022-04-10 12:49:56 | 26579 | | 2022-04-10 13:04:56 | 32762 | | 2022-04-10 13:19:56 | 114530 | | 2022-04-10 13:34:56 | 109620 | | 2022-04-10 13:49:56 | 25427 | | 2022-04-10 14:04:56 | 44127 | | 2022-04-10 14:19:56 | 2147480000 | | 2022-04-10 14:34:56 | 127744 | | 2022-04-10 14:49:56 | 121639 | | 2022-04-10 15:04:56 | 115687 | | 2022-04-10 15:19:55 | 110045 | | 2022-04-10 15:34:56 | 107524 | | 2022-04-10 15:49:56 | 102470 |
2147480000 = 7FFF F1C0
|
|
|
Post by doxidad on Feb 20, 2022 5:00:31 GMT -8
Just a note - You could have just installed the latest version of python 3.x to fix the problem.
Hope you get it sorted out. I didn't think about version of python in the v3 tree just v2 <=> v3 differences.
|
|
|
Post by doxidad on Feb 18, 2022 17:49:23 GMT -8
Try sudo apt install python3-mysqldb
python3-mysqldb is only the python interface library to the mysql/maria database. You do have mysql/maria installed?
|
|
|
Post by doxidad on Feb 14, 2022 12:30:02 GMT -8
Install python3-mysqldb. See if that helps.
|
|
|
Post by doxidad on Jan 17, 2022 5:05:21 GMT -8
The bits are CAB so 6 would be 110 (4+2+0) bits are powers of 2
C - 1 Voltage below 2.9V A - 1 Solar Present B - 0 HM3301 not present
So - solar is there, but battery low and because it is low, the HM3301 is shut off
I run into the same problem since it is winter and there a very few sunny days. I get about 2-3 weeks and then have to pull the box (lighting detector) and charge the batteries. Runs fine the other 3 seasons. I also have 2 solar cells on the unit which have helped somewhat. My area is known for having very few sunny days all year round since I am about 30 miles south of Lake Erie. Another 20 miles south the weather is totally different.
|
|
|
Post by doxidad on Jan 15, 2022 17:25:22 GMT -8
Legal in US since 2014. Not sure about other countries.
|
|