Value Persistence

Configuring value persistence

Value persistence ensures that objects keep their values between restarts.

In MobiusFlow versions before v3 any restart would cause all resources to be reset to their default values. This would often cause anomalies or loss of data such as all temperature values dropping to zero, meter readings being lost or people counts resetting.

MobiusFlow 3 has solved this problem by adding optional value persistence. This can be configured on a service by service basis in the service settings. To access a service's settings follow the instructions here.

When a service starts it first creates all objects with their default values and then applies any persisted values before running.

Enabling / Disabling Persistence

You can enable or disable persistence on each service. Changing the persistence enabled state will affect all objects belonging to that service.

If you wish to have persistence enabled only for some objects consider adding another service and putting splitting your objects between services

You can enable or disable persistence by clicking on the Enable Persistence switch in the service's settings.

If persistence is not required consider switching it off as it will add some CPU load.

Disabling persistence will also delete any persisted values. If you need to reset the persisted values you can disable and then re-enable persistence.

Setting the Persistence Interval

In order to lower CPU load values are only persisted at regular intervals and not on every value change. You can set this interval (in minutes) in the service's settings. Try to find a reasonable balance between saving the current values and load on the system. The more objects a service has, the greater the CPU load required to persist the values.

In addition to persisting values at a regular interval, values are also persisted when you manually stop a service.

Default Settings

Services have persistence enabled with an interval of 5 minutes by default.

Interactive Demo