Core: nello.io public api integration
Dear Home Assistant team,
we are very happy to see other smart home enthusiasts building integrations for us! Thus, we are happy to see that there is a Home Assistant integration for nello (https://www.home-assistant.io/components/lock.nello/).
I assume it was built before we had our public API ready. That鈥檚 probably the reason why it is polling our system instead of using the API. However, this may cause some some issues with your integration due to the limiters we have put in place. That鈥檚 why I would like to ask you to start using our public API instead: https://nellopublicapi.docs.apiary.io/#. We will also be happy to help in case you have any questions.
Thanks a lot.
Cheers,
the nello team
ermalguni
All 28 comments
CC @pschmitt
balloob
on 19 Dec 2018
As I remember from https://github.com/home-assistant/home-assistant/pull/18402 there is the problem that you need to use webhooks to get the event of a ringing bell.
This was the reason i've only updated to newest version of pynello using the old private API and discarded the new one.
ultrara1n
on 20 Dec 2018
Webhooks are much better supported now in home assistant. If using the home assistant cloud, it's not necessary to open up the router even.
https://www.home-assistant.io/blog/#cloud-webhooks
MartinHjelmare
on 20 Dec 2018
@ultrara1n yes, if you are using the PublicAPI you get notified via webhooks. We implemented the webhooks because our users asked for them. In what home-assistant use case would the webhooks not work anymore? Do you have any suggestion on what we can provide so that the integration would work (no guarantees on when/if we can implement it though)?
ermalguni
on 20 Dec 2018
Hi,
is there an update on this?
The version right now has a delay of 30 seconds in the event "bell_ring".
The nello support team confirmed this.
With the PublicAPI the "bell_ring" event will act in real time.
So I'm looking forward for this integration!
yan14
on 19 Jan 2019
Update on this?
snoopy12345
on 18 Mar 2019
I can help with testing, if anyone needs.
Currently I turned the integration off, as it was causing too many errors.
carloscae
on 2 Apr 2019
@ermalguni
As you can see there is not a lot of traction on the Nello component development and I wonder if maybe Nello team should contribute more directly on this. Would be also to your benefit to have one of the first manufacturer maintained component.
Meanwhile, you could provide users an interface to trigger webhooks on Nello events. That wouldn't allow users to buzz anyone in, but at least could improve the response time on bell ring events.
carloscae
on 15 May 2019
@carloscae we know that we should more actively contribute on this. Unfortunately due to us having a lack of people we rely and try to actively support(as much as we can) any community updates. I will talk internally and try to prioritise it.
On a sidenote, I will take a look on how to develop a plugin (as it is totally new to us) and take it from there. Any contributions by the community will be more than welcome.
ermalguni
on 20 May 2019
@ermalguni thanks for considering this. I'm sure the community will be happy to help. On my side, as a designer, all I can help with is testing. :)
would be great if the API would also allow setting time windows. I could imagine delivery service integrations that could talk to Nello and set those windows when a package is out for delivery, for example.
carloscae
on 20 May 2019
@carloscae our PublicAPI already supports Time-Window related actions. For more information please refer to it here: https://nellopublicapi.docs.apiary.io/#
ermalguni
on 20 May 2019
@ermalguni Those API docs seem very sparse.
codeclinic
on 5 Aug 2019
I leave this here: https://www.heise.de/newsticker/meldung/Smarter-Tueroeffner-Nello-Ab-18-Oktober-ohne-Funktion-4545084.html
tl;dr & not my language;dr: nello is shutting down their servers on 18th of October, so this gadget will be an expensive piece of home decoration.
ultrara1n
on 3 Oct 2019
Yeah. Got their email yesterday.
Startups and cloud services are always a dangerous mix.
They did say they are working on a solution so device will remain usable. But not holding my breath on it.
Email message as follows:
unfortunately we are forced to stop the operation of the nello server on 18.10., so that your nello one will only work until then. This happens against the background that we couldn't find an investor or buyer in the past 8 months, who would invest in the further development and maintenance of nello. disappointed_relieved
Therefore, insolvency proceedings for the company behind nello - LOCUMI LABS GmbH - had to be opened on 1st of October. Unfortunately, from now on we can no longer offer customer support. disappointed_relieved
Since 1st of October, the lawyer Dr. Hubert Ampferl (Nymphenburger Stra脽e 5, 80335 Munich, +49(89)30905860, [email protected]) has been appointed insolvency administrator. All insolvency claims must be submitted in writing to the insolvency administrator by 6th of November 2019.
So that you can still use your nello one, we are currently working on a solution, which we will present to you shortly. 馃
We would also like to thank you very much for your support on our way. Until the end we had hoped to achieve a better end for you and the company.
All the best,
the entire nello team green_heart
carloscae
on 3 Oct 2019
It looks like someone on the nello team is working on a self hosted solution designed for the raspberry pi. The Github account was setup the day before the announcement, and there is a shell repo for it.
codeclinic
on 3 Oct 2019
not sure it matters at this point, to be honest.
this integration didn't get much traction before, won't get it now that the company is no longer supporting or selling it.
thinking of moving to Nuki which already works locally, AFAIK.
carloscae
on 3 Oct 2019
You are right, but nuki is missing an essential function right now and that is the callback for bell ring.
The feature request in the development forum of nuki is still open and you are welcome to vote for it :)
yan14
on 3 Oct 2019
You are right, but nuki is missing an essential function right now and that is the callback for bell ring.
The feature request in the development forum of nuki is still open and you are welcome to vote for it :)
What do you mean buy callback for bell ring?
carloscae
on 3 Oct 2019
Ok. Found it. Yeah, but I guess it won't work worse than Nello which was already unusable on Hassio. I will upvote it anyway. Thanks for the tip.
carloscae
on 3 Oct 2019
I hope that it will work with a shorter delay, just because everything is operating locally.
yan14
on 3 Oct 2019
It should do, how much is really unpredictable though. It might also open up other ways to speed things up though.
codeclinic
on 3 Oct 2019
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 1 Jan 2020
It looks like Nello might be dead again. The service is patchy and there is no response from any of there support/contact channels regarding any questions put to them. Even the lost password email system seems to be out of order.
codeclinic
on 1 Jan 2020
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
stale[bot]
on 31 Mar 2020
Are any of you able to use the Nello integration? It just keeps failing for me and there seems to be no life in any of the official nello channels.
codeclinic
on 31 Mar 2020
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
stale[bot]
on 3 Jul 2020
Nello is dead.
codeclinic
on 14 Jul 2020
I also red this in News but That was a fail information. Nello is still working. So also the issue is not dead. I don鈥檛 get push notifications from nello app to my iPhone. So I use the nello integration for HA to get a message but as you know with a delay. My question. Has someone experience to use the nello API and ifttt to get informations to HA?
hubdihubdi
on 25 Aug 2020
Related issues
kirichkov
路
3Comments
Elmardus
路
3Comments
coolriku
路
3Comments
sogeniusio
路
3Comments
flsabourin
路
3Comments
Most helpful comment
@ermalguni
As you can see there is not a lot of traction on the Nello component development and I wonder if maybe Nello team should contribute more directly on this. Would be also to your benefit to have one of the first manufacturer maintained component.
Meanwhile, you could provide users an interface to trigger webhooks on Nello events. That wouldn't allow users to buzz anyone in, but at least could improve the response time on bell ring events.