When set to 0, SmartVolume is disabled and the up/down control APIs are used (with client-dependent results). This value represents the increment that should be used that is, if you set it to 10, then volume will be increased or decreased in increments of 10%. The feature can be enabled by setting the "SmartVolume" state variable to a non-zero value. This plugin's "SmartVolume" feature addresses this, when enabled, by avoiding the simple up/down API commands and explicitly setting the volume to an increment from its current value.
Many simply move the volume up or down by 1%, which isn't very useful-it takes a lot of 1% changes to make a meaningful change in volume.
The Emby remote control API's volume up and down functions rely on the client to do the "right" thing, and many don't. While not every Emby client implements every feature, the plugin does make an effort to get common functionality working using the available capabilities of the client. The Emby plugin makes some attempt to address this limitation by tracking the one last-known media item and providing an action to resume play of that item, but if it was one of many in a long list, there's no way for the plugin to know that and the remainder of the former list cannot be played. You can start playing from a paused state, no problem, but from a full stop/idle player, there's no history stored to use as a starting point. That means, for the moment, that you can't simply send a "Play" command to an Emby client and have it pick up from where it was previously stopped. There is a queue, but it exists only during play, and is not accessible through the Emby API (the author has said he plans to address this in future). If something works on one player but not another, that's probably a client issue, not a plugin issue, and I will not likely spend a lot of time chasing it.Įmby does not currently maintain an accessible "queue" of items a client is going to play. 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).
0 kommentar(er)
