docs: DC Guardian kit — BOM, wiring diagram, assembly guide, skill config#4
docs: DC Guardian kit — BOM, wiring diagram, assembly guide, skill config#4toxfox69 wants to merge 1 commit intoClawland-AI:mainfrom
Conversation
…l config Closes Clawland-AI#1 - BOM.md: 12-item parts list with purchase links totaling ~$88, cost breakdown by category, substitution table - WIRING.md: full ASCII schematic + detailed pin reference table for LicheeRV-Nano ↔ DHT22 / MQ-2 / water sensors / buzzer - README.md: overview, step-by-step assembly instructions (7 steps), maintenance schedule, ROI calculation, troubleshooting table - skill.yaml: PicClaw skill config — GPIO assignments, sensor drivers, alert thresholds, buzzer patterns, webhook output - alerts.yaml: named alert rules for all sensors with severity levels and cooldown periods Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Free Tier Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| pin: ${gpio.buzzer} | ||
| pattern: | ||
| warn: { on_ms: 100, off_ms: 900, repeat: 5 } | ||
| alert: { on_ms: 500, off_ms: 200, repeat: -1 } # -1 = continuous until cleared |
There was a problem hiding this comment.
Buzzer pattern key doesn't match alert severity name
High Severity
The buzzer pattern map in skill.yaml defines keys warn and alert, but alerts.yaml uses severity values warn and critical. When a critical-severity alert fires with buzzer as an output, the system would look up a pattern for critical and find no match — the key is alert instead. The buzzer likely won't sound for smoke or water leak events.
Additional Locations (1)
1 participant
Closes #1
What's included
kits/dc-guardian/BOM.mdkits/dc-guardian/WIRING.mdkits/dc-guardian/README.mdkits/dc-guardian/skill.yamlalerts.yaml)kits/dc-guardian/alerts.yamlTest plan
skill.yamlparses as valid YAML🤖 Generated with Claude Code
Note
Low Risk
Low risk: this PR only adds new kit documentation and YAML configuration files, with no changes to application/runtime code. Main risk is misconfigured GPIO pins/thresholds or invalid YAML leading to non-functional deployments.
Overview
Adds a new
kits/dc-guardiankit with a complete bill of materials, wiring/assembly documentation, and operational guidance for deploying a data-center monitoring node.Introduces PicClaw configuration via
skill.yaml(GPIO mappings, sensor polling/startup delays, buzzer/webhook/log outputs) andalerts.yaml(temperature/humidity/smoke/water/offline rules with cooldowns) to drive alerting behavior.Written by Cursor Bugbot for commit 3f131bf. This will update automatically on new commits. Configure here.