iobroker.zigbee 3.1.6 → 3.2.0

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
@@ -35,8 +35,6 @@ Current firmware files for these devices can be found [on GitHub](https://github
35
35
  ### Dresden Elektronik SoC
36
36
  <span><img src="https://raw.githubusercontent.com/ioBroker/ioBroker.zigbee/master/docs/en/img/deconz.png" width="180"></span>
37
37
 
38
- As of May 2025, raspbee and conbee variants are no longer recommended, as the code is no longer actively maintained and has fallen behind the other variants with regards to functionality.
39
-
40
38
  Conbee/RaspBee Support is no longer considered experimental in the zigbee-herdsman and zigbee-herdsman-converters libraries used by the zigbee Adapter, use of these devices with the adapter may limit functionality. Known issues are:
41
39
  - link quality display may be incorrect
42
40
  - device map metrics may be incorrect
@@ -60,7 +58,7 @@ The adapter should **always** be installed from within the ioBroker Admin. Direc
60
58
  At first start, it is vital to set up the adapter settings. These include:
61
59
  - the communication to the zigbee Coordinator (COM Port). This can be a device identifier or a network address for Network-based coordinators
62
60
  - the required firmware-Type
63
- - the network parameters PanID (a number between 0 and 65565), extended PanID (a 16 digit HEX number) and the zigbee Channel **important: Do not run the adapter without changing the values for PanID (6754) and Extended PanID (DDDDDDDDDDDDDDDD) to unique values for your Zigbee Installation.**
61
+ - the network parameters PanID (a number between 0 and 65565), extended PanID (a 16 digit HEX number) and the zigbee Channel **important: Do not run the adapter without changing the values for PanID (6754) and Extended PanID (DDDDDDDDDDDDDDDD) to unique values for your Zigbee Installation. From v3.0 onwards, the adapter will suggest a unique ExtPanID on any new install**
64
62
 
65
63
 
66
64
  ![](docs/en/img/Zigbee_config_en.png)
@@ -78,6 +76,11 @@ The adapter is placed in pairing mode by pressing the pairing button:
78
76
 
79
77
  A dialog showing a pairing countdown appears. When a new device is discovered, interviewed and paired with the network, messages will be shown in this dialog, and the device will show up in the grid of active devices. Any known device should show up with an image and the correct device name, as well as a number of changable settings. Any unknown device will show up with a device name and a ? as icon, while devices which failed the pairing will show up as 'unknown' with the same ? icon. These should be removed from the network to be paired again. Please refer to the documentation linked above for more details.
80
78
 
79
+
80
+ ## In Depth Documentation
81
+
82
+ In depth information can be found here [auf deutsch](https://github.com/ioBroker/ioBroker.zigbee/blob/master/docs/de/readme.md), here [in english](https://github.com/ioBroker/ioBroker.zigbee/blob/master/docs/en/readme.md). There is more information on the [wiki](https://github.com/ioBroker/ioBroker.zigbee/wiki) as well.
83
+
81
84
  ## Advanced options
82
85
 
83
86
  ### Groups
@@ -107,12 +110,19 @@ The Adapter offers to collect debug information for specific devices in order to
107
110
 
108
111
  The debug information is only available from the zigbee tab.
109
112
 
110
- ### Local overrides
113
+ ### Local overrides (Only available until v3.1.5)
111
114
 
112
- Device integration can be modified on a *per Model* basis, allowing the user to customise the states associated with the device. Note that before version 3.1.0, this is limited to choosing between the default *expose based* integration and the previous *legacy* integration. More options for customisation are under development.
115
+ ~~Device integration can be modified on a *per Model* basis, allowing the user to customise the states associated with the device. Note that before version 3.1.0, this is limited to choosing between the default *expose based* integration and the previous *legacy* integration. More options for customisation are under development.~~
113
116
 
114
117
  The local overrides are only available from the instance configuration
115
118
 
119
+ ### Local data (available v3.2.0 or newer)
120
+
121
+ Options, name and icon can be set on a model base from this section. Note: The legacy option (if offered) will revert to the legacy code in the adapter.
122
+ Changing anything here **may** require a restart of the adapter before it becomes active.
123
+
124
+ The local data are only available from the instance configuration
125
+
116
126
  ### Developer Mode
117
127
 
118
128
  The developer mode offers the ability to communicate with any paired device solely based on the details of the Zigbee communication rules. Use of this requires an insight into Zigbee Clusters, Attributes and messaging structure. It can be used to control devices which are not currently supported. An in depth desctiption of the developer Tab is available in the documentation.
@@ -121,7 +131,8 @@ The developer tab is only available from the instance configuration
121
131
 
122
132
 
123
133
 
124
- ## Additional info
134
+ ### Additional info
135
+
125
136
 
126
137
  There is a [friendly project](https://github.com/koenkk/zigbee2mqtt) with similar functionality which is based on the same technology. It uses the same base libraries for hardware communication and device integration. Any device listed as compatible in this project is likely to be compatible with the ioBroker.zigbee Adapter. Note that there is a delay between device integration into zigbee2mqtt.io and the Zigbee-Adapter, as compatibility with the hardware libraries requires verification before the adapter can move to the latest version.
127
138
 
@@ -133,15 +144,6 @@ There are knowledge bases that can be useful for working with Zigbee-devices and
133
144
 
134
145
  Pleae refer to [this list](https://www.zigbee2mqtt.io/supported-devices/) to check compatibility. Once a device is listed as compatible there, it is either already compatible with the Zigbee Adapter or can be made compatible using an external converter.
135
146
 
136
- ## In Depth Documentation
137
-
138
- [in Deutsch](https://github.com/ioBroker/ioBroker.zigbee/blob/master/docs/de/readme.md)
139
-
140
- [in English](https://github.com/ioBroker/ioBroker.zigbee/blob/master/docs/en/readme.md)
141
-
142
- or
143
-
144
- [wiki](https://github.com/ioBroker/ioBroker.zigbee/wiki)
145
147
 
146
148
 
147
149
 
@@ -152,6 +154,18 @@ You can thank the authors by these links:
152
154
 
153
155
  -----------------------------------------------------------------------------------------------------
154
156
  ## Changelog
157
+ ### 3.2.0 (2025-10-26)
158
+ * (asgothian) remove local overrides tab from config
159
+ * (asgothian) establish local data tab in config to edit global and device level settings and options
160
+ * (asgothian) remove the local overrides tab
161
+ * (asgothian) remove the ability to set model level overrides from device tab.
162
+ * (asgothian) fix errors for 'polling' devices with changed poll times.
163
+ * (asgothian) warning icon for devices which are not completely interviewed.
164
+ * (asgothian) improved router detection for opening the network
165
+ * (asgothian) bugfix: open network on router
166
+ * (asgothian) ZHC 25.x latest, ZH 6.1.3,
167
+ * (asgothian) restore from in-adapter backup
168
+
155
169
  ### 3.1.6 (2025-10-21)
156
170
  * (asgothian) Bugfixes
157
171
  *