Cannot switch to ARM HOME under Google Home automation

[alex_loo]

I have successfully linked my ARLO setup to google home.   The only things is that from Google Home automation, I can only select to "arm" (which is ARM AWAY) and "unarm" (which is STANDBY).  There is NO option for automation to switch to ARM HOME, which is apparently a big issue.

Setup:

• 3x ultra 2 cameras
• 1x SmartHUB VBM5000
• NO subscription

Further background in this discussion.

@ShayneS could you advise?  Thanks.

Regards,

Alex

ps: the same issue happens for IFTTT integration too.

[Jeff__h]

Unfortunately this new Arlo app was not ready for prime time.  I have encountered many limitations and bugs.  For a security product that people have relied on for years, Arlo has crippled the community.  I’ve even experienced many detection errors with random cameras.  This and many other bugs have exposed unnecessary risks to the reliability of the security system.  Always having to change mode actions for various situations is ludicrous and the limits on number of modes completely defeats the reason for the app.  The automations segment is a complete joke and totally unusable.

I’m trying to be patient with hopes Arlo will fix their design issues and many bugs.  I just can’t place my trust in Arlo if things don’t change.  Security system must be solid and open for users to control their own environment.  What we have today is a poorly designed app that wasn’t totally tested and forcing the community to switch was a fatal mistake!  We should of been able to run the app as a separate beta app till it was market tested and ready for prime time.

I will wait another 3 months for resolution and if nothing changes, I will scrap Arlo and invest into another product.  My security system must be reliable and flexible.period!

[alex_loo]

---

@Jeff__h wrote:

I’ve even experienced many detection errors with random cameras.

---

So far I haven't seen detection errors, with my 3x ultra 2 cameras.  There are occasional "false alarms" on sound detection, but given it's aeroplane flying by and I don't have any AI, I am not complaining about it.

What are your cases?

Always having to change mode actions for various situations is ludicrous and the limits on number of modes completely defeats the reason for the app.

---

Above is well spot-on!  Can't agree more.  Just 3 modes is simply not enough.  I need at least 4!

• Some user at home daytime and nobody is walking around the property: turn on ALL/some cameras (Mode 1 "arm home")
• Some user at home daytime and is walking around the property: turn off all cameras (Mode 2 "standby")
• Some user at home nighttime: always turn on ALL cameras at 1130pm (automation to switch to Mode 3 "night")
• All users away: always turn on ALL cameras FOREVER, until any user returning (this Mode 4 "arm away" is different from mode "night" above, since "arm away" will not switch back to daytime modes)

---

@@Jeff__ wrote:

The automations segment is a complete joke and totally unusable.

agree above, again.  Automation only gets triggered by time or geofencing (which then has been failing).  Even worse, I can't leverage other triggers via google home or ITFFF, since "arm home" is simply not there for 3rd party automation.  Simply useless.

---

@Jeff__h wrote:

I will wait another 3 months for resolution and if nothing changes, I will scrap Arlo and invest into another product.  My security system must be reliable and flexible.period!

---

I am afraid there won't be resolution in just 3 months.  I have been "new" to ARLO for more than 6 months now.  Confused, surprise, outraged, feeling hopeless and now --- trying my best just to "survive".

And don't forget it's Christmas soon.  They won't bother fixing big issues.  sigh.

Alex

ps: I started with new app and am ok with the "new" design around modes.  They just have to be working, and providing more modes.

[ShayneS]

@alex_loo 

Thank you for the info, as mentioned in the other thread, I will keep you posted with updates from the team. 

[alex_loo]

---

@alex_loo wrote:

I have successfully linked my ARLO setup to google home.   The only things is that from Google Home automation, I can only select to "arm" (which is ARM AWAY) and "unarm" (which is STANDBY).  There is NO option for automation to switch to ARM HOME, which is apparently a big issue.

---

Interestingly, I am revisiting this on Google home automation, and notice although there is still incorrectly just 2 modes to choose (should be 3), the 2 are "arm home mode" and "arm away mode".  ie "arm standby" is now missing.

VS

for IFTTT, I can only "ARM" (ARM AWAY) or "DISARM" (STANDBY)

So yes @ShayneS please continue looking into this for us.

Alex

[alex_loo]

---

@alex_loo wrote:

---

@alex_loo wrote:

I have successfully linked my ARLO setup to google home.   The only things is that from Google Home automation, I can only select to "arm" (which is ARM AWAY) and "unarm" (which is STANDBY).  There is NO option for automation to switch to ARM HOME, which is apparently a big issue.

---

