Also experiencing this issue, running [hueemulation] with OpenHAB v3.3.0. Out of my 42 exposed lights, only 30 items with unique IDs that end with a value under ‘-FF’, or numeric unique IDs of 1-99, are discovered by Alexa. Per my research, this isn’t really a bug but rather a change to how Alexa handles discovery. There were other breaking changes in the past, such as needing 9 Octets in the Bridge ID, reference this related GitHub Issue (habridge):
https://github.com/bwssytems/ha-bridge/issues/1325
Digging into the Openhab Hue Emulation code, I believe this function is the culprit of the problem. This ‘unique’ variable should be a sequence of only 2 characters, and as you noticed only use letters A-F when generating the unique ID.
To work around this, I attempted but failed to find where these values are stored. In habridge, there is a device.db file that can be directly edited, but in Openhab it seems these values are stored in JSON DB, and would require some openhab-cli console fun to find and change…
To confirm its not so much of a problem with hueemulation addon, but rather Alexa Device Discovery, I downloaded ‘Hue Essentials’ from Google Play, which finds and controls ALL of my Openhab exposed items correctly.
Any ideas on how to work around this?