Reply to thread

Message: <blockquote data-quote="TritonT" data-source="post: 281649" data-attributes="member: 26020">Hi Patrick,I have been using the plugin as my main means of interacting with my xAP network for more than a year.  v2.0i is working very well, I have it installed on more than a dozen computers in 4 different networks.  It is being used with X10, 1-Wire, iButton, raw devices (Netiom), cameras, Bluetooth and PSTN / VoIP telephony.The one area users would really like more functionality is OSD Messages.  I currently use message.display to put up a wide range of messages, caller ID, doorbell pressed, internet connectivity lost, asterisk status, etc.The main request being that messages 'stack' instead of disappearing after a number of seconds.  This is really useful when returning to the house, you can step back in time to see who has phoned you and in my setup see who has called to the door (I have a camera triggered by xAP from a doorbell press).  I was thinking that using the line 'Duration=0' could signify that the message was to remain up until 'Back' on the remote was pressed. 'Duration=5' etc would be unaffected.Another request has been to have a sound trigger with the OSD Message.  Last year you kindly added 'Image=' to message.display to enable different icons to be displayed depending on the message contents.  Would there be any possibility of adding 'Sound=' as well.  I realise this means deviating from the schema a bit, I have already checked that adding 'Sound=' does not break any other possible targets for a message.display.As all my OSD Messages are scripted out of xAP Floorplan I can make them any format I like, the following is my suggestion for a valid format:xap-header{v=12hop=1uid=FF456200Class=message.displaySource=mi4.floor.EPIA-800Target=MEPO.BHAConn.Abit-ic7.OSD.1}Display.text{Line1=Line2=Line3=Line4=Priority=Duration=}Display.look{Image=Sound=}Also, I don't think 'Pic=' works in v2.0i, but this isn't important as 'Image=' still works fine.Thanks!</blockquote>

Verification