Hardware:
Guition ESP32-P4 with ESP32-C6 (WiFi co-processor)
Firmware:
NukiHub 9.14 → problematic
NukiHub 9.13 → works stable
Description:
After flashing NukiHub 9.14, the device is able to:
scan for WiFi networks
connect to the configured SSID
successfully obtain an IP address via DHCP
However, shortly after obtaining the IP address, the device crashes and reboots.
This results in a continuous reboot loop.
Relevant log excerpt:
[WiFi-event] event: 112
Connected to access point
[WiFi-event] event: 115
Obtained IP address: 192.168.x.x
rst:0xc (SW_CPU_RESET)
After reboot, the same sequence repeats.
nukiHub.log
Expected behavior:
Device should remain connected and operational after obtaining an IP address.
Actual behavior:
Device crashes (SW_CPU_RESET) a few seconds after successful WiFi connection.
Additional observations:
Same hardware and WiFi configuration works perfectly with version 9.13
Issue occurs across different WiFi networks (mesh, IoT network, hotspot)
Full flash (erase + manual flash via esptool) was performed
Conclusion:
This appears to be a regression in version 9.14, likely related to ESP32-P4 + ESP32-C6 (ESP-Hosted WiFi).
Workaround:
Downgrading to 9.13 resolves the issue completely.
Hardware:
Guition ESP32-P4 with ESP32-C6 (WiFi co-processor)
Firmware:
NukiHub 9.14 → problematic
NukiHub 9.13 → works stable
Description:
After flashing NukiHub 9.14, the device is able to:
scan for WiFi networks
connect to the configured SSID
successfully obtain an IP address via DHCP
However, shortly after obtaining the IP address, the device crashes and reboots.
This results in a continuous reboot loop.
Relevant log excerpt:
[WiFi-event] event: 112
Connected to access point
[WiFi-event] event: 115
Obtained IP address: 192.168.x.x
rst:0xc (SW_CPU_RESET)
After reboot, the same sequence repeats.
nukiHub.log
Expected behavior:
Device should remain connected and operational after obtaining an IP address.
Actual behavior:
Device crashes (SW_CPU_RESET) a few seconds after successful WiFi connection.
Additional observations:
Same hardware and WiFi configuration works perfectly with version 9.13
Issue occurs across different WiFi networks (mesh, IoT network, hotspot)
Full flash (erase + manual flash via esptool) was performed
Conclusion:
This appears to be a regression in version 9.14, likely related to ESP32-P4 + ESP32-C6 (ESP-Hosted WiFi).
Workaround:
Downgrading to 9.13 resolves the issue completely.