wasp-deti-power

Deprecation Notice

WASP was deprecated on March 14th 2024, there will be no further dependency or security updates to this platform.

Uses wasp-payload-processor to build a payload processing service for Schneider power meters.

Example payload:

{
  "sentOn": 1620256786756,
  "metrics": {
    "CurrentAvg": 1.5844479,
    "TotalActiveEnergyDelivered": 1146.397,
    "ActivePowerTotal_timestamp": 1620256786755,
    "TotalActiveEnergyDelivered_timestamp": 1620256786724,
    "assetName": "Schneider5111-id2",
    "CurrentAvg_timestamp": 1620256786739,
    "ActivePowerTotal": 1.157379
  }
}

Getting started

wasp-deti-power can be run in a similar way to most nodejs applications. First install required dependencies using npm:

npm install

Testing

For integration testing, wasp-deti-power depends on Kafka and Zookeeper. These can be brought locally up using docker:

docker-compose up -d

You can then run tests with:

npm test

Environment Variables

wasp-deti-power is configured primarily using environment variables as follows:

variable	required	default	description
WASP_SENSOR_TYPE	N	detiPower	Type of this sensor/thing for wasp-thing-service

The following environment variables configure the use of wasp-payload-processor:

variable	required	default	description
PORT	N	3000	Port on which the service will listen
LOG_LEVEL	N	info	Logging level. Valid values are [trace, debug, info, warn, error, fatal]
KAFKA_LOG_LEVEL	N	nothing	Logging level for Kafka. Valid values are [debug, info, warn, error, nothing]
KAFKA_BROKERS	N	localhost:9092	List of addresses for the Kafka brokers
KAFKA_READINGS_TOPIC	N	readings	Outgoing Kafka topic for readings
KAFKA_PAYLOAD_ROUTING_PREFIX	N	payloads	Prefix for incoming Kafka topics for payloads