Quirks V1 equivalent to V2's switch, number, enum, etc?

[ekaszubski]

My understanding of quirks in general is that they assist in mapping manufacturer-specific functionality, like non-standard attribute IDs, onto, at a minimum, standard types like uint8_t. They also assist in constraining those mappings to specific cluster IDs (typically also manufacturer-specific).

There also appear to be some rules as to when home assistant entities are created for a given attribute; "standard" clusters like OnOff seem to have entities created automatically, but custom clusters and attributes don't appear to have any entities created even when mapped to a standard type like uint8_t, presumably because the value stored in that uint8_t could be 0/1 = on/off (switch) , or a set of modes e.g. 0/1/2 = mode1/mode2/mode3 (select), etc.

Quirks V2 seems to solve this via .switch(), .number(), .enum(), etc, which appear to help define the mapping from the manufacturer-specific values defined in the quirk's replacement clusters onto standardized home assistant entities like switch, select, number. What is the equivalent functionality for Quirks V1, i.e. how can I ensure that a specific kind of home assistant entity is created for a manufacturer-specific attribute using Quirks V1?

[Hedda]

• How to actually write a quirk - a complete(?) guide #4339

[ekaszubski]

Thanks for the response but I don't understand how this helps to answer my question. I asked essentially "I think I have an understanding of how X works and how to do it in quirks V2; but how do I do it in quirks V1?" You linked me to what appears to be a guide for writing quirks in quirks V2, which is great, but I don't see anything there that helps to answer my question specifically about quirks V1.

[Hedda]

Sorry I missunderstood, but fact ks that Quirks v1 is in the processor being completly phased out, so why do you want to write a quirk v1 now?

I read that zigpy/zha devs are looking to sooner rather than later convert all existing v1 quirks to v2 quirks so chances are they will not longer accept new submissions for thise using the old quirks v1 standard.

[ekaszubski]

The note about V1 being phased out is appreciated, but asking "why do you want to write a quirk v1 now" is really unhelpful to everybody. Plenty (most?) of the existing quirks are in the V1 format as far as I can tell. Information about the V2 format is hard to find, particularly examples of converting from V1 to V2, and what does exist is lacking in detail and/or description. Until every existing quirk has been converted to V2, and until more extensive documentation of V2 exists, knowing how to do things in V1 is still very relevant. A "rosetta stone" example that shows how to translate between the APIs would be extremely useful.

Again, I'm just asking for somebody to please point me to a V1 quirk that does the same thing as V2's switch(), number(), or enum() so I can learn some more about how these APIs work. Alternatively, if you're aware of some quirks that have already been converted from V1 to V2 that use this functionality, can you please point me to them so I can just look at the before/after conversion diffs?