jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2018-01-15 11:59:29 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-15 11:59:30 +00:00
parent bd22e4b200
commit bf18f14fe7
772 changed files with 16363 additions and 3384 deletions
Download patch file Download diff file Expand all files Collapse all files

38
components/media_player.squeezebox/index.html
View file

@ -90,6 +90,44 @@
<li><strong>password</strong> (<em>Optional</em>): The password, if password protection is enabled.</li>
</ul>
<p class="note">This platform now uses the web interface of the Logitech Media Server to send commands. The default port of the web interface is 9000. It is the same port that you use to access the LMS through your web browser. Originally, this platform used the telnet interface, which defaults to 9090. If you previously specified the port in your configuration file, you will likely need to update it.</p>
<h3><a class="title-link" name="service-squeezebox_call_method" href="#service-squeezebox_call_method"></a> Service <code class="highlighter-rouge">squeezebox_call_method</code></h3>
<p>Call a custom Squeezebox JSONRPC API.</p>
<p>See documentation for this interface on http://HOST:PORT/html/docs/cli-api.html?player= where HOST and PORT are the host name and port for your Logitech Media Server.</p>
<table>
<thead>
<tr>
<th>Service data attribute</th>
<th>Optional</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code class="highlighter-rouge">entity_id</code></td>
<td>no</td>
<td>Name(s) of the Squeezebox entities where to run the API method.</td>
</tr>
<tr>
<td><code class="highlighter-rouge">command</code></td>
<td>no</td>
<td>Command to pass to Logitech Media Server (p0 in the CLI documentation).</td>
</tr>
<tr>
<td><code class="highlighter-rouge">parameters</code></td>
<td>yes</td>
<td>Array of additional parameters to pass to Logitech Media Server (p1, …, pN in the CLI documentation).</td>
</tr>
</tbody>
</table>
<p>This service can be used to integrate any Squeezebox action to an automation.</p>
<p>It can also be used to target a Squeezebox from IFTT (or DialogFlow, Alexa…).</p>
<p>For example, to play an album from your collection, create an IFTT applet like this:</p>
<ul>
<li>Trigger: Google assistant, with sentence: <code class="highlighter-rouge">I want to listen to album $</code></li>
<li>Action: JSON post query with such JSON body:<br />
<code class="highlighter-rouge"><span class="p">{</span><span class="w"> </span><span class="nt">"entity_id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"media_player.squeezebox_radio"</span><span class="p">,</span><span class="w"> </span><span class="nt">"command"</span><span class="p">:</span><span class="w"> </span><span class="s2">"playlist"</span><span class="p">,</span><span class="w"> </span><span class="nt">"parameters"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">"loadtracks"</span><span class="p">,</span><span class="w"> </span><span class="s2">"album.titlesearch="</span><span class="p">]</span><span class="w"> </span><span class="p">}</span></code><br />
This can work with title search and basically any thing. The same wouldn’t have worked by calling directly Squeezebox server as IFTT cannot escape the text field.</li>
</ul>
</article>
</div>
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">