I have a Sonoff mini switch on my system for quite a while. Now for some reason I see reference to EP01 device whenever the switch is reference in the logs. I have the type set to Nue Zigbee Switch because the default one for that switch keeps putting info in the logs every 6 seconds. What is this EP01, do I need it, how can i get rid of it, and should I ?
Generally EP01 is the first( sometimes the only) endpoint of the switch/outlet.
The Nue switches this driver was written for come in 1- to 4-switch varieties (as one example: search the web for "HGZB-42" to find the 2-switch model). These are indeed exposed as different Zigbee endpoints, and the post above is therefore likely the explanation for why you're seeing what you're seeing.
Why are you using this driver, and what is the "default one"? The specific driver name and specific behavior you're seeing might be helpful to identify if there is a problem. And keep in mind that eliminating a log entry does not always mean the underlying behavior was changed if that is a concern.
I was using the "Generic Zigbee Driver" and I had Enable DescriptionText logging on because I wanted to monitor its behavior, but it was logging "Relay is on [physical]" entries every 4 minutes! I saw a thread somewhere here that had the same logging issue but solved it by switching to the Nue driver.
I was just puzzled about seeing the EP01 thing in the logs because I never had heard of "endpoints" before.
What must be happening is that your device is sending data to the hub that often. It sends the event for processing whenever this happens, but the platform will filter "duplicate" events (where the value doesn't change) by default (e.g., so it won't trigger apps unless the app elects to ignore the filter). The descriptionText logging writes this whenever it happens, regardless of the current value.
If the Nue driver you're using creates a child device, it looks like the Neu driver checks the value before sending the event or logging. It doesn't stop the data from actually being sent to the hub in case Zigbee traffic is your concern; it just stops that particular log entry (and event, so it affects "Last Activity At," one reason some people cared on the Generic Zigbee Outlet driver I assume you mean).
A similar check for just the logging could be added to this driver, though it again won't do anything about the actual traffic, just the log entry. The device might be odd for sending this ever few minutes without an actual change, as the driver configures it the same as any other device using this driver, a 0xFFFE (a bit over 18 hours) maximum time between reports if no change. A "Configure" might help if you haven't tried that already, otherwise the device just isn't doing that for some reason.
Of course, no reason to switch if you do prefer this driver -- just a bit odd.
