base_historian parameter 'device_data_filter' does not work when there are devices and subdevices

[schandrika]

base_historian has a 'device_data_filter' if we want to collect only certain points in a device. The format is {"device_name":[point1, point2], "device_2": [point1, point2] } The way matching is done breaks when the list contains both device and a subdevice. For example, the config

{"AHU1":['point1', 'point2'], "AHU1/VAV1": ['point1', 'point2'] }

captures points of AHU1 but not AHU1/VAV1.

Also if config has a trailing "/" in device name the match fails.

[rlutes]

So the way this is used in practice is to limit the points based on a device type. For example let us say that we have a building with 3 AHUs each with roughly 25 VAVs. We might do the following: { "AHU":['point1', 'point2'], "VAV": ['point3', 'point4'] } So, this would capture point1 and point2 for all AHUs and omit any other trended data from the AHUs. It would also capture point3 and point4 for all the VAVs for all the AHUs but omit the remaining trended data from the db.

This is functionality that we would like to keep if an update is made