BE469 Duplicate Status Messages

I know, I know, there's about a million BE469 Threads. It has to be one of the less reliable devices, at least on hubitat. But, it worked on Smart Things and served as the center of my home automations, enabling different functions as we left the house, returned, etc. It has great potential, but for some reason, it and hubitat just don't want to get along.

I am running one of the BE469ZP, the newer ones that should by most rights work with Hubitat.

As you can see below, I seem to be getting duplicate events. Below I triggered just one lock and unlock cycle.

image

These duplicate errors happen all the time. how may times they are repeated is somewhat variable. But when I subscribe to these events in webcore, sure enough I get multiple push notifications. You'll also note that these take upto 5 or more seconds to fully process.

These really make any automations difficult. And thats not even scratching the surface with trying to automate how the lock was unlocked (thumbscrew or keypad) which also doesn't work.

Does anyone have any ideas on what to do to get these working better? I've tried some of the other rules, apps, etc, but with the duplicate events, these are just as confused as anything else.

Thanks in advance:

PS, for kicks, I've also run this with debug logging turned on:


What's the RTT look like on it? The only time I've seen similar is with ghosts in the mesh so that it's trying to send twice when one isn't there. Can you post a screen shot of your z-wave details page?

2 Likes

I would say that, or maybe just a weak mesh overall.

+1

1 Like

Yeah, I've got at least one ghost I guess:




Possibly 4. Also, several S0 paired devices that should optimally be paired with no security.

1 Like

At least. All the ones with Discover, and potentially others with no routing in the last column.

The "notification sensors" (4-in one or multi sensors) are typically the worst, they send lots of reports in the first place, especially if configured wrong for too often temp, motion, or humidity changes. Then add the triple traffic penalty of S0, and you are asking for mesh trouble.

Power reporting devices are also a cause for crashing the mesh if configured in incorrectly.

And is that a Zooz Zen25 on 0x2B? Those are known offenders to be very damaging to Zwave mesh.

2 Likes

You've got 4. Get rid of those and see how things are. As @neonturbo pointed out, re pair the zooz sensors with no security. You may need to do that with a usb stick paired as a secondary controller

2 Likes

So is the only way to clean out ghosts the way using a usb stick?

Power down (actually disconnect the power) to the devices that created the ghosts. Shutdown the hub from the settings menu. Unplug at the wall (not the hub) for 20 mins. Bring back up. Start removing the ghosts..