Skip to content

Feature/huber chiller#229

Open
renereimann wants to merge 7 commits intodevelopfrom
feature/huber_chiller
Open

Feature/huber chiller#229
renereimann wants to merge 7 commits intodevelopfrom
feature/huber_chiller

Conversation

@renereimann
Copy link
Contributor

We implement yet another company specific service and endpoint.
For the chiller from Huber there is a set of three commands however one of the commands controls several values (get and set).
Therefore we implement the protocol from Huber.
The tool works nicely with our chiller and we can read:

  • model
  • limits
  • mode
  • error status
  • internal temperature
  • setpoint
  • external temperature (not available on our device)



__all__.append("HuberEntity")
class HuberEntity(Entity):
Copy link

Choose a reason for hiding this comment

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

set is disabled - is that universal for all Huber endpoints? should this be a HuberGetEntity?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You can set an Hiber endpoint but its ugly. I have to think about it and see if I want to implement it. Thanks for the suggestion

Copy link

Choose a reason for hiding this comment

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

just to be clear - I wasn't suggesting that you should implement the set (if it's ugly, and you don't really need it, probably not worth it); but if there later might be a get/set version, do you want the naming convention to already predict that. Otherwise in the future all of your HuberEntity usages will pick up a set functionality that you may not want (or maybe you do).

@renereimann renereimann changed the base branch from main to develop February 5, 2026 21:59
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