Matter Temperature Sensor Output

[Tony]

I created a new Matter project based on the light bulb example.

I want to add several more endpoints with different commands and values.

As a way to learn how things work, I followed the example tutorial to add the temperature sensor with an on_off command to start it going and stop it.

When I commission my device to my SmartThings hub, it shows up with 2 switched as expected.

I figured out how to get the endpoint id during in the MatterPostAttributeChangeCallback.

If the endpoint is 1, then I turn the light bulb on and off. if the endpoint is 2, then i send the app event to turn the temperature sensor on and off.

My question is where am I supposed to see the random temperature reading in the UI on my Android phone that is connected to the SmartThings hub?

When I turn the light bulb on and off that on/off switch turns on and off and the LED on the dev kit turns on and off.

When I hit the switch for the temperature sensor that is simply called "switch 2", nothing happens in the UI on my phone.

When the temperature sensor is enabled, I do get a call to MatterPostAttributeChangeCallback every second, but nothing else happens.

Shouldn't the phone UI have some place for the sensor value to show up? What controls that?

[Charlie]

Hi Tony,

Could you try other ecosystems like Apple Homekit or Google Home? It may depend on the smart home ecosystem manufacturer which Matters device type and attribute they support.

I suggest you try Adding clusters to Matter application — nRF Connect SDK 2.5.0 documentation (nordicsemi.com) first to confirm if a temperature sensor device works on your testing platform.

Best regards,

Charlie

[Tony]

The link you gave is exactly the tutorial I followed to get to this point.

When I try to use Apple Homekit or Google Home, they both won't complete the provisioning process. They both say it is because the device is not a certified device. This makes sense because we are not ready to certify our device, so it isn't registered with the certifying company.

Samsung's app is the only one that gives the option to continue when it detects it is not a certified device.

What do I do now?

[Charlie]

Tony said:

They both say it is because the device is not a certified device

OK, did you try with light bulb and light switch samples before?

Best regards,

Charlie

[Tony]

Yes, I have tried those.

In fact, my code was started as the light bulb example and then I added the temperature code from that tutorial.

Can you please point me to some information that explains how an app like the Smartthings App is supposed to determine what UI to use? How is it supposed to know that this is a temperature sensor with a value to display?

In the log output I can see the temperature value being generated every 300ms when it is on and nothing when it is off, so I know it is doing its thing.

It just isn't informing the UI of the Smartthings app that it is a temperature sensor because it the app is showing the same UI for the bulb / switch and temperature sensor as if it thinks the sensor is a switch.