Expose some settings via entity id's. about ha-dual-smart-thermostat HOT 12 CLOSED

All temps and models are currently exposed.

Could you please clarify what exactly you are missing?

from ha-dual-smart-thermostat.

Welll ... somehow it's not exposed for me ...

But hey, I might be stupid and be missing something.

from ha-dual-smart-thermostat.

This is true. This component does not create other entities. But you can read stuff from it's state.
Go to developer tools -> states and see.

from ha-dual-smart-thermostat.

And this is useful in what way ? If I have an entity I can use it for scripting etc.

from ha-dual-smart-thermostat.

You can build automation?

Can you explain what you are missing here?

from ha-dual-smart-thermostat.

Again, I might be stupid (definitely am) - if there is no entity ID, how can I change programatically a set-point / how can I access certain values from the UI directly, baring in mind that most UI requires entity_ID to get live updates from the item.

from ha-dual-smart-thermostat.

In your screenshot the 'entity_id' is 'climate.office_thermostat'

What entity ids are you missing?

from ha-dual-smart-thermostat.

climate.office_thermostat_ON
climate.office_thermostat_current_temp
climate.office_thermostat_max_temp
climate.office_thermostat_min_temp
climate.office_thermostat_state
climate.office_thermostat_state_reason
climate.office_thermostat_heat_on
climate.office_thermostat_fan_on
climate.office_thermostat_cool_on
climate.office_thermostat_whaever_you_think_might_be_worth_exposing

Don't you think that people might find it usefull in their UI / scripts / automations ? Also, not all items that this thermostat controls are simple switches, so right now I've got a intermediary variable that his switches, that I need to monitor to change the trv state ... a bit messy. Exposing those states via entities would help people.

from ha-dual-smart-thermostat.

These are state attributes. You can access them in scripts and automation.

You said that the standard thermoset exposes things that this component doesn't. Can you show me?

from ha-dual-smart-thermostat.

Here is an example of office thermostatic valve:

from ha-dual-smart-thermostat.

That's MQTT integration. This component uses climate integration under the hood.
It exposes state attributes as all sensors and switches you might use to configure already have an entity in HomeAssistant.
Thus, this component should not expose them as they are already exposed.

If you wish, I am happy to help you set up automation using state attributes.
Whit that, I will be able to close this issue for now.

from ha-dual-smart-thermostat.

OK, so ... no entity ID's for your thermostat, just attributes for foreseeable future.
Roger.

from ha-dual-smart-thermostat.