C7 - WakeUpNotification missing events

syepes · September 7, 2020, 10:50pm

Hello All,

I have started the migration of some of my battery operated devices which implement the WakeUp CC.
The issue is that after tracing all the events received from several devices I have not seen any "hubitat.zwave.commands.wakeupv2.WakeUpNotification" events, even after forcing the device to wakeup.
Most of the devices are using S2.

Has some else also noticed this?

I am running the last HE version .145

@bcopeland, Have you seen this when porting other drivers?

syepes · September 18, 2020, 9:57am

@bravenel | @mike.maxwell
It is really strange that I have not seen any kind of WakeUpNotification messages in my ZWave network since I migrated all my devices to the C7 hub

Have you guys noticed this? or is this just normal when devices are paired securely?

Am I missing something here?

syepes · September 23, 2020, 6:51pm

I am the only guy in town that is missing the WakeUp messages? our everyone is sleeping 24x7

JasonJoel · September 23, 2020, 6:53pm

I believe at least one other person has reported this, but I don't remember any specific response from the Hubitat side.

I only have ONE battery operated zwave device, so haven't bothered looking into it, to be honest.

bcopeland · September 23, 2020, 6:56pm

All my battery devices are doing wake ups

syepes · September 23, 2020, 6:59pm

Ok, Strange because on all my drivers I have enabled the tracking and non receive the WakeUpNotification CC.

@bcopeland, did you actually see this CC event get passed to the parse function?

JasonJoel · September 23, 2020, 7:02pm

Might be germane to ask if you are using the new secure wrapper for the functions too.

That is another new variable on the driver side post C-7.

syepes · September 23, 2020, 7:04pm

What is this new variable?

I have upgraded all my drivers the the devices are working I am just missing the WakeUp events to I can push / sync the configuration to the device when it wakes up.

bcopeland · September 23, 2020, 7:06pm

Yes

JasonJoel · September 23, 2020, 7:07pm

Poor choice of words. I didn't mean variable in the literal sense.

I meant wrapping the zwave functions in the updated zwaveSecureEncap wrapper to make them universally support unencrypted, S0, and S2 paired devices.

Like this driver example from Hubitat:

github.com

hubitat/HubitatPublic/blob/master/examples/drivers/genericZWaveCentralSceneDimmer.groovy

