• State Not Answered
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 173 views
  • Users 0 members are here
Attachments (4) Download All
Nordic Case Info
  • Case ID: 288942
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Matter Android CHIPtool crashing & own apk build possibly incomplete

user115603

I have been working with the matter sample project in the nrfconnect sdk and set up my Matter dev environment with a raspberry pi as border router.

When using the android CHIPtool to commission the sample, commssioning works and i can read values via the "cluster interaction tool" but whenever I try to set a value or use a command that I enabled in the .zap configuration the app crashes.

I was using the app from the releases for v1.9.1 on the git page (https://github.com/nrfconnect/sdk-connectedhomeip/releases). The matter sample is of the same version. I tried building my own version of the app via Android studio and followed the guide on https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/matter/android_building.html. THe APK was generated without any errors, but this version of the app fails to even commission the Mattter sample to my Thread network. I compared both APK files and saw my build is only 29MB while the apk on the git release is 207.1 MB. see the "apk comparinson.png"

I have included both debug logs of the matter template project and the android process. Can anyone tell my what is going wrong?   

Parents Reply Children
  • 0 in reply to user92402

    Within the "cluster interaction tool" section, I was trying to set the OccupiedHeatingSetpoint of the thermostat cluster. At line 634 of the v1.9.1 release apk debug you can see the app crashes when it tries to convert the desired setpoint entered in the textbox to an integer. I have tried this multiple times with different numerical values but the app always crashes

  • 0 in reply to user115603

    Hi,

    Thank you for the additional information.

    I saw the casting error, so I wanted to verify that the input was correct according to the attribute, which an integer of course is for the OccupiedHeatingSetpoint attribute. It seems like this might be a bug in the Android CHIPTool. I have forwarded it and your logs to the developers, and I am currently waiting for a response. I will update you when I know more.

    Best regards,

    Marte

Related
Terms of service