Legrand Teleruptor

[yves19]

Device

• Product name: Legrand Drivia Connected Teleruptor 4 121 70
• Manufacturer: Legrand
• Model identifier: Teleruptor
• Device type:
  • Light
  • Lock
  • Remote
  • Sensor
  • Siren
  • Thermostat
  • Other: Switch

Screenshots

Clusters

Basic Cluster Attributes

Legrand Specific Cluster

Electrical Measurement Cluster

On-Off Cluster attributes

[Smanar]

Yeah new legrand stuff, and again new feature ^^, I realy like netatmo. https://www.legrand.fr/pro/catalogue/44171-telerupteur-connecte-pour-tableau-electrique/telerupteur-modulaire-pour-installation-connectee-drivia-with-netatmo-silencieux-1p-16ax-230v-1-module

I can make it tommorow, will be easy, just some questions

• I m seeing 0 at tension/current/power, but I think only the power is working ?
• Do you think the "button state entry" will be usefull ? For me not, I think knowing if the device is on or off is enought ?
• Can you compile the code on your side to test it ?
• Have you tried the device with the app, to test if it haven't special hidden feature ?

[yves19]

I m seeing 0 at tension/current/power, but I think only the power is working ?
Yes only power is measured. No Current, no Voltage are measured.

Do you think the "button state entry" will be usefull ? For me not, I think knowing if the device is on or off is enought ?
The button state entry has no other function than network pairing or resetting. The LED attached to this button can be managed_ through the Specific Cluster Attributes (Option 2 and Option 3).

