LiXee ZLinky_TIC DDF File

DDF-Library
203

Seems you got the already documented FF endpoint bug : After DDF modification got duplicate clusters with 0xff endpoint - #27 by BabaIsYou

204

So you have added the total consumption in your DDF, have restart deconz and have now the ff-0B04 sensor ?

205

Yes i have a ff-0b04 sensor.

206

The only sure way I know to remove it is to delete the device first and then restart DeConz. If that’s not sufficient we perhaps have to go into database but it’s too early to go that way.

207

And we don’t know what provoke this issue, do you have set phoscon in permit join at a moment ? (“add new sensor”)

208

Pretty strange :thinking: gonna make a deep dive in the code to see where this is created, there can’t be that many places. The database loading should already prevent reloading such entries, but it doesn’t help if they are created again later on.

209

I try to remove my device in phoscon, remove device in jeedom. Restart jeedom and include device in phoscon. After synchro in jeedom. I always have a zhapower current, voltage and power ff-0b04.

210

And the bad thing is I don’t know a way to remove it, you need to use a SQL editor but it’s not something simple as thez device is not visible in it if I m right, or better if you have an old zigbee backup (made with phoscon)

211

Did you restart Deconz after deleting the device in Phoscon ? That’s the key here because Deconz seems to keep this sensor in memory until restart. As manup says, at restart some code prevent reloading it.

212

I remove zhapower for total power in zhaconsumption in ddf. And delete device and paring again. And the power ff-0b04 disappears.

213

Ha ? You mean adding

       {
          "name": "state/power",
          "refresh.interval": 300,
          "read": {
            "at": "0x0306",
            "cl": "0x0b04",
            "ep": 1,
            "fn": "zcl"
          },
          "parse": {
            "at": "0x0306",
            "cl": "0x0b04",
            "ep": 1,
            "eval": "if (Attr.val != -32768) { Item.val = Attr.val; }"
          },
          "default": 0
        },

this part, used for ZHAPower normally, inside the ZHAConsumption sensor provoke the ff-0b04 apparition ?
It’s exactly this code you are adding ?

214

Yes it’s exactly the code are adding. I post my ddf before.
This code adding power total in zhaconsumption but also a New zhapower ff-0b04 with no value.

215

Ha yes sorry LiXee ZLinky_TIC DDF File - #202 by Piksimou

Thx a lot, I realy have no clue where it’s from, but it’s the first time we have a way to produce the issue.

But about your problem, it mean if you want the total power, there is only 2 solutions, another ZHAPower just for it, or make yourself the addition using the 3 other ZHAPöwer ?

216

In your first ddf, i am add in zhaconsumption a total power. And i remove this part because i don’t know what is it.

{
          "at": "0x050B",
          "dt": "0x21",
          "min": 60,
          "max": 300,
          "change": "0x00000001"
        },

I remove device in phoscon, del in deconz. Include again device and all work.
Zhapower ff-0b04 has disappeared.

217

This part is the report for the attribute 0x050B, and you are right, it’s the power for monophase device, not used on your DDF, need to be removed.

Edit:
I m not sure have understand, you mean if you add the total power, but remove the useless report, you don’t have the ff-0b04 bad sensor ?

218

Yes i don’t have the bad sensor ff-0b04.

219

Ha ? This can be usefull.
So this FF endpoint sensor can be proboked by the binding/report table ! For exemple if the bind is on attribute that is not used in the DDF 


BTW as your DDF is now working and complete, do you want to make a PR to add it offcialy or do you want I make it ?

220

Yes you can make PR.
Thanks you for your help and your work.
Samuel.

221

Thx for help too.
PR done DDF add support for ZLinky_TIC standard+HPHC+triphase by Smanar · Pull Request #7016 · dresden-elektronik/deconz-rest-plugin · GitHub

222

Hi Smanar,

Just to let you know that eventually I decided to start again using my ZLinky device. I stopped using it because of instability. I update the firmware and used the limited one. It works like a charm ! Next step will thus to switch from the history mode to the standard one (I have now a solar panel and thus want to know how much electricity I send back to the grid when I do not use all the energy produced by the solar panel). I will use the latest DDF and I will probably have to adapt it so that it will generate correctly the OpenHAB items.