-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too much PacketInvalid
logspam
#209
Comments
any update on this? |
You can disable these via HA's configuration.yaml file: logger:
logs:
ramses_tx.transport: error Or similar (I have written this answer from memory). I will endeavour to remove this logspam when I next have a chance to throw another release. You should look at why you're getting so many of these errors. |
I'll try to disable them in the logger as suggested. |
It's a fair question, but - like your original question in the first post - are more user support questions than a bug in the code. Please ask again, in the community forum: https://community.home-assistant.io/t/honeywell-ch-dhw-via-rf-evohome-sundial-hometronics-chronotherm/151584/4583 This issue has been raised there before - likely poor reception / similar. Good luck. I will leave this issue open to remind me to reduce the log spam (or not). |
I have the following two errors in the HA log (amongst others - but these are the most common)
Logger: ramses_tx.protocol_fsm
Source: runner.py:189
First occurred: 21:16:32 (16 occurrences)
Last logged: 21:17:08
TOUT.. = : echo_timeout=0.5
TOUT.. = : echo_timeout=0.5
TOUT.. = : echo_timeout=1.0
TOUT.. = : echo_timeout=0.5
TOUT.. = : echo_timeout=0.5
Logger: ramses_tx.transport
Source: runner.py:189
First occurred: 21:16:32 (17 occurrences)
Last logged: 21:17:08
000 :073254 01:017166 --:------ 000A000 RQ --- 18:073254 01:017166 --:------ 000A 001 04 < PacketInvalid(Bad frame: invalid structure: >>>:073254 01:017166 --:------ 000A000 RQ --- 18:073254 01:017166 --:------ 000A 001 04<<<)
000 RQ --- 18:073254 01:017-- 0004 002 0400 < PacketInvalid(Bad frame: invalid structure: >>>RQ --- 18:073254 01:017-- 0004 002 0400<<<)
00-- 18:073254 01:109777 --:------ 2349 001 02 < PacketInvalid(Bad frame: invalid structure: >>> 18:073254 01:109777 --:------ 2349 001 02<<<)
0RP --- 01:109777 02070800FFFFFF < PacketInvalid(Bad frame: invalid structure: >>>--- 01:109777 02070800FFFFFF<<<)
087 I 036 37:045374 --:--4 31D9 017 00063C0020202020202020202020202000 < PacketInvalid(Bad frame: invalid structure: >>> I 036 37:045374 --:--4 31D9 017 00063C0020202020202020202020202000<<<)
Is there any real error here or a way to get them out of the logs? It's really annoying to see these errors continuously.
The text was updated successfully, but these errors were encountered: