Messaging system (API) strange behaviour.

[chef 3810]

Hi!

 

I noticed something interesting with the SendMessage call in the API.

 

Using the Webclient, if I send a message once it works and I get a popup in the lower left hand corner containing my message.

 

If I try to send another message, it will not show until the browser is refreshed/reloaded.

 

Is this common?

 

Also, does the messaging system work for clients like Xbox one?

[Luke 42077]

It should work for xbox yes

[chef 3810]

Luke,

 

I have created a call display plugin for emby.

 

It works really well using an old modem.

 

I take the serial port and ready the bytes of information into the caller name and number.

 

I was going to build a contact list people could edit in the plugin config.

 

How is it possible to work around the fact that the Webclient needs a refresh to show another message?

 

I don't see the popup in Xbox either. Is it better to send a message to users, devices, or just SendMessage?

Edited November 1, 2016 by chef

[chef 3810]

I decided after attempting a plugin I wanted more diverse functions with my call display app. So I built it standalone.

 

I wanted to add the ability for system.speech to announce calls and I the COM port was being used by emby I couldn't announce calls through another app.

 

When building a standalone app the ApiClient only has "SendMessageCommand"

 

This is very intrusive in the UI.

 

You have to press the "Got it" button to make the message disappear.

 

Does the "SendMessageCommand" class actually honour the "TimeoutMs" property?

[Luke 42077]

You can specify the timeout and it is up to each app individually to decide how and if to support that.