search

zigpy / zigpy-deconz

A library which communicates with Deconz radios for zigpy
GNU General Public License v3.0
87 stars 20 forks source link

Change log level to debug for unexpected transmit #253

Closed mbo18 closed 5 months ago

mbo18 commented 7 months ago

Change log level for unexpected transmit to debug. I don’t really know why this is useful for users. For example I have in my log multiple times per day:

Logger: zigpy_deconz.zigbee.application
Source: runner.py:189
First occurred: 00:26:55 (3 occurrences)
Last logged: 08:16:49

Unexpected transmit confirm for request id 11, Status: TXStatus.SUCCESS
Unexpected transmit confirm for request id 175, Status: TXStatus.SUCCESS
Unexpected transmit confirm for request id 163, Status: TXStatus.SUCCESS

Remark: it is not possible to filter these logs in HA with:

logger:
  default: warning
  logs:
    zigpy_deconz.zigbee.application: error

And I don’t know why.

Hedda commented 7 months ago

FYI, these community forum threads reported similar warning messages being logged when using ConBee II (ConBee 2) in ZHA:

WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id #, Status: TXStatus.SUCCESS
WARNING (MainThread) [zigpy_deconz.api] Duplicate or delayed response for 0x:5d sequence

Hoever I noted that most of them also mention that they have additional warnings in the logs that might bring more context?

mbo18 commented 7 months ago

I also have additional messages but I have removed them from the log with:

logger:
  default: warning
  logs:
    zigpy_deconz.api: error
    zigpy.zcl: error

This one is the only one that can’t be removed using the same method. I’m wondering how these messages can help as warnings as nearly no one can understand them. Maybe it helps developers but then it might be better to put them in error or debug. I’m using a conbee2 with a USB extension cable without issues since some years now