first planning stage: bird-house - data-logging and transport - to a server with Raspi or ESP32-Cam-module


Recommended Posts

Hello and good evening community,

 

first planning stage: bird-house - data-logging and transport - to a server with Raspi or ESP32-Cam-Module - 


I have a bird house in the garden - more precisely in a nesting box - and I want to attach a camera there. To date, great tits have always been inside. There are already many Birdhouse (Vogelhaus)-camera projects and many solutions with a Raspi-base or with the ESP32-Cam module: 

 

The goal: I would like to transfer pictures from the bird house next year (in the hope that someone will move into the house again) to a server. The alternative would be a Pi including a Pi Cam. But in terms of electricity and size, the ESP32 would probably be better.

 

main goal and approach: The bird-house will be outfitted with some ideas of IOT to track what kind of conditions attracts guests and will tweet you when they are at the door! in fact for the bird watchers, it is hard to know when the birds will be visiting your bird house. The smart birdhouse detects guest bird entries and exits. the set-up: It is also set up to take a photos and furthermore also tweet-notifications when a bird comes near the birdhouse. Sensors measuring the temperature, humidity, ,sounts and light inside/outside the birdhouse to help analyze the optimal condition for attracting guest-birds so that they will want to fly to the house.

i guess that a lot of extras with this electronically monitored bird house is necessary:  This will not only give us a look at what’s going on inside, but provide a source for several other bits of data as well that we can analyze and work with. First off, i want to set up a  camera that should be mounted to the underside of the roof. With this we get a  looks down on the nesting area and features night vision so that we can peek in any time day or night. We should use a WiFi webcam that operates separately from the other electronics. That would be great. With the remainder of the setup - we should be able to harvest temperature and humidity data inside, and besides that also and furthermore temperature outside: Besides that  and a in-and-out count for the doorway provided by an IR transmitter/receiver pair. That one also left a lot to be desired as far as protecting the electronics. 

 

First of all: in principle I would also trust the current hardware / software version of the ESP32 that it runs stably. And the ESP has a full http stack on it, so you can use the WLAN at the same time.

I wanted to briefly discuss the project with you here at an early stage in order to exchange ideas and possibly add new functions. So only with your ideas, opinions and reviews. If you read, you will find that a lot has not yet been determined and that 
I am still in the "viewing and collecting phase". I have all parts here - there should hardly be a thing that I have to order separately - let's take a look at the wood ..

Important: I do not want to disturb the birds, so I should probably cut off the power supply a bit, so that I can at least restart completely if the system gets stuck. Seen in this way - the battery should have a long line on it, the bird house hangs at a height where you can't get it without a ladder  that's 5 meters high. The question is what the cam can do and how good the camera is. e.g. The basic idea of the project is very simple: in the end,  it is an intelligent webcam mounted in the nesting box with software for detecting movement, in combination with sensors for monitoring the  temperature in the house.


So it should be about the following data:
- take pictures under event control;
- Images may transmit moving images;
- Humidity and Temperature Sensor
- tweet-notifications and sounds
- a in-and-out count for the doorway provided by an IR transmitter/receiver pair.
- Log more data if necessary; What would you log here....!?


Approaches and architectures:
The Raspberry or ESP - they are practically digital observers and allow programs and parameters to be viewed remotely and during operation change and thus flexibly adapt the solution to new framework conditions. With ESP and RasPi you can build everything well and have a highly flexible configurable system,

 

Tasks and dates; log temperature, take pictures and above all:
Log temperature: using a temperature sensor. several measuring points are planned, simply connect and connect further DS1820 via the serial interface. I think that one has to be careful with the frequency of the (constant) access of the processes - otherwise the maximum number of write accesses for the SD card may have been reached. Mounting the camera: if necessary, connect the camera with a 75 centimeter flat cable and install the ESP / RasPi in a separate housing. This would minimize disruptions to 
the breeding season during maintenance work. GGF could build all of the technology in a drawer under the nesting house. That would also be an idea.

 

Camera options - a first overview:


