Appdaemon startup log interpretation

[larrybarello]

I use AppDaemon to query my van electrical system via modbus (Renogy). I have the main process plus four side ones that are small. Two are dependent upon the main update completing so in Apps.yaml I set up dependencies. The flow is:
Initialize, set up 15 second update.
The update queries the electronics and sets state in a bunch of HA sensors. All seems to work. But.

On start up it appears that the creation of sensors occurs three times before initialization is complete. I do not understand why this is happening... Is it related to me just setting an entity value and letting HA/AppDaemon create the entity? Snipped of initalization log follows.

2025-08-01 15:39:07.021970 WARNING Renogy: Renogy: Entity sensor.Battery3_temp3 not found in namespace default 2025-08-01 15:39:07.024925 INFO AppDaemon: Renogy: Entity sensor.Battery3_temp3 created in namespace: default 2025-08-01 15:39:07.060799 WARNING Renogy: Renogy: Entity sensor.Battery3_temp4 not found in namespace default 2025-08-01 15:39:07.063832 INFO AppDaemon: Renogy: Entity sensor.Battery3_temp4 created in namespace: default
While creating entities, the update takes ~5 seconds and after everything settles down, about 3 seconds (reading values, updating state, many states are not changing... some every update).

TIA