Open imenawoperty opened 4 months ago
Same problem here. I load via API several codes to a keypad through the HUB, I receive a success at the webhook, but the codes doesn’t works.
I am experiencing a similar issue with my device. When I register a passcode via the API, I do not receive a webhook, but the passcode is registered in the app. However, I am unable to unlock the device using that passcode.
Every time i try to createKey on keypad i receive the following error "Device is not bound to a hub" But if i call the status (/v1.1/devices/deviceId/status) for the device it shows me that it has a hubDeviceId and it is the correct one
Please let me check if there is any progress on this issue. I'm having the exact same problem and am having trouble.
Analysis
Hello. I'm creating temporary keys on a keypad touch using an API endpoint. I have already enabled the webhook and I receive a success message for the createKey requests. The key appears in the SwitchBot app, but the device doesn't recognize the key and fails to open the SwitchBot lock. This error occurs on many devices; I have configured at least 20 devices and half of the time I encounter this problem. What is the solution?
Expected Behavior
To recognize the key when I get a success message.
Steps To Reproduce
Logs
Configuration
Environment
Additional Context
No response