Tuya light sensor doesn't expose sensor entities

[silver beacon]

I just picked up a Tuya luminance sensor and configured it through ZHA. It's mains-powered (USB), so it makes sense that it doesn't have a battery readout, but it also doesn't expose the luminance value. Confusingly enough, when hitting reconfigure, it appears to show that it should. I'm fairly new to this, is there anything I need to do to expose this, or better yet, anything I can do to help resolve this in HA for future users of the same device?

EDIT: And to be clear, it's not a disabled entity either. Only LQI and RSSI are.

Found my way to this, but I'm still not sure what to make of it re: getting a working sensor.
https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts0601_illuminance.py

[native nebula]

Hi@silver beacon,
Indeed you can work with quirks to fix that.
If you are looking at how to use the quirks, https://community.home-assistant.io/t/zigbee-guide-how-to-setup-local-custom-device-handler-quirks-in-zha-integration/683473.
Has a discussion about it.
There are also at least 3 custom integrations that work with Tuya devices, that's how convoluted Tuya stuff is.
The 3 I know about are all located in GitHub from different authors. You can get to them that way or using HACS to install them.
Personally I use the core one and live with the missing stuff because Tuya stuff is,... special.

[silver beacon]

While that's useful information in general, it looks like the quirk is already active, which leaves me at a loss for why it's not showing the relevant information.

[native nebula]

Restart HA after you make sure your config check passes?

[silver beacon]

Aha. Didn't try a restart. Sure enough, it works now.

[native nebula]

🧊 🫘

[jolly creek]

All quirks in the zha-device-handlers repo are included in ZHA by default.
There's a bug with Tuya devices at the moment where the entities won't appear until HA has been restarted. It should be fixed in the next major HA version.
If you can, try uninstalling the custom quirk again, restart HA, and see if the device still works.

Keeping custom quirks installed permanently is not recommended at all, as they can break with every HA/ZHA update.

And if the quirk directly came from the GitHub repo source, it's already included in HA (or will be in the next major version).

[silver beacon]

I skipped creation of a custom quirk because I could see that it was already active. As you said though, I ran into the issue that it wasn't functional until after a reboot. I do appreciate the advice though.