Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

Sigurd Hellesvik — Fri, 07 Oct 2022 10:14:26 GMT

Hi,

Testing the sample you uploaded, I am able to toggle on/off on endpoint 1:

D: 61937 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 61945 [DMG]IM RH moving to [AwaitingDestruction]
D: 61949 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
I: 61979 [EM]Received message of type 0x10 with protocolId (0, 0) and MessageCounter:121724512 on exchange 60191r
D: 61989 [EM]Found matching exchange: 60191r, Delegate: (nil)
D: 61995 [EM]Rxd Ack; Removing MessageCounter:252237330 from Retrans Table on exchange 60191r
D: 62003 [EM]Removed CHIP MessageCounter:252237330 from RetransTable on exchange 60191r
E: 68263 [SWU]No suitable OTA Provider candidate found
I: 68268 [SWU]No provider available
I: 78855 [EM]Received message of type 0x8 with protocolId (0, 1) and MessageCounter:121724513 on exchange 60192r
D: 78865 [EM]Handling via exchange: 60192r, Delegate: 0x2000cd74
D: 78872 [DMG]Received command for Endpoint=1 Cluster=0x0000_0006 Command=0x0000_0001
I: 78879 [ZCL]On/Off set value: 1 1
I: 78882 [ZCL]On/off already set to new value
D: 78887 [DMG]Command handler moving to [ Preparing]
D: 78891 [DMG]Command handler moving to [AddingComm]
D: 78896 [DMG]Command handler moving to [AddedComma]
D: 78901 [DMG]Decreasing reference count for CommandHandler, remaining 0
I: 78908 [IN]Prepared secure message 0x2000515c to 0x000000000001B669 (1)  of type 0x9 and protocolId (0, 1) on exchange 60192r with MessageCounter:252237331.
I: 78922 [IN]Sending encrypted msg 0x2000515c with MessageCounter:252237331 to 0x000000000001B669 (1) at monotonic time: 000000000001344A msec
D: 78936 [DMG]Command handler moving to [CommandSen]
D: 78941 [DMG]Command handler moving to [AwaitingDe]
D: 79268 [EM]Retransmitting MessageCounter:252237331 on exchange 60192r Send Cnt 1
I: 79275 [IN]Sending encrypted msg 0x2000515c with MessageCounter:252237331 to 0x000000000001B669 (1) at monotonic time: 00000000000135AB msec
D: 79289 [CSM]UpdatePeerAddress: No existing OperationalSessionSetup instance found
D: 79297 [CTL]OperationalSessionSetup[1:000000000001B669]: State change 1 --> 2
I: 79304 [DIS]Resolving DF18303D6875348B:000000000001B669 ...
I: 79424 [EM]Received message of type 0x10 with protocolId (0, 0) and MessageCounter:121724514 on exchange 60192r
D: 79435 [EM]Found matching exchange: 60192r, Delegate: (nil)
D: 79441 [EM]Rxd Ack; Removing MessageCounter:252237331 from Retrans Table on exchange 60192r
D: 79449 [EM]Removed CHIP MessageCounter:252237331 from RetransTable on exchange 60192r
I: 79458 [EM]Received message of type 0x10 with protocolId (0, 0) and MessageCounter:121724515 on exchange 60192r
I: 79504 [DIS]Checking node lookup status after 200 ms
I: 94304 [DIS]Checking node lookup status after 15000 ms
E: 94309 [DIS]OperationalSessionSetup[1:000000000001B669]: operational discovery failed: 32
q
uart:~$ I: 248283 [EM]Received message of type 0x8 with protocolId (0, 1) and MessageCounter:121724516 on exchange 60193r
D: 248293 [EM]Handling via exchange: 60193r, Delegate: 0x2000cd74
D: 248299 [DMG]Received command for Endpoint=1 Cluster=0x0000_0006 Command=0x0000_0000
I: 248307 [ZCL]On/Off set value: 1 0
I: 248310 [ZCL]Toggle on/off from 1 to 0
D: 248314 [DMG]Endpoint 1, Cluster 0x0000_0006 update version to 42c7976f
D: 248321 [DMG]Command handler moving to [ Preparing]
D: 248326 [DMG]Command handler moving to [AddingComm]
D: 248330 [DMG]Command handler moving to [AddedComma]
D: 248335 [DMG]Decreasing reference count for CommandHandler, remaining 0
I: 248343 [IN]Prepared secure message 0x2000515c to 0x000000000001B669 (1)  of type 0x9 and protocolId (0, 1) on exchange 60193r with MessageCounter:252237332.
I: 248357 [IN]Sending encrypted msg 0x2000515c with MessageCounter:252237332 to 0x000000000001B669 (1) at monotonic time: 000000000003CA25 msec
D: 248371 [DMG]Command handler moving to [CommandSen]
D: 248376 [DMG]Command handler moving to [AwaitingDe]
I: 248496 [EM]Received message of type 0x10 with protocolId (0, 0) and MessageCounter:121724517 on exchange 60193r
D: 248506 [EM]Found matching exchange: 60193r, Delegate: (nil)
D: 248512 [EM]Rxd Ack; Removing MessageCounter:252237332 from Retrans Table on exchange 60193r
D: 248520 [EM]Removed CHIP MessageCounter:252237332 from RetransTable on exchange 60193r

