Field validation
LARKBIRD Smart Coop Door
Remote door control and real status feedback for coops that may have neither reliable Wi-Fi nor mains power at the door.
Indoor Wi-Fi gateway + solar/battery outdoor endpoint.
One ~200m obstructed line-of-sight test returned information and door actions.
Icing, final wireless/FCC path, power, and mechanical reliability.
Development product imageThe real environment
The door is not next to the router—and a sent command is not a closed door.
Backyard coops and small farm enclosures may sit away from the house. Wi-Fi can be weak at the door, mains power may not be available, and remote control has limited value if the owner cannot confirm that the action completed.
The architecture therefore separates indoor networking from outdoor movement and returns state to the owner.
Three reasons to care
Send low-power control outdoors.
Continuous outdoor Wi-Fi raises power and coverage demands. A mains-powered indoor Wi-Fi gateway connects to the door over a low-power 433MHz-class link.
Remote access without requiring strong home Wi-Fi at the coop. The architecture is confirmed; final frequency, power, and FCC path remain under validation.
Keep network-heavy work away from the door.
A coop may have no 110V outlet. The solar/battery endpoint focuses on motor action, state sensing, and low-power communication.
An architecture aligned with outdoor power conditions. Solar power, battery life, and low-temperature performance need final-version testing.
Close the loop instead of only sending a command.
Owners need action confirmation when away. Door state, battery, signal, logs, and exception alerts return through the gateway/app direction.
A closed feedback loop. This is the current interface/system direction, not proof of public app availability or every alert path.
How it works
The indoor gateway handles the always-on network role. The outdoor endpoint concentrates on movement, sensing, and lower-power communication.
Remote open/close, door state, battery, signal, logs, sunrise/sunset schedules, and alerts are in the current system direction.
Always-on Wi-Fi work stays inside, closer to the home router and a power outlet.
Motor action, state sensing, and bidirectional communication use a low-power 433MHz-class link direction.
Development diagram · Final frequency, power, antenna, and regulatory configuration remain version-dependent.
Development journey
The door is not next to the router.
The target coop can be far from the house without stable Wi-Fi or mains power.
The problem changed from “add an app” to making the outdoor system reachable and knowable.
Indoor gateway + outdoor endpoint.
Always-on Wi-Fi/cloud work moved to a mains-powered indoor gateway.
The outdoor endpoint retained movement, state sensing, and low-power communication.
Low-power and bidirectional.
A bidirectional 433MHz-class point-to-point link became the current architecture direction.
Final frequency, power, antenna, and regulatory configuration remain version-dependent.
Return the outcome.
Control, door state, battery, signal, logs, schedules, and alerts were designed as one system.
Remote action is most useful when the result travels back to the owner.
One ~200m recorded test.
A line-of-sight test with trees and buildings as obstructions received information and completed open/close actions.
This is one recorded test, not a rated or guaranteed 200m range.
Reliability work surfaced.
Icing, lock timing, Hall-sensor alignment, button fit, and mechanical tolerances appeared as active problems.
Extreme icing is not solved and remains visible in the validation plan.
Repeat, measure, review.
Launch package and app/listing work continue while field validation remains active.
Measure bidirectional success, low-power behavior, cycle life, icing response, and final wireless/FCC configuration.
Evidence gallery
Each item states what it supports and what it cannot establish alone.
The separate indoor-gateway architecture.
Final industrial design, certification, or availability.
Intended English control and status flows.
A public App Store release or every production alert path.
Physical prototype development and power architecture work.
Production reliability, cycle life, or certification.
One obstructed line-of-sight test received information and completed actions.
A rated range, every environment, or through-wall 200m performance.
Current status
At approximately 200m with trees and buildings as obstructions, information returned and open/close actions completed.
Gateway, low-power field link, state return, battery/signal visibility, logs, schedules, and alerts define the current direction.
Repeated communication, power behavior, mechanical reliability, app/listing work, and wireless review remain active.
Final frequency, power, FCC path, low-temperature power, and production mechanical reliability remain open.
Product FAQ
One test is a data point, not a universal rating.
No public iOS or Android availability is claimed. The English interface shown here is labeled as a concept based on the current control/status direction.
No. One approximately 200m line-of-sight test with trees and buildings as obstructions received information and completed door actions. Actual results depend on the environment.
No. Final wireless frequency, power, antenna, and the FCC path are still under validation.
The current architecture direction uses a solar/battery outdoor endpoint while the indoor gateway uses mains power. Final power and low-temperature performance require testing.
That boundary is not fully solved. Icing retests and mechanical reliability remain active validation work.
Field updates
Choose launch updates, field-test interest, or both. This prototype stores submissions only in this browser.
