iobroker.openknx 0.1.8 → 0.1.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -8,28 +8,76 @@
8
8
 
9
9
  [![NPM](https://nodei.co/npm/iobroker.openknx.png?downloads=true)](https://nodei.co/npm/iobroker.openknx/)
10
10
 
11
- **Tests:** ![Test and Release](https://github.com/boellner/ioBroker.openknx/workflows/Test%20and%20Release/badge.svg)
11
+ **Tests:** ![Test and Release](https://github.com/iobroker-community-adapters/ioBroker.openknx/workflows/Test%20and%20Release/badge.svg)
12
12
 
13
-
14
- This adapter serves as communication interface between Iobroker and your KNX IP Gateway.
15
- The adapter allows to generate the iobroker communication objects automatically by importing an ETS group address xml export.
16
- All generated communication objects are initially configured readable and writeable, values are fetched from the knx bus on adapter restart.
13
+ # Deutsch
14
+ Dieser Adapter dient als Kommunikationsschnittstelle zwischen ioBroker und einem KNX IP Gateway.
15
+ Der Adapter ermöglicht die automatische Generierung der ioBroker Datenobjekte durch den Import eines ETS-Gruppenadressen-XML-Exports.
16
+ Alle generierten Kommunikationsobjekte sind zunächst lesbar und schreibbar konfiguriert, Werte werden beim Neustart des Adapters vom knx-Bus geholt.
17
17
 
18
18
  # Installation
19
- This is an early untested version. Please make a good backup of all your data before installation! Please do not test in critical environments.
19
+ Der Adapter ist im latest/beta Repository verfügbar. Wenn dieses in den ioBroker Systemeinstellung ausgewählt ist kann der Adapter in der Adapterliste unter "openknx" gesucht und installiert werden. Eine Alternative ist im Expertenmodus das installieren über das Github Symbol möglich in dem man "von Github" auswählt und nach openknx sucht.
20
+
21
+ # Adapterkonfiguration
22
+ In den Instanzeinstellung muss mindestens die Gateway IP eingetragen werden. Dann kann man ein ETS-Export XML Datei importiert werden. Die XML kann über ETS dem Fenster Gruppenadressen mit Rechtsklick auf den oberen Ebene der Gruppenadresse exportiert werden. GA die keinem DPT zugeordnet sind werden nicht importiert. Es handelt sich dabei um GA die keinem Kommunikationsobjekt in ETS zugeordnet sind.
23
+
24
+ # Nutzung
25
+ ioBroker Datenpunkte können einfach mit ACK false/Nicht Bestätigt gesetzt werden. Komplexe Datenpunkt müssen im korrekt format wie zb: {"priority":0,"data":1} gesetzt werden
26
+
27
+ # Fragen und Diskussion
28
+ https://forum.iobroker.net/topic/50352/test-adapter-openknx-0-1-x
29
+
30
+ # Adaptermigration
31
+
32
+ ## Node Red migrieren
33
+ - Wählen Sie im Menü auf der rechten Seite Exportieren
34
+ - Alle Flows auswählen, herunterladen
35
+ - im Texteditor knx.0 ersetzen mit openknx.0
36
+ - Menü auf der rechten Seite, Import auswählen
37
+ - Geänderte Datei auswählen
38
+ - im Dialog Flows auswählen (Subflows, Configuration-Nodes nur wenn sie betroffen sind) -> neue Tabs werden hinzugefügt
39
+ - alte Flows manuell löschen
40
+
41
+
42
+ ## VIS migrieren
43
+
44
+ - Vis-Editor öffnen
45
+ - Setup -> Projekt-Export/Import -> Normal exportieren
46
+ - Entpacken der Zip-Datei und vis-views.json in einem Editor öffnen
47
+ - Suche Ersetzen knx.0 mit openknx.0
48
+ - Komprimieren Sie vis-views.json und vis-user.css in einer Zip-Datei
49
+ - Setup -> Projekt-Export/Import -> Import
50
+ - Zip-Datei in Drop-Bereich verschieben
51
+ - Projektname = main
52
+ - Projekt importieren
53
+
54
+ ## Skripte migrieren
55
+
56
+ - Skripte öffnen
57
+ - 3 Punkte -> Alle Skripte exportieren
58
+ - Zip-Datei öffnen und den Ordner in einem Editor öffnen
59
+ - Suche knx.0 durch openknx.0 ersetzen
60
+ - alle geänderten Dateien in eine Zip-Datei komprimieren
61
+ - 3 Punkte -> Skripte importieren
62
+ - Zip-Datei in Drop-Bereich verschieben
20
63
 
21
- installation from shell
22
64
 
23
- cd /opt/iobroker/
24
- npm i iobroker.openknx
25
- iobroker add openknx
65
+ ## Grafana migrieren
26
66
 
27
- updates
67
+ - Alle Dashboards durchgehen und Share/Teilen -> Exportieren -> In Datei speichern
68
+ - im Texteditor knx.0 ersetzen. mit openknx.0
69
+ - Um ein Dashboard zu importieren, klicken Sie im Seitenmenü auf das Symbol + und dann auf Importieren.
70
+ - Von hier aus können Sie eine Dashboard-JSON-Datei hochladen
71
+ - Wählen Sie Importieren (Überschreiben)
72
+
28
73
 
29
- npm i iobroker.openknx
30
- iobroker upload openknx
74
+ # English
75
+ This adapter serves as communication interface between Iobroker and your KNX IP Gateway.
76
+ The adapter allows to generate the iobroker communication objects automatically by importing an ETS group address xml export.
77
+ All generated communication objects are initially configured readable and writeable, values are fetched from the knx bus on adapter restart.
31
78
 
32
- Check the npm output for error logs. Stop the openknx adapter before update.
79
+ # Installation
80
+ The adapter is available in the latest / beta repository. If this is selected in the ioBroker system settings, the adapter can be searched in the adapter list under "openknx" and installed by clicking the + Symbol. An alternative is to install in expert mode via the Github symbol by selecting "from Github" and searching for openknx.
33
81
 
34
82
  # Adapter configuration
35
83
  ![settings](docs/pictures/setting.png)
@@ -38,49 +86,89 @@ When starting, the adapter tries to read all GroupAdresses with have the autorea
38
86
  This could take a while and can produce a higher load on your KNX-bus. This ensures that the adapter operates with up-to-date values from the start.
39
87
  Autoread is done on the first connection with the knx bus after an adapter start or restart, not on every knx reconnection.
40
88
  After adapter installation, open the adapter configuration. Fill in:
41
- #### KNX Gateway IP
42
- IP of your KNX/Lan GW
89
+ ### KNX Gateway IP
90
+ IP of your KNX IP gateway.
43
91
 
44
- ##### Port
92
+ ### Port
45
93
  this is normally port 3671 of the KNX IP gateway.
46
94
 
47
- ##### phys. EIB Adress
95
+ ### phys. EIB Adress
48
96
  Fill in physical address of the gateway in the format 1/1/1.
49
97
 
50
- ##### Add only new Objects
98
+ ### Add only new Objects
51
99
  If checked, the import will skip overwriting existing communication objects.
52
100
 
53
- ##### Override object path
54
- The adapter uses openknx.0 for first instance as default path for Iobroker objects.
55
- If your curent setup has a lot of references to existing knx objects to an existing folder, then you can specify its location, for example knx.0.
56
- This feature will be removed in future.
101
+ ### GA XML import
102
+ ![ETS export](docs/pictures/exportGA.png)
103
+ 1. In ETS go to Group Addresses, select export group address and select XML export in latest format version.
104
+ ETS4 Format is not supported, it does not contain DPTs information.
57
105
 
58
- #### GA XML import
59
- 1. In ETS go to Group Addresses, select export group addresse and select XML export in latest format version
60
106
  2. upload your ETS Export XML in the adapter via the GA XML-Import dialog
61
107
  3. Import will immediatelly start after file selection and give a status report after completion.
62
108
  After the successful import a message shows how much objects where recognized. More detailed information could be found in the log.
63
109
 
64
- #### Frames per sec
110
+ Hint on ETS configuration:
111
+ If you have different DPT Subtypes for the GA and in the communication objets that use this GA, then the ETS seems to use the DPT Type with the lowest number. In this case manually ensure that all fields are using the same datatype.
112
+
113
+ ### Frames per sec
65
114
  This settings protects the KNX bus from data flooding by limiting data frames to a certain rate. Not sent frames are put into a fifo buffer.
66
115
 
116
+ # adapter migration
117
+ ## migrate Node Red
118
+ - in right side menu, select Export
119
+ - select All Flows, Download
120
+ - in text editor replace knx.0. with openknx.0.
121
+ - right side menu, select import
122
+ - select changed file
123
+ - in the dialog select Flows (Subflows, Configuration-Nodes only if they are affected) -> new tabs get added
124
+ - delete old flows manually
125
+
126
+ ## migrate VIS
127
+ - Open Vis Editor
128
+ - Setup -> Projekt-Export/import -> Exportieren normal
129
+ - Open Zip File and vis-views.json in an editor
130
+ - Search Replace knx.0. with openknx.0.
131
+ - Compress vis-views.json and vis-user.css in a zip file
132
+ - Setup -> Projekt-Export/import -> Import
133
+ - Move zip file in Drop Area
134
+ - Projektname = main
135
+ - Import project
136
+
137
+ ## migrate Scripts
138
+ - Open Scripts
139
+ - 3 dots -> Export all scripts
140
+ - Open Zip File and open the folder in a editor
141
+ - Search Replace knx.0 with openknx.0
142
+ - compress all changed files in a zip file
143
+ - 3 dots ->Import scripts
144
+ - Move zip file in Drop Area
145
+
146
+
147
+ ## migrate Grafana
148
+ - go through all dashboards and select share - export - save to file
149
+ - in text editor replace knx.0. with openknx.0.
150
+ - To import a dashboard click the + icon in the side menu, and then click Import.
151
+ - From here you can upload a dashboard JSON file
152
+ - select Import (Overwrite)
153
+
67
154
  # howto use the adapter & basic concept
68
- todo
69
155
 
70
- # Compatibility
71
- This adapter has its own namespace 'openknx'.
72
- for existing applications, that are connected to knx signals of other knx adapters you can use the setting:
73
- Override object path
74
- to e.g. knx.0. A new project import will then store the data in this object tree space.
75
- Objects are not compatible, remove them manually before the import and disable all other knx adapters.
76
- Leave setting empty to use the adapters own namespace.
156
+ ### ACK flags
157
+ Application shall not set ack flag, application is notified from this adapter by the ack flag if data is updated.
158
+ KNX Stack sets the ack flag of the linked IoBroker object on receiption of a group address.
159
+ Sent frames on KNX do not result into a ack of the writing object.
160
+
161
+ ### Node Red complex datatype example
162
+ Create a function node that connects to a ioBroker out node that connects with a KNX object of DPT2.
163
+ msg.payload = {"priority":1 ,"data":0};
164
+ return msg;
77
165
 
78
166
  # log level
79
167
  Enable expert mode to enable switching between different log levels. Default loglevel is info.
80
168
  ![loglevel](docs/pictures/loglevel.png)
81
169
 
82
170
  # IOBroker Communication Object description
83
-
171
+ IoBroker defines Objects to hold communication interfaces settings.
84
172
  GA import generates a communication object folder structure following the ga main-group/middle-group scheme. Each groupaddress is an oject with following automatically generated data.
85
173
 
86
174
  IoBroker state roles (https://github.com/ioBroker/ioBroker/blob/master/doc/STATE_ROLES.md) have value 'state' by default. Some more granular values are derieved from the DPT, for example Date or Switch.
@@ -92,8 +180,6 @@ Autoread is set to false where it is clear from the DPT that this is a trigger s
92
180
  "type": "state",
93
181
  "common": { //values here can be interpreted by iobroker
94
182
  "desc": "Basetype: 1-bit value, Subtype: switch", //informative, from dpt
95
- "min": 0, //derieved from dpt
96
- "max": 1, //derieved from dpt
97
183
  "name": "Aussen Melder Licht schalten", //informative description from ets export
98
184
  "read": true, //default set, if false incoming bus values are not updating the object
99
185
  "role": state, //default state, derieved from DPT
@@ -102,7 +188,7 @@ Autoread is set to false where it is clear from the DPT that this is a trigger s
102
188
  "write": true //default true, if set change on object is triggering knx write, succ. write sets then ack flag to true
103
189
  },
104
190
  "native": { //values here can be interpreted by openknx adapter
105
- "address": "0/0/7", //knx address
191
+ "address": "0/1/2", //knx group address
106
192
  "answer_groupValueResponse": false, //default false, if set to true adapter responds with value on GroupValue_Read
107
193
  "autoread": true, //default true for non trigger signals , adapter sends a GroupValue_read on start to sync its states
108
194
  "bitlength": 1, //size ob knx data, derived from dpt
@@ -120,96 +206,126 @@ Autoread is set to false where it is clear from the DPT that this is a trigger s
120
206
  "ts": 1638913951639
121
207
  }
122
208
 
123
-
124
209
  # Adapter communication Interface Description
125
210
  Handeled DPTs are: 1-21,232,237,238
126
211
  Unhandeled DPTs are written as raw buffers, the interface is a sequencial string of hexadecimal numbers. For example write '0102feff' to send values 0x01 0x02 0xfe 0xff on the bus.
127
212
  Where number datatype is used please note that interface values can be scaled.
128
213
 
129
- #### API call
214
+ ### API call
215
+ IoBroker defines States as communication interface.
130
216
 
131
217
  setState(
132
218
  id: string, // object path
133
219
  state: State | StateValue | SettableState,
134
- ack: false, //set to false and will be set to true by KNX stack on send confirmation
220
+ ack: false, //has to be set to false by convention
135
221
  c: 'GroupValue_Read' //optional comment, set this value to trigger a bus read to this object, given StateValue is ignored
136
222
  ): void;
137
223
 
138
-
139
-
140
- #### Description of all DPTs
141
-
142
- |KNX DPT |javascript datatype |special values |value range |
143
- |--- |--- |--- |---|
144
- |DPT-1 |boolean | |false, true|
145
- |DPT-2 |object |{"priority":1 bit,"data":1 bit} |-|
146
- |DPT-3 |object |{"decr_incr":1 bit,"data":2 bit} |-|
147
- |DPT-18 |object |{"save_recall":0,"scenenumber":0} |
148
- |DPT-21 |object |{"outofservice":0,"fault":0,"overridden":0,"inalarm":0,"alarmunack":0} |-|
149
- |DPT-232 |object |{red:0..255, green:0.255, blue:0.255} -|
150
- |DPT-237 |object |{"address":0,"addresstype":0,"readresponse":0,"lampfailure":0,"ballastfailure":0,"convertorerror":0} |-|
151
- |DPT-4 |string ||one character sent as 8-bit character|
152
- |DPT-16 |string ||one character sent as 16-character string|
153
- |DPT-5 |number ||8-bit unsigned value|
154
- |DPT-5.001 |number ||0..100 [%] scaled to 1-byte|
155
- |DPT-5.003 |number ||0..360 [°] scaled to 1-byte|
156
- |DPT-6 |number ||8-bit signed -128..127|
157
- |DPT-7 |number ||16-bit unsigned value|
158
- |DPT-8 |number ||2-byte signed value |-32768..32767|
159
- |DPT-9 |number ||2-byte floating point value|
160
- |DPT-14 |number ||4-byte floating point value|
161
- |DPT-12 |number ||4-byte unsigned value|
162
- |DPT-13 |number ||4-byte signed value|
163
- |DPT-15 |number ||4-byte|
164
- |DPT-17 |number ||1-byte|
165
- |DPT-20 |number ||1-byte|
166
- |DPT-238 |number | |1-byte|
167
- |DPT-10 |number for Date Object ||-|
168
- |DPT-11 |number for Date Object ||-|
169
- |DPT-19 |number for Date Object ||-|
170
- |rest |string |00010203.. |-|
171
-
172
-
173
- Only time and date information is exchanged with KNX time based datatypes, e.g. DPT-19 has unsupported fields for signal quality
224
+ ### Description of all DPTs
225
+ | KNX DPT | javascript datatype | special values | value range | remark |
226
+ | --------- | ---------------------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------------- | --------------------------------------------------- |
227
+ | DPT-1 | boolean | | false, true ||
228
+ | DPT-2 | object | {"priority":1 bit,"data":1 bit} | - ||
229
+ | DPT-3 | object | {"decr_incr":1 bit,"data":2 bit} | - ||
230
+ | DPT-18 | object | {"save_recall":0,"scenenumber":0} | - |Datapoint Type DPT_SceneControl removed from autoread|
231
+ | DPT-21 | object | {"outofservice":0,"fault":0,"overridden":0,"inalarm":0,"alarmunack":0} | - ||
232
+ | DPT-232 | object | {red:0..255, green:0.255, blue:0.255} | - ||
233
+ | DPT-237 | object | {"address":0,"addresstype":0,"readresponse":0,"lampfailure":0,"ballastfailure":0,"convertorerror":0} | - ||
234
+ | DPT-4 | string | | one character sent as 8-bit character ||
235
+ | DPT-16 | string | | one character sent as 16-character string ||
236
+ | DPT-5 | number | | 8-bit unsigned value ||
237
+ | DPT-5.001 | number | | 0..100 [%] scaled to 1-byte ||
238
+ | DPT-5.003 | number | | 0..360 [°] scaled to 1-byte ||
239
+ | DPT-6 | number | | 8-bit signed -128..127 ||
240
+ | DPT-7 | number | | 16-bit unsigned value ||
241
+ | DPT-8 | number | | 2-byte signed value -32768..32767 ||
242
+ | DPT-9 | number | | 2-byte floating point value ||
243
+ | DPT-14 | number | | 4-byte floating point value ||
244
+ | DPT-12 | number | | 4-byte unsigned value ||
245
+ | DPT-13 | number | | 4-byte signed value ||
246
+ | DPT-15 | number | | 4-byte ||
247
+ | DPT-17 | number | | 1-byte | DPT_SceneNumber removed from autoread|
248
+ | DPT-20 | number | | 1-byte ||
249
+ | DPT-238 | number | | 1-byte ||
250
+ | DPT-10 | number for Date Object | | - ||
251
+ | DPT-11 | number for Date Object | | - ||
252
+ | DPT-19 | number for Date Object | | - ||
253
+ | DPT-26 | string | e.g. 00010203.. | - | Datapoint Type DPT_SceneInfo not read by autread|
254
+ | DPT-238 | string | e.g. 00010203.. | - | DPT_SceneConfig not read by autread|
255
+ | rest | string | e.g. 00010203.. | - ||
256
+
257
+ Only time and date information is exchanged with KNX time based datatypes, e.g. DPT-19 has unsupported fields for signal quality.
174
258
 
175
259
  Object send and receive values are of type boolean DPT1), number (scaled, or unscaled), string.
176
260
  DPT 2 'expects a object {"priority":0,"data":1}' receive provides a strinified object of same type.
177
261
  Other joint DPTs have similar object notation.
178
- DPT19 expects a Number from a Date Object, Iobroker can not handle objects, fields of KNX ko that cannot be derived from timestamp are not implemented eg. quality flags
262
+ DPT19 expects a Number from a Date Object, Iobroker can not handle objects, fields of KNX ko that cannot be derived from timestamp are not implemented eg. quality flags.
179
263
 
180
264
  Date and time DPTs (DPT10, DPT11)
181
265
  Please have in mind that Javascript and KNX have very different base type for time and date.
182
266
  DPT10 is time (hh:mm:ss) plus "day of week". This concept is unavailable in JS, so you'll be getting/setting a regular Date Js object, but please remember you'll need to ignore the date, month and year. The exact same datagram that converts to "Mon, Jul 1st 12:34:56", will evaluate to a wildly different JS Date of "Mon, Jul 8th 12:34:56" one week later. Be warned!
183
267
  DPT11 is date (dd/mm/yyyy): the same applies for DPT11, you'll need to ignore the time part.
184
268
 
185
- #### group value write
186
- send is triggered by writing a communication object.
269
+ (KNX specification of DPTs https://www.knx.org/wAssets/docs/downloads/Certification/Interworking-Datapoint-types/03_07_02-Datapoint-Types-v02.02.01-AS.pdf)
270
+
271
+ ### group value write
272
+ Sending is triggered by writing a communication object.
187
273
  Communication object is triggered when a write frame is received on the bus.
188
274
 
189
- #### group value read
275
+ ### group value read
190
276
  Sending can be triggered by writing a communicaton object with comment.
191
- Receiving, if configured will trigger a group value response (limitation: write) of the actual c.o. value, see below
277
+ Receiving, if configured will trigger a group value response (limitation: group value write at the moment) of the actual c.o. value, see below.
192
278
 
193
- #### group value response
194
- Sending Not yet supported. Emulated if response setting is set and adapter writes a group value write.
195
- Receiving will update the value of the iobroker object in read is set to true.
279
+ ### group value response
280
+ If answer_groupValueResponse is set to true, then the adapter will reply with a GroupValue_response to a previously received GroupValue_read request.
196
281
 
197
282
  # Features
198
- * fast import of groupaddresses in XML format
199
- * stable knx stack
200
- * interpretation of many DPTs
201
- * raw read and write of unsupported DPTs
202
- * support of group value read and group value write, group value write as response to group value request
203
- * Autoread
283
+ * stable and reliable knx stack
284
+ * easy interface to group adresses of many DPTs, raw read and write for other DPTs
285
+ * support of KNX group value read and group value write and group value response
204
286
  * free open source
287
+ * no dependencies to cloud services, runs without internet access
288
+ * Autoread on start
289
+ * fast import of group addresses in XML format
290
+ * create joint alias objects that react on status inputs
205
291
 
206
292
  # Known Problems
207
- - sends write instead of GroupValue_Response on GroupValue_Read
293
+ - none
208
294
 
209
295
  # Limitations
210
296
  - only three level group addresses are supported
297
+ - ETS 4 export file format is not supported
211
298
 
212
299
  ## Changelog
300
+ ### 0.1.12 (2021-12-30)
301
+ * feature: improve alias status search algorithm, add units
302
+ * feature: notify user after import if no dpt subtype is set
303
+ * fix: library did not allow to write possible 0 values to certain dpts
304
+ * fix: admin dialog ui fixes, better presentation of some warnings
305
+
306
+
307
+ ### 0.1.11 (2021-12-28)
308
+ * feature: remove more scene DPTs from default autoread
309
+ * feature: sends GroupValue_Response on GroupValue_Read if configured
310
+ * feature: admin dialog with option to generate aliases (beta)
311
+ * feature: admin dialog reactivates after adapter reset
312
+ * feature: add support for DPT 7.600
313
+ * feature: show logs of knx library
314
+ * fix: filter out logs with device address bus interactions
315
+ * fix: filter ga names that are forbidden in IOB
316
+ * fix: reply with groupvalueresponse on request, not with groupvaluewrite
317
+ * fix: remove more scene dpts from autoread
318
+
319
+ ### 0.1.10 (2021-12-24)
320
+ * fix: interface to write objects corrected
321
+
322
+ ### 0.1.9 (2021-12-22)
323
+ * fix: algorith to generate the iob objects improved
324
+ * fix: min max removed for boolean
325
+ * fix: ackqnowledgement handling
326
+ * removed feature: override path of knx objects
327
+ * feature: new logo
328
+
213
329
  ### 0.1.8
214
330
  * (tombox) feature: changed ui and many fixes
215
331
  * (boellner) feature: skip wrong initial disconnect warning
@@ -247,7 +363,6 @@ Receiving will update the value of the iobroker object in read is set to true.
247
363
  * (boellner) feature: import ga xml
248
364
 
249
365
  ## License
250
-
251
366
  GNU GENERAL PUBLIC LICENSE
252
367
  ==========================
253
368
  Copyright (c) 2021 boellner
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "So exportieren Sie GA-XML aus der ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj werden nicht unterstützt, bitte öffnen Sie in der ETS die Gruppenadressen und klicken Sie mit der rechten Maustaste auf Gruppenadressen und dann Gruppenadressen-Export",
8
8
  "Port": "Hafen",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex zum Erkennen von Status-GAs (Endung mit status, rm, rückmeldung..) Leer zum Deaktivieren",
9
10
  "Restarting adapter": "Adapter neu starten...",
10
11
  "Unsupported file format": "Nicht unterstütztes Dateiformat",
11
12
  "add only new Objects": "Nur neue Objekte hinzufügen",
@@ -13,10 +14,10 @@
13
14
  "invalid port number": "ungültige Portnummer",
14
15
  "local network interface": "lokale Netzwerkschnittstelle",
15
16
  "min 1": "Minimum ist 1",
16
- "override object path": "Objektpfad überschreiben",
17
+ "override object path": "",
17
18
  "physical KNX address": "physikalische KNX-Adresse",
18
19
  "physical KNX address in format a/b/c not valid": "physikalische KNX-Adresse im Format a/b/c ungültig",
19
20
  "this is not a number": "das ist keine Zahl",
20
- "using old knx path for objects": "Verwenden des alten knx-Pfads für Objekte",
21
- "using old knx path for objects (Before importing, delete old objects manually)": "alten knx-Pfad für Objekte verwenden (Vor dem Import alte Objekte manuell löschen)"
21
+ "using old knx path for objects": "",
22
+ "using old knx path for objects (Before importing, delete old objects manually)": ""
22
23
  }
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "How to export GA XML from ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export",
8
8
  "Port": "Port",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex to identify Status GAs (ending with status, rm, rückmeldung..) Empty to deactivate",
9
10
  "Restarting adapter": "Restarting adapter...",
10
11
  "Unsupported file format": "Unsupported file format",
11
12
  "add only new Objects": "Add only new Objects",
@@ -13,10 +14,10 @@
13
14
  "invalid port number": "invalid port number",
14
15
  "local network interface": "local network interface",
15
16
  "min 1": "minimum is 1",
16
- "override object path": "override object path",
17
+ "override object path": "",
17
18
  "physical KNX address": "physical KNX address",
18
19
  "physical KNX address in format a/b/c not valid": "physical KNX address in format a/b/c not valid",
19
20
  "this is not a number": "this is not a number",
20
- "using old knx path for objects": "using old knx path for objects",
21
- "using old knx path for objects (Before importing, delete old objects manually)": "using old knx path for objects (Before importing, delete old objects manually)"
21
+ "using old knx path for objects": "",
22
+ "using old knx path for objects (Before importing, delete old objects manually)": ""
22
23
  }
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "Cómo exportar GA XML desde ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj no es compatible, abra en ETS las direcciones del grupo y haga clic con el botón derecho en las direcciones del grupo y luego exportar la dirección del grupo.",
8
8
  "Port": "Puerto",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex para identificar estados GA (terminando con status, rm, rückmeldung ..). ",
9
10
  "Restarting adapter": "Reiniciando el adaptador ...",
10
11
  "Unsupported file format": "Formato de archivo no soportado",
11
12
  "add only new Objects": "Agregar solo nuevos objetos",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "Comment exporter GA XML depuis ETS :",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj ne sont pas pris en charge, veuillez ouvrir dans ETS les adresses de groupe et faites un clic droit sur les adresses de groupe, puis exportez l'adresse de groupe",
8
8
  "Port": "Port",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex pour identifier les Status GA (se terminant par status, rm, rückmeldung..). ",
9
10
  "Restarting adapter": "Redémarrage de l'adaptateur...",
10
11
  "Unsupported file format": "Format de fichier non pris en charge",
11
12
  "add only new Objects": "Ajouter uniquement de nouveaux objets",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "Come esportare GA XML da ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj non sono supportati, aprire in ETS gli indirizzi di gruppo e fare clic con il pulsante destro del mouse sugli indirizzi di gruppo e quindi esportare gli indirizzi di gruppo",
8
8
  "Port": "Porta",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex per identificare gli Status GA (che termina con status, rm, rückmeldung..). ",
9
10
  "Restarting adapter": "Riavvio dell'adattatore...",
10
11
  "Unsupported file format": "Formato file non supportato",
11
12
  "add only new Objects": "Aggiungi solo nuovi oggetti",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "GA XML exporteren vanuit ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj worden niet ondersteund, open in ETS de groepsadressen en klik met de rechtermuisknop op groepsadressen en exporteer groepsadressen",
8
8
  "Port": "Haven",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex om Status GA's te identificeren (eindigend met status, rm, rückmeldung..). ",
9
10
  "Restarting adapter": "Adapter opnieuw opstarten...",
10
11
  "Unsupported file format": "Niet ondersteund bestandsformaat",
11
12
  "add only new Objects": "Alleen nieuwe objecten toevoegen",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "Jak wyeksportować GA XML z ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj nie są obsługiwane, otwórz w ETS adresy grup i kliknij prawym przyciskiem adresy grup, a następnie wyeksportuj adresy grup",
8
8
  "Port": "Port",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex do identyfikacji statusów GA (kończących się na status, rm, rückmeldung...). ",
9
10
  "Restarting adapter": "Ponowne uruchamianie adaptera...",
10
11
  "Unsupported file format": "Niewspierany format pliku",
11
12
  "add only new Objects": "Dodaj tylko nowe obiekty",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "Como exportar GA XML do ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj não são suportados, por favor, abra no ETS o Group Adresses e clique com o botão direito nos endereços de grupo e então a exportação de endereço de grupo",
8
8
  "Port": "Porta",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Regex para identificar Status GAs (terminando com status, rm, rückmeldung ..). ",
9
10
  "Restarting adapter": "Reiniciando o adaptador ...",
10
11
  "Unsupported file format": "Formato de arquivo não suportado",
11
12
  "add only new Objects": "Adicionar apenas novos objetos",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "Как экспортировать GA XML из ETS:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "KNXproj не поддерживаются, откройте в ETS групповые адреса и щелкните правой кнопкой мыши по групповым адресам, а затем экспортируйте групповые адреса.",
8
8
  "Port": "Порт",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "Регулярное выражение для определения GA состояния (заканчивающееся на status, rm, rückmeldung ..). ",
9
10
  "Restarting adapter": "Перезапуск адаптера ...",
10
11
  "Unsupported file format": "Неподдерживаемый формат файла",
11
12
  "add only new Objects": "Добавляйте только новые объекты",
@@ -6,6 +6,7 @@
6
6
  "How to export GA XML from ETS:": "如何从 ETS 导出 GA XML:",
7
7
  "KNXproj are not supported, please open in ETS the Group Adresses and right click on group addresses and then group adresse export": "不支持KNXproj,请在ETS中打开群组地址,右键点击群组地址,然后群组地址导出",
8
8
  "Port": "港口",
9
+ "Regex to identify Status GAs (ending with status, rm, rückmeldung..). Empty to deactivate": "用于识别状态 GA 的正则表达式(以状态、rm、rückmeldung 结尾...)。",
9
10
  "Restarting adapter": "重新启动适配器...",
10
11
  "Unsupported file format": "不支持的文件格式",
11
12
  "add only new Objects": "仅添加新对象",