zwave-implement-cc

Guide Z-Wave Command Class implementation in the ZWave.NET library.

3|Updated Dec 11, 2021
One-click install
npx skills add https://github.com/dfederm/ZWave.NET --skill zwave-implement-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zwave-implement-cc
Source: https://github.com/dfederm/ZWave.NET/tree/main/.github/skills/zwave-implement-cc
Command: npx skills add https://github.com/dfederm/ZWave.NET --skill zwave-implement-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide and best practices for developers looking to implement new Z-Wave Command Classes (CCs) within the ZWave.NET library, ensuring adherence to specifications and promoting robust, forward-compatible code.

Core Features & Use Cases

  • Step-by-step Implementation Guide: Covers defining command enums, public report types, CC classes, and inner command structs.
  • Design Principles: Emphasizes specification conformance, forward compatibility, handling solicited vs. unsolicited reports, and state management.
  • Use Case: A developer needs to add support for a new Z-Wave sensor type to the ZWave.NET library. They can use this Skill to understand the exact file structure, coding patterns, and validation requirements for implementing the corresponding Command Class.

Quick Start

Follow the checklist in this skill to implement a new Z-Wave Command Class in the ZWave.NET codebase.

Frequently Asked Questions about zwave-implement-cc

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

FAQPage Schema
How do I implement a new Z-Wave Command Class in ZWave.NET?

Implementing Z-Wave Command Classes requires defining command enums, public report types, CC classes, and inner command structs. You must also handle solicited and unsolicited reports, manage state, and validate payloads.

What is the structure of a Z-Wave Command Class implementation?

A Z-Wave Command Class implementation consists of command enums, public report types, CC classes, and inner command structs. This structure ensures specification conformance and robust forward compatibility for new Z-Wave sensors.

How do you handle solicited and unsolicited reports in Z-Wave Command Classes?

Handling solicited and unsolicited reports in Z-Wave Command Classes involves specific design principles for state management and payload validation. This ensures the CC classes process incoming data correctly per the Z-Wave Application Specifications.

Does ZWave.NET support forward compatibility for new Z-Wave Command Classes?

Yes, ZWave.NET supports forward compatibility by emphasizing strict adherence to Z-Wave Application Specifications during Command Class implementation. This approach ensures new code remains robust against future protocol updates.

What are the design principles for Z-Wave Command Class payload validation?

Design principles for Z-Wave Command Class payload validation focus on specification conformance and state management. Proper validation within CC classes ensures data integrity for both solicited and unsolicited reports.