# EmberZNet 8.2.2 now runs on the Lidl Silvercrest Gateway!

[jnilo1]

Despite Silicon Labs dropping Series 1 support in EmberZNet 8.x, we found a workaround using the RCP architecture: the Zigbee stack runs on a Linux host via cpcd + zigbeed, while the gateway's EFR32 chip handles only the radio layer.

Result: EZSP 18 / EmberZNet 8.2.2 on a Series 1 chip.

See the full guide: EMBERZNET-8.x-GUIDE.md

---

🐳 Docker Stack Now Available

For those who don't want to compile cpcd and zigbeed from source, a ready-to-use Docker stack is now available:

Lidl Gateway (RCP)  ◄── TCP:8888 ──►  Docker: cpcd-zigbeed ◄──► Zigbee2MQTT

Features:

• Pre-built multi-arch image (amd64 + arm64) — works on PC and Raspberry Pi
• Includes cpcd 4.5.3 + EmberZNet 8.2.2 (EZSP v18)
• Bundles Zigbee2MQTT + Mosquitto — just configure your gateway IP and go
• Compatible with Zigbee2MQTT 2.7.2+ and Home Assistant

Quick start:

git clone https://github.com/jnilo1/hacking-lidl-silvercrest-gateway
cd hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/26-Docker
# Edit docker-compose.yml → set RCP_HOST to your gateway IP
docker compose up -d

Web UI available at http://localhost:8080 after ~60 seconds.

📦 Image: ghcr.io/jnilo1/cpcd-zigbeed:latest

See the full RCP-UART-HW Docker documentation.

[psolyca]

Thanks,
We just need a Home Assistant plugin to handle this ^^

[jnilo1]

Actually, no specific Home Assistant plugin is needed! For Z2M the standard integration works:

1. rcp-stack runs on any Linux host (PC, Raspberry Pi, etc.)
2. Zigbee2MQTT connects to /tmp/ttyZ2M (the PTY created by rcp-stack)
3. Home Assistant integrates with Zigbee2MQTT via MQTT (as usual)

If you run Home Assistant OS on a Raspberry Pi, you can:

• Run rcp-stack + zigbeed on the same Pi (outside HA containers)
• Or run it on a separate host and point Z2M to the remote gateway

The only difference from a "normal" Zigbee setup is that the Zigbee stack runs on your Linux host instead of on the gateway's chip.

For ZHA users: The same setup should work with ZHA since zigbeed exposes a standard EZSP/ASH interface. Configure ZHA with port /tmp/ttyZ2M and baudrate 115200. I've only tested with Zigbee2MQTT though - if you try ZHA, please report back whether bellows (used by ZHA) handles EZSP 18 correctly!

[psolyca]

I use HA OS has a non standard version, HA OS on a BIOS laptop.
BTW, I will try running this on the host, the only concern is when HA OS update. Does the system is kept ?
I will try.
Thanks

[sipe]

I have multiple issues with installation on Ubuntu 24.04.3 LTS

I installed successfully RCP firmware on Lidl gateway.

Building deps, cpcd and zigbeed is successfull.

First trouble is with rcp-stack. After copying and starting the command systemd services are not created

rcp-stack up Checking RCP endpoint: 192.168.178.94:8888 ... RCP endpoint 192.168.178.94:8888 is reachable Failed to start socat-cpc-rcp.service: Unit socat-cpc-rcp.service not found.

If I try file from path
hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/rcp-stack/bin/rcp-stack
I get different error

./rcp-stack up
Checking RCP endpoint: 192.168.178.94:8888 ...
RCP endpoint 192.168.178.94:8888 is reachable
Job for zigbeed.service failed because the control process exited with error code.
See "systemctl --user status zigbeed.service" and "journalctl --user -xeu zigbeed.service" for details.

systemctl --user status zigbeed.service
 systemctl --user status zigbeed.service
× zigbeed.service - Zigbee daemon (CPC)
     Loaded: loaded (/home/sipe/.config/systemd/user/zigbeed.service; linked; preset: enabled)
     Active: failed (Result: exit-code) since Sat 2026-01-24 23:47:37 UTC; 44s ago
    Process: 2177852 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-ensure-dirs (code=exited, status=0/SUCCESS)
    Process: 2177857 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-check-zigbeed-conf (code=exited, status=0/SUCCESS)
    Process: 2177859 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-wait-cpcd (code=exited, status=0/SUCCESS)
    Process: 2177863 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-wait-pty /tmp/ttyZigbeed (code=exited, status=0/SUCCESS)
    Process: 2177865 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-check-command ZIGBEED_COMMAND (code=exited, status=203/EXEC)
        CPU: 30ms

