Thanks — I’m responding to your question about the Python SDK not emitting

participant_active

and whether you can get that information from

participant_attributes_changed

. I don’t have specifics about your SDK version or your current event handlers. A couple quick clarifying questions so I can give the right guidance: • Which LiveKit Python SDK version are you using? • Are you running a server-side participant (e.g., Room/Participant on SDK) or a client-side integration? • What do you consider “active” (speaking, publishing tracks, sending audio packets, focused in UI)? If you want a short answer now: I can’t confirm that

participant_active

is emitted by your Python SDK without the version.

participant_attributes_changed

can carry arbitrary attributes you set for a participant — if you can detect activity client-side (e.g., VAD/speaking events, track publishing) you can write an attribute like

active=true

and update it; that change will raise

participant_attributes_changed

for others. If you prefer, tell me the SDK version and how you define “active” and I’ll suggest the exact event/attribute flow and code snippets. , with interactive elements