Ok, with 7 devices and 12 hours, basically your mesh is being hammered by route discovery packets non-stop. I dont need to do the math again. No wonder its slow. *They might be route changing due to whatever the well pump is spamming out.
I would be inclined to set Paramater 2 to value 2, which will report the energy (kWh) daily. There seems to be no adjusting of the power reporting.
You should turn on debug logging for that device and see if anything gets generated in the logs, maybe some incoming messages will go into debug logs. It might look like gibberish to you but it will make sense to me. Might help to figure out what it keeps chatting about.
Yup. That's it. I have two of them. One on my 220v clothes dryer, the other on the 220v well pump. Not a bit of trouble from the clothes dryer one -- it's about 20' away from the C7, on the same floor.
The Well Pump one is at the far reach of the house -- downstairs, through the floor and two walls. Going to work on getting better signal, etc down there -- but I have three Dome water shutoff thingies, and they are just fine -- within 5' of the problem Well Pump 40-amp switch.
And yes, for the power reporting -- I have to poll it once a minute. When the well pump runs, it runs for about 2-3 minutes -- so that is sufficient to detect it's on. The whole point was to detect if the well pump "ran too long" so I don't burn out a very expensive deep-well pump
So you are polling it every minute, constantly?
Doesn't it report power on its own when it changes?
EDIT: Actually looks like it does not report automatically... thats lame.
Your polling is probably the source of ALL the problems in the network.
When you are polling it, it is probably requesting ALL 4 values as well, instead of just the one you need!
That could be fixed with a custom driver. I wonder if someone has made one already we could tweak it.
Completely concur on it's lame. The polling is the only option to get power readings (per a lots of community and google)
That said, the other one -- the Clothes Washer 40-amp -- is also polled every minute (for WAF - "the dryer has started/finished") -- and doesn't have these issues of flooding the Z-wave net.
Yeah its polling everything.
Its not chatty, you are asking it for info!
I think a good test might be to disable the polling on both of those device for a short while to see if it makes any improvement?
Also, if there is a custom driver for this device already, a custom command could be added that only requests the power value instead of everything! It may even work with the Power metering plug driver I have already created.
If you find a custom driver that works for it, I would be happy to modify it to add the custom command.
You could try this driver as well if you are feeling adventurous. [DRIVER] Zooz Smart Plugs Advanced (ZEN04 / ZEN05 / ZEN14 / ZEN15) I suspect it will work, and I could make a custom version for this 40 amp switch with a command that only requests the power reading. That would cut down the traffic 4x.
Have "stopped" and "paused" that rule that appears to be "stuck" in polling/repeat.
Holy crap. My Z-wave net has dramatically gotten quieter. Been looking at that logic in that rule causing the problem - - can't figure out why it got stuck "repeating" -- says do it just 2 times.
I went and checked the "events" for the three triggers -- nope, nothing abnormal -- not like any of them were triggering constantly.
Stay tuned -- have rebooted hub -- to reset all the counters -- it's looking a LOT better.
your asking it to refresh 2 times in less than a second then a further 2 times 1 second apart. Your asking it to do that every time the trigger events happen. I would just get rid of the repeat and add a elapse time of a few seconds above the 1st refresh.
Yea, I toned it down to just a single poll -- no repeat. But don't understand how it got "stuck" repeating constantly. But, as of now 8ish hours -- with this change -- we're still "happy" in Z-wave land....
New simple rule -- based on a new "vibration/accelleration" sensor I put on the incoming well 1" pipe. Works great to detect the inrush of water from the well.
Here's the latest Z-wave details. Last full shutdown, pull power, reboot - was about 24 hours ago.
(This cut/paste is from the earlier-in-this-thread-recommended ShareX "scrolling capture' tool -- it looks darned small to me - not sure how to make it pretty)
Yup. I plan to stay hands-off for now and see how it goes. My live Z-wave logs look pretty sane now as well -- a nice slow scroll, not constant flooding....
I'm assuming some values, like "route" are the latest route.
As an aside -- not clear on Neighbors, RTT, RSSI, etc -- are they representing the "most recent" value (and would go up/down?) -- or instead, are they the "max/worse".
RTT am pretty sure is the "max seen" based on empirical observations.
PER, I get, by definition is an incrementing value. So is route-changes.
I'm going to differ by just a little bit.. your device #16 looks like a half joined device and that you had to try 5 more times to get it to join as "WATER - Well..."
Both rows show the same type of device, that Discover button means the join cycle took too long and it only partially completed. Ideally, you'd see that, click discover then wake the ZWave device to allow the exchange to finish... but I'm guessing you gave up and tried a few more times.
I'd treat it like a Ghost and get rid of it. Click Repair and confirm it can't find the device, then slowly click Refresh til the Remove button appears. Click Remove and then come back to this page in 15 mins... allowing the internal processes of the hub/radio to settle.
