Nuts that is a significant problem for me when editing that forces me to use the “CLASSIC” automation option to avoid the editor wiping out my configs.
I’d like to draw everyone’s attention to a useful new option in this release, called snapshot_entities, that simplifies creating scenes on the fly. It was created by Santobert in PR 28939 and is an enhancement to scene.create.
The use-case is when you want to:
- Record the current state of several entities before you change them to something else.
- Change them to something else.
- Restore their states to their previous values.
Using snapshot_entities, you can now simply list the entities in scene.create. Their current state will be stored in the temporary scene.
Example from the documentation:
Save the states of two entities to a new, temporary scene called scene.before.
- service: scene.create
data:
scene_id: before
snapshot_entities:
- climate.ecobee
- light.ceiling_lights
When the time comes to restore their states, simply turn on scene.before.
- service: scene.turn_on
data:
entity_id: scene.before
EDIT
Clarified the use-case.
14 Likes
Anyone got the proxmox integration working?
I get a :
Package proxmox setup failed. Component proxmox Integration 'proxmox' not found.
when i check my config
♂From this release every integration based on alarm_control_panel (like this one) won’t work because they introduced an abstract method supported_features.
It’s obviously a breaking change, but it wasn’t listed as such… 
1 Like
Anyone else seeing an issue with lutron_caseta lights? I’m getting an issue because pylutron doesn’t get installed
Unable to prepare setup for platform lutron_caseta.light: Platform not found (No module named 'pylutron').
I didn’t think anything about the lights portion of lutron_caseta changed, so I’m not sure if this is due to the python package import changes? As far as I can tell, lutron_caseta.light requires pylutron because it imports a couple of things from homeassistant.components.lutron.light and the lutron component uses pylutron. I’m not sure how it was working before this update, but just that import apparently isn’t enough to make homeassistant go off and get the dependencies of the lutron component
Do you know if that works for media_players?
For instance if you are casting an Internet radio station to a Google Mini media_player, will it remember what it was playing/volume, etc, if an open/close door cast alert goes to the speaker?
I have no media_players so I can’t test it. Give it a try and let us know.
Have you tried restarting HA, sometimes it needs to pull it down and install
Awesome release! Thanks for the hard work and Merry Christmas!!!
1 Like
I did raise this earlier this week on the alarm github page. Hopefully a simple fix
It is proxmoxve, please check the documentation. 
The docs say it is set up using proxmox in the configuration.yaml, even though the integration seems to be called proxmoxve
This is what the docs say
# Example configuration.yaml entry
proxmox:
- host: IP_ADDRESS
username: USERNAME
password: PASSWORD
nodes:
- node: NODE_NAME
vms:
- VM_ID
containers:
- CONTAINER_ID
You are absolutely correct! PR has already been filed I see 
Thanks, I’m all set. I figured if it was announced that it would be available to all installations. I just had not waited long enough.
Restart the Gateway, this same error occurs for me when I update HA on occasion. Restarting the Gateway, and then HA fixes the issue.
Thanks to all 4 (and the others) for this amazing work !
Have great holidays and see u next year 
Another solid releases!!! Thanks for the great year, all the fun (and tears) you’ve given other, lives you’ve improved and excitement you’ve generated.
Have a great break! and see you in the new year to smash it out the park in 2010!!!
I see we have over 1500 integrations now. It doesn’t seem that long ago we got to 1,000. https://www.home-assistant.io/blog/2018/02/26/release-64/
Keep up the good work.
3 Likes