A quick update: my Onyx2 is reporting that it has firmware 1.6, and that it’s up-to-date. This could mean that you have a hardware revision that we’ve not seen yet.
Whilst I suspect that the protocol will not have changed, I’d love to test before making any changes.
If you happen to have an Android phone, nRF Connect will let you see the service and characteristic UUIDs of your Onyx, if these match the ones from the original Onyx2, then we can try sending it the same commands and see how it reacts.
The service UUID should be f60402a6-0293-4bdb-9f20-6758133f7090
Which should have these characteristic UUIDs:
If that all looks right, send 0x00 (byte) to c7b7a04b-2cc4-40ff-8b10-5d531d1161db.
Then send [ 0x60 0x32 ] to 02962ac9-e86f-4094-989d-231d69995fc2
Then send [ 0x03 0x32 ] to 02962ac9-e86f-4094-989d-231d69995fc2
If this all works right, the Onyx should “move” at half pace from one extreme to the other.