Jump to content

Search the Community

Showing results for tags 'DisplayMessage'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 1 result

  1. Very similar to this thread and this thread which was marked complete but never really rectified... I've unfortunately got the same problem. In short: I can authenticate without a problem (with the Emby API) I can retrieve the active Sessions but when i try to post to the browser based one I have open using: http://<emby host>/Sessions/<my emby browser session>/Command/DisplayMessage It successfully posts (returns a 204) and triggers a modal popup box with none of the content i passed in with the post. I also even passed in TimeoutMs which is supposed to over-ride the Modal setting. Emby is actioning the DisplayMessage correctly but it isn't parsing the payload as part of the POST Now according to this wiki page it states: To which it also states: I am definitely posting the application/json properly in the header along with all of the other required entries (X-Emby-Authorization and X-MediaBrowser-Token). I also assume this because I can query for active sessions in addition to actioning the Message itself. { "Arguments": { "Header": "Test Header", "Text": "My Test Message Body", "TimeoutMs" : 10000, } } I tried without the Arguments too since googling seems to turn up results of people polling Emby that way. But this yields the same result (a successful post, a successful event driven popup on the browser side, but no content - see attached screenshot): { "Header": "Test Header", "Text": "My Test Message Body", "TimeoutMs" : 10000, } I was just curious what I'm doing wrong here? My goal is to integrate this with Apprise which powers my NZBGet and SABNzbd plugins. I attached a screenshot of the Emby instance I'm connected too (via the browser) and what the pop-ups look like after it spawns. I tried to highlight in the Firefox inspector where i believe the text is supposed to go. I'm using a simple docker container based on emby/embyserver:latest (documented here). I'm wondering if it's just a lack of documentation or a small over-sight on me? Any help would be fantastic!
×
×
  • Create New...