feat(zigbee2mqtt): MQTT login by client certificate (REN-953) #1165

Merged

Ghost merged 1 commits from atlas/ren-953-z2m-cert into master

2026-10-07 01:47:36 +00:00

Author	SHA1	Message	Date
atlas-botandClaude Opus 5.5	5be1d0a250	feat(zigbee2mqtt): log in to MQTT by client certificate (REN-953) ci/woodpecker/pr/ci-scripts-test Pipeline was successful Details ci/woodpecker/pr/pr-review Pipeline was successful Details ci/woodpecker/pr/ci-manifests-test Pipeline was successful Details Z2M, discovery-guard and interview-watch use the certificate of the register account zigbee2mqtt-bridge on the mTLS listener :8884 instead of the legacy password. Z2M gets server/ca/cert/key by env because its configuration.yaml on the PVC is never re-seeded. The init container no longer renders mqtt_password. The legacy broker user stays until a later broker roll. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 00:50:39 +00:00

Author

SHA1

Message

Date

atlas-botandClaude Opus 5.5

5be1d0a250

feat(zigbee2mqtt): log in to MQTT by client certificate (REN-953)

ci/woodpecker/pr/ci-scripts-test Pipeline was successful

Details

ci/woodpecker/pr/pr-review Pipeline was successful

Details

ci/woodpecker/pr/ci-manifests-test Pipeline was successful

Details

Z2M, discovery-guard and interview-watch use the certificate of the
register account zigbee2mqtt-bridge on the mTLS listener :8884 instead of
the legacy password. Z2M gets server/ca/cert/key by env because its
configuration.yaml on the PVC is never re-seeded. The init container no
longer renders mqtt_password. The legacy broker user stays until a later
broker roll.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 00:50:39 +00:00