A NoIR camera from the Raspberry Pi is possible. (NoIR camera at Amazon)
This camera does not have an infrared filter and, together with infrared lighting, also enables a picture in the dark. It is therefore quite suitable for a nesting box project.
Raspberry Pi Zero W with MotionEyeOs: with the "Motion" software and the Raspberry Pi Cam, you can react to movements in front of the camera.
There is even the MotionEyeOS operating system here, which makes the Raspberry Pi Zero W an easy to configure surveillance camera with motion detection.
Principle: the Motion software detects motion in front of the camera, saves the images and / or videos on the SD card or a network storage device and then carries out user-defined actions. For example, after detecting a movement, uploading the images to the dropbox or an email notification. (more about this here: http://raspberry.tips/raspberr…ngskamera-mit-motioneyeos)
Raspberry Pi Zero W with MotionEyeOs can also be used e.g. drive with a "finished" infrared camera (https://www.amazon.de/MakerHawk-Raspberry-Nachtsicht-Infrarot-Himbeere/dp/B073W6KRSK/ (affiliate link)). I think that the setup required here should not be a mega problem so far and I've heard that it should work well. But I wonder if the potential residents will not be bothered by the visible red light on the camera. If you work with headlights: if you work with "headlights" it can often happen that the light emits in the visible area; But we can also use a Abus type mini IR spotlight with 2 LEDs and a twilight sensor;


Furthermore, one can also use e.g. Use Bright Pi. It is a small circuit board with several infrared LEDs. These can then be controlled via the Raspberry Pi. 
The whole thing works relatively easily via commands: I found a short and very compact guide to this here: https://www.pi-supply.com/bright-pi-v1-0-code-examples Unfortunately, the infrared LEDs have to be turned on themselves the small circuit board to be soldered on. The infrared board in the nesting box is best attached next to the camera, which illuminates the field of view of the mini camera.
Basically, the question arises: is that still acceptable for such a project, or is the NoIR better?
- Infrared LEDs - but they are sometimes bright depending on the product.
- I had already seen cameras with a comparatively strong red glow.

So then the question is whether the birds might not be bothered by it !? I had heard of cameras with an IR solution that only emitted a very weak glow - and the birds had no problem with that.

 

further camera details and types:
- the "OV2640": According to the product description, OV2640 and OV7670 cameras are supported by the ESP 32,
- the Pi has what it feels like to be hundreds of variants with IR or without ...
- ESP32-CAM WiFi + Bluetooth camera module ESP32-CAM development board WiFi Bluetooth dual module OV2640 2MP
Durable Mini Wireless Dual Core Development Board Camera for Arduino…. https://www.amazon.de/esp32-camera/s?k=esp32+camera

Question about data transfer to the resolution and the entire concept: Basically: The question is how the resolution should be:
- OV2640 is quite usable so far, apart from IR now: as a guide: 320x240 MJPEG_Stream the ESP32 manages approx. 20-25 fps, maximum resolution 1600x1200,but then there are only 2-3 fps.
- Of course, this cannot be compared to a RasPi-Cam;
- RasPi Zero W + RasPi-Cam is also relatively small and the power consumption is of course much higher, but FullHD with 30fps is possible. If the WLAN plays along at the location.

Basically, in my opinion, it is also a classic Pi application. this would require the possibility of a permanent power supply - if this is guaranteed then I could use a Pi Zero. But then the data transfer is not yet solved or?

 

what bout more sensors: 
i want to add many sensors: The sensors schould find themselves nestled in plastic enclosures, although some work needs to be done to ensure that the temperature and humidity sensors. What about this setup?!

 
Questions about DATA RATES:
- how about a reduction to 1-3 frames per minute? What about:
- in total - if you extrapolate that: That would be about 3000 pictures a day,
- if I convert it afterwards on an external device with 30fps that would be 100 seconds a day,
that would result in a cool video from hatching to departure ...
But the data-rates: they depends very much on the ideas and the basic-concepts. Color takes up more space than grayscale. 
Then weu have to weigh up what we prefer for a given bandwidth: more compression or lower resolution. 
And who will calculate the images for the desired resolution? Is the CPU sufficient for this or are there any dropouts?


Additional idea: Maybe the first project should be equipped with a motion detection, which will send me a mail if something settles in, what do you think about the thoughts
 of data transmission - about the basic architectural ideas - and so on.
- a movement notification that sends a mail if something nests,
- and this mail can then be routed to several addresses
- or to several e-mail addresses -
- If necessary, we could also set it to a gateway that then transfers the data via Whatsapp
- If we want continuous operation, a watchdog is not bad.

So much for the collection of ideas: So now only with your ideas, opinions and reviews. If we read, we will find that a lot has not yet been determined and that I 
am still in the "viewing and collecting phase". I have all parts here - there should hardly be a thing that I have to order separately - let's take a look at the wood


love to jear  from you

regards 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Glow 26.10 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 26.10 changelog: New Features The bootstrapping algorithm has been completely redesigned. The software can now launch directly without requiring TS Preloader. As part of this change, the startup splash screen displayed during initialization has been removed. In addition, spikes in CPU usage have been eliminated, resulting in a more stable architecture with significantly lower memory consumption. The Microsoft Office detection infrastructure within the Operating System section has been enhanced. Additional detection support has been added for Office C2R (Click-to-Run) installations. Furthermore, the license status evaluation system has been improved, and the priority order has been revised as follows: Licensed > Grace Period > Other (NOTIFICATIONS, EVALUATION, etc.). Glow now includes preliminary support for Wi-Fi 8 technology, allowing more detailed information to be displayed for Wi-Fi 8-compatible network adapters. Glow now provides full support for Bluetooth 6.2. Adapters supporting Bluetooth 6.2 can be analyzed in greater detail and with improved accuracy. The disk distribution view in the Disk section has been modernized, replacing the traditional table layout with a new 2×2 card-based design. The TS Custom Controls module has been updated to v26.7. Thanks to the new custom controls, all Türkaysoft applications now offer a more modern and consistent user interface aligned with Windows 11 design standards. Bug Fixes Potential line-ending handling issues in the Office detection code within the Operating System section have been resolved. Additionally, the output format has been standardized to UTF-8 to prevent character encoding issues and ensure consistent data processing. Several stability and file management issues within the Debugging infrastructure have been addressed. Problems that prevented new log files from being created after Debugging was disabled, as well as issues causing debug records to be lost, have been fixed. File deletion and reaccess issues that occurred after file locks were released have also been resolved. In addition, a bug that caused newly recreated log files to remain locked after deletion has been eliminated. Unnecessary blank lines within debug logs and the extra empty line that could appear at the end of log files have also been corrected. A shortcut key conflict caused by assigning identical hotkeys to both the DNS Test Tool and the Donation page has been fixed. The DNS Test Tool can now be accessed using CTRL + Shift + D, while the Donation page is available via CTRL + Alt + D. Changes The service responsible for providing the Public IP Address and Internet Service Provider information in the Network section has been updated to use the ipinfo.io infrastructure. This change improves the accuracy and consistency of the displayed data. (No external requests are made while Hiding Mode is enabled.) Some terms in the Dutch and Korean language files have been updated to make them clearer and more user-friendly. [TS Updater] Before the update process begins, users are now prompted to choose whether they would like to view the release notes. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 26.10 | 1.8 MB (Open Source) Links: Glow Homepage | Screenshot | Github Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Maradona if hydration breaks had existed in Mexico 86.
    • The quantum search for Time's origin had an equally mind-boggling conclusion by Sayan Sen Image by Steve Johnson via Pexels A theoretical study from researchers at the University of Surrey suggested that the direction of time may not be fundamentally fixed in certain quantum systems. The work, published in Scientific Reports, examined how the “arrow of time” could emerge from microscopic physics and found that time-reversal symmetry can remain intact even in models used to describe processes such as energy loss and thermalisation. The arrow of time refers to the observed one-way direction from past to future in everyday life. In macroscopic processes, this is easy to see. Spilled milk spreads across a table and does not gather back into a glass, and heat flows from hotter objects to colder ones. These processes shape the common sense idea that time moves in a single direction. However, at the level of fundamental physics, many equations do not prefer a direction of time. Time-reversal symmetry means that the same physical laws can describe a system whether time moves forward or backward. This has made it difficult to explain why irreversible behaviour appears in the large-scale world even when the underlying rules do not require it. Dr Andrea Rocco, Associate Professor in Physics and Mathematical Biology at the University of Surrey, described this contrast: "One way to explain this is when you look at a process like spilt milk spreading across a table, it's clear that time is moving forward. But if you were to play that in reverse, like a movie, you'd immediately know something was wrong – it would be hard to believe milk could just gather back into a glass. However, there are processes, such as the motion of a pendulum, that look just as believable in reverse. The puzzle is that, at the most fundamental level, the laws of physics resemble the pendulum; they do not account for irreversible processes. Our findings suggest that while our common experience tells us that time only moves one way, we are just unaware that the opposite direction would have been equally possible." The study focused on open quantum systems, which are quantum systems that interact with a surrounding environment. This environment, often described as a heat bath, can exchange energy and information with the system. The researchers used this framework to study how a direction of time might appear even when the underlying physics does not enforce one. A key part of the analysis involved the Markov approximation. This is a simplification used in many models where the system is assumed not to retain memory of its past states. The idea is that changes depend only on the current state, not on earlier history. This is commonly used when studying thermalisation, which is the process where a system settles into equilibrium with its environment. The study also used concepts such as master equations, including the Lindblad and Pauli equations, which describe how probabilities of different quantum states change over time. Another related model discussed was quantum Brownian motion, which describes the random-like movement of a quantum particle interacting continuously with its environment. In these descriptions, a “memory kernel” can appear, which is a mathematical term that accounts for how past states influence current behaviour. The researchers found that applying the Markov approximation did not break time-reversal symmetry. Even when the system interacted with an effectively infinite heat bath, the resulting equations of motion remained symmetric in time. This meant that the same mathematical description could, in principle, run forward or backward in time without contradiction. The study further showed that standard frameworks used in open quantum systems, including quantum Brownian motion and master equations like the Lindblad and Pauli forms, could be written in a time-symmetric way. These equations are typically used to describe processes that look irreversible, such as dissipation and thermalisation, but the results suggested they can also be interpreted as allowing evolution in both time directions. Thomas Guff, Research Fellow in Quantum Thermodynamics, said: "The surprising part of this project was that even after making the standard simplifying assumption to our equations describing open quantum systems, the equations still behaved the same way whether the system was moving forwards or backwards in time. When we carefully worked through the maths, we found that this behaviour had to be the case because a key part of the equation, the "memory kernel," is symmetrical in time. We also found a small but important detail which is usually overlooked – a time discontinuous factor emerged that kept the time-symmetry property intact. It’s unusual to see such a mathematical mechanism in a physics equation because it's not continuous, and it was very surprising to see it appear so naturally." The researchers also noted that deriving a one-way arrow of time from time-reversal symmetric microscopic dynamics remains an open problem across fields such as thermodynamics, statistical mechanics, particle physics, and cosmology. Their results suggested that some standard descriptions of irreversible behaviour in open quantum systems may be better understood using a time-symmetric formulation of Markovianity. According to the study, processes such as thermalisation, which are usually treated as irreversible, could in theory be described in a way that allows evolution in either time direction under the same rules. This does not imply that time reversal occurs in everyday life, but rather that the underlying equations do not strictly enforce a single direction. Overall, the findings suggested that the perceived direction of time may emerge from how physical systems are modelled and approximated, rather than from a fundamental asymmetry in the laws themselves. The researchers noted that this perspective could have implications for ongoing work in quantum mechanics, thermodynamics, and cosmology on the origin of time’s arrow. Source: University of Surrey, Nature This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • A bit premature... 100% Marketing. Bizarre.
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      581
    2. 2
      +Edouard
      182
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!