ZWAVE LOG - ZOOZ Powerstrip ZEN20 log spam

Configuration Z-Wave
1

Hello All,

So my Zooz Zen20 Powerstrip generates the same messages in my log over and over(3-4 times a minute or more) … I’ve disabled all of the power reading sensors, but continue to get log spam. Any ideas of how I should approach stopping this? I’ve tried excluding and doing a new inclusion, still the same issue. I’ve tried editing the config file and removing the COMMAND_CLASS_METER which drastically reduces the number of lines but obviously errors out at that point…

> 2019-10-17 20:12:55.989 Error, Node006, MultiChannelEncap with endpoint set to 0 - Send to Root Device
> 2019-10-17 20:12:55.989 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
> 2019-10-17 20:12:55.989 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:55.989 Info, Node006, Received Meter report from node 6: Power=33.5W
> 2019-10-17 20:12:55.989 Detail, Node006, Refreshed Value: old value=33.6, new value=33.5, type=decimal
> 2019-10-17 20:12:55.989 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:55.989 Info, Node006,     Previous value was 33.6W, received 30 seconds ago.
> 2019-10-17 20:12:55.989 Detail, Node006, Refreshed Value: old value=33.1, new value=33.6, type=decimal
> 2019-10-17 20:12:55.990 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:55.990 Detail, Node006, Refreshed Value: old value=30, new value=30, type=int
> 2019-10-17 20:12:55.990 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:55.990 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:55.992 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:55.993 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:55.994 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.089 Detail, Node006,   Received: 0x01, 0x15, 0x00, 0x04, 0x00, 0x06, 0x0f, 0x60, 0x0d, 0x01, 0x00, 0x32, 0x02, 0x21, 0x32, 0x00, 0xe7, 0x00, 0x1e, 0x00, 0xe7, 0x00, 0xb6
> 2019-10-17 20:12:56.089 Detail, 
> 2019-10-17 20:12:56.089 Info, Node006, Received a MultiChannelEncap from node 6, endpoint 1 for Command Class COMMAND_CLASS_METER
> 2019-10-17 20:12:56.089 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
> 2019-10-17 20:12:56.089 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.089 Info, Node006, Received Meter report from node 6: Power=23.1W
> 2019-10-17 20:12:56.089 Detail, Node006, Refreshed Value: old value=23.1, new value=23.1, type=decimal
> 2019-10-17 20:12:56.089 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.089 Info, Node006,     Previous value was 23.1W, received 30 seconds ago.
> 2019-10-17 20:12:56.089 Detail, Node006, Refreshed Value: old value=22.7, new value=23.1, type=decimal
> 2019-10-17 20:12:56.089 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.090 Detail, Node006, Refreshed Value: old value=30, new value=30, type=int
> 2019-10-17 20:12:56.090 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.090 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.091 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.093 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.094 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.189 Detail, Node006,   Received: 0x01, 0x15, 0x00, 0x04, 0x00, 0x06, 0x0f, 0x60, 0x0d, 0x02, 0x00, 0x32, 0x02, 0x21, 0x32, 0x00, 0x00, 0x00, 0x1e, 0x00, 0x00, 0x00, 0xb5
> 2019-10-17 20:12:56.189 Detail, 
> 2019-10-17 20:12:56.189 Info, Node006, Received a MultiChannelEncap from node 6, endpoint 2 for Command Class COMMAND_CLASS_METER
> 2019-10-17 20:12:56.189 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
> 2019-10-17 20:12:56.189 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.189 Info, Node006, Received Meter report from node 6: Power=0.0W
> 2019-10-17 20:12:56.189 Detail, Node006, Refreshed Value: old value=0.0, new value=0.0, type=decimal
> 2019-10-17 20:12:56.189 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.189 Info, Node006,     Previous value was 0.0W, received 30 seconds ago.
> 2019-10-17 20:12:56.189 Detail, Node006, Refreshed Value: old value=0.0, new value=0.0, type=decimal
> 2019-10-17 20:12:56.190 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.190 Detail, Node006, Refreshed Value: old value=30, new value=30, type=int
> 2019-10-17 20:12:56.190 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.190 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.191 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.193 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.194 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.290 Detail, Node006,   Received: 0x01, 0x15, 0x00, 0x04, 0x00, 0x06, 0x0f, 0x60, 0x0d, 0x03, 0x00, 0x32, 0x02, 0x21, 0x32, 0x00, 0x68, 0x00, 0x1e, 0x00, 0x69, 0x00, 0xb5
> 2019-10-17 20:12:56.290 Detail, 
> 2019-10-17 20:12:56.290 Info, Node006, Received a MultiChannelEncap from node 6, endpoint 3 for Command Class COMMAND_CLASS_METER
> 2019-10-17 20:12:56.290 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
> 2019-10-17 20:12:56.290 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.290 Info, Node006, Received Meter report from node 6: Power=10.4W
> 2019-10-17 20:12:56.290 Detail, Node006, Refreshed Value: old value=10.5, new value=10.4, type=decimal
> 2019-10-17 20:12:56.290 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.290 Info, Node006,     Previous value was 10.5W, received 30 seconds ago.
> 2019-10-17 20:12:56.291 Detail, Node006, Refreshed Value: old value=10.4, new value=10.5, type=decimal
> 2019-10-17 20:12:56.291 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.291 Detail, Node006, Refreshed Value: old value=30, new value=30, type=int
> 2019-10-17 20:12:56.291 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.291 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.292 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.294 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.295 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.389 Detail, Node006,   Received: 0x01, 0x15, 0x00, 0x04, 0x00, 0x06, 0x0f, 0x60, 0x0d, 0x04, 0x00, 0x32, 0x02, 0x21, 0x32, 0x00, 0x00, 0x00, 0x1e, 0x00, 0x00, 0x00, 0xb3
> 2019-10-17 20:12:56.389 Detail, 
> 2019-10-17 20:12:56.389 Info, Node006, Received a MultiChannelEncap from node 6, endpoint 4 for Command Class COMMAND_CLASS_METER
> 2019-10-17 20:12:56.389 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
> 2019-10-17 20:12:56.389 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.389 Info, Node006, Received Meter report from node 6: Power=0.0W
> 2019-10-17 20:12:56.389 Detail, Node006, Refreshed Value: old value=0.0, new value=0.0, type=decimal
> 2019-10-17 20:12:56.389 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.389 Info, Node006,     Previous value was 0.0W, received 30 seconds ago.
> 2019-10-17 20:12:56.390 Detail, Node006, Refreshed Value: old value=0.0, new value=0.0, type=decimal
> 2019-10-17 20:12:56.390 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.390 Detail, Node006, Refreshed Value: old value=30, new value=30, type=int
> 2019-10-17 20:12:56.390 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.390 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.391 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.392 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.394 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.489 Detail, Node006,   Received: 0x01, 0x15, 0x00, 0x04, 0x00, 0x06, 0x0f, 0x60, 0x0d, 0x05, 0x00, 0x32, 0x02, 0x21, 0x32, 0x00, 0x00, 0x00, 0x1e, 0x00, 0x00, 0x00, 0xb2
> 2019-10-17 20:12:56.489 Detail, 
> 2019-10-17 20:12:56.489 Info, Node006, Received a MultiChannelEncap from node 6, endpoint 5 for Command Class COMMAND_CLASS_METER
> 2019-10-17 20:12:56.489 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
> 2019-10-17 20:12:56.489 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.489 Info, Node006, Received Meter report from node 6: Power=0.0W
> 2019-10-17 20:12:56.489 Detail, Node006, Refreshed Value: old value=0.0, new value=0.0, type=decimal
> 2019-10-17 20:12:56.489 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.489 Info, Node006,     Previous value was 0.0W, received 30 seconds ago.
> 2019-10-17 20:12:56.489 Detail, Node006, Refreshed Value: old value=0.0, new value=0.0, type=decimal
> 2019-10-17 20:12:56.489 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.489 Detail, Node006, Refreshed Value: old value=30, new value=30, type=int
> 2019-10-17 20:12:56.489 Detail, Node006, Changes to this value are not verified
> 2019-10-17 20:12:56.490 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.491 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.492 Detail, Node006, Notification: ValueChanged
> 2019-10-17 20:12:56.493 Detail, Node006, Notification: ValueChanged

Any help would be greatly appreciated!

2

Why do you care how many log messages are appearing? Is your log file growing too large? Is the quality of your Z-Wave network being impacted by the frequency of updates?

If all you want to do is quiet the logs without impacting the update frequency, you can adjust the log levels in the options.xml file. That will affect all nodes though.

Otherwise you can configure the device to report values less frequently. Look at your device manual, you can adjust the Power and Energy report frequencies to whatever time you want. Power defaults to every 30 seconds. The settings are in the ZWave control panel. Increasing the report time frequencies will also reduce the traffic in your Z-Wave network, so that is a benefit, but you lose out on the granularity of data you can log.

Modifying the zwcfg*.xml isn’t going to do anything, and not something you want to do unless you need to do enable central scenes or some other hack. Removing the class has no effect.

Disabling sensors in HA has no relation to what’s logged in OZW_Log.txt.

1 Like
3

Also, since your device has a “Power Wattage Report Value Threshold” setting, which defaults to 5W, you probably won’t miss much by reducing the report frequency to a much longer value. If your power levels don’t change within 5W (or whatever value you choose) very often, and you don’t care about < 5W changes, reporting less often will reduce the congestion in your network, so probably a good idea.

4

Thank you! Very thorough answer, much appreciated!

5

Just as a follow up: I was able to modify all the configuration parameters with an automation … I had to define the size for it to actually take (not sure if that’s normal?) … I couldn’t do it via the zwave configuration page, or I wasn’t bright enough to figure it out (not sure which).

I maxed them out for now and disabled the other, as I don’t currently utilize the reported usage for anything of significance. Eventually I may do more with the readings.

Here’s the important part of my automation:

  action:
  - data_template:
      node_id: 6
      parameter: 2
      size: 4
      value: 0
    service: zwave.set_config_parameter
  - data_template:
      node_id: 6
      parameter: 3
      size: 4
      value: 2678400
    service: zwave.set_config_parameter
  - data_template:
      node_id: 6
      parameter: 4
      size: 4
      value: 2678400
    service: zwave.set_config_parameter

Once again, thanks for the assistance FrechCoast!