snarky-snark

As far as I can tell, this is expected behavior from home assistant that I cannot change from this component.

Unfortunately, the [Home Assistant documentation](https://data.home-assistant.io/docs/events#state_changed) doesn't explain this situation well.

I wonder if this has something to do with [significant change support](https://developers.home-assistant.io/docs/significant_change_index/).

It might be that [this function](https://github.com/snarky-snark/home-assistant-variables/blob/27f0169dc74d2dfbbde907c2fb8ff57fa7fe9a31/custom_components/var/__init__.py#L389) must be passed `true` if `force_update == true`. I've lost context...

You might be able to workaround your problem by using the SQL query features of this component. Sorry, I can't be of more help.

initial_value is only used on the first restart of HA unless restore is set to false. Could this be your issue?

Strange. As far as a I know, home assistant shouldn't treat those entities any differently, nor does the var component.

What happens if you try to change the friendly name from the debugging tools page using the `var.set` service?

Thanks for reporting the issue. It seems that the correct fix for this will be to update all config values besides `initial_value` on restart.

Thanks for the feedback, all. I will do what I can to keep this integration maintained, but I encourage everyone to use the native home assistant features where possible.