You are placing the device and hub within inches of each other when excluding?
@jkp makes an excellent point.
Frequently, when you are rebuilding a network, your end devices will lose their usual paths to the hub because other devices that would typically pass along your messages are themselves temporarily offline. So It can definitely be a good idea when trying General exclusion to make sure that the end device is close to the hub that is issuing the general exclusion command. If the exclusion is timing out in the app, it may just be a matter of not being able to get messages back-and-forth. (or it could again be an issue with sequence or timing, so that the end device has left its âready for exclusionâ state before the hub has issued the exclusion command.)
I wouldnât say inches, though. Because zwave spreads, and these are Omni directional antenna, you often get the best reception about 10 feet away from the hub. And that will avoid potential interference from any of the other radios in the hub. When I was a field tech, I typically plugged the device into an outlet across the room on the opposite wall from the hub.
(the exception to that is zwave locks, which have to be within âwhisper distanceâ to exchange a security key: with those I put them about 3 feet away.)
I appreciate from your side I probably appear like a scatterbrain, but I assure you I am following the procedure. Again, I will try it again, but I am dubious.
Yes, it is definitely right near the hub. I measured and itâs about 3 feet away. Nothing in its way straight shot.
1 Like
When you start the exclude, do you see the hub lights blinking?
A few releases back there was an issue with the mobile apps not actually starting an include/exclude on the hub when requested. Thatâs been fixed but just checking.
In the mobile app, if a device exclude is recieved by the hub, youâll always see â1 device excluded.â.
Triggering an exclude from the advanced web app doesnât work for me very often as it seems to run the exclusion for only 15 seconds or so. The mobile app runs it for about a minute.
1 Like
Thatâs a good question and you know what I did look at that and I didnât see it blinking so I wondered if maybe just a new glitch was making that light not blink on the hub. Now what?
1 Like
Open An official support ticket about a device which is officially supported by smartthings. One of your GE/Enbrighten switches would be fine for this.
1 Like
I would -
- Close the app from my phone
- Reboot the hub
- When the hub comes back on line, open the fresh copy of the app and try to start the exclude.
If the hub isnât blinking while its supposedly in the exclusion mode, youâve easily repeated the issue and support should be able to diagnose.
1 Like
Just saw this thread, and for what it is worth I tried to exclude a Zooz ZSE41 yesterday and it would not exclude or force delete, but when I closed the app and went back in it was gone.
1 Like
Closed the app as in signed out and closed or just closed?
The current production hub firmware version for V2/V3 hubs is in fact 000.048.00005. It updates automatically according to the schedule set by ST.
Zwave info tho. Aeotec hub vs the old (offline) hub. Iâve no idea what these numbers mean. Assuming theyâre some sort of firmware for zwave?? Looks like old hub had a later release?
DSK is the Device Specific Key. Its the security key for the zwave radio. Each zwave plus device has a unique key. Google is your friend for researching.
1 Like
Thanks. Very kind.
1 Like
Iâm having issues with the iOS app not starting zwave exclusion. The led on the front of the hub doesnât double blink to indicate exclusion is running. Starting exclusion using the advanced users site starts exclusion successfully as indicated by the led double blinking.
2 Likes
Hey Jimmy. Forgive my ignorance which is the website youâre referring to? The new st site? https://my.smartthings.com/advanced ?
1 Like
yep⌠that is the site⌠go to the hubs section, tap on your hub name to find that utility
1 Like
SUCCESS. Using the website is the fix.
THANK YOU EVERYONE!!
3 Likes