ETM-Schurig/powersync-zigbee
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix a crash if the controller takes too long to start

Browse Source 
This may happen on very rare occations after a nymea restart
if the controller is taking too long to initialize but still succeeds
in the end. Also increases the timeout for the procedure.
This commit is contained in:
Michael Zanetti 2022-06-08 23:30:05 +02:00
parent 62e003887e
commit e9d594ee5b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libnymea-zigbee/backends/ti/zigbeebridgecontrollerti.cpp
View File

@ -77,7 +77,7 @@ ZigbeeInterfaceTiReply* ZigbeeBridgeControllerTi::reset()
ZigbeeInterfaceTiReply *ZigbeeBridgeControllerTi::init()
{
ZigbeeInterfaceTiReply *initReply = new ZigbeeInterfaceTiReply(this, 10000);
ZigbeeInterfaceTiReply *initReply = new ZigbeeInterfaceTiReply(this, 15000);
ZigbeeInterfaceTiReply *resetReply = reset();
connect(resetReply, &ZigbeeInterfaceTiReply::finished, initReply, [=]() {
@ -179,10 +179,10 @@ void ZigbeeBridgeControllerTi::initPhase2(ZigbeeInterfaceTiReply *initReply, int
qCDebug(dcZigbeeController()) << "Reading IEEE address";
ZigbeeInterfaceTiReply *getIeeeAddrReply = readNvItem(Ti::NvItemIdPanId);
connect(getIeeeAddrReply, &ZigbeeInterfaceTiReply::finished, this, [=](){
connect(getIeeeAddrReply, &ZigbeeInterfaceTiReply::finished, initReply, [=](){
ZigbeeInterfaceTiReply *getExtAddrReply = sendCommand(Ti::SubSystemSys, Ti::SYSCommandGetExtAddress);
connect(getExtAddrReply, &ZigbeeInterfaceTiReply::finished, this, [=](){
connect(getExtAddrReply, &ZigbeeInterfaceTiReply::finished, initReply, [=](){
if (getExtAddrReply->statusCode() != Ti::StatusCodeSuccess) {
qCWarning(dcZigbeeController()) << "Call to getDeviceInfo failed:" << getExtAddrReply->statusCode();
initReply->finish(getExtAddrReply->statusCode());