Skip to content
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

ERROR messagePump - unexpected exception #340

Open
garyak opened this issue Aug 31, 2024 · 4 comments · May be fixed by PeteRager/lennoxs30api#85
Open

ERROR messagePump - unexpected exception #340

garyak opened this issue Aug 31, 2024 · 4 comments · May be fixed by PeteRager/lennoxs30api#85

Comments

@garyak
Copy link

garyak commented Aug 31, 2024

Describe the bug
Seen in HA log. No clear correlation with HVAC activity.

Screenshots/Logs
If applicable, add screenshots to help explain your problem.

2024-08-29 20:25:57.409 ERROR (MainThread) [lennoxs30api.s30api_async] messagePump - unexpected exception - please raise an issue to track
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/lennoxs30api/s30api_async.py", line 706, in messagePump
    resp_json = json.loads(resp_txt)
                ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/decoder.py", line 353, in raw_decode
    obj, end = self.scan_once(s, idx)
               ^^^^^^^^^^^^^^^^^^^^^^
json.decoder.JSONDecodeError: Expecting ',' delimiter: line 1 column 1976 (char 1975)

Version

  • Home Assistant:
  • Core 2024.8.3
  • Supervisor 2024.08.0
  • Operating System 13.1
  • Frontend 20240809.0
  • This Integration: 2024.8.0

**Integration Configuration **

  • Cloud or Local Connection: Local
  • Inverter or Sensor Diagnostics Enabled: No
@PeteRager
Copy link
Owner

It looks like the message sent from the s30 was unable to be parsed. Unfortunately, the error handling does not log the message text that failed to parse and we don't have info on the root cause. That need to be enhanced so we can see what is in the message that has improper formatting.

What version firmware is on the S30s. Easiest place to find is on the s30 device for the integration.

IMG_3169

@garyak
Copy link
Author

garyak commented Aug 31, 2024

Two s30's

  • 3.81.207 - South
  • 3.81.213 - North

@PeteRager
Copy link
Owner

This is a strange error. Has this been reoccuring? I'm going to update the API to log the text of the message that fails to decode.

@garyak
Copy link
Author

garyak commented Nov 11, 2024

This has not been a reoccurring error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants