Can you post your z-wave details page?
1 Like
Z-Wave Radio Devices
Node Stats Status Device Class Device Security Route
| 0x0A (010) | PER: 0, RTT Avg: 1ms, LWR RSSI: 3dB | |||||
| Neighbors: 1, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Gate Big] | None | 01 -> 0A 100kbps | |||
| 0x0C (012) | PER: 0, RTT Avg: 1ms, LWR RSSI: 8dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Door House Front] | S2 Authenticated | 01 -> 0C 40kbps | |||
| 0x0D (013) | PER: 1, RTT Avg: 2ms, LWR RSSI: -9dB | |||||
| Neighbors: 1, Route Changes: 2 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Door House Back] | |||||
| S2 Authenticated | 01 -> 0D 40kbps | |||||
| 0x0E (014) | PER: 0, RTT Avg: 1ms, LWR RSSI: 0dB | |||||
| Neighbors: 1, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Hall] | |||||
| S2 Authenticated | 01 -> 0E 100kbps | |||||
| 0x0F (015) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | S2 Unauthenticated | |||
| 0x10 (016) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Heiman Technology Co., Ltd | [Smoke 1] | |||||
| None | 01 -> 0B -> 10 100kbps | |||||
| 0x13 (019) | PER: 3, RTT Avg: 1ms, LWR RSSI: 2dB | |||||
| Neighbors: 3, Route Changes: 3 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 1 Kitchen] | |||||
| S2 Authenticated | 01 -> 13 100kbps | |||||
| 0x15 (021) | PER: 0, RTT Avg: 1ms, LWR RSSI: -6dB | |||||
| Neighbors: 1, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Door Garage Front] | |||||
| S2 Authenticated | 01 -> 15 40kbps | |||||
| 0x16 (022) | PER: 8, RTT Avg: 1ms, LWR RSSI: -2dB | |||||
| Neighbors: 1, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 4 Hall] | |||||
| S2 Authenticated | 01 -> 16 100kbps | |||||
| 0x17 (023) | PER: 0, RTT Avg: 19ms, LWR RSSI: 20dB | |||||
| Neighbors: 1, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| AEON Labs | [Leaky Kitchen] | |||||
| None | 01 -> 0B -> 17 9.6kbps | |||||
| 0x18 (024) | PER: 0, RTT Avg: 1ms, LWR RSSI: 7dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Gate Small] | |||||
| S2 Authenticated | 01 -> 18 100kbps | |||||
| 0x19 (025) | PER: 1, RTT Avg: 1ms, LWR RSSI: -3dB | |||||
| Neighbors: 1, Route Changes: 2 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 7 Garage Front] | S2 Authenticated | 01 -> 19 40kbps | |||
| 0x1D (029) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | None | |||
| 0x1F (031) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | None | 01 -> 1C -> 1F 9.6kbps | ||
| 0x21 (033) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_BASIC_WALL_CONTROLLER | S2 Unauthenticated | 01 -> 1C -> 21 9.6kbps | ||
| 0x23 (035) | PER: 0, RTT Avg: 1ms, LWR RSSI: 14dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Living room 2] | S2 Authenticated | 01 -> 23 100kbps | |||
| 0x24 (036) | PER: 0, RTT Avg: 1ms, LWR RSSI: 0dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Kitchen 1] | S2 Authenticated | 01 -> 24 100kbps | |||
| 0x27 (039) | PER: 0, RTT Avg: 1ms, LWR RSSI: 28dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Living room 1] | S2 Authenticated | 01 -> 27 100kbps | |||
| 0x28 (040) | PER: 0, RTT Avg: 1ms, LWR RSSI: 4dB | |||||
| Neighbors: 3, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Toilet] | S2 Authenticated | 01 -> 28 100kbps | |||
| 0x29 (041) | PER: 0, RTT Avg: 8ms, LWR RSSI: 31dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Lounge 2] | S2 Authenticated | 01 -> 3A -> 29 40kbps | |||
| 0x2B (043) | PER: 4, RTT Avg: 4ms, LWR RSSI: 2dB | |||||
| Neighbors: 1, Route Changes: 2 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Window Pantry] | S2 Authenticated | 01 -> 3A -> 2B 40kbps | |||
| 0x2D (045) | PER: 0, RTT Avg: 1ms, LWR RSSI: -6dB | |||||
| Neighbors: 1, Route Changes: 2 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Door Kitchen] | S2 Authenticated | 01 -> 2D 40kbps | |||
| 0x2F (047) | PER: 3, RTT Avg: 5ms, LWR RSSI: -1dB | |||||
| Neighbors: 1, Route Changes: 2 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 6 Garage Rear] | S2 Authenticated | 01 -> 3A -> 2F 40kbps | |||
| 0x30 (048) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_BASIC_WALL_CONTROLLER | S2 Unauthenticated | 01 -> 1B -> 30 40kbps | ||
| 0x31 (049) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_BASIC_WALL_CONTROLLER | None | |||
| 0x33 (051) | PER: 96, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 11, Route Changes: 0 | OKRepair | SPECIFIC_TYPE_POWER_SWITCH_BINARY | ||||
| AEON Labs | [Immersion Heater] | S0 | ||||
| 0x35 (053) | PER: 0, RTT Avg: 5ms, LWR RSSI: 2dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Door Garage Rear] | S2 Authenticated | 01 -> 3A -> 35 40kbps | |||
| 0x39 (057) | PER: 4, RTT Avg: 1ms, LWR RSSI: 13dB | |||||
| Neighbors: 2, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 3 Living room] | S2 Authenticated | 01 -> 39 100kbps | |||
| 0x3A (058) | PER: 0, RTT Avg: 1ms, LWR RSSI: 1dB | |||||
| Neighbors: 4, Route Changes: 1 | OKRepair | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 5 Lounge] | S2 Authenticated | 01 -> 3A 100kbps | |||
| 0x3B (059) | PER: 0, RTT Avg: 1057ms, LWR RSSI: 18dB | |||||
| Neighbors: 3, Route Changes: 3 | OKRepair | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Motion 9 Barn] | S2 Authenticated | 01 -> 40 -> 3B 9.6kbps | |||
| 0x3C (060) | PER: 0, RTT Avg: 1ms, LWR RSSI: 4dB | |||||
| Neighbors: 4, Route Changes: 1 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Aeotec Limited | [Window Kitchen 2] | S2 Authenticated | 01 -> 3C 100kbps | |||
| 0x40 (064) | PER: 0, RTT Avg: 1ms, LWR RSSI: 7dB | |||||
| Neighbors: 8, Route Changes: 1 | OKRepair | SPECIFIC_TYPE_REPEATER_SLAVE_[SIC] | ||||
| Ring | [Ring Extender Garage] | S2 Authenticated | 01 -> 40 100kbps | |||
| 0x41 (065) | PER: 0, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 1, Route Changes: 0 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | None | 01 -> 41 40kbps | ||
| 0x42 (066) | PER: 1, RTT Avg: 3ms, LWR RSSI: 8dB | |||||
| Neighbors: 3, Route Changes: 3 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | ||||
| Shenzhen Neo Electronics Co., Ltd | [Window Living room 4] | S2 Authenticated | 01 -> 42 100kbps | |||
| 0x43 (067) | PER: 2, RTT Avg: ms, LWR RSSI: | |||||
| Neighbors: 2, Route Changes: 0 | OK | SPECIFIC_TYPE_NOTIFICATION_SENSOR | S2 Authenticated |
Thanks @rlithgow1 Hopefully the formatting is legible.
Still no idea what 0B, 1B and 1C are.
Also I have no idea what these 'SPECIFIC_TYPE_BASIC_WALL_CONTROLLER' are? Devices 0x21, 30 and 31. Two are connected with s2 and one with none.
I do have one RING chime pro (which I believe is a zwave repeater) in my home. However this isn't joined to the hub - is being a traditional Ring chime for the doorbell. Plus I read that repeaters do need to be joined to a hub to be seen/used as repeaters (and the chime has never been added to the hub).
Kind of hard to read. Can you post a screenshot?
@bobbyD - can you give @Creeps permission to post screenshots?
2 Likes
Done!
1 Like
Missing part.
So as an example here I'm filtering on 0x3a repeater which is a battery powered Neo 700 motion sensor (located in the lounge). It has 4 devices attached two of which are in the garage which is right next to the main powered ring range extender (gen2). Doesn't make much sense to me.
And like I've said no idea what the UNKNOWN repeaters are.
I'm no z-wave expert, but you have several devices that haven't paired correctly, and may be ghosts. You need to correct that first before proceeding.
There will be others who pitch in and guide you toward removing ghosts, but I'll tag them here: @csteele @danabw @erktrek @rlithgow1
2 Likes
which ones are the ghosts? i.e. how does one identify a 'ghost'
I do have an aeotec z wave stick so potentially the means to try and remove the offending devices. Just not sure which ones to remove. Still puzzled but the motion 5 sensor listed as a repeater. This is working okay (as a motion sensor) BTW
Looking at your Z-wave Radio Devices page, every device that has a “Dicover” button is a ghost (partially joined) device. I would exclude each of them, reboot the hub, and try to join them again.
1 Like
@Creeps I agree with @wayne.pirtle. You've got ghosts. If you hit discover and they're not coming up and finishing the inclusion, you should get a remove button. You should remove the ghosts. If you find you cannot, you have 2 options...
Option #1 (This usually works, but if it fails, you can use option 2): Find the device that made the ghost. Physically disconnect power. Shut down the hub from the settings menu and unplug from wall (not hub) for 5 mins and then power back up. Click refresh on that line until the remove button appears. Remove it. It may take a couple of button pushes and you may end up getting a force remove option. If not go to option 2. Repeat with all devices that are ghosts..
Option 2. Purchase a USB stick (You can get the zooz 700 on amazon) and follow this document to remove them.. Another thing I would recommend is re pair all your s2 devices with no security (leave only devices like locks and garage door with security enabled) Your mesh will be very happy.
4 Likes
Based on the details you are showing, it looks like you are having a mix of encrypted devices (S2) that may no be able to properly communicate with the hub, and they are possibly generating lots of simultaneous events that your radio may not be able to process, causing the entire mesh to go unresponsive at times. I suggest not only eliminating the ghosts, but also trying to minimize or completely eliminate the S2 encryptions.
S2 (S0) security is required for devices that allow access to your home, such as locks and garage door openers. But for devices such as sensors and bulbs, the encryption is optional. While many of the new devices support S2 security, some may be running outdated firmware. Generally, devices included with S0 or even newer S2 encryption will cause your mesh to slow down. Including devices without S2 or S0 security, is the easiest way to avoid Z-Wave network issues.
3 Likes
A post was split to a new topic: Are there any improvements in handling the S2 encryption in SDK 7.17.1 or 7.17.2?
thanks @bobbyD and @rlithgow1 I'm a network engineer (traditional switching, 802.11 wireless and firewalls) by day and the idea of any form of wireless communication without encryption freaks me out 
I don't want any tom dick or harry (no offence to those chaps) eavesdropping my bathroom motion sensor knowing that I've walked in for a pee. In all seriousness I guess its a balance of genuine risk and practicality. Fun weekend converting all my devices back to unencrypted then 
Means removing and re-adding I assume...sigh. Do you chaps remove them from their associated rules before removing? Seems like the clean way but does take an age what with so many device and rules.
So there's no instance of a an attacker using these unencrypted communications to compromise the hub, which obviously then has a connection to the wider ethernet network?
I've done a bit of reading on the zwave mesh and its still a little unclear to me what happens in a mesh/repeater environment. It seems repeaters with no encryption enabled can repeat non-encrypted message and encrypted S0/S2 messages, correct? And vice versa. So again I should setup things like my RING extender as unencrypted i.e. they'd still be able to repeat my S2 door lock (when I get one)?
Much of my stuff is a little spread out (in sheds, garages etc) so I've been moving as much as I can to gen7 devices. It sounds like having a mix of gen5 and gen7 devices can reduce the benefits of a pure gen7 network. Is this true? My mind is reverting back to the problem of having 802.11b clients on ones fancy 802.11ax wifi network - you don't want this.
hi @rlithgow1 when I hit discover the page refreshes but nothing changes so I guess of screwed. Need a zstick style removal.
Okay so I have no idea what or where these ghosts have come from. Okay so in the past there have been a couple of aborted join attempts... the C7 saying 'device xyz found' and then going no further. In those instance I just get closer to the hub try again and most of the time the device joins fine. I assume this could be were the ghost appears. In this case I no idea which of the now working fine devices created which ghost entry. As I say to my knowledge all my devices are working fine.
Equally in this case I assume I can just remove the ghost entry using the zstick and it would attempt to rejoin as now has a working entry?
This is exactly what creates a ghost....
No, you would remove the ghost(s) and be done with it. If you still have problematic devices that you are having problems controlling, and exclusion and inclusion may be warranted. As previously stated, except for door locks and garage door openers, exclude and reinclude those devices WITHOUT security. Your mesh will happier... Your hub will perform much better,.
I'm a network engineer (30+ years) and do high end network security. That said, turn it off. Honestly, if someone is close enough to sniff your z-wave mesh, they are right outside your home and can watch what lights you are turning on via your windows. Breaking into houses is typically a crime of opportunity. If they want in they're going to break a window not try to sniff your HA network. Then again, if you have several hundred thousand in cash in a safe bolted to the concrete in your basement and it requires an Ocean's 11 style crew, then maybe you'd benefit, but even if you did, likely it would be a home invasion where you wouldn't get to hit an alarm anyway... So honestly, locks/garage doors yes, everything else no... even the dev's will pretty much tell you that. (and avoid s0 when ever possible, it's the worst)
4 Likes
LOL. Thanks for the advice.
Glad I paid the extra now for all those fancy S2 capable [cough] devices.
The only thing worth pinching from my house would be the blooming HA devices anyway. Too much of my hard earned cash wrapped up in this cr@p.
2 Likes
Said as I just pushed the buy button on an IoTawata unit 
1 Like
thought about it but my two aeon ver 5 are working fine.. one for whole house and one for the dryer.
