I see on your website you have the request that I was just going to request 
“Ability to send message to an Android Client using LAN, bypassing Google’s C2DM”
Any update on that?
Thanks!
I am doing an upgrade to VeraAlerts in the next week.
I will consider the options at that time.
Great plugins you are putting together. Keep it up!
Sent from my SPH-D710 using Tapatalk 2
am I the only one who tested vera alert plug-in and can’t use differend alert sounds?
with {tone:1}, {tone:2} . {tone:3} in de message it’s play always de sound of tone:1
Did you configure the sound in your Android phone for these additional tones ?
It’s at the bottom of the settings page … you have to scroll down.
Does it show the number for the tone in the message list ? It’s the left most column of data.
i have found the problem. a grappy app installation.
I deinstalled the app and installed it again en then de app was working . It did crashing also if I deleted a notification.
I’ve been using Vera Alerts for a couple weeks and really like it. Since you asked for feature requests, I have some that may or may not be worth considering:
[ul][li]Horizontal rule separator between Days (midnight)[/li]
[li]I’d like one Alert level (or tone) that is effectively “Log, but do not Notify”. I’d like to see the event listed for context, but no new Android alert or vibe[/li]
[li]Quick option to “delete yesterday’s events”[/li]
[li]Bug fixes for the ‘sorting’ (new events appear at the wrong end when the app is open)[/li]
[li]Option to sort in reverse date order (New to old, vs old to new)
[/li][li]There’s some strange color changing of the background color when the app is used… teal or yellow, depending on touch?[/li]
[li]It would be great if the Plug-In and App had some kind of ‘heartbeat’ handshake, where a periodic (15m?) event went out to the app. The App could then Notify if no heartbeat was heard recently, alerting me to failed networking or stale data.[/li][/ul]
Some one just told me about this app… about to install it.
It looks really handy , hopefully the next update can play mp3 sounds
Cor
[quote=“Cor, post:48, topic:172920”]Some one just told me about this app… about to install it.
It looks really handy , hopefully the next update can play mp3 sounds
Cor[/quote]
It can. Create a directory on your SD called “Notifications”, and put your MP3 in it. Then in the app, select it as one of the tones, and call it with the luup code. You can only have 5 of them right now though.
Sent from my Galaxy Nexus using Tapatalk 2
Also bug fix request: Verify that Recipient as a User name is supported (and correctly maps to multiple space-delimited Vera IDs). Seems to be broken. (User name never translates to ID.)
Thanks again for Vera’s best plug-in!
I’m buying up used/cracked/outdated Android devices just for this.
I am not sure I understand this … can you send me some more details about your configuration.
Sure. There’s this thread describing it in more detail:
http://forum.micasaverde.com/index.php/topic,12992.msg96023.html#msg96023
I’m trying to associate one User with multiple Vera Alert IDs (space-delimited list), but then none of the messages go out to the Android phones.
It works correctly if I list multiple Vera Alert IDs directly, just not indirectly via User name.
Hello,
@signal15: thanks, I initially thought it was not possible
Today I played with this app… what an insane programm… so cool!! Altough I didn’t think it was very easy to setup , it took me quite a while to understand it. I am planning to use it initially as a kind of doorbell.
Playing a sound works fine, I setup a mp3 sound for alert1 , but how do I tell vera to play alert 2-5?
On the device tab i can just select “notify this user for a device on or off”
I am also not able to use the text to speech option, I tried the “howto” from a message in the beginning of the thread , but it’s too complicated for me 
can someone go into more detail for me?
[quote=“signal15, post:8, topic:172920”][ul][li]Installed IVONA text to speech engine from the market[/li]
[li]Installed the IVONA “Amy” voice (sexy british accent, and very good quality. Difficult to tell it’s synthesized). I could have used the built in Android TTS engine/voices, but this one is way better[/li]
[li]Installed SetCPU to prevent the CPU speed from going below 1113mhz to keep the phone responsive (not required)[/li]
[li]Go under the wifi settings, join it to your network. Click the menu button and select “Advanced”. Set a static IP for the phone, and change the power saving settings in this screen so the Wifi will never turn off[/li]
[li]Install Vera Alerts from the android market[/li]
[li]Start Vera Alerts, click menu, click Register to register it with google’s C2DM service [/li]
[li]Install VeraAlerts from the Micasaverde app store [/li]
[li]In the Vera Alerts device created on Vera, edit it, and put in the Device ID listed in the VeraAlerts app on your android device [/li]
[li]Send a test message [/li][/ul]
Now you’re ready to use it. I created a new scene called Voice Alerts. I did not select any devices for it. But, I create a trigger for each voice announcement I want, and after the trigger is created, I put the LUUP code in the trigger event rather than in the LUUP tab for the scene. This way, you can have one scene for voice alerts instead of one for each one. For example, I have a trigger for when the front door is tripped, and the LUUP event is:
luup.call_action("urn:richardgreen:serviceId:VeraAlert1", "SendAlert",
{Message = "{tone:2} Front door has been opened.", Recipients = ""}, 46)[/quote]
Ivona : done
installed a voice: done
setcpu: nope not done
static ip and powersaving: not done
veraalerts : installed and working fine with "notification 1
vera alert device page : ID iserted.
create a new scene: done
click trigger: done
the only option I have than is to select a device, otherwise I will not have the luup option ïn the trigger event
I selected device #40 (wallplug) and selected to notify when the device is on
than there is an option "luup event"where I can insert this code:
luup.call_action("urn:richardgreen:serviceId:VeraAlert1", "SendAlert",
{Message = "{tone:2} Front door has been opened.", Recipients = ""}, 40)
I changed the device ID to 40
When I activate the scene, nothing happends.
when I switch the wallplug on, nothing happends
Where do I go wrong, since there are so many variables here :-/
hope someone can help ,
Many thanks,
cor
To use different tones for your notification, goto the Vera Alerts Additional Configuration tab.
You will have to override the default message for your notification:
In your message string add:
{tone:N}
where N = 1 to 5
Don’t forget to save.
I am also not able to use the text to speech option, I tried the "howto" from a message in the beginning of the thread , but it's too complicated for me :-( can someone go into more detail for me?If you just want it for a particular message add: {tone:tts} If you want all messages to speak, you can do this from the Android phone. In [b]Vera Alerts[/b] goto the settings page. Check the [b]Override Alert Tone[/b] Set the [b]Message Repeat Count[/b] as appropriate. A value of Zero, will play the message with no repeats. Set the [b]Message Repeat Delay[/b]. This should be at LEAST 1. If it is zero ... change it to one and REBOOT the phone. This is a bug that I will fix shortly. This is the time between messages (including repeats).
hmm, no joy yet with the tts:
the " {tone:tts} " where do I insert this ,also in the " Vera Alerts Additional Configuration tab" or do I do this in the LUA code?
This LUA code is correct in my case?
luup.call_action("urn:richardgreen:serviceId:VeraAlert1", "SendAlert",
{Message = "{tone:2} Front door has been opened.", Recipients = ""}, 46)
thanks,
Cor
Well there are lots of way to send an alert.
You can do it from a Notification for a device and/or scene trigger.
In that case the Additional Configuration tab of Vera Alertsallows you to override the default message for the notification. There is where you would include {tone:tts}.
You can also send an Alert from luup code.
In the case of the code you supplied: replace the {tone:2} with {tone:tts}.
You are right about the complexity … but it’s there to support the various types of usage that people want.
signal15, I’m going to give that a try – coding Luup directly is so much easier than a bunch of opaquely associated data bits in Trigger/Notification/Configs.
Is there any way to set global variables in UI5? I’d like to set the recipient list once in a piece of code somewhere, and then reference that from each of my call_actions() invocations through the system.
I’m not sure where to set global variables, but something like:
local HOME_VOICE = “xcvb09g9df adfb99df8”
local HOME_URGENT = HOME_VOICE … “0b0sd8fd0s8f”
and why not the Device ID as well:
local VERA_ALERT = 19
Then something like:
luup.call_action(“urn:richardgreen:serviceId:VeraAlert1”, “SendAlert”,
{Message = “{tone:2} Front door has been opened.”, Recipients = HOME_URGENT}, VERA_ALERT)
hard-coding the ID strings everywhere seems prone to error and hard to update. Is there something like a master prepended “header”, autoexec.bat, bashrc, profile, something like that?
The device ID in the LUUP code for the voice alert should be the device ID of the “Vera Alerts” device, not the ID of your wallplug.
@ Signal15: thanks , that’s allready one error gone I left the luup code for the moment, I first want my phone to talk to me , since I understood from RichardTSchaefer it was possible from the device setup and veraalerts without the luup code…
@RichardTSchaefer: something is going wrong here
I deleted the scene/trigger with the luup code since I understood it was possible with the device setup and veraalerts only as well.
I do recieve on my cellphone a notification and when I click that notification there is a “t” with the time it has been activated , but there is no sound.
Attached 2 screenshots, one from veraalerts and one from the device. What else needs to be done? or needs something to be done on my cellphone (samsung S3)
Many thanks for your help,
Cor
I believe the problem is on the Phone side.
Check the Settings: Message Repeat Delay.
You probably have this as ZERO. Change it to a number greater than 0, like 1.
Then cycle the power for the PHONE … It must reboot to reset the TTS engine.
This bug is fixed in the next Vera Alerts Android release.