egony / cc2652p_e72-2g4m20s1e Goto Github PK

The firmware LED must be re-flashed to be normal, but it will not light up after several reboots

@egony Can you please consider providing OpenThread Border Router (OTBR) "RCP mode" firmware images well as "NCP mode" firmware images (with support for the OpenThread spinel+hdlc+uart protocol) and preferably using the latest SDK for this Texas Instruments CC2652 based adapter so that it will be compatible with the "OpenThread Border Router Add-on" that Home Assistant developer agners (Nabu Casa employee Stefan Agner) is currently developing? Check out:

https://github.com/home-assistant/addons-development/tree/master/openthread_border_router

https://github.com/openthread/ot-br-posix/

https://github.com/agners

https://community.home-assistant.io/u/agners/summary

https://groups.google.com/g/openthread-users/

OTBR should be a "Thread Certified Component" Texas Instruments CC2652 based chips:

https://github.com/openthread/ot-cc13x2-cc26x2/blob/main/src/cc2652/README.md

https://github.com/openthread/ot-cc13x2-cc26x2

https://github.com/openthread/openthread/tree/main/examples/platforms

https://dev.ti.com/tirex/explore/node?node=APzU0zOtgnQIe0sFnHCfxg__BSEc4rl__LATEST

https://openthread.io/vendors/texas-instruments

https://www.threadgroup.org/What-is-Thread/Thread-Benefits#certifiedproducts

https://training.ti.com/thread-cc2652-cc1352

The main reason for this request is that an "RPC" firmware with OTBR (OpenThread Border Router) support will make your adapter will be compatible with upcoming Thread based "Matter" (Project CHIP / Connected Home over IP) devices if used in Home Assistant with their other add-ons for the that is also in development. This addon by agners requires that the radio hard a firmware in "RPC" mode instead of the no traditional "NCP" mode:

https://github.com/home-assistant/addons-development/tree/master/chip_controller_repl

https://github.com/home-assistant/addons-development/tree/master/chip_tool

https://github.com/project-chip/connectedhomeip

https://buildwithmatter.com

https://csa-iot.org/all-solutions/matter/

Also having optional OpenThread "NCP" border router firmware would allow users to alternatively use other existing OpenThread applications that use "NCP" mode instead of the newer "RPC" mode which require additional component running on the host. Ex:

https://github.com/openthread/wpantund

Note that so far agners has only worked with Silicon Labs based adapter with OpenThread "RPC" firmware for Thread based Matter (as well as ESP32-C3 based devkit for Matter over WiFi) and that is only because it is a Silabs EFR32MG21 chip based adapter that will ship inside the official Home Assistant Yellow (formerly Home Assistant Amber) hardware:

zigpy/zigpy#894

https://github.com/home-assistant/addons-development/tree/master/silabs-multiprotocol

https://www.home-assistant.io/blog/2021/09/13/home-assistant-yellow/

https://www.crowdsupply.com/nabu-casa/home-assistant-yellow

PS: By the way, you might be interested in the the "Matter" workshop that Home Assistant is holding on the 15th of June even if they are in that specific workshop will not use a Thread based controller or devices and instead use a WiFi (+ Bluetooth) based "Matter" devices:

https://www.home-assistant.io/blog/2022/05/29/matter-in-home-assistant-workshop-announcement/

https://www.youtube.com/watch?v=9fOHBl5w0_k

https://community.home-assistant.io/t/matter-in-home-assistant-workshop-announcement/426129/

I want to update to the last available firmware, but there's only the "_Delete znp_CC2652P_E72_20220217.zi_p" so what's the latest functional version for now
Also because there none older version anymore on the github

Could you/somebody please compile a newest firmware version.
Latest version now here: 20220301 ( 2022) and we're now 2024 and there's a new 20230507 : https://github.com/Koenkk/Z-Stack-firmware/raw/Z-Stack_3.x.0_coordinator_20230507/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_other_coordinator_20230507.zip

Hello, thank you for the project.
This is not an issue, just a question.

Should I use J-link or XDS110 to flash CC2652P ?

Zigbee2MQTT:warn 2021-12-21 12:22:59: permit_join set to true in configuration.yaml.
Zigbee2MQTT:warn 2021-12-21 12:22:59: Allowing new devices to join.
Zigbee2MQTT:warn 2021-12-21 12:22:59: Set permit_join to false once you joined all devices.
Zigbee2MQTT:info 2021-12-21 12:22:59: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2021-12-21 12:22:59: Failed to set permit join to true

Hi Alex, congratulations for your work.
I build my own zigbee adapter using E72-2G4M20S1E chip.
I would like to ask you what are the differences between your latest coordinator firmware and the latest Koenkk one (https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_other_coordinator_20210120.zip).
I'm asking because i constantly find differences in radio performance between the two. Koenkk version give me better performance with sensors that have very low lqi. I tried it several times and the result is always the same. I even found that a far sensor that i use for test is seen with kk firmware (lqi= 0) but is unreachable with your latest version.
Did you change some radio setting in your last version respect to the Koenkk version?
Thank you.

Thanks for you great designs. Very appreciated.

I have a few questions about the firmware:

You wrote:
"Coordinator backup from 2538/2652/1352 can be loaded back into another 2538/2652/1352, but into CLEAN (never used with zigbee2mqtt) chip only. You can clear chip with zigbee2mqtt script scripts\zStackEraseAllNvMem.js"

1. What do you mean with coordinator backup ?

You wrote:
"As I know, sharing source codes prohibited by TI, so there is no sources here. And I can't made patches because they will include code. But you now what to do ;)"

2. Are you sure, because Koenkk is also sharing his patches. I can also download TI source code from TI site. I'am interested in your patches.
3. I don't understand what you mean with "But you now what to do" ?

You wrote:
"One of the features of this module is that it uses generator and RF-Switch settings that are not compatible with Koenkk's Launchpad firmware ."
and "Koenkk now also supports this module in their firmwares . "

4. Do you know if in the current koenkk firmware (Zigbeer E72 by Egony) the generator and RF-Switch settings are compatible now?

What happened

Hello

I recently updated my cc2652p_E72-2G4M20S1E firmware from 20210211 to 20210901
I followed the procédure https://github.com/egony/cc2652p_E72-2G4M20S1E/wiki/Flashing-EN

Flash was sucessfull and erased NVRAM at the end as described.

Since I got regulary 0x10: MEM_ERROR and Data request failed with error: 'MAC no resources' (26)

Need to unplug/plug the stick and work for a while.

I have only 28 devices and most of them are routers.

What did you expect to happen

Work as before

Debug info