Jan 24 23:47:37 m710 systemd[2093469]: zigbeed.service: Scheduled restart job, restart counter is at 5.
Jan 24 23:47:37 m710 systemd[2093469]: zigbeed.service: Start request repeated too quickly.
Jan 24 23:47:37 m710 systemd[2093469]: zigbeed.service: Failed with result 'exit-code'.
Jan 24 23:47:37 m710 systemd[2093469]: Failed to start zigbeed.service - Zigbee daemon (CPC).

Also some files in path /home/sipe/.config/rcp-stack/bin were copied manually, not automatically by script.

Also others errors that I found and fixed manually

First rcp-stackp up

`/usr/local/bin/rcp-stack: line 53: CPC_INSTANCE_NAME: unbound variable`
'error: missing unit directory: /usr/local/systemd/user'
'/usr/local/bin/rcp-stack: line 127: /home/sipe/.config/rcp-stack/bin/rcp-check-cpcd-conf: No such file or directory'
'/usr/local/bin/rcp-stack: line 128: /home/sipe/.config/rcp-stack/bin/rcp-check-zigbeed-conf: No such file or directory'

And after that socat service error.

Maybe I missed some steps during the installation phase, appreciate your help and guide.

Thank you.

[jnilo1]

Thanks for the detailed report! The issue is that rcp-stack needs its companion files (scripts/, systemd/, examples/) - copying just the script to /usr/local/bin/ breaks it.

Quick fix: Run the script directly from the cloned repo instead:

A/ Clone the repo (if not already done)

git clone https://github.com/jnilo1/hacking-lidl-silvercrest-gateway.git                                                                                                            
cd hacking-lidl-silvercrest-gateway   

B/ Run rcp-stack from its directory

./2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/rcp-stack/bin/rcp-stack up

Or add an alias to your ~/.bashrc:
alias rcp-stack='/path/to/hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/rcp-stack/bin/rcp-stack'

The first rcp-stack up will:

1. Create ~/.config/rcp-stack/rcp-stack.env (edit this with your gateway IP)
2. Copy helper scripts to ~/.config/rcp-stack/bin/
3. Link systemd units to ~/.config/systemd/user/

Let me know if that fixes your problem. I have updated the guide to clarify this. Thanks for pointing it out!

[sipe]

Looks like there is rcp-check-command missing

systemd/user/zigbeed.service
ExecStartPre=%h/.config/rcp-stack/bin/rcp-check-command ZIGBEED_COMMAND

rcp-stack up is failing
./2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/rcp-stack/bin/rcp-stack up Checking RCP endpoint: 192.168.178.94:8888 ... RCP endpoint 192.168.178.94:8888 is reachable Job for zigbeed.service failed because the control process exited with error code. See "systemctl --user status zigbeed.service" and "journalctl --user -xeu zigbeed.service" for details.

 systemctl --user status zigbeed.service
× zigbeed.service - Zigbee daemon (CPC)
     Loaded: loaded (/home/sipe/.config/systemd/user/zigbeed.service; linked; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2026-01-25 21:26:47 UTC; 56s ago
    Process: 3553194 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-ensure-dirs (code=exited, status=0/SUCCESS)
    Process: 3553199 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-check-zigbeed-conf (code=exited, status=0/SUCCESS)
    Process: 3553201 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-wait-cpcd (code=exited, status=0/SUCCESS)
    Process: 3553205 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-wait-pty /tmp/ttyZigbeed (code=exited, status=0/SUCCESS)
    Process: 3553207 ExecStartPre=/home/sipe/.config/rcp-stack/bin/rcp-check-command ZIGBEED_COMMAND (code=exited, status=203/EXEC)
        CPU: 69ms

Jan 25 21:26:47 m710 systemd[3087820]: zigbeed.service: Scheduled restart job, restart counter is at 5.
Jan 25 21:26:47 m710 systemd[3087820]: zigbeed.service: Start request repeated too quickly.
Jan 25 21:26:47 m710 systemd[3087820]: zigbeed.service: Failed with result 'exit-code'.
Jan 25 21:26:47 m710 systemd[3087820]: Failed to start zigbeed.service - Zigbee daemon (CPC).`

journalctl --user -xeu zigbeed.service
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Jan 25 21:26:45 m710 systemd[3087820]: Failed to start zigbeed.service - Zigbee daemon (CPC).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 916 and the job result is failed.
Jan 25 21:26:47 m710 systemd[3087820]: zigbeed.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit UNIT has been scheduled, as the result for
░░ the configured Restart= setting for the unit.`

cpcd seems to start fine

journalctl --user -u cpcd-bringup.service -f
Jan 25 21:25:41 m710 rcp-run-command[3552135]: [2026-01-25T21:25:40.344813Z] Info : ENCRYPTION IS DISABLED
Jan 25 21:25:41 m710 rcp-run-command[3552135]: [2026-01-25T21:25:40.355964Z] Info : Starting daemon in normal mode
Jan 25 21:25:41 m710 rcp-run-command[3552135]: [2026-01-25T21:25:40.366467Z] Info : Connecting to Secondary...
Jan 25 21:25:42 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.252968Z] Info : RX capability is 256 bytes
Jan 25 21:25:42 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.252983Z] Info : Connected to Secondary
Jan 25 21:25:43 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.359630Z] Info : Secondary Protocol v5
Jan 25 21:25:43 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.373651Z] Info : Secondary CPC v4.4.7
Jan 25 21:25:43 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.386403Z] Info : Secondary bus bitrate is 115200
Jan 25 21:25:43 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.402663Z] Info : Secondary APP vUNDEFINED
Jan 25 21:25:43 m710 rcp-run-command[3552135]: [2026-01-25T21:25:42.402860Z] Info : Daemon startup was successful. Waiting for client connections

