If I were you I would use an esp8266 or similar to turn a bright white LED on and off put it against the light sensor of the auto door and encapsulate it in something like blu tack so no other light can get to the sensor. You would of course need a usb power source but often power banks and solar panels can be combined to make such a thing or you just run a USB cable out to the coop.
Because of horrible Battery Life of my units I am forced to use 12V Batteries for Power supply. Of course Omlet Auto Door Units detect my batteries as “grid”.
Is there any way to receive voltage readings from these batteries (to be able to know when its time to recharge them).
How do you protect the battery from the chickens and the weather? I am looking at this too.
I have in the past managed to get hold of a wireless battery monitor for that sort of job - not seen one recently, but not really looking though.
I put together this HA integration for my omlet chicken coops. My coops are currently under some big oak trees so the light sensor is not always the best/accurate. I am able to use a service call every night to update the door open / close schedule to the next days sunrise and sunset time. The benefit of this approach I find is I can keep the coop in deep sleep for the entire day and only come online during a short time when I am updating the next days schedule, which is appears to help with the battery life of my two coops. GitHub - krozgrov/ha-omlet-integration: Custom Home Assistant integration for Omlet devices, enabling monitoring and control of Autodoors and related devices. Includes features like battery level monitoring, door/light control, and updates via API.
1 Like
That was one of the challenges I had - so I made sure with the integration I created I added those service action to update some of the common items via HA services.
1 Like
Hi @krozgrov thank you for making this HA integration! Could you please detail how you have your HA automatic setup as you’ve mentioned. That allows you to dynamically adjust to mins before and after sunrise/sunset (each day) to maximize deep sleep? My Omlet coop is also under a tree for shade (intentionally for relief in summer) which results in me having to manually adjust the time by a few mins each day (open and close) because I cannot use the light sensor. Thanks AGAIN.
Here is my YAML - I have all my automations setup with Triggers to reduce number of individuals automations. I use the Sunrise / Sunset and offset and to update the daily schedule.
alias: Chicken Coop - Master Control
description: Handles battery alerts, nesting box notifications, and door schedules.
triggers:
- entity_id:
- sensor.temperature_humidity_sensor_lite_4_battery_state
id: low_battery
trigger: state
to: Low
- type: not_opened
device_id: 17ee1897a72173cd750eaa100ba06a12
entity_id: 165bd7f75c9219ea5ae81db2b0b9ebb2
domain: binary_sensor
id: nesting_box_closed
trigger: device
- event: sunset
offset: "-00:15:00"
id: nesting_box_still_open
trigger: sun
- event: sunrise
offset: "01:00:00"
id: nesting_box_reminder
trigger: sun
- at: "00:05:00"
id: update_schedule
trigger: time
actions:
- choose:
- conditions:
- condition: trigger
id: low_battery
sequence:
- data:
title: Chicken Coop - Low Battery
message: Temperature Sensor battery is low
action: notify.mobile_app_spacesloth12pro
- data:
title: Chicken Coop - Low Battery
message: Temperature Sensor battery is low
action: notify.mobile_app_poopphone14promax
- conditions:
- condition: trigger
id: nesting_box_closed
- condition: state
entity_id: input_boolean.nesting_box_lights_changed
state: "on"
sequence:
- target:
entity_id: scene.before_red
action: scene.turn_on
data: {}
- target:
entity_id: input_boolean.nesting_box_lights_changed
action: input_boolean.turn_off
data: {}
- data:
title: Chicken Coop - Nesting Box
message: The nesting box is now closed
action: notify.mobile_app_spacesloth12pro
- data:
title: Chicken Coop - Nesting Box
message: The nesting box is now closed
action: notify.mobile_app_poopphone14promax
- conditions:
- condition: trigger
id: nesting_box_still_open
- condition: device
type: is_open
device_id: 17ee1897a72173cd750eaa100ba06a12
entity_id: 165bd7f75c9219ea5ae81db2b0b9ebb2
domain: binary_sensor
sequence:
- data:
scene_id: before_red
snapshot_entities:
- light.hot_tub_lights_2
- light.wall_light_back_yard_2
action: scene.create
- target:
device_id:
- 1960320fe2aacd33be1d9119e8da2093
- b507769e01276f582761178c16a7d522
data:
rgb_color:
- 97
- 24
- 124
brightness_pct: 100
action: light.turn_on
- target:
entity_id: input_boolean.nesting_box_lights_changed
action: input_boolean.turn_on
data: {}
- data:
title: Chicken Coop - Nesting Box
message: The nesting box is still open
action: notify.mobile_app_spacesloth12pro
- data:
title: Chicken Coop - Nesting Box
message: The nesting box is still open
action: notify.mobile_app_poopphone14promax
- conditions:
- condition: trigger
id: nesting_box_reminder
- condition: device
type: is_not_open
device_id: 17ee1897a72173cd750eaa100ba06a12
entity_id: 165bd7f75c9219ea5ae81db2b0b9ebb2
domain: binary_sensor
sequence:
- data:
title: Chicken Coop - Nesting Box
message: Nesting Box is still closed, the girls want to lay eggs!
action: notify.mobile_app_spacesloth12pro
- data:
title: Chicken Coop - Nesting Box
message: Nesting Box is still closed, the girls want to lay eggs!
action: notify.mobile_app_poopphone14promax
- conditions:
- condition: trigger
id: update_schedule
sequence:
- target:
device_id:
- 97191a38686dabe828e147c7028df45f
- 6e4f8bf80778efc66dabca31a3c87d9e
data:
door_mode: time
open_time: >-
{{ states('sensor.sun_next_rising') | as_datetime | as_timestamp
| timestamp_custom('%H:%M', true) }}
close_time: >-
{{ (states('sensor.sun_next_setting') | as_datetime +
timedelta(minutes=30)) | as_timestamp |
timestamp_custom('%H:%M', true) }}
action: omlet_smart_coop.update_door_schedule
mode: single
I’m interested in this kind of setup, could you briefly detail how you’ve achieved it ? Is it only a matter of wiring a 12v battery to the unit, using the mains connector ?
Ideally, I’d use a solar panel to keep the battery charged and forget about the whole thing.
Thats how I solved it. Wired a 12V Battery (+ Solar Panel) to the Mains and it is running perfectly fine 
After some experimentation I have an Omlet Auto Door working as desired for my needs. I use these integrations.
- HACS dpwood/hassio-omlet-smartcoop-door
- HACS Sun2 pnbruckner/ha-sun2
I have set the Omlet door to manual mode and power it from a 7Ah 12v battery that recharges periodically. I tried a solar panel but that didn’t manage the power needs of the Omlet, so it’s recharged for twelve hours per day from a mains DC supply (on a timed HASS switch) connected to a solar charge manager.
For closing the door, I created a Sun2 entity that gives the time when the sun is next at -4 degrees elevation. This seems to be the earliest time after sunset that my girls have all come in to roost. This time changes daily throughout the year and the Sun2 calculation takes into account my geographic location and appears to handle daylight savings well. This has, in turn, been inserted into a helper sensor template that returns the timestamp for the chosen elevation.
sensor.sundown_below_horizon => {{ state_attr('sensor.home_sun_sundown_minus_4', 'today') | as_datetime }}
Because I use the same timestamp in other automations, having it in the helper means I can adjust the time in just one place if I ever need to change it; - say to -5 degrees, as the girls can cut it pretty fine coming in to roost.
So I now have a relatively simple automation for closing the door that triggers on that Sun2 time every evening. It starts ten minutes prior so it can turn on the Omlet light before closing the door.
alias: Coop Auto Door Close
description: Close coop door when sun is 4 degrees below the horizon
triggers:
- trigger: time
at:
entity_id: sensor.sundown_below_horizon
offset: "-00:10:00"
actions:
- action: light.turn_on
target:
entity_id:
- light.omlet_smart_coop_xxx_light
- delay:
hours: 0
minutes: 10
seconds: 0
milliseconds: 0
- action: light.turn_off
target:
entity_id:
- light.omlet_smart_coop_xxx_light
- device_id: c4c7xxx4110
domain: cover
entity_id: bdbxxx43
type: close
mode: single
For opening the Omlet door I have a similar Sun2 entity for the time when the sun is next at ten degrees above the horizon. That is a basic automation triggered at that time each morning. (I keep my girls in the coop until well after sunrise, once the risk of fox attack has reduced.)
I monitor the Omlet door state with a standard Zigbee door sensor, because that’s independent of the Omlet system and very reliable.
So all I need to tell the Omlet is to open or close and turn the light on or off. But I’m stuck with the webhooks and API, which means when the internet is down or the Omlet appears to be offline (which is awfully often) I can’t control the door. This is very frustrating.
I would love to be able to talk directly to the Omlet over WiFi and bypass ‘the cloud’ but can’t figure out how to do that.
2 Likes
I got the new Omlet feeder today, and encountered an issue with the integration upon adding it to the Omlet app. This may be an issue introduced at Omlet”s end, not certain. I also tried renaming the autodoor in the app, and this seemed to create another device.
@OmletDave Is there a plan to add more functionality for the feeder?
I had some time to look further at this today, and determined the issue is in Omlets library, specifically in the StateGeneral class, for variables displayLine1 and displayLine2, which I presume relate to the actual display on the Autodoor controller, which the feeder does not have, therefore the entries don’t exist in the JSON.
@OmletDave Could you please arrange to push a bug fix to address this?
Apologies for the delay, I’ve just rolled out an updated version of our Python SDK with the following changes:
- Resolved issue with handling 204 responses (thanks williamschey)
- Added support for the Feeder
- Added connected boolean into the state.connectivity class
Updates for the other SDKs coming shortly.
Thank you!
Ooooh. another new Omlet smart toy - Omlet Smart Chicken Coop Fan
Hope that is already part of the SDK/API!
Shame the fan isn’t included in the 20% off discovery day sale (25-29 Sep 2025) 
Will have to wait…
G’day @OmletDave
My two “smart” door controllers continue to work a treat, except for a nightmare that developed a few firmwares ago… the Wifi keeps dropping out,
I’ve been putting up with this for months - and I have to keep power cycling them to get them going again,.
I’ve now searched the Internet… holy mother of god, the number of people having this same problem is mind boggling.
At a wild guess it seems that if WiFi strength drops below a certain value, I’m not sure say below 50% or 40%, it seems the controller not only drops but struggles to reconnect. Sometimes you get crazy about of disconnects and reconnects, but then other times it disconnects and will then never… even if you wait a few weeks… reconnect. Turn off the power and turn it back on and it reconnects… so it’s not like there isn’t enough signal because a power cycle is enough to have it back up again for a few hours before bam, it’s gone again.
I’ve been experimenting with trying to get the controllers into a better position and it has made things better - I can go quite a few days now instead of hours before boom, they’re gone. So I’ve now experimented again and got them to around 60%, hoping that makes teh difference,.
HOWEVER… ultimately this a product that sits in your backyard. Likely the end of your backyard. By its very nature it will never have a strong signal, but it doesn’t seem to cope well with that. I feel it needs an external antenna support…
Plus… this wasn’t a problem when I first installed them, so I feel somewhere along the way with the firmware updates it has become less resilient to signal losses… which of course is normal at that distance, in fact you can see it fluctuate with every bit of wind/etc.
Hopefully there might be some improvement that can be made as this has otherwise been a fantastic replacement to my former hacks to the original non-start controllers.
And that it only fits their latest mega-sized coop, with the heat we get in Australia I’d otherwise be all over this. Unless I try and retrofit like I did to get an auto door on my nesting area.
We’re working really hard to resolve this at the moment. I believe the wifi is fine, and the issue is with the connection to our servers where it drops (for some reason we’re currently trying to determine), and then fails to reconnect as it should (again, we’re still trying to determine why). Annoyingly, none of our many control panels at the office are experiencing the issue, so it’s tricky for us to figure out the cause and validate a fix. We should have a new firmware coming soon that will help us to get to the bottom of the issue
3 Likes
So I am running HA Omlet integration Version 2025.1.4. First question, is that the latest?
Secondly, am having challenges figuring out best way to dynamically adjust the open/close time of my Omlet Coop Autodoor based on shorter daylight hours. I find myself having to constantly go into the Omlet iOS app and manually update the OPEN and CLOSE times each day to stay on top of this. If I already use HA’s built in Next Sunrise and Next Sunset values for my location, can anyone recommend an automation that would allow me to, for example, OPEN Coop Door at Next Sunrise +10 mins? So that I can can have it work based on the daylight time that changes daily? Thank you.
Thanks so much for the response @OmletDave - I’ve actually now got my two controllers dangling in a way that is not viable or safe, but now have a signal strength of around 95%. The problem is tremendously reduced - rather than many drop-outs per day I might have one and then it almost always reconnects, in fact ironically as I type this ONE of my door controllers went offline and never reconnected again for the first time since I did those last tweaks 6 days ago. Has been down almost 8 hours so I’ll have to go do that first power cycle.
It has been such a breath of fresh air to not be power cycling them repeatedly over the past 6 days - I was having to do it so often it got to the point where, as I mentioned, I left it a few WEEKS at one point and they still never reconnected again until I power cycled.
So strangely while as a programmer I understand what you are saying, I have found WiFi strength has made a big difference.
Could that in turn be affecting communications and exasperating the server connection issue you are having? Hard to say from customer end, but troubleshooting obviously goes much better with as much context as possible so thought you should be aware that I’m no longer having major difficulties except that I’ve got the controllers sitting in a completely unrealistic way to get a better signal. Not that they had an unusable one before, but they just didn’t like being anywhere near 50% or even 68% where I previously got it. 90% and higher things are super stable now.
Just a suggestion, but are you guys monitoring the number of offline devices you are seeing from your end and compiling statistics on that - eg geographic locations, percentage of devices offline, how long a device is online before it is lost, what the WiFi signal percentage was at time of loss, etc? I’m sure you’re doing everything you can it’s just that this is all data you could be logging and it might reveal why you can’t reproduce the failure as you aren’t recreating the circumstances. eg perhaps if a combination of low signal strength combined with latency from locations not within your hosting country is causing some kind of code lock that then means you loose contact and never regain.