Self-improving AI Employees for everyone
Python ai-agentsai-employeeai-employeesassistantautonomous-agentsco-employeescompanygrok-botinstinctloop-agentsmuseown-your-datapersonalself-hosted
Battery Monitor (batteryMonitor)
| Field | Value |
|---|---|
| Category | android / monitoring |
| Backend handler | plugin server/nodes/android/battery_monitor/__init__.py; dispatch via BaseNode.execute() -> shared AndroidServiceBase.invoke (@Operation("invoke")) |
| Tests | server/tests/nodes/test_android.py |
| Skill (if any) | server/skills/android_agent/battery-skill/SKILL.md |
| Direct agent tool | connects straight to any agent's input-tools |
Purpose
Monitor battery status on the connected Android device: level percentage, charging state, temperature, and health.
Backend service mapping
| Field | Value |
|---|---|
| Handler dispatch | uniform - see _pattern.md |
SERVICE_ID_MAP[batteryMonitor] |
battery |
| Default action | status |
All transport, parameter promotion, and output flattening behaviour is
identical to every other Android node. See _pattern.md.
Parameters
Only the shared parameter set; no node-specific additions. See
_pattern.md.
Logic Flow (node-specific slice)
flowchart TD
A[Dispatch to handle_android_service] --> B[service_id = 'battery']
B --> C{action}
C -- status --> D[POST /api/battery {action: status, parameters}]
C -- other --> D
D --> E[AndroidService.execute_service envelope]
E --> F[NodeExecutor flattens data.battery_level,<br/>data.charging, data.temperature, data.health<br/>to top level of output]
Output payload (typical, after flatten)
{
service_id: 'battery',
action: 'status',
battery_level: number, // promoted from data
charging: boolean, // promoted from data
temperature: number, // promoted from data
health: string, // promoted from data
data: { ... }, // original nested block still present
response_time: number,
android_host: string,
android_port: number,
timestamp: string
}
Edge cases & known limits
- Exact
datakeys depend on the device-side handler; the flatten logic blindly promotes whatever the device returns. - Relay mode returns the same shape but via
_execute_via_relay. - See
_pattern.mdfor shared edge cases.
Related
- Skill:
battery-skill/SKILL.md - Shared pattern:
_pattern.md