Beacon spam not working

[moumouhdupro]

Describe the bug:
the beacon spam feature doesn't work with the latest version of Bruce and Beta, but work with the 1.14.

• Device used: Lilygo T embed cc1101 Plus with external antennas

[henkefelix88-blip]

Multiple issues on LilyGO T-Embed CC1101 Plus (External Antenna)

Board

• LilyGO T-Embed CC1101 Plus (External Antenna)
• Purchased from the official LilyGO store

Firmware versions tested

• Bruce v1.14
• Bruce v1.15
• Latest beta

The same issues occur on all tested versions.

Host

• Windows 11

HID / BadUSB Issue

All HID-based functions fail on Windows with Code 10.

Windows reports:

The HID report descriptor validation failed. A top-level collection in a complex device (more than one top-level collection) had no declared report ID, or a report ID spanned multiple collections.

Device Manager:

• Driver: input.inf
• Service: HidUsb
• VID: 303A
• PID: 0002
• Problem Code: 0xA
• Status: 0xC00000B9

Tested

• USB Serial (CDC): ✅ Works
• USB Keyboard: ❌ Code 10
• USB Mouse: ❌ Code 10
• BadUSB: ❌ Same Code 10

The same board works correctly on an iPad, but Windows rejects every HID interface.

I also tested:

• Different USB cables
• Different USB ports
• Reinstalling the device
• Reflashing Bruce v1.14, v1.15 and the latest beta

None of these solved the problem.

---

NRF24

The NRF24 functionality does not work at all on my board.

I have not been able to get any NRF24 feature working.

---

General experience

Besides the HID issue, I have experienced several other problems on this board.

Overall, many features appear to be unavailable, unstable, or not functioning as expected. Compared to the advertised capabilities, the firmware currently feels very limited on the LilyGO T-Embed CC1101 Plus (External Antenna).

I am not sure whether this is caused by my specific hardware revision or by incomplete support for this board.

---

Possible cause

Since USB CDC works correctly but every HID interface fails, the USB hardware itself appears to be functioning.

The Windows error suggests that the HID report descriptor may not be fully compatible with the Windows HID parser (possibly missing Report IDs or invalid top-level collections).

If additional logs or testing are needed, I would be happy to provide them.

[Ninja-jr]

Well we are trying to fix a few issues introduced on 1.15 im sure some will be looking specifically into it. I've more been looking into the ble issues and wifi deauther but some have already been trying to solve the others