Skip to main content

AppCTRL® Connectors

Every device speaks its own protocol. Connectors bring them all into one app.

In AppCTRL®, every integration is a connector: a protocol adapter that brings one kind of device or system into a site. Chargers, meters, smart breakers, battery storage, building automation and business systems each plug in through their own connector, and all of it shows up in one AppCTRL® view and one RESTful JSON API.

Connecting everything is what lets AppCTRL® run charging, solar, storage and smart breakers as one system. That is the foundation for facilities that keep working when the grid doesn't.

Charging

EV chargers connect to the AppCTRL® central system.

OCPP 1.6J chargers

OCPP 1.6J · chargers connect in to AppCTRL®

Charger status, sessions, load limits and remote start/stop for OCPP 1.6J chargers, with chargers from Atom Power (including the H48), BTC Power, Efacec and Tesla connected today.

OCPP 2.0.1 chargers

OCPP 2.0.1

Support for chargers on the newer OCPP 2.0.1 protocol.

Kempower DC fast chargers

Vendor connector

A dedicated connector for Kempower DC charging systems.

Enphase HCS with COSMOS

Including legacy ClipperCreek HCS units in the field and on the shelf. Enphase HCS chargers with the COSMOS option (and earlier ClipperCreek HCS units) connect to AppCTRL® through its serial interface. A node controller is a small Linux computer in each pedestal that talks to its charger; a core controller in the site panel polls the node controllers over a daisy-chained RS-485 line and connects outbound to AppCTRL®, so no inbound firewall ports are needed. See Enphase commercial EV chargers.

Enphase / ClipperCreek HCS COSMOS (TCP serial)

TCP serial · AppCTRL® v2

Charger status and faults over a direct serial link.

Enphase / ClipperCreek HCS COSMOS (MQTT, via node controller)

MQTT · node controller

A node controller at the pedestal reads the charger locally and publishes outbound MQTT to AppCTRL®.

Enphase / ClipperCreek HCS COSMOS (BACnet MS/TP)

BACnet MS/TP · RS-485 daisy chain

Node controllers on a daisy-chained RS-485 line present each charger as BACnet objects; a core controller in the site panel polls them and connects outbound to AppCTRL®.

Enphase / ClipperCreek HCS COSMOS (Modbus RTU)

Modbus RTU · RS-485 daisy chain

Same pedestal node-controller layout as the BACnet MS/TP connector, using Modbus RTU on the shared RS-485 chain back to a core controller.

Enphase / ClipperCreek HCS COSMOS (BACnet MS/TP to SC)

BACnet MS/TP to BACnet/SC

The core controller routes the pedestal MS/TP network and connects outbound over TLS to a Pine Shore–hosted BACnet/SC hub that AppCTRL® reads.

Enphase IQ EV Charger 2 (OCPP)

OCPP 1.6 / 2.0.1

Connects to AppCTRL®'s OCPP server like other OCPP chargers. Enphase states OCPP 1.6 and 2.0.1 support for charging station management systems.

Enphase IQ EV Charger 2 (Modbus TCP)

Modbus TCP · Ethernet

Local energy-management integration over Ethernet: AppCTRL® reads charger status and metering and can set charging current limits on site.

Metering

Circuit and site energy meters.

Shelly EM meters

Shelly Cloud / MQTT

Energy readings from Shelly energy meters on charger and panel circuits.

Modbus TCP meters

Modbus TCP

A general Modbus TCP meter connector, first for Accuenergy Acuvim meters.

Breakers & power

Smart breakers, storage and power systems at the site.

Eaton AbleEdge smart breakers

Vendor cloud API

Breaker status and readings for Eaton AbleEdge smart breakers, linked to the chargers they feed.

Energy storage (ESS)

Site device records + monitoring hooks

Battery and inverter units are recorded per site today, with hooks for live vendor monitoring links.

Tesla Powerhub

Vendor energy API

Monitoring for sites reporting through Tesla Powerhub.

Atom Power load management

Vendor connector

Demand and load management with Atom Power systems.

Building automation

Bring EV charging and building energy data out of the building automation system.

ClipperCreek CS and HCS chargers

Pine Shore driver · BACnet via AppCTRL® v1

Where Pine Shore started in EV charging: our first charging connector brings ClipperCreek CS and HCS chargers into BACnet building automation. When Enphase acquired ClipperCreek, the same connector carried over to Enphase EV chargers. In service at ASHRAE's headquarters, installed with Automated Logic's Georgia branch. See AppCTRL® v1.

BACnet via AppCTRL® v1

BACnet®

Pine Shore's driver connects EV charging into any BACnet® building automation system, including systems from Automated Logic branches and dealers, who buy EV charging systems through Pine Shore. AppCTRL® v1 connectors run on BTL-listed BACnet® controllers. See AppCTRL® v1.

BACnet to Drupal

BACnet via SOAP · Drupal module

Pine Shore's first connector. Paste a device's SOAP address from a building automation server and the module pulls its live data into Drupal (open source) dashboards. Built on Drupal 7; a working demo is available on request. See our software story.

Business systems

Keep operations and business records in step.

AppCTRL® Connector for PineCTRL™

Frappe app · read-only to start

Links AppCTRL® organizations to PineCTRL™ customers. Roadmap: sites to projects, service tickets, and usage billing as drafts. See PineCTRL™.

Need a connector?

Don't see your equipment? Tell us what's at your site: call 828-553-6257 or email dave@pineshoreenergy.com.

AppCTRL® is a registered trademark and PineCTRL™ a trademark of Pine Shore Energy LLC. BACnet® and ASHRAE® are registered trademarks of ASHRAE (mention does not imply endorsement). Automated Logic, ClipperCreek and Enphase are trademarks of their respective owners. All other product and company names are the property of their respective owners and are used only to describe compatibility; their mention does not imply endorsement.