• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 391 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652P: End Device joined to network, but does not toggle ON/OFF attribute!

Roberto Nucera
Intellectual 265 points

Part Number: CC2652P

Here I am again with a trouble sometimes arises: my network is composed by 1 Coordinator, 5 Routers and 20 End devices. .All this replied many times in a wide area.

The coordinator joins through zigbee2mqtt an HTML page where I can see all my devices in dashboard page.

 

It happens that after many hours where all is Ok, an end device (may be due to coordinator… I don’t know)  does not accept the command that toggles all outputs (4 outs): (even “Reconfigure” command sent by zigbee2mqtt does not reset the problem).

At the moment the only solution is turning off then on the device (which is 70 km far away!)

Please notice that this device sends data, updating endpoints correctly! Even the “Devices” page tells everything is ok. But the Log page shows what here attached.

Thanks for any help!

Luigi

  • 0
    TI__Guru**** 220787 points

    Hi Luigi,

    I don't know what exactly is going wrong without additional sniffer logs or debug information.  So you can confirm that the ZED is still in the network and communicating Zigbee packets to its parent?  And yet power cycling is a known method for correctly restarting proper behavior, but a soft reset is ineffective?  If you know where the device is getting stuck in code then you could try implementing a watchdog or system reset.  It would also be helpful to more reliably and quickly recreate such behavior.  As it pertains to the Zigbee2MQTT solution, you can you can also get support and ask questions on their Forum and Discord channel.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 265 points

    Thanks Ryan! I did not explain myself exactly... sorry: I mentioned power cycle because when we are in filed it's the simplest way to restart the locked device. But notice that processor Hw reset mostly resolves the trouble.

    Hw reset is made by a joined processor on the same board that works as IO expander and other useful functions….

    Lastly we decided to make it also act as a watchdog, controlling data continuously coming from TI processor.

    What I feel strange is that if it was a Coordinator or zigbee2mqtt problem, resetting the end device would not resolve the hang up situation, unless reset procedure triggers something on these higher level devices, and it all restarts….

    Anyway you are very kind taking care quickly of my tickets!

    BR

    Luigi

  • 0 in reply to Roberto Nucera
    TI__Guru**** 220787 points

    Are you certain that the device is locked, meaning that it cannot send, acknowledge, or receive any packets or operate its application?  Once more, please try to find a way to replicate this behavior with a device you can access.

    Regards,
    Ryan