z2m-device-setting

Publishes Zigbee2MQTT device settings via authenticated MQTT and records them for re-pair recovery.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/DanielH2018/server --skill z2m-device-setting-danielh2018
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: z2m-device-setting
Source: https://github.com/DanielH2018/server/tree/main/.claude/skills/z2m-device-setting
Command: npx skills add https://github.com/DanielH2018/server --skill z2m-device-setting-danielh2018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Zigbee device tuning settings (like Aqara FP300 motion_sensitivity or absence_delay_timer) live only in Zigbee2MQTT runtime state, not in git, so a device re-pair silently wipes them. This Skill applies settings through authenticated MQTT publishes and ensures each change is verified and documented. ## Core Features & Use Cases - Authenticated MQTT publish: Decrypts mqtt_username/mqtt_password from SOPS and publishes JSON settings to zigbee2mqtt/<Friendly Name>/set against the k3s broker at 10.0.0.242:1883. - Verification workflow: Confirms the applied value via mosquitto_sub, checks Z2M logs for rejected options, and optionally validates the Home Assistant-visible effect with ha-verify-state. - Persistence reminder: Prompts recording each setting in the home-assistant role's CLAUDE.md so it survives a re-pair. - Use Case: Tune an Aqara FP300 presence sensor by setting motion_sensitivity to high and absence_delay_timer to 60, verify the new state, then document the change. ## Quick Start Set the Aqara FP300 motion_sensitivity to high in Zigbee2MQTT and verify the new state was applied.

Frequently Asked Questions about z2m-device-setting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change a Zigbee2MQTT device setting via MQTT?▼

Publish a JSON payload to the topic zigbee2mqtt/<Friendly Name>/set using mosquitto_pub with your broker credentials. For example, send {"motion_sensitivity":"high"} to zigbee2mqtt/Aqara FP300/set, then subscribe to the device topic to confirm the new value.

How to set Aqara FP300 motion sensitivity in Zigbee2MQTT?▼

Publish {"motion_sensitivity":"high"} to zigbee2mqtt/Aqara FP300/set on your MQTT broker. Battery-powered Aqara devices may need a wake or poll before the change takes effect, since some settings apply on the next check-in.

Do Zigbee2MQTT device settings survive a re-pair?▼

No, device settings live in Z2M runtime state and on the device itself, so a re-pair resets them. Record every applied setting and value in your documentation so they can be re-applied after re-pairing.

Why is my Zigbee2MQTT setting not applying after publish?▼

Check the Z2M logs with kubectl -n homelab logs deploy/zigbee2mqtt for rejected or unknown options. Battery devices may also need to wake before the setting takes effect, and you can confirm the applied value by subscribing to the device topic.

Can I rename a Zigbee device through MQTT in Zigbee2MQTT?▼

Yes, publish to zigbee2mqtt/bridge/request/device/rename with {"from":"<old>","to":"<new>"}. Unlike runtime settings, renames are persisted by Z2M in its configuration.yaml.