There is one zwave mesh change that I noticed a few months ago.
It involves the aeon 6 plugin switch.
Previously I could place them anywhere.
Recently there seems to be a change, such that if I use more than on my network, their performance is horrible and it messes with the entire zwave mesh.
My point is, there were zwave repair errors that would not go away, removing the second aeon 6 plugin switch and the zwave repair errors went away.
Is there any way you can look at these device ID’s and tell me what you guys see on your end that I can’t with the typical hub event logs? I won’t have access to a zwave stick and tools for some time, so I’m hoping ST can shine some light as to why I keep seeing large blocks of zwave devices do this all at the same time:
The devices in this block of activity vary in terms of distance to the hub (they’re spread across all areas of my home, literally corner to corner). They’re all GE switches, and the model numbers are mostly the 4xxxx series, with a few 1xxxx series (including Master Bedroom Fan [25]).
I don’t seem to be impacted that I’ve noticed, but I’d like to track down root cause if possible.
Yes. the Arrival Sensor DTH is for the original kickstarter SmartThings arrival sensor (the one that is egg shaped). It used mostly manufacturer specific clusters for its communications and has been running locally forever. The Arrival Sensor HA DTH is for the more recent more rectangular one (there are a couple of models of these), and this is just moving local now. Each device should automatically pair with the correct DTH. In terms of functionality, they are nearly identical, but in terms of code support they are different due to the manufacturer specific stuff for the old presence sensor.