devaskim

I think I understood question `Get Customer Devices` and provided possible solutions, but you need the answer for `Get Types of Customer Devices`, right?

Unfortunately, there is no easy way to implement such functionality. I know 2 ways: 1. Based on Rule Chains: catch `Entity Assigned` and `Entity Unassigned` events, check customer ownership of...

Hm, it is programming basics. The `getCustomer` is JavaScript method with 1 obligatory parameter and 1 option parameter. So to call this method, you should do at least `widgetContext.customerService.getCustomer(param1)` https://github.com/thingsboard/thingsboard/blob/master/ui-ngx/src/app/core/http/customer.service.ts#L39

As alternative to programming way of getting customer title, you can create Entity Alias of `Current Customer` Type and use it in your widget's data source

https://github.com/user-attachments/assets/07b489a6-c0d8-4a90-9466-689b8ad6ceae

If it is OK for your business, you could share your solution as widget json dump here. And I would add it to https://github.com/devaskim/awesome-thingsboard

Great! And thanks! The main valuable "thing" is an approach you have implemented. Added the link above to the aforementioned collection.

Create chart for your group, inpsect how `widgetContext.datasources` are formed for groups (e.g. create widget header custom action with `console.log(widgetContext.datasources)` in it), then rewrite the solution for individual devices accordingly

I think you can find a root cause by comparing datasource(s) of pre-configured single parameter chart and pre-configured 2+ parameter chart

> The problem is that the datasource, with its many entities, is complex to analyze; it has many parameters All you need is to update `dataKeys` array in each datasource...