Unfortunately it looks like a real mess (and a firmware problem from Fakro):
@chris, could we do something like:
|device|type|id|firmware|
|—|—|—|—|—|
|ZWS12|0003|0001|up to 2.0|
|ARZ|0003|0001|2.1 to 2.1|
|ZWS12|0003|0001|from 2.2|
So basically we create another device (a clone from ZWS12) and set new firmware limits.
Or we just remove 0003:0001 from ZWS12 and advise those users to contact Fakro for a firmware update (not the best option but I don’t think we should fix device firmware errors in the zwave openHAB database)