So you code is right.

Try to remove your build folder and build again, then erase all and flash again.

Try to download the chip-tool from https://github.com/nrfconnect/sdk-connectedhomeip/releases/tag/v2.1.0.

Try the same on another android phone and see if the issue persists.

Regards,
Sigurd Hellesvik

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

Sigurd Hellesvik — Wed, 05 Oct 2022 14:03:14 GMT

I did not find anything at a scan through your project.

I will try to run it and see if I see the same issue or not tomorrow.

Regards,
Sigurd Hellesvik

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

jacobbluhm — Tue, 04 Oct 2022 13:19:07 GMT

devzone.nordicsemi.com/.../sensor-_2D00_-Copy.zip

I have this project located in C:\ncs\v2.1.0\nrf\samples\matter

Thanks!

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

Sigurd Hellesvik — Tue, 04 Oct 2022 13:15:18 GMT

Hi,

I am not able to figure out what is wrong so far.

Can you zip your project, so that I can have a look to see if it looks right and see if I am able to reproduce?

Regards,
Sigurd Hellesvik

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

jacobbluhm — Mon, 03 Oct 2022 19:03:02 GMT

Does the setup of the cluster refer to the .zap file? (Attached below, changed name from template.zap to template - zap.txt because DevZone wouldn't accept .zap file)

devzone.nordicsemi.com/.../template-_2D00_-zap.txt

I have double checked I've made all the modifications called out in the Nordic tutorial, which I think is a double check that the cluster is setup correctly. I can only interact with Endpoint 0 from the Android CHIP Tool.

void MatterPostAttributeChangeCallback in zcl_callbacks.cpp is never called, this seems to be the root of the problem

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

Sigurd Hellesvik — Fri, 30 Sep 2022 08:03:22 GMT

Hi,

Having another look at your log, it looks like the error is that the command you try to send is not available from your application
"No command 0x0000_0001 in Cluster 0x0000_0006 on Endpoint 0x1"

I realize that it is not the best tip, but let's start with:
Can you double check that your setup of the cluster is correct?

Regards,
Sigurd Hellesvik

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

jacobbluhm — Thu, 29 Sep 2022 14:09:49 GMT

No, the event handlers are not called, I confirmed this by adding LOG_INF() print statements inside the event handlers.

void AppTask::SensorActivateHandler()
{
        LOG_INF("SensorActivateHandler");
        StartSensorTimer(500);
}

void AppTask::SensorDeactivateHandler()
{
        LOG_INF("SensorDeactivateHandler");
        StopSensorTimer();
}

void AppTask::SensorMeasureHandler()
{
        LOG_INF("SensorMeasureHandler");
        chip::app::Clusters::TemperatureMeasurement::Attributes::MeasuredValue::Set(
                /* endpoint ID */ 1, /* temperature in 0.01*C */ int16_t(rand() % 5000));
}

The tutorial puts the event handlers into app_task.cpp.

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

Sigurd Hellesvik — Thu, 29 Sep 2022 13:21:43 GMT

Will the event handler in your main.c be called when the error happens?

Regards,
Sigurd Hellesvik

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

jacobbluhm — Wed, 28 Sep 2022 13:21:10 GMT

Yes, the ErrorOutput.txt is what the end device outputs after pressing 'Invoke' on the Android CHIP Tool.

RE: Matter - Android CHIP Tool fails to send commands to clusters and read attributes from clusters

Sigurd Hellesvik — Wed, 28 Sep 2022 09:17:33 GMT

Hi Jacob,

To clarify:

Does the error from your End Device only appear after you try to send the command from the Android CHIP Tool?

Regards,
Sigurd Hellesvik