-
-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.10.14 Aqara Smartplugs, Rollershade und Tint LEuchten nicht mehr ansprechbar #2358
Comments
This is a known issue (#2351). Current state is that there are 2 options to move forward:
There is an open issue on the zigbee-herdsman level to add an option which retains both network and hardware, but that is slow going. A. |
I bought `SLZB-07P7 Zigbee USB CC2652P7' should this do the Job ("inherit the Network") ? |
Yes, that one should work. |
great, could you give me a link for proper way to change the coordinator without having to pair everything again. Probably just plugging out my CC2538 (Arteck Platine) and plugin'in SLZB-07P7 Zigbee USB CC2652P7 wont do it right ? ;) |
Actually, it almost will:
|
Works ! Top thank You. |
Best Usecase for the remaining old flagship ? Router ? 😄 |
i just found Routerfirmware and flashed it (before i erased the chip) with j-link (TI CC2538SF53TI) and the actual router firmware from above. Segger says successfull flash but the device isnt recognized as router within zigbee. Did i miss sth ? |
describe the problem in Detail. What do you expect to happen ? What does happen ?
Just wanted to leave a note that directly after updating to newest stable version some vendors stopped to work. i directly changed down to last version, with which everything works as intended. The devices were even not deletable, I did not investigate further.
Adapter version
1.10.14
Coordinator firmware version
0000000
Coordinator
type:zStack30x version:2-2.2.7.2. revision:20211222 port:/dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00 channel:11
Setup
pi5
Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections
No response
The text was updated successfully, but these errors were encountered: