Many DLNA players will be discovered by the Emby server and thus made visible in this plugin, but are not controllable (even though Emby's flag for the session says remote control is available). In fact, when an idle client begins playing media, it may take up to a minute before the plugin first reflects this state change and starts updating more frequently.Įmby clients are not required to implement every action, and many don't. Although the plugin displays activity information for known clients as reported by the Emby server, it is neither possible nor practical for that information to be up-to-the-second accurate and identical to that displayed on the client itself.
It's meant to do things like mute your player when the doorbell rings, or start playing music when you run a scene, for example. Caveatsįirst and foremost, keep in mind that this plugin is to be used as an automation interface to Emby, and not as a replacement UI for clients. Once a server is registered, go into its control panel and use the login functionto get the necessary authentication token the plugin needs to access the server.
Install by uploading to your Vera, then creating the base Emby Plugin master device (device file D_Emby1.xml and implementation file I_Emby1.xml).ĭiscovery is used to register the server launch discovery from the plugin device's control panel. The plugin is currently available only from Github. A session represents a connection from an Emby client to a server. A server represents an Emby Server (you can have more than one). The plugin has two types of child devices: servers and sessions. The Emby Plugin is the interface for all Emby servers discovered in the network (servers outside the LAN can also be registered by IP discovery). An Emby Interface for Vera Home Automation Controllers (Vera plugin).