Lixee zlinky on domoticz+conbee2+DSM7 synology

I wanted the zlinky lixee, but no confirmation of its possible operation in my configuration (dsm7 and deconz) except the addition of the DDF file in HA, I summarize the project (4 days):
conbee 2 update = easy
installing deconz stable docker = easy
the fair4e communicate with the conbee 2, two days (yet the old docker no worries), the firmware does not connect (resinstalling the drivers via two packages)
make the key appear in phoscon (2 days), knowing that the DDF files were originally present and the error and there is a difference in the name of the key (LIXee) and the name of the directory and in the files DDF:
-directory share/deCONZ/devices/lixee => modification devices/LIXee
and in DDF files
“manufacturername”: “LIXee”, (before lixee)
“status”: “Gold”, (before Draft)

and it works
I have three modules in domoticz
current consumption
daily consumption
alarm

This worry me, do you have the device json (direclty from the APÏ, you can see it in domoticz) or the capture with the manufacture name from deconz ?

To be sure there is not a new version.

Hello, I don’t understand your question.
you want to know where the *.json files come from?
they are inside deconz, but they need to be modified anyway in my case.
my zlinky has the firmware last
here is the sheet when the device is recognized

So I don’t understand how your DDF can work.

“manufacturername”: “LIXee”, (before lixee)

Look at your capture, the manufacturer is still LiXee and deconz use the manufacture name and the model id to reconize device, so it’s realy important field.

hello, sincerely me either I spent 4 days this the problem is it is in changing the name of the manufacturer and the name of the folder that it works perfectly, I just miss the measurement of the current.

inside the json
{
“schema”: “devcap1.schema.json”,
“manufacturername”: “LIXee”,
“modelid”: “ZLinky_TIC”,
“product”: “ZLinky_TIC historique+base”,
“sleeper”: false,
“status”: “Gold”,
“subdevices”: [
{
“type”: “$TYPE_POWER_SENSOR”,
“restapi”: “/sensors”,
“uuid”: [
“$address.ext”,
“0x01”,
“0x0b04”
],
“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/on”
},
{
“name”: “config/reachable”
},
{
“name”: “state/current”,
“refresh.interval”: 10,
“read”: {
“at”: “0x0508”,
“cl”: “0x0b04”,
“ep”: 1,
“fn”: “zcl”
},
“parse”: {
“at”: “0x0508”,
“cl”: “0x0b04”,
“ep”: 1,
“eval”: “if (Attr.val != 65535) { Item.val = Attr.val; }”
}
},
{
“name”: “state/lastupdated”
},
{
“name”: “state/power”,
“refresh.interval”: 10,
“read”: {
“at”: “0x050f”,
“cl”: “0x0b04”,
“ep”: 1,
“fn”: “zcl”
},
“parse”: {
“at”: “0x050f”,
“cl”: “0x0b04”,
“ep”: 1,
“eval”: “if (Attr.val != -32768) { Item.val = Attr.val; }”
}
},
{
“name”: “state/voltage”,
“refresh.interval”: 300
}
]
},
{
“type”: “$TYPE_CONSUMPTION_SENSOR”,
“restapi”: “/sensors”,
“uuid”: [
“$address.ext”,
“0x01”,
“0x0702”
],
“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/on”
},
{
“name”: “config/reachable”
},
{
“name”: “state/consumption”,
“refresh.interval”: 10,
“read”: {
“at”: “0x0100”,
“cl”: “0x0702”,
“ep”: 1,
“fn”: “zcl”
},
“parse”: {
“at”: “0x0100”,
“cl”: “0x0702”,
“ep”: 1,
“eval”: “Item.val = Attr.val”
}
},
{
“name”: “state/lastupdated”
}
]
},
{
“type”: “ZHAAlarm”,
“restapi”: “/sensors”,
“uuid”: [
“$address.ext”,
“0x01”,
“0xff66”
],
“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/on”
},
{
“name”: “config/reachable”
},
{
“name”: “state/alarm”,
“refresh.interval”: 300,
“read”: {
“at”: “0x0005”,
“cl”: “0xff66”,
“ep”: 1,
“fn”: “zcl”
},
“parse”: {
“at”: “0x0005”,
“cl”: “0xff66”,
“ep”: 1,
“eval”: “Item.val = Attr.val > 0 ? true : false”,
“fn”: “zcl”
},
“default”: false
},
{
“name”: “state/lastupdated”
}
]
}
],
“bindings”: [
{
“bind”: “unicast”,
“src.ep”: 1,
“cl”: “0x0702”,
“report”: [
{
“at”: “0x0000”,
“dt”: “0x23”,
“min”: 60,
“max”: 300,
“change”: “0x00000001”
}
]
},
{
“bind”: “unicast”,
“src.ep”: 1,
“cl”: “0x0B04”,
“report”: [
{
“at”: “0x0505”,
“dt”: “0x21”,
“min”: 60,
“max”: 300,
“change”: “0x00000001”
},
{
“at”: “0x0508”,
“dt”: “0x21”,
“min”: 60,
“max”: 300,
“change”: “0x00000001”
},
{
“at”: “0x050F”,
“dt”: “0x21”,
“min”: 60,
“max”: 300,
“change”: “0x00000001”
}
]
},
{
“bind”: “unicast”,
“src.ep”: 1,
“cl”: “0xFF66”,
“report”: [
{
“at”: “0x0005”,
“dt”: “0x21”,
“min”: 60,
“max”: 300,
“change”: “0x00000001”
}
]
}
]
}

If you are using the GUI, you can enable some logs, “DDF” not talkative, and “info” and “info_l2”, realy more talkative.

You can enable logs and make a “hot relaod” in the DDF editor, you will see usefull information.

But for me the DDF can’t be used by the device, or the code was modified and was no more case sensitive …