Using Hello Sena Command

Commenti

49 commenti

  • Will Adams
    Will Adams

    You are correct that when the 20S is in standby mode you should be able to say 'hello sena' and the headset should respond with 'say a command'.  If the headset does not respond with 'say a command', then the device didn't recognize your 'hello sena'.  Also if you are listening to music the device will not recognize 'hello sena'.  I've just downloaded software update 1.3 so my comments apply to version 1.2 and I don't yet know if any changes have been made to how the head set functions.

    0
  • Will Adams
    Will Adams

    After an extended ride this weekend I would say that the 'hello sena' does not work as well as it did with the 1.2 software.  With 1.2 I could get the Sena 20S to respond almost every time and with the 1.3 it seems more like 10 percent of the time it will respond.  So something seem awry with the 1.3 voice performance.  

     

    0
  • Steve Keiser
    Steve Keiser

    I am also having this issue with 1.3. It worked most of the time before I updated but only works if I just turn it on.

    0
  • Fernando de la Garza
    Fernando de la Garza

    Same problem here with 1.3. They should be looking to fix this issue.

    0
  • Kamp
    Kamp

    And also here issues with version 1.3

    0
  • Martin de Graaf
    Martin de Graaf

    Yes, it is a bit hit and miss for me also.  On speaking to the Australian agent, he did say that you need to listen to the tutorials and try to produce the same sound/say it the same e.g,. American accent to get the best results. 

    0
  • Jim
    Jim

    I am having the same issue, i thought I was crazy.  1 time out of `10 the hello sena works, then when that does work  saying a command may fail  it keeps saying  Say a command, then cancels

    0
  • Keith
    Keith

    With version 1.3, I've found that the "Hello Sena" command stops working after 60 seconds in stand-by mode on my 20S units. Saying "Hello Sena" works fine 15, 30, 45 and even 55 seconds after any activity on the units. But, once it has been allowed to sit in stand-by mode for 60+ seconds, that functionality appears to go away. This is simple to test. Simply power the unit up, immediately say "Hello Sena", say "Cancel" after the unit responds, wait more than 60 seconds after that and then say "Hello Sena" again. My units will not respond at that point. They will respond at any point up to 60 seconds. After that, I have to use the "Ambient Mode Button" or double tap the unit to use voice commands again.

     

    Both the "Hello Sena" command described above as well as the LOUD "Hello" command to answer the phone do not work for me in version 1.3. Both of these commands work fine for me in version 1.2. I spoke with Sena support and their advice was to use version 1.2 if it works fine for me. Hopefully these issues will be addressed in version 1.4.

    0
  • Will Adams
    Will Adams

    I went back to version 1.2 and the unit works much better on this and other issues that I was having with 1.3.

    0
  • Blenvid
    Blenvid

    I'm having the same issue. I was at 1.3 and recently upgraded to newly released 1.4. It still isn't working for me. I've just got in the habit of double-tapping the unit or hitting the bottom button as it does seem to respond to many of the other commands without issue, commands such as "FM Radio," "Stereo," and the "Intercom..." commands, just not "Hello Sena." Hopefully this is still being looked into...

    0
  • Jim
    Jim

    I had one of the original shipments of the 20s, after i upgraded to the 1.4 hello sena didnt work great.,I opened a ticked and they asked me to RMA my unit .  got my new uinit and it seems to work a lot better

    0
  • Keith
    Keith

    I'm working on a few issues with Sena support. The "Hello Sena" command is one of the issues. I just got this response from them regarding that issue:

    ++++++++++++++++++++++++++++++++++++++++++++++++++++

    I checked the Voice command issue and found the reason of problem.
    I forwarded this issue to our product management team.
    We will fix it next firmware

    ++++++++++++++++++++++++++++++++++++++++++++++++++++

    So, it looks like it will get fixed. However, given that the mic will always be on (not just for 60 seconds), it may reduce battery life.

    It looks like the "Hello" phone answering command (not to be confused with the "Hello Sena" command) got fixed in 1.4. But, you literally have to yell "Hello" or some other word/sound

    0
  • Barry lack
    Barry lack
    Hi,Keith thanks for your note re hello Sena not phone answer.that is what my unit does cuts out after 60 secs which I can live with had I known that was the way it would work. Sena are working with me to try and resolve Vox phone answer issue
    0
  • Blenvid
    Blenvid

    "So, it looks like it will get fixed. However, given that the mic will always be on (not just for 60 seconds), it may reduce battery life."

    Well, if this is the case, reduced battery life, I'd rather them not implement the change then. Battery life is important for me due to how long I ride sometimes. I'd rather it just require manual input with no battery loss. Better yet, a little bar mounted control unit would be best, something with small buttons that would allow one to switch between coms, radio, stereo, etc...

    0
  • Keith
    Keith

    I agree. For me, on my original S/N 14XXXX units, the mic always being on reduced stand-by battery life by 33% (~30 hours running 1.3 with mic cutting off at 60 seconds vs ~20 hours running 1.2 and the mic always on). If it's the same 10 hour difference after the fix, I'll get ~40 hours on stand-by vs the ~50 hours I'm getting now on my new S/N 15XXXX units (20% reduction). That would be less than even their new stated 2 day stand-by battery life. I sent the engineer an email to make sure he is aware that fixing the voice command 60 second cutoff may reduce battery life. They may undo an earlier "fix" for the short stand-by battery life.

    0
  • Keith
    Keith

    I got this response from the Sena engineer regarding how fixing the 60 second mic cut off seen in firmware versions 1.3 and 1.4 possibly reducing stand-by time:

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++

    Currently, the standby time is approximate 2 days with v1.4 firmware.

    I think that the Voice command feature is higher priority than standby time.
    So, we will improve this issue and try to low affect to the standby time."

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++

    They know their customers better than I. But, given the already lowered stand-by battery life expectation (10 days down to 2 days), I'd rather conserve battery life and use the ambient mode button to issue voice commands.

    0
  • Blenvid
    Blenvid

    Same Keith.

    No additional news yet on my ticket and my trouble with the "Hello Sena" command. A Sena engineer said that my motorcycle may be too loud for the 20S, and that's why I'm having trouble. I didn't think the Ducati 848 was a loud motorcycle so I don't know... My Sena 20S is installed in a full-face Shoei Multitec helmet.

    0
  • Keith
    Keith

    It's not your bike being too loud. I don't know why the Sena engineer would say that. Both of my 20S units stop responding to "Hello Sena" after 60 seconds in stand-by mode even when I'm in my house. Sena is aware of the issue. Which is why they are saying they will fix it in the next firmware version. We'll just have to wait and see how it works and what the stand-by time is with firmware version 1.5 whenever it is released and if they fix it in time for that release. Hopefully they'll mention the fix in their release notes so we don't have to update and try it to find out.

    http://www.sena.com/support/firmware/

    0
  • JHLR
    JHLR

    I do have the same issue with answering the phone. Only thing that works is just push the button. About the responding to "Hello Sena" my opinion is that I don't care about standby time I care about the time I'm using the 20S - talk time, anyway probably I'm never going to drive 2 days at a run. And even if i'm going to do so I'll use my external battery cause my smartphone will die as well in that time. So please just fix both of the problems. And if there is too many opinions in that topic this could be changeable in Sena smartphone app. 

     

    0
  • Keith
    Keith

    Hi JHLR, If you are running firmware version 1.4 and still not able to answer the phone with the LOUD "Hello", then maybe it wasn't version 1.4 that got it working for me. Maybe it was simply my 2 replacement 15XXXXX units that fixed the problem. In any case, I won't use that feature as you really have to yell way too loud for it to respond. I'll just use the jog dial or phone button.

    0
  • JHLR
    JHLR

    My units are 1503 ones so they are quite new. I'm pretty sure that FW is 1.4 but I need to try again it with very loud voice. So for example yesterday I was on slow but quite technical  raceway and I can tell I really didn't want to  use the buttons while I was driving. Anyway I hope they gonna fix it and it would be very useful if i could cancel/dismiss the call as well with my voice command. For example saying just NO or smth.

    0
  • Wz4i
    Wz4i

    Hello Sena....

    https://www.youtube.com/watch?v=nLISRnHPnWg

    0
  • Kym Moulds
    Kym Moulds

    For what it's worth I have the exact same problem with my SENA 20S.  I thought that it was the mount until I tested my second helmet with a 20S mount and the same thing happened.  I then got onto this forum and sure enough it's a firmware problem.  I'm in the group that doesn't care about standby time but to overcome this problem SENA should be able to do something that doesn't reduce this for those that rely on standby time. 

    0
  • Barry lack
    Barry lack
    My no answer has been rectified,Sena asked me to pack up box and send back to America which I wasnt happy to do ,time ,cost etc.Went back to dealer in Tasmania and they sent of straight away to Australia distributor who tested my main unit on another clamp and it worked .I have version 1.4 FYI on my unit. Today I received the new clamp fitted it up put my main unit on and it works picks up the incoming calls. You do have to shout into it and it is slow to respond but it does work. I found that it is best when the mic is square onto your mouth and foam lightly touching lips .i have a BMW system 6 helmet flip up and feed the mic internally through the cheek pad .
    0
  • Stephan Seitz
    Stephan Seitz

    I recognized the same problem with "Hello Sena" starting with 1.3.

    1.2 and prior were fine.

    Please fix this, Sena, I'm using this feature! :)

    0
  • Stephan Seitz
    Stephan Seitz

    Maybe a config on/off-switch like with the double-tapping? Then the guys that want to drive days and the guys like me would all be happy. :)

    0
  • Blenvid
    Blenvid
    Hilarious Wz4i! Lol

    Interesting Stephan Seitz. I can't comment on the versions as I'd received mine just before the switch to 1.4. Both 1.3 and 1.4 don't work for me.

    Sena had me send my units back. If they're having people send their units back instead of simply and easily downgrading to 1.2, it sounds like it could be a hardware, not firmware, problem. Idk..

    -Brent
    0
  • Keith
    Keith

    As I already have above on this thread, I can testify that the "Hello Sena" command worked no matter how long either of my two original 14XXXXXX 20S units were in stand-by mode running version 1.2. As soon as I went to version 1.3, the "Hello Sena" command on both of my 20S units would stop working after exactly 60 seconds in stand-by mode. I haven't ran version 1.2 on my two replacement 15XXXXXX units as they came loaded with version 1.3. However, I did test the "Hello Sena" command on the replacement units running version 1.3 and again after updating to version 1.4. The "Hello Sena" command doesn't work with either version on either of my 20S units after 60 seconds in stand-by mode. As a side note, the LOUD "Hello" phone answering function did start working with version 1.4 where it didn't with version 1.3.

    Again, from what the Sena engineer told me on 5/7/15 after I pointed it out, they found the problem and are supposed to fix it in the next firmware version (version 1.5, maybe?): Below is a copy of what they told me:

    ++++++++++++++++++++++++++++++++++++++++++++++++++++

    I checked the Voice command issue and found the reason of problem.
    I forwarded this issue to our product management team.
    We will fix it next firmware

    ++++++++++++++++++++++++++++++++++++++++++++++++++++

    My guess is that, given Sena's significant reduction in stated stand-by time (from 10 days down to 2 days), they cut the mic off after 60 seconds to conserve the battery. Otherwise, stand-by time may very well have fallen short of even 2 days as I found out when I tested stand-by battery life with both versions 1.2 and 1.3. I got ~24 hours of stand-by time running version 1.2 (mic always on) and ~34 hours running version 1.3 (mic turning off after 60 seconds) on my original 14XXXXXX units. I'm now getting a little over 50 hours of stand-by time running version 1.4 on my replacement 15XXXXXX units. I believe the longer stand-by time with my replacement units is more due to luck of the draw battery quality than improvements in version 1.4. But, I could be wrong and there may have been other hardware and firmware updates. In any case, this is PURE stand-by time with the units powered up and just sitting on my table. ZERO other use. The current stated stand-by time of 2 days and the concept of an "always on" mic (as it was with version 1.2) being a greater drain on the battery is NOT my guess, however. I was told exactly that on 5/1/15. Below is an exact quote from the Sena engineer:

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    The R&D told me that the standby time of 20S is approximate 2 days now. Also, since the mic is always on they say 48 hours of stand by time.

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

     So, while there may be a hardware problem causing problems with the "Hello Sena" command on *some* units, there definitely is a firmware issue as well.

    Some users will place a higher value on stand-by time and some will value true hands free operation more. In an ideal world, the "Hello Sena" command would always be available (even beyond 60 seconds in stand-by mode) and stand-by time would be the original Sena stated 10 days. But, we apparently don't live in an ideal world. So, it looks like we are facing 2 days of stand-by time with versions 1.3 and 1.4 and hoping that it doesn't decrease even more when they fix the "Hello Sena" command (mic always on) in the future. Stephan's wish for a configuration option to turn the "Hello Sena" feature on or off would be a good compromise to give users the choice of longer stand-by time or true hands free operation. I still wish for both :-)

    0
  • Ken
    Ken

    My experience is that when the iPhone is connected, Hello Sena doesn't work at all.  To confirm this, I went into the iPhone settings and did a "Forget this device".  Instantly, Hello Sena worked.  Then, I re-paired.  Instantly, Hello Sena quit working.  

    Apparently, there was an unannounced change in the firmware that also kills the microphone after 60 seconds; because I get the 60-second time-out on my 20S just as several others reported as well.  30 seconds, no problem.  50 seconds, no problem.  But at 65 seconds, the Sena Lady doesn't respond to "Hello Sena".   

    I've yet to find any mention on the limitations of Hello Sena in the documentation.  

     

    0
  • Blenvid
    Blenvid
    Ken, Keith, you both make some good points here and obviously have had some different input from your Sena support tech on this issue.

    I, however, have been told this may be a hardware issue. As I had to ship both Sena 20S units I purchased across the entire United States to San Jose, CA from Maryland it doesn't make sense they'd have me do this if this is something that could've just been fixed with the next firmware upgrade.

    Perhaps you're having a similar issue caused by a different problem, or perhaps, and I'd hate to think it, my Sena tech support engineer wasn't as aware of this issue as your engineers were and he jumped the gun on having me send it back...

    -Brent
    0

Accedi per aggiungere un commento.