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

The scene restore the HVAC state is wrong. #45748

Closed
vampywiz17 opened this issue Jan 30, 2021 · 6 comments
Closed

The scene restore the HVAC state is wrong. #45748

vampywiz17 opened this issue Jan 30, 2021 · 6 comments

Comments

@vampywiz17
Copy link

vampywiz17 commented Jan 30, 2021

The problem

The scene restore the HVAC state wrong.

Environment

Hass.OS Latest stable release.

Problem-relevant automation.yaml

- alias: Window opened
  trigger:
  - platform: state
    entity_id: binary_sensor.xxx_contact
    from: 'off'
    to: 'on'
  condition: []
  action:
  - service: scene.create
    data:
      scene_id: before
      snapshot_entities:
      - climate.room_1
  - service: climate.set_hvac_mode
    data:
      entity_id: climate.room_1
      hvac_mode: 'off'
- alias: Window closed
  trigger:
  - platform: state
    entity_id: binary_sensor.xxx_contact
    from: 'on'
    to: 'off'
  condition: []
  action:
  - service: scene.turn_on
    data:
      entity_id: scene.before

Additional information

It need to revert the HVAC state if i close the window. The problem is if the HVAC is auto, it set back it to heat. My idea is that the problem if it restore the state it also restore the setpoint temperature. This is automatically turn it to "heat" mode not "auto"

@probot-home-assistant
Copy link

Hey there @home-assistant/core, mind taking a look at this issue as its been labeled with an integration (scene) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@github-actions
Copy link

github-actions bot commented Jul 6, 2021

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 6, 2021
@cgtobi
Copy link
Contributor

cgtobi commented Jul 6, 2021

not fixed yet.

@github-actions github-actions bot removed the stale label Jul 6, 2021
@hnykda
Copy link

hnykda commented Sep 21, 2021

I believe I hit this here: https://community.home-assistant.io/t/scene-setting-wrong-input-select-in-automation-for-some-reason/340185/4 . Let me know if I can help to provide any more details on my settings core-2021.9.6

@wigster
Copy link

wigster commented Dec 15, 2021

I have also hit a version of this:

HA 2021.12.2 on HAOS 7.0
TRV is a Eurotronic Spirit on ZWave, running through ZWAveJS2MQTT plugin 0.31.1

Climate entity has preset modes Heat, Energy heat and Full power with separate temperature set points for Heat and Energy heat.

To replicate problem.

  1. Start with climate.trv entity with set points Heat: 22, Energy heat 20.
  2. Set Energy heat preset mode.
  3. scene.create with snapshot entity climate.trv
  4. change set point temps to heat 23, energy heat 17 and preset mode to Heat
  5. scene.turn_on of the saved scene

Result:
preset mode: energy heat (ok);
Heat set point -- 20 (taken from the saved Energy heat setting),
Energy heat set point 17 (unchanged by scene_turn_on).

I guess the logic in scene.turn_on is that it first restores whatever temperature set point was active at the time of scene creation and then sets the preset mode. A minimal fix would swap these two operations, although a dump of all the states of the climate entity into the scene snapshot would be a nicer solution.

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 30, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Aug 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants