senderId is an optional 16-bit integer and will be present as the senderId field on the returned message. Emits the circuitStateChanged event when response is acknowledged. See SLSetCircuitStateMessage documentation for argument values. setCircuitState(controllerId, circuitId, circuitState, senderId)Īctivates or deactivates a circuit. senderId isan optional 16-bit integer and will be present as the senderId field on the returned message. Emits the controllerConfig event when the response comes back. Requests controller configuration from the connected unit. Emits the saltCellConfig event when the response comes back. Requests salt cell status/configuration from the connected unit (requires an IntelliChlor or compatible salt cell). Emits the chemicalData event when the response comes back. Requests chemical data from the connected unit (may require an IntelliChem or similar). Emits the poolStatus event when the response comes back. Requests pool status from the connected unit. Emits the version event when the response comes back. Requests the system version string from the connected unit. connect ( ) close()Ĭloses the connection. Pull requests to document undocumented properties are most welcome. The final 4 bytes are a little-endian-encoded length of the data payload on the packet. The second 2 bytes are a little-endian-encoded message ID. The first 2 bytes are a little-endian-encoded sender ID (which is normally specified when making the original request). Packet formatĪll ScreenLogic packets are sent with an 8-byte header. There are lots of available messages supported by ScreenLogic that the app doesn't support yet, but can be added pretty easily as needed. See UnitConnection API reference.Īll communication with a ScreenLogic unit is done via TCP, so responses will come back in the order they were requested. Once you've connected with connect(), there are a number of methods available and corresponding events for when they've completed successfully. Where '1234' is the remote login password. See example.js for an example of interfacing with the library. Tested with a Pentair ScreenLogic system on firmware versions 5.2 Build 736.0 Rel, 5.2 Build 738.0 Rel Local connections require a Pentair ScreenLogic device on the same network (a network which supports UDP broadcasts). This is a Node.JS library for interfacing with Pentair ScreenLogic systems over your local network or remotely through the Pentair dispatcher.

Pentair screenlogic login