Cannot set state attributes of a device

[philhawthorne]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): 0.28

Component/platform: Synology -> Docker Image

Description of problem: When using the states UI in Home Assistant (/dev-states), changing the value of an entity removes any "state attributes".

For example, a multisensor has the value of "on", I change that to "off", and things such as battery level, node_id and friendly name are lost. This means my "Ensuite Motion Sensor" is now "aeotec multi sensor sensor 33".

When the Z-wave network updates the status, the friendly names and attributes are returned.

Expected: When setting the state of an entity, for example a multisensor from on to off via the dev tools, the attributes such as friendly_name etc should be maintained (as they were in previous versions)

Problem-relevant configuration.yaml entries and steps to reproduce: Happens with various entities, not just z-wave. For example, you may change the weather temp from Forecast.io and it will remove the nice name.

- platform: forecast
    api_key: 
    monitored_conditions:
    - summary
    - precip_probability
    - temperature
    - hourly_summary
    - temperature_max

[Landrash]

That would be expected behavior? If you write a state to an entity without a friendly_name it won't have a friendly_name anymore.

[philhawthorne]

No, sorry the issue is, even if you do set a friendly_name, it doesn't keep it. It's like the entire state_attributes are ignored.

[grahamwetzler]

I'm having the same issue. When I restart HA I manually set myself from "not_home" to "home". This used to work fine. However, now when I do it the state attributes are removed.

I select my state:

Manually change the state from "not_home" to "home":

The state attributes are removed.

[balloob]

Can confirm this too. Working on a fix.

[balloob]

Will be fixed in 0.29