Yes, @AbrahamYezioro has correctly identified the use of (non ideal air) detailed HVAC as the source of the error. But it’s not a bug and let me explain why you aren’t able to construct energy balances or match data to rooms with detailed HVAC results.
When you run a simulation with detailed HVAC, the energy use happens on the basis of each piece of HVAC equipment rather than each room like ideal air systems. So I can have one boiler that serves 10 rooms and I can get the fuel energy use of this boiler. However, figuring out how much of that energy use corresponds to which room is kinda like unscrambling an egg, especially for certain HVAC systems which supply heating/cooling through both the central air stream and through the zone equipment like baseboards, reheat boxes, etc. Granted, I know that some types of HVAC like the window air conditioning have only one unit per room and so it’s technically possible to match the results with the rooms. However, for the sake of clarity the only HVAC type with results that can be matched to rooms is the ideal air system so I recommend running simulations with that if you need to get visuals of room heating cooling loads. If you really need to make a visual of window AC electric energy matched to rooms, I can put together a component with a few lines of Python that does the matching but I think I would like to avoid trying to support this within the plugin and core libraries since the ability to match results of HVAC equipment varies so much between different HVAC systems. You really need to know how the HVAC is set up to write something that does the matching.
As for the energy balance, there’s not only the issue of matching results to rooms but also the fact that the heating/cooling results you get for a detailed HVAC are electricity/fuel and not the heating/cooling load that needs to be added or removed from the room. So trying to use electricity or fuel like this is going to give you an incorrect “unbalanced” set of loads.
I’ll try to add in some better error messages for this in the components when I get the chance.