Hi Lars.
I stopped LiVi storing hourly data on individual mesh points in Blender a while ago as it could result is so much data being stored, that Blender became distinctly unhappy.
You can however cheat.
If you create a sensing plane and instead of sub-dividing it you create a 2 arrays to cover the room area in an effective grid. You can then separate the grid 'by loose parts' in Blender so that each plane becomes it's own object. Do a DA/UDI/ASE calc and in the resultant CSV you will get the hourly %area of each object that hits the specified targets. By default DA or UDI-supp is 300 lux and UDI-l is 100 lux. If the %area in the CSV file is 100, then that point hit either the 100 or 300 lux target for that hour. You can then process the CSV to calculate what percentage of the total area represented by the "grid" hit that target for each hour which should then give you what you want.
As EN17037 seems to be a new standard adopted by the EU I will add an automated, post-simulation calculation that can be viewed in the VI-Metrics node at some point.
Cheers
Ryan