Interestingly, I am revisiting this on Google home automation, and notice although there is still incorrectly just 2 modes to choose (should be 3), the 2 are "arm home mode" and "arm away mode".  ie "arm standby" is now missing.

VS

for IFTTT, I can only "ARM" (ARM AWAY) or "DISARM" (STANDBY)

So yes @ShayneS please continue looking into this for us.

So to summarise:

• "ARM HOME" is missing from IFTTT
• "STANDBY" is missing from google automation

Hope this clarifies my question.

Alex

[StephenB]

---

@alex_loo wrote:

---

@alex_loo wrote:

---

@alex_loo wrote:

I have successfully linked my ARLO setup to google home.   The only things is that from Google Home automation, I can only select to "arm" (which is ARM AWAY) and "unarm" (which is STANDBY).  There is NO option for automation to switch to ARM HOME, which is apparently a big issue.

---

Interestingly, I am revisiting this on Google home automation, and notice although there is still incorrectly just 2 modes to choose (should be 3), the 2 are "arm home mode" and "arm away mode".  ie "arm standby" is now missing.

VS

for IFTTT, I can only "ARM" (ARM AWAY) or "DISARM" (STANDBY)

So yes @ShayneS please continue looking into this for us.

So to summarise:

• "ARM HOME" is missing from IFTTT
• "STANDBY" is missing from google automation

Hope this clarifies my question.

Alex

---

Actually the posts in your quote say that "Arm Home" is missing from both.

The underlying issue is that both integrations were designed for the "Library" interface, and have not yet been updated for "Feed".

[alex_loo]

---

@StephenB wrote:

Actually the posts in your quote say that "Arm Home" is missing from both.

---

yes, that's why I clarified this by correcting my question.

---

@StephenB wrote:

The underlying issue is that both integrations were designed for the "Library" interface, and have not yet been updated for "Feed".

---

So does "library" has 3 modes too?  (including ARM HOME)

Alex

[StephenB]

---

@alex_loo wrote:
So does "library" has 3 modes too?  (including ARM HOME)

It has only two modes built on - Armed and Disarmed.  You can add more custom modes, which is a feature that unfortunately was taken out with "Feed" and "Dashboard".  I suspect Arlo is working on adding them back, though I guess it is possible they will go with a different approach.

[alex_loo]

---

@StephenB wrote:

---

@alex_loo wrote:

---

@alex_loo wrote:

---

@alex_loo wrote:

I have successfully linked my ARLO setup to google home.   The only things is that from Google Home automation, I can only select to "arm" (which is ARM AWAY) and "unarm" (which is STANDBY).  There is NO option for automation to switch to ARM HOME, which is apparently a big issue.

---

Interestingly, I am revisiting this on Google home automation, and notice although there is still incorrectly just 2 modes to choose (should be 3), the 2 are "arm home mode" and "arm away mode".  ie "arm standby" is now missing.

VS

for IFTTT, I can only "ARM" (ARM AWAY) or "DISARM" (STANDBY)

So yes @ShayneS please continue looking into this for us.

So to summarise:

• "ARM HOME" is missing from IFTTT
• "STANDBY" is missing from google automation

Hope this clarifies my question.

Alex

---

Actually the posts in your quote say that "Arm Home" is missing from both.

The underlying issue is that both integrations were designed for the "Library" interface, and have not yet been updated for "Feed".

---

Agree IFTTT integration was designed for the "library" interface, since with former you can only ARM or DISARM.

As for Google Automation integration, I am not sure it was designed for the "library" interface, since there is NOT the option for DISARM/STANDBY, but one for "ARM HOME" instead.

Anyway these integrations are not consistent, in terms of offering and capabilities.

Alex

[HalinaK]

Users of the Google Home App who have linked their Arlo account can use voice commands to control the security system’s mode. Specifically, they can:

1. Set the system to "armHome" mode by saying, "Hey Google, set my <security system name> to Arm Home mode.”
2. Set the system to "armAway" mode by saying, "Hey Google, set my <security system name> to Arm Away mode.”
3. Set the system to "standby" mode by saying, "Hey Google, disarm my <security system name>."

Please note that Arlo is not responsible for automations that may trigger these modes.

If you encounter issues with the device's inability to disarm (set it to "standby" mode) through automation, please report it here: Google Issue Tracker.

Someone has already reported this issue, and the Google team is currently working on it.

https://issuetracker.google.com/issues/360520328

[alex_loo]

---

@HalinaK wrote:

Users of the Google Home App who have linked their Arlo account can use voice commands to control the security system’s mode. Specifically, they can:

