I think it’s still using the original quirk.
Personnally I had made a quirk for a LIDL light and started from the original quirk.
I renamed the main class to make a distinction in the name and appended ‘Local’:
class RGBCCTLightLocal(CustomDevice):
I called the file ‘rgbcct.py’ and it shows up like ‘rgbcct.RGBCCTLIghtLocal’:
So clearly, your quirk is not applied to the device.
What is important is that the signature corresponds to the definition returned by the firmware. In the “replacement” you’re free to define the apparent definition.
The logs can be a good place to check for errors, you could also add a LOGGER to your quirk and log a message when it enters some of the code.
You may have a basic syntax error - you could run tools such as flake8, blake, mypy to help you identify common mistakes before restarting (pip install flake8 flake8-2020 flake8-bugbear flake8-comprehensions blake mypy and run blake, flake8, mypy on your quirk).