So I was finally able to update to 5.192.6 (beta). I’ve also tried to start my switch over to long range for some sensors to see if that fixes some of my issues, however I think I may have stumbled across an issue.
Here are my exact steps at the moment (not sure what matters, so I will list everything):
I’m on a LAN connection (wifi is disabled)
I remove a ZSE18 the traditional way, click the red remove device at the top, click the button three times.
Then add device at the top.
Choose smart start, scan the QR code, choose LR.
Rename the device, choose the room etc.
Attempt to move on to the next motion sensor, click remove device. This is where it falls apart, the ZBox never moves past this screen below, or lets you remove anything else (see below):
After you remove the device–but before re-adding as LR–have you performed a factory reset on the device?
That’s what tripped me up doing something similar, but it was on an earlier hub release. So perhaps the issue manifests itself differently?
That being said, nothing should hang–it should put up some error message or whatever–so, it is still a bug. But try the factory reset of the device to see if you can move on…
The device removes successfully, and I had added the device as LR. This afterwards when I go to remove the next device (this is the hang point). I can’t remove any other devices afterwards until I reboot the hub. The pattern repeats itself. Remove device, add device, then a reboot is necessary.
Or are you saying a factory reset of the device is necessary even after a correct removal procedure on the hub? (the three button press, and the hub acknowledges the removal) I thought the reset was only necessary if there was an issue, or a force removal?
The case I was seeing was when the error message The Device is Already Scanned came up on the mobile app while scanning the QR code on a ZSE42 800LR Water Leak Sensor using Z-Wave Smart Start. If you’re not seeing that message, I’m probably talking about something else…
Yeah I’m using the PC so it sounds like a different issue. . I can’t do any of this stuff from the mobile app. Having everything isolated with VLANs is great for security, but it makes some things a huge hassle.
@Sara has anyone else noticed this, it’s really annoying to reboot after every removal. It’s not just the motion sensor, I started converting over more devices, and I’m rebooting after each ZSE44 for example this morning.
@OhioYJ - I am on the same Beta code 5.192.6 and am experiencing the same error/issue but under slightly different conditions.
I added a new LR device. Now I need to exclude a different device and can not. I get the same screen as you above when clicking ‘remove device’ then ‘zwave device’. Instead of the z-box going into exclusion mode I get this:
A reboot resolved that issue, however I had other issues removing a LR node. Where it said the device was removed, but it was still showing in the device list, yet disconnected. Force remove isn’t working because it says it isn’t on the broken device list, but it shows in the list as broken!? I pulled power to the device and waited to retry the force remove. Still can’t get the device to go away. Strange.
Yeah I noticed it’s triggered many ways. I also just can’t add two LR devices in a row. Hopefully it’s being worked as the app isn’t a viable solution for me unfortunately.
Well that is definitely new information. I can’t test the app, so I think everyone was under the impression the app was working. @BartekZooz , @Sara , this problem seems to be a bit larger than first thought.
@getoffmylawn@OhioYJ We have been testing the iOS mobile app (Z-Box beta version 5.192) since this issue was reported, and so far we have not been able to reproduce the inclusion/exclusion problem on the mobile app the same way we can on the web UI under certain conditions (webUI SmartStart + LR).
Here is the most recent test sequence we performed:
Added ZEN14 as an LR device using the mobile app
Added ZEN04 as an LR device using the mobile app
Removed ZEN04 using the web UI
Removed ZEN14 using the mobile app
This is the latest combination we tested, mixing the mobile app and web UI workflows.
@getoffmylawn Could you please share the exact step-by-step process you used to reproduce this issue, specifically in the mobile app? This will help us better isolate and diagnose the problem.
My apologies. I didn’t mean to derail this thread.
I’ve tested a ton of scenarios and can’t reproduce my exact issue again. I think my issue may be some sort of one-off with a Shelly Wave 1 device. ( see the my specific issue section below )
I did test your scenario above (but using a ZEN04 and a ZEN76) and I had the successes you mentioned. However - if I add just one more step - step 5, adding LR via web ui; I was then unable to add/remove devices via the web ui any more.
Added ZEN76 as an LR device using the mobile app
Added ZEN04 as an LR device using the mobile app
Removed ZEN04 using the web UI
Removed ZEN76 using the mobile app
Add ZEN76 as an LR device using the web UI
I believe this was the same scenario @OhioYJ had - where you add an LR device via web ui, and then can’t remove or add a device via the web ui any longer (until you reboot). However you seem to be able to continue to add/remove devices via the mobile app continually without issue, without rebooting.
Note: I think found an interesting detail for the removal at least… Instead of using the “Remove Device” button in the upper right of the devices screen, if I instead click the “Trash Can Icon” on the line for one of the nodes, then click “Exclusion Mode” I can continue to remove devices via the web ui without a reboot! In the console window you can see it go into exclusion mode. At that point I just put the device I want to remove in exclusion mode (three presses).
When it comes to adding new devices via the web ui at that point the ‘standard’ way is broken. But I found if you hand key the full DSK in the Zwave > Smart start screen, they will auto-add from the web ui, but unfortunately they join as non-LR.
My specific issue: (unsure if related)
I have a Shelly Wave 1 that won’t remove. The device was joined via LR via the mobile app. I then tried to remove it via the web ui. The event log says “Device has been removed from the other Z-Wave network.”
However it is still in the list.
I tried to do a force remove, and it says “Device was not found on the list of failing nodes, cannot be force removed. Please use learn mode (removing) as instructed in user manual.” But it’s been offline now for over a day. [physically powered off, too]
What’s crazy is I can RE-ADD it to the Z-box, as both LR and NON-LR (and remove it in either case) yet the original LR entry stays stuck in the device list. Almost like this one instance of the device is stuck in the database for some reason. It was this failed removal that happened both on the web ui and the mobile app, causing my statement above that confused the issues. At the time I thought this was any device, but it turned out to only be this one Shelly instance. Apologies!
Hey all! I wanted to provide a quick update here. We forwarded our findings to our development team, and they were able to replicate and pinpoint the issue. They’ve confirmed it is not about the Z-Wave chip blocking itself, and rather it is more of a cosmetic/refreshing issue in the Web UI. It will be fixed in the next beta firmware release.
Until the new firmware, you can do a hard refresh of the page (CTRL+F5) in the browser instead of rebooting the Z-Box. We’ve confirmed this works here as well.
