Hello everyone, I’m reaching out to seek some guidance regarding an issue I’m encountering with my ConBee II stick after upgrading my Debian system to kernel 6.0. Previously, I had been using the ConBee II stick seamlessly with Deconz on Debian Bullseye for over three years, managing a network of Aqara temperature sensors. However, following a recent system reboot, Deconz no longer detects the ConBee II stick, despite it being physically present and recognized by the system.Upon checking the system logs, I can confirm that the ConBee II stick is detected by the kernel. The logs indicate the device’s VID as 0x1cf1 and PID as 0x0030, along with the manufacturer and product information. However, when I attempt to start Deconz with debugging enabled, I notice that the debug output repeatedly displays hexadecimal values (0x8086/0x1C26) that do not match the known VID/PID of the ConBee II stick. This discrepancy suggests that Deconz might be encountering an issue in correctly identifying or communicating with the device.I have verified that my user account is part of the dialout group, which should grant the necessary permissions to access the ConBee II stick. Additionally, I have tried restarting the Deconz service and rebooting the system to rule out temporary glitches. Despite these efforts, the issue persists.I am curious to understand if these hexadecimal values (0x8086/0x1C26) correspond to any known hardware or if they might be indicative of a driver or firmware issue. Furthermore, I would appreciate any suggestions on how to test the ttyACM0 device to ensure it is functioning correctly. Is there a diagnostic tool or command that can provide more detailed information about the device’s status and communication with Deconz?Given that this issue arose after a kernel upgrade, I suspect that there might be compatibility problems between the ConBee II stick and the newer kernel version. I am wondering if others in the community have encountered similar issues and if there are any workarounds or fixes that have been successful. Perhaps updating the firmware of the ConBee II stick or installing specific kernel modules could resolve the problem.At this point, I am keen to explore any potential solutions, whether they involve adjusting system configurations, updating software components, or reaching out to the manufacturer for support. Your insights and experiences would be invaluable in helping me get my ConBee II stick operational again with Deconz.Thank you in advance for your assistance and for sharing your expertise. I look forward to hearing from you and learning more about how others have navigated similar challenges.