Power and energy are not updated (Qubino and Fibaro)

[JF_Castanier]

Hi all,
I have a behavior that I don’t explain without sense.
For some objects, even it’s the same model, the power and energy are not interpreted by the Homey box, but not all. Some of them are working.
I don’t understand this behavior.

Behavior 1:

• 2 same module for light (Qubino ZMNHSD1) : 1 is reporting energy and power, other does not. Why ?
• Both modules have the same parameters.
  

Behavior 2 :

• 2 same module for Roller Shutter (Fibaro FGR-223) : 1 is reporting energy and power, other does not. Why ?
• Both modules have the same parameters.
  

This is just an extract and I have same issue with other modules.

Is someone have experimented this issue ?
Do you think I can do somthing by my side ?

Thanks all in advance for your help.
Regard.

[DirkG]

I have some similar problems with Fibaro Walli Switch (FGWDSEU-221):
– same settings
– same hardware firmware
– different date when I added these devices (= different Homey FW and different Fibaro app version!)

The left one “Walli Switch HWR” was added some month ago.
The right one “Walli Switch Spiegellicht Bad” was added some days ago.
So I guess Athom made some changes at the Homey firmware and/or the Fibaro app between the first and the second installation.

Is that the case for you as well?

Regarding the Fibaro RS2 please read this thread.

Conclusion of this thread
From my point of view, there are two possibilities that cause the problem:
– different installation date (as already mentioned)
– different “blind position” report type (but you say that the parameter are equal, so this can’t be the point)

Anyway, I would like to ask you to inform Athom about the problem.

[JF_Castanier]

Hi @DirkG.
Your case is very similar than mine and your possibilities are very interesting but my both behavior have been integrated the same day.
So the hypothese of different installation date does not match with my case, but I think it may be a way to investigate for your case from Homey team.

I think the issue come from Homey because it occurs with Qubino and Fibaro too, not only Fibaro.
No idea why one in well interpreted and the other one not, even both have been integrated the same days, with the same HW version.

How can I contact Homey team for this issue and submit them it ?

[DirkG]

Ok, same day, same firmware, same app state, same settings.

Did you checked in Developer if the capabilities are identical (Developer → Tools → Devices)?

A possible theory could be that not all data was transferred during the inclusion process to homey, or data was transferred incorrectly. But it is my personal theory, I am not a Z-Wave expert, nor a programmer.
Maybe try to include a faulty module again.

But indeed there are some problems with Z-Wave devices and the firmware and/or apps.

You can contact the support of Athom via this email: support@athom.com

@Caseda, do you know what is going on here with some Z-Wave devices (wrong on/off state; wrong dim level state; no report of consumption)?

[Caseda]

@DirkG

@Caseda, do you know what is going on here with some Z-Wave devices (wrong on/off state; wrong dim level state; no report of consumption)?

I do not.
It isn’t “not all data was transferred during inclusion” then the device won’t work at all in Homey, and will give an error like “invalid command class” or “that isn’t a function of command class”, or something the like.
It could be distance (Homey’s range isn’t the biggest) or an interference factor (nearby/in between) that one device has, and the other not.

[DirkG]

Thank you for your reply and the info regarding info regarding my theory.
But I can not imagine that the Qubino devices work without errors (on/off) and only the consumption values are not transmitted.

In my case, it is almost definitely due to the fact that the Walli Switch was included at different times (= different Homey FW and app version).

@JF_Castanier, could it be a distance or connection problem?

[JF_Castanier]

the on/off commutation is working well, no problem with that.
Each on/off command is sent with success, even it is done by wall switch or from the phone.
Modules do the job, but some don’t send the energy/power consumtion

@DirkG Regarding the distance, the Qubino module are 8m of distance from the Homey (both are at the same distance because they are into the electrical table).
The Fibaro module are behin roller switch, one (which is working) is 7m with 2 wall between, and other one (wich does not send infos) is 5m with 1 wall between.

In case of, I have restarted the homey box many time, no change.

@Caseda i have 4 Qubino ZMNHSD1 side by side to control my main room. Don’t know if it may have an impact on interference. I guess this is a typical case and no problem with that.
Here is an overview of what is workking and not, if it can help :

[JF_Castanier]

to complete information for troubleshoot, below the log associated to Node214 (one which has problem) :
[2021-05-30T13:41:15.959Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:15.960Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}
[2021-05-30T13:41:16.958Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:16.960Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}
[2021-05-30T13:41:17.964Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:17.965Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}
[2021-05-30T13:41:18.957Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:18.958Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}
[2021-05-30T13:41:20.003Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:20.005Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}
[2021-05-30T13:41:20.956Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:20.957Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}
[2021-05-30T13:41:21.955Z] Node[214]: Received application command for COMMAND_CLASS_METER, data: 0x020134000000000000
[2021-05-30T13:41:21.956Z] Node[214]: [COMMAND_CLASS_METER] {“Meter Type (Raw)”:{“type”:“Buffer”,“data”:[1]},“Meter Type”:“Electric meter”,“Properties1 (Raw)”:{“type”:“Buffer”,“data”:[52]},“Properties1”:{“Size”:4,“Scale”:2,“Precision”:1},“Meter Value”:{“type”:“Buffer”,“data”:[0,0,0,0]}}

Below the technical specs of 2 modules in error (Qubino & Fibaro) :

[JF_Castanier]

Hi all,
I come back with news.
I have sent the issue to Athom support and the recommended solution is to unpaire and pair again the module.
I have tested the solution on 2 modules (ZMNHSD1 & ZMNHAD1) and it works.
Now I have the energy meter and power consumtion on each module.

I don’t have a real reason of why, but my opinion is once we pair for the first time a module, we have to verify that each information are well interpreted by Homey box before closing the electrical box/switch, preventing to unpai and pair gain.

Thanks to @DirkG and @Caseda for their time and help.
Hope this can help other persons.

Best regards.

[DirkG]

That was also my suggestion in post #4, to re-include the devices.

However, this does not seem to be the whole truth. I have 2 Fibaro Walli Switch (single switch operating mode configured) which I included a few months ago. In the beginning the power consumption and energy was displayed. Since about 2 months the power consumption and energy is no longer displayed as you can see at the screenshots.

I guess that some Homey firmware update or Fibaro app update caused the problem.

Regarding the inclusion. I always include Z-Wave modules in close distance to the Homey (max. 5 cm). I also wait enough time after the LEDs have stopped blinking before I disconnect the modules from the power. Then I install the modules at their place of use.

In the meantime, I have contacted Athom again. Let’s see what Athom says this time.

EDIT

@JF_Castanier, this is the answer from Athom regarding my two mentioned Walli Switch after I send them a Z-Wave report/communication log:

„Some data does seem to be communicated to Homey, so it most likely is a minor app bug.“