Joined in 2023 
82 
63 About this deal
First batch is said to come pre-flashed with their own build of Silicon Labs EmberZNet 6.10.3 firmware (revision 6.10.3-41) which does work out-of-the-box with ZHA and Zigbee2MQTT, however, note that Zigbee2MQTT currently only offers experimental support for Silabs EZSP.
Most experienced Zigbee users in the community know that Texas Instruments CC2652P is together with the competing Silicon Labs EFRMG21 chips at this time the most capable and most powerful multi-protocol MCU with 2.4 GHz radios on the market. CC2652P radio chip is currently also the most popular as a Zigbee Coordinator and Zigbee Router in the DIY Zigbee userbase community because it is newer so the firmware is well maintained and is stable/mature in both Zigbee2MQTT and the built-in ZHA integration for Home Assistant. Just like Silabs EFRMG21, TI’s CC2652P feature an integrated Power Amplifier that is technically capable of +20 dBM amplification (though legally the firmware is probably not allowed to be configured to use more than +10 dBM amplification).Looks like @CoolKit-Technologies = Shenzhen Cool House Technology Co., Ltd. (abbreviated as Cool House Technology) might be the Chinese manufacturer of this SM-011 V1.0 / ZYZBP008 module: The feature ability to change Zigbee channel without re-pairing devices is discussed with zigpy developers here → Is it (technically) possible to change ZigBee channel without having to re-pair every device? · Discussion #908 · zigpy/zigpy · GitHub As seen on this previous pull request will also need the standard VID and PID used for CH9102F chips:
For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description. Put your device in pairing mode and it should appear very soon (piring mode is normally only open for 10-60 seconds depending on manufacturer, model and firmware). Elelabs_EzspFwUtility: Error: install code setup failed. Is an install code flashed onto the device? And sleeping end devices is normally using 1/10 of its maximal normal power out put. and need good parents in the near for working well and not burning there batteries. However, if you are using the Zigbee2MQTT (Z2M) application instead of ome Assistant’s ZHA integration then know that Zigbee2MQTT software code for EZSP (EmberZNet Serial Protocol) support for Silabs based adapters is not yet mature and still listed as “experimental”. It is my understanding that they need more developers or testers actively working on their ezsp code in the zigbee-herdsman library that Zigbee2MQTT depends on. So, for now, Texas Instruments CC2652 and CC1352 based adapters is the way to go for a stable experience if use Zigbee2MQTT for “production” at home.at SerialDriver.handleDATA (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:228:14) You need to configure the TTY port you wish to use for the OTBR to connect your RCP at startup. Look for the TTY port of your RCP device. The easiest way to do this is to look for a /tty/dev... entry once the RCP is connected. It should generally either be /dev/ttyUSB0 or /dev/ttyACM0. PS: The "ZBDongle-E" USB "product description id" has also "SONOFF Zigbee 3.0 USB Dongle Plus V2" written to EEPROM of WCH CH9102F USB-to-UART bridge on the board to enable auto-discovered of the USB-adapter for ZHA integration in Home Assistant.
Updated thread with price + links and some new information from ITead after the product was released. That will add USB identifiers for VID (Vendor ID)+ PID (Product ID) in combination with "Product Description ID" as unique identifier for it:https://github.com/home-assistant/home-assistant.io/blob/68fe05453ec6da839320f68acd471deaee19b888/source/_integrations/zha.markdown On your SD card, make sure you flash the Raspbian Stretch Lite OS image or Raspbian Stretch with Desktop. Silicon Labs Simplicity Studio included "Flash Programmer" ( instructions) (can't find your device? read below!) Debug 2022-08-31 08:16:43Received Zigbee message from '0x00158d000894fa97', type 'attributeReport', cluster 'genBasic', data '{"appVersion":5,"modelId":"lumi.sensor_motion.aq2"}' from endpoint 1 with groupID 0 Bad reception caused by either long distances or interference will cause the Zigbee devices to keep resending their messages and thus draining the battery from battery-operated devices.
Great Deal 
New Comment