There is a feature that I find hard to work without: detailed back logs; especially regarding where a command came from. Sometimes I have some devices that are turned on without being able to figure which app did it since none of the apps they're attached to seem to show the related conditions to trigger such events at the precise time of the event. It could be coming from other sources, such as Alexa, IFTTT, etc. but, apparently, there is no way to see this within the very scarce backlogs we have access to. The only thing that barely approaches a useful info in that regard is, for some events and some devices only, if the cmd type was digital or physical. This is far from enough for figuring out where the command came from, except through probabilistic deductions, which submits debugging to chance and many attempts to fix this through days and days of trial and errors.
Would it be possible to soon release a way to access a more exhaustive history of events which would mention which app did what?
Instead of looking for triggers, you should directly at the app's event logs.
Most built-in apps have logging options that can be turned on. Also, most built-in apps keep their own event logs (look at the top of the app status page). Devices keep event logs for every action, and they show which apps touch that device. So, for a given device that you have some question about, track down each of the apps that show as using that device, and check their event logs. It may take a little detective work, but it's not that hard to track down with what's available now.
If you can identify an app that has inadequate logging available we could certainly look into adding more logging; likewise with an app that has inadequate event logs (apps that don't log much to Logs do keep event logs). There is no system-wide means beyond those mentioned above to display "a more exhaustive history of events". It's not on our roadmap to add a system-wide facility, given the complete event histories available now for devices and apps.