OK thanks. I've only ever had the one. I include the Z stick when I want to include an older 500 device without security and exclude it again afterwards. I can see from their addresses when this was. I was having a complete nightmare including/excluding an Aeotec switch and the "new" virtual nodes appeared at that time. I'm wondering as I was having such a chew on whether there is something I could have clicked in the PC Controller software that could have caused them to be added again (I maybe used the NWI button rather than add)
Should only have 4, but I also have the same setup as you (only one hub) and I also have 8, one of the devs said there was probably some sort of corruption before the zwave sdk/firmware was updated to fix those issues and the hub created new ones (72-75 for me). Doesnt seems to be hurting anything besides annoying me.
This is weird, a few months ago, an Aeotec bulb suddenly became unresponsive, but I was not able to exclude it by any means. Also it was getting really, really hot.
After doing a factory reset, there was an unnamed device left, that the hub had not been able to keep on the failed node list.
And if I do remember correctly, one on the new virtual nodes took over it's ID, 85.
Though, using Z-Stick I was able to remove a ghost device, which didn't seem to hurt.
A week before, the same happened to an Aeotec D/W-Sensor 7, but I was able to get rid of it without having to use the Z-Stick.
It could be, that another new virtual node took over it's former ID, 33, since there's a gap in my node list.
Doesn't seem to make much sense, right?
Another question, does anyone know if there's a way to decrypt the S2-secured packets, I have no idea where to get the keys?
Edit found this as an answer:
I normally hit the "Update" (not "Neighbors Update") button on occasion to refresh the stick info with the gateway. Not sure if that is the issue though.
Yeah you found my post... The S2 is a pain for sniffing. Once you get the Nonce it works while you keep it open but I think once you close the software it forgets it. You also have to get it for each device. Also if you save the trace and then open it later, it is not saved decrypted. So if you want to retain any info take screenshots.
Don't have a PC-Controller anymore, since my only stick is now busy with zniffing.
Looks like I need to get another one.
Yeah, it was the second hit when searching for "Zniffer".
Actually, I don't have many S2-devices that support Supervision CC anymore, so I keep on letting it zniff and lurk around for a matching packet. Not that important to me, just for educational purposes.
Found some more inexplicable behaviour, maybe one of you guys have an idea how to rate this?
As you can see, the hub keeps spamming wake-up beams, also to targets that are non-FLiRS or don't even exist.
The weirdest thing is node-ID 233, isn't the maximum node-count at 232?
Also, my highest node-ID is at 96, so why calling 164 and 170?
And why tries the hub to wake up ID2?
Sorry for being that persistent, but may I ask you guys to have a look at this, am I the only one that thinks that this behaviour is not sane?
Video download size about 14MB.
Edit says that I probably had been able to narrow down one of the issues.
All of my MS6 kept spamming battery status reports and explorer frames, they are USB-powered, though and had never seen a battery.
But still, they all seemed to behave like battery powered devices, I saw a lot of wake up notifications in rapid successions from all of them, especially the one in my livingroom, which is the busiest of them all.
So I re-included this one, et voila, no more battery spamming anymore, even the explorer frames are gone.
My theory is that, during an update with same hand-made firmware, all MS6's read-only parameter #9 had been set to battery-powered.
Tagging @bcopeland to verify that my findings make any sense.
Also, may I ask you to take a look at my video and tell me, what causes the hub to continously ask node 8 , which had been my livingroom sensor, to find all nodes in range.
Could this behaviour probably degrade my Z-Wave performance?
Thanks in advance for your efforts.