Can` you compile the code on your side to test it ?
Yes I can (when I Have time for this)

Have you tried the device with the app, to test if it haven't special hidden feature ?
I have tried the device with decONZ GUI on Win 10 as well as on Debian10. No hidden feature seen. I did not try yet the device with Legrand app

[Smanar]

You can add wire a physical switch on the Teleruptor, was for this button I m asking (sorry have a bad english).

So only 2 lines to add ^^ (Legrand stuff is realy nice to add in deconz, all is already in place).
To compile it just change the tep 1 by
git clone --branch Legrand-teleruptor https://github.com/Smanar/deconz-rest-plugin.git

[Smanar]

@yves19 Hello, have you make a try ?

[yves19]

Not yet . Not at home. Probably next week end.
I keep in touch.

[yves19]

@Smanar

Just tested this evening . It rocks :-)
On, Off and power measurement are OK.
Zigbee remote command is OK (tested with 3 smart buttons from Philips)
Local wired Legrand push buttons work also.
Thanks.

[trungkstn]

Anyone test with Contactor (Legrand 412171)

[Smanar]

The teleruptor is 4 121 70
The contactor is 4 121 71

Both are in the code, perhaps on another issue ?

        sensor->modelId() == QLatin1String("Teleruptor") || //Legrand teleruptor
        sensor->modelId() == QLatin1String("Contactor") || //Legrand Contactor

[Michel57189]

Hello,

I have bought the Legrand Contactor 412171. https://www.legrand.fr/pro/catalogue/contacteur-connecte-drivia-with-netatmo-multifonction-silencieux-1p-20ax-230v-1-module
It's not the same as 412170 Legrand Teleruptor.

I've tested it with deCONZ. It doesn't work as in the Legrand application.
This device should work according to HP/HC (in french) (off peak time / peak time in english) depending on the terminal C1/C2. So I have set up the parameter 0x0000 (option 1) with 0x0004 in FC01 cluster. But in this setting, I should have the possibility to force the switch off and the switch on even if it is peak time.
In deCONZ I only have ''on'' and ''off'' commands that are ineffective in this setting. (These commands are only effective when parameter option1 is 0x0003 in FC01 cluster, but in this case the terminal C1/C2 is ineffective)

See the following screenshots

Please, can you do something for me ...

[Smanar]

Hello, yes, I think comment about this device are only on the PR #3053

But the working mode is normal, what is the problem ? You need to change the working mode "on the fly" ? You can't set one and keep it all the time ?

If it's that It's possible to increase the support for this device, this one is an older one, so need to create a DDF from scratch.
If you can share the "auto generated" one, from the editor it will help me, else I just need 5mn to create a new one, but it can be a little different that the one you already have.

If you want we can try to add a command "config/mode" to switch "auto"/"manu" ?

Do you know what is DDF, and what is your OS ?

[Michel57189]

Hello,

Thank you for looking into this problem.

I’m using the Jeedom application with deCONZ plugin based on your REST API (I think). It is working on a RPI4 with Debian11.

Before using Jeedom/deCONZ, I was using the LEGRAND application. If you look at the screenshot below, yon can see 3 commands :

• ‘’Auto’’ : where C1/C2 terminal (HP/HC ) is effective
• ‘’Off’’ : to force the switch off
• ‘’Marche forcée’’ : translated as ‘’forced switch on’’ even if it’s peak time.
  

So, as you suggest, I think you can add a command "config/mode" to switch "auto"/"manu" ?
But, to answer your question I don’t know what is the DDF is and how to find it. Maybe you can tell me where I can find it …

[Smanar]

On jeedom it's easy, except if you are using docker or VM.
Somes explanations here https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet

To make short I will give you a DDF, you just need to put it on one of the 2 possibles folders

• /usr/share/deCONZ/devices/
• /home/<DECONZUSER>/.local/share/ (I think here <DECONZUSER> is jeedom ?

To do this you can use all the tools you want, command line or application
https://community.jeedom.com/t/ddf-deconz/99220/18
https://community.jeedom.com/t/deconz-creation-dun-ddf/90540/9
It's possible too jeedom have a file explorator, but it seem users have right acces when using it.

Just install the DDF and restart the jeedom daemon

For the DDF (can use the name you want, with extension *.json)

{
  "schema": "devcap1.schema.json",
  "ddfvalidate": false,
  "manufacturername": "Legrand",
  "modelid": "Contactor",
  "product": "Contactor",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_PLUGIN_UNIT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "meta": {
        "values": {
          "config/mode": {"auto": 4, "manu" : 3}
        }
      },
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/mode",
          "refresh.interval": 86400,
          "read": {
            "at": "0x0000",
            "cl": "0xFC01",
            "ep": "0x01",
            "fn": "zcl:attr"
          },
          "parse": {
            "at": "0x0000",
            "cl": "0xFC01",
            "ep": "0x01",
            "eval": "if (Attr.val == 4) { Item.val = 'auto'; }  else if (Attr.val == 3) { Item.val = 'manu'; }",
            "fn": "zcl:attr"
          },
          "write": {
            "at": "0x0000",
            "cl": "0xFC01",
            "dt": "0x09",
            "ep": "0x01",
            "eval": "if (Item.val == 'auto') { 4 } else if (Item.val == 'manu') { 3 }",
            "fn": "zcl:attr"
          }
        },
        {
          "name": "state/on"
        },
        {
          "name": "state/reachable"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 1,
          "max": 300
        }
      ]
    }
  ]
}

If you have the GUI (but from my memory jeedom use headless OS) you can right clic on the node, then "edit DDF" to see if it work.
Else you can see direclty on the API using phoscon/help/API Information/Light
Or you can check the "donnée brutes" on jeedom. If it work you need to see the new field "config/mode".

For the moment it's the base, I will explain later how to use it (but you will need "créer des commandes" on jeedom, ca m'etonnerait que ce soit natif.
I have Legrand device too, not the same, but devices that use the same cluster, so if you have problem, I can make test on my side, but for me it's fine.

"Off" will be config=manu with off state
"Marche forcée" will be config=manu with on state
"Auto" will be config=auto
So it mean you will need to make "script" to make 2 commands on the same time.