I think issue is within zigbeed.service
ExecStartPre=%h/.config/rcp-stack/bin/rcp-check-command ZIGBEED_COMMAND

I don't see rcp-check-command in repo.

Thank you for assistance to resolve this.

[jnilo1]

Good catch! The rcp-check-command script was indeed missing from the repository.

I just fixed it. To resolve the issue:

cd ~/hacking-lidl-silvercrest-gateway
git pull
./2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/rcp-stack/bin/rcp-stack up

The script will be automatically copied to ~/.config/rcp-stack/bin/ during up.

Thanks for reporting this bug!

[geduxas]

is ti possible whole stack run inside system? isn't RTL8196E powerful enough to handle this task alone?

[jnilo1]

Maybe. I have not tried. But RTL8196E ressources are limited...

[sipe]

rcp-stack up now started successfully but zigbeed service fails due to configuration missing

journalctl --user -u zigbeed.service -f
Jan 28 00:25:48 m710 zigbeed[2030191]: [C] Platform------: CPC init failed Error: -2. Ensure radio-url argument has the form 'spinel+cpc://cpcd_0?iid=<1..3>'
Jan 28 00:25:48 m710 rcp-run-command[2030191]: close cpc endpoint: No such file or directory
Jan 28 00:25:48 m710 rcp-run-command[2030191]: By using this software, you are agreeing to the Silicon Labs MSLA found at https://www.silabs.com/about-us/legal/master-software-license-agreement.
Jan 28 00:25:48 m710 zigbeed[2030191]: [C] Platform------: Init() at cpc_interface.cpp:99: Failure
Jan 28 00:25:48 m710 systemd[1196686]: zigbeed.service: Main process exited, code=exited, status=1/FAILURE
Jan 28 00:25:48 m710 systemd[1196686]: zigbeed.service: Failed with result 'exit-code'.
Jan 28 00:25:50 m710 systemd[1196686]: zigbeed.service: Scheduled restart job, restart counter is at 4.
Jan 28 00:25:50 m710 systemd[1196686]: zigbeed.service: Start request repeated too quickly.
Jan 28 00:25:50 m710 systemd[1196686]: zigbeed.service: Failed with result 'exit-code'.
Jan 28 00:25:50 m710 systemd[1196686]: Failed to start zigbeed.service - Zigbee daemon (CPC).

journalctl --user -u zigbeed.service -n 50 --no-pager
Jan 28 00:25:35 m710 zigbeed[2029587]: [C] Platform------: CPC init failed Error: -2. Ensure radio-url argument has the form 'spinel+cpc://cpcd_0?iid=<1..3>'
Jan 28 00:25:35 m710 rcp-run-command[2029587]: close cpc endpoint: No such file or directory
Jan 28 00:25:35 m710 rcp-run-command[2029587]: By using this software, you are agreeing to the Silicon Labs MSLA found at https://www.silabs.com/about-us/legal/master-software-license-agreement.
Jan 28 00:25:35 m710 zigbeed[2029587]: [C] Platform------: Init() at cpc_interface.cpp:99: Failure
Jan 28 00:25:35 m710 systemd[1196686]: zigbeed.service: Main process exited, code=exited, status=1/FAILURE
Jan 28 00:25:35 m710 systemd[1196686]: zigbeed.service: Failed with result 'exit-code'.
Jan 28 00:25:37 m710 systemd[1196686]: Stopped zigbeed.service - Zigbee daemon (CPC).
Jan 28 00:25:37 m710 systemd[1196686]: Starting zigbeed.service - Zigbee daemon (CPC)...
Jan 28 00:25:37 m710 systemd[1196686]: Started zigbeed.service - Zigbee daemon (CPC).
Jan 28 00:25:37 m710 rcp-run-command[2029659]: Cannot open file /usr/local/etc/zigbeed.conf
Jan 28 00:25:38 m710 zigbeed[2029659]: [C] Platform------: CPC init failed Error: -2. Ensure radio-url argument has the form 'spinel+cpc://cpcd_0?iid=<1..3>'
Jan 28 00:25:38 m710 zigbeed[2029659]: [C] Platform------: Init() at cpc_interface.cpp:99: Failure

