The persistence has multiple downsides.

The biggest for me was, that old sensor values are reported as new when restarting home assistant.

The downside is, that the presentation of your nodes has to be more robust. If you use persistence, you do not notice if your nodes only present at startup. Without persistence, they will not reappear in HA, if they only present once after powering on.

This might have changed meanwhile.

Perhaps you are also affected from

https://www.home-assistant.io/blog/2020/01/15/release-104/#improved-entity-handling-on-startup

I am currently not running the latest HA version.

Regards
Leonard

In mine the switch broke, so I replaced it.

But as I am going to tradfri, I replaced the whole transformer in the meantime, so I have a remote left... in germany...

Regards
Leonard

The persistence has multiple downsides.

The biggest for me was, that old sensor values are reported as new when restarting home assistant.

The downside is, that the presentation of your nodes has to be more robust. If you use persistence, you do not notice if your nodes only present at startup. Without persistence, they will not reappear in HA, if they only present once after powering on.

This might have changed meanwhile.

Perhaps you are also affected from

https://www.home-assistant.io/blog/2020/01/15/release-104/#improved-entity-handling-on-startup

I am currently not running the latest HA version.

Regards
Leonard

I'am using home-assistant for a while and build some temperature sensors with mysensors.

With the default settings, home-assistant is caching the presentation and sensor values in a pickle file. This has the following downsides:

• when restarting home-assistant, old sensor values are beeing shown as new (just received)
• when changing a sketch, some added information does not update (or partly).

So I decided to turn off the persistence. Now I do have the problem, that nodes have to repeat their presentation when restarting home-assistant. I haven't got this working properly. Resetting the nodes fixes this issue, but that is not an solution.

I see two solutions

• repeat presentation (if necessary, nodes are battery powered)
• tweak home-assistant to do a more clever persistence

The more clever persistance would involve:

• discard old sensor values (or do not show them as new values...)
• allow sketch updates without limitations (details would have to be investigated)
• Allow to remove nodes that are not present any more (pickle file can not be edited easily).

Has anyone suggestions to solve this issues?

Regards
Leonard