# Plex client remote control protocol info **URL:** \ **Category:** Dev/API Corner\ **Tags:** other-dev\ **Created:** [October 30, 2012, 12:09am UTC](https://forums.plex.tv/t/plex-client-remote-control-protocol-info/22770 "2012-10-30T00:09:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![zcorneli](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/zcorneli/32/1282_2.png) [@zcorneli](https://forums.plex.tv/u/zcorneli)\ **Post date:** [October 30, 2012, 12:09am UTC](https://forums.plex.tv/t/plex-client-remote-control-protocol-info/22770/1 "2012-10-30T00:09:20Z")
Copying the question asked in this post: [http://forums.plexapp.com/index.php/topic/35906-raspberry-pi/page\_\_view\_\_findpost\_\_p\_\_306588](http://forums.plexapp.com/index.php/topic/35906-raspberry-pi/page __view__ findpost __p__ 306588) Is there a document available that defines the remote control communications between the a client and the server, and how to advertise as a client, and how to advertise capabilities as a client? Context: A group of community members (see thread mentioned above) are working on a python script for the raspberry Pi that acts as a gui-less client, purely remote controlled (either from the web interface, or mobile device as a remote), and just plays what its given. They’re currently using Avahi and advertising as \_plexclient.\_tcp on port 3000, but most remote control commands (like play, pause, or stop) are never received by the client. ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [December 20, 2019, 10:22pm UTC](https://forums.plex.tv/t/plex-client-remote-control-protocol-info/22770/2 "2019-12-20T22:22:37Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.