See below -:
This states that the manufacturer ID MUST carry the unique ID for the manufacturer - clearly, FFFF is not the correct ID for TKB.
The registry shows the following ID is allocated to TKB -:
While what the manufacturer says is partly correct - ie that the binding could use the command class data reported from the device, and this is what is done, that doesn’t make it a compliant product. It is also impossible to know what configuration is available without using these definitions since the device doesn’t report this, so the ONLY way to know the configuration is through the manufacturer and device type information.
I should add, that with the 800+ devices we have in the database, this is the only device that doesn’t respect this requirement.