iammeter

What This Skill Does

The iammeter skill is a powerful integration for OpenClaw that connects directly to the IAMMETER energy monitoring platform. It allows users to interface with their smart energy meters via the official API, enabling the retrieval of real-time power consumption data, historical energy usage reports, and advanced device diagnostics. By leveraging the iammeter skill, OpenClaw can act as a centralized hub for your energy management, providing actionable insights into electricity usage across one or multiple sites. The skill handles authentication securely using API tokens and provides a command-line interface that can be triggered directly via natural language commands within the OpenClaw environment.

Installation

To install this skill, use the ClawHub command: clawhub install openclaw/skills/skills/guanvee/iammeter-openclaw-skill. Once installed, you must configure your API key. You can add your credentials via the OpenClaw Skills UI, which automatically updates ~/.openclaw/openclaw.json. For local development or debugging, you can manually set the IAMMETER_TOKEN environment variable in your terminal session. Ensure you have Node.js installed on your system, as the skill relies on axios for network requests and yargs for CLI command parsing.

Use Cases

This skill is ideal for home automation enthusiasts, facility managers, and data analysts. You can use it to automate weekly energy audits, generate CSV exports for spreadsheet analysis, or trigger alerts when power consumption exceeds defined thresholds. It is particularly useful for optimizing energy efficiency in solar-equipped homes, as it allows you to compare generation against consumption data retrieved from the meter.

Example Prompts

1. "List all my registered sites and show me the latest power usage for each."
2. "Get the energy history for site ID 12345 from February 1st to February 25th and save it as a CSV file."
3. "Run a power analysis for the main meter and let me know if there are any efficiency patterns I should look at."

Tips & Limitations

• Rate Limits: Be mindful of the API rate limits outlined in references/api.md. Avoid excessive polling in tight loops.
• Security: Never share your IAMMETER_TOKEN. If you are contributing code, ensure your token is stored in environment variables rather than hardcoded in files.
• Data Integrity: Always verify the date formats when querying historical data to ensure the API returns the expected time-series ranges.