Okay I am about to give up

S0 also generates a lot more traffic than no security at all. Unless you feel you really need security on this device (like it somehow controls a security gate or door or something) I'd suggest unpairing it and re-pairing it without S0. Unfortunately, I think the only way to do this is with the assistance of a secondary controller (USB stick or the like).

2 Likes

This ^^^ If the driver doesn't have an effective option to control power/status reporting, the device will continue to spam that data. And if it's S0 security that adds additional traffic as noted.

1 Like

If this is the Gen5 you may be able to change the reporting parameters (see page #7 of the pdf linked below) with the "Basic Z-Wave Tool" driver.

https://manuals.plus/wp-content/uploads/2021/08/ES-Heavy-Duty-Smart-Switch-Gen5-V3.26.pdf

The Basic Z-Wave tool can be installed via the HPM or here:

Install the driver, temporarily change your device to it then enter the appropriate parameter and value.. then change your driver back. Do not hit configure or you might wipe out your changes.

2 Likes

50 extra points for Hufflepuff for you thinking of this. :slight_smile:

1 Like

Do I use the hex or decimal for the parameter number?

decimal is what I've always used

1 Like

Yeah the parameter report (which shows up in the logs) is in decimal. It's been a while since I used it but I agree with @danabw.

edit: Do run the parameter report so you can see the parameter sizes etc.. and see if it matches up with the docs.

2 Likes

Here's my report for an old Aeotec nano relay..

I do not know how to make this one stop.

What driver is device 1328 using? Built-in drivers and most community drivers will stop debug logging after 30 minutes. If it’s a HE driver then a quick message to support usually gets it addressed in the next release, if it’s a community driver often times the developer will address it.

3 Likes

The driver is [Release] Aeotec Heavy Duty Smart Switch, which apparently is no longer supported. However, I believe I was able to make parameter changes that stopped the mesh chatter. Thanks everyone.

2 Likes

Give me a few minutes to fire up my laptop and I’ll take a quick trip through the code to see if I can spot an errant log.debug.

1 Like

Not seeing a skip debug message in that code, sorry.

2 Likes