Expose manufacturer and model names to the services/list.json

[gmarty]

That'd be nice to have the name of the manufacturer and the model ID of each services in list.json.
This can be used to display specific icon to help users to identify devices quicker.

cc @fabricedesre and @cr

[Yoric]

Just to be clear, services/list.json is the placeholder until we have an official REST API for requesting nodes, right?

If so, @gmarty, it would be great if you could also start filing these issues to fxbox_taxononomy.

[mcav]

Is this still valid, in light of alleged plans to move away from services/list.json?

[fabricedesre]

I don't think it is. Closing.

[gmarty]

Please unclose this bug. It's still relevant to services/list.
We need to expose more data about the services so that the app looks better.

Alternatively, we can list them in the service/id/state response.

[Yoric]

Note that this will eventually move to /api/*, instead of /services/, once that is implemented.

[fabricedesre]

@gmarty So which details do you need exactly?

[gmarty]

@fabricedesre At least the manufacturer and the model name of the devices.
Phillips has a nice set of SVG icons for all the products in the Hue range. Displaying this icon somewhere in the app will help the user to identify the device quicker.

Also the Hue API makes a distinction between attributes (immutable) and state (that change over time) of each devices. Both are clearly separated in the response and we probably need something similar.

[azasypkin]

I'll take it, as we've agreed I'll expose manufacturer, type and model via ServiceSetttings::custom_properties BTreeMap.