#Message client & Kill stream message issue on Jellyfin
1 messages · Page 1 of 1 (latest)
Thanks for opening a support thread!
Please include the following so we can help:
• Tracearr version
• Environment (Docker, LXC, Unraid, etc.)
• Docker compose file
• Logs (pastebin.com) or screenshots
• Expected behavior
• Actual behavior
• Steps to reproduce
- Tracearr v1.4.22
- Truenas scale (docker)
Don’t forget to add your compose file and logs.
I use truenas so i dont have any compose file
And nothing in the logs
But you said your deployment is docker above?
Yep, truenas use docker
But you don’t use compose?
Technicaly, I do. But I can't share you the compose file, it's "auto generated"
https://apps.truenas.com/catalog/tracearr/
👀
Can you also share the full rule?
cant really tell if the rule is setup right without seeing it
Ok, fair enough. I don’t know enough about TrueNAS, but the devs will almost certainly want to see the logs as well.
yep sorry, I forgot the most important part 
I also tried "Message client" alone with "Triggering session" or "All sessions"
messaging is fairly unreliable on jellyfin and emby
The stream is correctly killed, but the message isn't showing up
as you cant kill the stream with a message
so behind the scenes we send the message- wait a small bit then kill it
ok I see, so there's nothing I can do ?
its really on JF side - its reliable on plex because you can stop with a message
does it work from the dashboard?
yes
so it shows a message on dash, not in the rule?
Ok sorry for the confusion :
- When rule actions are executed, the stream is killed correctly and I see indeed messages on the tracearr dashboard telling that action was executed (screenshot)
- When I send a message with Jellyfin dashboard, I can see the message but when I send a message with Tracearr rule, nothing

you are still confused
on the stream on the Tracearr dashboard - when you kill the stream (via the "X" on the Tracearr dashboard) does the message appear for the client
nope
This was a bug ! I created a PR if you want to check 👀 : https://github.com/connorgallopo/Tracearr/pull/590/changes
yeah i already fixed it locally lol
Did you test with emby? as this effects JF and emby
no sorry
Regression testing it is the requirement for that PR to be merged, especially when it effects multiple server types
Yes I'm just lazy sorry 
I can test with Emby 
Please attach SS of the message appearing on emby - otherwise code looks good and after that ill merge
Merged 👍
, before creating an issue, i want to know if anyone has issue about "Message client" feature in rules action (for Jellyfin)