It is not clear what types queue returned from resource subscription contains

[kuggenhoffen]

Documentation for ConnectAPI.add_resource_subscription does not clearly indicate what is the type of objects that will be put into the returned queue. Consider explicitly documenting what is the type.

[davidhyman]

An update on this:
For the most part, these objects are not defined anywhere. For resources, for example, we have no way of knowing what the client code on the device will return. We parse TLV data before passing it to observers, but cannot document what this is in advance. Hopefully that makes sense?

In some cases (such as DeviceStateChange) we would like to return SDK objects, but at present simply pass through the payload of the notification. We're working to improve the higher level abstractions, such as this, provided by the SDKs.

[kuggenhoffen]

I was probably thinking about what are the python types that will be put into the queue. Now it seems they will be dictionaries with item-id's as keys and resource values as values. This dictionary would be nice to have documented on the add_resource_subscription API, also would be nice to know the value type as well even though the SDK won't have knowledge of the actual value format right now (seems that it will be an int in case tlv decoded value and bytearray(?) for non tlv values)