Assets and entities inheriting data from devices
Hi,
Is there a way for assets and entities like customers or machines to inherit telemetry from devices without using really larges and possible overloaded rule chains? I'm running into issues with rule chains overloading when applied across all my assets and customers. I need a solution where, for example, a customer entity can automatically aggregate telemetry, such as temperature, from all its devices and have this data available at the customer or asset level.
Another challenge is tracking the number of active and inactive devices associated with an asset or customer. While I could potentially solve this with a rule chain, it's not feasible for all assets without causing overload.
I'm working with locations, areas, assets, and devices. Currently, I’m passing data to assets and, for larger customers, to customers as well. However, doing this for all customers significantly increases API usage through rule chains. Is there a node for this feature, or could it be implemented in decoders? Additionally, is it possible to add a feature that counts the number of active and inactive devices? Inheriting telemetry is essential because a sensor might be linked to more than one device, such as for temperature readings.
Thanks!
@nicovon24 Try to use entity queries. There is counting and finding REST endpoints, also with custom rule nodes you can use this backend Java service directly but with some limitations.
Yes but what I mean is the overloading of the platform, if I do this with my locations, areas, assets and customers, with my 100 devices, it is generating so many msgs in the rule chain and it is not good, is there not a better way? Because what i understand, the loops in the rule chains are not good
Well, I relies on rule chain and processing on Activity/Inactivity/Entity Create/Entity Deleted/Entity Asssigned/Entity Unassigned events. Once such event occurs, I count up or down corresponding server attribute on customer level. Then use this attribute on dashboards
I closed this ticket due to inactivity. If this question is still relevant to you, feel free to open a new ticket with a full description of your request.