Tuya TS0601 TRV force not available as 'select' entity in HA any longer

[kds69]

What happened?

Since quite some releases (since 2021?), the "select.xxxx" entity for TRV force is not created in HA any longer.
This is removing the very useful capability to force valve and TRV mode with a select option in HA. For instance when PID is too slow to close or open valve and user would like to force it.
We can of course use as a workaround the publishing of "force" mqtt messages, but this is not integrated with HA directly.

What did you expect to happen?

Looking into homeassistant.ts, I presume when force is found for the exposed attribute it should be a set as {entity_category: 'config', icon: 'mdi:valve'} instead of the below

 else if (firstExpose.type === 'enum') {
            const lookup: {[s: string]: KeyValue} = {
                action: {icon: 'mdi:gesture-double-tap'},
                ...
                force: {enabled_by_default: false, icon: 'mdi:valve'},

and strangely, below code doesn't kick in:

            if ((firstExpose.access & ACCESS_SET)) {
                discoveryEntries.push({
                    type: 'select',
                    object_id: firstExpose.property,
                    mockProperties: [], // Already mocked above in case access STATE is supported
                    discovery_payload: {

How to reproduce it (minimal and precise)

Same behavior for at least this very common version: _TZE200_cwnjrr72 of TS0601

Zigbee2MQTT version

1.33.1-1

Adapter firmware version

20220219

Adapter

zzh!

Debug log

N/A

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days