Hello to all, Below are the setup details I'm using: nRF52840 DevKit SDK: nRF5_SDK_for_Thread_and_Zigbee_v4.1.0 Segger Embedded Studio 4.16 Aim: Controlling the Radiator through ZigBee using thermostat cluster and updating the firmware using OTA cluster ZigBee UART protocol Reference Example code: ZigBee OTA Upgrade Client code Issue: The device is not advertising on the gateway (deconz/Alexa) Once the client device firmware is updated successfully, the device does not advertise on the gateway. I did the following test to check the advertisement of my device Flashed the MBR.hex file flashed the updated firmware code in debug mode. run the code. Here I'm able to discover my device and able to perform the operation successfully. Why am I not able to discover my client device once the firmware is updated? Do I have to do any other operations? ? I would appreciate your efforts for a quick response at the earliest. Kind regards, Shivaprasad.

ZigBee OTA updated but device is not advertising on the gateway (deconz/Alexa)

user105526 over 4 years ago

Hello to all,

Below are the setup details I'm using:

nRF52840 DevKit
SDK: nRF5_SDK_for_Thread_and_Zigbee_v4.1.0
Segger Embedded Studio 4.16

Aim: Controlling the Radiator through ZigBee using thermostat cluster and updating the firmware using OTA cluster

ZigBee
UART protocol

Reference Example code:

ZigBee OTA Upgrade Client code

Issue: The device is not advertising on the gateway (deconz/Alexa)

Once the client device firmware is updated successfully, the device does not advertise on the gateway.
I did the following test to check the advertisement of my device
1. Flashed the MBR.hex file
2. flashed the updated firmware code in debug mode.
3. run the code.
Here I'm able to discover my device and able to perform the operation successfully.

Why am I not able to discover my client device once the firmware is updated? Do I have to do any other operations??

I would appreciate your efforts for a quick response at the earliest.

Kind regards,

Shivaprasad.

Parents

0 user14926 over 4 years ago
Hi,

Did you closely follow the instructions in Zigbee OTA Upgrade Client Example to generate the packet and perform the upgrade?

Can you provide a sniffer trace of the connection establishment with the gateway before and after the upgrade?

Can you provide the device logs from the "ZigBee OTA Upgrade Client code" before and after the upgrade?

Best regards,
Jørgen
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user105526 over 4 years ago in reply to user14926
Hello,

Yes, I have followed instructions from the same link.

Please find the link for sniffer and device logs below

Firmware update was done using the deCONZ gateway, client DK and server DK.

Zigbee OTA client example code, modified the same code and updated it as a firmware

here used the example code

Sniffer: https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/EU51wSLHW2xHoAIbdPIzaE0BtMnKRYAdpDKfjHtCfmugqw?e=T1xq7D

Device log:https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/Ee3lqnlTOMNCnDOhwUsYIzEBNhUdJTAC9OaAqpt6Gp-krg?e=6FimlF

Zigbee OTA client example code, used Custom code as the firmware update

here used example code as client and custom code as an firmware update

The reason to use example code is because the OTA cluster is visible, but it's attributes are not visible in the custom code, please can you suggest what may be the reason for this?

Without the Ota cluster attributes, one cannot perform the OTA update using deCONZ gateway.

Sniffer: https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/ETnoS8kt3DVEuRuVBALbsrQBgnsOD5w6X3cfXEnbJk0xjA?e=B8kDEz

Device log: https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/Eat-A3G4rVRAjbYoKAhL2eoBCab5XQnyI5fvO54mjmH8Ow?e=L7wQBd

Thanks is advance.

Kind regards,

Shivaprasad
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 user105526 over 4 years ago in reply to user14926
Hello,

Yes, I have followed instructions from the same link.

Please find the link for sniffer and device logs below

Firmware update was done using the deCONZ gateway, client DK and server DK.

Zigbee OTA client example code, modified the same code and updated it as a firmware

here used the example code

Sniffer: https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/EU51wSLHW2xHoAIbdPIzaE0BtMnKRYAdpDKfjHtCfmugqw?e=T1xq7D

Device log:https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/Ee3lqnlTOMNCnDOhwUsYIzEBNhUdJTAC9OaAqpt6Gp-krg?e=6FimlF

Zigbee OTA client example code, used Custom code as the firmware update

here used example code as client and custom code as an firmware update

The reason to use example code is because the OTA cluster is visible, but it's attributes are not visible in the custom code, please can you suggest what may be the reason for this?

Without the Ota cluster attributes, one cannot perform the OTA update using deCONZ gateway.

Sniffer: https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/ETnoS8kt3DVEuRuVBALbsrQBgnsOD5w6X3cfXEnbJk0xjA?e=B8kDEz

Device log: https://shalakacom-my.sharepoint.com/:u:/g/personal/shivaprasad_desai_shalaka_com/Eat-A3G4rVRAjbYoKAhL2eoBCab5XQnyI5fvO54mjmH8Ow?e=L7wQBd

Thanks is advance.

Kind regards,

Shivaprasad
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data