[jnilo1]

The error CPC init failed Error: -2 means zigbeed can't find the CPC sockets. This is usually a mismatch between cpcd and zigbeed configuration.

1. Check that cpcd is running and created the sockets:

systemctl --user status cpcd-bringup.service
ls -la /dev/shm/cpcd/

You should see a directory like /dev/shm/cpcd/cpcd_bringup/ with socket files inside.

2. Check your ~/.config/rcp-stack/cpcd.conf:

The instance_name and socket_folder must match what's in rcp-stack.env:

instance_name: cpcd_bringup
socket_folder: /dev/shm/cpcd/cpcd_bringup

3. Check your ~/.config/rcp-stack/rcp-stack.env:

Make sure these match your cpcd.conf:

CPC_INSTANCE_NAME=cpcd_bringup
CPC_SOCKET_DIR=/dev/shm/cpcd/cpcd_bringup
ZIGBEED_COMMAND='zigbeed -r "spinel+cpc://$CPC_INSTANCE_NAME?iid=1&iid-list=0" -p "$ZIGBEED_PTY"'

4. After fixing, restart:

rcp-stack down
rcp-stack up

Quick diagnostic:

rcp-stack doctor

This will show if there's a mismatch between config files.

[sipe]

Sorry for taking long to respond, lots of other stuff to do :)

Looks like cpcd dependacy fail

cpcd-bringup.service - CPC daemon bringup (user)
     Loaded: loaded (/home/sipe/.config/systemd/user/cpcd-bringup.service; linked; preset: enabled)
     Active: inactive (dead)

Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.751463Z] Info : Secondary APP vUNDEFINED
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.751543Z] Info : Daemon startup was successful. Waiting for client connections
Jan 28 00:36:07 m710 systemd[1196686]: Stopping cpcd-bringup.service - CPC daemon bringup (user)...
Jan 28 00:36:07 m710 rcp-run-command[2037207]: [2026-01-28T00:36:07.335289Z] Info : Server core cleanup
Jan 28 00:36:07 m710 rcp-run-command[2037207]: [2026-01-28T00:36:07.335511Z] Info : Daemon exiting with status EXIT_SUCCESS
Jan 28 00:36:07 m710 rcp-run-command[2037207]: Logger buffer size = 28672, highwater mark = 2581 : 9.00%. Lost logs : 0
Jan 28 00:36:07 m710 systemd[1196686]: Stopped cpcd-bringup.service - CPC daemon bringup (user).
Jan 28 00:36:07 m710 systemd[1196686]: cpcd-bringup.service: Consumed 2.228s CPU time.
Jan 28 00:36:07 m710 systemd[1196686]: Dependency failed for cpcd-bringup.service - CPC daemon bringup (user).
Jan 28 00:36:07 m710 systemd[1196686]: cpcd-bringup.service: Job cpcd-bringup.service/start failed with result 'dependency'.

