Just to follow-up. It turns out it wasn’t broken, it’s that I had http://192.168.1.10 when I should just use the IP address ie 192.168.1.10
Also I managed to get the switches to also update their states and thought I’d post for others. This example supposes I have a an airplay device and a playlist called “The A List: Rock”
platform: command_line
switches:
bathroom_airplay:
friendly_name: Bathroom Airplay
command_on: "curl -X PUT http://192.168.1.10:8181/airplay_devices/90-84-0d-f1-04-74/on"
command_off: "curl -X PUT http://192.168.1.10:8181/airplay_devices/90-84-0d-f1-04-74/off"
command_state: "curl -X GET http://192.168.1.10:8181/airplay_devices/90-84-0d-f1-04-74"
value_template: '{{ value_json["selected"] }}'
a_list_rock:
friendly_name: Rock
command_on: "curl -X PUT http://192.168.1.10:8181/playlists/the-a-list-rock/play"
command_off: "curl -X PUT http://192.168.1.10:8181/pause"
command_state: "curl -X GET http://192.168.1.10:8181/now_playing"
value_template: '{{ value_json["playlist"] == "The A List: Rock" }}'
Hi all, if anyone is interested, I have made some little buttons in lovelace using the custom button card that change the playlist to the one listed on the button. Maybe it will save some of you some time to do the same. There’s probably a cleaner way to do this with the rest_command, but this worked.
So first I defined the switches in my configuration.yaml pretty much as described above, except I made both toggle on and toggle off assigned to turn the playlist on. If I want a different playlist, I will just click that button, so the playlist button should always assign the chosen playlist regardless of state.
switch:
- platform: command_line
switches:
mix:
friendly_name: Mix
command_on: "curl -X PUT http://x.x.x.x:8181/playlists/a-45-star/play"
command_off: "curl -X PUT http://x.x.x.x:8181/playlists/a-45-star/play"
- platform: command_line
switches:
jazz:
friendly_name: Jazz
command_on: "curl -X PUT http://x.x.x.x:8181/playlists/best-jazz/play"
command_off: "curl -X PUT http://x.x.x.x:8181/playlists/best-jazz/play"
- platform: command_line
switches:
rock:
friendly_name: Rock
command_on: "curl -X PUT http://x.x.x.x:8181/playlists/best-rock/play"
command_off: "curl -X PUT http://x.x.x.x:8181/playlists/best-rock/play"
- platform: command_line
switches:
pop:
friendly_name: Pop
command_on: "curl -X PUT http://x.x.x.x:8181/playlists/best-pop/play"
command_off: "curl -X PUT http://x.x.x.x:8181/playlists/best-pop/play"
Then in ui-lovelace.yaml I defined the buttons as below (4 simple small text buttons in a row, but much more fancy ones are possible. I will probably make mine nicer someday)
- type: horizontal-stack
cards:
- type: "custom:button-card"
name: Mix
action: service
service:
domain: switch
action: toggle
data:
entity_id: switch.mix
- type: "custom:button-card"
name: Jazz
action: service
service:
domain: switch
action: toggle
data:
entity_id: switch.jazz
- type: "custom:button-card"
name: Rock
action: service
service:
domain: switch
action: toggle
data:
entity_id: switch.rock
- type: "custom:button-card"
name: Pop
action: service
service:
domain: switch
action: toggle
data:
entity_id: switch.pop
I was playing around with this some more and it turns out that there’s actually nothing wrong with calling the service for play_media on media_player_itunes directly to change the playlist. No curl or shell commands needed. The following works fine:
And so you can create a button with the lovelace custom button card mentioned in my previous post as below (tested and working).
- type: "custom:button-card"
name: Jazz
action: service
service:
domain: media_player
action: play_media
data:
entity_id: "media_player.itunes"
media_content_id: "best-jazz"
media_content_type: "playlist"
Next I’m going to have it show which playlist is active using input_boolean and a script which you pass the playlist name in with a variable…
Then I’ll try an input_select for the subgenre of the selected genre… Will report back when I have something working.
I’m also trying to play from Apple generated playlists (e.g. “Favourites mix”) but can’t get it to work.
Also I can’t find a way to access playlists that contain spaces (standard fixes like adding a forward slash or %20 don’t work).
Does anyone have an idea?
You can see all the ones I defined in my config which I published to github… Some of them maybe had spaces but I generally avoid spaces exactly for reasons like this.
If you copy paste the name it says at http://YOUR_SERVER_IP:8181/playlists
it should work, at least it always has for me.
Can you help me?
So I added the shuffle function to my itunes.
How to get the status update? If I activate the shuffle function from itunes I would like it to activate also in HA.
My configuration is:
Wow well done, I moved on to other things and never came back to it, but it will be very nice to have ! Surprising that there’s an attribute for something there’s no service call for, I’m not sure I ever would have noticed that.
BTW I tried the switch but it didn’t update status when I toggled on iTunes or remote. Apparently the standard switch component only updates when used by hass. So I don’t think the value template is doing much here as even without it, it would be in sync after 1 use anyway.
I’m trying to see if we can move over to a RESTful switch which apparently does poll the state with the value template. But I can’t even get it to appear in my switches or logs for some reason. Will have to mess with it some more
Alright, so you inspired me to finally get around to making a shuffle that properly reports the state of the shuffle on the media player even if it gets changed from outside of hass and turns it on/off when toggled. If you change the state from outside hass via iTunes or Remote, it takes 5-10 seconds to sync, that’s just how long it takes itunes-api to do it. A better way to do this might be with a RESTful switch, but I got tired of banging my head against that wall and did it this way.
Add the following to configuration.yaml:
the commands that turn shuffle off and on:
rest_command:
shuffle_on:
url: "http://[YOUR_ITUNES-API_SERVER_IP]:8181/shuffle"
method: put
content_type: "application/x-www-form-urlencoded"
payload: "mode=songs"
shuffle_off:
url: "http://[YOUR_ITUNES-API_SERVER_IP]:8181/shuffle"
method: put
content_type: "application/x-www-form-urlencoded"
payload: "mode=off"
the input boolean you will use as a switch in your ui:
The automations which make sure it displays the correct status if someone changes it in iTunes or Remote rather than via homeassistant and which make the service calls when the input boolean is toggled: