Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQTT: missing image/title on webstream assigned (custom) Tonies #194

Open
ks61625 opened this issue Jul 3, 2024 · 2 comments
Open

MQTT: missing image/title on webstream assigned (custom) Tonies #194

ks61625 opened this issue Jul 3, 2024 · 2 comments

Comments

@ks61625
Copy link

ks61625 commented Jul 3, 2024

Whenever I place a (custom) tonie on a box, with radio-web-stream assigned, mqtt points to default "teddy" picture. Although there is a record in tonies.custom.json with an available image-source path, it wont get transfered via mqtt.

I guess it has to do with the missing "audio_id" in tonies.custom.json. Since the audio_id seems to change every time you place the webstream-tonie on the box, there is no chance to define one in tonies.custom.json.

So...maybe mqtt should use the path directly (if there is one), instead of using a maping by audio_id (just guessing)??

Also: sensor.box_content_title shows just "Unknown". It should be the title or series defined in tonies.custom.json as well, I guess.

@ks61625 ks61625 changed the title MQTT: missing image on webstream assigned (custom) Tonies MQTT: missing image/title on webstream assigned (custom) Tonies Jul 3, 2024
@meiser79
Copy link

Could you maybe use "StreamTitle" from the ffmpeg output as title?

@SciLor
Copy link
Contributor

SciLor commented Oct 4, 2024

Could you maybe use "StreamTitle" from the ffmpeg output as title?
This is not possible, as we do not have that within teddyCloud.

We need two separate blocks: One for the model selected, one for the actual content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants