Hi there,
I am using EM357 module for installing a gateway on openhab. It is able to open network and my node is also finding it. But It is unable to pair. Same module is working fine on cygwin. I am unable, understand what is happening. Is gateway is not permitting to join?
node_pairing_log.txt (2.7 KB)
This is my node terminal data.
It looks like the device has joined and is in the inbox, so the problem is likely elsewhere. You don’t really provide a lot of information - what is the device? What version of the binding are you using? What is the dongle?
I don’t know what you have used to generate this log? Is it from the Silabs CLI? It would be more useful to provide a binding debug log.
All devices are from Silabs.
Device is EM357 zigbee gateway module.
Binding version is 2.4
This what i get is from karaf window, when I opened network for pairing.
karaf_pairing.txt (37.4 KB)
This what i getiing is node side data which is displayed during scaning mode on UART
sim_data_karaf.txt (2.7 KB)
Please can you advise what the device is that you are trying to join? There are a couple of nodes joined your network - have you looked at the logs? What are these devices?
//------------------------------------------------------------------------------------------------------
NWK Steering State: Scan Primary Channels and use Install Code
Error: NWK Steering could not setup security: 0xB7
NWK Steering State: Scan Secondary Channels and use Install Code
Error: NWK Steering could not setup security: 0xB7
NWK Steering State: Scan Primary Channels and Use Centralized Key
Starting scan on channel 11
NWK Steering: Start: 0x00
Join network start: 0x00
NWK Steering joining 0x43AA
EMBER_JOIN_FAILED
Starting scan on channel 14
ZllCommStackStatus: status = AF, flags = 00
Starting scan on channel 15
Starting scan on channel 19
Starting scan on channel 20
Starting scan on channel 24
Starting scan on channel 25
NWK Steering State: Scan Secondary Channels and Use Centralized Key
Starting scan on channel 18
Starting scan on channel 19
Starting scan on channel 20
Starting scan on channel 21
Starting scan on channel 22
Starting scan on channel 23
Starting scan on channel 24
Starting scan on channel 25
Starting scan on channel 26
Starting scan on channel 11
NWK Steering joining 0x43AA
EMBER_JOIN_FAILED
//----------------------------------------------------------------------------
I am using MGM13p zigbee device from silabs, basically it is the type of Light switch.
And their is no two of device connected. It is one device which is not paired completely.
Currently there is very little for me to go on - sorry. I see a couple of nodes that the binding is trying to communicate with, but you haven’t enabled all debug logging, and the log is very short. There are no responses to any requests in the log.
Sorry - but it’s very difficult to comment on this at the moment as there is very little information. Since you are developing your own device, I would suggest to look there. You can see some errors in your device log for starters - maybe it’s worth looking at what they mean?
Hi chris,
As per my program at node end, it scans available network on all channels, on the basic of 3 types of keys
And I m not using Install codes, that’s why it is showing 2 nodes connected (basically they are not paired completely).
I talked to the silabs,
https://www.silabs.com/community/wireless/zigbee-and-thread/forum.topic.html/unable_to_pair_gatew-udNB
and I found this.
Can I suggest that we continue to discuss in one place? I think it will be confusing if we start splitting the conversation across multiple lists and you didn’t provide the log as I requested on that list.
I’m not super sure what you are trying to show here? Images are very difficult to use when analysing logs, and there are only a small number of packets. It looks like it has probably joined the network as I can see a ZCL frame here which would probably not be sent if the association hasn’t worked, but again, from this, it’s very hard to tell and you should provide the ISD as I requested on the other list.
What does this show that you want me to look at? Please help me to help you by providing some information since the last thing I suggested was to get the ISD log as was requested a number of times here and on the other forum where we are discussing this issue. Do you have this?
This log shows a device joining, but I don’t know what your issue is now?
I am not able to send file directly, so
https://drive.google.com/file/d/1NQKOOQ1E3t5FPUsDH9XFs7LzhmoDyHFk/view?usp=sharing
I cannot access this log. Also, as I just asked above, please can you describe what the log is. If you just provide a log with no explanation and no answer to my previous questions, I don’t know what it tries to show me.
In the log, policy for network connection is EMBER_USE_PRECONFIGURED_KEY
2019-01-16 23:01:24.562 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspTrustCenterJoinHandler [newNodeId=54162, newNodeEui64=000B57FFFEF19ED5, status=EMBER_STANDARD_SECURITY_UNSECURED_JOIN, policyDecision=EMBER_USE_PRECONFIGURED_KEY, parentOfNewNodeId=0]
2019-01-16 23:01:32.586 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspTrustCenterJoinHandler [newNodeId=54162, newNodeEui64=000B57FFFEF19ED5, status=EMBER_STANDARD_SECURITY_UNSECURED_JOIN, policyDecision=EMBER_USE_PRECONFIGURED_KEY, parentOfNewNodeId=0]
I think their is mis-matching of PRECONFIGURED_KEY
shared isd file
https://drive.google.com/open?id=1F2JFi_m59WLR1Lf-dxP4K9TxqVIKHGrS
In that case can you provide the log from the binding that shows the key you are using? Unless it is changed (by you), it is set to the standard ZigBeeAlliance09 key (as I said on the other forum).
Why do you think this?
As I mentioned earlier, the last log you provided shows the devices are working?
Therefore, the key must be correct or the device would not join the network. Sorry - I’m still a little confused by what your problem is that you’re reporting?
Hi chris,
My stack is not receiving NETWORK_KEY in APS Unicast packet which is sended by coordinate.
I hope I got the actual problem.
What are the devices I see in the log then? Are they other devices? They seem to have joined the network, and are working ok.
Can you provide the log I asked for above please (ie the binding startup log)?
Logs are of same device, but the network formation is incomplete.
2019-01-16 23:01:27.448 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspIncomingRouteRecordHandler [source=54162, sourceEui=000B57FFFEF19ED5, lastHopLqi=255, lastHopRssi=-77, relayList=]
2019-01-16 23:01:27.456 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspIncomingRouteRecordHandler [source=54162, sourceEui=000B57FFFEF19ED5, lastHopLqi=254, lastHopRssi=-78, relayList=]
2019-01-16 23:01:27.459 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspIncomingRouteRecordHandler [source=54162, sourceEui=000B57FFFEF19ED5, lastHopLqi=254, lastHopRssi=-78, relayList=]
2019-01-16 23:01:27.489 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspIncomingMessageHandler [type=EMBER_INCOMING_UNICAST, apsFrame=EmberApsFrame [profileId=0, clusterId=32772, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=98], lastHopLqi=255, lastHopRssi=-78, sender=54162, bindingIndex=255, addressIndex=255, messageContents=00 00 92 D3 1A 1A 04 01 0D 01 00 08 00 00 03 00 04 00 05 00 06 00 08 00 00 03 00 10 01 00 10]
2019-01-16 23:01:27.494 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=54162/0, destinationAddress=0/0, profile=0000, cluster=32772, addressMode=null, radius=0, apsSecurity=false, apsCounter=98, payload=00 00 92 D3 1A 1A 04 01 0D 01 00 08 00 00 03 00 04 00 05 00 06 00 08 00 00 03 00 10 01 00 10]
2019-01-16 23:01:27.496 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: SimpleDescriptorResponse [54162/0 -> 0/0, cluster=8004, TID=NULL, status=SUCCESS, nwkAddrOfInterest=54162, length=26, simpleDescriptor=SimpleDescriptor [endpoint=26, profileId=0104, deviceId=269, deviceVersion=0, inputClusterList=[0, 3, 4, 5, 6, 8, 768, 4096], outputClusterList=[4096]]]
2019-01-16 23:01:27.505 [DEBUG] [zigbee.transaction.ZigBeeTransaction] - Transaction complete: SimpleDescriptorRequest [0/0 -> 54162/0, cluster=0004, TID=3F, nwkAddrOfInterest=54162, endpoint=26]
2019-01-16 23:01:27.508 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspMessageSentHandler [type=EMBER_OUTGOING_DIRECT, indexOrDestination=54162, apsFrame=EmberApsFrame [profileId=0, clusterId=4, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=13], messageTag=63, status=EMBER_SUCCESS, messageContents=]
2019-01-16 23:01:27.510 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspMessageSentHandler [type=EMBER_OUTGOING_DIRECT, indexOrDestination=54162, apsFrame=EmberApsFrame [profileId=0, clusterId=4, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=13], messageTag=63, status=EMBER_SUCCESS, messageContents=]
2019-01-16 23:01:27.514 [DEBUG] [iscovery.ZigBeeNodeServiceDiscoverer] - 000B57FFFEF19ED5: Node SVC Discovery: SimpleDescriptorResponse returned SimpleDescriptorResponse [54162/0 -> 0/0, cluster=8004, TID=NULL, status=SUCCESS, nwkAddrOfInterest=54162, length=26, simpleDescriptor=SimpleDescriptor [endpoint=26, profileId=0104, deviceId=269, deviceVersion=0, inputClusterList=[0, 3, 4, 5, 6, 8, 768, 4096], outputClusterList=[4096]]]
2019-01-16 23:01:27.516 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting input clusters [0, 3, 4, 5, 6, 8, 768, 4096]
2019-01-16 23:01:27.519 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster BASIC as server
2019-01-16 23:01:27.522 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster IDENTIFY as server
2019-01-16 23:01:27.525 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster GROUPS as server
2019-01-16 23:01:27.528 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster SCENES as server
2019-01-16 23:01:27.531 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster ON_OFF as server
2019-01-16 23:01:27.534 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster LEVEL_CONTROL as server
2019-01-16 23:01:27.537 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster COLOR_CONTROL as server
2019-01-16 23:01:27.540 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster TOUCHLINK as server
2019-01-16 23:01:27.542 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting output clusters [4096]
2019-01-16 23:01:27.545 [DEBUG] [.zsmartsystems.zigbee.ZigBeeEndpoint] - 54162/26: Setting cluster TOUCHLINK as client
2019-01-16 23:01:27.548 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: SimpleDescriptorRequest [0/0 -> 54162/0, cluster=0004, TID=40, nwkAddrOfInterest=54162, endpoint=242]
2019-01-16 23:01:27.551 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=54162/0, profile=0000, cluster=4, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=64, payload=00 92 D3 F2]
2019-01-16 23:01:27.554 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EzspSendUnicastRequest [type=EMBER_OUTGOING_DIRECT, indexOrDestination=54162, apsFrame=EmberApsFrame [profileId=0, clusterId=4, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=64], messageTag=64, messageContents=00 92 D3 F2]
2019-01-16 23:01:27.665 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspSendUnicastResponse [status=EMBER_SUCCESS, sequence=14]
2019-01-16 23:01:27.667 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspSendUnicastResponse [status=EMBER_SUCCESS, sequence=14]
2019-01-16 23:01:32.361 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspMessageSentHandler [type=EMBER_OUTGOING_DIRECT, indexOrDestination=54162, apsFrame=EmberApsFrame [profileId=0, clusterId=4, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=14], messageTag=64, status=EMBER_DELIVERY_FAILED, messageContents=]
2019-01-16 23:01:32.364 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspMessageSentHandler [type=EMBER_OUTGOING_DIRECT, indexOrDestination=54162, apsFrame=EmberApsFrame [profileId=0, clusterId=4, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=14], messageTag=64, status=EMBER_DELIVERY_FAILED, messageContents=]
2019-01-16 23:01:32.586 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspTrustCenterJoinHandler [newNodeId=54162, newNodeEui64=000B57FFFEF19ED5, status=EMBER_STANDARD_SECURITY_UNSECURED_JOIN, policyDecision=EMBER_USE_PRECONFIGURED_KEY, parentOfNewNodeId=0]
2019-01-16 23:01:32.591 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 000B57FFFEF19ED5: nodeStatusUpdate - node status is UNSECURED_JOIN, network address is 54162.
2019-01-16 23:01:32.596 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - 000B57FFFEF19ED5: Device status updated. NWK=54162
2019-01-16 23:01:32.600 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 000B57FFFEF19ED5: Node 54162 update
2019-01-16 23:01:32.619 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 000B57FFFEF19ED5: Starting ZigBee device discovery
2019-01-16 23:01:32.626 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 000B57FFFEF19ED5: Creating ZigBee device zigbee:device with bridge zigbee:coordinator_ember:280bea57
2019-01-16 23:01:32.661 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 000B57FFFEF19ED5: Node discovery not complete
Binding start up log how can i get it.
Please can you explain what you mean by this? The network is formed by the coordinator - another device has joined the network, and the binding has retrieved the endpoints and clusters etc. How can the network formation be incomplete? Clearly this device has joined the network correctly (right?) otherwise the binding it would not be able to download all the service information from the device.
The log you provide here also shows communication with the device -:
(please post logs with code fences to make them readable).
This log is very short so I can’t really comment on it very much, but obviously before this the binding would have sent the descriptor request since it has received the response from the end device. Again, the network must be working or there would not be this communication.
By restarting the binding 
Is this pic is generated by my given isd
