OH restart always after upgrade from 2.4 to 2.5

This appears regularly in your events.log

2020-08-20 02:58:25.352 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node4' has been updated.

ThingUpdatedEvent is about the properties of the Thing, not the status (online etc.) or the actual sensor readings.

It means the binding has found device properties that don’t match your configuration, and made an update. That’s all very well, but Thing updates force some kind of re-initialization. Exactly how and what gets reinitialized seems to vary and is a mystery to me, but especially noted with zwave - under different circumstances that we’ll come to in a minute - “system started” rules triggering, etc.

Suffice to say this regular node 4 log is not a Good Thing.

What has probably happened is that the zwave database for this device has been updated since your Thing was created, and no longer matches.
The recommended course I think is to delete your Thing (leave the zwave stick and device alone) and allow rediscovery or create manually. If you use the same Thing name, it will re-attach to your existing openHAB channels and Items.

Later in your logs, extractions -

2020-08-20 02:54:46.583 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node37' has been updated.
2020-08-20 02:54:59.064 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node36' has been updated.
2020-08-20 02:55:03.282 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node37' has been updated.
2020-08-20 02:55:05.940 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node31' has been updated.
2020-08-20 02:55:08.031 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node36' has been updated.
2020-08-20 02:55:08.812 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node33' has been updated.
2020-08-20 02:55:08.822 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node4' has been updated.
2020-08-20 02:55:08.982 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node41' has been updated.
2020-08-20 02:55:09.148 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node32' has been updated.
2020-08-20 02:55:13.262 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node32' has been updated.
2020-08-20 02:55:13.294 [hingStatusInfoChangedEvent] - 'zwave:device:5204811e:node32' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
2020-08-20 02:55:14.074 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node34' has been updated.
2020-08-20 02:55:16.146 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node41' has been updated.
2020-08-20 02:55:17.205 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node38' has been updated.
2020-08-20 02:55:23.740 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node34' has been updated.
2020-08-20 02:56:40.285 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:5204811e:node38' has been updated.
2020-08-20 02:56:42.558 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node36_meter_watts changed from NULL to 0
2020-08-20 02:56:42.676 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node36_meter_voltage changed from NULL to 234.66
2020-08-20 02:56:42.782 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node36_meter_current changed from NULL to 0
2020-08-20 02:57:42.438 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node41_meter_kwh changed from NULL to 1.85
2020-08-20 02:57:42.627 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node41_meter_watts changed from NULL to 0
2020-08-20 02:57:42.983 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node41_meter_current changed from NULL to 0
2020-08-20 02:58:02.833 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node31_sensor_temperature changed from NULL to 26.7 °C
2020-08-20 02:58:08.705 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node31_sensor_luminance changed from NULL to 0
2020-08-20 02:58:09.422 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node31_sensor_relhumidity changed from NULL to 55
2020-08-20 02:58:11.042 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node31_battery_level changed from NULL to 100

Okay, so chaos on zwave at 3am.

What’s going on is the zwave “nightly network heal”, which does seem to give some users much grief.

Especially noticeable is that some Items later get updated from NULL to new value. Those Items have been silently reinitialized (hence NULL state), The knock-on effects can take ages to clear up -

2020-08-20 07:58:44.957 [vent.ItemStateChangedEvent] - zwave_device_5204811e_node31_alarm_tamper changed from NULL to OFF

Imagine if you had a rule that relied on that being OFF.

I’ll leave it to zwave users to advise what to do here, but you’ll probably want to disable nightly heal for now.
However, with your big 2.4 -> 2.5 update, maybe you really just need to do the delete/rediscover Thing business on those nodes as well.