home.md

@@ -3,7 +3,7 @@ All the tests were done with the zigbee-gateway-server console, version 3.1.0.
 With permit join set to enable the smart plug join the network and is added to the device list.
 The plug generates repeatedly a message of the IdentifyCluster containing an IdentifyQueryCommand and send it broadcast.
 
-I found that the library does not explicitly manage broadcast messages, so the message is received to all endpoints (by default the program creates 3 endpoints for the dongle, with different clusters on each), but, because only endpoint 1 has the Identify Cluster, when the message reaches the other endpoints an exception is thrown. The exception let the console usable but the long message that prints on the screen is annoying, so see issue #4.
+I found that the library does not explicitly manage broadcast messages, so the message is received to all endpoints (by default the program creates 3 endpoints for the dongle, with different clusters on each), but, because only endpoint 1 has the Identify Cluster, when the message reaches the other endpoints an exception is thrown. The exception let the console usable but the long message that prints on the screen is annoying, so see issue #4. This is also an efficiency issue.
 
 Also noticed that changing the permit join parameter generates an unknown package, then a warning. Analyzing the packages I think that the unknown one is only some form of notification that the status changed, in fact the unknown frame is not generated if the join command is used without changing the status (e.g. join enable when permit join is already enabled). I don't have the certainty because the command ID of the package is not on the "Z-Stack Monitor and Test API" document.