Zwave repair and Inovelli Switch

[squidbillyms (Jr. Bates)]

I have tried to run a zwave network repair from the hub (SmartThings v2). I see in the HUB event log that it starts:

zwStatus device setup Z-Wave device setup started
zwStatus network repair Z-Wave network repair started
zwNwkRepair started Z-Wave network repair started

Immediately, in the live log, I see the following which is for an Inovelli switch using the following DTH

• Inovelli Switch NZW30/NZW30T w/Scene
• Author: Eric Maycock (erocm123)
• Date: 2018-08-03

debug Couldn’t zwave.parse 'zw device: 0B, command: 5E02, payload: 01 05 00 1D 00 1D 00 ’
warn Exception ‘java.lang.NullPointerException: Cannot invoke method parse() on null object’ encountered parsing ‘cmd: 5E02, payload: 01 05 00 1D 00 1D 00’
debug Unhandled: AssociationGroupCommandListReport(command: [37, 3, 91, 3, 90, 1], groupingIdentifier: 1, listLength: 6)
debug Unhandled: AssociationGroupNameReport(groupingIdentifier: 1, lengthOfName: 8, name: [76, 105, 102, 101, 108, 105, 110, 101])
debug Unhandled: AssociationGroupInfoReport(dynamicInfo: false, groupCount: 1, listMode: true)
debug Unhandled: AssociationGroupInfoReport(dynamicInfo: false, groupCount: 1, listMode: true)

And that is all I get concerning the network repair from either the hub event or live log … no failed or successful … that’s it. Pings still show and other polling events are logged.

UPDATE:
Changed all Inovelli switches to type - Zwave Switch and I get the following upon initiating a repair
debug Parse returned null
warn Exception ‘java.lang.NullPointerException: Cannot invoke method parse() on null object’ encountered parsing ‘cmd: 5E02, payload: 01 05 00 1D 00 1D 00’
debug Parse returned null
debug Parse returned null
debug Parse returned null
debug Parse returned null

[JDRoberts]

Tagging @erocm1231 @Eric_Inovelli

[erocm1231 (Eric M)]

Hi @squidbillyms, those informational messages won’t cause any problems. The ones that are displayed with my handler are just logging that there are some association group reports that aren’t being handled by the device handler. The device handler doesn’t need those reports to function so it is ignoring them (unhandled). Looking at the code for the “Z-Wave Switch” handler it does not log unhandled reports so they won’t show up.

As for the Exception warning, I wouldn’t worry about that either. I would have to take a look at the frame with a zniffer, but it looks like the switch is sending the SmartThings hub a command from the COMMAND_CLASS_ZWAVEPLUS_INFO_V2 class. The SmartThings hub can’t parse the command that is received. I would have to do more digging to find out why, but I see these kinds of errors pop up here and there from various devices.