journalctl --user -u cpcd-bringup.service -n 100 --no-pager
Jan 28 00:34:14 m710 rcp-run-command[2036267]: WARNING in function 'config_parse_config_file' in file /home/sipe/lidl/ember8/hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/cpcd/cpc-daemon/misc/config.c at line #860 : Configuration file error : key "socket_folder" not recognized
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913667Z] Info : [CPCd v4.5.3.0] [Library API v3] [RCP Protocol v5]
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913689Z] Info : Git commit: 0c9fb76e16a4df765132131f26dd292bb9267514 / branch:
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913693Z] Info : Reading cli arguments
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913695Z] Info : cpcd -c /home/sipe/.config/rcp-stack/cpcd.conf
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913716Z] WARNING : In function 'config_parse_config_file' in file /home/sipe/lidl/ember8/hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/cpcd/cpc-daemon/misc/config.c at line #860 : Configuration file error : key "socket_folder" not recognized
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913765Z] Info : Reading configuration
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913767Z] Info :   file_path = /home/sipe/.config/rcp-stack/cpcd.conf
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913768Z] Info :   instance_name = cpcd_bringup
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913769Z] Info :   socket_folder = /dev/shm
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913770Z] Info :   operation_mode = MODE_NORMAL
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913771Z] Info :   use_encryption = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913772Z] Info :   binding_key_file = /home/sipe/.cpcd/binding.key
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913773Z] Info :   stdout_tracing = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913774Z] Info :   file_tracing = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913774Z] Info :   lttng_tracing = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913775Z] Info :   enable_frame_trace = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913777Z] Info :   traces_folder = /run/user/1000/rcp-stack/traces
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913778Z] Info :   bus = UART
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913779Z] Info :   uart_baudrate = 115200
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913780Z] Info :   uart_hardflow = true
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913781Z] Info :   uart_file = /tmp/ttyCpcRcp
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913782Z] Info :   fwu_recovery_pins_enabled = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913783Z] Info :   fwu_connect_to_bootloader = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913783Z] Info :   fwu_enter_bootloader = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913784Z] Info :   restart_cpcd = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913785Z] Info :   application_version_validation = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913787Z] Info :   print_secondary_versions_and_exit = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913788Z] Info :   use_noop_keep_alive = false
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913789Z] Info :   reset_sequence = true
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913790Z] Info :   stats_interval = 0
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913790Z] Info :   rlimit_nofile = 2000
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.913791Z] Info : ENCRYPTION IS DISABLED
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.924959Z] Info : Starting daemon in normal mode
Jan 28 00:34:15 m710 rcp-run-command[2036267]: [2026-01-28T00:34:14.935365Z] Info : Connecting to Secondary...
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:16.955583Z] Info : RX capability is 256 bytes
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:16.955599Z] Info : Connected to Secondary
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:16.961424Z] Info : Secondary Protocol v5
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:16.976428Z] Info : Secondary CPC v4.4.7
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:16.990780Z] Info : Secondary bus bitrate is 115200
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:17.005806Z] Info : Secondary APP vUNDEFINED
Jan 28 00:34:17 m710 rcp-run-command[2036267]: [2026-01-28T00:34:17.005989Z] Info : Daemon startup was successful. Waiting for client connections
Jan 28 00:35:35 m710 systemd[1196686]: Stopping cpcd-bringup.service - CPC daemon bringup (user)...
Jan 28 00:35:35 m710 rcp-run-command[2036267]: [2026-01-28T00:35:35.585266Z] Info : Server core cleanup
Jan 28 00:35:35 m710 rcp-run-command[2036267]: [2026-01-28T00:35:35.585601Z] Info : Daemon exiting with status EXIT_SUCCESS
Jan 28 00:35:35 m710 rcp-run-command[2036267]: Logger buffer size = 28672, highwater mark = 2581 : 9.00%. Lost logs : 0
Jan 28 00:35:35 m710 systemd[1196686]: Stopped cpcd-bringup.service - CPC daemon bringup (user).
Jan 28 00:35:35 m710 systemd[1196686]: cpcd-bringup.service: Consumed 2.284s CPU time.
Jan 28 00:35:35 m710 systemd[1196686]: Starting cpcd-bringup.service - CPC daemon bringup (user)...
Jan 28 00:35:35 m710 systemd[1196686]: Started cpcd-bringup.service - CPC daemon bringup (user).
Jan 28 00:35:35 m710 rcp-run-command[2037207]: WARNING in function 'config_parse_config_file' in file /home/sipe/lidl/ember8/hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/cpcd/cpc-daemon/misc/config.c at line #860 : Configuration file error : key "socket_folder" not recognized
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666354Z] Info : [CPCd v4.5.3.0] [Library API v3] [RCP Protocol v5]
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666378Z] Info : Git commit: 0c9fb76e16a4df765132131f26dd292bb9267514 / branch:
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666384Z] Info : Reading cli arguments
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666385Z] Info : cpcd -c /home/sipe/.config/rcp-stack/cpcd.conf
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666410Z] WARNING : In function 'config_parse_config_file' in file /home/sipe/lidl/ember8/hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/cpcd/cpc-daemon/misc/config.c at line #860 : Configuration file error : key "socket_folder" not recognized
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666453Z] Info : Reading configuration
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666454Z] Info :   file_path = /home/sipe/.config/rcp-stack/cpcd.conf
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666455Z] Info :   instance_name = cpcd_bringup
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666455Z] Info :   socket_folder = /dev/shm
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666456Z] Info :   operation_mode = MODE_NORMAL
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666456Z] Info :   use_encryption = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666457Z] Info :   binding_key_file = /home/sipe/.cpcd/binding.key
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666457Z] Info :   stdout_tracing = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666458Z] Info :   file_tracing = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666458Z] Info :   lttng_tracing = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666459Z] Info :   enable_frame_trace = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666459Z] Info :   traces_folder = /run/user/1000/rcp-stack/traces
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666460Z] Info :   bus = UART
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666460Z] Info :   uart_baudrate = 115200
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666461Z] Info :   uart_hardflow = true
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666461Z] Info :   uart_file = /tmp/ttyCpcRcp
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666462Z] Info :   fwu_recovery_pins_enabled = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666462Z] Info :   fwu_connect_to_bootloader = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666463Z] Info :   fwu_enter_bootloader = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666463Z] Info :   restart_cpcd = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666463Z] Info :   application_version_validation = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666464Z] Info :   print_secondary_versions_and_exit = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666464Z] Info :   use_noop_keep_alive = false
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666465Z] Info :   reset_sequence = true
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666465Z] Info :   stats_interval = 0
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666466Z] Info :   rlimit_nofile = 2000
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.666466Z] Info : ENCRYPTION IS DISABLED
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.677532Z] Info : Starting daemon in normal mode
Jan 28 00:35:36 m710 rcp-run-command[2037207]: [2026-01-28T00:35:35.688022Z] Info : Connecting to Secondary...
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.705530Z] Info : RX capability is 256 bytes
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.705538Z] Info : Connected to Secondary
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.711046Z] Info : Secondary Protocol v5
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.725582Z] Info : Secondary CPC v4.4.7
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.738148Z] Info : Secondary bus bitrate is 115200
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.751463Z] Info : Secondary APP vUNDEFINED
Jan 28 00:35:38 m710 rcp-run-command[2037207]: [2026-01-28T00:35:37.751543Z] Info : Daemon startup was successful. Waiting for client connections
Jan 28 00:36:07 m710 systemd[1196686]: Stopping cpcd-bringup.service - CPC daemon bringup (user)...
Jan 28 00:36:07 m710 rcp-run-command[2037207]: [2026-01-28T00:36:07.335289Z] Info : Server core cleanup
Jan 28 00:36:07 m710 rcp-run-command[2037207]: [2026-01-28T00:36:07.335511Z] Info : Daemon exiting with status EXIT_SUCCESS
Jan 28 00:36:07 m710 rcp-run-command[2037207]: Logger buffer size = 28672, highwater mark = 2581 : 9.00%. Lost logs : 0
Jan 28 00:36:07 m710 systemd[1196686]: Stopped cpcd-bringup.service - CPC daemon bringup (user).
Jan 28 00:36:07 m710 systemd[1196686]: cpcd-bringup.service: Consumed 2.228s CPU time.
Jan 28 00:36:07 m710 systemd[1196686]: Dependency failed for cpcd-bringup.service - CPC daemon bringup (user).
Jan 28 00:36:07 m710 systemd[1196686]: cpcd-bringup.service: Job cpcd-bringup.service/start failed with result 'dependency'.

