Announcement

Collapse
No announcement yet.

CallerID name and number in the Subject of an email plus number of rings

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Raptor
    replied
    Originally posted by DavidG View Post
    Son of a gun, that works. UltraCID is house code [ in my system, so had to use that instead.

    How about number of rings? i don't think there's a device for that one.

    Can you point me toward documentation about the $$DS: function? What other innards can I get to with that or similar functions? I suspect you've awakened me to a whole realm of possibilities....

    Thanks!
    Hi David,

    Sorry for not getting back to you sooner.

    This info is from the homeseer manual under the help section then Using replacement Variables:
    Code:
    [B]Using Replacement Variables[/B]
    
    Replacement variables are a series of special characters that you can use in text being spoken or in the subject or body of an email.  When HomeSeer encounters one of these variables, it substitutes the information indicated by the variable in place of the variable.
    [B]Example[/B]
    
    hs.Speak "The time is $$time"
     
          Results in (at 11AM):  "The time is <say-it type="time"> 11:00 AM </say-it>"
    Or to do the same without the prosody/pronunciation tag:
    hs.Speak "The time is $time"
          Results in (at 11AM):  "The time is 11:00 AM"
     
    [B]HomeSeer Replacement Variables[/B]
    
    [B](Replacement Variables are Case Insensitive)[/B]
    
    <!--(Table)=========================================================--><TABLE class=whs2 cellSpacing=0 summary="   " width="100%" x-use-null-cells><SCRIPT language=JavaScript><!--if ((navigator.appName == "Netscape") && (parseInt(navigator.appVersion) == 4)) document.write("</table><table x-use-null-cells cellspacing='0' width='100%' border='1' bordercolor='black' bordercolorlight='black' bordercolordark='black'>");//--></SCRIPT><COLGROUP><COL class=whs3><COL class=whs4><TBODY><TR class=whs5 vAlign=top><TD class=whs6 width="9.9%">$date
    </TD><TD class=whs7 width="90.09%">Replacement is the current date in long format, e.g.: April 1, 2006
    </TD></TR><TR class=whs5 vAlign=top><TD class=whs8 width="9.9%">$time
    </TD><TD class=whs9 width="90.09%">Replacement is the current time in 12 hour format, e.g. 2:00 PM
    </TD></TR><TR class=whs5 vAlign=top><TD class=whs8 width="9.9%">$$date
    </TD><TD class=whs9 width="90.09%">Replacement is the same as $date, but it is wrapped with the SAPI context tag for date so the text to speech engine knows it is a date being spoken.  Use $$date when the output is going to be spoken.
    </TD></TR><TR class=whs5 vAlign=top><TD class=whs8 width="9.9%">$$time
    </TD><TD class=whs9 width="90.09%">Replacement is the same as $time, but it is wrapped with the SAPI context tag for time so the text to speech engine knows it is a time being spoken.  Use $$time when the output is going to be spoken.
    </TD></TR><TR class=whs5 vAlign=top><TD class=whs8 width="9.9%">$from
    </TD><TD class=whs9 width="90.09%">Replacement is the email address of the last email received.
    </TD></TR><TR class=whs5 vAlign=top><TD class=whs8 width="9.9%">$$DV:(address)
    </TD><TD class=whs9 width="90.09%">Replacement is the VALUE of the device indicated by (address).  For example, if the device at address R40 has a value of 100, then using $$DV:R40 in the text will result in 100 after the substitution.
    </TD></TR><TR class=whs5 vAlign=top><TD class=whs8 width="9.9%">$$DS:(address)
    </TD><TD class=whs9 width="90.09%">Replacement is the STATUS of the device indicated by (address).  For example, if the device at address S39 has a status of "Disarmed", then using $$DS:S39 in the text will result in "Disarmed" after the substitution.[LIST][LIST][*][B][B]Note[/B][/B]: HTML used in the status may result in problems when the replaced text is spoken.[/LIST][/LIST]</TD></TR><SCRIPT language=JavaScript><!--if ((navigator.appName == "Netscape") && (parseInt(navigator.appVersion) == 4)) document.write("</table></table><table>");//--></SCRIPT></TBODY></TABLE>
    I have not been able to get access to the number of rings yet. I have a post open about that.

    Hope that helps

    Raptor

    Leave a comment:


  • DavidG
    Guest replied
    Son of a gun, that works. UltraCID is house code [ in my system, so had to use that instead.

    How about number of rings? i don't think there's a device for that one.

    Can you point me toward documentation about the $$DS: function? What other innards can I get to with that or similar functions? I suspect you've awakened me to a whole realm of possibilities....

    Thanks!

    Leave a comment:


  • DavidG
    Guest replied
    Originally posted by Raptor View Post
    Hi David,

    i use the homeseer email feature by accessing the variables directly:
    From: $$DS:^4
    Number: $$DS:^5


    there is also a series of groups that you can trigger events from, that might help with what you are trying todo. The groups are located in the ULTRACID plugin

    Raptor
    OK, so tell me more about $$DS:^4 and $$DS:^5. These are notations that allow an UltraCID variable to be used within the standard homeseer email function? So I can use (for example) $$DS^4 as a part of the sentence I use within the body of the email I want to send, and it will replace that with the caller ID number? If not, how do I use this notation?

    regarding the UltraCID groups, they don't reliably work...see my other post: http://board.homeseer.com/showthread.php?t=146879 which is as of yet unresolved.

    Leave a comment:


  • Raptor
    replied
    Originally posted by DavidG View Post
    @raptor - Are you saying that the UltraCID variables for the call details that UltraCID generates (# of rings, caller ID, caller name, etc) are available within the standard HS email send action? Without access to those details, I would need to set up a million separate events to handle the various unique incoming callers. And I still wouldn't get details for a new caller.

    Hi David,

    i use the homeseer email feature by accessing the variables directly:
    From: $$DS:^4
    Number: $$DS:^5


    there is also a series of groups that you can trigger events from, that might help with what you are trying todo. The groups are located in the ULTRACID plugin

    Raptor

    Leave a comment:


  • DavidG
    Guest replied
    @raptor - Are you saying that the UltraCID variables for the call details that UltraCID generates (# of rings, caller ID, caller name, etc) are available within the standard HS email send action? Without access to those details, I would need to set up a million separate events to handle the various unique incoming callers. And I still wouldn't get details for a new caller.

    Leave a comment:


  • Raptor
    replied
    @David,

    what you want can be done using events. You just spcify the trigger as UltraCID incoming call and the action as send an email.

    Raptor

    Leave a comment:


  • DavidG
    Guest replied
    Any chance for specifying the email destination for notifications in the event action?

    I use this to text details about incoming calls to my cell. Some members of the household would like details about all calls whereas others only want details about certain calls. To do that I either have to make up a million individual events, one each for the various callers.

    In the alternative, could UltraCID variables like caller ID and number of rings etc. be made available to the standard "send email" event action?

    Leave a comment:


  • Raptor
    replied
    Hi,

    this has been workign great but could you add the ability to add the number of rings to HSTouch?

    thanks
    Raptor

    Leave a comment:


  • Raptor
    replied
    Have not tested the rings yet but the subject line is working a charm!!

    Leave a comment:


  • Monk
    replied
    I see the same circumstance as DavidG -

    Leave a comment:


  • DavidG
    Guest replied
    I added a wait, and it's OK

    FYI - I added a 1 min wait to the actions before the email action, and it seems to be doing fine that way. It takes a while for the notice to go out but the number of rings is correct.

    Obviously if there's a more elegant answer based on the call actually ending, that would be better. This way it means a 1 minute wait before it sends every email, even if the call was dropped 55 seconds earlier. And potentially, another call (or calls) could be received and end during the minute the wait is happening, in which case the first call's email notice might be sent with details that actually came from the other call.

    Leave a comment:


  • DavidG
    Guest replied
    New problem with $rings

    Ok, new problem. I am sending an email on incoming call and I am including $rings in the body. Problem is, the $rings variable always returns "1" since the trigger available is on on the start of a call..."incoming call"...

    How about a trigger based on End of call - if the modem knows that? Or a condition that indicates that there's no call/ last ring time was more than 1.5*(normal ring plus silence time)? If I could send the email at the end of the call, I'd be in good shape I think. Otherwise I have to trigger on incoming call, but put in an arbitrary wait equal to the maximum no-answer time before sending the email maybe the $ring would be right?

    Leave a comment:


  • DavidG
    Guest replied
    very nice! I'll try it out.

    Leave a comment:


  • Raptor
    replied
    awesome thanks!

    Leave a comment:


  • Monk
    replied
    Nice!
    Thank you very much.

    Leave a comment:

Working...
X