-
Notifications
You must be signed in to change notification settings - Fork 218
DeviceScheduling
Jereme Haack edited this page Apr 6, 2014
·
1 revision
The ActuatorAgent can take a schedule for specifying which agents are eligible to get a lock during the day. Currently, the schedule is repeated every day. To change the schedule, set a new file and restart the agent.
The schedule is set in the ActuatorAgent's launch config file:
"points":
{
"lbnl/building46/fakecatalyst":
{
"heartbeat_point":"ESMMode",
"schedule":
{
"17:00": ["foo1", "bar1"],
"17:03": ["foo2", "bar2"],
"17:06": ["foo3", "bar3"],
"17:09": ["foo4", "bar4"]
}
},
"campus1/building1/catalyst2":
{
"schedule":
{
"03:00": ["foo1", "bar1"],
"11:00": ["foo2", "bar2"],
"17:00": ["foo3", "bar3"],
"18:00": ["foo4", "bar4"]
}
}
}
- Platform Agent
- VOLTTRON Central Agent
- Platform Commands
- Platform Configuration
- [Platform Hardening Security Recommendations] (Linux-Platform-Hardening-Recommendations-for-VOLTTRON-users)
- ...
- [Building VOLTTRON] (Building-VOLTTRON)
- Example Agents
- Agent Development
- [Shortcut Scripts] (Scripts)
- [VOLTTRON Conventions] (Conventions)
- [sMAP Test Server] (sMAP-Test-Instance)
- [Design Discussions] (Design Discussions)
- VIP
- VIP - VOLTTRON Interconnect Protocol
- RPC by example
- VIP - Known Identities
- VIP - Authentication
- VIP - Authorization
- Protecting Pub/Sub Topics
- Setup Eclipse for VOLTTRON
- Deployment Walkthrough
- Forward Historian Walkthrough
- [Create New Historian Agent] (Developing-Historian-Agents)
- [Create New Driver Agent] (Develop-Driver-Agent)
- [Developing With Eclipse] (Eclipse)
- Migrations
- [2.x to 3.x Migration](2.x-to 3.x-Migration)
- 1.2 to 2.0 Migration
- [Deployment Recommendations](Recommendations for Deployments)
VOLTTRON Versions and Features
Transactional Network Platform Overview
- Established Topics
- Working with the Actuator Agent
- Logging
- [Multi-Node Communication] (MultiBuildingMessaging)
Information Exchange Standards