Inovelli Red dimmer LZW31-SN stopped working but now fixed

As set forth in my final post here the problem has been fixed. However, I'm leaving the post series in case anyone finds themselves in a similar situation.

Here is how it began:

I have an Inovelli Red dimmer, LZW31-SN, that suddenly is acting strangely. If I air gap it I get the green light showing connection is strong, the blue LED comes on but then the the LED goes out. Pushing the top paddle does nothing and turning it it on from inside its device does nothing.

I took a screen shot of the log and uploaded it below.

The text of the logs say:

dev:1652025-04-28 10:32:40.461 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

dev:1652025-04-28 10:32:29.841 PM

error

java.lang.NullPointerException: Cannot get property 'deviceNetworkId' on null object on line 739 (method componentOn)

dev:1652025-04-28 10:31:51.966 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

dev:1652025-04-28 10:31:34.384 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

dev:1652025-04-28 10:28:43.476 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

dev:1652025-04-28 10:22:14.653 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

dev:1652025-04-28 10:22:11.917 PM

debug

Palm Room Bathroom Sink Lights: MeterReport(meterType: 1, precision: 1, scale: 2, size: 4, meterValue: [0, 0, 0, 0], rateType: 1, deltaTime: 0, previousMeterValue: )

dev:1652025-04-28 10:22:10.926 PM

debug

Palm Room Bathroom Sink Lights: MeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 235, 12], rateType: 1, deltaTime: 35, previousMeterValue: [0, 0, 235, 12])

dev:1652025-04-28 10:22:09.902 PM

debug

Palm Room Bathroom Sink Lights: SwitchMultilevelReport(value: 0, targetValue: 0, duration: 0)

dev:1652025-04-28 10:22:09.544 PM

debug

refresh()

dev:1652025-04-28 10:22:04.284 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

dev:1652025-04-28 10:22:02.202 PM

debug

Palm Room Bathroom Sink Lights: Unhandled: ApplicationRejectedRequest(status:0)

Help please

Along with the standard questions (what HE version, are you on ZwaveJS or ZipGateway, etc.), what does the Zwave Details page show for it?

I'm running Hubitat version 2.4.0.151 on a C-8. I am not on ZwaveJS. I don't know what ZipGateway is.

Here are the Z-Wave details:

BTW, when I clicked the "On" button from within the device the time changed, but that may just be a Hubitat internal thing. The switch did not turn on.

I tried to exclude the device, but Hubitat didn't find it. I then tried a factor reset. After I did that I tried to do a "repair" on the Z-Wave page but it said it wasn't responding and now only has the Repair button:

So I went ahead an put it into pairing mode. When it found it the button to swap it for an existing device was grayed out so I re-added it but with a slightly different name (I left the "s" off "Lights").

Here it is re-included:

So now my issue is: How do I get rid of the old one?

This is normal. If you factory reset a Z-Wave device, you have (normally) erased any memory it had of joining the hub's network -- so it can't possibly respond to anything from the hub addressed to that node.

Try a "Refresh," wait a minute or so, see if there's a Remove button. Repeat once if not, or check back in a day or two to see if something changed and there is then. Z-Wave JS should be better at this (with "Remove" appearing sooner or not working if it's there), but if you aren't having problems, I wouldn't say it's worth switching at the moment.

In case there is any confusion, a Z-Wave Repair is not the same as "re-pairing" a device, i.e., adding it to your hub again (technically "inclusion" and not "pairing" for Z-Wave). It is a specific network operation that may help with routing and aimolar problems, particularly on older devices, but is unlikely to solve other problems.

1 Like

I understand that "repair" is used as a synonym for "fix" not to re-pair (pair again).

I tried to Repair it a couple of times, but that didn't work.

I've removed the old one from all Apps except Z-Wave Mesh Details, which I can't do.

I was thinking of using the Remove button inside the device, but that wanted me to put the device in Exclude mode, which, of course, would exclude the "new" one. Since it is finally working again, I'd rather not do that.

If I go to Z-Wave JS would the Remove button also remove the one I just added also?

Why not try what I suggested above instead of any of that?

I'm a little confused. I thought you said to try a Refresh, which I did, and it didn't work. I was going to wait until tomorrow and then try it again.

If you did, that is not what you said:

Make sure you are using the right button. If that does not work right away; waiting, as suggested above, and trying again if "Remove" isn't there by itself would be the next best thing.

Also, why couldn't you do this? Not that it probably matters at this point...

I didn't see where to remove an individual device. I was looking for a device list like the Amazon Echo app or the Google app

Are you sure there isn't and you didn't select them here? It won't interfere with your issue, in any case, though some apps don't like it when you do this.

Perfect! Thanks!

Original one In Use By is now nice and empty:

I was finally able to get it to factory reset and then re-added it with a slightly different name. (I did that as the button to swap it for an existing device during the inclusion process was grayed out).

I only had the “repair” button for the original one. I tried that and it didn’t work (Continued to show a "Non-Responsive). But I then waited a day and tried to “repair” it again and this time the remove (trash can icon) was there and it removed it on its first try.

While the “new” one does showing that it is routing through another switch it seems to be responding virtually instantaneously.