Successfully Configuring Schneider PowerTags with Modbus and Acti9 Smartlink

General
1

After spending quite some time figuring out how to integrate my Schneider PowerTags with Modbus and the Acti9 Smartlink SI D, I wanted to share my journey and solution with the community. This guide is perfect for anyone looking to monitor their electrical consumption with precision and automation.

My Setup

I have a setup consisting of:

  • 1x Acti9 Smartlink SI D (A9XMWA20)
  • 2x Acti9 PowerTag 1p+N (A9MEM1521)

The Smartlink was a breeze to set up, but the real challenge was configuring the Modbus settings to read all the necessary data points from my PowerTags. Here’s how I did it.

Configuration Steps

  1. Identify the Phase Connections: When setting up the Smartlink, make sure to note the phase connections as this is crucial for accurate readings.
  2. Auto-Addressing: The Smartlink automatically assigns addresses starting from 150. My PowerTags were assigned to 150 and 151.
  3. Modbus Configuration in configuration.yaml: Below is the YAML configuration I used to pull data from both PowerTags. This includes power, power factor, energy consumption, temperature, and voltage/current readings.

yaml
modbus:

  • name: “hub2”
    type: tcp
    host: 192.168.x.x
    port: 502
    sensors:
    • name: “Powertag: Name 1”
      device_class: power
      state_class: measurement
      slave: 151
      address: 3059
      unit_of_measurement: W
      count: 2
      precision: 1
      scan_interval: 2
      data_type: float

    Additional sensor configurations for voltage, current, etc.

Key Learnings

  • Temperature Readings: I noticed that temperature readings weren’t showing up initially. It turned out my PowerTag model doesn’t have a temperature sensor. Always check your device specs!
  • Multiple Modbus Adapters: If you have several devices, organizing them into separate hubs (hub1, hub2) can streamline your setup.

Community Contributions

I hope this guide helps others avoid the trial and error I went through. If anyone has tips or improvements, I’d love to hear them! Let’s keep the community knowledge flowing.

Happy automating! :rocket: