Device appear in deCONZ but not in Phoscon

monpelaud · February 10, 2023, 11:18pm

Hi,
For months I have been using an aqara llkzmk11lm wireless relay with the deCONZ plugin for HA.
Everything was working fine until deCONZ restarted after an HA core update.
Now this device appears in deCONZ but not in Phoscon and is no longer visible in HA.

In deCONZ ui the device is connected and everything works fine. No errors in deCONZ logs, communication with the RaspBee II module seems to work well.
But I no longer see the device in Phoscon and HA.

To test I mounted a new SD-card from an Phoscon image with the pre-installed deCONZ software as well as the Phoscon App.
After a new pairing of the device, the result is the same!
Any solution to fixe this issue?
What will I lose if I try to reset the RaspBee II module?
Will the pairing of all my devices disappear?

Thanks for your help.
Best regard.

Smanar · February 11, 2023, 8:53am

Hello, How is the node in deconz GUI ? his name is like 0xXXXX or have a correct name ?

If the name is “correct” the device is probably in the API too, try making a search with the uniqueID, something can have moved.

If the device is not correclty included, it can work, but will be removed at next deconz start (not saved if incomplete), it s vivible too on deconz node. Xiaomi: Lost devices or functional issues · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

Mimiix · February 11, 2023, 8:58am

Moved to general support.

monpelaud · February 11, 2023, 10:55am

Hi,
Thanks for your quick reply.
For me the name is “correct”: Power 54

Can you explain to me what you mean by “making search with the uniqueID”?

Making search in deCONZ, Phoscon or HA?
What do you call uniqueID? The MAC Adress?

joe-muc · February 11, 2023, 10:23pm

Edit/Removed: Looked same for me, so moved to another topic:

Smanar · February 12, 2023, 9:11am

You have not same issue, when the name return back too something like 0xXXXX, it’s because the detection is not finished.

I have updated a DDF for this device Xiaomi Aqara relay controller lumi.relay.c2acn01 stopped working · Issue #6512 · dresden-elektronik/deconz-rest-plugin · GitHub

But it’s made with copy/paste from anbother device, not sure power and consumption will work.

Mimiix · February 12, 2023, 9:35am

Please don’t hijack an topic but start your own.

monpelaud · February 12, 2023, 8:55pm

@Smanar,
What should I understand from your answer?
You think that this issue is cause by a wrong DDF file?

Smanar · February 13, 2023, 3:58pm

No, at all ^^.
This device don’t have DDF, and It’s generaly faster to make a DDF than trying to repair the c++ code (that will be removed soon).

I have put the DDF on the github, I think the on/off will work, not sure for consumption.

monpelaud · February 13, 2023, 7:24pm

@Smanar,
Will this new DDF file be released with the next stable version v2.21?

Smanar · February 14, 2023, 5:09pm

I need someone test the DDF and confirm it’s working, or say what it’is not working to finish it.

monpelaud · February 16, 2023, 3:26pm

@Smanar
With the DDF file, now I see the device in deCONZ.
It seems to work but I’m not an expert.
For information I use only one channel on the relay.

    "12": {
        "capabilities": {
            "alerts": [
                "none",
                "select",
                "lselect"
            ]
        },
        "config": {
            "groups": [
                "1"
            ]
        },
        "etag": "4e3ad69a687677449c4a47f8a56722bf",
        "hascolor": false,
        "lastannounced": null,
        "lastseen": "2023-02-16T13:45Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "On/Off output 12",
        "state": {
            "alert": "none",
            "on": false,
            "reachable": true
        },
        "swversion": null,
        "type": "On/Off output",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-01"
    },
    "13": {
        "capabilities": {
            "alerts": [
                "none",
                "select",
                "lselect"
            ]
        },
        "config": {
            "groups": [
                "1"
            ]
        },
        "etag": "c7ae538075e320dd3b4bddd91292ce62",
        "hascolor": false,
        "lastannounced": null,
        "lastseen": "2023-02-16T13:45Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "On/Off output 13",
        "state": {
            "alert": "none",
            "on": false,
            "reachable": true
        },
        "swversion": null,
        "type": "On/Off output",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-02"
    }
		
    "9": {
        "config": {
            "on": true,
            "reachable": true,
            "temperature": null
        },
        "ep": 1,
        "etag": "0875707bdcef3d0cfa70309dc7b19eb4",
        "lastannounced": null,
        "lastseen": "2023-02-16T13:45Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "Consumption 9",
        "state": {
            "consumption": 0,
            "current": 0,
            "lastupdated": "2023-02-16T13:45:21.483",
            "power": 0,
            "voltage": 240
        },
        "type": "ZHAConsumption",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-01-000c"
    },
    "10": {
        "config": {
            "on": true,
            "reachable": true,
            "temperature": 0
        },
        "ep": 1,
        "etag": "c7ae538075e320dd3b4bddd91292ce62",
        "lastannounced": "2023-02-16T10:11:28Z",
        "lastseen": "2023-02-16T13:45Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "Power 10",
        "state": {
            "current": 0,
            "lastupdated": "2023-02-16T13:45:34.015",
            "power": -1,
            "voltage": 0
        },
        "type": "ZHAPower",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-01-0b04"
    }
}

}

{
“13:55:19:683”: {
“attr”: {
“id”: “12”,
“lastannounced”: null,
“lastseen”: “2023-02-16T13:55Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “On/Off output 12”,
“swversion”: null,
“type”: “On/Off output”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01”
},
“e”: “changed”,
“id”: “12”,
“r”: “lights”,
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01”
},
“13:55:19:754”: {
“attr”: {
“id”: “13”,
“lastannounced”: null,
“lastseen”: “2023-02-16T13:55Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “On/Off output 13”,
“swversion”: null,
“type”: “On/Off output”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-02”
},
“e”: “changed”,
“id”: “13”,
“r”: “lights”,
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-02”
}
}

Smanar · February 17, 2023, 5:37pm

monpelaud:

        "state": {
            "consumption": 0,
            "current": 0,
            "lastupdated": "2023-02-16T13:45:21.483",
            "power": 0,
            "voltage": 240
        },
        "type": "ZHAConsumption",

        "state": {
            "current": 0,
            "lastupdated": "2023-02-16T13:45:34.015",
            "power": -1,
            "voltage": 0
        },
        "type": "ZHAPower",

The on/off is working ? The voltage seem good
The power and consumption I m not sure …

And BTW there is no state/power, state/voltage and ect on the ZHAConsumption on the DDF, idk where they are from …
It was from the previous inclusion without the DDF ?

monpelaud · February 18, 2023, 8:07am

@Smanar
Yes, On/Off is working:
“12”: {
“capabilities”: {
“alerts”: [
“none”,
“select”,
“lselect”
]
},
“config”: {
“groups”: [
“1”
]
},
“etag”: “a6f1df1ed12ace78ffee46222b9c1a16”,
“hascolor”: false,
“lastannounced”: null,
“lastseen”: “2023-02-17T20:30Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “On/Off output 12”,
“state”: {
“alert”: “none”,
“on”: true,
“reachable”: true
},
“swversion”: “0x00000000”,
“type”: “On/Off output”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01”
},

“consumption”, “power”, “voltage” are working and I don’t know what is “current”:
“22:33:20:259”: {
“attr”: {
“id”: “9”,
“lastannounced”: null,
“lastseen”: “2023-02-17T22:33Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “Consumption 9”,
“swversion”: null,
“type”: “ZHAConsumption”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-000c”
}

"22:33:20:954": {
    "e": "changed",
    "id": "9",
    "r": "sensors",
    "state": {
        "consumption": 10700,
        "current": 0,
        "lastupdated": "2023-02-17T22:33:20.951",
        "power": 11,
        "voltage": 241
    }

I don’t understand why you say “there is no state/power, state/voltage and etc on the ZHAConsumption on the DDFIn DDF file”?
I see “state/current, state/power, state/voltage” in DDF:
{
“name”: “state/current”,
“parse”: {
“at”: “0x00F7”,
“eval”: “Item.val = Math.round(Attr.val);”,
“fn”: “xiaomi:special”,
“idx”: “0x97”
},
“read”: {
“fn”: “none”
}
},
{
“name”: “state/lastupdated”
},
{
“name”: “state/power”,
“refresh.interval”: 10,
“read”: {
“at”: “0x0055”,
“cl”: “0x000C”,
“ep”: 1,
“fn”: “zcl”
},
“parse”: {
“at”: “0x0055”,
“cl”: “0x000C”,
“ep”: 1,
“eval”: “Item.val = Math.round(Attr.val);”
}
},
{
“name”: “state/voltage”,
“parse”: {
“at”: “0x00F7”,
“eval”: “Item.val = Math.round(Attr.val / 10);”,
“fn”: “xiaomi:special”,
“idx”: “0x96”
},
“read”: {
“fn”: “none”
}
}

Thanks for your help.
Bests regards

Smanar · February 18, 2023, 1:25pm

Yep, but they are in the ZHAPower sensor, not the ZHAConsumption.
The device id 9 is a ZHAConsumption and this one have only a “state/consumption” in the DDF, its for that I think there is a conflict with the legacy code and the DDF one.

Edit: My fault, I m using the ame uniqueID for both.

Edit2:
Have corrected the DDF on the github, now ZHAPower and ZHAConsumption will have a different uniqueID, better to delete old sensor before using the new DD as it will change the uniqueID.

github.com/dresden-elektronik/deconz-rest-plugin

Xiaomi Aqara relay controller lumi.relay.c2acn01 stopped working

opened 10:19PM - 07 Nov 22 UTC

closed 01:55AM - 21 Dec 22 UTC

espen4001

stale Bug report

## Describe the bug  Xiaomi Aqara relay controller lumi.relay.c2acn01, has stopped working. In previous versions this was working somewhat OK, being able to turn on/off both relays as lights via API. Not sure which version it stopped working, but I see it was done some work on it in version 2.05.79. Tried modifying DDF in GUI, but file is not loaded when container is restarted/recreated, even if file is persistent in the correct location - /home/deconz/.local/share/dresden-elektronik/deCONZ/devices ## Steps to reproduce the behavior  Device is showing in the deCONZ VNC-viewer, and it is possible to turn on/off/toggle from cluster menu. But device not listed in api/lights/ ## Expected behavior  Ability to toggle on/off from API. Device listed when doing API-call for lights Device shown as light in Phoscon App, as it was earlier. ## Screenshots  <img width="575" alt="Skjermbilde 2022-11-07 kl 22 56 54" src="https://user-images.githubusercontent.com/38804642/200424623-edc83632-7c35-41fa-99c1-2210e98e6d7f.png"> <img width="644" alt="Skjermbilde 2022-11-07 kl 22 57 49" src="https://user-images.githubusercontent.com/38804642/200424697-4518738b-b68f-416e-9925-56ab0da44c1a.png"> ## Environment  - Host system: Ubuntu VM, ESXi - Running method: Ubuntu Docker container, deconzcommunity image - Firmware version: 26780700 - deCONZ version: 2.19.1 - Device: ConBee II - Do you use an USB extension cable: yes - Is there any other USB or serial devices connected to the host system? No ## deCONZ Logs [_deconz_logs-2.txt](https://github.com/dresden-elektronik/deconz-rest-plugin/files/9955895/_deconz_logs-2.txt) ## Additional context

monpelaud · February 19, 2023, 5:18pm

@Smanar
Here the logs with new DDF file:
{
“10:36:53:288”: {
“attr”: {
“id”: “2”,
“lastannounced”: “2023-02-19T10:19:26Z”,
“lastseen”: “2023-02-19T10:36Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “On/Off output 2”,
“swversion”: null,
“type”: “On/Off output”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01”
},
“e”: “changed”,
“id”: “2”,
“r”: “lights”,
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01”
},
“10:36:53:294”: {
“attr”: {
“id”: “3”,
“lastannounced”: “2023-02-19T10:19:26Z”,
“lastseen”: “2023-02-19T10:36Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “On/Off output 3”,
“swversion”: null,
“type”: “On/Off output”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-02”
},
“e”: “changed”,
“id”: “3”,
“r”: “lights”,
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-02”
},
“10:36:53:302”: {
“attr”: {
“id”: “15”,
“lastannounced”: “2023-02-19T10:19:26Z”,
“lastseen”: “2023-02-19T10:36Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “Power 15”,
“swversion”: null,
“type”: “ZHAPower”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-0b04”
},
“e”: “changed”,
“id”: “15”,
“r”: “sensors”,
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-0b04”
},
“10:36:53:308”: {
“attr”: {
“id”: “14”,
“lastannounced”: “2023-02-19T10:19:26Z”,
“lastseen”: “2023-02-19T10:36Z”,
“manufacturername”: “LUMI”,
“modelid”: “lumi.relay.c2acn01”,
“name”: “Consumption 14”,
“swversion”: null,
“type”: “ZHAConsumption”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-000c”
},
“e”: “changed”,
“id”: “14”,
“r”: “sensors”,
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-000c”
},
“10:36:53:499”: {
“e”: “changed”,
“id”: “15”,
“r”: “sensors”,
“state”: {
“current”: 0,
“lastupdated”: “2023-02-19T10:36:53.494”,
“power”: 0,
“voltage”: 234
},
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-0b04”
},
“10:36:53:503”: {
“e”: “changed”,
“id”: “14”,
“r”: “sensors”,
“state”: {
“consumption”: 5,
“lastupdated”: “2023-02-19T10:36:53.495”
},
“t”: “event”,
“uniqueid”: “00:15:8d:00:07:9b:88:e1-01-000c”
}

I report a bug on github:

github.com/dresden-elektronik/deconz-rest-plugin

Xiaomi Aqara relay controller lumi.relay.c2acn01 stopped working

opened 05:14PM - 19 Feb 23 UTC

monpelaud

Bug report

## Describe the bug  Hi, For months I have been using an aqara llkzmk11lm wireless relay with the deCONZ plugin for HA. Everything was working fine until deCONZ restarted after an HA core update. Now this device appears in deCONZ but not in Phoscon and is no longer visible in HA. In deCONZ UI the device is connected and everything works fine. No errors in deCONZ logs, communication with the RaspBee II module seems to work well. But I no longer see the device in Phoscon and HA. ## Steps to reproduce the behavior  See discussion with @Smanar on Phoscon forum: https://forum.phoscon.de/t/device-appear-in-deconz-but-not-in-phoscon/3298 ## Expected behavior  DDF file proposed by @Smanar in https://github.com/dresden-elektronik/deconz-rest-plugin/issues/6512#issuecomment-1426980875 fixe this issue. ## Screenshots  ![Capture1](https://user-images.githubusercontent.com/16806004/219963276-be492401-6ee0-4e3b-a184-bfb5a4ffa9c1.jpg) ![Capture2](https://user-images.githubusercontent.com/16806004/219963314-9bab7d5b-3eea-49a8-b341-a2b5323afc1e.jpg) ## Environment  - Host system: (Raspberry Pi / PC / NAS) - Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / Marthoc Docker container / Windows / Virtual Machine) - Firmware version: (26xxyy00) - deCONZ version: (2.xx.yy) - Device: (ConBee I / ConBee II / RaspBee I / RaspBee II) - Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II - Is there any other USB or serial devices connected to the host system? If so: Which? ## deCONZ Logs  ## Additional context

Bests regards.

Smanar · February 19, 2023, 5:54pm

I will continue the issue on the github, I m more often on it.

monpelaud · February 19, 2023, 10:19pm

@Smanar, I don’t understand why @SwoopX closed my issue on github, if it’s not a REST API issue, what is it ?
Is DDF file not in the code of deconz-rest-plugin?

Smanar · February 20, 2023, 4:54pm

Yes, but don’t take care, we can continue here if they prefer.
You can’t use deconz to see value for current/power and ect … This device use the Xiaomi cluster. The only way to see them is direclty in the API.

“state”: {
“current”: 0,
“lastupdated”: “2023-02-19T10:36:53.494”,
“power”: 0,
“voltage”: 234
},

You have 0 for current and power, perhaps you haven’t enought load ?

Except that, all is working ? Now all is visible, even in phoscon ?

monpelaud · February 20, 2023, 11:28pm

@Smanar, here are the REST API logs:

"21:51:14:801": {
    "attr": {
        "id": "2",
        "lastannounced": null,
        "lastseen": "2023-02-20T21:51Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "On/Off output 2",
        "swversion": "0x00000000",
        "type": "On/Off output",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-01"
    },
    "e": "changed",
    "id": "2",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:15:8d:00:07:9b:88:e1-01"
},
"21:51:14:804": {
    "attr": {
        "id": "3",
        "lastannounced": null,
        "lastseen": "2023-02-20T21:51Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "On/Off output 3",
        "swversion": "0x00000000",
        "type": "On/Off output",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-02"
    },
    "e": "changed",
    "id": "3",
    "r": "lights",
    "t": "event",
    "uniqueid": "00:15:8d:00:07:9b:88:e1-02"
},
"21:51:14:809": {
    "attr": {
        "id": "15",
        "lastannounced": null,
        "lastseen": "2023-02-20T21:51Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "Power 15",
        "swversion": null,
        "type": "ZHAPower",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-01-0b04"
    },
    "e": "changed",
    "id": "15",
    "r": "sensors",
    "t": "event",
    "uniqueid": "00:15:8d:00:07:9b:88:e1-01-0b04"
},
"21:51:14:812": {
    "attr": {
        "id": "14",
        "lastannounced": null,
        "lastseen": "2023-02-20T21:51Z",
        "manufacturername": "LUMI",
        "modelid": "lumi.relay.c2acn01",
        "name": "Consumption 14",
        "swversion": null,
        "type": "ZHAConsumption",
        "uniqueid": "00:15:8d:00:07:9b:88:e1-01-000c"
    },
    "e": "changed",
    "id": "14",
    "r": "sensors",
    "t": "event",
    "uniqueid": "00:15:8d:00:07:9b:88:e1-01-000c"
},
"21:51:15:22": {
    "e": "changed",
    "id": "15",
    "r": "sensors",
    "state": {
        "current": 0,
        "lastupdated": "2023-02-20T21:51:15.016",
        "power": 1,
        "voltage": 236
    },
    "t": "event",
    "uniqueid": "00:15:8d:00:07:9b:88:e1-01-0b04"
},
"21:51:15:27": {
    "e": "changed",
    "id": "14",
    "r": "sensors",
    "state": {
        "consumption": 552,
        "lastupdated": "2023-02-20T21:51:15.017"
    },
    "t": "event",
    "uniqueid": "00:15:8d:00:07:9b:88:e1-01-000c"
},

We can see:
“current”: 0
“power”: 1,
“voltage”: 236
“consumption”: 552

For me all is ok!
Do you know what the “current” value is?