Skip to content

Orpek

Pre-release
Pre-release
Compare
Choose a tag to compare
@manup manup released this 06 Oct 22:54
· 1774 commits to master since this release
v2.13.0-beta
69f0504

This beta release is the successor of stable version v2.12.6.

Backup first

This version has some heavy additions and changes under the hood.
Before installing please create a backup first.

For the first days the release is only available for manual installation, APT repositories will be updated at the weekend.

Changes

  • Initial support for Tuya door windows sensor _TZ3000_402jjyro #5307
  • Initial support for Tuya covering _TZE200_iossyxra #5235
  • Initial support for CASA.ia Temperature probe CTHS-317-ET #5259
  • Initial support for Xiaomi Aqara D1 1-gang (neutral wire) QBKG23LM #5164
  • Initial support for Device Description Files (DDF) #5288
  • Support for Woox R7049 Smoke Alarm #5281
  • Fix direction for Tuya covering _TZE200_rddyvrci #5265
  • Fix SIGBUS crash in deCONZ core on ARM architectures while reading neighbor tables.
  • Xiaomi specific attribute additions for given clusters #5135
  • Enable websocket server to listen on IP specified via --http-listen command line parameter #5247
  • Move power configuration related code to dedicated file #5240
  • Don't reset Sonoff SNZB-03 presence #5276
  • Add Develco specific attributes to general.xml #5325
  • Corrections on sensor fingerprints #5246
  • Allow temperature adjustment on Sengled Tunable White Z01-A19NAE26 #5273
  • Enable alarm systems in rules; return alarm systems in full config request #5255
  • Correct Apex smart plug current readings #5348
  • Replaced "Edit → Permit Join" dialog with new UI in "Panels → Control → Pairing" widget.
  • Source Routing feature leaves beta with improved path finding and maintenance.
  • Sensors in the Phoscon App under "Menu → Sensors" are now shown generically.

deCONZ GUI

  • Double click on a node now opens the node endpoints/cluster drop down.
  • Double click on a cluster opens it in the Cluster Info panel.
  • Double click on a clusters attributes count (the gray text right to the cluster name) jumps to the attributes in the Cluster Info panel.
  • Dragging a cluster of a node into the Wireshark filter input field, selects the node and cluster in Wireshark.

Device Description Files (DDF)

The future direction to support devices will be via JSON based DDF files.

  • This version adds initial support for DDF handling.
  • Each device is meant to be described in a DDF file, instead of hard coded C++.
  • Supporting or editing devices becomes easier, with live editing, and without having to restart deCONZ or compiling C++ code.
    (For example, supporting the Innr SP-120 smart plug with: power measurement, Zigbee bindings and ZCL attribute reporting can be done in less than 3 minutes)
  • It will take a few months to move existing devices from C++ to DDF.

Learn more about DDF at https://dresden-elektronik.github.io/deconz-dev-doc

Important: This is a developer preview and disabled by default for the next versions, to enable DDF handling select the mode "Normal" in "Panels → Control".

DDF Editor (preview version)

DDF files don't need to be written by hand, the GUI DDF editor provides a drag 'n' drop interface to assemble and configure devices.

Use the node mouse context menu → "Edit DDF" to open the editor for a device.

image

Currently more complex devices still require manual changes but this will become easier over time, as more features are added to the editor. The current version allows to edit devices such as lights and power sockets.

The next steps target the integration of sensors and switches.

Zigbee network troubleshooting

A new visual LQI filter has been added to find routing issues in a Zigbee network.

image

  • Under "Panels → Source Routing" is a new checkbox Minimum LQI display which hides links below the given LQI value.
  • By changing the value weak links are hidden in the UI, to easier spot areas where a router should be placed.
  • The line colors between nodes have more contrast, in v2.13.0, to better show weak links.

Routing depends on how good devices can "see" each other — Link Quality Indicator (LQI).
For example: For two devices A and B, there are two LQI values at play: 1) How A sees B, and 2) how B sees A.

LQI value meanings:

  • 255 excellent
  • 200 good
  • 130 flaky but can work
  • < 100 problematic

Always aim for LQI values of 200 and above to get a stable network!

New Dependency

Under Linux libqt5qml5 and qtdeclarative5-dev need to be installed.

A special thanks to all contributors of the deCONZ GitHub community.

Assets 2