SpaceMouse Wireless BT Edition bricked after 10.8.7 update or preexisting hardware issue?

[llealloo]

This morning I turned on my computer to find that my SpaceMouse Wireless BT Edition had become unresponsive. I have already contacted support with the following message:

Sadly, my SpaceMouse Wireless BT Edition stopped working today. I can not get it to turn on/connect/show LED lights. It is totally unresponsive and will not accept charge.

Preface: I have been having some USB issues over the last month on my mac laptop:

- macOS lockscreen would repeatedly flash on when the screen would attempt to sleep, it seemed like a USB device kept waking up the computer
- macOS notifications began to appear about 3 days ago "USB device disabled for drawing too much power"

I installed the latest update for macOS: 3DxWare 10.8.7 2 days ago, and the device continued to function same as before.

Then today, my SpaceMouse Wireless BT Edition became unresponsive.

I have tried:
- plugging in SpaceMouse with included usb-c cable to different computer (PC - Windows 11)
- plugging in SpaceMouse with different [known working] usb-c cable to different computer (PC - Windows 11)
- plugging in SpaceMouse with different [known working] usb-c cables to the macOS computer
- plugging in SpaceMouse with different [known working] usb-c cables to various [known working] usb charging bricks (no lights showing charging)

Sadly, it seems like my device has had an internal hardware failure with its USB controller or charge controller, or maybe it has become "bricked" by the recent update?

Are there any known procedures to do a hard reset of the SpaceMouse device that might un-brick it? I think this is more likely a hardware problem than related to the update, but figured I would ask here just in case anyone has any ideas.

[llealloo]

Support is processing a replacement for my SpaceMouse Wireless BT Edition.

I have a feeling this was not related to the latest update because I was already having USB issues predating the driver update (hopefully it was just a preexisting hardware issue).