Reagarding the XML that is created during initalization. There are 2 devices in the DB which I created identically - as they should be a 100% clone despite the manufacuterer id.
Now when I compare the XMLs that are created after initalization ā¦ one device has NO command class āMeterā in the XML - its in the DB though
Does the device itself identify itself not having this capability or how does this happen?
Yes - this comes from the device itself, so the devices are (apparently) different in some way it seems. Now, it might just be that the class has been removed from the NIF, or, it might be that the functionality has been completely removedā¦
Itās like the Danfoss LC13 and the Devolo version - they look the same, they are (nearly!) the same, but the Devolo version reports current temperature, while the Danfoss doesnātā¦
Can I somehow āforceā the usage of this command class? Or another way to find out if I really have a plug where āmeteringā was removed from the physcial device?
My Screenshot shows a Devolo vs a Philio device. However other users also confirm for the Philio that āMeteringā works for the them - always identified as PAN11 in Habmin. So that would mean there are 2 versions of the same device (PAN11) - with and w/o metering.
Yes - in the database we can add the class, and then in the command class options, put the word āADDā (no quotes). You would also need to add the channels - you should be able to copy the config from the other device.
If it doesnāt work, we need to clean up though as I dont want to leave lots of incorrect configuration in the database where weāre adding channels that arenāt real (like the smoke sensor notification ;))ā¦
I did not forget about that
Your last comment was you would change something in the way messages are processed. I always look in the changes of the new builds . Once I am convinced theere is no way I can send alarms to the sensors (for smoke I am 99% convinced / for the plug I still have some hope) I will definately clean them again ā¦ or ask you for that as I have no right to remove stuff like that I thinkā¦
Well, there are other things we could try, but I suggest for now, letās park it for a while. Iām in communication with Fibaro about some things so I might ask them how this is meant to work. It might be (possibly!) that itās the V1 alarm itās looking for, not the notificationsā¦
Sorry - been busy. Iām just trying to catch up on messages here to make sure thereās nothing else - Iāve already exported the database updates so Iāll generate new code tonightā¦
Iāve removed the smoke sensor channel since Iām pretty sure this canāt work as itās a battery device. Iāll leave the wallplug for now as Iād like to think we can get this working (possibly Iāll try the V1 alarm class rather than the notification).
I updated the binding. Removed the XML. Removed and readded the device.
Although there is the ADD option now in the DBā¦ the xml thats created still does not have this class.
I understood that ADD should have actually forced this?