Nuki Hub 9.13: Keypad Timeout Issues

by SLV Team 37 views
Nuki Hub 9.13 Frequent Keypad Timeout Errors

Hey guys, this is a breakdown of a frustrating issue some of us are encountering with the Nuki Hub, specifically the 9.13 release. We're seeing frequent "receive keypadcodes timeout" errors. Let's dive into what's happening, what we've checked, and how we might tackle this.

Understanding the Problem: Keypad Timeout

The core issue: Users are experiencing frequent "receive keypadcodes timeout" errors. This suggests the Nuki Hub isn't reliably getting the code inputs from the keypad. This is a real pain, especially when you need quick access to your door! The error disrupts the normal function of the keypad, making it difficult or impossible to unlock the door with the code.

I've checked the connection between the ESP32, Opener, and Keypad, confirming everything's stable. In the past, there were occasional Bluetooth disconnects, but the ESP32 would auto-restart. However, this "receive keypadcodes timeout" is a new beast, not seen before the 9.13 update.

Let's be clear, this is not a desired behavior. We expect the keypad to work seamlessly, especially when BLE is active and a solid connection exists. The timeout error is a clear indication something is not right, disrupting the expected operational flow. So, what can we do?

Troubleshooting Steps and Information Gathering

To help pinpoint the cause of this issue, the user has provided some essential information. This includes verification of the steps taken, such as reviewing the contributing guide, searching through existing issues, discussions, documentation, and even the chat. This initial troubleshooting helps to rule out basic problems.

  • Device Used: ESP32-S3 (Octal PSRAM). This is the specific hardware, and it is important to know which device you have, as there might be hardware-specific issues.
  • Firmware Version: 9.13, Build: 18439885128.18.1. Knowing the exact firmware version is crucial for reproducing the issue and finding potential bugs.
  • Output from /get?page=info: This gives us detailed insights into the hub's configuration, network settings, and operational status. The provided output is quite extensive and gives us a snapshot of the current configuration. This helps us see if something is misconfigured or if there's a setting that may be contributing to the problem.

From the output, we can see a lot of useful info:

  • Network: The hub is connected to Wi-Fi with a static IP. Network stability is crucial for consistent operation.
  • MQTT: MQTT is configured and connected, which is used for communication and integration with home automation systems.
  • Bluetooth: The Bluetooth settings are present, which are important because the keypad relies on Bluetooth to communicate.
  • Keypad Settings: Keypad-related settings like query intervals, code publishing, and control enablement are set, indicating that the keypad functionality is enabled.
  • Opener Settings: The opener is enabled and paired. The opener firmware version is 1.11.0, and hardware version is 4.17. Opener settings and connectivity are critical to the system's function.

Reproducing the Issue

To see if we can replicate the issue, here are the steps: Update to the 9.13 pre-compiled build, and restart. Once the hub restarts, the user observes the frequent "receive keypadcodes timeout" error.

This simple set of steps allows us to check if the problem is consistent. If we can reproduce this, it gives us a clear path for isolating the cause, which could be anything from a software bug to a hardware issue.

Expected Behavior

The expected behavior is that the keypad codes are received without any timeouts. The user correctly states that with an active BLE connection and stable connection, there should be no reason for the timeout errors. The system should reliably accept and process the code inputs from the keypad. The goal is smooth and reliable operation.

Additional Context and Possible Causes

Here are some possible causes to consider:

  • Firmware Bug: There is a possibility that a software bug is present in the 9.13 release. Sometimes new firmware versions introduce unforeseen issues.
  • Bluetooth Interference: Although the user has verified the connection stability, environmental factors such as other devices emitting radio signals, or physical obstructions could cause interference. This can lead to communication problems.
  • Keypad Issues: Less likely, but it's possible that the keypad itself may have issues. The keypad could be faulty or experiencing its own problems.
  • Hardware Problems: There could be issues with the ESP32 hardware or its connection to the Nuki Opener or Keypad.

Further Steps and Troubleshooting

  1. Check Bluetooth Environment: Make sure the environment around the Hub and Keypad is free of sources of potential interference. This could include other Bluetooth devices, microwave ovens, or other Wi-Fi devices.
  2. Keypad Battery: Although not mentioned in the report, a low battery on the keypad can cause communication problems. It's a good idea to check the keypad battery level.
  3. Logs: Examine the MQTT logs for any additional clues, such as errors or connection issues. These logs can often provide a more detailed understanding of what is going on. Enable all the debug logs if possible.
  4. Revert and Test: One of the easier steps is to revert to an older firmware version to see if the problem disappears. This could help determine if a new firmware version has introduced the problem.
  5. Contact Support: If the problem persists, reach out to Nuki support or the community channels for help. They can provide additional diagnostics and support. Provide them with all the troubleshooting steps you have taken, along with any relevant log data.

Closing the issue will be possible once the problem has been addressed. Keep in mind that troubleshooting requires time and effort, so be patient and persistent! I hope this helps you get your keypad working properly again, guys! Good luck!