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

Current- and Set- temperature in Sensor entity #22

Open
jdschuitemaker opened this issue Nov 2, 2022 · 15 comments
Open

Current- and Set- temperature in Sensor entity #22

jdschuitemaker opened this issue Nov 2, 2022 · 15 comments

Comments

@jdschuitemaker
Copy link

I am using the graph card on my dashboard for showing temperatures on the different floors in my house. Just the room temperature, which is provided through a climate-entity, cannot be used in the graph-card because it does not support the climate entity.

Would it be possible to move (or add), the temperature to a sensor-entity instead. This would make my temperature dashboard more consistent.

@carresquet
Copy link

I have the same "problem"

@dimitribo
Copy link

And also want to see the same. In sensor values te current and set temperature.
I have Remeha E-twist working on it at the moment.

@dimitribo
Copy link

Find it ;)
At this in the configuration.yaml

sensor:

  • platform: template
    sensors:
    temperature:
    friendly_name: "your current temp"
    unit_of_measurement: '°c'
    value_template: "{{ state_attr('climate.bdr_thermostat', 'current_temperature') }}"
    temperature_set:
    friendly_name: "your current set temp"
    unit_of_measurement: '°c'
    value_template: "{{ state_attr('climate.bdr_thermostat', 'temperature') }}"

@jdschuitemaker
Copy link
Author

jdschuitemaker commented Jan 3, 2023

@dimitribo, that doesn't work for me. Something of your example is not correct (I think something went wrong with copy/paste), I changed it to this:

sensor:
  - platform: template
    temperature:
    friendly_name: "your current temp"
    unit_of_measurement: '°c'
    value_template: "{{ state_attr('climate.bdr_thermostat', 'current_temperature') }}"
    temperature_set:

Then I see the following error when I verify the configuration in Developer tools -> Check and restart:

Invalid config for [sensor.template]: [temperature] is an invalid option for [sensor.template]. Check: sensor.template->temperature. (See ?, line ?).

Do you know what is wrong? Thank you in advance!

@dimitribo
Copy link

Hello,

As I can see, you didn't do a good copy i think...
You code is not the same like my code.
Can you retry please ?

@jdschuitemaker
Copy link
Author

I appreciate your reply!

Something goes wrong with formatting when I use your code, I think.

sensor:
    platform: template
    sensors:
    temperature:
    friendly_name: "your current temp"
    unit_of_measurement: '°c'
    value_template: "{{ state_attr('climate.bdr_thermostat', 'current_temperature') }}"
    temperature_set:
    friendly_name: "your current set temp"
    unit_of_measurement: '°c'
    value_template: "{{ state_attr('climate.bdr_thermostat', 'temperature') }}"

When I use that in my configuration.yaml I get a warning from the editor:

duplicated mapping key (75:5)

 72 |     unit_of_measurement: '°c'
 73 |     value_template: "{{ state_attr( ...
 74 |     temperature_set:
 75 |     friendly_name: "your current se ...
----------^
 76 |     unit_of_measurement: '°c'
 77 |     value_template: "{{ state_attr( ...

@dimitribo
Copy link

Hello,

This is really my code ... see the image:

image

Duplicated mapping key in the error for you ? Is the entitie already in use for you ?

@jdschuitemaker
Copy link
Author

Thank you for that, that seems to have helped to solve it. It was purely formatting (indention)

@TWilhoWI
Copy link

TWilhoWI commented Jan 5, 2023

Thank you for that, that seems to have helped to solve it. It was purely formatting (indention)

Could you also change the desired temperature now? When do I have to paste your code?

@jdschuitemaker
Copy link
Author

jdschuitemaker commented Jan 5, 2023

I have not tried that, but I am using the temperature gauge that comes with the integration for that.

It seems that he update rate of the current temperature is not really high, the graph is therefore not very smooth when the temp changes. Could also be that the temperature that the e-twist is measuring or providing is providing only full or half degrees (20.0, 20.5, 21.0) and not 20.5, 20.4, 20.3.

Edit: I found that the reading interval is once every 10 minutes. See sensor.py

SCAN_INTERVAL = timedelta(minutes=10)

@TWilhoWI
Copy link

TWilhoWI commented Jan 5, 2023

How do I enable the temperatur gauge? I didn't find it?

@jdschuitemaker
Copy link
Author

The documentation explains how to do that: https://github.com/freitdav/BDRthermostatHA

@TWilhoWI
Copy link

TWilhoWI commented Jan 5, 2023

The documentation explains how to do that: https://github.com/freitdav/BDRthermostatHA

Correct but for me the integration doesn't create a climate entity for some reason

@jdschuitemaker
Copy link
Author

Not sure if I am able to help you then. Maybe remove the integration and try again?

@TWilhoWI
Copy link

TWilhoWI commented Jan 7, 2023

Not sure if I am able to help you then. Maybe remove the integration and try again?

Tried it, didn't work unfortunately

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