Send alerts to Airplay or DLNA?

n0ir · July 13, 2015, 5:17pm

Hi!

I have some difficulties getting the VeraAlerts app working continuously on my Android devices. I have a tablet and a phone, and both Vera-Alerts-Mobile and Vera-Alerts-LAN profiles seems to stop working properly after a while. I don’t know if this is caused by the app on my Vera, the Android devices or my network. I don’t really care either, I just want a robotic voice telling me my wife have arrived home using geofencing…

I have bought a small device that plugs in directly to a set of speakers, making them Airplay and DLNA combatibel (http://www.uyesee.com/us/products/audio/2014/0807/21.html). My thinking was trying to use these instead around the house.

My two questions:

Can I create a VeraAlerts profile that send alerts to a Airplay or DLNA device? Is there a better way than VeraAlerts?
If yes, how? I have the DLNA Media Controller app to control my HTPC running Kodi. I haven’t used this to send alerts though.

RichardTSchaefer · July 13, 2015, 8:36pm

You can use the Plugin Forwarding profile to send alerts to any device that responds to a luup.call_action command.

You can probably fix your Mobil by running a tasker task to periodically disable/enable Wifi.

n0ir · July 22, 2015, 2:18pm

Could you please expand on what I should use in the specific settings?

I have:

ForwardedPluginDeviceID
ServiceID
Action
DefaultArgs

I assume ForwardedPluginDeviceID should be the device ID of the DLNA device created with the DLNA Media Controller app?

What should I use under ServiceID, Action and DefaultArgs?

I have read several users trying to get Vera send notifications to DLNA devices. Maybe add the information in your guide (Vera Alerts - Vera Plugin for Notifications)?

RichardTSchaefer · July 22, 2015, 6:02pm

Send me the arguments you would use via a call to luup.call_action for the DLNA device to get the notification you desire … and I will tell you how to setup Vera Alerts to use plugin forwarding.

n0ir · September 12, 2015, 8:31pm

I seem to have missed using the notify feature on this thread…

Could you please look at lolodomos manual for the DLNA Media Controller (DLNA Media Controller) and let me know if there is a possibility to add a DLNA device as a profile?

For example, when using VeraMate, I needed to add this to a Plugin-Forwarding-profile:

ForwardedPluginDeviceID: 8
ServiceID:urn:veramate-com:serviceId:VeraMatePN
Action:SendAlert
DefaultArgs: Msg=“{Message}”

What do I need to add in the fields for a DLNA device?

RichardTSchaefer · September 12, 2015, 10:52pm

Send me some LUA code to do a message to your DLNA device and I will translate that into Forwarding Profile arguments.

n0ir · September 12, 2015, 11:09pm

I don’t quite understand what that means, but there is some snippets of LUA in the URL I provided (DLNA Media Controller):

[b]Making a renderer say something[/b]
The DLNA Media Controller plugin exposes Text to Speech capability through Google’s service. The functionality is exposed declaratively through the Say action under Advanced Scenes. The functionality is also exposed programmatically via Lua code.

To play a message, use this lua code:

luup.call_action("urn:dlna-org:serviceId:DLNAMediaController1", "Say", {Text="The sun shines outside", Language="en"}, 666)This action will pause the current playback, say the text, and then the playback will be resumed. Language is a string of 2 characters, like en, fr …

To play a message setting the volume for the message at level 60:

luup.call_action("urn:dlna-org:serviceId:DLNAMediaController1", "Say", {Text="The sun shines outside", Language="en", Volume=60}, 666)
The volume will be adjusted to play the message, and finally restored to its previous level. When the Volume parameter is not used, the volume is not adjusted and the message is played with the current volume.

To play a message using your personal OSX TTS server rather than using Google Internet service:

luup.call_action("urn:dlna-org:serviceId:DLNAMediaController1", "Say", {Text="The sun shines outside", Language="en", Engine="OSX_TTS_SERVER"}, 666)
Two accepted values for the engine: “GOOGLE” for the Google Internet service and “OSX_TTS_SERVER” for a personal OSX TTS server.

In addition, the Text to Speech capability can be setup with the following variables (use the TTS tab to adjust the values):

DefaultLanguageTTS - default language used when calling the Say action; must be a string of 2 characters
DefaultEngineTTS - default engine used when calling the Say action; must be either GOOGLE or OSX_TTS_SERVER
OSXTTSServerURL - defines the location of your OSX TTS server; something like http://www.mypersonaltts.org:80
Notes:

Google service may be removed at any time
Explanations on how to setup the OSX TTS server: Wolf Paulus' Journal, thoughts and ideas on technology
Parameters not specified will default internally. (Language=en, Engine=GOOGLE, Volume=nil) By default, the volume is not set.

RichardTSchaefer · September 13, 2015, 1:11pm

For the forwarding profile the Service ID is obvious it is
urn:dlna-org:serviceId:DLNAMediaController1

The Action is
Say

The DefaultArgs is something like:

 Text="{Message}",Language="en"

or
Text=“{Message}”,Language=“en”, volume=60
or
Text=“{Message}”,Language=“en”, Engine=“OSX_TTS_SERVER”

The ForwardedPluginDeviceID is the Vera Device ID for your DLNA device. (i.e. 666 in your example)