Zigbee2MQTT version: Zigbee2MQTT version 1.21.1-dev (commit #58957a30) on RPI 3B+ Venv install
Adapter hardware: CC2652P E72-2G4M20S1E
Adapter firmware version: CC2652P_E72_20210901
log : zigbee2mqtt.zip

Добрый день! Можете помочь с этой проблемой? Koenkk/zigbee2mqtt#11202
вот временное решение.

Excuse me, what do these two LEDs mean? thank you!
I tried to find the answer in the design of the V3 board, but failed.

In README.md, I found that:
LEDs description:

• LED4 (Green) turns ON when High-power PA is not used (TX power from -20 to 5 dBm)
• LED3 (Red) turns ON when High-power PA is used (TX power from 15 to 20 dBm)
• LED1,2 supported in source code, but currently not used and perhaps never will be used.
• Leds can't be turned OFF by zigbee2mqtt config - sorry, I haven't skills for it.

But it doesn't seem to match v4.

Hello, can you make a no flow contrl firmware,

thank U

Using JLINK to write firmware succeeded, but could not run in ZigBee 2mqtt

Hello @egony,

and thanks for your great work brining ZigBee stick v4 to life!

This weekend I managed to build the PCB, but I have some questions about modifying the module to support external antenna. Here's a snapshot from the picture on your Wiki page:

https://github.com/egony/cc2652p_E72-2G4M20S1E/wiki

From what I could see at that picture, I've cut the tracks near the pins of the SMA connector, which I circled in red ink. But when I powered on the board, the LDO got really hot, so I disconnected the power supply. Measuring the resistance between the pins of the SMA connector, it appears that they are all shorted. So my question is - is the track, circled in yellow, also cut? I can't judge from the photo alone if it is just scratched or it is cut out.

Many thanks!

Will you consider making CC2674/CC2674P/CC2674R and/or CC1354/CC1354P Zigbee adapters for developers and early adopters?

Check out this developer discussion in Koenkk's Z-Stack firmware repository -> Koenkk/Z-Stack-firmware#476

There is no community firmware from Koenkk yet but that is probably partially because no one made a CC2674 or CC1354 adapter yet.

Chicken or the egg, what comes first, early prototype adapters that Koenkk can test or firmware built in the blind?

FYI, E72-2G4M20S1C (CC2674P10) radio module from Ebyte/Cdebyte is already available for prototyping and first-to-market devices:

https://www.cdebyte.com/products/E72-2G4M20S1C

According to LSagiroglu this new CC2674P10 based module is is pin to pin compatible with their CC2652P based module:

https://www.cdebyte.com/products/E72-2G4M20S1E

PS: No news so far from RFstar if they are working on CC2674P or CC1354P radio modules yet.

The LED on the board is always on (see the picture).It's too bright on my bedroom at night.Can I turn off it by configuration ？

my env：zigbee2mqtt at docker; flash the coordinator znp_CC1352P_E72_20220301.zip

Hi there

I have just finished building a Modkam V4. I have tried both FW and on these two versions I lose connectivity with my Tuya based devices. I have cloned the ieee address of my Modkam V3 Alternate which works perfectly fine with all my devices including Tuya ones. But as soon as I put the Modkam V4, I start to get error message that it cannot ping them. Also it is impossible to repair them.

As soon as I put back my Modkam V3, I get connectivity back. This is really strange, I already had this issue with some FW for the original version of Modkam V3, and they disappeared when I switched to the Alternate version. Now I see the same problem coming back again with :
-Modkam V4
-Sonoff USB 3.0 plus

I've tried all the latest FW on all these devices and I see the exact same behavior on all of them.
-I first loose connectivity to specific class of devices : Tuya plugs, Tuya Remote 3 buttons and Blitzwolf SHP13
-I cannot repair them, the interview of the Tuya plugs fails after Timeout, the Remote control does not even start the interview (no log at all as if it was emitting in a wrong frequency).
-All Xiaomi devices work totally fine with all FW versions, and all coordinators I tested
-As soon as I plug back my Modkam V3 Alternate, I regain connectivity to all Tuya devices, and I can totally repair them, interview never fails.

As I said, I already had this issue with previous versions of FW on the Modkam V3 original version.
What can cause such a behavior inside the FW so that it cannot connect specific class of devices. Is there a frequency range setting or a code multiplexing protocol compatibility ? It is really really strange that these exact same devices come back to life as soon as I plug a Modkam V3 Alternate version.

Coordinator hardware seems out of the equation as I have the exact same behavior with Sonoff USB 3.0 Plus and Modkam V4, except if the issue is coming from TI chip itself.

I don't understand how the FW can affect the ability to conduct proper transactions with the devices (ping, interviews...). I must be missing something.

Does anybody know if the Ebyte modules have a bootloader by factory or do I need a JTAG programmer?

Hi! Thanks for your great work with this.

I only want to know if the use of the script cc2538-bsl.py is mandatory for flashing, or you simply recommend it because it is open source and you have tested it but I can use other tools like the TI SmartRF Flash Programmer v2 or uniflash or there is something in the hardware that limits the tools to use...

Thanks in advance!

Can this devive work as Zigbee coordinator and bluetooth dongle?

Hello
With cc2652p chip I can't receive real time event of opening door as with Xiaomi MCCGQ11LM product.
The event is received several seconds after and it seems to be buffering.
I don't have any problem with CC2531 coordinator.
Can you please help me ?
Thank you

My z2m can't start

error 2021-09-06 13:39:54: Error while starting zigbee-herdsman

I tried to update stick firmware. I have CC2652P E72 2G4M20S1E. Looks like the update was success:

(zigbee2mqtt) homeassistant@raspberrypi:~ $ python3.8 cc2538-bsl.py -p /dev/ttyUSB0 -ewv znp_CC2652P_E72_sdk_5_20_00_52_20210901.hex
Invoking bootloader by method 1 (default)
Opening port /dev/ttyUSB0, baud 500000
Reading data from znp_CC2652P_E72_sdk_5_20_00_52_20210901.hex
Your firmware looks like an Intel Hex file
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:22:AB:78:56
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F980
    Write done
Verifying by comparing CRC32 calculations.
    Verified (match: 0x39d15b77)

But something wrong with last step:

root@raspberrypi:/opt/zigbee2mqtt/scripts# source /opt/zigbee2mqtt/bin/activate
(zigbee2mqtt) root@raspberrypi:/opt/zigbee2mqtt/scripts# node zStackEraseAllNvMem.js /dev/ttyUSB0
Detected znp version 'zStack3x0' ({"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210901})
Clearing all NVMEM items, from 0 to 815
NVMEM item #4 - deleting, size: 20
(node:8106) UnhandledPromiseRejectionWarning: Error: SRSP - SYS - nvDelete after 0,9ms
    at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:37:35)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
(node:8106) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8106) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

What can I do?

Hi,
i realized this board: https://github.com/egony/cc2652p_E72-2G4M20S1E/wiki/Home-EN#board-for-soldering-sma-directly-to-the-module
I made 5 pieces of it (bought modules on Aliexpress): it works really well, fast and responsive (tested both with your firmware and with koenkk firmware). The problem is that i was expecting more coverage from this chip (i used classic 11 cm antennas). Sensitivity is not very good, i made many test with some xiaomi zigbee sensor and Sonoff devices at long distance or with obstacles: I have to say that result is similar (or even worse) than a cheap cc2531 in the same exact conditions. In some case can't reach a far device that is seen by the 2531.
I must exclude assembly issues because i'm an electronic technician and i design and/or assemble hundreds of boards both for work and in my free time.
Did you ever compared directly real coverage with other adapters?

I made the following experience with the E72: https://github.com/Koenkk/zigbee2mqtt/issues/5356

Can somebody share my perception?
Or is a individual problem of my set-up?

Best regards, O.

I flashed this router firmwarerouter firmware. .
It works well, but the tx power is only 5dbm.
Could you please make 20dbm firmware for E72?
Thank you!

Hello,

I use SLAESH CC2652R stick (info here https://slae.sh/projects/cc2652/)
I flashed it with your firmware CC2652P_E72_20200921.zip
After this, I cant get into bootloader anymore.
Normally, i press the bootloader button, and then reset then release boot loader button.
But SmartRF Flash program will not connect.

Error message:

Initiate access to target: COM3 using 2-pin cJTAG.
No response from device. Device may not be in bootloader mode. Reset device and try again.
If problem persists, check connection and baud rate.
Connecting over serial bootloader failed: No response from device. Device may not be in bootloader mode. Reset device and try again.
If problem persists, check connection and baud rate.
Failed to create device object.

The led is RED which indicates it is on (?).

Any advice?

I use 1,7v stick. Firmware znp_CC2652P_E72_sdk_4_40_00_44_20210319.
Z2M cannot see them when pairing.
Reloading the firmware and restarting Z2M does not help.
How can I fix the pairing problem?

The patch described here:
https://github.com/egony/cc2652p_E72-2G4M20S1E/blob/master/firmware/coordinator/README.md

Leds can be turned OFF by zigbee2mqtt config, but on March 2021 you need to modify file zStackAdapter.js:

supportsLED() {
    return __awaiter(this, void 0, void 0, function* () {
      return true; //this.version.product !== tstype_1.ZnpVersion.zStack3x0; // <---- change like this
    });

Doesn't seem to be necessary anymore with the latest version of zigbee-herdsman:

        const zStack3x0 = this.version.product === ZnpVersion.zStack3x0;
        this.supportsLED_ = !zStack3x0 || (zStack3x0 && parseInt(this.version.revision) >= 20210430);

https://github.com/Koenkk/zigbee-herdsman/blob/master/src/adapter/z-stack/adapter/zStackAdapter.ts#L116

The README.md can probably be updated.

Start again encountered errors, occasionally can also enter, not too affect the work, afraid of affecting the stability, God help me see it, thank you

Zigbee2MQTT:error 2021-05-25 19:49:24: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-05-25 19:49:24: Failed to start zigbee
Zigbee2MQTT:error 2021-05-25 19:49:24: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions
Zigbee2MQTT:error 2021-05-25 19:49:24: Exiting...
Zigbee2MQTT:error 2021-05-25 19:49:24: Error: Error while opening serialport 'Error: Error: I/O error, cannot open /dev/ttyUSB0'
at Znp. (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
at Generator.next ()
at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
at new Promise ()
at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
at SerialPort. (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-05-25T11_49_24_133Z-debug.log
[19:49:24] INFO: Handing over control to Zigbee2mqtt Core ...

[email protected] start /app
node index.js
(node:365) UnhandledPromiseRejectionWarning: AssertionError [ERR_ASSERTION]: Endpoint name 'right' is given but device is unsupported
at Zigbee.resolveEntity (/app/lib/zigbee.js:240:25)
at Groups.onStateChange (/app/lib/extension/groups.js:102:48)
at EventBus.emit (events.js:315:20)
at EventBus.emit (/app/lib/eventBus.js:23:15)
at State.set (/app/lib/state.js:90:23)
at Controller.publishEntityState

Hi,
it seems possible to change Tx Power on coordinator via zigbee2mqtt config file, but what about router?

is there a way to read/get current Tx power from mqtt request?

Is there somebody who can/would compile an newer firmware version ? This because of the battery drain issue (Ikea remotes)

Please consider switching the design to a other USB-to-Serial converter chip with its own writable EEPROM as a hardware feature.

This would allow you to add your own custom "Product Description String" as a unique identifier for it via the USB interface, and the reason for wanting a unique identifier via the USB interface is in order to enable the possibility for it to support automatic USB discovery of Zigbee USB adapters.

The whole point of this is to make it possible for developers to make the initial installation of Zigbee solution plug-and-play friendly and easier for different home automation software to automatically USB discover and initiate a setup without end-user interactions.

Support for USB discovery was recently added to Home Assistant OS (formerly HASSIO) and the ZHA integration for it, see here:

https://community.home-assistant.io/t/unique-friendly-name-description-for-automatic-zigbee-usb-adapter-discovery-in-home-assistant-zha-using-dongle-vendor-product-ids/337077

That unique customized USB description string could be something like ex.; "Egony Ebyte CC2652P Zigbee Stick v5 hardware revision 5.0.0" and/or "Egony Ebyte E72-2G4M20S1E CC2652P Zigbee Stick v5 hardware revision 5.0.0"

The unique "description" string for each USB adapter can then be added to HA via a PR like this -> home-assistant/core#56201

As I understand it, cheaper CH340 series (example CH340C and CH340E) by WCH which unfortunately does not support this feature.

UPDATE! It has now been confirmed that the CH340B variant does have an EEPROM that support "Product Description String", etc.

http://www.wch-ic.com/products/CH340.html

I understand that more expensive chips like FT231 chips by FTDI and CP210x chips by Silicon Labs / Silabs do support this feature:

https://ftdichip.com/products/ft231xs/
https://ftdichip.com/products/ft231xq/

FT231X/FT231XS: "Key Hardware Features" "Fully integrated 2048 byte EEPROM for storing device descriptors and CBUS I/O configuration."

https://www.silabs.com/interface/usb-bridges/classic/device.cp2102
https://www.silabs.com/interface/usb-bridges/classic/device.cp2104
https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
https://www.silabs.com/documents/public/data-sheets/cp2102n-datasheet.pdf
https://www.silabs.com/documents/public/application-notes/an197.pdf
https://www.silabs.com/documents/public/application-notes/an978-cp210x-usb-to-uart-api-specification.pdf
https://www.silabs.com/documents/public/application-notes/AN571.pdf

"The CP2102N devices have the following features" "Internal 960-byte programmable ROM for vendor ID, product ID, serial number, power descriptor, release number, and product description strings"

"The CP2102N includes an internal electrically erasable programmable read-only memory (EEPROM). This memory may be used to customize the USB Vendor ID (VID), Product ID (PID), Product Description String, Power Descriptor, Device Release Number and Device Serial Number as desired for OEM applications. If the EEPROM is not programmed with OEM data, the default configuration data shown in the table below is used."

"Product String The Product String is an optional string that describes the product. It is limited to 126 characters."

PS: I understand that a bonus feature in of chips like FT231 and CP210x is to add the ability to allow users to auto-reset and put the device in bootloader mode via the DTR/RTS pins exposed will enable much easier firmware upgrades for the end-users as they will no longer need to press any buttons to enter bootloader mode, and then bootloader mode could be activated via software from the firmware flasher program software which could make the OTW (Over-The-Wire) firmware upgrade procedure more user-friendly.

Пытаюсь из стика сделать роутер, шью прошивкой из гита, вроде никаких проблем, но при попытке добавить устройство в Z2M или ZHA оно инициализируется как координатор и определяется версия билда координатора, а не роутера. Пробовал на двух стиках - везде одинаковое поведение.
cc2538-bsl_x64.exe -p COM3 -e -w -v router_CC2652P_E72_sdk_5_10_00_48_20210812.hex Invoking bootloader by method 1 (default) Opening port COM3, baud 500000 Reading data from router_CC2652P_E72_sdk_5_10_00_48_20210812.hex Your firmware looks like an Intel Hex file Connecting to target... CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8 Primary IEEE Address: 00:12:4B:00:25:79:0F:05 Performing mass erase Erasing all main bank flash sectors Erase done Writing 360448 bytes starting at address 0x00000000 Write 104 bytes at 0x00057F988 Write done Verifying by comparing CRC32 calculations. Verified (match: 0xedd82cbe)

Zigbee2MQTT:warn 2021-12-21 12:22:59: permit_join set to true in configuration.yaml.
Zigbee2MQTT:warn 2021-12-21 12:22:59: Allowing new devices to join.
Zigbee2MQTT:warn 2021-12-21 12:22:59: Set permit_join to false once you joined all devices.
Zigbee2MQTT:info 2021-12-21 12:22:59: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2021-12-21 12:22:59: Failed to set permit join to true

В папке cc2652p_E72-2G4M20S1E/firmware/coordinator/ находится прошивка znp_CC1352P_E72_20220301.zip с подозрительным названием CC1352P нет ли здесь ошибки?

Ею точно можно перепрошивать CC2652 стик?

Hello,

Can you please publish firmware.patch for the E72-2G4M20S1E(cc2652p1f) module?
What kind of radio frequency switch, connected to DIO5/DIO6 EByte use?
Also they mentioned, that "the chip used in the module is in DC/DC mode", this is not clear at all, as I can see only program change between DC/DC and LDO.

I'm trying python cc2538-bsl.py -a 10.0.0.224:6638 -ewv CC1352P2_CC2652P_other_router_20220125.hex but it's not working. Should it? Usb doesn't seem to be the solution because it is on the esp32 board and doesn't show up on /dev/tty*

[email protected] start /app

node index.js

Zigbee2MQTT:info 2021-02-01 01:12:42: Logging to console and directory: '/app/data/log/2021-02-01.01-12-39' filename: log.txt

Zigbee2MQTT:info 2021-02-01 01:12:42: Starting Zigbee2MQTT version 1.17.0 (commit #07cdc9d)

Zigbee2MQTT:info 2021-02-01 01:12:42: Starting zigbee-herdsman (0.13.46)

Zigbee2MQTT:error 2021-02-01 01:13:02: Error while starting zigbee-herdsman

Zigbee2MQTT:error 2021-02-01 01:13:02: Failed to start zigbee

Zigbee2MQTT:error 2021-02-01 01:13:02: Exiting...

Zigbee2MQTT:error 2021-02-01 01:13:02: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)

at Generator.throw (<anonymous>)

at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)

npm ERR! code ELIFECYCLE

npm ERR! errno 1

npm ERR! [email protected] start: node index.js

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the [email protected] start script.

npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

npm ERR! /root/.npm/_logs/2021-01-31T17_13_02_811Z-debug.log

Firstly thanks for posting the details of the design! Currently I am trying to build myself a version with RS232 port and external antenna based on your "RPi shield" design. However seems like I am not able to find any detail about the testing pad connected to the antenna output under the module. As I am going to make a larger board I am not able to use the "SMA connect directly rides on the PCB antenna trace with solder mask scratched" method. On your design I can see that you made a though hole exactly to that pad and fill it with solder when assembling, in order to break it out to external antenna, and cut the PCB antenna. I have contacted EByte official but they only have the drawing of GPIO pins around the module, but not that test pad. Could you please share the footprint you used for that?

Докер Synology, как писать файлы конфигурации, про USB-порт, большое спасибо!

Плата: "Плата в форм-факторе стика v3"
Модуль: E72 2G4M20S1E
SMA разъем: Используется

Салют!
Столкнулся с проблемой
Спустя 12-24 часа работы стика все устройства в сети Z2m перестают работать
Перезагрузка плагина не помогает, ругается на то что стик недоступен
Последняя ошибка в логах:

Zigbee2MQTT:info  2021-01-31 21:10:18: MQTT publish: topic 'zigbee2mqtt/[Hallway] Wall switch', payload '{"linkquality":81,"state":"ON","state_left":"ON","state_right":"ON","temperature":29}'
Zigbee2MQTT:error 2021-01-31 21:27:51: Publish 'set' 'state' to '[Hallway] Wall switch' failed: 'Error: Command 0x00158d0003464047/3 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":7472,"destendpoint":3,"srcendpoint":1,"clusterid":6,"transid":106,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,135,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))'
Zigbee2MQTT:info  2021-01-31 21:27:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '[Hallway] Wall switch' failed: 'Error: Command 0x00158d0003464047/3 genOnOff.off({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (SREQ '--> AF - dataRequest - {\"dstaddr\":7472,\"destendpoint\":3,\"srcendpoint\":1,\"clusterid\":6,\"transid\":106,\"options\":0,\"radius\":30,\"len\":3,\"data\":{\"type\":\"Buffer\",\"data\":[1,135,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))'","meta":{"friendly_name":"[Hallway] Wall switch"},"type":"zigbee_publish_error"}'

В настройках Z2m не указывал

advanced:
  baudrate: 115200
  rtscts: false

Помогите пожалуйста решить проблему, очень уж хочу с Conbee 2 переехать :)