Energy usage log entry driving me bonkers

Posted on
Sat Nov 25, 2017 5:54 am
Stoutjesdijk offline
User avatar
Posts: 135
Joined: Dec 21, 2014
Location: The Netherlands

Energy usage log entry driving me bonkers

Hi all,

I have one device that's spamming the log with once-a-second updates on its load.
It makes it very hard to work with the log. Is it a bug or can I somehow turn this off? The device settings do not give me that options...

Thanks!


Code: Select all
Indigo Z-Wave Version: 2.0.111
Node ID: 80
Model: Flush 1 Micro Relay (ZMNHAD)
Model ID: 00020052
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 1.01
Model Definition Version: 5
Library Type: 3
Class Name: Relay Power Switch
Class Hierarchy: 04 : 10 : 01
Command Class Base: 25
Command Versions: 20v1 25v1 86v1 27v1 72v1 8Ev1 70v1 32v4 73v1 59v1 5Av1 5Ev1 85v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming, energyMeter
Neighbors: 1, 12, 15, 26, 28, 31, 38, 39, 41, 43, 81, 85, 87, 88
Associations: 1:[1] 2:[1] 3:[] 4:[] 5:[] 6:[] 7:[] 8:[] 9:[1]
Config Values: 1:1 2:0 3:0 100:0 101:0 120:5 110:32536 30:0 63:0
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 5A 00 00 CE
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.0 W (float: 9.000000)
   Z-Wave                          received "BR Kids light" power load to 9.0 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 5A 00 00 CE
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.0 W (float: 9.000000)
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 75 00 00 E1
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 11.7 W (float: 11.700000)
   Z-Wave                          received "BR Kids light" power load to 11.7 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 5D 00 00 C9
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.3 W (float: 9.300000)
   Z-Wave                          received "BR Kids light" power load to 9.3 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 6A 00 00 FE
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 10.6 W (float: 10.600000)
   Z-Wave                          received "BR Kids light" power load to 10.6 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 57 00 00 C3
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 8.7 W (float: 8.700000)
   Z-Wave                          received "BR Kids light" power load to 8.7 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 69 00 00 FD
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 10.5 W (float: 10.500000)
   Z-Wave                          received "BR Kids light" power load to 10.5 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 5C 00 00 C8
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.2 W (float: 9.200000)
   Z-Wave                          received "BR Kids light" power load to 9.2 W
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 5C 00 00 C8
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 9.2 W (float: 9.200000)
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 34 00 00 00 68 00 00 FC
   Z-Wave Debug                    . .  requestMeterLevel: node 080, endpoint None, meterType 01, raw value 3400...
   Z-Wave Debug                    . .  requestMeterLevel: 10.4 W (float: 10.400000)

Best regards,

Mark

Trying to tie it all together...
| Indigo | Plex | NAD M33 | Unifi | LG WebOS | Tado | Sonos | SolarEdge | HUE |

Posted on
Sat Nov 25, 2017 6:33 am
CliveS offline
Posts: 770
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Energy usage log entry driving me bonkers

Have a look at configuration parameters 40 and 42

Parameter no. 40 – Power reporting in Watts on power change
Set value means percentage, set value from 0 - 100 = 0 % - 100 %. Available configuration parameters (data type is 1 Byte DEC):
* default value 10 = 10 %
* 0 – Reporting Disabled
* 1 – 100 = 1 % - 100 % reporting enabled
* Power report is sent (pushed) only when actual power in Watts in real time changes for more than set percentage comparing to previous actual power in Watts, step is 1 %.
NOTE: If power changed is less than 1 W, the report is not sent (pushed), independent of percentage set.

Parameter no. 42 – Power reporting in Watts by time interval
Set value means time interval (0 – 32535) in seconds, when power report is sent. Available configuration parameters (data type is 2 Byte DEC):
* default value 300 = 300 s
* 0 – Reporting Disabled
* 1 – 32535 = 1 second – 32535 seconds.
* Reporting enabled. Power report is sent with time interval set by entered value.

CliveS

Indigo 2023.2.0 : macOS Ventura 13.6.3 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Sat Nov 25, 2017 7:06 am
Stoutjesdijk offline
User avatar
Posts: 135
Joined: Dec 21, 2014
Location: The Netherlands

Re: Energy usage log entry driving me bonkers

Parameter 42 to 0 worked. Awesome, thanks! :D

Best regards,

Mark

Trying to tie it all together...
| Indigo | Plex | NAD M33 | Unifi | LG WebOS | Tado | Sonos | SolarEdge | HUE |

Posted on
Sun Dec 30, 2018 4:51 am
128lyonsroad offline
Posts: 2
Joined: Dec 26, 2018

Re: Energy usage log entry driving me bonkers

Hi,
I’m using Qubino in wall dimmers. Have about 20. One single one is constantly reporting cumulatively energy usage every second.
I’ve set para 40 and 42 and confirmed both to 0. No effect.
Any ideas?
Matt

Posted on
Sun Dec 30, 2018 11:06 am
matt (support) offline
Site Admin
User avatar
Posts: 21416
Joined: Jan 27, 2003
Location: Texas

Re: Energy usage log entry driving me bonkers

Does it show in Indigo that it has the same firmware version as the other (better behaving) modules?

Try excluding it from the Z-Wave controller, re-including, and re-syncing it (and also change the parameters again).

Image

Posted on
Mon Dec 31, 2018 6:59 am
siclark offline
Posts: 1960
Joined: Jun 13, 2017
Location: UK

Energy usage log entry driving me bonkers

It does the same to me too. Drives me crazy. Parameter changes made no difference. I hate the buggy firmware on qubino devices.

In my case it's the current power that's reporting every few seconds. Sometimes for as little a change as 0.3W despite the instructions saying it will never report for less than 1W change

Sent from my iPhone using Tapatalk

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 3 guests

cron