cpcd.conf

cat ~/.config/rcp-stack/cpcd.conf
instance_name: cpcd_bringup
bus_type: UART
uart_device_file: /tmp/ttyCpcRcp
uart_device_baud: 115200
uart_hardflow: true
disable_encryption: true
binding_key_file: /home/sipe/.cpcd/binding.key
stdout_trace: false
trace_to_file: false
traces_folder: /run/user/1000/rcp-stack/traces
socket_folder: /dev/shm/cpcd/cpcd_bringup

rcp-stack.env

cat ~/.config/rcp-stack/rcp-stack.env
RCP_ENDPOINT=tcp://192.168.178.94:8888
CPCD_COMMAND='cpcd -c "$HOME/.config/rcp-stack/cpcd.conf"'
ZIGBEED_COMMAND='zigbeed -r "spinel+cpc://$CPC_INSTANCE_NAME?iid=1&iid-list=0" -p "$ZIGBEED_PTY" -d 1 -v 0'

Also did rcp-stack env changed? I see entries
CPC_INSTANCE_NAME
CPC_SOCKET_DIR

Maybe I have older format before you updated.

Thanks for troubleshooting, I hope we will make it work.

[stream2me]

Also did rcp-stack env changed? I see entries
CPC_INSTANCE_NAME
CPC_SOCKET_DIR

