Skip to content

Discovered two new error codes#265

Open
Guzz-T wants to merge 1 commit intoBouni:mainfrom
Guzz-T:try/errorcodes
Open

Discovered two new error codes#265
Guzz-T wants to merge 1 commit intoBouni:mainfrom
Guzz-T:try/errorcodes

Conversation

@Guzz-T
Copy link
Contributor

@Guzz-T Guzz-T commented Mar 17, 2026

image

@github-actions
Copy link

Coverage

Coverage Report
FileStmtsMissCoverMissing
luxtronik
   __main__.py25250%3–66
   datatypes.py450199%147
   discover.py58198%63
luxtronik/cfi
   interface.py175398%167–168, 256
luxtronik/definitions
   __init__.py208199%216
luxtronik/scripts
   __init__.py35586%7–16, 51
   discover_shi.py60600%8–98
   dump_cfi.py14657%18–25, 29
   dump_shi.py15660%21–28, 32
   performance_shi.py63630%7–89
   update_screen.py1058222%6, 20–41, 46–48, 51–61, 64, 70–75, 78, 81–85, 88–92, 95–97, 100–103, 106–111, 115–116, 119–126, 129–136
   watch_cfi.py321650%36–47, 50–56, 60
   watch_shi.py331652%38–49, 52–58, 62
luxtronik/shi
   interface.py337399%438, 519, 527
TOTAL243228888% 

Tests Skipped Failures Errors Time
378 0 💤 0 ❌ 0 🔥 18.079s ⏱️

805: "sensor desuperheater",
806: "Modbus SEC",
807: "Lost modbus connection",
810: "Parallel-Operation Version",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering what this specifically means? Version mis-match in case of parallel operation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect that the firmware versions aren't compatible in a master-slave heatpump setup.

806: "Modbus SEC",
807: "Lost modbus connection",
810: "Parallel-Operation Version",
816: "Multiple SHI data sources",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this something that you've triggered during development? Can this still happen with this library when used normally (i.e. not multiple instances, etc.).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, I’m not exactly sure how I triggered the error. However, this shouldn’t happen during normal use of the library. The classes should implement threads so that concurrent accesses are handled sequentially.

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 this pull request may close these issues.

2 participants