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

Enhance Thermostat definition: Determine Working state #90

Open
Apollon77 opened this issue Jan 29, 2025 · 3 comments
Open

Enhance Thermostat definition: Determine Working state #90

Apollon77 opened this issue Jan 29, 2025 · 3 comments

Comments

@Apollon77
Copy link
Collaborator

Apollon77 commented Jan 29, 2025

To better work with Thermostats we should enhance the Thermostat type by:

  • adding optional Valve-State ... 0..100% (mainly relevant for heating) role: value.valve - valve level (also allowed level.valve because sometimes it is writable)
  • adding optional Valve-Mode with an Enum with values like "HEAT", "COOL", "NEUTRAL/OFF" that reflects what the device is actually doing

Then I could map this to matter. WDYT?

@Garfonso
Copy link
Contributor

👍

  • I really like the valve state. Missed that in the past.
  • mode is a good addition, too. AirCondition has a mode, too. And in HomeAssistant thermostat and aircondition both are "climate" entities, where mode is the most important attribute (at least for the frontend, it seems). Would make mapping a bit easier, currenlty lovelace adapter does some crude mapping of on/off to modes. 😄

@Feuer-sturm
Copy link

issue in hm-rpc "HMIP thermostat HmIP-eTRV-B - wrong role for LEVEL and VALVE_STATE" ioBroker/ioBroker.hm-rpc#1343 which has an impact on this issue

@GermanBluefox
Copy link
Contributor

Both is ok

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

No branches or pull requests

4 participants