|
Post by mikethechap on Jan 24, 2021 21:21:16 GMT -8
I'm getting an error when I am running SkyWeather2.py. It looks like the error occurs when it tries to take a picture. So I ran test testSkyCamera.py and got the same error. It looks like it boils down to:
Type
Error: Object of type bytes is not JSON serializable Here's the whole error statement:
mySkyCameraText= SkyWeather2 V001 24-Jan-2021 23:14:28 Wind Speed: 0.0MPH Wind Gust: 0.0MPH Temp: 32.0 F -------------------- SkyCam Package Sending -------------------- API Key: c35af0b6b86f7a064bebd3f44e3b88f4 ------->Sea Level 0.0 Traceback (most recent call last): File "testSkyCamera.py", line 17, in <module> SkyCamera.takeSkyPicture() File "/home/pi/SDL_Pi_SkyWeather2/SkyCamera.py", line 124, in takeSkyPicture sendSkyWeather() File "/home/pi/SDL_Pi_SkyWeather2/SkyCamera.py", line 386, in sendSkyWeather r = requests.post(url = API_ENDPOINT, json = data) File "/usr/lib/python3/dist-packages/requests/api.py", line 116, in post return request('post', url, data=data, json=json, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 519, in request prep = self.prepare_request(req) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 462, in prepare_request hooks=merge_hooks(request.hooks, self.hooks), File "/usr/lib/python3/dist-packages/requests/models.py", line 316, in prepare self.prepare_body(data, files, json) File "/usr/lib/python3/dist-packages/requests/models.py", line 466, in prepare_body body = complexjson.dumps(json) File "/usr/lib/python3.7/json/__init__.py", line 231, in dumps return _default_encoder.encode(obj) File "/usr/lib/python3.7/json/encoder.py", line 199, in encode chunks = self.iterencode(o, _one_shot=True) File "/usr/lib/python3.7/json/encoder.py", line 257, in iterencode return _iterencode(o, 0) File "/usr/lib/python3.7/json/encoder.py", line 179, in default raise TypeError(f'Object of type {o.__class__.__name__} ' TypeError: Object of type bytes is not JSON serializable
I'm guessing there's a package I'm missing somewhere. Or, maybe something else.
Any help would be appreciated.
Mike
|
|
|
Post by mikethechap on Jan 24, 2021 20:20:02 GMT -8
Thanks so much, Jason. I finally figured out that's what I needed to do. It was not at all clear from the instructions. I think one of your earlier posts helped point me in the correct direction. Be well. Mike
|
|
|
Post by mikethechap on Jan 23, 2021 23:43:52 GMT -8
This instruction on the top of page 20, v.1.2 says:
sudo python3 skyweather2.py
I get the error:
python3: can't open file 'skyweather2.py': [Errno 2] No such file or directory
Indeed, there is a SDL_PI_SkyWeather2.py file,with different capitalization, however: SkyWeather2.py. When I try to run SkyWeather
SkyWeather2.JSON File does not exist Traceback (most recent call last): File "SkyWeather2.py", line 21, in <module> from apscheduler.schedulers.background import BackgroundScheduler ModuleNotFoundError: No module named 'apscheduler'
What gives? I do not have the dedicated SD card. I thought I'd be able to set this up without it.
|
|
|
cmake
Jan 23, 2021 23:12:35 GMT -8
Jason likes this
Post by mikethechap on Jan 23, 2021 23:12:35 GMT -8
Thanks, Jason. I ran into the same problem as cbluto and your statement also appears to have gotten me past that roadblock. Please put this in the instructions: sudo apt-get install libtool libusb-1.0-0-dev librtlsdr-dev rtl-sdr build-essential autoconf cmake pkg-config Thanks, Jason.
Mike
|
|
|
Post by mikethechap on Mar 1, 2020 13:46:19 GMT -8
So, I don't understand. I would have thought a driver (and all the software for the ThunderBoard suitable for the Pro Mini) would be included on the SDL ThunderBoard Github. After all, it's part of the package when you get the kit. In fact, I did buy the kit (for the SkyWeather AND the ThunderBoard) twice over. When I was trying to "tune" the ThunderBoard for the ProMini is when I accidentally deleted the code on it. It would be nice to get it working. And, I believe, the code should be readily available to allow the product to be reset to factory default. Like a zip file with everything. By way of note, Sparkfun is no longer selling nor supporting the I2C alone version. Theirs V2 are now SPI by default, but I2C capable (with alteration) because of problems with a percentage of I2C boards. From here:
Thanks for any assistance you can provide.
Mike
|
|
|
Post by mikethechap on Feb 12, 2020 19:46:32 GMT -8
I'm looking for instructions about how to upload all the lightning detector code to the Pro Mini LP. I need to upload all the code and also include the wifi connection information. I haven't found that information on the site and it didn't work out of the box.
Thanks,
Mike Davis
|
|
|
Post by mikethechap on Mar 26, 2019 23:04:41 GMT -8
What’s the status on selecting a replacement for Weather Underground? SmartCitizen doesn’t seem to be doing much at all. Is Blynk fully integrated into the code at this point?
Thanks
|
|
|
Post by mikethechap on Mar 26, 2019 22:49:03 GMT -8
How/where does one add the 3k pull-up?
Thanks
|
|
|
Post by mikethechap on Jun 30, 2018 2:48:05 GMT -8
I got my BC24 today and was quite excited about it. The time may show that I'm typing this at 3:45am here in Dallas.
I am frustrated. As seems so often the case with SwitchDoc products, they are technologically pretty cool. But, they also have non-tutorial, tutorials. They are nothing like the Adafruit tutorials: Nothing at all. And, for you to get your products in people's hands and keep current purchasers returning, they need to be made for newbies. Or, at lease motivated newbies.
How are people who are starting out in their journey supposed to know what provisioning refers to, make any sense of the BC24 connection tools "IOT_Espressif or another application ESP8266 SmartConfig"? Those apps make no sense whatsoever, feature no written instructions. The apps are crap.
The WPS setup option doesn't say anything about what buttons to push, when, and really nothing about the sequence to set this up. This is what I'm asking for: a step-by-step explanation of the details an inexperienced person can expect. Same for the AP method.
How do you get to that point? Right now, I have 5 red lights flashing. I have no idea what those three red lights mean. Indeed, aside from an explanation of the istory of connecting via WPS, and the amazing things this board really can do, there's no guidance.
I can't even tell how to upload the sketches with my computer using USB (given the failure of every one of the 3 really cool wireless methods). If you hadn't prepragrammed the BC24 with something, I would really be angry.
Here's the thing: I think you have really cool stuff. Perhaps there's enough business coming in to only support people who are smart enough and generous enough to make these products work without real tutorials. But, those less skilled can't succeed in the absence of screenshots, pictures of physical connections in various resolutions (not low-quality pictures linking to Pinterest), Step 1 do this, step 2 do that. I have no idea when to push the buttons or switches nor what they mean (except the Mode one does have some stuff that it deals with the Mode, though I'm still not clear on what that means).
So, all I have is a pretty cool display going round and round. At this point, I don't know how to use it, connect to it, or anything else other than how to plug it in. That's not enough anymore. Unless there's a serious effort to make tutorials similar to the Adafruit tutorials, I'm done, I think, buying or supporting SwitchDoc products or Kickstarters. I say I think because the products are always tantalizing. And, when there are glitches you are really, really good at helping out. But, as far as setting all this up, SwitchDoc doesn't. I will just have to try to remind myself that it will be too frustrating to mess with it. Please, please hire someone or pay for tutorials by the piece. Just slow down the train of products until you make usable tutorials appropriate to motivated newbies. As it stands, these products aren't even for them.If a newbie can't connect in two hours with the provided instructions, the instructions aren't adequate. Oh, and please don't confuse instructions with linking people to other tutorials, articles on SmartConfig, app source code, etc.
I really want SwitchDoc to succeed. But, I also want to enjoy these projects and feel like I can succeed in setup in an hour or so. It might be helpful when you do Kickstarters to say who your audience is and the expected skill level to be successful and find the project pleasant.
|
|
|
Post by mikethechap on Jun 2, 2018 20:52:13 GMT -8
The same thing is happening with me. I went for probably six months with my Grove Weather Pi reporting temperature and humidity just fine using the AM2315. Then, early this winter it started reporting 32degrees 24/7 to Weather Underground regardless of the temperature. For various reasons, I left it that way until 2 weekends ago when I changed out the AM2315. After a reboot, it started reporting the right temp/humidity again. Yeah, right? Then tonight, I checked and it's back to reporting 32 degrees. That's 2 AM2315's that have quit reporting correctly. So, for caughron, did you ever implement the powersaver. If so, did it fix it? For SDL, I'm a little concerned about "programmatically shutting it down and then powering it back up." Is that in the GitHub software somewhere for that device? Is there another device that might be more dependable but still economical? When you say programmatically shutting it down, I assume you mean that it has some sort of timer that routinely shuts it down and starts it back up? And, that I could figure out how to do this? I just placed an order for more items for my station upgrade but if this is going to be a continuing issue... In other respects, reporting to WU is fine and things look okay when I SSH into to Grove Weather Pi except for the AM2315. Last, when these are "locked up" does that mean they are shot permanently? Update 6/4/18: In reviewing several different pages, there is mention of the need for 2 pull-up resistors with the AM2315, quoting from the Adafruit AM2315 page: Could that be part of the reason for potential issues with the AM2315? I also found more information here, with a downloadable guide. Much of that, however, deals with timing, etc. It also says that the resistors are required.
|
|
|
Post by mikethechap on May 29, 2018 10:48:48 GMT -8
I'll leave aside the disregard of Weather Underground (WU) for Personal Weather Stations. I took comfort in the knowledge that my weather station information might improve weather prediction through machine learning given larger datasets of local and real-time data. Here in Texas, as elsewhere, tornadoes can spin up in a heartbeat. Our home had over 21k damage in 2016. Having more and better data might help improve the ability to reliably predict loss of life. This is the focus of my interest in my weather station. To that end, I've been interested in the Citizen Weather Observer Program (CWOP). Data ultimately ends up on the NOAA MADIS servers. Of course, unlike with the Weather Underground benefit of being able to see your data live, the CWOP approach doesn't have the ability to easily show your station data. Another provider, without cost, is PersonalWeatherStation.com, tied into the Aeris network. As you consider what interface to design for, here are some things that are important to me in order of priority: - Ability to upload to NOAA (or other weather science and prediction resources)
- Ability to view my PWS data online
- Reliability
- Cost (over $10/month and I'm on the fence unless there are some personalization perks)
- History available?
- Ease of use and interface
As an example, here's how I would have scored WeatherUnderground (1-5, 5 = best, with comments following): - Use of aggregate data to improve weather prediction? 4 - though I really have no idea where the data went after it got to WU, they used to say that they would aggregate data from PWSs to improve weather prediction. At least it got fed into WU predictions, if they are to be believed.
- Ability to view my PWS data online? 3 - an okay interface that included solar radiation, soil temperature, and other details.
- Reliability? 4, maybe 5. Pretty reliably able to upload AND view my PWS data.
- Cost? 5. But, staying with WeatherUnderground would reportedly cost about $800/month.
- History available? 5 Easily able to view past PWS data for long term trends. I don't see this in OpenWeatherMap, for instance, except at considerable cost.
- Ease of use and interface? 3 No ability to personalize the interface except for a little PWS update box and the webcam interface.
Other services could be similarly ranked. I liked WeatherUnderground, for the most part. Looking at the services mentioned earlier in the thread as well as elsewhere, I'm inclined to PersonalWeatherStation or OpenWeatherMap.
|
|
|
Post by mikethechap on Jan 29, 2018 5:55:15 GMT -8
One other question. If I were to switch to the Lora version, would I need the Yagi antenna? For less than 75'? Or, would another antenna do? And, do I need a Lora antenna for both transmitter and receiver?
Can I suggest that the Lora WXLINK kits be modified or separate versions or add-ons be created that include antenna/s? I imagined that it would be frustrating to get one of these kits and find I needed to add 1 or more antennas, especially if I was just getting started.
Moreover, on the Store descriptions, I think I would add that an antenna is also required. If both transmitter and receiver need one then I would note that, as well. Perhaps no antennas are necessary? In which case, my confusion might also be shared by others?
|
|
|
Post by mikethechap on Jan 28, 2018 21:10:25 GMT -8
Awesome! Thanks for the reply. Nearly complete with the infrastructure (a nicely stained 4x4 that will have a wooden box on top connected to the 4x4 with an industrial lazy-Susan). We’ll mount the distant enclosure, the wind/rain/vane, temp and the solar array to the 16x16” square and the lazy-Susan will allow us to align the solar for greatest power. Maybe later, I’ll use you sun tracker feature. Anyway, we’re having fun making progress. Your suggestions will make it easier.
|
|
|
Post by mikethechap on Jan 24, 2018 3:11:54 GMT -8
So, I'm finally preparing to separate my GroveWeatherPi into 2 enclosures with the wind/rain sensors being further away from the house. The distant box will, of course, use WXLINK. The WXLINK instructions have the instructions for connecting up the wind/rain instruments. But, I'm wondering about putting the temperature/humidity sensor in there as well? How about a ground moisture sensor?
Would the WXLINK programming have to be altered to get it to report out these added values to the GroveWeatherPi?
If it is possible, how would I do the wiring? Are there instructions?
I'm afraid the temperature/humidity sensor may be picking up some radiant heat from the house. I plan to keep the light sensor, Thunder board, and possibly air quality sensor in the enclosure near the house since I don't think they are affected by proximity to the house.
Thanks for any advice you can give.
Mike D.
|
|
|
Post by mikethechap on Jan 24, 2018 2:46:12 GMT -8
I gave up on the whole MiloCreek interfaces. Too much of a learning curve, basically iOS only, I did see more downtimr than I liked, and the instructions were cryptic. There's no doubt it's well intended with its seafaring design. Perhaps more important, the case for it's use was strong: if I remember rightly it monitored the first distant weather station that formed the Curocao Project. It was the basis for what we have now. As such, it kept a close eye on power issues since the station was using solar unattended for much of the time. So,the MiloCreek stuff has a lot of power-related graphs, etc. I guess what I'm saying is that those power graphs were very relevant to where Switchdoc is now with Patting the Dog, Watchdog Timers, etc.
|
|