Alexander Groß

In the OP I was referring to the stub server that provides examples for the frontend people.

Yes, I think so. Answering this while boarding an airplane. Cannot check my project's source code right now.

Unstale

Sure, see attached files: [kodi.0.json.zip](https://github.com/ioBroker/ioBroker.lovelace/files/8853858/kodi.0.json.zip) [alias.0.kodi.json.zip](https://github.com/ioBroker/ioBroker.lovelace/files/8853863/alias.0.kodi.json.zip) The alias was created based on what I understood from the type-detector. Not the easiest code to understand!

Unstale

The LL builtin media player card only sends [`media_play` or `media_pause`](https://github.com/home-assistant/frontend/blob/a9d44fcb6128207d8b2e43f997b996170b371a39/src/data/media-player.ts#L336-L346). Both commands are not registered by ioBroker.lovelace, only `media_play_pause`, which might a legacy way of handling play/pause. I also...

After some more research: * > * Progress bar: only updated sometimes Doesn't work because if `media_position` is updated, `media_position_updated_at` also needs to change (e.g. by assigning `state.lc` or a...

I've got a dirty hack in https://github.com/agross/ioBroker.lovelace if you are interested. Fixes the problems mentioned above (except repeat).

@Dalmapalma The relevant parts are in the "Testing" commit by me here: https://github.com/agross/ioBroker.lovelace/blame/master/lib/converters/media_player.js#L124 The ioBroker state responsible for play and pause needs to be detectable by ioBroker's type-detector, see here:...

This is my `media.state` role: https://github.com/agross/iobroker-scripts/blob/master/home/Automation/Media_Player.ts#L135-L148 As you can see there is a mapping for the read side from `kodi.0.state` to the alias where what Kodi calls `play` is translated...