-
Notifications
You must be signed in to change notification settings - Fork 11
/
Copy pathzenoh-config-client.json5
110 lines (95 loc) · 3.67 KB
/
zenoh-config-client.json5
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
/*
# SPDX-FileCopyrightText: 2023 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# SPDX-License-Identifier: Apache-2.0
*/
{
plugins: {
////
//// MQTT related configuration
//// All settings are optional and are unset by default - uncomment the ones you want to set
////
// mqtt: {
////
//// port: The address to bind the MQTT server. Default: "0.0.0.0:1883". Accepted values:'
//// - a port number ("0.0.0.0" will be used as IP to bind, meaning any interface of the host)
//// - a string with format `<local_ip>:<port_number>` (to bind the MQTT server to a specific interface).
////
// port: "0.0.0.0:1883",
////
//// scope: A string added as prefix to all routed MQTT topics when mapped to a zenoh resource.
//// This should be used to avoid conflicts when several distinct MQTT systems using
//// the same topics names are routed via zenoh.
////
// scope: "home-1",
////
//// allow: A regular expression matching the MQTT topic name that must be routed via zenoh. By default topics are allowed.
//// If both '--allow' and '--deny' are set a topic will be allowed if it matches only the 'allow' expression.
////
// allow: "zigbee2mqtt|home-1/room-2",
////
//// deny: A regular expression matching the MQTT topic name that must not be routed via zenoh. By default no topics are denied.
//// If both '--allow' and '--deny' are set a topic will be allowed if it matches only the 'allow' expression.
////
// deny: "zigbee2mqtt|home-1/room-2",
////
//// generalise_subs: A list of key expression to use for generalising subscriptions.
////
// generalise_subs: ["SUB1", "SUB2"],
////
//// generalise_subs: A list of key expression to use for generalising publications.
////
// generalise_subs: ["PUB1", "PUB2"],
// },
////
//// REST API configuration (active only if this part is defined)
////
// Optionally, add the REST plugin
// rest: { http_port: 8000 },
},
////
//// zenoh related configuration (see zenoh documentation for more details)
////
////
//// id: The identifier (as hex-string) that zenoh-bridge-mqtt must use. If not set, a random UUIDv4 will be used.
//// WARNING: this id must be unique in your zenoh network.
// id: "A00001",
////
//// mode: The bridge's mode (peer or client)
////
mode: "client",
////
//// Which endpoints to connect to. E.g. tcp/localhost:7447.
//// By configuring the endpoints, it is possible to tell zenoh which router/peer to connect to at startup.
////
connect: {
endpoints: [
"tcp/fms-zenoh-router:7447"
]
},
////
//// Which endpoints to listen on. E.g. tcp/localhost:7447.
//// By configuring the endpoints, it is possible to tell zenoh which are the endpoints that other routers,
//// peers, or client can use to establish a zenoh session.
////
listen: {
endpoints: [
//"tcp/127.0.0.1:7447"
]
},
}