Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This is a stub PR that explores implementing the Home Assistant Core "event" platform for ZHA. This platform is a little different from the others in that it does not expose state but rather expects events to be triggered at runtime via
core_entity.trigger_event(event_type).The functionality exposed by this platform has always been a pain point for ZHA (since we rely on device automation triggers at the moment) and I think brings up the first difficulty with quirks v2. Below is a sample implementation that fits within the constraints of quirks v2:
An alternative implementation that relies on quirks directly creating ZHA entities is something that I somewhat prefer: