iobroker.zigbee 2.0.5 → 3.0.1
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 +22 -3
- package/admin/admin.js +420 -115
- package/admin/index_m.html +285 -229
- package/admin/tab_m.html +108 -91
- package/docs/de/img/Bild30.png +0 -0
- package/docs/de/img/Bild38.png +0 -0
- package/docs/de/img/Info.png +0 -0
- package/docs/de/img/Zigbee_config_de.jpg +0 -0
- package/docs/de/img/battery.png +0 -0
- package/docs/de/img/debug.png +0 -0
- package/docs/de/img/delete.png +0 -0
- package/docs/de/img/disconnected.png +0 -0
- package/docs/de/img/edit_grp.png +0 -0
- package/docs/de/img/edit_image.png +0 -0
- package/docs/de/img/grp_nok.png +0 -0
- package/docs/de/img/grp_ok.png +0 -0
- package/docs/de/img/on_off.png +0 -0
- package/docs/de/img/reconfigure.png +0 -0
- package/docs/de/readme.md +52 -43
- package/docs/en/img/Zigbee_config_en.png +0 -0
- package/docs/en/img/Zigbee_pairing_en.png +0 -0
- package/docs/en/readme.md +66 -66
- package/io-package.json +32 -31
- package/lib/DeviceDebug.js +2 -1
- package/lib/commands.js +203 -40
- package/lib/devices.js +2 -2
- package/lib/exposes.js +8 -30
- package/lib/groups.js +1 -1
- package/lib/localConfig.js +33 -10
- package/lib/networkmap.js +2 -1
- package/lib/seriallist.js +9 -2
- package/lib/statescontroller.js +185 -91
- package/lib/utils.js +41 -11
- package/lib/zbDeviceConfigure.js +10 -3
- package/lib/zigbeecontroller.js +121 -94
- package/main.js +135 -73
- package/package.json +8 -8
- package/docs/en/img/Bild23.png +0 -0
- package/docs/en/img/Bild25.png +0 -0
- package/docs/en/img/Bild26.png +0 -0
- package/docs/en/img/Bild4.png +0 -0
- package/docs/en/img/Bild9.png +0 -0
package/docs/en/readme.md
CHANGED
|
@@ -1,30 +1,20 @@
|
|
|
1
|
-
# ioBroker
|
|
2
|
-
|
|
1
|
+
# ioBroker Adapter for ZigBee Devices
|
|
2
|
+
Using a ZigBee network coordinator, a dedicated ZigBee network is created, to which ZigBee devices (lights, dimmers, sensors, etc.) can join. Thanks to direct interaction with the coordinator, the ZigBee adapter allows the devices to be controlled without any gateways/bridges from the manufacturers (Xiaomi/Tradfri/Hue). Additional information about ZigBee can be found [here](https://github.com/Koenkk/zigbee2mqtt/wiki/ZigBee-network).
|
|
3
3
|
|
|
4
4
|
## Hardware
|
|
5
|
-
|
|
5
|
+
The coordinator (see above) requires additional hardware that enables the conversion between USB and ZigBee wireless signals. There are three types of coordinators:
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
7
|
+
- Plug-in modules for the Raspberry Pi (The use of these modules is **not** recommended.)
|
|
8
|
+
- USB-connected modules, either in the form of development boards or USB sticks
|
|
9
|
+
- Network coordinators
|
|
9
10
|
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
11
|
+
A complete list of compatible coordinators can be found [here](https://www.zigbee2mqtt.io/guide/adapters/). We recommend using only coordinators listed as 'recommended'. Instructions for installing the required firmware can also be found there.
|
|
15
12
|
|
|
13
|
+
Coordinators are also sold with pre-installed firmware. The following applies: **Any coordinator whose firmware is compatible with Zigbee2mqtt.io can also be used with the ZigBee adapter**.
|
|
16
14
|
|
|
17
|
-
|
|
18
|
-
The required flasher/programmer and the process of preparation are described [here](https://github.com/Koenkk/zigbee2mqtt/wiki/Getting-started) or [here (Russian)](https://github.com/kirovilya/ioBroker.zigbee/wiki/%D0%9F%D1%80%D0%BE%D1%88%D0%B8%D0%B2%D0%BA%D0%B0).
|
|
19
|
-
|
|
20
|
-
The "Sonoff ZIGBEE 3.0 USB STICK CC2652P" is becoming increasingly popular:
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
- Flashing of suitable firmware is not absolutely necessary (hardware is already delivered with suitable firmware)
|
|
24
|
-
- Supports the newer ZigBee 3.0 standard
|
|
25
|
-
|
|
26
|
-
The devices connected to the ZigBee network transmit their status to the coordinator and notify it of events (button press, motion detection, temperature change, ...). This information is displayed in the adapter under the respective ioBroker objects and can thus be further processed in ioBroker. It is also possible to send commands to the ZigBee device (change of status of sockets and lamps, color and brightness settings, ...).
|
|
15
|
+
Currently (as of March 2025), the "Sonoff ZIGBEE 3.0 USB-STICK CC2652P" (both the CC2652P and EZSP chipset versions) and network coordinators with Cod.m and/or XTG firmware are particularly popular. The Conbee II and Conbee III are also frequently used. The use of TI coordinators with CC2530/CC2531 is strongly discouraged – these are now considered obsolete.
|
|
27
16
|
|
|
17
|
+
The devices connected to the ZigBee network transmit their status to the coordinator and notify them of events (button presses, motion detection, temperature changes, etc.). This information is displayed in the adapter under the respective ioBroker objects and can thus be further processed in ioBroker. It is also possible to send commands to the ZigBee device (change of status of sockets and lamps, color and brightness settings, etc.).
|
|
28
18
|
|
|
29
19
|
## Software
|
|
30
20
|
|
|
@@ -39,36 +29,45 @@ The software is divided into "converter" and "adapter".
|
|
|
39
29
|
- Adapter<br>
|
|
40
30
|
This software part is the connection of the converter to ioBroker. The [adapter](https://github.com/ioBroker/ioBroker.zigbee) includes the graphical user interface for managing the ZigBee devices and the creation of ioBroker objects for controlling the ZigBee devices.
|
|
41
31
|
|
|
42
|
-
|
|
32
|
+
|
|
43
33
|
## Installation
|
|
44
|
-
1.
|
|
45
|
-
2.
|
|
46
|
-
3.
|
|
47
|
-
|
|
48
|
-
`ls -la /dev/serial/by-id/`
|
|
34
|
+
1. Connect the coordinator hardware to computer running ioBroker (or the network, in case of LAN/WLan coordinators).<br>
|
|
35
|
+
2. Open a console on the server. In case of Unix/Linux based systems, this can be done remotely via ssh. Depending on the OS used, additional programs (e.g. puTTY on Windows) may be needed.<br>
|
|
36
|
+
3. Determine the coordinator path. On Unix/Linux systems, this is often located in the /dev/serial/by-id directory. Alternatively, /dev/ttyUSB*, /dev/ttyAM* (Unix/Linux), /dev/tty.usbserial-* (macOS), or com* (Windows) are expected.<br>
|
|
37
|
+
The following example shows a Linux installation on a Raspberry Pi. The command `ls -la /dev/serial/by-id/` produces the output shown in the image.
|
|
49
38
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
39
|
+
4. ioBroker -> Install the ZigBee adapter, here version 1.8.10 as an example. <br>  <br> This installs all required software components (converter and adapter). <br><br>
|
|
40
|
+
5. Open the adapter configuration. The above image shows the interface version 3.0.0 or newer.
|
|
41
|
+
In this situation, the admin indicates whether the ZigBee subsystem is started (A).
|
|
42
|
+
6. Enter the port for the coordinator (B). In the case of USB coordinators, this is the previously determined device path. For coordinators controlled via the network, the network address and port must be specified in the form tcp://ip:port instead of the device path. If the adapter itself (not the Zigbee subsystem) is active, a list of available serial interfaces is available for selection. The following applies when selecting:
|
|
43
|
+
- If multiple adapters with different USB devices are used for communication on the system, a port from the /dev/serial/by-id directory (if available) should **absolutely** be selected. This ensures that the adapter's association with the coordinator is retained when the system is restarted.
|
|
44
|
+
- If only one USB device is used, the /dev/TTY* port is preferable. This allows the coordinator to be replaced with an identical device in the event of a defect without having to adjust the configuration.
|
|
45
|
+
7. Assign a Network ID and Pan ID to distinguish it from other ZigBee networks within wireless range. e.g., starting with adapter version 2.1.0, ExtPanID (C) and PanID (D) are automatically pre-assigned with random values until the configuration is saved.<br>
|
|
46
|
+
8. Select a suitable ZigBee channel (E). Please note that ZigBee and 2.4GHz Wi-Fi share the same frequency band. The optimal channel therefore depends, among other things, on the Wi-Fi channels used in the area. The channel names for ZigBee and Wi-Fi are **not** identical, e.g. WIFI channel 11 and Zigbee channel 11 do **not** interfere with each other. It is also advisable to limit your selection to the ZigBee Light Link channels (11, 15, 20, 25). If a channel is selected that does not belong to the ZLL, the interface displays a yellow triangle with an exclamation mark above the entered channel. <br>After the adapter has been successfully started, a scan of the network channels can also be performed via the configuration.<br>
|
|
47
|
+
**Note:** Starting with adapter version 2.1.0, it is possible to change the channel without deleting the configuration and re-learning all devices. However, **this feature is considered experimental** – individual devices may not respond to the channel change; these devices will then need to be re-learned.<br>
|
|
48
|
+
9. Check whether the Zigbee subsystem is starting. To do this, try starting the Zigbee subsystem using *Start/Stop* (F). The progress of the start attempt can be observed in the log. The icon (A) changes from black/red to black/orange while the Herdsman starts. If the attempt was successful, the icon disappears completely; otherwise, it turns red again, and the messages in the log provide clues as to the cause.<br>
|
|
49
|
+
The Herdsman can also be stopped using the same button. The icon is also displayed in black/orange. **Important: Stopping can take up to 2 minutes in some cases – especially when using network coordinators.** Patience is required here. After Herdsman has been terminated, the icon appears in black/red and the message 'Herdsman stopped!' appears.
|
|
50
|
+
Depending on the error, there are various possible reasons why Herdsman may not start. If it is 'just' a timeout, it is certainly advisable to repeat the attempt immediately. If the configuration is inconsistent, the relevant data is displayed in the log. The adapter offers two options for resolving the conflict:
|
|
51
|
+
- Reading the data from the NV backup. In this case, the adapter's configuration is adjusted.
|
|
52
|
+
- Deleting the NV backup. In this case, the adapter's configuration remains as it is. This **forces** a rebuild of the network, which subsequently requires all previously trained devices to be reset and retrained.<br>
|
|
53
|
+
The log output can also be used to search for a solution in the [ioBroker Forum](https://forum.iobroker.net). Please highlight the messages and post them **as text** in the forum.
|
|
55
54
|
|
|
56
55
|
## Pairing
|
|
57
56
|
Each ZigBee device (switch, bulb, sensor, ...) must be paired with the coordinator (pairing): <br>
|
|
58
57
|
|
|
59
58
|
- ZigBee device:
|
|
60
59
|
Each ZigBee device can only be connected to exactly 1 ZigBee network. If the ZigBee device still has pairing information saved for a different coordinator (e.g. Philips Hue Bridge), then it must first be decoupled from this ZigBee network. This decoupling from the old ZigBee network preferably is done via the user interface of the old ZigBee network (z.B. Philips Hue App). Alternatively, you can reset the ZigBee device to factory settings. <br>
|
|
61
|
-
There are typically the following options for putting a ZigBee device into pairing mode <br>
|
|
60
|
+
There are typically the following options for putting a ZigBee device into pairing mode <br>
|
|
62
61
|
1. Unpair a ZigBee device from a ZigBee network
|
|
63
|
-
2. Press the pairing button on the ZigBee device
|
|
62
|
+
2. Press the pairing button on the ZigBee device
|
|
64
63
|
3. Switch the supply voltage of the ZigBee device off and then on again
|
|
65
64
|
|
|
66
|
-
|
|
65
|
+
|
|
67
66
|
The ZigBee device is then in pairing mode for typically 60 seconds. Similar to the procedure for resetting to factory settings, activating the pairing mode also depends on the respective device type (if necessary, read the operating instructions of the ZigBee device).
|
|
68
67
|
|
|
69
68
|
- Coordinator:
|
|
70
69
|
Press the green button to put the coordinator into pairing mode for 60 seconds. <br>
|
|
71
|
-
|
|
72
71
|
|
|
73
72
|
- Wait until "New device joined" appears in the dialog: <br>
|
|
74
73
|
|
|
@@ -81,48 +80,49 @@ The device to be paired must be supported by the ioBroker ZigBee adapter. In the
|
|
|
81
80
|
|
|
82
81
|
## Pairing of unknown ZigBee devices so far
|
|
83
82
|
|
|
84
|
-
|
|
85
|
-
 <br>
|
|
83
|
+
For previously unknown ZigBee devices, the ZigBee name of the ZigBee device (e.g., HOMA1001) appears during pairing with the suffix "supported": false. <br>
|
|
86
84
|
 <br>
|
|
87
85
|
|
|
88
|
-
|
|
86
|
+
Rotating this tile provides detailed information about the ZigBee device: <br>
|
|
89
87
|
  <br>
|
|
90
88
|
|
|
91
|
-
After registering at [github.com](https://github.com/ioBroker/ioBroker.zigbee/issues) the missing ZigBee device
|
|
89
|
+
After registering at [github.com](https://github.com/ioBroker/ioBroker.zigbee/issues), the missing ZigBee device can be reported via an "issue":
|
|
92
90
|
|
|
93
91
|
 <br>
|
|
94
92
|
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
After modifying the relevant files, the ZigBee adapter must be restarted, and the ZigBee device must be unpaired from the coordinator:
|
|
98
|
-
 <br>
|
|
99
|
-
After that, the pairing can be repeated. Target state after pairing: <br>
|
|
100
|
-
 <br>
|
|
101
|
-
|
|
102
|
-
With some ZigBee devices, it is necessary to display all software interfaces ("exposes") of the new ZigBee device in the ioBroker objects in order to be able to use all the functions of this ZigBee device. In such cases, the new ZigBee device must be included in the "Exclude" group.
|
|
103
|
-
|
|
104
|
-
 <br>
|
|
105
|
-
|
|
106
|
-
 ->  ->  -> select ZigBee device (e.g. HOMA1001) ->  <br>
|
|
107
|
-
After restarting the ZigBee adapter, the new ZigBee device should now work without restrictions.
|
|
93
|
+
Include the detailed information about the tile (see above) in the issue, create a brief documentation (preferably in English), and submit it. A developer will then respond to the issue.
|
|
108
94
|
|
|
95
|
+
One of two options is possible as a result:
|
|
96
|
+
- Adapting to the Zigbee Herdsman converter. This requires an updated version of the Zigbee adapter, which is first tested and then made available in the Latest Repository.
|
|
97
|
+
- Creating an "external converter" – a file with JS code that can be copied to the Zigbee adapter's data directory and specified in the adapter's configuration.
|
|
98
|
+
In both cases, restarting the adapter is sufficient – the adapter's correspondingly adapted data points will be created. If data points are no longer supported, they will be highlighted in orange, and the adapter will display a button for deleting the orphaned data points.
|
|
109
99
|
|
|
110
100
|
|
|
111
101
|
## Symbols within the ZigBee adapter
|
|
112
|
-
|
|
102
|
+
|
|
113
103
|
| Icon | Description |
|
|
114
104
|
|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
115
|
-
| 
|
|
116
|
-
|  | **State Cleanup** <br> Deletes unconnected ioBroker objects. These can be created by the "Exclude" operation. |
|
|
106
|
+
|  | **Show stashed errors** <br> Displays accumulated error messages that occur repeatedly. This icon is only visible if the system has suppressed recurring error messages and serves to alert the user to their existence. |
|
|
107
|
+
|  | **Check for Firmware Updates** <br> The Zigbee adapter supports OTA firmware upgrades, provided the connected devices support them. This button initiates the check for newer firmware – the actual upgrade must then be initiated individually on each device. |
|
|
108
|
+
|  | **Add Group** <br>The Zigbee specification supports the creation of groups of devices that can be controlled together via a single command. While the specification supports almost any command as group commands, the implementation in the Zigbee adapter is limited to light bulbs - this button can be used to create a new group. Members can be added and removed via the devices |
|
|
109
|
+
|  | **Reset and pair Touchlink** <br> Touchlink is a function of the Zigbee Light Link (ZLL) that allows devices that are physically close to one another to communicate with each other without being connected to a coordinator. This function is not supported by all devices. To reset a Zigbee device to factory settings via Touchlink, bring the device close (< 10 cm) to the Zigbee coordinator and then press the green symbol. **Warning** If the Touchlink reset process is not carried out correctly, devices located further away may also be reset. If in doubt, it is advisable to briefly unplug any affected devices. |
|
|
110
|
+
|  | **Pairing with a QR Code** <br>There are devices that require an additional security code to pair with a network. This is usually provided as a QR code on the device and/or in the instructions. Pairing with these devices is only possible if the corresponding code has been entered beforehand. **Note** Many instructions specify QR codes that should be read with the manufacturer-specific app in order to connect the device to the manufacturer's gateway, even though the devices do not support a security code. In this case, the adapter displays an error when you try to enter the code. If this happens, it makes sense to try to program the device 'normally'. |
|
|
111
|
+
|  | **Pairing** <br> Start the pairing process for new ZigBee devices. Pressing this button opens the network for a (configurable) time between 10 and 250 seconds so that new devices can be added to the network.
|
|
112
|
+
## Device tiles
|
|
113
|
+
| Icon | Description |
|
|
114
|
+
|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
115
|
+
|  | Time since a data exchange last took place with this ZigBee device. |
|
|
116
|
+
|  | Battery level, if the device reports a battery level. |
|
|
117
|
+
| <br> | Strength of the ZigBee radio signal on this ZigBee device (<10 poor, <50 medium, >50 good). ZigBee is a wireless mesh network. Most mains-powered ZigBee devices (e.g., Philips Hue lamps) can act as ZigBee routers, i.e., as wireless nodes. ZigBee devices therefore do not necessarily have to establish a direct wireless connection to the coordinator, but can instead use any router in the network for a wireless connection. With each ZigBee router, the wireless range of the network is extended. All ZigBee devices regularly check whether there is a better wireless route and automatically switch over. However, this process can take several minutes.<br>Manually assigning devices to routers is **not** possible.<br> The red, crossed-out symbol is displayed when a device is considered 'not connected'. |
|
|
118
|
+
|   | Status of a group <br> A green circle indicates that a group has members and is functional; the red X appears when a group is empty or unusable for other reasons. |
|
|
119
|
+
|  | Info <br> Opens the information display for the device. The information shown on this page comes directly from the device. It is also available for unknown devices. |
|
|
120
|
+
|  | Debug device <br> Enables / disables the generation of extended debug messages for this device. The color of the icon indicates the current status: (Black/White: no debug messages, Green: debug messages - can be deactivated with this button. Orange: debug messages via filter under zigbee.x.info.debugmessages. |
|
|
121
|
+
|  | On/Off <br> This button can be used to activate/deactivate a device. No communication takes place with deactivated devices. |
|
|
122
|
+
|  | Assign image/name <br> This button allows you to specify a custom image and/or name for the device based on the device or device type. Settings made in this way are retained even if the device is deleted. |
|
|
123
|
+
|  | Edit name/groups <br> This button can be used to change the name of a device and - if applicable - the assignment of the device to one or more groups. |
|
|
124
|
+
|  | Delete device <br> Starts the deletion process for this device. |
|
|
124
125
|
## Additional information
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
126
|
+
The Zigbee-Adapter shares the same libraries (zigbee-herdsman, zigbee-herdsman-converters) asn the [Zigbee2mqtt](https://www.zigbee2mqtt.io/) Project ([Github Link](https://github.com/Koenkk/zigbee2mqtt)). It is possible to use zigbee2mqtt.io directly with ioBroker using MQTT or its own [Adapter](https://github.com/arteck/ioBroker.zigbee2mqtt).<br>
|
|
127
|
+
As the libraries are shared, any device supported in zigbee2mqtt.io will in time also be supported in the Zigbee Adapter. Due to the need for compatibility-checks, this can occur with a delay of a few days or weeks. Generating an issue describing the device and its zigbee2mqtt.io integration usually leads to either a temporary solution or an adapter update to include the support in the zigbee Adapter.<br>
|
|
128
|
+
Other topics related to this adapter are also documented in the associated [wiki](https://github.com/ioBroker/ioBroker.zigbee/wiki).
|
package/io-package.json
CHANGED
|
@@ -1,8 +1,34 @@
|
|
|
1
1
|
{
|
|
2
2
|
"common": {
|
|
3
3
|
"name": "zigbee",
|
|
4
|
-
"version": "
|
|
4
|
+
"version": "3.0.1",
|
|
5
5
|
"news": {
|
|
6
|
+
"3.0.1": {
|
|
7
|
+
"en": "Fix for Ikea SOMRIG configuration raising 'definition.endpoint is not a function' error.\nAccess to 'zigbee2mqtt options as settings in zigbee adapter (ALPHA Stage !)\nFix for 'error: zigbee.0 (1118300) zigbee.0 already running' at adapter start (Alpha Stage)\nUpdated hardware configuration panel - exchanged text buttons for buttons with icons.\nLimited states on device tiles to states which are read only or which can be modified sensibly via the device tile.\n",
|
|
8
|
+
"de": "Fix für Ikea SOMRIG Konfiguration erhöhen 'Definition. Endpoint ist kein Funktionsfehler.\nZugriff auf 'zigbee2mqtt Optionen als Einstellungen im Zickbee Adapter (ALPHA Stage!)\nFix für 'error: zigbee.0 (1118300) zigbee.0 bereits läuft' bei Adapterstart (Alpha Stage)\nAktualisiertes Hardware-Konfigurationsfeld - ausgetauschte Texttasten für Tasten mit Symbolen.\nBegrenzte Zustände auf Gerätefliesen zu Zuständen, die nur gelesen werden oder über die Gerätefliese sensibel modifiziert werden können.\n",
|
|
9
|
+
"ru": "Исправьте конфигурацию IKEA SOMRIG, повысив «определение». Конечная точка не является ошибкой функции.\nДоступ к опциям Zigbee2mqtt в качестве настроек в адаптере Zigbee (стадия ALPHA!)\nИсправьте ошибку: zigbee.0 (1118300) zigbee.0 уже работает на старте адаптера\nОбновленная аппаратная панель конфигурации - обмен текстовыми кнопками на кнопки с иконками.\nОграниченные состояния на плитках устройства к состояниям, которые читаются только или которые могут быть изменены чувственно через плитку устройства.\n",
|
|
10
|
+
"pt": "Corrigir para configuração Ikea SOMRIG elevando 'definição. endpoint não é um erro de função.\nAcesso às opções \"zigbee2mqttt como configurações no adaptador zigbee (Estação LAPHA!)\nFix for 'error: zigbee.0 (1118300) zigbee.0 já em execução' no início do adaptador (Alpha Stage)\nPainel de configuração de hardware atualizado - botões de texto trocados para botões com ícones.\nEstados limitados em telhas de dispositivo para estados que são lidos apenas ou que podem ser modificados sensivelmente através da telha do dispositivo.\n",
|
|
11
|
+
"nl": "Fix voor Ikea SOMRIG configuratie verhogen 'definitie. eindpunt is geen functiefout.\nToegang tot 'zigbee2mqtt opties als instellingen in zigbee adapter (ALPHA Stage !)\nFix voor 'fout: zigbee.0 (1118300) zigbee.0 al actief' bij adapterstart (Alpha Stage)\nBijgewerkt hardware configuratiepaneel - uitgewisselde tekstknoppen voor knoppen met pictogrammen.\nBeperkte toestanden op apparaattegels naar toestanden die alleen worden gelezen of die verstandig kunnen worden gewijzigd via de apparaattegel.\n",
|
|
12
|
+
"fr": "Correction pour la configuration Ikea SOMRIG augmentant la définition. le paramètre n'est pas une erreur de fonction.\nAccès aux options 'zigbee2mqtt comme réglages dans l'adaptateur zigbee (ALPHA Stage !)\nCorrection pour 'erreur: zigbee.0 (1118300) zigbee.0 déjà en cours d'exécution' au démarrage de l'adaptateur (Alpha Stage)\nPanneau de configuration du matériel mis à jour - boutons texte échangés pour les boutons avec des icônes.\nLes états limités sur les tuiles de l'appareil aux états qui sont lus seulement ou qui peuvent être modifiés de façon sensible via la tuile de l'appareil.\n",
|
|
13
|
+
"it": "Fissare per Ikea SOMRIG configurazione aumentando 'definizione. endpoint non è un errore di funzione.\nAccesso alle opzioni 'zigbee2mqtt come impostazioni nell'adattatore zigbee (ALPHA Stage !)\nCorrezione per 'error: zigbee.0 (1118300) zigbee.0 già in esecuzione' all'inizio dell'adattatore (Alpha Stage)\nPannello di configurazione hardware aggiornato - pulsanti di testo scambiati per pulsanti con icone.\nStati limitati su piastrelle di dispositivo a stati che sono letti solo o che possono essere modificati sensibilmente tramite la piastrella del dispositivo.\n",
|
|
14
|
+
"es": "Arregla para la configuración de Ikea SOMRIG criando 'definición. endpoint no es un error de función.\nAcceso a las opciones 'zigbee2mqtt como configuración en el adaptador de zigbee (ALPHA Stage !)\nFijación para 'error: zigbee.0 (1118300) zigbee.0 ya funcionando en el inicio del adaptador (Alpha Stage)\nPanel de configuración de hardware actualizado - botones de texto intercambiados para botones con iconos.\nEstados limitados en fichas de dispositivo a estados que se leen solamente o que pueden ser modificados de forma sensata a través de la ficha del dispositivo.\n",
|
|
15
|
+
"pl": "Napraw dla definicji podnoszenie konfiguracji Ikea SOMRIG. Punkt końcowy nie jest błędem funkcji.\nDostęp do opcji 'zigbee2mqtt jako ustawień w adapterze zigbee (ALPHA Stage!)\nFix for 'error: zigbee.0 (1118300) zigbee.0 already running' at adapter start (Alpha Stage)\nAktualizacja panelu konfiguracji sprzętowej - wymieniono przyciski tekstowe na przyciski z ikonami.\nOgraniczone stany na płytkach urządzenia do stanów, które są tylko odczytywane lub które mogą być modyfikowane w sposób rozsądny za pomocą płytki urządzenia.\n",
|
|
16
|
+
"uk": "Виправлення для налаштування Ikea SOMRIG 'Визначення. кінцева точка не є помилкою функції.\nДоступ до опцій Zigbee2mqtt як налаштування адаптера Zigbee (ALPHA Stage !)\nВиправлення для 'error: zigbee.0 (1118300) zigbee.0 вже запущений' при запуску адаптера (Alpha Stage)\nОновлена панель конфігурації обладнання - обмінні текстові кнопки для гудзиків з іконками.\nОбмежені стани на плитці пристрою для станів, які читаються тільки або які можуть бути змінені, швидко через плитку пристрою.\n",
|
|
17
|
+
"zh-cn": "修复Ikea SOMRIG 配置提升定义 。 结束点不是一个函数'错误.\n访问 'zigbee2mqtt 选项作为 Zigbee 适配器的设置( ALPHA stage !) \n在适配器启动( Alpha Stage)时为 'error: zigbee. 0 (1118300) zigbee. 0 已经运行' 进行修复\n更新的硬件配置面板 - 用图标交换文本按钮作为按钮.\n将设备瓦片的状态限制在只读或通过设备瓦片可敏感修改的状态.\n"
|
|
18
|
+
},
|
|
19
|
+
"3.0.0": {
|
|
20
|
+
"en": "Breaking change: Start of zigbee subsystem requires configuration entry !!!\nHardware configuration panel\nUpdate for external converter - detect /dist/ subfolder\nUpdate device image: use of icons defined in external converter (beta)\n",
|
|
21
|
+
"de": "Bruchänderung: Beginn des Zickbee Subsystems erfordert Konfigurationseintrag!!!\nHardware-Konfigurationspanel\nUpdate für externen Konverter - Erkennung /dist/ Unterordner\nGerätebild aktualisieren: Verwendung von Icons, die im externen Konverter (beta) definiert sind\n",
|
|
22
|
+
"ru": "Переломные изменения: Запуск подсистемы Zigbee требует ввода конфигурации!!!\nАппаратная конфигурационная панель\nОбновление внешнего конвертера - детектировать /dist/ подпапку\nОбновление изображения устройства: использование значков, определенных во внешнем конвертере (бета)\n",
|
|
23
|
+
"pt": "Mudança de ruptura: O início do subsistema zigbee requer entrada de configuração !!!\nPainel de configuração do hardware\nAtualização para conversor externo - detectar /dist / subpastas\nImagem do dispositivo de atualização: uso de ícones definidos no conversor externo (beta)\n",
|
|
24
|
+
"nl": "Verandering: Start van zigbee subsysteem vereist configuratie toegang !!!\nHardware configuratiepaneel\nUpdate voor externe converter - detecteer /dist/submap\nAfbeelding van het apparaat bijwerken: gebruik van pictogrammen gedefinieerd in externe converter (beta)\n",
|
|
25
|
+
"fr": "Briser le changement : Le démarrage du sous-système zigbee nécessite une entrée de configuration !!!\nPanneau de configuration du matériel\nMise à jour pour convertisseur externe - détecter /dist/ sous-dossier\nMise à jour de l'image du périphérique : utilisation d'icônes définies dans le convertisseur externe (beta)\n",
|
|
26
|
+
"it": "Cambiamento di rottura: L'avvio del sottosistema zigbee richiede l'ingresso di configurazione !!!\nPannello di configurazione hardware\nAggiornamento per convertitore esterno - rilevare /dist/ subfolder\nImmagine del dispositivo di aggiornamento: uso delle icone definite nel convertitore esterno (beta)\n",
|
|
27
|
+
"es": "Cambio de ruptura: Inicio del subsistema zigbee requiere entrada de configuración !!!\nPanel de configuración de hardware\nActualización para convertidor externo - detect /dist/ subfolder\nActualizar imagen del dispositivo: uso de iconos definidos en convertidor externo (beta)\n",
|
|
28
|
+
"pl": "Łamanie zmian: Rozpoczęcie podsystemu Zigbee wymaga wprowadzenia konfiguracji!!!\nPanel konfiguracji sprzętu\nAktualizacja konwertera zewnętrznego - wykryj / dist / subfolder\nAktualizacja obrazu urządzenia: użycie ikon zdefiniowanych w konwerterze zewnętrznym (beta)\n",
|
|
29
|
+
"uk": "Зміна розривів: Старт підсистеми zigbee вимагає введення конфігурації !!!\nПанель конфігурації обладнання\nОновлення для зовнішнього конвертера - виявлення /dist / підпалювач\nОновлення зображення пристрою: використання ікон, визначених у зовнішній конвертер (beta)\n",
|
|
30
|
+
"zh-cn": "中断更改 : Zigbee子系统的启动需要配置输入!!!!\n硬件配置面板\n外部转换器更新 - 检测/ dist/ 子文件夹\n更新设备图像: 使用外部转换器( β) 中定义的图标\n"
|
|
31
|
+
},
|
|
6
32
|
"2.0.5": {
|
|
7
33
|
"en": "ZHC 23.6.0\nZH 3.3.x\nremoved extra logging\nfixed memory issue.\nConfigure on Message - 5 attempts.\nupdate transmitPower\nfix crash in ZigbeeController.ByteArrayToString\ndevice designation for devices without mapped model (allows use in groups and bindings)\n",
|
|
8
34
|
"de": "ZHC 23.6.0\nZH 3.3.x\nentfernte zusätzliche protokollierung\nfeste speicherausgabe.\nKonfigurieren auf Nachricht - 5 Versuche.\nupdate sendPower\ncrash in ZigbeeController beheben. ByteArrayToString\ngerätebezeichnung für geräte ohne abgebildetes modell (ermöglicht die verwendung in gruppen und bindungen)\n",
|
|
@@ -67,32 +93,6 @@
|
|
|
67
93
|
"pl": "ZMIANY ZBIORCZE\n\nprzełączanie na konwertery 21 zmienia eksponaty dużej liczby urządzeń (głównie pilotów)\nnowa metoda kontrolowania koloru na podstawie podkanałów dla rgb, hs i xy\nWyświetla jako domyślne dla urządzeń ALL. Używanie starej definicji jako opcji\nWymaga węzła 20.x lub nowsze\n\nNapraw parowanie\nzmienić ping\nopóźnianie generowania mapy aż do uruchomienia odświeżania, wiadomości mapy po generacji\nusunąć zakładkę wiązania z zakładki zigbee\nponownie zamówić karty w konfiguracji\nusunąć zakładkę wiązania z konfiguracji\nusuń mapę z konfiguracji\ndodaj debug do karty zigbee\nHerdsman 3.2.5, Konwertery 21.30.0\nWyświetla jako domyślne, użycie starych definicji urządzenia jako dotychczasowe opcjonalne\nObrazy specyficzne dla użytkownika (oparte na modelu, na urządzeniu)\nUlepszona edycja grupowa - usunąć członków z karty grupowej",
|
|
68
94
|
"uk": "БРЕАКІНГОВІ ЗМІНИ\n\nперемикач на перетворювачі 21 змінює висадки для великої кількості пристроїв (найбільш віддалені)\nновий метод контролю кольору на основі підканалів для rgb, hs і xy\nЗа замовчуванням для всіх пристроїв. Використання старого визначення як варіант\nВимагає Node 20.x або нові\n\nФіксація Пірсинг\nзмінити пінг\nгенерація карти затримки до освіження активується, повідомлення після генерації\nвидалити вкладку в'язання з вкладки zigbee\nвкладка зворотного замовлення в конфігурації\nвидалити вкладку з конфігурації\nвидалити карту з конфігурації\nadd debug до zigbee tab\nEnglish, Українська, Français..\nЕкспози як за замовчуванням, використання застарілих параметрів пристрою, як необов'язковий\nКористувальницькі специфічні зображення (моделі на основі пристрою)\nУдосконалено редагування груп - видалення членів з групової картки",
|
|
69
95
|
"zh-cn": "裂变\n\n21 更改大量设备(大多为远程设备)的曝光量\n基于 rgb、 hs 和 xy 子通道的新的颜色控制方法\n曝光为默认所有设备 。 仅将旧定义用作选项\n需要节点 20.x 或更新\n\n修复对齐\n更改键\n将映射生成延迟到刷新启动, 映射消息生成后\n从 zigbee 标签中删除绑定标签\n在配置中重新排序标签\n从配置中删除绑定标签\n从配置中删除地图\n添加调试到 zigbee 标签\n牧民 3.2.5,转换器 21.30.0\n将曝光作为默认, 将旧设备定义作为遗留选项\n用户特定图像( 基于模型、 设备)\n改进组编辑 - 从组卡中删除成员"
|
|
70
|
-
},
|
|
71
|
-
"1.10.14": {
|
|
72
|
-
"en": "Herdsman 2.1.9, Converters 20.58.0\nFix: Aqara T1M (CL-L02D) \ndeleteDeviceStates change to deleteObj",
|
|
73
|
-
"de": "Herdsman 2.1.9, Konverter 20.58.0\nFix: Aqara T1M (CL-L02D)\nlöschen DeviceState Änderung zum Löschen Ob",
|
|
74
|
-
"ru": "Herdsman 2.1.9, Converters 20.58.0\nFix: Aqara T1M (CL-L02D)\nудалить Устройства меняются для удаления Obj",
|
|
75
|
-
"pt": "Herdsman 2.1.9, Conversores 20.58.0\nFix: Aqara T1M (CL-L02D)\nexcluir DeviceStates mudam para excluir Objecção",
|
|
76
|
-
"nl": "Herdsman 2.1.9, Converters 20.58.0\nFix: Aqara T1M (CL-L02D)\nverwijderen Apparaatstaten wijzigen om te verwijderen Obj",
|
|
77
|
-
"fr": "Herdsman 2.1.9, Convertisseurs 20.58.0\nCorrection: Aqara T1M (CL-L02D)\nsupprimer Les états de périphérique changent pour supprimer OBJ",
|
|
78
|
-
"it": "Herdsman 2.1.9, Convertitori 20.58.0\nFisso: Aqara T1M (CL-L02D)\ncancella DeviceStates modifica per eliminare Obj",
|
|
79
|
-
"es": "Herdsman 2.1.9, convertidores 20.58.0\nFijación: Aqara T1M (CL-L02D)\nborrar Los Estados de dispositivos cambian para eliminar Obj",
|
|
80
|
-
"pl": "Herdsman 2.1.9, konwertery 20.58.0\nFix: Aqara T1M (CL- L02D)\nusuń DeviceStates zmienić, aby usunąć Obj",
|
|
81
|
-
"uk": "Herdsman 2.1.9, Конвертер 20.58.0\nФіксація: Aqara T1M (CL-L02D)\nвидалити Зміна стану пристроїв для видалення Офіціант",
|
|
82
|
-
"zh-cn": "牧民2.1.9,转换器 20.58.0\n修补:Aqara T1M(CL-L02D)\n删除 设备状态更改以删除 欧比"
|
|
83
|
-
},
|
|
84
|
-
"1.10.13": {
|
|
85
|
-
"en": "corr icon download bug (axios)",
|
|
86
|
-
"de": "corr icon download bug (axios)",
|
|
87
|
-
"ru": "значок скачать bug (axios)",
|
|
88
|
-
"pt": "corr ícone de download bug (eixos)",
|
|
89
|
-
"nl": "corr pictogram download bug (axios)",
|
|
90
|
-
"fr": "corr icône de téléchargement bug (axios)",
|
|
91
|
-
"it": "corr icon download bug (assios)",
|
|
92
|
-
"es": "corr icono descargar bug (axios)",
|
|
93
|
-
"pl": "corr ikona pobierz błąd (axios)",
|
|
94
|
-
"uk": "корр іконки завантажити помилку (axios)",
|
|
95
|
-
"zh-cn": "corr 图标下载错误( axios)"
|
|
96
96
|
}
|
|
97
97
|
},
|
|
98
98
|
"titleLang": {
|
|
@@ -159,6 +159,7 @@
|
|
|
159
159
|
"tab": "materialize"
|
|
160
160
|
},
|
|
161
161
|
"messagebox": true,
|
|
162
|
+
"stopTimeout": 30000,
|
|
162
163
|
"stopBeforeUpdate": true,
|
|
163
164
|
"dataFolder": "zigbee_%INSTANCE%",
|
|
164
165
|
"compact": true,
|
|
@@ -187,7 +188,7 @@
|
|
|
187
188
|
},
|
|
188
189
|
"globalDependencies": [
|
|
189
190
|
{
|
|
190
|
-
"admin": ">=
|
|
191
|
+
"admin": ">=7.4.10"
|
|
191
192
|
}
|
|
192
193
|
],
|
|
193
194
|
"dependencies": [
|
|
@@ -248,8 +249,7 @@
|
|
|
248
249
|
"cancel"
|
|
249
250
|
]
|
|
250
251
|
}
|
|
251
|
-
]
|
|
252
|
-
"installedFrom": "asgothian/ioBroker.zigbee#1.11"
|
|
252
|
+
]
|
|
253
253
|
},
|
|
254
254
|
"native": {
|
|
255
255
|
"port": "",
|
|
@@ -267,7 +267,8 @@
|
|
|
267
267
|
"startWithInconsistent": false,
|
|
268
268
|
"warnOnDeviceAnnouncement": true,
|
|
269
269
|
"baudRate": 115200,
|
|
270
|
-
"flowCTRL": false
|
|
270
|
+
"flowCTRL": false,
|
|
271
|
+
"autostart": false
|
|
271
272
|
},
|
|
272
273
|
"instanceObjects": [
|
|
273
274
|
{
|