Is it normal that power button of mini-media-player “does no support this service”??
yes linkplay modules don’t support power on/off
I looked in the official documentation and I see that the manufacturer did not provide such a function at all. It’s a pity because I thought that I would be able to do automatic switching off the amplifier when my wife leaves the house because somehow she never remembers to do it herself 
I have an automation that turns on/off the amplifier smart plug depending on the status of my Linkplay device.
1 Like
Have you found a solution?
The link doesn’t work from France (“The website is currently inaccessible…
The website has not obtained an ICP filing according to the law of the Ministry of Industry and Information Technology of the People’s Republic of China”)
Is there another one that can be used outside of China? Thx.
I also have a forbidden message:
“Forbidden
You don’t have permission to access this resource.
Apache/2.4.41 (Ubuntu) Server at s000.linkplay.com Port 8020”
Is it the right link?
Added support for Music Assistant:
- retrieve artist, title, coverart of the current playing media
- retrieve current playing position of the current playing media
- support for Previous/Next track in Music Assistant play queue
- support for
announceflag of TTS messages (no need anymore for snapshot and restore services) from HA 2022.06
6 Likes
Hi! I have been using linkplay for maybe 2 years with mini media player card and it have worked really well until 2 months ago.
Now it won’t read the player group and can’t add players to the “master”
This is an error I get
Felet härrör från en anpassad integration.
Logger: custom_components.linkplay.media_player
Source: custom_components/linkplay/media_player.py:412
Integration: Linkplay (documentation, issues)
First occurred: 9 juli 2022 00:57:37 (9329 occurrences)
Last logged: 07:22:33
Failed communicating with LinkPlayDevice (httpapi) 'Vardagsrum': <class 'aiohttp.client_exceptions.ClientConnectorError'>
Failed communicating with LinkPlayDevice (httpapi) 'Köket': <class 'aiohttp.client_exceptions.ClientConnectorError'>
Failed communicating with LinkPlayDevice (httpapi) 'Kontoret': <class 'aiohttp.client_exceptions.ClientConnectorError'>
Failed communicating with LinkPlayDevice (httpapi) 'Tv bänk': <class 'asyncio.exceptions.TimeoutError'>
And this is my card
type: grid
cards:
- type: custom:mini-media-player
entity: media_player.tv_bank
icon: mdi:speaker-wireless
artwork: cover
shortcuts:
columns: 3
buttons:
- icon: mdi:sofa
type: service
id: spotcast.start
data:
spotify_device_id: ********************
uri: spotify:playlist:37i9dQZF1EMf7p3p04uNyJ
random_song: true
- icon: mdi:desk
type: service
id: spotcast.start
data:
platform: linkplay
spotify_device_id: ********************
uri: spotify:playlist:37i9dQZF1EMf7p3p04uNyJ
random_song: true
- icon: mdi:dog-side
type: music
entity_id: media_player.tv_bank
id: https://sverigesradio.se/topsy/direkt/164-mp3.pls
hide:
volume: false
source: false
power: true
speaker_group:
platform: linkplay
show_group_count: true
entities:
- entity_id: media_player.koket2
name: Köket
- entity_id: media_player.vardagsrum2
name: Vardagsrum
- entity_id: media_player.tv_bank
name: Tv bänk
- entity_id: media_player.kontoret2
name: Kontoret
toggle_power: false
columns: 1
square: false
I have tries Google the error but can’t seem to find anything about it. The speakers are audio pro and like I said, it worked great before
i have the same error… i think is aproblem with Music Assistant
What is your linkplay component version?
Think its might be another reason because I don’t use music assistant.
@robi I use the latest one, I think its 3.1.6 ?
Latest stable version is 3.1.5. The ones after were withdrawn.
I just rolled back to 3.15 but still wont join in multi-room, now I dont get any error in my log and I have tried pair them with a more simplier card than before
type: custom:mini-media-player
entity: media_player.tv_bank
hide:
power: true
icon: true
source: true
speaker_group:
platform: linkplay
show_group_count: true
entities:
- entity_id: media_player.tv_bank
name: Tv bänk
- entity_id: media_player.koket_2
name: Köket
- entity_id: media_player.vardagsrum_2
name: Vardagsrum
Any idea why lastfm coverart would stop working some time after a recent linkplay component update when they used to work fine for most of my radio stations? Nothing else changed in the config, stream URLs are also unchanged.
I tried a new lastfm API key but didn’t help.
Has something changed in the component that might cause this?
Also, how do I get logs of the icecast/lastfm lookups? I set the linkplay component to debug but don’t see anything in the logs.
I have a GGMM_E2 speaker (it is based on linkplay) it worked great for me,
But since last week I have some problems,
First problem, I can’t turn on the radio,
Another problem is that in TTS he manages to read a simple word,
But a complex sentence is not successful, for example I write 12:45 in the past he always said it in the form of an hour,
But now that I’m writing a complex sentence like this he doesn’t say at all,
Attached is the error I am getting, I would appreciate your help.
Error during call async_media_play: UpnpActionResponseError('Error during async_call(), status: 500, upnp error: 704 (play not allowed)')
[281473372176448] Entity media_player.ggmm_e2_2844 does not support this service.
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 199, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1713, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1750, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 653, in entity_service_call
raise HomeAssistantError(
I checked again, and the TTS problem in GGMM_E2 is really weird,
He reads words without problems, but only numbers with 3 digits, from then on he does not read,
When I connect another speaker it reads perfectly normal and the radio also works properly,
The problem is only with the GGMM_E2 speaker
what could be the problem?
Try another TTS service.
I tried and still have the same problem
Hi Robert! Thanks for all of your work on this.
It seems no matter what I do, the entities are listed as ‘unavailable’ in Home Assistant. Here is my config file:
media_player:
- platform: linkplay
host: 192.168.1.252
name: Console Player
volume_step: 5
uuid: "FF9700169D79193339EF44F3"
icecast_metadata: "StationNameSongTitle"
multiroom_wifidirect: False
sources: { "line-in": "Record Player", "bluetooth": "Bluetooth" }
common_sources: !include linkplay-radio-sources.yaml
- platform: linkplay
host: 192.168.1.237
name: Kitchen
icecast_metadata: "Off" # valid values: 'Off', 'StationName', 'StationNameSongTitle'
sources: { "bluetooth": "Bluetooth" }
common_sources: !include linkplay-radio-sources.yaml
uuid: "FF9700169841A4CB6A81120D"
Can you advise?