[APP][Pro] Schneider Electric - Life is ON (modbus)

Apps
,
1

I’ve created an app for the Schneider Electric products.

It supports the following devices:

  • Acti9 smartlink SI D [gateway] with the following RF-meters:
    • PowerTag Acti9 M63 1P (A9MEM1520)
    • PowerTag Acti9 M63 1P+N Top (A9MEM1521)
    • PowerTag Acti9 M63 1P+N Bottom (A9MEM1522)
    • PowerTag Acti9 M63 3P (A9MEM1540)
    • PowerTag Acti9 M63 3P+N Top (A9MEM1541)
    • PowerTag Acti9 M63 3P+N Bottom (A9MEM1542)
    • PowerTag Acti9 F63 1P+N(A9MEM1560)
    • PowerTag Acti9 P63 1P+N Top (A9MEM1561)
    • PowerTag Acti9 P63 1P+N Bottom (A9MEM1562)
    • PowerTag Acti9 P63 1P+N Bottom (A9MEM1563)
    • PowerTag Acti9 F63 3P+N (A9MEM1570)
    • PowerTag Acti9 P63 3P+N Top (A9MEM1571)
    • PowerTag Acti9 P63 3P+N Bottom (A9MEM1572)
1 Like
2

Hi @Tjar, how to find the app? And how did you manage to enable modbus? I cannot seem to activate modbus for my setup. Maybe you know :smiley:

3

As far as I now it’s enabled by default, as it’s a modbus gateway. The product is accessible at port 502 (by default).

The app is waiting for validation by Homey. as soon as it’s validated it will be available at the store as experimental.

Best regards,

4
5

Did you do anything to enable port 502? I think I get a timeout. Tried a few days now.

image
image1284×698 57.7 KB

Is this error related maybe?

6

No I did not,

What kind of ventilation product are you using?

Best regards,

7

Dear Kim

I’ll check my code tomorrow just to be sure. If your device is created it should be a warning.

Best regards,

8

Hi have the following in my setup:
Wiser Energy IP modul + Wiser Energy Powertag 3P + Wiser Energy Powertag 1P

Wiser Energy IP modul is connected with LAN.

I am not able to ping my device with the following command (Powershell): Test-NetConnection 192.168.1.x -port 502
I am expecting Modbus not being able/available on my device - very sad.

9

Hi Kim,

It looks like you have a IP gateway that connects your system to the Schneider Weiser energy management platform. It doesn’t seem to support modbus.
The smart link SI D does support modbus TCP (A9XMWD20 or A9XMWD100)

Best regards,

10

Okay, thank you for your input. I was looking forward to using your app, I’ve tried and googled how to get data from my setup over the last couple of years - without luck. Now I’m a owner of Homey I would very much like these smart data to be collected in Homey.

I will return if I get updated products.

11

Hi @Kim_Kokholm ,

If you switch to the smartlink SI D you should check the compatibility:

image
image775×888 108 KB

I’ve implemented all acti9 powertags, the NSX types not (yet).

12

Hello nice app.
I dont have a powertag at the moment but it looks like a nice product. But do i still need the schnieder gateway to connect the powertag to homey?

13

yes,

you need it as its a protocol converter to their 868 wireless protocol.

14

Would this app work with the new controller? PAS400 or PAS600? They seem to support modbus. Considering purchasing the Schneider powertag system just because of this app, but I see the controllers you referenced above is deprecated now…

15

I’d really like to know too about PAS400 compatibility, since A9XMWD20 seems to be discontinued. Also PAS400 seems to support wireless connectivity, afaik.

16

I purchased 4 of the Schneider Acti 9 Smartlink SI D, and tried to connect to the app. I get the same error as @Kim_Kokholm. But I do have the right gateway, so this seems to maybe be an app issue @Tjar ?

nc -vz 10.0.20.199 502

Connection to 10.0.20.199 port 502 [tcp/asa-appl-proto] succeeded!

17

The same happened to me. Looking at the code the app while pairing is looking for PowerTags already paired on the gateway with IDs between 150-169 (I guess). Simply scanning modbus slaves, it should work with a PASx00 gateway. I tried using a PAS600 with powertags paired and set to those IDs but no success. The app appears to be broken. I now use the PAS600 (PAS400 should work also) and the Homey app for Modbus TCP/IP. I use advanced flows to read the data and transfer it to Virtual Devices (Virtual Device App) with Voltage, Current, Power, Energy capabilities enabled. It works and should work with Acti9 Smartlink, just get the PowerTags id right. (I added a scale card but found it’s not needed, you can connect the output from the modbus card directly to the Virtual device.)

image
image1547×567 153 KB

image
image840×360 38.7 KB

18

It was a bug in the code. I would love to submit a PR; but seems like @Tjar is not responding anyone anymore. And I cant submit his code to Athom either, so we are kind of in a dilema. I do have the fix on here however, and it works for me: GitHub - thaulow/schneider.modbus: Schneider Electric device driver for Homey

19

hi guys,

If I can transfer the ownership to someone I would be glad to do so. I just have no time to maintain.

just PM me.

1 Like
20

If you are able to submit a beta version I’m glad to test it with the new PAS gateways. I think that if we simply pair the PowerTags with a virtual ID of 150 onwards it will work, or do you see anything else that the app looks for when connecting to the gateway?