I’ve got a node (16) that’s bogging things down. I’m not sure how to read my log and figure out what’s wrong or how to fix it.
Link to pastebin log:
https://paste.ubuntu.com/p/QFMmvx2Yzb/
need more info. what type of device? what effects do you see when it’s made part of the network?
Ugh, I’m sorry. It’s an Aeotec Nano Switch. It is part of the network already - has been for days. I tried disabling the entity, but the log entries didn’t stop so I figured that wasn’t the answer.
Maybe a wrong reporting interval (default 600 seconds) or Watt/percentage threshold (default 25/5 out of the top of my head)?
Heh, I have no idea, or what to do about it if you’re correct.
The device is sending a Hail command, which causes OZW to refresh all of the “dynamic” values.
What happens if you set config parameter “Notification report association group 1” (number 80) to “Basic”?
I found where to do that. After I press “Set Configuration Parameter” do I click the switch, restart HA, reboot host, any of those?
You shouldn’t need to restart anything. Just set the parameter.
Sigh. Went to “Entities” and it says “This device is currently unavailable”.
Do you mean “entity unavailable”? Which entity/entities? Any difference in the OZW_Log.txt?
Well… Here’s what it looks like:
All other entities for the device don’t have that red text.
Furnace Light Alarm Level
Furnace Light Alarm Type
Furnace Light Heat
Furnace Light SourceNodeId
Furnace Lightswitch
I don’t even NEED any of those entities - I just want on/off. And it WAS working…
Anyway -
And the log:
https://paste.ubuntu.com/p/VyC4wq9QCf/
The logs look much worse actually, the switch is sending way too many messages. What was the previous configuration setting? I would try setting “Hail CC when using the external switch to switch the loads” instead, if that wasn’t it.
While there are a bunch of options, that isn’t one of them.
I DO use a dumb (single pole/single throw) connected to the switch. Not sure if that matters.
I’m still talking about parameter “Notification report association group 1” (80). It has 4 options, the last one being “Hail CC when using the external switch to switch the loads”.
For comparison, SmartThings will configure the device to use the “Basic” setting as I first suggested. Not sure why that isn’t working for you, either a bad device or a problem with OZW.
Ohhh, misunderstood! On it! I’ll give it a few, then check.
I’m thinking - you got it!
2021-01-19 16:31:59.291 Detail, Node019, Notification: ValueChanged
2021-01-19 16:32:44.656 Detail, Node016, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x10, 0x03, 0x20, 0x03, 0xff, 0x3d
2021-01-19 16:32:44.656 Detail,
2021-01-19 16:32:44.656 Info, Node016, Received Basic report from node 16: level=255
2021-01-19 16:32:44.656 Detail, Node016, Queuing (Send) SwitchBinaryCmd_Get (Node=16): 0x01, 0x09, 0x00, 0x13, 0x10, 0x02, 0x25, 0x02, 0x25, 0x61, 0x94
2021-01-19 16:32:44.656 Detail,
2021-01-19 16:32:44.656 Info, Node016, Sending (Send) message (Callback ID=0x61, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=16): 0x01, 0x09, 0x00, 0x13, 0x10, 0x02, 0x25, 0x02, 0x25, 0x61, 0x94
2021-01-19 16:32:44.662 Detail, Node016, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2021-01-19 16:32:44.662 Detail, Node016, ZW_SEND_DATA delivered to Z-Wave stack
2021-01-19 16:32:44.722 Detail, Node016, Received: 0x01, 0x05, 0x00, 0x13, 0x61, 0x00, 0x88
2021-01-19 16:32:44.722 Detail, Node016, ZW_SEND_DATA Request with callback ID 0x61 received (expected 0x61)
2021-01-19 16:32:44.722 Info, Node016, Request RTT 66 Average Request RTT 77
2021-01-19 16:32:44.722 Detail, Expected callbackId was received
2021-01-19 16:32:44.741 Detail, Node016, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x10, 0x03, 0x25, 0x03, 0xff, 0x38
2021-01-19 16:32:44.741 Detail,
2021-01-19 16:32:44.741 Info, Node016, Response RTT 84 Average Response RTT 64
2021-01-19 16:32:44.741 Info, Node016, Received SwitchBinary report from node 16: level=On
2021-01-19 16:32:44.741 Detail, Node016, Refreshed Value: old value=true, new value=true, type=bool
2021-01-19 16:32:44.741 Detail, Node016, Changes to this value are not verified
2021-01-19 16:32:44.741 Detail, Node016, Expected reply and command class was received
2021-01-19 16:32:44.741 Detail, Node016, Message transaction complete
2021-01-19 16:32:44.741 Detail,
2021-01-19 16:32:44.741 Detail, Node016, Removing current message
2021-01-19 16:32:44.741 Detail, Node016, Notification: ValueChanged
2021-01-19 16:32:44.758 Detail, Node016, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x10, 0x03, 0x25, 0x03, 0xff, 0x38
2021-01-19 16:32:44.758 Detail,
2021-01-19 16:32:44.758 Info, Node016, Received SwitchBinary report from node 16: level=On
2021-01-19 16:32:44.759 Detail, Node016, Refreshed Value: old value=true, new value=true, type=bool
2021-01-19 16:32:44.759 Detail, Node016, Changes to this value are not verified
2021-01-19 16:32:44.759 Detail, Node016, Notification: ValueChanged
2021-01-19 16:32:51.706 Detail, Node019, Received: 0x01, 0x11, 0x00, 0x04, 0x00, 0x13, 0x0b, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x16, 0x00, 0x00, 0x00, 0x69
2021-01-19 16:32:51.706 Detail,
2021-01-19 16:32:51.706 Info, Node019, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:22, status=255
2021-01-19 16:32:51.706 Detail, Node019, Refreshed Value: old value=0, new value=0, type=byte
2021-01-19 16:32:51.706 Detail, Node019, Changes to this value are not verified
2021-01-19 16:32:51.706 Detail, Node019, Refreshed Value: old value=0, new value=0, type=byte
This is the only Node 16 mention in the past few minutes. Does it look right?
yeah go over your zwave configuration parameters for that device. turn off anything you don’t need and set the polling to say 3 minutes. should quiet it down a bunch
That’s not really what I was expecting, but if the switch and everything else is working fine, then I guess it’s good. 
Heh, it is, but I have to ask: What WERE you expecting???