Must be of type float, string given on calculateEnergy

Created a simple patch to fix the issues. It works well as long as energy and timestamp aren’t null or complex types like arrays/objects.

That section of code should only be called if you are using a Radioactivity field instead of a Radioactivity Reference field.

In 4.1.x, you can't use a Radioactivity field unless you've upgraded an old site from 8.x-3.x and you were using the Radioactivity field in 8.x-3.x. Using the Radioactivity field is something that is supported only for backwards compatibility, but it is not allowed on new installs.

Does this correctly describe your situation?

Rather than using a cast, I would prefer to use getValue() so that the datatype of the energy and timestamp variables is maintained. They are declared as float and integer respectively, in the database schema.

I moved the patch into an MR to that it can be tested.