lwestenberg
Unable to add Bold lock to Home Assistant
Hi folks, thanks for your help in advance for this one.
My Bold device stopped working in Home Assistant today. I deleted them, deleted the HACS repo, redownloaded it (2ca295d) and tried to re-add my lock.
I complete the code and sign in on the Bold side, but when it passes back to Home Assistant I get the below error.
Oops... an error occured Unexpected response Too Many Requests
Screenshots below. Is there any further information I can provide that might help with troubleshooting this?
Many thanks,
James.
Hi James,
Sounds like some issues at Nabu Casa. Have you tried all the steps on a later time?
Seems like again an issue with the bold servers, same issue here since today. This happened several times last months
Same problem here! But I don't use Nabu Casa, I'm using a standalone version (accessible from own subdomain).
I was able to setup a previous version...
Best regards, Thomas
Hello everyone! I too have the same problem since yesterday! All attempts to reinstall it have so far been futile! I don't use nabucasa but cloudflair if it helps.
Nabu Casa is used as an authentication broker between your installation and Bold. (for everyone)
So, probably there are problems with Nabu Casa and/or Bold.
Alright. Will try later on (still not working)…
In case of, I’m also behind Cloudflare…
I've contacted Bold and indeed; they ratelimit their OAuth service (for a good reason!), but all the authentication comes from Nabu Casa (same IP-address, over and over again), and therefor hitting the threshold.
Nabu Casa doesn't have any back-pressuring (yet?), and therefore retrying the rate-limited request, which makes everything worse :)
TLDR: Bold, Nabu Casa and I are currently brainstorming for a short and long term solution.
Thank you for the update.
It sounds to me that previous version was Nuba Casa free. Am I wrong?
Would it be possible to have an (advanced user) option to bypass Nuba Casa and get the OAuth done directly by the Internet accessible HA instance?
Technically, yes. But then each use has to register its own application with Bold, etc.
Now the App-secret is with Nabu Casa, allowing everyone to authenticate via Nabu Casa, without signing-up with Bold.
BTW: This is completely separate from the paid Nabu Casa service.
Alright. I think that I got it.
You mean that now that Bold opened its app to third party app, we have to get the 3rd party registred by Bold to be able to create a link.
Before, it was emulating the app connection and then was not implementing the 3rd party API mechanisms.
Then I have 2 questions:
- having the link with Nabu Casa created means that anyone linked to NC can access to my Bold locks? Or NC is just acting as a proxy and only my HA instance is linked?
- is it difficult to get MyApp registred at Bold or just some HTTP requests?
Thank you for your appreciated support.
- having the link with Nabu Casa created means that anyone linked to NC can access to my Bold locks? Or NC is just acting as a proxy and only my HA instance is linked?
Nope, it's just an authentication broker and the callback goes directly to your HA-installation, and the actual API-requests directly to Bold.
- is it difficult to get MyApp registred at Bold or just some HTTP requests?
Yes, they don't accept this, that's why we use Nabu Casa as an authentication broker.
Nothing special, nothing fancy. It worked before, and will work soon again (as we are working on a solution).
Short-term solution will probably; allowing temporarily Nabu Casa without rate-limit or with a much higher rate-limit Long-term solution will probably; prevent all HomeAssistant Bold-integration hitting many times the OAuth server ;)
This integration is getting more and more popular, and therefore hitting new thresholds/rate-limits. In the end everything will get better ;)
Hi folks, thanks for your help in advance for this one.
My Bold device stopped working in Home Assistant today. I deleted them, deleted the HACS repo, redownloaded it (2ca295d) and tried to re-add my lock.
I complete the code and sign in on the Bold side, but when it passes back to Home Assistant I get the below error.
Oops... an error occured Unexpected response Too Many Requests
Screenshots below. Is there any further information I can provide that might help with troubleshooting this?
Many thanks,
James.
same happening to me.
@tim427 Many thanks to you and everyone for your efforts and time invested. I really appreciate that!
Oh, I don't know if that's appropriate now, but the lock also has a battery status, is it planned to show this as an entity in HA?
As a temporary solution Bold killed the OAuth for a while, so the rate-limit shrunk; everything should work now.
When I'll have some time, I'll try to add some back-pressuring on this integration.
PS: also the the translation of "battery status" is on my roadmap :)
Thank you very much, the registration also worked for me again without reinstallation. All door locks can be operated
Hi everyone,
Unfortunately, I have the issue. I cannot say if appreared long time ago or these to last days (I have not played with HA for weeks). I juste restarted HA few times today, and it could explain this status...
It is still working fine for you ?
@Golgautier - yes, my door still unlocks. I've not tried removing and re-adding the integration though I'm afraid.
Mine are still working. On 7 Aug 2023, at 13:51, Gautier LEBLANC @.***> wrote: Hi everyone, Unfortunately, I have the issue. I cannot say if appreared long time ago or these to last days (I have not played with HA for weeks). I juste restarted HA few times today, and it could explain this status... It is still working fine for you ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Arg... It is strange...
Actually I am surprised that all authentication request comes from Nabu ? Why the HA server does not do it by itself ?
Arg... It is strange...
Actually I am surprised that all authentication request comes from Nabu ? Why the HA server does not do it by itself ?
I'll qoute myself;
Now the App-secret is with Nabu Casa, allowing everyone to authenticate via Nabu Casa, without signing-up with Bold.
Otherwise every HA installation requires it's own OAuth App secret, callback URL, etc. etc. -> Bold will not provide this, as the administration will be grow exponentially. Nabu Casa has a OAuth proxy for many years and is exactly solving this issue (and works for a lot of different integrations). So the only thing we still need to do; a back-pressuring system.
Feel free to create a pull request ;)
Oh no oh no oh no! This afternoon we found out that the locks cannot be operated again! The error message from nabucasa comes again. Please don't tell me it's just me :-/
Me too 😩Sent from my iPhoneOn 8 Aug 2023, at 17:02, zumheulen @.***> wrote: Oh no oh no oh no! This afternoon we found out that the locks cannot be operated again! The error message from nabucasa comes again. Please don't tell me it's just me :-/
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
I have contacted nabu casa and raised the issue. I have updated my review on Amazon to warn other potential home assistant purchasers of these locks. I can’t understand why Bold are not working on a full native implementation. It really is a pain in the ass and I’m tempted to just sell my locks and connects and look for another solution 😩
When I contacted bold, they simply point you to this custom integration. Not good enough for a company to not actively look to enhance their products.
As good as the product is, smart doesn't stop there "for me", only with its own app ec. to run. Bold should be ashamed not to be actively involved here. If my family and I didn't find these motorized locks like the Nuci so ugly and noisy, I probably wouldn't have gotten the Bold. But it's small, rugged, quiet, stylish and we've color matched it by powder coating it.
@plasterer41 and @zumheulen this integration has nothing to do with the company Bold and/or Nabu Casa.
Please understand this plugin/integration is still in an unofficial state (not in HomeAssistant yet, but via HACS) and currently only developed by me and @lwestenberg
Both of us have full time dayjobs, etc. If you want to speed things up; feel free to contribute by creating a pull request.
Otherwise; please be patient, we are working on it (in our free time).
If this problem is fixed (and some extra features are added), we are planning to make it an official integration within HomeAssistant.
Sorry if that came across as blaming you. I understand that very well and you have the greatest respect for this work, which should actually be Bold's job because this company wants to sell its "smart products". Who as a provider today the alternative market was ZB. Homeassistant refuses, I think he will lose the race. After the chts nevertheless, thank you very much for your work. I/we will continue to provide feedback here if desired. Best regards
Totally agree with you!On 9 Aug 2023, at 09:26, zumheulen @.***> wrote: Sorry if that came across as blaming you. I understand that very well and you have the greatest respect for this work, which should actually be Bold's job because this company wants to sell its "smart products". Who as a provider today the alternative market was ZB. Homeassistant refuses, I think he will lose the race. After the chts nevertheless, thank you very much for your work. I/we will continue to provide feedback here if desired. Best regards
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>