Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

wrong module detection #19108

Closed
apages2 opened this issue Sep 29, 2023 · 41 comments
Closed

wrong module detection #19108

apages2 opened this issue Sep 29, 2023 · 41 comments

Comments

@apages2
Copy link

apages2 commented Sep 29, 2023

Link

https://www.zigbee2mqtt.io/devices/067776.html

Model

067726A

Description

Netatmo wired shutter switch

Vendor

LEGRAND

Picture (link)

https://www.zigbee2mqtt.io/devices/067776.html

Database entry

"device": {"applicationVersion": 0,"dateCode": " \u000020221202\u0000\u0000\u0000\u0000\u0000","hardwareVersion": 1,"manufacturerID": 4129,"manufacturerName": " Legrand","model": "K4027C/L4027C/N4027C/NT4027C","networkAddress": 13499,"powerSource": "Mains (single phase)","softwareBuildID": "002c","stackVersion": 66,"type": "Router","zclVersion": 2},

Notes

Hello

my Legrand 067726A module is detected as BTICINO K4027C/L4027C/N4027C/NT4027C module. It seems to work on basic up/down/stop actions, but the LED remains flashing green and the specific "support position" configuration does not work (no calibration)

Best regards
@Diaoul
Copy link

Diaoul commented Oct 2, 2023 •
edited
Loading

Same issue here but the led stays red in my case and I can't seem to get the rolling shutter move (edit: wiring issue).

@Diaoul
Copy link

Diaoul commented Oct 2, 2023 •
edited
Loading

database.db entry

{
  "id": 54,
  "type": "Router",
  "ieeeAddr": "0x0004740000a434c1",
  "nwkAddr": 56064,
  "manufId": 4129,
  "manufName": " Legrand\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
  "powerSource": "Mains (single phase)",
  "modelId": " Shutter SW with level control\u0000",
  "epList": [
    1,
    242
  ],
  "endpoints": {
    "1": {
      "profId": 260,
      "epId": 1,
      "devId": 514,
      "inClusterList": [
        0,
        3,
        4,
        5,
        15,
        64513,
        258
      ],
      "outClusterList": [
        0,
        64513,
        5,
        25,
        258
      ],
      "clusters": {
        "genBasic": {
          "attributes": {
            "appVersion": 0
          }
        }
      },
      "binds": [
        {
          "cluster": 15,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b00237dfb5a",
          "endpointID": 1
        },
        {
          "cluster": 258,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b00237dfb5a",
          "endpointID": 1
        },
        {
          "cluster": 3,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b00237dfb5a",
          "endpointID": 1
        }
      ],
      "configuredReportings": [
        {
          "cluster": 258,
          "attrId": 8,
          "minRepIntval": 1,
          "maxRepIntval": 62000,
          "repChange": 1
        }
      ],
      "meta": {}
    },
    "242": {
      "profId": 41440,
      "epId": 242,
      "devId": 102,
      "inClusterList": [
        33
      ],
      "outClusterList": [
        33
      ],
      "clusters": {},
      "binds": [],
      "configuredReportings": [],
      "meta": {}
    }
  },
  "appVersion": 0,
  "stackVersion": 66,
  "hwVersion": 4,
  "dateCode": " \u000020230221\u0000\u0000\u0000\u0000\u0000",
  "swBuildId": "002c",
  "zclVersion": 2,
  "interviewCompleted": true,
  "meta": {
    "configured": -904845555
  },
  "lastSeen": 1696267835803,
  "defaultSendRequestWhen": "immediate"
}

@Diaoul
Copy link

Diaoul commented Oct 2, 2023 •
edited
Loading

Trying out things... (papertrail)

legrand.js

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const ota = require('zigbee-herdsman-converters/lib/ota');
const e = exposes.presets;
const ea = exposes.access;

const definition = {
    zigbeeModel: [' Shutter SW with level control\u0000'],
    model: '067726A',
    vendor: 'Legrand',
    description: 'Netatmo wired shutter switch with level',
    fromZigbee: [fz.identify, fz.ignore_basic_report, fz.legrand_binary_input_moving, fz.cover_position_tilt, fz.legrand_led_in_dark],
    toZigbee: [tz.cover_state, tz.cover_position_tilt, tz.legrand_identify, tz.legrand_settingEnableLedInDark],
    ota: ota.zigbeeOTA,
    configure: async (device, coordinatorEndpoint, logger) => {
        const endpoint = device.getEndpoint(1);
        await reporting.bind(endpoint, coordinatorEndpoint, ['genBinaryInput', 'closuresWindowCovering', 'genIdentify']);
        await reporting.currentPositionLiftPercentage(endpoint);
    },
    exposes: [e.cover_position(),
        e.binary('led_in_dark', ea.ALL, 'ON', 'OFF').withDescription(`Enables the LED when the power socket is turned off,
        allowing to see it in the dark`)],
};

module.exports = definition;

This seems to work but led still red and no cover position.

@Diaoul
Copy link

Diaoul commented Oct 2, 2023

Well that's it, this is the max I can do 😬
I'm not sure it changed anything ant BTicino and Legrand seem to actually be in the same basked device-wise.

@apages2
Copy link
Author

apages2 commented Oct 3, 2023 •
edited
Loading

Koenkk/zigbee-herdsman-converters#6229

@Diaoul
Copy link

Diaoul commented Oct 4, 2023 •
edited
Loading

@apages2 does this solve the module still thinking it's in pairing mode issue even after pairing?

@apages2
Copy link
Author

apages2 commented Oct 4, 2023

yes, but the push request has a problem because it is duplicated with the BTICINO module. Under discussion with koenkk

@FabianMangold
Copy link
Contributor

FabianMangold commented Oct 9, 2023 •
edited
Loading

Hi @apages2 and @Diaoul ,

Basic support for 067776A was added to the DEV branch today.
Can you please try this, and close this issue in case the problem is solved ?

Regarding the pairing mode, you may need to:

  • Try to power cycle it (that worked for some of my devices)
  • Unfortunately "Factory reset" the device and (there is a small dip-switch underneath the down button, next to the LED) and subsequently re-pair it once more.

@Diaoul
Copy link

Diaoul commented Oct 21, 2023 •
edited
Loading

Wanted to test today but I cannot without a docker image and there is no image for dev builds 😢
Edit: never mind, wrong repo, testing now

@Diaoul
Copy link

Diaoul commented Oct 21, 2023 •
edited
Loading

@FabianMangold Seems to be recognized correctly 👍 A few comments:

  • I still have the red led staying even after factory reset then pairing, it works fine with the Legrand gateway
  • There is no way to trigger the "calibration" from zigbee2mqtt it seems
  • Manually triggering the calibration with the buttons has no effect
  • Blink works (overrides the red light)
  • Led in dark does not work (light still red)
  • Action (in exposes tab) does not seem to report anything
  • Position seems to be 0-50-100 but since I cannot trigger calibration, hard to say what the culprit is really

All in all, it does not seem that there is a lot of improvements compared to the previous situation with the exception of the correct detection.

@Diaoul
Copy link

Diaoul commented Oct 21, 2023

I'll sniff the traffic on the Legrand gateway and report back with the logs (in a few days).

@FabianMangold
Copy link
Contributor

Hi @Diaoul,

The latest DEV build contains an update, that features switching the calibration mode on the switch.
The behaviour you've described is somewhat odd, I cannot reproduce this on any of my device.

You may want to give this build a try, and attempt to switch the calibration modes. Switching to a simple "Up/Down/Stop" may help to "reset" the device to a normal state.

@Diaoul
Copy link

Diaoul commented Nov 1, 2023

Testing now, I'll report back when I've played a bit with the calibrations.

@Diaoul
Copy link

Diaoul commented Nov 2, 2023 •
edited
Loading

So the options work, it triggers the calibration. But then, asking for a position just does 0 or 100% 🤷
Regarding the led, it's still blinking green or continuous red like it was right before pairing (depends if I pressed the reset button after reset or not).
I've not yet had the time to sniff the network with the Legrand gateway to see what the difference is.

@FabianMangold
Copy link
Contributor

Hi @Diaoul,
Well, first of all, your device must be paired, otherwise it would not answer to the requests sent by Z2M.
In order to request a position, the switch must first be "calibrated", as the switch has no actual knowledge of the actual position a blind in the first place! (Please keep in mind that there is no feedback loop / sensor, the switch remains a switch after all)!
I'll reply to similar questions in PR#6333 shortly (you may want to read through this as well), but in a nutshell, you will have to go through the calibration learning prior requesting a position.

When switching modes, the switch automatically enters "calibration mode". Therefore, i suppose that your switch is currently locked there. If i were you, i would deliberately mess up the calibration, and start over.
To do so, simply physically press and stay on the down button until the blind is down and you hear the relay click, then press down shortly, and then press and stay on the up button until the blind is fully open. This process must be repeated twice. Once done, the switch is back is "normal" mode, but with a messed up calibration.
I would then start the process over.
Can you please try this ? This worked just fine for all of my devices.

Sniffing the traffic might be interesting, albeit unrelevant at this stage, as the Legrand GW uses the very same commands and attributes to handle the situation.
Please let us know the outcome.

@Diaoul
Copy link

Diaoul commented Nov 2, 2023 •
edited
Loading

Well, first of all, your device must be paired

They are, although the led's pattern does not change from before to after pairing.

In order to request a position, the switch must first be "calibrated"

I triggered a calibration by switching to "specific_nllv" which did the same thing as pressing the up + down button for 5 seconds when connected to the Legrand Gateway: the led turns orange and the auto calibration starts.

you will have to go through the calibration learning prior requesting a position

With the Legrand gateway, the above calibration worked and I could request a position.

Sniffing the traffic might be interesting, albeit unrelevant at this stage

It's really weird that my module still has the LED as if it was not paired but is paired nonetheless. I do not have this behavior when connected to the Legrand Gateway. I suspect this causes the module to behave weirdly and that I could learn more by sniffing the traffic.
If you did that already, let me know and I will not waste my time 😅

I will try your calibration technique 👍

@FabianMangold
Copy link
Contributor

FabianMangold commented Nov 2, 2023 •
edited
Loading

They are, although the led's pattern does not change from before to after pairing.

That's really odd, i really cannot reproduce this. To be honest, i remember one similar situation when i first bought the switches a couple of month back, and i may have gotten rid of this by re-forcing a firmware update. Probably not the finest way, but given the fact i wanted to update anyway....
Might be worth trying this on one of your devices.

I triggered a calibration by switching to "specific_nllv" which did the same thing as pressing the up + down button for 5 seconds when connected to the Legrand Gateway: the led turns orange and the auto calibration starts.

Interesting. I've added some notes here:
Koenkk/zigbee-herdsman-converters#6333 (comment)
Would you mind checking / confirming or obviously commenting on those findings ? I have no Legrand GW and thus my findings are reverse-engineering and trial and errors.
I have to check my config. once back home, but on top of my head, i am using the classic mode on my NLLV switches, not the specific mode. Would you know the difference ?
I am interested in the BSO mode anyway, therefore i have not lost much time on the NLLV modes really, but i am happy to assist if i can.

We probably should update the documentation once we've confirmed the calibration modes.
I am not yet happy with the BSO calibration mode, and am still working on that.

Just looping @Koenkk in here, for info only.

@Diaoul
Copy link

Diaoul commented Nov 2, 2023 •
edited
Loading

FYI my firmware version is 0036 (on the Zigbee2MQTT dashboard)

re-forcing a firmware update

How do you do that?

i am using the classic mode on my NLLV switches, not the specific mode. Would you know the difference ?

I actually don't know, I just know that when I used the classic one, nothing happened so I switched to the specific one and auto-calibration started 🤷

@FabianMangold
Copy link
Contributor

FabianMangold commented Nov 2, 2023 via email •
edited
Loading

@Diaoul
Copy link

Diaoul commented Nov 2, 2023

I cannot capture the gateway's network key because when pairing there is no device announcement message 😳
@Koenkk is there something I should do to capture the traffic specifically on Legrand's Gateway? Maybe there is some other kind of security?

When monitoring I see an Association Request from the module followed by an Association Response from the gateway then the following messages are encrypted 😕

@Diaoul
Copy link

Diaoul commented Nov 2, 2023

Well, it turns out it uses a link key over APS and it's actually the default global trust center link key 5A 69 67 42 65 65 41 6C 6C 69 61 6E 63 65 30 39 as described here.
With this I was able to retrieve the actual network key used by the Legrand gateway 🎉

@FabianMangold
Copy link
Contributor

Regarding the firmware updates, you may want to take a look at this page:
https://www.zigbee2mqtt.io/guide/usage/ota_updates.html#local-ota-index-and-firmware-files

Apologies for the confusion regarding the NLLV modes.
You are right, and i've update my comment accordingly.
The "classic" mode indeed seems to be a basic Up/Down/Stop mode, and the "specific" mode is the one supporting the auto-calibration. Just verified this on one of the switches.

@Diaoul
Copy link

Diaoul commented Nov 2, 2023 •
edited
Loading

There is a capture of the pairing of the rolling shutter module with the gateway: legrand.pcapng.zip

I don't think that's an issue with my firmware, it works well with the Legrand Gateway, it must do something that is not done by the Zigbee2MQTT implementation 🤷

@Diaoul
Copy link

Diaoul commented Nov 2, 2023 •
edited
Loading

On the Legrand app, there are 3 modes for "Control mode":

  • Aperture level
  • Orientable sun shades
  • Up / Down / Stop

When picking "Aperture level", you can then choose automatic calibration or manual calibration.

I think this matches well what you did in the newest PR (with the exception of the names).
I can send you zigbee network captures of when I change the mode through the app but I don't think this will help much.

@FabianMangold
Copy link
Contributor

FabianMangold commented Nov 2, 2023 •
edited
Loading

Hi @Diaoul ,
The names and the cluster attributes were extracted from the Legrand documentation, we didn't make them up.
Z2M doesn't do any magic there, all that gets done is changing the calibration_mode. (Attribute 0xf002 in Cluster 0x102).

You'll find the document attached hereafter for reference.
NLLV-cluster-list.xlsx

I don't understand the behaviour of your switch, as i have identical ones (10 of them actually) running the same firmware, all of them working perfectly fine..

To recap.: All 3 modes work with the Legrand App right ?
Aperture Level / Manual -> must be temporal
Aperture Level / Automatic -> must be specific NLLV on 067776A switches, and unavailable on 067776s.

What exactly differs between Z2M and the Legrand GW ?

@Diaoul
Copy link

Diaoul commented Nov 3, 2023

To recap.: All 3 modes work with the Legrand App right ?

Yes, everything works with the Legrand app.

My main focus is to solve this LED issue, it either keeps blinking green as it was before pairing OR still red as it was before pairing.
I imagine there must be something that differs right after the pairing is done.

For example this device does not considers itself "configured" until bound to a group.

As part of its configuration, the remote expects to have a "group" binding configured for each of its button. Otherwise, it will consider itself not fully configured and send unecessary commands on the zigbee network resulting in noticeable delay when controlling your device(s).

Maybe something similar is happening here I have no idea 🤷

What exactly differs between Z2M and the Legrand GW ?

That is my next step, I'll run the same sniffing with my own coordinator and compare in a few days.

as i have identical ones (10 of them actually)

I'd like to have more but first testing with one first so I have no comparison point. Glad you could get them working! No reason I cannot 💪

Maybe my problem is a coordinator issue 🤷
Coordinator: tube_zb_gw_cc2652p2_poe
Coordinator type: zStack3x0
Coordinator revision: 20230507

To recap my next steps:

  1. Sniff network on my own coordinator and compare the results
  2. Force update the firmware on the module
  3. Buy an additional one to compare

@FabianMangold
Copy link
Contributor

FabianMangold commented Nov 3, 2023 •
edited
Loading

I am sure you will, no doubt.
Curious to see the results of your investigations. My devices are not linked to any groups, and the other users having such devices too have not reported such problems either.
Looking forward to your findings.

Just a small edit, as i am trying to figure out some issues related to PR#6333:
Your database.db shows that your devices have HW Version 4. Is that correct ?

Trying to figure out how to differentiate BTicino devices from Legrand 067776A.
My 067776 (without Level Detection) report HW version 8
My 067776A (NLLVs) report HW version 1
BTicino 4027C seem to report HW version 13

Could you please confirm your hardware and the exact model of the device ?

And another question if you don't mind: It didn't work either when the switches were detected as BTicino switches, right ?

That would help a lot.

This was referenced Nov 3, 2023
Merged
Closed
Merged
@apages2
Copy link
Author

apages2 commented Nov 5, 2023 via email

@Diaoul
Copy link

Diaoul commented Nov 6, 2023

I did not find anything super relevant in the capture of the network sadly, join is successful, binding as well, no error shown. I don't really even know what to look for so it makes it a bit hard 😢

There must be something though, or something related to my coordinator I don't know as it is working on the gateway 😠

I'm no trying to force update the firmware on the device but I have this error:

Update of '0x0004740000a434c1' failed (Timeout: device did not request any image blocks)

I've order 4 other modules, see if they work otherwise I'll send them back.

@FabianMangold
Copy link
Contributor

Bonsoir @Diaoul,

That's really odd indeed.
Not sure if that helps, but i am using a "cheap" Sonoff Dongle-E, absolutely happy with it, not a single glitch.

I am stating the obivous, and i am quite sure you've done all of that already, but better safe than sorry:

  • Factory Reset
  • Long power off (electrically disconnected)
  • and for the OTA, attempt to re-launch an OTA straight after the failure of the first one
    The latter is a bit of a "known" issue with the last firmware, that was noticed in another thread when the OTA process was fixed..

Also, can you confirm that your modules are Legrand 067776As ? I've seen that the hardware cersion reported is 4, whereas all of mines are having HW version 1. That "could" explain some differences.

Cheers

@Diaoul
Copy link

Diaoul commented Nov 6, 2023 •
edited
Loading

I've tried the Factory Reset many many times, several times in a row and even reset -> cut power -> reset again
As for the OTA, I tried that but I've made many attempts in various conditions (right after reset / power cycle).
Nonetheless, I will try the long power cycling and re-attempt OTA after failure specifically.

Also, can you confirm that your modules are Legrand 067776As ? I've seen that the hardware cersion reported is 4, whereas all of mines are having HW version 1. That "could" explain some differences.

  • My module is 067726A not 067776A (it's the white version)
  • hwVersion is 4

@FabianMangold
Copy link
Contributor

FabianMangold commented Nov 8, 2023 •
edited
Loading

Hi @Diaoul,
Are you aware of this ? #16948 (comment)
From various reports, it looks like the issue seems to be linked to the Hardware ID indeed, as we suspected.

You may want to take a look at the procedure described over there.

Cheers,

@Diaoul
Copy link

Diaoul commented Nov 8, 2023

I was not aware of that, trying now.

@Diaoul
Copy link

Diaoul commented Nov 8, 2023

Thanks for finding this, this is the exact same issue.

It seems to be partially working at least:

  • the led is now solid green
  • the rolling shutter moved up right after the second pairing
  • I also could trigger the auto-calibration by pressing the buttons

Now I'll wait, see how it goes from there and report back in a few hours.

@Diaoul
Copy link

Diaoul commented Nov 8, 2023

No need to wait a few hours, the auto-calibration finished and everything seems to be working fine now 👍

@FabianMangold
Copy link
Contributor

Amazing, so it was really a weird association issue it seems right ?
Happy to hear it is fixed. Credits go to the users in the thread, and thanks to @syntesys87 for mentioning it in another thread.
Not sure how we can debug this behaviour best really... Should we reach out to Legrand and report that issue ?
Is it really strange that it affects certain HW Versions only..

@FabianMangold
Copy link
Contributor

@apages2: Is everything fixed on your end too ? If so, can we close that issue ?

@Diaoul
Copy link

Diaoul commented Nov 8, 2023

Amazing, so it was really a weird association issue it seems right ?

Yes, I tried resetting many times but not with Zigbee2MQTT down. It's worth noting that the whole time my coordinator was up though so I'm not sure an issue with Zigbee2MQTT is to exclude entirely.

Should we reach out to Legrand and report that issue ?

I believe yes. One lead maybe is that the association to the Legrand Gateway seems different as it does not expose the Network Key the regular way but relies on APS Link security first. Maybe the second association without Zigbee2MQTT noticing that the device left the network triggered another round of packet exchanges that was missing the first time?
The good thing is that now we've tied it to the HW version, Legrand will be able to reproduce and hopefully fix it.

@syntesys87
Copy link

syntesys87 commented Nov 9, 2023 •
edited
Loading

So the green led blinking problem was related to the hardware id exchanged on interview phase? Because before the fix that @FabianMangold gently provided, I resolved the issue following this guide.

@apages2
Copy link
Author

apages2 commented Nov 12, 2023 via email

@FabianMangold
Copy link
Contributor

Hi @apages2,

Thanks for confirming. Could you please close it, since you've opened it ?
Thanks a lot.

@apages2 apages2 closed this as completed Nov 12, 2023
@FabianMangold FabianMangold mentioned this issue Nov 14, 2023
Merged
@Xavinooo Xavinooo mentioned this issue Jan 6, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Diaoul @apages2 @syntesys87 @FabianMangold