Adorne API

Theiding

15 August 2019 at 6 h 57 min

Hi,

I have integrated my Legrand Adorne light switches via the Samsung Artik Cloud into OpenHab. Now that Artik has been discontinued I need to swap my OpenHab binding to a new API. Is Legrand offering such an API?

Thanks,

Mark

Leslie – Community Manager

16 August 2019 at 11 h 04 min

Hi Mark,

Solutions based on Artik are on the way to be integrated into a new Cloud. I don’t know for the moment if there will be a new API. I should have more information about it from the US teams next week

I keep you in touch

Have a good day,

Leslie – Community Manager

Theiding

22 August 2019 at 23 h 07 min

Great – thank you. Looking forward to it.

Matt K.

23 August 2019 at 16 h 58 min

Looking for the same. Any update here?

Jayhead13

23 August 2019 at 18 h 37 min

Have my eye on this, as well. Keeping my fingers crossed for some good news!

Paul Harrington

27 August 2019 at 20 h 35 min

Legrand plans to support the Eliot API going forward. The integration of Adorne (really the LC7001 black plastic gateway in your house) with SmartThings was never a Legrand-supported integration. It worked “by luck” because Samsung developed Artik Cloud and owns SmartThings and they implemented a Cloud-to-Cloud connection between the Artik Cloud and the SmartThings Cloud. As you know Samsung is shutting down the Artik Cloud, and Legrand (Eliot) Cloud does not have an integration with SmartThings. At this point there is not a plan to add SmartThings support into Legrand Cloud.

Theiding

29 August 2019 at 0 h 39 min

Paul, thank you for the update. I am not looking specifically for SmartThings support for Adorne. I am just looking for any public API into Adorne/LC7001. Legrand must already have an internal API for their app and Alexa implementation.

Will the internal API for Adorne be made publicly available? And/or will Adorne be integrated with the Eliot API?

This reply was modified 4 years, 8 months ago by Theiding.

Kavanoz

7 September 2019 at 5 h 59 min

Look at the current status of Alexa integration with Legrand Lighting Control. They can’t even manage to get their own equipment work with home automation systems. I am not sure if they know how their own API works.

Theiding

23 September 2019 at 6 h 12 min

Hi Paul, any update re. my question above? Thanks,

Mark

Ross Tyler

8 October 2019 at 0 h 56 min

There is a similar problem with the SmartThings/ARTIK Cloud/Legrand integration now that ARTIK Cloud is gone.

As discussed here:

Eliot integration with SmartThings

I have solved this for myself with a SmartThings part and a UPnP part that sits between the SmartThings hub and the LC7001. If your system can speak UPnP, perhaps all you need is this second part. If not, perhaps the code will expose enough for you to get it to work elsewhere.

https://github.com/rtyle/upnp-things

I have been promised that the LC7001 interface will not change as long as it exists. I have yet to receive any formal documentation on this interface.

Michael

11 January 2020 at 5 h 08 min

And I did solve this for myself in python for Home Assistant. But I have 1 problem:

About 1% of all submissions between the LC7001 and the actual switch fail. So eg when I turn a light OFF either via the API or the Android App, the LC7001 shows the switch as OFF, while in reality the light remains still ON. This seems to be dependent on the distance between the switch and the LC7001, and also dependent on time of day. So I suspect Radio interference. But that’s not the question.

The question is whether it’s possible via the Adorne API to remediate such a situation. In other words can I send a second command to force the LC7001 to turn off a switch which the LC7001 thinks is off alreadty? If I simply send the same message again (ie. {‘Service’: ‘SetZoneProperties’, ‘ZID’: 0, ‘ID’: 1, ‘PropertyList’: {‘Power’: False}}), nothing happens. The LC7001 seems to filter this out as it thinks (erroneously) that the light is OFF already. So currently, I must turn the light on first before I can try to turn it off again. So the question is if it’s possible to send the “turn-off” command again without first turning it on? Some kind of a force update?

PS: The same problem happens on the Android App. So if the OFF command fails, the App still shows it as OFF while the light remains ON in reality. I then need to turn it ON again via the App before I can turn it OFF a second time.

Theiding

23 February 2020 at 5 h 24 min

Michael, I have the exact same issue. It’s good to know that this is indeed a common problem. The issue comes down to that the communication between hub and switches appears to be rather unreliable. Legrand really needs to fix that. But as long as the communication remains unreliable the hub mustn’t trust its own state and shouldn’t filter out what appears to be duplicate commands (i.e. what you describe above). If communication were reliable then it would be a good optimization to filter out commands for the state the switch is already in, but with unreliable communication every command should be passed on to at least recover from past mistakes (the forced update you described above). In other words every update should be forced in the hub.

There is an additional, but related issue: if you reboot the hub all switches initialize to off regardless of the actual switch state. That is fully reproducible. A clear bug in the hub.

I have been trying to work with support starting with the reboot issue (as it is easier to understand). Unfortunately interaction with support has been rather difficult as they have little technical background (most don’t know what an API is). Overall the LC7001 feels more like a beta product.

Leslie – Community Manager

24 February 2020 at 14 h 01 min

Hello everyone,

The LNCA dev team is aware of the issue and is investigating to find the root cause

Once done, they will work on a resolution. We’ll warn you when it will be fixed

Have a good day,

Leslie – Community Manager