How long do the batteries last on the new wifi one? Also is the new controller able to be bought on its own and used with an exisiting omlet auto door by changing out the controller?
Wonderful! I’m one of the people who reached out to your support team to encourage them to make the API accessible to devs. It’s good to hear that you are receptive to this feedback and reinforces that I made the right choice buying the Omlet Door. One other request – please allow for local control of the door if possible. That will allow Home Assistant to continue controlling the door even if there are internet connection issues.
Regarding the battery issue, one option I considered was purchasing a rechargeable 6V lantern battery with a trickle charger. You can find various options on Amazon that come with both the battery and charger (e.g., Amazon.com). I haven’t tested it out, but thought it might be a nice option.
Alternatively, could you create a version of the board that has the needed diode to switch between battery and mains, but add jumpers that we can use to enable/disable the diode? That will allow users the option of whether they want battery backup vs. better battery life? For now, I plan to just put in batteries when I will be out of town but use mains otherwise.
Hi All,
I’m pleased to say our developer section is now available on our Smart Knowledge base. You’ll find API documentation, and client libraries / SDKs for PHP and Typescript.
If you log in with the same details you do on the app you’ll be able to generate an API key to use, and also setup webhooks to be notified immediately of events from your device.
Really excited to see what people build with this, as I said before we always imagined this new “Smart” project as a way to enable our customers to customise the door so that it works the best for them. We’d really appreciate any feedback on the API and client libraries you might have so we can make them as useful as possible.
To pick up some of the other questions:
Battery life for the new smart control panel is 2+ months when using the smart functionality, and 6+ months if you have wifi disabled (similar to the previous non-smart panel)
You can indeed purchase the new control panel on its own to upgrade an existing door, there should be a link on the main product page to take you to the standalone control panel
Local control might be tricky with the architecture we currently have, but I’ll make a note of the request and see if this is something we want to / can add for a future release
As you say, some kind of switch to connect / disconnect the diode may be a solution for the future. It’s definitely on our list of most requested features, and we will be considering it again should we make any future revisions to the board. It wouldn’t be the simplest modification to make to the board yourself if you wanted to, but it’s not impossible to do if you know your way around a soldering iron
5 Likes
Awesome on the release of the APIs! I did have a question about connecting this potentially to our own mqtt servers for local only control? It’d be nice to have my servers talk directly to the door for control.
Connecting to a local MQTT server is not on the roadmap currently, but I’ve made a note of the request for us to review in the future - I can’t promise anything at this stage though
1 Like
Just want to jump in here as I know Omlet well and love what they are doing. I also love HA very much although I’m a relatively new user. We work in the embedded space and have a lot of background working with MQTT and so forth. Lots of my setup here involves Tasmota / ESPHome / MQTT and we do a lot with NodeRed to wire things up.
So just to say - would be super pleased to be involved in this conversation and/or any testing.
Cheers!
Alex Lennon
Quick update from us - we’ve just published the Python SDK into our developer section
3 Likes
Guess I can replace this sister board I created now!! Very exciting to see this being done officially.
Local API would be nice. Mine uses local MQTT. I also added a low power mode which disables the WiFi, just polls every 5 mins to see if it should resume. Kicks in automatically if voltage is low, however with a 12v battery + solar it’s really just a fail safe. I’m sure the official board is a lot more efficient.
You have to get a completely new control panel. Smart Autodoor Control Panel | Omlet I just swapped mine over. It’s nice not to have to replace the door too.
Anyone got the new one working in home assistant yet, just ordered the new smart controller.
I replaced the old controller with the new one. For now, it works well.
In waiting for a home-assistant integration 
1 Like
Thank you for this! Just an FYI - actions currently appear to be broken, probably because of the duplicate ‘/’ in the generated URL:
>>> omlet.perform_action(devices[0].actions[4])
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.10/dist-packages/smartcoop/api/omlet.py", line 23, in perform_action
self.client.post(endpoint)
File "/usr/local/lib/python3.10/dist-packages/smartcoop/client.py", line 25, in post
response.raise_for_status()
File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://x107.omlet.co.uk/api/v1//device/NYy4bGOvAvD7bweC/action/off
Hi Nick,
Thanks for flagging that, I’ve just uploaded a new version with a patch for that issue. Let us know if you spot any other issues
2 Likes
That was fast - thank you!
One other thing I’ve noticed is that authentication errors aren’t handled well; if I try and access the API with an invalid auth token, I get a generic error about parsing JSON; presumably because you’re not checking the HTTP status code, and the 403 response isn’t JSON-formatted.
I’ve checked that issue, it looks like the 401 behaviour on the server side was mistakenly changed recently. We’ve reverted that back which should resolve the JSON parsing error you were seeing.
I’ve also pushed a new version with a couple of minor changes - a few of the URLs had superfluous trailing slashes, which would have resulted in 302’s and a second request being required. I’ve also added response status code checks on API calls that don’t do anything with the responses, so that any errors are flagged to the user
2 Likes
I came here expecting to have to raise a feature request for Omlet Smart Auto Door integration - I should have known better!!! 
@OmletDave - thank you for being so engaged with the community, and building the Smart Auto Door from the ground up with 3rd party integration in mind. You’ve really made me feel so much better about investing in an Omlet Auto Door a few months ago! You are a real credit to Omlet brand ambassadorship!
Knowing that it won’t be long until this community comes up with an integration, I need to re-prioritise getting power run to my coop so that when I upgrade to the Smart controller, I can switch from battery to 12V power for the more reliable experience!!!
1 Like
EDIT: This is not my code! just found this on the internet. No credits to me.
3 Likes
Have you figured out how this code works and needs to be setup, doesn’t look like it has any documentation.
I like the way Omlet is going with their smart control panel. I switched my own-upgraded control panel (I used a Shelly Uni) for the new Omlet panel, because this allows me to check the state of the door instead of simply mimicking button pushes.
I quickly encountered some practicalities that I would like to translate to feature requests. Note that I am using the daylight sensor to control my door.
(1) When closing the door manually during the day, I would like it to stay closed until I manually open it, or until the next opening cycle after night. Some use cases: (1) I might want to clean out the coop and keep the chickens out. I noticed that if I closed it manually, it automatically reopened after the time delay (20min?) because of course… there was daylight. Another case would be when the chickens are in their coop early for some reason and I want to close it until the next morning. As in the previous example, the door might reopen if there is still enough light.
(2) Relying on the daylight sensor is sometimes tricky: finding the proper values, coping with rainy days, etc… When I used my own Shelly to control the ‘dumb’ control panel, I actually set it to open and close based on a setoff time to the actual sunset and sunrise (within the Shelly Uni itself). This way, I never had issues with those rainy days and my chickens were always safe in their coop. It happened before that the chickens were chilling underneath the coop, out of the rain, and the door closed (early) for the night.
Hoping to see these through some future firmware updates.
Thanks and keep up the good work!
1 Like
Tried copying the files to cucstom component folder but not sure how to configure it in the config file and set up from ui doesnt work.
Doesnt looks like the developer is very active on github prob made for himself and then never looked at it again shame.