Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect zigbee bulb(sengled) #92

Open
sharad12oc opened this issue Aug 14, 2024 · 0 comments
Open

Unable to connect zigbee bulb(sengled) #92

sharad12oc opened this issue Aug 14, 2024 · 0 comments

Comments

@sharad12oc
Copy link

sharad12oc commented Aug 14, 2024

Hi,

I hope this message finds you well!

I wanted to say that your repository has been incredibly useful for our project. We are using an Ubuntu machine along with a SkyConnect (SkyConnect v1.0, manufacturer: Nabu Casa, version: 7.3.1.0, build: 176) dongle as a coordinator and a Sengled bulb as an end device.

EZSP Version: 12

We are able to form the Zigbee network, which can be seen in the logs below. However, we are unable to connect the end device (Sengled bulb) to the Zigbee network formed.

Kindly help to resolve the above query.

Logs:
sharad:~/sharad/libezsp-2.2.2$ LD_LIBRARY_PATH=/home/sharad/sharad/Zigbee/serial ./example/mainEzspTest -C 11 -c 26 -r '*' -d -Z
Starting ezsp test program (info) .............
ashCbInfo : ASH_STATE_DISCONNECTED
handleDongleState() dongle removed
CEzspDongle UART reset
EZSP serial communication started
CLibEzspMain state changing from UNINITIALIZED to WAIT_DONGLE_READY
EZSP library change to state UNINITIALIZED ...............
AshCodec::decode RSTACK v2, resetCode=0x0b
ashCbInfo : ASH_STATE_CONNECTED
CLibEzspMain state changing from WAIT_DONGLE_READY to GETTING_EZSP_VERSION
EZSP library change to state UNINITIALIZED
EZSP message is too short
Got EZSP_VERSION payload:0c 02 10 73
Current EZSP version supported by dongle (12) is higher than our minimum (6). Re-initializing dongle
CLibEzspMain state changing from GETTING_EZSP_VERSION to GETTING_EZSP_VERSION
EZSP library change to state UNINITIALIZED
Got EZSP_VERSION payload:0c 02 10 73
EZSP adapter version is supported: EZSPv12 with stack type 2 (mesh). Stack version: 7.3.1.0
CLibEzspMain state changing from GETTING_EZSP_VERSION to GETTING_XNCP_INFO
EZSP library change to state UNINITIALIZED
Wrong size for EZSP_GET_XNCP_INFO message: 1 bytes
CLibEzspMain state changing from GETTING_XNCP_INFO to STACK_INIT
EZSP library change to state UNINITIALIZED
EZSP_SET_CONFIGURATION_VALUE RSP : 53
EZSP_SET_CONFIGURATION_VALUE RSP : 53
EZSP_SET_CONFIGURATION_VALUE RSP : 53
EZSP_SET_CONFIGURATION_VALUE RSP : 53
EZSP_SET_CONFIGURATION_VALUE RSP : 55
EZSP_SET_CONFIGURATION_VALUE RSP : 55
EZSP_SET_CONFIGURATION_VALUE RSP : 55
EZSP_SET_CONFIGURATION_VALUE RSP : 55
Call EZSP_NETWORK_INIT
Call EZSP_NETWORK_INIT
Multiple EZSP payloads extraction from one ASH stream:
32 84 01 17 00 00
32 90 01 19 00 90
Call EZSP_NETWORK_STATE
Asynchronous EZSP message received
CEZSP_STACK_STATUS_HANDLER status : EMBER_NETWORK_UP
Call EZSP_NETWORK_STATE
Call EZSP_NETWORK_STATE
Zigbee reset requested... Leaving current network
CLibEzspMain state changing from STACK_INIT to LEAVE_NWK_IN_PROGRESS
EZSP library change to state SINK_BUSY
CLibEzspMain state changing from LEAVE_NWK_IN_PROGRESS to STACK_INIT
EZSP library change to state UNINITIALIZED
EZSP_LEAVE_NETWORK status : EMBER_SUCCESS
CEZSP_STACK_STATUS_HANDLER status : EMBER_NETWORK_DOWN
Call EZSP_NETWORK_STATE
No pre-existing network on the EZSP adapter
Creating new network on channel 26
CLibEzspMain state changing from STACK_INIT to FORM_NWK_IN_PROGRESS
EZSP library change to state SINK_BUSY
EZSP_SET_INITIAL_SECURITY_STATE status : EMBER_SUCCESS
Multiple EZSP payloads extraction from one ASH stream:
3c 84 01 1e 00 00
3c 90 01 19 00 90
EZSP_FORM_NETWORK status : EMBER_SUCCESS
CEZSP_STACK_STATUS_HANDLER status : EMBER_NETWORK_UP
CLibEzspMain state changing from FORM_NWK_IN_PROGRESS to SINK_BUSY
EZSP library change to state SINK_BUSY
Call EZSP_GP_SINK_TABLE_INIT
SINK State change from SINK_NOT_INIT to SINK_READY
Underneath sink changed to state: 2, current libezsp state: 12
CLibEzspMain state changing from SINK_BUSY to READY
EZSP library change to state READY
EZSP library is ready, entering main state machine with MainState 0
Applying remove all GPD action
CLibEzspMain state changing from READY to SINK_BUSY
EZSP library change to state SINK_BUSY
SINK State change from SINK_READY to SINK_CLEAR_ALL
Underneath sink changed to state: 8, current libezsp state: 12
Moving to MainState 1
EZSP_GP_SINK_TABLE_INIT RSP
GetNetworkParametersResponse : { [status : EMBER_SUCCESS][modeType : EMBER_COORDINATOR][EmberNetworkParameters : { [extend_pan_id: 0xfe946a1edae4d1f2][pan_id : 3d49][radio_tx_power : 3][radio_channel : 26][join_method : EMBER_USE_MAC_ASSOCIATION][nwk_manager_id : 0000][nwk_update_id : 00][channels : f8000000] }] }
EZSP_GP_PROXY_TABLE_PROCESS_GP_PAIRING
EZSP_GP_PROXY_TABLE_PROCESS_GP_PAIRING
EZSP_GP_PROXY_TABLE_PROCESS_GP_PAIRING
EZSP_GP_PROXY_TABLE_PROCESS_GP_PAIRING
EZSP_GP_PROXY_TABLE_PROCESS_GP_PAIRING
SINK State change from SINK_CLEAR_ALL to SINK_READY
Underneath sink changed to state: 2, current libezsp state: 12
CLibEzspMain state changing from SINK_BUSY to READY
EZSP library change to state READY
EZSP library is ready, entering main state machine with MainState 1
Opening GP channel request window for 11s
Now scanning spectrum for clearest channel
CLibEzspMain state changing from READY to SCANNING
EZSP library change to state READY
EZSP library is ready, entering main state machine with MainState 5
Moving to MainState 5
Moving to MainState 5
Multiple EZSP payloads extraction from one ASH stream:
4b 84 01 22 00 00
4b 90 01 19 00 9c
EZSP_PERMIT_JOINING return status : EMBER_SUCCESS
Asynchronous EZSP message received
CEZSP_STACK_STATUS_HANDLER status : EMBER_NETWORK_OPENED
Call EZSP_NETWORK_STATE
EZSP_SEND_BROADCAST return status : EMBER_SUCCESS
GetNetworkParametersResponse : { [status : EMBER_SUCCESS][modeType : EMBER_COORDINATOR][EmberNetworkParameters : { [extend_pan_id: 0xfe946a1edae4d1f2][pan_id : 3d49][radio_tx_power : 3][radio_channel : 26][join_method : EMBER_USE_MAC_ASSOCIATION][nwk_manager_id : 0000][nwk_update_id : 00][channels : f8000000] }] }
EZSP_GET_KEY status : EMBER_SUCCESS, EmberKeyStruct : { [bitmask : 0003][type : EMBER_CURRENT_NETWORK_KEY][key : 46 40 20 68 c8 24 f7 fa 21 86 27 f2 18 7c c7 5e][outgoingFrameCounter : 00000002][incomingFrameCounter : 00000000][sequenceNumber : 0][partnerEUI64 : 00 00 00 00 00 00 00 00] }
EZSP_GET_CHILD_DATA return at index : 0, status : EMBER_NOT_JOINED
Scan succesfully started
Unexpectedly got EZSP_NETWORK_STATE with value 2 while not in STACK_INIT or FORM_NWK_IN_PROGRESS or LEAVE_NWK_IN_PROGRESS state... assuming stack has been initialized. Ignoring...
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 11 rssi: -30 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 12 rssi: -13 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 13 rssi: -13 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 14 rssi: -25 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 15 rssi: -26 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 16 rssi: -44 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 17 rssi: -46 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 18 rssi: -49 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 19 rssi: -50 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 20 rssi: -38 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 21 rssi: -38 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 22 rssi: -39 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 23 rssi: -39 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 24 rssi: -42 dBm
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 25 rssi: -47 dBm
Multiple EZSP payloads extraction from one ASH stream:
52 94 01 48 00 1a d5
52 90 01 1c 00 1a 00
EZSP_ENERGY_SCAN_RESULT_HANDLER: channel: 26 rssi: -43 dBm
Scan finished
CLibEzspMain state changing from SCANNING to READY
EZSP library change to state READY
EZSP library is ready, entering main state machine with MainState 5
Moving to MainState 5
Selecting channel 19 with rssi: -50 dBm
Adapter version: EzspAdapterVersion : { [EZSPv12 running stack type 2 (mesh)][stack v7.3.1.0] }
Preparation steps finished... switching to run state
EZSP_PERMIT_JOINING return status : EMBER_SUCCESS
EZSP_SEND_BROADCAST return status : EMBER_SUCCESS
GetNetworkParametersResponse : { [status : EMBER_SUCCESS][modeType : EMBER_COORDINATOR][EmberNetworkParameters : { [extend_pan_id: 0xfe946a1edae4d1f2][pan_id : 3d49][radio_tx_power : 3][radio_channel : 26][join_method : EMBER_USE_MAC_ASSOCIATION][nwk_manager_id : 0000][nwk_update_id : 00][channels : f8000000] }] }
EZSP_GET_KEY status : EMBER_SUCCESS, EmberKeyStruct : { [bitmask : 0003][type : EMBER_CURRENT_NETWORK_KEY][key : 46 40 20 68 c8 24 f7 fa 21 86 27 f2 18 7c c7 5e][outgoingFrameCounter : 00000004][incomingFrameCounter : 00000000][sequenceNumber : 0][partnerEUI64 : 00 00 00 00 00 00 00 00] }
EZSP_GET_CHILD_DATA return at index : 0, status : EMBER_NOT_JOINED
EZSP_MESSAGE_SENT_HANDLER return status : EMBER_SUCCESS
EZSP_MESSAGE_SENT_HANDLER return status : EMBER_SUCCESS
EZSP_MESSAGE_SENT_HANDLER return status : EMBER_SUCCESS
Closing GP channel request window
Multiple EZSP payloads extraction from one ASH stream:
58 94 01 23 00 00 00 51 64 fc 3a 16 00 14 18 ce b0 03
58 90 01 24 00 51 64 fc 3a 16 00 14 18 ce b0 02 03 ff ff
EZSP_MESSAGE_SENT_HANDLER return status : EMBER_SUCCESS
Multiple EZSP payloads extraction from one ASH stream:
58 94 01 23 00 00 00 ee b0 fc 3a 16 00 14 18 ce b0 03
58 90 01 24 00 ee b0 fc 3a 16 00 14 18 ce b0 02 03 ff ff
EZSP_MESSAGE_SENT_HANDLER return status : EMBER_SUCCESS
CEZSP_STACK_STATUS_HANDLER status : EMBER_NETWORK_CLOSED
Call EZSP_NETWORK_STATE
Unexpectedly got EZSP_NETWORK_STATE with value 2 while not in STACK_INIT or FORM_NWK_IN_PROGRESS or LEAVE_NWK_IN_PROGRESS state... assuming stack has been initialized. Ignoring...
Multiple EZSP payloads extraction from one ASH stream:
59 94 01 23 00 00 00 a2 32 fc 3a 16 00 14 18 ce b0 03
59 90 01 24 00 a2 32 fc 3a 16 00 14 18 ce b0 02 03 ff ff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant