Coder Social home page Coder Social logo

iobroker / iobroker.zigbee Goto Github PK

View Code? Open in Web Editor NEW
312.0 28.0 191.0 22.74 MB

Zigbee communcation with Hue, Xiaomi, Lighttify... via TI CC2xxx USB stick

License: MIT License

JavaScript 85.87% HTML 14.04% Shell 0.09%
zigbee iobroker smarthome cc2530 cc2531 cc26x2r1 cc2652p2

iobroker.zigbee's Introduction

Logo

ioBroker.zigbee

Number of Installations Number of Installations NPM version

Test and Release Translation status Downloads

ioBroker adapter for Zigbee devices via TI cc2531/cc2530/cc26x2r/cc2538 and deCONZ ConBee/RaspBee.

With the Zigbee-coordinator based on Texas Instruments SoC, deCONZ ConBee/RaspBee modules, Silicon Labs EZSP v8 or ZIGate USB-TTL it creates its own zigbee-network, into which zigbee-devices are connected.

By working directly with the coordinator, the driver allows you to manage devices without additional application / gateways / bridge from device manufacturers (Xiaomi / TRADFRI / Hue / Tuya). About the device Zigbee-network can be read here (in English).

Hardware

One coordinator device is required for each zigbee Adapter instance. The device must be flashed with the respective coordinator firmware. A list of supported coordinators, the necessary equipment for the firmware and the device preparation process for different coordinator devices are described here in English or smarthomescene.com or here in Russian

Texas Instruments SoC

Recommended devices are based on either the CC2652 or CC1352 chip. Devices based on cc253x chips are still supported but are no longer recommended. Only CC26xx/cc1352/cc2538 Devices support extraction of the NVRam backup which should allow to swap coordinator hardware without having to reconnect all zigbee devices to the network. Current firmware files for these devices can be found on GitHub

tutorial/zigbee.png

Dresden Elektronik SoC

recommended:

  • ConBee II
  • RaspBee II

no longer recommended:

  • ConBee I
  • RaspBee

While 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:

  • link quality display may be incorrect
  • device map metrics may be incorrect
  • NVRam Backup is not supported.

Silicon Labs SoC

Support for Silicon Lab Zigbee based adapters is experimental. The initial support for EZSP v8 is still not yet considered stable, and the project is in need of more developers volunteering to help with this integration. Please refer to the respective documentation on this page and ongoing development discussion with regards to the state of Silabs EmberZNet Serial Protocol (EZSP) adapter implementation integration into the zigbee-herdsman and zigbee-herdsman-converters libraries which it depends on.

ZiGate SoC

Support for ZiGate based adapters is experimental. The initial support for ZiGate is still not yet considered stable, and the project is in need of more developers volunteering to help with this integration. Please refer to the respective documentation on this page and ongoing development discussion with regards to the state of ZiGate adapter implementation into the zigbee-herdsman and zigbee-herdsman-converters libraries which it depends on.

Work with adapter

To start the driver, you must specify the name of the port on which the Zigbee module (stick) is connected. Usually this is the port /dev/ttyACM0 or /dev/ttyUSB0 for the UART-connection. Or you can find with ls -l /dev/serial/by-id the device direct.

open the settings and change port

For Windows, this will be the COM port number.

Starting from version 1.0.0, you can also use tcp connection for cases using esp8266 (or other microcontrollers) as serial-bridge. For example tcp://192.168.1.46:8880. Read more info here https://www.zigbee2mqtt.io/information/connecting_cc2530#via-an-esp8266

To connect devices, you need to switch the Zigbee coordinator to pairing mode by pressing the green button. The countdown will begin (60 seconds) until the device connectivity is available. To connect Zigbee devices in most cases, just press the pairing button on the device itself. But there are features for some devices. More information about pairing with devices can be found here (in English)

After successful pairing, the device appears in the configuration panel. If the device appears in the configuration panel but has the type "undefined", then this is an unknown device and cannot be worked with it. If the device is in the list of available devices, but added as "undefined", then try to remove the device and add it again.

The devices connected to the Zigbee-network and inform the coordinator of their status and events (button presses, motion detection, temperature change). This information is reflected in the ioBroker object-states. Some ioBroker states have feedback and send commands to the zigbee-device when the value changes (switching the state of the outlet or lamp, changing the scene or the brightness of the lamp).

Device Groups

You may create groups of devices.

It is a Zigbee feature, intended for example to switch bulbs synchronized. Assign groups via device tabs edit button. A group will show as own "device" in Objects.

Note: Not all devices support groups (not supported by end devices like sensors).

Binding

https://www.zigbee2mqtt.io/information/binding

Developer Tab

This is a tool for advanced users to test currently unsupported devices or enhance this adapter's functionality. More instructions can be found on the tab.

Additional info

There is a friendly project with similar functionality on the same technologies, where you can work with the same devices using the MQTT protocol. Therefore, if any improvements or support for new zigbee-devices occur in the Zigbee2MQTT project, we can transfer and add the same functionality to this adapter. If you notice this, then write the issue - we'll postpone it.

There are knowledge bases that can be useful for working with Zigbee-devices and equipment:

Supported devices

Works with devices from this list

More Information

in Deutsch

in English

or

wiki

Donate

You can thank the authors by these links:


Changelog

UNRELEASED

  • (lebrinkma) fix linter errors

1.10.9 (2024-09-05)

  • (arteck) typo admin settings
  • (arteck) eslint config

1.10.8 (2024-09-05)

  • (arteck) corr admin settings
  • (arteck) add new eslint version

1.10.7 (2024-09-05)

  • (arteck) add flow control option
  • (asgothian) add new NewHerdsman
  • (arteck) add new ezsp coordinator Firmware (7.4.1.0)

1.10.5 (2024-06-21)

  • (arteck) icon ota device update
  • (arteck) icon fix

1.10.4 (2024-04-20)

  • (arteck) core update
  • (arteck) dependency update

1.10.3 (2024-04-06)

  • (arteck) dependency update

Changelog

1.10.2 (2024-01-25)

  • (arteck) dependency update

1.10.1 (2024-01-21)

  • (arteck) Baudrate is now configurable. works ONLY with Deconz/Conbee(38400)
  • (arteck) add nvbackup.json delete button

1.10.0 (2024-01-13)

  • (arteck) new zigbee-herdsman-converters 18.x
  • (arteck) configure message is now a warning

1.9.7 (2024-01-05)

  • (arteck) corr configure for some devices

1.9.6 (2024-01-01)

  • (arteck) corr ikea bug
  • (crckmc) trv child lock works

1.9.5 (2023-12-29)

  • (arteck) update dependency
  • (arteck) min node 18.x.

1.9.4 (2023-12-29)

  • (arteck) typo

1.9.3 (2023-12-26)

  • (arteck) last zhc Version 16.x
  • (arteck) corr reboot in statecontroller

1.9.2 (2023-12-25)

  • (arteck) gen states from exposes as function
  • (arteck) rebuild dev_names.json with state cleanup button

1.9.1 (2023-12-23)

  • (arteck) corr TypeError: Cannot read properties of undefined (reading 'state')

1.9.0 (2023-12-22)

  • (arteck) up to new zhc
  • (arteck) update dependency

1.8.27 (2023-12-22)

  • (arteck) update dependency

1.8.26 (2023-12-22)

  • (arteck) corr toZigbee message
  • (arteck) add deviceManager

1.8.25 (2023-12-17)

  • zhc 16.x
  • (arteck) corr group from exclude dialog

1.8.24 (2023-09-05)

  • (arteck) switch to exposes tab for some Aqara Devices more infos

1.8.23 (2023-08-10)

  • (arteck) query from xiaomi is now better

1.8.22 (2023-08-05)

  • (arteck) crash when meta is empty

1.8.21 (2023-07-31)

  • (arteck) no converter found

1.8.20 (2023-07-31)

  • (arteck) add log

1.8.19 (2023-07-31)

  • (arteck) fix occupancy_timeout
  • (arteck) fix battery percentage and voltage

1.8.18 (2023-07-16)

  • (arteck) little fix sentry and error log

1.8.17 (2023-07-15)

  • (arteck) sentry corr

1.8.16 (2023-07-11)

  • (arteck) battery corr

1.8.15 (2023-07-11)

  • (arteck) corr battery status

1.8.13 (2023-07-09)

  • (arteck) ota corr
  • (arteck) devices are wrong with enum exposes
  • (arteck) select field for groups is larger
  • (kirovilya) tuya.whitelabel corr

1.8.12 (2023-06-30)

  • (arteck) new Documentation (thx Stefan)

1.8.11 (2022-12-10)

  • (arteck) fix compsite exposes with a list

1.8.10 (2022-12-12)

  • (asgothian) fix group access
  • (asgothian) add option for pairing code: A new icon allows opening the network after first entering a pairing code listed on the device
  • (asgothian) easier use of external converters
    • external converters can now be placed in the zigbee adapter data folder
    • no absolite path is required to access them
    • external converters posted on the GitHub for zigbee-herdsman-converters should work as they are - folders for libraries are rewritten to match the expected location when 'required' from within the zigbee adapter
    • Log entries will identify which files are entered as converters. Errors in these files should not cause the adapter to crash - instead, use of external converters may be unavailable.

1.8.9 (2022-12-10)

  • (arteck) fix lidl plug

1.8.7 (2022-12-01)

  • (arteck) fix exposes

1.8.5 (2022-11-30)

  • (arteck) fix for new code

1.8.3 (2022-11-30)

  • (arteck) back to old source

1.8.1 (2022-11-28)

  • (bluefox) Packages updated
  • (bluefox) Added names of serial ports in configuration dialog

1.7.7 (2022-11-24)

  • dep update

1.7.6 (2022-07-23)

  • (kirovilya) fix selecting nodes in admin
  • (arteck) ikea fix

1.7.5 (2022-06-01)

  • (arteck) error message for undefined devices or icons

1.7.4 (2022-05-30)

  • (arteck) missing icons with multiple description

1.7.2 (2022-05-28)

  • (arteck) download missing icons corr

1.7.1 (2022-05-28)

  • (arteck) available status in admin is colored
  • (arteck) disable Backups checkbox in settings
  • (arteck) we keep last 10 backup files
  • (arteck) download missing icons automatically (manual upload needed)

1.6.18 (2022-04-21)

  • (arteck) fix pairing modus

1.6.17 (2022-04)

rollback

1.6.16 (2022-02-16)

  • (arteck) admin dep fix
  • (arteck) colored objects for online/offline state

1.6.15 (2022-02-08)

  • (arteck) Battery status % calculation was changed for xiaomi devices

1.6.14 (2022-01)

  • (asgothian) OTA limitation
    • devices with the available state set to false are excluded from OTA updates (and the update check)
    • devices with link_quality 0 are excluded from OTA updates (and the update check)
  • (asgothian) Device deactivation:
    • Devices can be marked inactive from the device card.
    • inactive devices are not pinged
    • state changes by the user are not sent to inactive devices.
    • when a pingable device is marked active (from being inactive) it will be pinged again.
    • inactive devices are excluded from OTA updates.
  • (asgothian) Group rework part 2:
    • state device.groups will now be deleted with state Cleanup
    • state info.groups is now obsolete and will be deleted at adapter start (after transferring data to the new storage)
  • (asgothian) Device name persistance.
    • Changes to device names made within the zigbee adapter are stored in the file dev_names.json. This file is not deleted when the adapter is removed, and will be referenced when a device is added to the zigbee adapter. Deleting and reinstalling the adapter will no longer remove custom device names, nor will deleting and adding the device anew.
  • (asgothian) Readme edit to reflect the current information on zigbee coordinator hardware.
  • (arteck) Zigbee-Herdsman 0.14.4, Zigbee-Herdsman-Converters 14.0.394

1.6.13 (2022-01)

  • (kirovilya) update to Zigbee-Herdsman 0.14

1.6.12 (2022-01)

  • (asgothian) Groups were newly revised (read here )
    • object device.groups is obsolet..the old one is no longer up to date

1.6.9 (2021-12)

  • (simatec) fix admin Dark-Mode
  • (asgothian) Expose Access Handling
  • (arteck) translations
  • (asgothian) fix groups
  • (agross) use different normalization rules

