[quote=“RichardTSchaefer, post:19, topic:172920”]The android TTS engine supports the ability to associate a list of text strings to local sound files.
When it sees the text it plays the sound file instead of synthesizing it.
I can add the ability to configure this to the Vera Alert Android app.
Then, for example, when you send the string fragment “BAD DOG” it will be spoken in the voice you use when the dog is doing something wrong![/quote]
I found a potential bug with the Android app. I have my delay set to 0, since I want to be notified of everything right away. If it is speaking, and another message gets sent to it while it’s speaking, it stops speaking the first message and speaks the second one. Shouldn’t it queue the second message and speak it when the first is done?
For example, I have a scene that speaks the current weather when my alarm is disarmed in the morning. This morning, I opened the front door while it was still speaking the weather, and the message that my front door was opened was sent. It stopped speaking the weather and notified me of the front door.
There are 3 components … Not sure where the problem is.
[ol][li]Vera Plugin
The problem could be that the string is NOT URL encoded properly. I added a lot to this over the original plugin … Which version of the plugin are you using[/li]
[li]The VeraAlert C2DM gateway
I do not have access to this … setup by the original author … not sure if there is a problem here.[/li]
[li]The VeraAlerts Client
Is it delivered to the phone and not handling the language strings properly.
[/li][/ol]
If that is the URL for the message that did not get delivered … than it looks like it [2]
The urlencoding in vera plugin looks ok so I would also guess on (2).
Do you have any contact with the original author? I could probably help out fix it in the gateway.
He supposedly gave me access to this … But I was not able to connect.
I can dig through the emails and see if I can figure it out.
I think he has other priorities … I have a few unanswered messages to him.
[quote=“RichardTSchaefer, post:27, topic:172920”]He supposedly gave me access to this … But I was not able to connect.
I can dig through the emails and see if I can figure it out.
I think he has other priorities … I have a few unanswered messages to him.[/quote]
So does Vera Alerts rely on a 3rd party server in addition to Google to work?
My HP TouchPad runs CyanogenMod 9 which is a version of Android IceCreamSandwich that runs on the HP Touchpad. It basically turns it into an Android tablet. With the CM9 latest nightlies, now the microphone and audio fully works. Work is progressiing on CM10 which is Android JellyBean.
The standard Android version of Vera Alerts runs on it just fine, as do AuthomationHD, HomeBuddy and imperihome. I’m trying to come up with a wall mount as the unit is charged via an inductive charging stand. So I can slip it onto the wall mount when not in use and it’s being charged.
[quote=“RichardTSchaefer, post:25, topic:172920”]There are 3 components … Not sure where the problem is.
[ol][li]Vera Plugin
The problem could be that the string is NOT URL encoded properly. I added a lot to this over the original plugin … Which version of the plugin are you using[/li]
[li]The VeraAlert C2DM gateway
I do not have access to this … setup by the original author … not sure if there is a problem here.[/li]
[li]The VeraAlerts Client
Is it delivered to the phone and not handling the language strings properly.
[/li][/ol]
If that is the URL for the message that did not get delivered … than it looks like it [2][/quote]
Did you perhaps put a filter on the plugin so it no longer works with google talk? I saw the plugin in the app store and downloaded it over the previous version. With the original you could send an alert to my.email@gmail.com and the gateway apparently would know to send the message via googletalk rather than to the app on the phone directly. That doesn’t seem to work anymore with your version of the plugin. Since the gateway is the same i assume you put a filter on the plugin?
[quote=“ragmondo, post:26, topic:167861”]NEW UPDATE **** FOR USERS OF ANDROID < 2.2 (and also just google talk users in general - no phone needed!)
I have made an update to the server side so that you do not need a later version of android, or in fact any phone at all.
When setting up the Vera Alert virtual device, you just put your google email address as the “ALERT ID” recipient instead of the alert ID generated by the app.
The message is sent via the “google talk” protocol, so the first time you will be invited that “VeraAlert@vera-alert.appspotchat.com” wants to talk to you - you MUST accept this or you won’t receive any messages.
From then on , messages will be sent as if someone is talking to you
I have to ask, Can this be ported to the iPhone???[/quote]
if there’s a googletalk app for the iphone than the plugin can send messages (if things get tweaked) but it wont read outload or do any of the fancy add on type things that the android app does. That would need someone to port the mobile device app over.
Richard - first off I need to say thanks. I’ve been using Vera Alert(s) for over a year and love it. Thanks for picking up the baton and keeping it alive and moving forward. (And as someone who switches phones about twice a year for work, I like being able to reuse the device identifier rather than reprogram all my scripts!)
I do have one quibble, the new Android app doesn’t sort the alerts by date and time. Any chance we can get that back as an option? (or is it already there and I missed it?)