That sounds like some sort of hardware failure. Or firmware problem, which might be better news but odd because everyone has the latest and greatest firmware and I haven’t seen messages like that before.
Has there been any resolution to this. I too am seeing the same errors in my Events. Been having weird issues lately like my Home-Sleep mode would only turn on things but would not turn off requested things. This is what prompted me to look in IDE.
I was able to replicate the behavior by rebuilding my entire network. I narrowed the error down to a battery powered device that got included kind of funky. Even after removing the device, I could not remove the error without nuking the whole thing and starting over.
Do you have an Enerwave ZWN-BPC? That is what I suspected did it, but I have not confirmed yet.
Yes I do. I have two of them. Would you suggest removing them and re-running a repair. I am digging back deeper into the logs and I noticed that the I started receiving the error after I attempted a z-wave repair. Plus I see a few a few errors where it could not assign a new route. I fixed on these yesterday by doing an exclude and include, maybe I should try that for the other two items.
Yea go ahead and see if removing those devices clears up the error for you. In my experience, it has not – it took a full factory reset to fix this error the last 2 times I got it. Just so you know, I removed every single device individually and still got the error. Factory reset was the only thing that worked.
So last night and after chatting with support it was suggested that I try the airgap trick, which did not work. So I end up removing the non-responding devices and re-added them. Of course we all know what fun this is. Once I got it all added back in I did a reboot of the hub and that seem to take forever followed by a z-wave repair. After that my system went completely haywire, nothing seem to work correctly. At that point I sent an email to support and stepped away from it for the night. Several hours later I was able to execute my sleep routine without issues. So this morning I logged into IDE and noticed that several devices were not responding last night during the z-wave repair but I no longer saw the power cycle events in IDE. I rolled the dice and ran another z-wave repair and I am happy to say that I got a successful z-wave repair to run!
I did the repair on the whole z-wave network. I did not remove the Enerwave devices. I did not want to remove them if I did not have to because they were very difficult to install. In fact, I have not even updated the device to the official supported device type because after install I never had issues and I did not want to deal with the headache again.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
14
Yep - Factory reset I had to do it a few times because I kept adding the suspect Enerwave devices back in. Even if you do remove the bad device, it seems that the chip gets locked into that state. I’ve noticed some poor behavior with old Jasco switches as well so even if you don’t have those Enerwaves, it still might be caused by old lame switches.
If you do end up doing a factory reset, I highly recommend a V2 minimote. That thing was a lifesaver. Too bad you can’t back up the SmartLighting (or Rule Machine) config though!
Kristopher
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
16
I have a ver. One Minimote with updated firmware… How do I use it to exclude devices?
You don’t even need it paired to do an exclusion. Just hit the - button and then whatever you need to on the device to make it exclude. You’ll see the remote blink red and blue a little and then it’s excluded. If you have the V2 (won’t work with V1 + new firmware) you can actually make it repair via the remote as well.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
18
Ok, do I need the v2 Minimote? The v1 updated won’t work?
Yeah, unfortunately. I tried using the V1 upgraded. It won’t associate with the network properly for whatever reason. You can still use the V1 to exclude though.