You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -397,7 +397,7 @@ replacement = {
397
397
398
398
You can see that we have replaced `ElectricalMeasurement.cluster_id`from endpoint 1in the `signature`dictwith the name of our cluster that we created: `ElectricalMeasurementCluster`and on endpoint 2 we replaced `AnalogInput.cluster_id`with the implementation we created for that: `AnalogInputCluster`. This instructs Zigpy to use these `CustomCluster` derivatives instead of the normal cluster definitions for these clusters and this is why this part of the quirk is called `replacement`.
399
399
400
-
Now lets put this all together. If you examine the device definition above you will see that we have defined our custom device, we defined the `signature`dict where we transcribed the `SimpleDescriptor` output we obtained when the device joined the network and we defined the `replacement`dict where we swapped the cluster ids for the culsters that we wanted to replace with the `CustomCluster` implementations that we created.
400
+
Now lets put this all together. If you examine the device definition above you will see that we have defined our custom device, we defined the `signature`dict where we transcribed the `SimpleDescriptor` output we obtained when the device joined the network and we defined the `replacement`dict where we swapped the cluster ids for the clusters that we wanted to replace with the `CustomCluster` implementations that we created.
0 commit comments