Problem with scene edit while a device is unavailable

[austinmroczek]

trafficstars

The problem

I have a zwave_js setup, and sometimes some of my z-wave devices are unavailable in HA. However, this is not the problem I need to report, and I'm pretty sure this is not directly related to zwave_js.

If I edit an existing scene that includes an unavailable device (using the UI scene editor <my_URL>/config/scene/edit/my_scene), when I save the scene, that unavailable state is then set as the state for the device in the scenes.yaml file.

I am able to re-create this problem:

1. edit an existing scene in the UI
2. ensure one of the previously included devices is currently unavailable
3. change only the icon associated with the scene (don't touch any of the devices/entities in the scene editor)
4. hit Save
5. git diff scenes.yaml shows the entity for the unavailable device now shows state: unavailable

     switch.front_lawn:
       friendly_name: Front Lawn
-      state: 'off'
+      state: unavailable

What version of Home Assistant Core has the issue?

core-2022.4.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

core ?

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

switch.front_lawn:
      friendly_name: Front Lawn
      state: unavailable

Anything in the logs that might be useful for us?

nothing in the logs

Additional information

No response

[github-actions[bot]]

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[bot]]

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.