/*
	Generic Z-Wave CentralScene Dimmer

	Copyright 2016 -> 2020 Hubitat Inc.  All Rights Reserved
	2020--07-31 2.2.3 maxwell
	    -switch to internal secure encap method
	2020-06-01 2.2.1 bcopeland
	    -basicSet to switchMultilevelSet conversion
	2020-03-25 2.2.0 maxwell
	    -C7/S2 updates
	    -refactor
	    -remove DZMX1 (move to generic dimmer)
	    -add supervision report response
	2019-11-14 2.1.7 maxwell
	    -add safe nav on flashrate
	    -add command class versions
	    -move some leviton dimmers over from generic
	2018-07-15 maxwell
	    -add all button commands
	2018-06-04 maxwell

This file has been truncated. show original

JasonJoel · September 23, 2020, 7:10pm

Probably has nothing to do with anything, though. Was just a thought on another place that maybe the message could get lost/not returned.

That happens post-parse though, so not likely applicable to your issue if the messages are never making it to parse at all.

syepes · September 23, 2020, 7:11pm

Yes I update my drivers following these new methods.
The strange thing is that the device works as expected but I have never seen one single WakeUp event, I have even forced them from the device but nothing..

Below is just one example, but this never gets called:

github.com

syepes/Hubitat/blob/master/Drivers/Fibaro/Fibaro Smoke Sensor.groovy#L212


      
              logger("debug", "parse() - parsed to cmd: ${cmd?.inspect()} with result: ${result?.inspect()}")
          
            } else {
              logger("error", "parse() - Non-parsed - description: ${description?.inspect()}")
            }
          
            result
          }
          
          def zwaveEvent(hubitat.zwave.commands.wakeupv2.WakeUpIntervalCapabilitiesReport cmd) {
            logger("trace", "zwaveEvent(WakeUpIntervalCapabilitiesReport) - cmd: ${cmd.inspect()}")
          }
          
          def zwaveEvent(hubitat.zwave.commands.wakeupv2.WakeUpIntervalGet cmd) {
            logger("trace", "zwaveEvent(WakeUpIntervalGet) - cmd: ${cmd.inspect()}")
          }
          
          def zwaveEvent(hubitat.zwave.commands.wakeupv2.WakeUpIntervalReport cmd) {
            logger("trace", "zwaveEvent(WakeUpIntervalReport) - cmd: ${cmd.inspect()}")
            logger("info", "Device wakup interval: ${cmd.seconds}")
          }

syepes · September 23, 2020, 7:39pm

@bcopeland, have there been any inner changes in this CC or new dependencies on the driver side? I just what to fix my drivers

bcopeland · September 23, 2020, 7:50pm

No.. have you polled the wakeup interval to see what the device is set to?

syepes · September 23, 2020, 7:53pm

That's the hole thing, it need to wakeup so I can set the configs..

github.com

syepes/Hubitat/blob/master/Drivers/Fibaro/Fibaro Smoke Sensor.groovy#L232


// Only send config if not synced
if (!state?.driverInfo?.configSynced) {
  logger("info", "Synchronizing device config")

  cmds = cmds + cmdSequence([
    zwave.associationV2.associationSet(groupingIdentifier:1, nodeId:zwaveHubNodeId),
    zwave.associationV2.associationSet(groupingIdentifier:2, nodeId:zwaveHubNodeId),
    zwave.associationV2.associationSet(groupingIdentifier:3, nodeId:zwaveHubNodeId),
    zwave.associationV2.associationSet(groupingIdentifier:4, nodeId:zwaveHubNodeId),
    zwave.associationV2.associationSet(groupingIdentifier:5, nodeId:zwaveHubNodeId),
    zwave.wakeUpV2.wakeUpIntervalSet(seconds:wakeUpInterval.toInteger() * 3600, nodeid:zwaveHubNodeId),
    zwave.configurationV1.configurationSet(parameterNumber: 1, size: 1, scaledConfigurationValue: param1.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 2, size: 1, scaledConfigurationValue: param2.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 3, size: 1, scaledConfigurationValue: param3.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 4, size: 1, scaledConfigurationValue: param4.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 10, size: 1, scaledConfigurationValue: param10.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 11, size: 2, scaledConfigurationValue: param11.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 12, size: 2, scaledConfigurationValue: param12.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 13, size: 1, scaledConfigurationValue: param13.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 20, size: 2, scaledConfigurationValue: param20.toInteger()),
    zwave.configurationV1.configurationSet(parameterNumber: 21, size: 1, scaledConfigurationValue: param21.toInteger()),

bcopeland · September 23, 2020, 7:54pm

You can trigger a wakeup on sleepy devices.. You can then poll the wakeup interval

syepes · September 24, 2020, 5:03pm

@bcopeland
There is definitively something strange or different with the C7.

I have connected a "Aeotec Water Sensor 6" to my old C4 and I can see the WakeUpNotifications events but when I get the same device reconnect it to the C7 I can never get the WakeUpNotification events using the same driver.

github.com

syepes/Hubitat/blob/master/Drivers/Aeotec/Aeotec Water Sensor 6.groovy#L211


    break;
  }

  return result
}

def zwaveEvent(hubitat.zwave.commands.wakeupv2.WakeUpIntervalGet cmd) {
  logger("trace", "zwaveEvent(WakeUpIntervalGet) - cmd: ${cmd.inspect()}")
}

def zwaveEvent(hubitat.zwave.commands.wakeupv2.WakeUpNotification cmd) {
  logger("trace", "zwaveEvent(WakeUpNotification) - cmd: ${cmd.inspect()}")
  logger("info", "Device woke up")
  def cmds = []
  def result = []

  cmds = cmds + cmdSequence([
    zwave.sensorMultilevelV5.sensorMultilevelGet(sensorType: 1, scale: (location.temperatureScale=="F"?1:0))
  ], 300)

  // Only send config if not synced

I think you also have this device, I you seeing them on yours?

bcopeland · September 24, 2020, 5:07pm

Yes.. The built-in driver sees these wake ups

syepes · September 24, 2020, 5:25pm

There must be some changes in the driver handling, do you know what it could be?

Is there something specific you guys are doing? That I am not?

El-Rick · March 4, 2023, 11:47pm

Hi @syepes. Did you ever solve this? I just downloaded you zipato keypad driver and after a bit of debbuging I found that the driver is not getting the WakeUpNotification event. I'm on C7.