Skip to content

Add new parameters/visibilities/calculations names#204

Merged
Bouni merged 2 commits intoBouni:mainfrom
Guzz-T:try/field-names
Dec 22, 2025
Merged

Add new parameters/visibilities/calculations names#204
Bouni merged 2 commits intoBouni:mainfrom
Guzz-T:try/field-names

Conversation

@Guzz-T
Copy link
Contributor

@Guzz-T Guzz-T commented Nov 6, 2025

  • Add new parameters/visiblities/calculations names as used in benpru/2025.10.25-beta
  • Add "unknown calculations" names for compatibility reasons

First small step towards #198

Please feel free to suggest more suitable names. Anything is better than “unknown”.

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

Coverage

Coverage Report
FileStmtsMissCoverMissing
luxtronik
   __init__.py1841194%42–43, 46–51, 257–258, 263
   __main__.py21210%3–49
   datatypes.py322199%110
   discover.py58198%62
luxtronik/scripts
   dump_changes.py43430%7–85
   dump_luxtronik.py26260%6–52
luxtronik/shi
   definitions.py210399%113, 431–432
   modbus.py105199%320
TOTAL126710792% 

Tests Skipped Failures Errors Time
245 0 💤 0 ❌ 0 🔥 16.039s ⏱️

@Guzz-T Guzz-T force-pushed the try/field-names branch 2 times, most recently from 7ba48d6 to add62b9 Compare November 6, 2025 21:48
@Guzz-T Guzz-T changed the title Add new parameter name HEATING_TARGET_TEMP_ROOM_THERMOSTAT Add new parameters/visibilities names Nov 6, 2025
@Guzz-T Guzz-T changed the title Add new parameters/visibilities names Add new parameters/visibilities/calculations names Nov 6, 2025
1117: Unknown("Unknown_Parameter_1117"),
1118: Unknown("Unknown_Parameter_1118"),
1119: Unknown("Unknown_Parameter_1119"),
1119: Timestamp(["LAST_DEFROST_TIMESTAMP", "Unknown_Parameter_1119"]),
Copy link
Collaborator

Choose a reason for hiding this comment

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

Out of curiosity: Why is this written in all upper case, since most other names are written in a different way?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The names in capital letters are used in this way in the HA integration of BenPru. In principle, I would be in favor of a case-insensitive name search (if not already implemented), so that this makes no difference.

Copy link
Collaborator

@kbabioch kbabioch left a comment

Choose a reason for hiding this comment

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

Overall looks good to me, just wondering regarding the naming scheme (see previous comment).

@Guzz-T
Copy link
Contributor Author

Guzz-T commented Dec 21, 2025

Overall looks good to me, just wondering regarding the naming scheme (see previous comment).

See my other comment.

@Bouni
Copy link
Owner

Bouni commented Dec 22, 2025

I just did a quick test, we are case sensitive at the moment.
Thats not ideal in my opinion and totally not necessary, I'll submit a PR that changes this behaviour to be case insensitive.

@Bouni
Copy link
Owner

Bouni commented Dec 22, 2025

I'll merge this now, we can add case insensitivity later

@Bouni Bouni merged commit 9e2f01e into Bouni:main Dec 22, 2025
4 checks passed
@Guzz-T Guzz-T deleted the try/field-names branch December 22, 2025 15:16
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.

3 participants