You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Allows customisation of the attributes and/or configuration items that are sent to the central instance on a per asset & attribute basis (wildcards can also be used)
47
+
1. Until we have a UI to do this configuration you will need to write/copy/paste JSON into the textarea using the following schema:
48
+
```
49
+
{
50
+
"*": { <-- Applies to all assets
51
+
"excludeAttributes": ["notes"],
52
+
"excludeAttributeMeta": {
53
+
"*": ["accessPublicRead"],
54
+
"location": [] <-- Don't exclude any meta items for location attribute
55
+
},
56
+
"addAttributeMeta": {
57
+
"*": { <-- MetaMap
58
+
"accessRestrictedRead": true
59
+
},
60
+
}
61
+
},
62
+
"CityAsset": {
63
+
"excludeAttributes": ["city"]
64
+
}
65
+
}
66
+
```
67
+
3. If a definition exists for a specific asset type or attribute then that should be used instead of any * wildcard definition
68
+
4. If a definition exists for a specific attribute within `excludeMetaItems` then that should be used instead of any * wildcard definition
69
+
70
+

71
+
45
72
## Interaction with Gateway Manager UI via Gateway tunnels
46
73
47
74
On top of the Interaction via the Gateway, you can remotely access the full Manager UI of the Gateway instances of OpenRemote, by creating Gateway tunnels. Note that you first have to [technically configure the (edge) gateway and central instance of OpenRemote to enable the tunnelling set-up](../../developer-guide/gateway-tunnelling-setup.md). Next you can access the Manager UI of the Gateway instance via the 'Gateway Tunnels' (Settings) or via a 'Gateway Widget' on the Insights dashboards.
0 commit comments