I had simular issues. Thats why i changed the rcp-stack. See my post bellow.
You have to change the vars to real path.
Or delete the env and change the rcp-stack and rerun rcp-stack up.
This should fix the wrong paths.

ensure_env() {
  mkdir -p "$CONFIG_DIR" "$STATE_DIR"
  if [ ! -s "$ENV_FILE" ]; then
    set_defaults
    cat >"$ENV_FILE" <<EOF

[sipe]

thanks @stream2me, I continued with docker option and made it work, as I already have z2m and mosquito in docker containers this is perfect setup for me.

@jnilo1 thank you for all the help, maybe to separate docker containers as probably people already have setup z2m and mosquito so cpcd+zigbeed container is just drop in. I also exposed port as stream2me, and pointed existing z2m container to exposed port.

Working perfectly. Thank you for all your hard work.

cpcd-zigbeed | [2026-02-15T22:35:08.740403Z] Info : Endpoint socket #12: Client connected. 1 connection(s)
cpcd-zigbeed | 2026-02-15 23:35:11,676 INFO success: cpcd entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
cpcd-zigbeed | 2026-02-15 23:35:11,676 INFO success: socat-zigbeed entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
cpcd-zigbeed | 2026-02-15 23:35:16,682 INFO success: zigbeed entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

zigbee2mqtt | [2026-02-15 23:37:05] info: zh:ember: Adapter version info: {"ezsp":18,"revision":"8.2.2 [GA]","build":436,"major":8,"minor":2,"patch":2,"special":0,"type":170}

[stream2me]

I found a small problem when I first ran “rcp-stack up” from inside the local git clone.
./rcp-stack: line 53: CPC_INSTANCE_NAME: unbound variable
I adjusted the code:

ensure_env() {
  mkdir -p “$CONFIG_DIR” “$STATE_DIR”
  if [ ! -s “$ENV_FILE” ]; then
    cat >“$ENV_FILE” <<‘EOF’

That helped.
I think it's a good idea to also check whether the file is empty.

[jnilo1]

Thanks @stream2me, good catch!

I just pushed the fix — ensure_env() now uses [ ! -s "$ENV_FILE" ] instead of [ ! -f "$ENV_FILE" ], so the template is regenerated if the file exists but is empty.

[stream2me]

The -s was just a side effect. The main attempt was to use “EOF” instead of EOF. Because of the unbound Variables this will build the file.
But this didn't fix the whole script. It now breaks the creation of the links inside the file. My attempt is now to run run set_defaults once if the file not exists. This will fix the problem with the unbound vars and create the correct links inside the config file.

ensure_env() {
  mkdir -p "$CONFIG_DIR" "$STATE_DIR"
  if [ ! -s "$ENV_FILE" ]; then
    set_defaults
    cat >"$ENV_FILE" <<EOF

I also added a function to create the cpcd config:

ensure_cpcd_conf() {
  if [ ! -s "$CPCD_CONF" ]; then
    log "Generating $CPCD_CONF..."
    cat >"$CPCD_CONF" <<EOF
instance_name: ${CPC_INSTANCE_NAME:-cpcd_bringup}
bus_type: UART
uart_device_file: ${CPC_RCP_PTY:-/tmp/ttyCpcRcp}
uart_device_baud: 115200
uart_hardflow: true
disable_encryption: true
binding_key_file: $HOME/.cpcd/binding.key
stdout_trace: false
trace_to_file: false
traces_folder: /run/user/$UID/rcp-stack/traces
socket_folder: /dev/shm/cpcd/${CPC_INSTANCE_NAME:-cpcd_bringup}
EOF
    log "Edit if needed (binding_key_file, etc.)"
  fi
}

cmd_up() {
  ensure_env
  sync_scripts
  link_units
  load_env
  set_defaults
  ensure_cpcd_conf

Maybe later we can open nano or vim directly to edit the new config files.

[jnilo1]

@stream2me @sipe @psolyca @geduxas — and anyone else following this thread — how's it going on your side? Does rcp-stack up work smoothly for you now? Also, have any of you tried the Docker version? I'd love to get some feedback on it!

[stream2me]

I am using the docker version in the meantime until the script works correctly.
I only use the container for CPCD+zigbeed. It works out of the box. I only added option to expose port 9999 so that I can use it for my z2m.

[psolyca]

Hoo I did not tried this version.
I'm still using the NCP 7.5.1.... ^^;
I'm on other project currently

[stream2me]

Another problem found.
After implementing the above correction in rcp-stack, I simply copied the rcp-stack folder to the destination and ran rcp-stack up.
This now generates the configuration files as it should. After adjusting the config, but without a "Z2M_COMMAND", I ran rcp-stack up again. This worked so far and the required symlinks were created in the tmp directory.
I was now able to successfully start zigbee2mqtt.
The next step was to use "Z2M_COMMAND" to automatically start Z2M. Since I already use a systemd service for Z2M, I deactivated it and now call it up in the config as follows:
Z2M_COMMAND='systemctl restart zigbee2mqtt'
I ran rcp-stack down/up. However, Z2M no longer starts after that.
After some time, I found the problem.
It is due to the way the unit files work.
As long as the main process is still running, the unit file also continues to run.
In my case, only Z2M is started and therefore the unit file is terminated afterwards. Since the necessary symlink for Z2M is deleted when it is terminated, Z2M cannot start.
I therefore deleted the line:
ExecStopPost=%h/.config/rcp-stack/bin/rcp-cleanup --symlink /tmp/ttyZ2M
Now it works.
Since the symlink is not provided by this service, I don't think there's any point in deleting it here.

Finally i'm now able to restart the System and Z2M will start up again.

[jnilo1]

Thank you very much @stream2me for your detailed feedback. Always very useful. Could you share your updated script (as an attached file or PR) so that I can include it in the repo ? Thanks

[jnilo1]

Hey @stream2me,

Thanks again for PR #55 — the set_defaults fix, ensure_cpcd_conf, and the ExecStopPost removal were all real bugs that needed fixing. Much appreciated!

I just pushed a follow-up commit (a6becb2) that builds on your work with a few refinements:

Build scripts (build_cpcd.sh / build_zigbeed.sh):

• Added --local / --deb CLI flags so builds work non-interactively (CI, Docker, piped scripts). Without a flag, the script prompts on a TTY or defaults to local install on non-TTY.
• --local installs to /usr/local, --deb generates a .deb with /usr prefix
• Added a fallback for REPO_OWNER when there's no .git directory (tarball builds)
• Restored make output in zigbeed (make -sf → make -f) — the -s was hiding useful build diagnostics
• Replaced the auto-trigger of build_cpcd.sh from build_zigbeed.sh with an explicit error + exit (a build script silently kicking off another full build was a bit too surprising)

Dockerfile / install_deps.sh:

• Removed libmbedtls-dev (encryption is disabled via -DENABLE_ENCRYPTION=OFF)
• Removed gcc / g++ (already provided by build-essential)
• Added cmake to install_deps.sh

Docker image (Dockerfile.multiarch):

• Added -DENABLE_ENCRYPTION=OFF to cpcd cmake build — encryption was already disabled in cpcd.conf.template (disable_encryption: true) but the binary was still compiled with mbedTLS support
• Removed libmbedtls-dev from builder stage and libmbedcrypto.so from runtime stage
• Result: ~0.7 MB smaller image, 2 fewer layers, no unused crypto library

Docs & minor:

• Updated prerequisites in README and guide (cmake build-essential instead of cmake gcc g++ libmbedtls-dev)
• Fixed indentation in rcp-stack ensure_env()

All your fixes (unbound variable, ensure_cpcd_conf, ExecStopPost removal) are preserved — I only touched the areas above.

Would you be able to pull and test on your side? Especially:

git pull
./build_cpcd.sh --local    # or --deb
./build_zigbeed.sh --local # or --deb

Let me know if anything breaks!

[stream2me]

Updated my local fork with your commits.

./build_cpcd.sh --local:

Installing locally...
-- Install configuration: "Release"
-- Install component: "runtime"
-- Installing: /usr/local/bin/cpcd
-- Installing: /usr/local/etc/cpcd.conf

--deb is also working.

Same for zigbeed:

Stripping binary...
Generating DEB-Package...
Creating build helper scripts...
CPack: Create package using DEB
CPack: Install projects
CPack: - Install directory: ../hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/zigbeed-8.2.2/build/tmp
CPack: Create package
-- CPACK_DEBIAN_PACKAGE_DEPENDS not set, the package will have no dependencies.
CPack: - package: ../hacking-lidl-silvercrest-gateway/2-Zigbee-Radio-Silabs-EFR32/25-RCP-UART-HW/zigbeed-8.2.2/packages/zigbeed-1.0.0-x86-64.deb generated.
Done.
use dpkg -i zigbeed.deb to install

So everything seems to be fine.
By the way, great idea with the flags.

I also tried rcp-stack up to see if the editor would open. Works as expected.