Marcel van der Veldt

Valid point but do you plan to keep support of multiple integrations ? Or keep it side-by-side for a while and EOL the old implementation ? Good to know the...

@Fishwaldo will the ValueIDKey be the same when migrating from 1.4 to 1.6 ? Or is this something generated by OZW itself and not from the actual hardware/mesh ? If...

## identifier for device in device-registry **current implementation:** first node_instance: `identifier = (DOMAIN, node_id, node_name)` if node_instance > 1: `identifier = (DOMAIN, node_id, instance, node_name)` `node_name = node.name or f"{node.manufacturer_name}...

## unique id for entities **current implementation:** `f"{node.node_id}-{value.object_id}"` value.object_id == primary value valueid_key [Link to code](https://github.com/home-assistant/core/blob/b4083dc14ffaad77f55a174ad05b6355b045eaab/homeassistant/components/zwave/__init__.py#L1328) __________________________ **zwave_mqtt implementation** `f"{self.primary.node.id}-{self.primary.value_id_key}"` [Link to code](https://github.com/cgarwood/homeassistant-zwave_mqtt/blob/master/custom_components/zwave_mqtt/entity.py#L135) __________________________ So assuming the ValueIDKey status/is the...

@balloob @MartinHjelmare I worked out some details for the migration path, see my comments above. You guys are more familiar with the device and entity registry but this sounds perfectly...

Yeah, that would be even more safe. I’m not sure how big the chance is to have the same ValueIDKey on multiple instances, let alone with matching node id

OK, we might be in luck in that case as the old implementation did not use (or generate entities for) 2, 3 and 4. As for item 1 we'll have...

Hi could you please create a MQTT dump and upload it here ? That way we can test/debug with your exact device config which makes life much easier for us....

The 2nd instance on these Fibaro dimmers is indeed used for associations. You can for example control an associated light (or group of lights) with the second wall switch. I...

BTW: Just as an FYI, this Instance 2 behaviour also exists in the current Z-wave implementation.