Minimal Matter Device Type

[josh_s]

I'm working on an accelerometer based smarthome sensor using thread. It will not need any interoperability with other smarthome devices since it's just a sensor that would stream data back to a cloud backend occasionally, but I want users to be able pair it to apple/google/amazon hubs acting as border routers.

I would like the device to be a matter device because that would ensure that it can be commissioned to google/apple/amazon hubs, but my device role doesn't fit neatly into any of the existing matter device types (i.e. it's not a lock, light, switch etc). Is there a generic "base" device type that I can use?

Thank you!

[josh_s]

I’m not so sure-  I built the matter sample template with no additional clusters or changes whatsoever- and went into my apple home app to commission the device. It works, but the device doesn’t show up in the home app since it’s not a supported device type.  

However, in the matter CLI on the device I am able to ping 8.8.8.8 etc. into the open internet, so it seems possible to set up an AWS IOT core connection too using the homepod mini as a OTBR.

[ovrebekk]

Hi Joshua

My point is that this can not be guaranteed, since it's not something the hubs are required to support. 

What works on one hub might not work on another, and as such it is risky to depend on this functionality for an end product that could be used with any hub.  

Also, the hubs will frequently receive firmware updates, and it's possible that this capability will be removed or restricted in a future update. 

It's the classic difference between something that might work on your desk, but might not work reliably in the field when you have a lot of devices in different environments. 

Best regards
Torbjørn