1.6.1 (2021-08)

  • (kirovilya) herdsman compatibility

1.6.0 (2021-08-09)

1.5.6 (2021-05-26)

  • (kirovilya) new UI add

1.5.5 (2021-05-05)

  • Fixes for new zigbee-herdsman-converters
  • UI fixes

1.5.3 (2021-04-30)

  • (arteck) Fix for js-controller 3.3.*

1.5.2 (2021-04-29)

  • (asgothian) Groups on dashboard

1.5.1 (2021-04-14)

1.4.4 (2021-02-14)

1.4.1 (2020-12)

  • (o0shojo0o) added a kelvin possibility into colortemp
  • (asgothian) Hue_calibration for exposed devices (Use requires PR on zigbee-herdsman-converters, PR is being worked on)
  • (asgothian) fix Tuya Thermostat: restore lost property "preset"
  • (asgothian) Change for Device Availability: Stagger initial ping by 200 ms to prevent network congestion due to a large number of ping requests
  • (asgothian) Change for Device Availability: Ping request triggered on reconnect. Before the herdsman Ping function is used, the adapter attempts to read the "state" dp. If this is successful, no ping is sent and the state is set
  • (asgothian) Change for Device Availability: Set link Quality to 0 when a device is not connected, 10 when it is reconnecting.
  • (asgothian) fix for message "illegal properties x,y" - remove color and color_temp from readable states on device available again (Issue #607)
  • (asgothian) RGB Color can now be entered as "named" color. Implemented names are taken from the list of extended web colors on wikipedia (https://en.wikipedia.org/wiki/Web_colors)
  • (asgothian) change in how RGB color is parsed. Incomplete colors will now be parsed successfully. #FFF will result in R 0, G 15, B 255
  • (asgothian) change in OTA: Message that a device does not respond for OTA query downgraded to "info" from "error"
  • (asgothian) new coordinator card

1.4.0 (2020-12)

  • Many new devices available

Starting from version 1.4.0, new devices in iobroker.zigbee will be added automatically, based on the exposes described in zigbee-herdsman-converters. The exposes section describes the device's capabilities, events and control commands. In iobroker.zigbee these descriptions are converted to iobroker states. This means that the new device is described correctly enough in zigbee-herdsman-converters to start working with iobroker.zigbee (do not need to add it to our /lib/devices files.js and /lib/states.js).

The only thing that is not described (yet, it may change in the future) in zigbee-herdsman-converters is the device image. This is why the device icon on network map uses external links to the resource https://www.zigbee2mqtt.io/images/devices/*. If you want to use local images, then you need to put the image file in /admin/img and briefly describe the device in the /lib/devices.js file without the states:

{
    models: [‘01MINIZB’],
    icon: 'img/ITEAD01ZBMINI. png',
}

in this case, the states attribute will be formed based on the exposes description and the image will be local.

1.3.1 (2020-10-30)

1.3.0 (2020-10-07)

  • More stable (zigbee-herdsman)
  • Backup prior database and nv-data (for z-stack 3) before start adapter
  • Allow to select bind cluster
  • Admin Tab support (experimental)
  • (UncleSamSwiss, DutchmanNL) Translation
  • New devices by: arteck, kirovilya, Shade, krumbholz, fre, Alex18081, ae, asgothian, Strunzdesign, kairauer, VLGorskij, Hesse-Bub, PaulchenPlump, blackrozes

1.2.1 (2020-08-16)

  • Fixes after changing device identify method
  • (Garfonso) Allow unbinding from coordinator

1.2.0 (2020-08-09)

  • Serialport 9.0.0. (zigbee-herdsman)
  • Drop support Node < 10 (zigbee-herdsman)
  • Device now identify (for zigbee-herdsman-converters) by model not zigbeeModel

Improvements and fixes:

  • (Strunzdesign) Fixed the mapping between bulb levels and adapter levels
  • (kirovilya) Fix ota for unavailable devices
  • (kirovilya) Lazy states - created only when an event arrives
  • (kirovilya) States generator - states are created depending on the device and its endpoints
  • (Shade) Fixed WXKG11LM clicks
  • (allofmex) Improved DeveloperTab logs
  • (allofmex) Add humidity and temperature calibration state to Tuya RH3052
  • (kirovilya) Fixed a typo due to which extPanID was not set
  • (allofmex) Retry reconnect gateway all the time for TCP-connected gateway
  • (kirovilya) Allow collecting zigbee-herdsman logs to iobroker logs
  • (kirovilya) Additional states for QBKG12LM

New devices:

  • (kirovilya) BlitzWolf BW-IS3, Paulmann 500.67, Paulmann 798.09
  • (kirovilya) DiY Geiger counter https://modkam.ru/?p=1591
  • (kirovilya) DiY 8 Relays + 8 switches https://modkam.ru/?p=1638
  • (kirovilya) DiY Freepad https://github.com/diyruz/freepad
  • (kirovilya) Neo Zigbee Siren Alarm https://szneo.com/en/products/show.php?id=241
  • (Shade) RB 278 T
  • (arteck) TS0601_thermostat
  • (arteck) TS0121
  • (arteck) GL-D-004Z
  • (Shade) WXKG07LM
  • (drohne200) 1746430P7
  • (sebastian) 4058075816459
  • (itProfi) SGMHM-I1
  • (arteck) owvfni3
  • (arteck) TS0001, TS0111
  • (Daniel Dreier) Paulmann 500.45
  • (arteck) ZK-EU-2U
  • (Newan) Busch-Jaeger 6735/6736/6737
  • (andrico21) ZM-L03E-Z
  • (arteck) 915005106701, 9290018187B
  • (frankjoke) HGZB-20-UK, GL-W-001Z
  • (arteck) 4034031P7, 3435011P7
  • (arteck) TS0041
  • (agross) 5062231P7, 5062431P7
  • (kirovilya) TI0001-switch, TI0001-socket
  • (arteck) RB 178 T
  • (arteck) HGZB-07A, AV2010/22, AV2010/22A, TS0041, TS0043
  • (nbars) E1744
  • (Florian Look) GS361A-H04
  • (arteck) ICZB-IW11SW
  • (kirovilya) HS2WD-E
  • (Sacred-Shadow) FL 130 C
  • (arteck) HS3SA, 9290022169, 4096730U7, AC10787, SP 220, SP 222, SP 224, 07004D, BW-IS2, InstaRemote
  • (kirovilya) MCLH-08, MCLH-05
  • (Sacred-Shadow) 1746130P7
  • (mar565) GUNNARP panel round
  • (Erdnuss3003) 4090531P7

1.1.1 (2020-04-17)

  • (kirovilya) Critical. Fixed error starting adapter if cc-chip was only flashed
  • (kirovilya) Nue/3A FNB56-ZSW02LX2.0
  • (Strunzdesign) Added missing raw button events for Philips Hue Smart Button ROM001
  • (Sacred-Shadow) Fix Color for Outdoor Lantern W RGBW OSRAM

1.1.0 (2020-04-12)

new Zigbee-herdsman features:

  • ConBee/RaspBee (experimental support) Koenkk/zigbee-herdsman#72
  • OTA update for some devices (IKEA, OSRAM and other) Koenkk/zigbee2mqtt#2921
  • Touchlink reset and join Koenkk/zigbee2mqtt#2396
  • Green Power devices support Koenkk/zigbee2mqtt#3322
  • (peterfido) iCasa KPD14S und KPD18S hinzu
  • (kirovilya) Moes Zigbee Thermostatic Radiator
  • (kirovilya) LifeControl power plug MCLH-03, bulb MCLH-02, water leak MCLH-07, door sensor MCLH-04
  • (kirovilya) Philips LCT002, LCT011, LTW015, LWG004
  • (kirovilya) Gledopto GL-C-007 with a channel
  • (MultivitaminJuice) Iluminize 511.040
  • (Sacred-Shadow) Bitron 902010/24
  • (kirovilya) Color indication of LQI and Battery icon
  • (kirovilya) Device info modal dialog
  • (arteck) Philips LCT026
  • (obakuhl) Improvements Osram switch mini
  • (arteck) Nue / 3A FB56+ZSW1GKJ2.5, LXN-1S27LX1.0
  • (agross) Philips Signe Floor and Table
  • (arteck) TRADFRI bulb E14 WS 470lm, OSRAM PAR16 TW Z3
  • (kirovilya) Smart remote controller (4 buttons)
  • (allofmex) OTA updates
  • (kirovilya) Aqara opple change mode keys (for binding)
  • (palsch) Heiman HS2WD-E siren

1.0.4 (2020-03-14)

  • (kirovilya) Philips Hue Adore Bathroom Mirror Light
  • (kirovilya) Oujiabao Gas and carbon monoxide alarm
  • (kirovilya) Tuya SOS button
  • (Erdnuss3003) Schwaiger ZBT-DIMLight-GLS0800
  • (arteck) Smart Home Pty FB56-ZCW11HG1.4, LXT56-LS27LX1.7
  • (arteck) Xiaomi plug lumi.plug.mmeu01
  • (arteck) Innr RS 228 T, RS 230 C
  • (arteck) Gledopto GL-MC-001, GL-D-003ZS
  • (allmyjoes) Bitron AV2010/21A
  • (arteck) Osram Panel TW 595 UGR22
  • (kirovilya) IKEA SURTE door WS 38x64
  • (andigandi) Philips Hue LCG002, Hue LTG002
  • (arteck) iCasa ICZB-FC
  • (arteck) Osram A60 DIM Z3
  • (arteck) Paulmann 371000001
  • (DaCHRIS) Osram PAR16 DIM Z3
  • (DaCHRIS) Philips LWG001
  • (DaCHRIS) Illuminize 511.202
  • (SchumyHao) TERNCY-SD01 knob dimmer
  • (SchumyHao) Xiaomi lumi.lock.aq1
  • (kirovilya) New eWeLink devices: button, TH sensor, contact sensor, motion sensor
  • (kirovilya) Allow pairing to routers (again)
  • (Erdnuss3003) Philips Hue LCT021
  • (root) Trust ZWLD-100 water leak sensor
  • (smartpran) Bitron AV2010/32

1.0.3 (2020-02-09)

  • (Tw1nh34d) Hornbach FLAIR LED
  • (asgothian) Hue smart button, Heiman smoke sensor
  • (kirovilya) Philips LTC014, LTC015
  • (kirovilya) Power states for QBKG11LM
  • (Garfonso) Change role for occupancy state to 'sensor.motion'
  • (kirovilya) Change illuminance state to illuminance_lux (for lux value)
  • (arteck) Philips LCF002
  • (arteck) TRADFRI open/close remote
  • (kirovilya) Tuya sensor TS0201

1.0.2 (2020-01-29)

  • (kirovilya) All button events for Aqara Opple switch
  • (ma-john) OSRAM PAR16 RGBW Z3
  • (arteck) Phillips LWA004
  • (MiniMe6666) Heiman SmokeSendor-N-3.0
  • (kirovilya) Force remove device
  • (kirovilya) Fix some networkmap bugs
  • (kirovilya) Extended info button
  • (kirovilya) Long press for WXKG01LM

1.0.1 (2020-01-23)

  • fix for old z-stack firmware

1.0.0 (2020-01-22)

  • Powered by new zigbee-herdsman library and new converters database
  • Drop support NodeJS 6
  • Serialport 8.0.5 (in zigbee-herdsman)
  • More new devices
  • Some design update
  • Binding

License

The MIT License (MIT)

Copyright (c) 2018-2024 Kirov Ilya [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.zigbee's People

Contributors

agross avatar allofmex avatar aokhrimenko avatar apollon77 avatar arteck avatar asgothian avatar dependabot[bot] avatar diginix avatar garfonso avatar germanbluefox avatar kirovilya avatar ldittmar81 avatar lebrinkma avatar mcm1957 avatar modmax avatar newan avatar o0shojo0o avatar obakuhl avatar paulchenplump avatar peterfido avatar petervoronov avatar sacred-shadow avatar schmidti2007 avatar schumyhao avatar simatec avatar sonntam avatar strunzdesign avatar theimo1221 avatar unclesamswiss avatar vlgorskij avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

iobroker.zigbee's Issues

delete device

when device has a many rows in db then i have to press the delete buttun several times
i think we need here a loop for all rows to delete

Flashing cc2530/cc2591 with Arduino

Hi.
I tried to flash a cc2530/cc2591 with an Arduino Uno. It seems that the connection is ok:

INFO: Found a CC2530 chip on COM5

Chip information:
      Chip ID : 0xa524
   Flash size : 16 Kb
    Page size : 2 Kb
    SRAM size : 1 Kb
          USB : No

Device information:
 IEEE Address : 000000000000
           PC : 0000

Debug status:
 [ ] CHIP_ERASE_BUSY
 [ ] PCON_IDLE
 [X] CPU_HALTED
 [ ] PM_ACTIVE
 [ ] HALT_STATUS
 [X] DEBUG_LOCKED
 [X] OSCILLATOR_STABLE
 [ ] STACK_OVERFLOW

Debug config:
 [ ] SOFT_POWER_MODE
 [ ] TIMERS_OFF
 [ ] DMA_PAUSE
 [ ] TIMER_SUSPEND

But when I tried to flash the CC2530ZNP-Test_for_CC2591.hex I got the following error:
IOError: Line 1: Source file is not in HEX format! Do I need a special version for an arduino-flash?

Thanks for your help.
Boris

Hue for Yahka Adapter

Hi team,

I want to add my IKEA TRADFRI bulb E27 CWS opal 600lm with RGB support to the IOBroker Yahka Adapter for HomeKit Usage.

But:
ioBroker.zigbee wants an RGB value for the colors

Yahka gives only a hue value from 0 to 360. Ist there a way to make this compatible?

Without selected COM port no connection should be tried ...

... else erros in log:

2018-09-27 21:37:41.869  - error: zigbee.0 Join failure.. Error: Shepherd is not enabled.
2018-09-27 21:38:29.899  - info: zigbee.0 Starting zigbee-shepherd
2018-09-27 21:38:29.937  - error: zigbee.0 Error while starting zigbee-shepherd!. TypeError: "path" is not defined: 

Ikea Tradfri Light Bulb

Hello,

how can IKEA Lightbulb be connected to the iobroker without gateway?

Thank you for your help

plz implement Switch 4x EU-LIGHTIFY

{
        zigbeeModel: ['Switch 4x EU-LIGHTIFY'],
        model: 'TODO',
        vendor: 'OSRAM',
        description: 'LIGHTIFY Switch 4x',
        supports: 'TODO',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.bind('genOnOff', coordinator, cb),
                (cb) => device.bind('lightingColorCtrl', coordinator, cb),
                (cb) => device.bind('genLevelCtrl', coordinator, cb),
                (cb) => device.bind('genPowerCfg', coordinator, cb),
            ];

            execute(device, actions, callback);
        },
},

click

Error Log from Adapter

Sorry .. I don't speak Zigbee:

https://pastebin.com/4NFXtsjP

And now and then if I go into configuration I get the message that I need to configure and save the adapter first before I pair something. But something is already paired.
But generally all seems to work .. just thought it might be helpful to let you devs know.

host.raspi 2018-09-23 08:09:50.018 info instance system.adapter.zigbee.0 terminated with code 0 (OK) Caught 2018-09-23 08:09:50.016 error by controller[7]: Sun, 23 Sep 2018 06:09:49 GMT cc-znp:SREQ --> ZDO:mgmtPermitJoinReq, { addrmode: 15, dstaddr: 65532, duration: 0, tcsignificance: 0 } Caught 2018-09-23 08:09:50.016 error by controller[6]: Sun, 23 Sep 2018 06:09:49 GMT zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq Caught 2018-09-23 08:09:50.016 error by controller[5]: status: 'online' } ] Caught 2018-09-23 08:09:50.016 error by controller[5]: parent: '0x00124b0014d9de74', Caught 2018-09-23 08:09:50.015 error by controller[5]: deviceType: 2, Caught 2018-09-23 08:09:50.015 error by controller[5]: depth: 1, Caught 2018-09-23 08:09:50.015 error by controller[5]: lqi: 12, Caught 2018-09-23 08:09:50.015 error by controller[5]: nwkAddr: 2909, Caught 2018-09-23 08:09:50.015 error by controller[5]: Sun, 23 Sep 2018 06:09:23 GMT zigbee:controller debug lqiScan result: [ { ieeeAddr: '0x00158d000278e743', Caught 2018-09-23 08:09:50.015 error by controller[4]: Sun, 23 Sep 2018 06:09:23 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtLqiRsp Caught 2018-09-23 08:09:50.015 error by controller[3]: Sun, 23 Sep 2018 06:09:23 GMT cc-znp:AREQ <-- ZDO:mgmtLqiRsp, { srcaddr: 0, status: 0, neighbortableentries: 1, startindex: 0, neighborlqilistcount: 1, neighborlqilist: [ { extPandI Caught 2018-09-23 08:09:50.014 error by controller[2]: Sun, 23 Sep 2018 06:09:23 GMT cc-znp:SRSP <-- ZDO:mgmtLqiReq, { status: 0 } Caught 2018-09-23 08:09:50.014 error by controller[1]: Sun, 23 Sep 2018 06:09:23 GMT cc-znp:SREQ --> ZDO:mgmtLqiReq, { dstaddr: 0, scanchannels: undefined, scanduration: undefined, startindex: 0 } Caught 2018-09-23 08:09:50.014 error by controller[1]: Sun, 23 Sep 2018 06:09:23 GMT zigbee-shepherd:request REQ --> ZDO:mgmtLqiReq host.raspi 2018-09-23 08:09:49.935 info stopInstance system.adapter.zigbee.0 killing pid 14553

Tradfri E14 bulb

Please could you add a picture of Tradfri E14 bulb? All other tradfri bulbs have pictures but E14 doesnt.

CC2531 as router?

Is there a firmware to use a CC2531 as router? Unfortunately I only have an arduino for flashing. I can't reach the sensors in the basement.
Thx
Boris

error after stop the adapter

Caught | 2018-07-08 22:05:38.004 | error | by controller[24]: Sun, 08 Jul 2018 20:05:32 GMT zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq
Caught | 2018-07-08 22:05:38.004 | error | by controller[23]: Sun, 08 Jul 2018 20:05:32 GMT cc-znp:SREQ --> AF:dataRequest, { dstaddr: 33463, destendpoint: 11, srcendpoint: 1, clusterid: 6, transid: 23, options: 48, radius: 30, len: 3, data:
Caught | 2018-07-08 22:05:38.003 | error | by controller[22]: Sun, 08 Jul 2018 20:05:32 GMT zigbee-shepherd:request RSP <-- AF:dataRequest
Caught | 2018-07-08 22:05:38.003 | error | by controller[21]: Sun, 08 Jul 2018 20:05:32 GMT cc-znp:SRSP <-- AF:dataRequest, __timeout__
Caught | 2018-07-08 22:05:38.002 | error | by controller[20]: Sun, 08 Jul 2018 20:05:29 GMT cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14835, destendpoint: 11, srcendpoint: 1, clusterid: 6, transid: 22, options: 48, radius: 30, len: 3, data:
Caught | 2018-07-08 22:05:38.002 | error | by controller[19]: Sun, 08 Jul 2018 20:05:29 GMT zigbee-shepherd:request RSP <-- AF:dataRequest
Caught | 2018-07-08 22:05:38.001 | error | by controller[18]: Sun, 08 Jul 2018 20:05:29 GMT cc-znp:SRSP <-- AF:dataRequest, __timeout__
Caught | 2018-07-08 22:05:38.000 | error | by controller[17]: Sun, 08 Jul 2018 20:05:28 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 23
Caught | 2018-07-08 22:05:38.000 | error | by controller[16]: 2018-07-08T20:05:28.017Z zigbee:controller debug Zigbee publish to '0x0017880103dcc9d2', genOnOff - cmd off - payload {} - endpoint 11 undefined
Caught | 2018-07-08 22:05:37.999 | error | by controller[15]: Sun, 08 Jul 2018 20:05:26 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 22
Caught | 2018-07-08 22:05:37.999 | error | by controller[14]: 2018-07-08T20:05:26.874Z zigbee:controller debug Zigbee publish to '0x00178801026e5c91', genOnOff - cmd on - payload {} - endpoint 11 undefined
Caught | 2018-07-08 22:05:37.998 | error | by controller[13]: Sun, 08 Jul 2018 20:05:26 GMT cc-znp:SREQ --> AF:dataRequest, { dstaddr: 18203, destendpoint: 11, srcendpoint: 1, clusterid: 6, transid: 21, options: 48, radius: 30, len: 3, data:
Caught | 2018-07-08 22:05:37.998 | error | by controller[12]: Sun, 08 Jul 2018 20:05:26 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 21
Caught | 2018-07-08 22:05:37.997 | error | by controller[11]: 2018-07-08T20:05:26.009Z zigbee:controller debug Zigbee publish to '0x0017880102de40ac', genOnOff - cmd off - payload {} - endpoint 11 undefined
Caught | 2018-07-08 22:05:37.997 | error | by controller[10]: Sun, 08 Jul 2018 20:05:25 GMT zigbee-shepherd:request RSP <-- AF:dataRequest
Caught | 2018-07-08 22:05:37.996 | error | by controller[9]: Sun, 08 Jul 2018 20:05:25 GMT cc-znp:SRSP <-- AF:dataRequest, __timeout__
Caught | 2018-07-08 22:05:37.996 | error | by controller[8]: Sun, 08 Jul 2018 20:05:22 GMT cc-znp:SREQ --> AF:dataRequest, { dstaddr: 33463, destendpoint: 11, srcendpoint: 1, clusterid: 6, transid: 20, options: 48, radius: 30, len: 3, data: <
Caught | 2018-07-08 22:05:37.995 | error | by controller[7]: Sun, 08 Jul 2018 20:05:22 GMT zigbee-shepherd:request RSP <-- AF:dataRequest
Caught | 2018-07-08 22:05:37.995 | error | by controller[6]: Sun, 08 Jul 2018 20:05:22 GMT cc-znp:SRSP <-- AF:dataRequest, __timeout__
Caught | 2018-07-08 22:05:37.994 | error | by controller[5]: Sun, 08 Jul 2018 20:05:21 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 20
Caught | 2018-07-08 22:05:37.994 | error | by controller[4]: 2018-07-08T20:05:21.526Z zigbee:controller debug Zigbee publish to '0x0017880103dcc9d2', genOnOff - cmd on - payload {} - endpoint 11 undefined
Caught | 2018-07-08 22:05:37.993 | error | by controller[3]: Sun, 08 Jul 2018 20:05:19 GMT cc-znp:SREQ --> AF:dataRequest, { dstaddr: 18203, destendpoint: 11, srcendpoint: 1, clusterid: 6, transid: 19, options: 48, radius: 30, len: 3, data: <
Caught | 2018-07-08 22:05:37.993 | error | by controller[2]: Sun, 08 Jul 2018 20:05:19 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 19
Caught | 2018-07-08 22:05:37.991 | error | by controller[1]: 2018-07-08T20:05:19.529Z zigbee:controller debug Zigbee publish to '0x0017880102de40ac', genOnOff - cmd on - payload {} - endpoint 11 undefined
zigbee.0 | 2018-07-08 22:05:32.894 | info | terminating
zigbee.0 | 2018-07-08 22:05:32.854 | debug | cleaned everything up...
host.zigbee-RasPi | 2018-07-08 22:05:32.846 | info | stopInstance system.adapter.zigbee.0 killing pid 419
host.zigbee-RasPi | 2018-07-08 22:05:32.845 | info | stopInstance system.adapter.zigbee.0

Cannot get the Node Descriptor of the Device xxxxxx

018-07-04 06:10:55.933 | error | Cannot get the Node Descriptor of the Device: 0x84182600000b911f (Error: request unsuccess: 16)
zigbee.0 | 2018-07-04 06:10:55.898 | error | Cannot get the Node Descriptor of the Device: 0x84182600000e4d12 (Error: request unsuccess: 16)
zigbee.0 | 2018-07-04 06:10:55.862 | error | Cannot get the Node Descriptor of the Device: 0x8418260000016523 (Error: request unsuccess: 16)
zigbee.0 | 2018-07-04 06:10:55.809 | error | Cannot get the Node Descriptor of the Device: 0x8418260000012920 (Error: request unsuccess: 16)

hmmm. What that.. the lamps are on and controllable.. are only osram devices

Problems when sending more than one command to a lightbulb

Hi Team!

I have a problem with all my lights paired to Zigbee Adapter.

Lets say I have a script like this:
setState("zigbee.0.----------------.state"/switch/, true);
setState("zigbee.0.----------------.colortemp"/color Temp/, 0);
setState("zigbee.0.----------------.brightness"/brightness/,100);

Three commands. The first one is always (!!) ok and working 100 %. With the second and third a have a high risk that it doesn't work.

Errors look like:
zigbee.0 2018-08-17 22:10:20.726 error Zigbee publish to '0x.----------------', genOnOff - on - {} - 1 failed with error Error: Timed out after 30000 ms
zigbee.0 2018-08-17 22:10:05.702 error Zigbee publish to '0x.----------------', genOnOff - off - {} - 1 failed with error Error: rsp error: 17
zigbee.0 2018-08-17 22:10:05.603 error Zigbee publish to '0x.----------------', genOnOff - on - {} - 1 failed with error Error: rsp error: 17
zigbee.0 2018-08-17 22:10:05.571 error Zigbee publish to '0x.----------------', genLevelCtrl - moveToLevel - {"level":100,"transtime":0} - 1 failed with error Error: rsp error: 17

If I put a delay of 3,5 Seconds between the commands everthing is working 100%. But without delay chaos. As I said, the first command is always ok. With the second and third it is like lottery. This is valid for ALL my devices. I hear in IOBroker Forum other peoble are also having this problem.

What can be done? Any ideas? This problem makes real life use...difficult... ;(

ZigBee-Adapter bleibt rot

Hallo,

beim start des Adapters, bleibt dieser rot und wirft einige Fehler.

Als Hardware ist ein Raspberry 3 und der geflashte CC253 im Einsatz.

Hier der entsprechende Teil des Log-Files:
.adapter.zigbee.0 because enabled 2018-09-27 17:59:46.471 - info: host.ioBroker-RasPi instance system.adapter.zigbee.0 started with pid 23382 2018-09-27 17:59:47.536 - error: Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:96 2018-09-27 17:59:47.536 - error: Caught by controller[0]: throw err 2018-09-27 17:59:47.536 - error: Caught by controller[0]: ^ 2018-09-27 17:59:47.536 - error: Caught by controller[0]: Error: Could not locate the bindings file. Tried: 2018-09-27 17:59:47.536 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/serialport.node 2018-09-27 17:59:47.536 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/Debug/serialport.node 2018-09-27 17:59:47.536 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/Release/serialport.node 2018-09-27 17:59:47.537 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/out/Debug/serialport.node 2018-09-27 17:59:47.537 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/Debug/serialport.node 2018-09-27 17:59:47.537 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/out/Release/serialport.node 2018-09-27 17:59:47.538 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/Release/serialport.node 2018-09-27 17:59:47.538 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/default/serialport.node 2018-09-27 17:59:47.538 - error: Caught by controller[0]: → /opt/iobroker/node_modules/serialport/compiled/8.11.4/linux/arm/serialport.node 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:93:9) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/serialport/lib/bindings/linux.js:2:36) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at Module._compile (module.js:652:30) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at Object.Module._extensions..js (module.js:663:10) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at Module.load (module.js:565:32) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at tryModuleLoad (module.js:505:12) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at Function.Module._load (module.js:497:3) 2018-09-27 17:59:47.538 - error: Caught by controller[0]: at Module.require (module.js:596:17) 2018-09-27 17:59:47.539 - error: Caught by controller[0]: at require (internal/module.js:11:18) 2018-09-27 17:59:47.539 - error: Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/serialport/lib/bindings/auto-detect.js:16:22) 2018-09-27 17:59:47.539 - error: host.ioBroker-RasPi instance system.adapter.zigbee.0 terminated with code 1 () 2018-09-27 17:59:47.539 - info: host.ioBroker-RasPi Restart adapter system.adapter.zigbee.0 because enabled

Kann mir jemand sagen, woran das liegt? COM-Port ist angegeben.

Gruß Jonas

Philips HUE RWL021

Philips HUE RWL021 is detected in the iobroker and displayed under Objects. Unfortunately, when pressing the buttons on the remote control no reaction in the iobroker. Under zigbee2mqtt the remote control can be operated correctly. Is it possible to repair this at ioBroker.zigbee so that Philips HUE RWL021 can be used in iobroker.

Sincerely

Network map does not show connections

I can open the network-map tab and all devices are shown but there are no connections visible.
The refresh butten is inactive.

iobroker error log every time I open network map:

`

2018-08-16 07:44:04.009 - error: zigbee.0 message messagebox.system.adapter.zigbee.0 [object Object] this.shepherd.lqiScan is not a function
2018-08-16 07:44:04.010 - error: zigbee.0 TypeError: this.shepherd.lqiScan is not a function
at ZigbeeController.getMap (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:273:23)
at getMap (/opt/iobroker/node_modules/iobroker.zigbee/main.js:320:19)
at Adapter. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:114:21)
at emitOne (events.js:96:13)
at Adapter.emit (events.js:188:7)
at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3400:34)
at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
at Socket.onevent (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:278:10)
at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12)

`

check a offline device

when one device are offline

zigbee.0 | 2018-07-08 08:47:20.013 | error | Cannot get the Node Descriptor of the Device: 0x8418260000012920 (Error: Timed out after 10000 ms)

is the other processing very slow..
any idea why??

Change UART ports

Hello! I have this device. How I can change UART ports from P0_2, P0_3 to P1_4, P1_5 in firmware?

Здравствуйте! У меня есть такой модуль. Подскажите, пожалуйста, как мне поменять UART порты с P0_2, P0_3 на P1_4, P1_5 в прошивке чтобы была возможность использовать штатный usb-serial конвертер? В наличии есть IAR и CC Debugger.

battery stat from xiaomi

can you check the xiaomi battery handling. my sensoers and switsches has wrong batt percent
grafik

battery was removed and replaced.. same result

Xiaomi wireless switch with less functionality as zigbee2mqtt

zigbee2mqtt supports single, double, triple, quadruple click for Xiaomi Aqara wireless switch (WXKG11LM)

With this adapter I only get single and double click objects in iobroker.

Is it possible to enhance the functionality with triple at least?

Integrate keypad from Centralite

Hi kirovilya, can you possibly try to integrate the Centralite keypad?
It works with the ZigBee standard.

ZigBee Home Automation 1.2 Compatibility
The 3-Series Security Keypad is fully ZigBee HA 1.2
certified and is compatible with ZigBee HA 1.2-certified
hubs and devices.

Here is a link:
https://centralite.com/products/security-keypad
https://centralite.com/downloads/DataSheet-3SeriesSecurityKeypad.pdf
https://www.smarthome.de/geraete/centralite-security-tastenfeld-weiss

Max Number of same End-Devices?

Hi
I'm running a CC2531 USB Stick on a Raspberry Pi with ioBroker. Additionaly I run a second Stick CC2531 USB Stick as a router. Everthing works so far but it seems that i have a problem with maximum supported devices. I have paired 20 devices of type "MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)". I want to pair another 5 of theese devices. But pairing seems not possible anymore. the pairing-Process doesn't find any of them. Is there a limit of 20 Devices of "same type"?

Brightness and color for heu stripe

when i put color to blue i can not set brightness to 254.. the blue color is very dark..
I can not do both, set blue and bright

i found this for brightness and color set..
wiki
any idea ??

TRADFRI wireless dimmer

Hello,
can you please implement the IKEA TRADFRI wireless dimmer ?
The friendly project ZIGBEE2MQTT has it implementated but it would be nice to controll it directly in the Zigbee iobroker adapter.

Thank you,
Axel

invert state for lumi.sensor_magnet

for iobroker we need a configurable state for lumi.sensor_magnet
magnet close = false
magnet open = true

or

magnet close = true
magnet open = false

i think in admin we can make a checkbox for this

communication problems

after update to ver 0.6 and raspi restart i have communications problem to many devices
first..its ok


zigbee.0 | 2018-07-08 22:00:55.717 | info | (0x0017880102f054a7): TODO - Philips Hue white GU10 (Router)
-- | -- | -- | --
zigbee.0 | 2018-07-08 22:00:55.716 | info | (0x84182600000b911f): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
zigbee.0 | 2018-07-08 22:00:55.716 | info | (0x00158d0001052cc5): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 | 2018-07-08 22:00:55.716 | info | (0x00158d0001573a56): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
zigbee.0 | 2018-07-08 22:00:55.715 | info | (0x84182600000e4d12): AB3257001NJ - OSRAM Smart+ plug (Router)
zigbee.0 | 2018-07-08 22:00:55.715 | info | (0x00158d0001de760b): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0 | 2018-07-08 22:00:55.714 | info | (0x0017880102e251de): unkown - undefined unknown (EndDevice)
zigbee.0 | 2018-07-08 22:00:55.713 | info | (0x00158d00018b3ed8): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
zigbee.0 | 2018-07-08 22:00:55.713 | info | (0x00158d0001f5621b): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0 | 2018-07-08 22:00:55.712 | info | (0x0017880103648612): 915005106701 - Philips Hue white and color ambiance LightStrip plus (Router)
zigbee.0 | 2018-07-08 22:00:55.712 | info | (0x0017880103dcc9d2): TODO - Philips Hue white GU10 (Router)
zigbee.0 | 2018-07-08 22:00:55.711 | info | (0x0017880102de40ac): TODO - Philips Hue white and color ambiance GU10 (Router)
zigbee.0 | 2018-07-08 22:00:55.710 | info | (0x00178801026e5c91): 8718696449691 - Philips Hue White Single bulb B22 (Router)
zigbee.0 | 2018-07-08 22:00:55.710 | info | (0x00158d0001e4508f): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)

but after state change

Failed to configure 0x84182600000e4d12

from here i have no control ..

after restart adapter only

zigbee.0 | 2018-07-08 22:07:08.900 | error | Error while starting zigbee-shepherd!. Error: request timeout
zigbee.0 | 2018-07-08 22:07:00.851 | info | Starting zigbee-shepherd

Converter issue with lumi.sensor_motion.aq2

I just paired the AQARA motion sensor lumi.sensor_motion.aq2 successfully and configured it via Blockly-Script to turn on lights when motion recognized. My goal is to keep the the sensor recognizing new motions immediatly, after first motion recognition.

By default the motion-sensor = occupancy is set to true when motion recognized and it remains in status true for exactly 60 sec. This means that the sensor is not able to recognize new motions within the 60 seconds.
Therefore I force the occupancy value via Blockly-Script from true to false after 3 secs, when motion has been recognized. Actually it worked for a while very good and as intended , but after 4-5 hours I am facing the following issues:

  1. I receive this error-msg in the logs:

converter

  1. After forcing it to false via script, the value doesn't switch to true anymore for exactly 60 sec, even if I move myself directly in front of the sensor. So within this 60 sec no new motion recognition is possible.

It it possible to fix this?

I've installed iobroker.zigbee 0.7.1 and zigbee-shepherd-converters v2.0.42

Thank you in advance.

a few questions

after new flash the device cc2531 the knows devices should work direktly or after re-pairing??

CC2530 als Slave

Hallo,
Habe neben dem CC2531 als Master auch einen CC2530 als Slave installiert.
Die Kommunikation der gepairten Geräte am CC250 funktioniert.
Nur im iobroker wird beim CC230 unter Switch State "false" eingetragen.
Somit kann man die Kommunikation nicht überwachen.
Beste Grüße

brightness percentage

for iobroker we need a configurable or static value from 0% to 100%

0%=0
100%=254

i think a value for percentage is available direct in device object

grafik

Xiaomi AQara keine binding

Guten Abend,

bekomme den Xiaomi AQara nicht gebindet. Drücke den Knopf einmal am AQara bis es blau blink leider keine Verbindung zum zigbee auf Io

Error: Cannot get the Node Descriptor of the Device

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.