1. Set the system to "armHome" mode by saying, "Hey Google, set my <security system name> to Arm Home mode.”
2. Set the system to "armAway" mode by saying, "Hey Google, set my <security system name> to Arm Away mode.”
3. Set the system to "standby" mode by saying, "Hey Google, disarm my <security system name>."

Please note that Arlo is not responsible for automations that may trigger these modes.

If you encounter issues with the device's inability to disarm (set it to "standby" mode) through automation, please report it here: Google Issue Tracker.

Someone has already reported this issue, and the Google team is currently working on it.

https://issuetracker.google.com/issues/360520328

---

thanks for the info, @HalinaK .

From above update from google (automation) team, they have decided NOT to support the DISARM state.  Not super happy with this, but I respect their decision, and appreciate the transparency with the communication (a good example for ARLO support).

Afterall, I understand that automation on security system is best taken up by the security system itself (ie the ARLO app, not 3rd party like google automation).

Alex

[alex_loo]

---

@alex_loo wrote:

---

From above update from google (automation) team, they have decided NOT to support the DISARM state. 

---

side info: I notice that IFTTT has NOT made such decision.  I can still do automation to DISARM my ARLO, using that.

Alex

[HalinaK]

However, there is a workaround to disarm the Arlo device using automation 🙂

When selecting a way to set an action, choose the "Try adding your own" tab instead of "Adjust Phone Devices." Then, enter the desired command, such as "Disarm my <device name>." This worked for me.

[alex_loo]

---

@HalinaK wrote:

However, there is a workaround to disarm the Arlo device using automation 🙂

When selecting a way to set an action, choose the "Try adding your own" tab instead of "Adjust Phone Devices." Then, enter the desired command, such as "Disarm my <device name>." This worked for me.

---

"This action requires a PIN, but it hasn't been set up in your device's app"

I was trying to disarm my SmartHub VMB5000.

Did you encounter this?  What's your configuration?

Alex

[HalinaK]

---

@alex_loo wrote:

---

@HalinaK wrote:

However, there is a workaround to disarm the Arlo device using automation 🙂

When selecting a way to set an action, choose the "Try adding your own" tab instead of "Adjust Phone Devices." Then, enter the desired command, such as "Disarm my <device name>." This worked for me.

---

"This action requires a PIN, but it hasn't been set up in your device's app"

I was trying to disarm my SmartHub VMB5000.

Did you encounter this?  What's your configuration?

Alex

---

On the Arlo website or in the Arlo app, go to the "Settings" tab and click on the "Assistant PIN" button.
Next, enter 4 digits twice.
Use these digits when Google Assistant asks you to enter your PIN.
This is required to disable arm mode securely.

[alex_loo]

---

@HalinaK wrote:

---

@alex_loo wrote:

---

Did you encounter this?  What's your configuration?

Alex

---

On the Arlo website or in the Arlo app, go to the "Settings" tab and click on the "Assistant PIN" button.
Next, enter 4 digits twice.
Use these digits when Google Assistant asks you to enter your PIN.
This is required to disable arm mode securely.

---

Yes, I know and am not asking about this.  I am "complaining" this instead.  While I am expecting some peace of mind from automations, why should I now yell to Google home automation?  Even worse, IT IS MY PIN I am yelling out! What if I am trying to do this in the public?😨

Alex

[HalinaK]

---

---

Yes, I know and am not asking about this.  I am "complaining" this instead.  While I am expecting some peace of mind from automations, why should I now yell to Google home automation?  Even worse, IT IS MY PIN I am yelling out! What if I am trying to do this in the public?😨

Alex

---

I think it’s challenging to find a compromise here. On one hand, it’s really inconvenient in your case, but on the other hand, not having a PIN code makes the whole system insecure. Perhaps in the Arlo app, a button could be added next to the PIN code where the user has the option to opt out of using a PIN code and confirm this choice directly within the Arlo app.

[alex_loo]

---

@HalinaK wrote:

---

---

I think it’s challenging to find a compromise here. On one hand, it’s really inconvenient in your case, but on the other hand, not having a PIN code makes the whole system insecure. Perhaps in the Arlo app, a button could be added next to the PIN code where the user has the option to opt out of using a PIN code and confirm this choice directly within the Arlo app.

---

personally I don't see a need to compromise.  If there is concern regarding security, the whole idea of voice control is not secure in the first hand.  If we trust there is certain level of security with (google) automation, then so long as my ARLO account is linked (via authentication) to my automation, I'd just trust the security level there, and enjoy my convenience.

Haven't said that, I do agree with you that the opt-out feature a good way to compromise (at least between us 😉)

Alex