Peter, I don’t know how else to help you, I’m sorry. Too many strange things. I should connect to your system and check myself, but now I’m leaving for vacation, so for a couple of weeks I won’t be able to help.
Joerg told me everything looked ok, but now you tell me the callback on the bridge was different respect to the LL token you configured in the secret, so I don’t know what to say. If you do everything properly, Nuki Card works.
Well, I forget to check that, when I was on his machine. But I asked him to check this later and he deleted the callback. Maybe it will work, when he is manually creating the callback, which is what I asked Peter to do.
I click on the Nuki Callback sensor in the section entities
A card opened showing the settings of Nuki Bridge callback
on the right of the card I clicked on “Verwandte”
Then I clicked on the link of the “polling qeue” link and it added a callback to the bridge.
Joerg wrote me to add the Callback manually via CURL. I think I did the same within the “system”.
Thanks for your help Joerg and Ale. If you need furthewr infos that may halp you for your great job, contact me after your holidays Kind regards Peter
The script runs everytime there’s a callback from the bridge, and it should always run when you start HA, so technically it should’ve added the callback to the bridge before. Anyway, glad you made it. I think what went wrong in your trial&error process was always the LL token, the one you configured in the secret was not the one created in HA.
Trying to set this up however can’t get callback to work. I have an error when starting HA “Invalid config for [automation]: [id] is an invalid option for [automation]. Check: automation->id. (See ?, line ?).”
The webhook is the same but there is another id also shown with url “unknown”
I removed this but it gets recreated if when the script nuki_bridge_polling_queue runs
Also you can see it states there is an “Invalid config” and the log states as I posted before
Logger: homeassistant.config
Source: config.py:437
First occurred: 15:18:18 (2 occurrences)
Last logged: 15:56:17
Invalid config for [automation]: [id] is an invalid option for [automation]. Check: automation->id. (See ?, line ?).
Tried that but it just recreates a new one with url “unknown”
I can’t understand why I also have the Invalid config warning. I downloaded the nuki_card_callback.yaml and copied it directly in to the packages folder, so I know it hasn’t been altered or corrupted in any way
hi everyone, I’m getting mad because “Nuki Bridge CallBack” appears “unavailable”
I’ve configured in secrets.yaml:
nuki_bridge_url: “http:// My Nuki Bridge IP:8080”
nuki_bridge_token: “Nuki Bridge token”
nuki_bridge_webhook: “long life token that I’ve generated”
nuki_ha_internal_url: “http:// My Raspberry IP:8123”
After I’ve created the packages folder and uploaded the document “nuki_card_callback.yaml” that Alex gave us on GitHub.
At the end I’ve included packages in config.yaml
What am I doing wrong? Should I modify something in the file “nuki_card_callback.yaml”??