Automations only start after I open the Home app and go to tab Devices

[jwfukkink]

In the Home app I have configured some automations that switch groups of lights (WiZ) in the living room and kitchen on and off, triggered by a starter (Shelly Motion Sensor (via PlugS) or Aqara FP2).

This has worked correctly for months until last night.
Apparently my Internet-router went berserk but it is working okay again now.

Since then the automations will only trigger after I open the Home app and go to tab Devices. Then they all work correctly.

So far I have tried several things but with no success:
- re-install the Home app
- re-start my mobile phone
- renew the Shelly integration in the Home app

Any suggestions how to fix this?

[Elessar18]

Same issue with an Aqara FP2 sensor. Stopped working suddenly 4 days ago. Tried writing scripts and resetting my phone and google nest mini. No fixes. 

Please let me know if there is a solution.

[Ck89]

Same here. But I notice that the household automation will be triggered with voice commands to turn on the starter

[ajar]

I got the information that shelly devs are in contact with google folks to improve their "works with google" experience (haha).

For me the triggers work, the only thing is that I'm limited to "home.google.com" to setup new automations as the android home-app will not allow to pick shelly devices as triggers. But via that website its works.

So try to delete your automations from home-app and use home.google.com to setup new ones - maybe that will fix the issue for the time beeing.

[oivheg]

I just Updated Aqara FP2 to latest 1.2.4_0002.0066  
and it appears that might have solved the Google home issue. 
as my automations are now triggering again. 

[AndyRoid]

Same here, up to a point. Automations that use zones seem a bit iffy, but automations using the device as trigger seem to be behaving...

[kverul]

are you in the US? I dont seem to have that update for my fp2

[oivheg]

I am in EU . Different server so apparently different update schedule.

M

[kverul]

Im in EU as well, which country? Maybe I can change to your region as well to trigger the update

[oivheg]

I am in Norway . 

[kverul]

strange im in  Sweden and it doesnt work

[PeterHammer]

Here same problem. I have an ewelink light and a tuya switch. I want the switch to control the light via Google Home, but it only works 70% of the time, the other 30% I have to open the app in my phone, I just doing that makes the automation work. As if it was executed from the phone and not the servers, and the app was sleeping. Wierd. Google Home is such a let down.

[patrikwa]

Here I am in september 2024 and finding out this exact problem, it still isn't resolved. Did anyone actually find a workaround, I cannot have automations work only when I manually update Google Home since that kinda makes tho whole system pointless.

What to do here? I have devices that ONLY works with Google Home so even if I have a Homey Pro, I cannot automate it unless Google Home starts working... 

[ajar]

Have you already tried to setup new automations via home.google.com ?

[patrikwa]

I tried creating the automations from home.google.com but when I click the "+"-sign I only see the script editor (not the usual "if -> then" triggering boxes , I might try it out but I wasn't super interested in learning the syntax for a new programming language for something I might end up never using (I want to focus on getting all automations running from Homey Pro and just use any other app when absolutely necessary). 
With that said, if that is indeed the fix to the problem (is it confirmed that these work differently?) I will have to start using the script editor for sure. 

[jwfukkink]

I decided not to wait any longer and went for another solution: IFTTT. The WiZ-integration for IFTTT works fine, but the Aqara-integration needed some attention and months after I reported it still wasn't fixed.

The problem with IFTTT (and similar solutions) is that the Internet dependency makes the light-switching a bit slow-ish (which you experience every time you walk into a room). In the end I decided to go one step further: Home Assistant.

With HA local is key: no Internet-connection needed at all which makes the switching really fast! If you don't like to configure your own device (e.g. RasPi) you can buy their HA Green plug-and-play device.

What I find amazing with HA is it's community-based and a large number of users have already created integrations for virtually any brand and platform of devices. And bug fixing is not dependant on the priorites of one company (like with Google Home and IFTTT).

[patrikwa]

Yeah, I considered HA when I started this whole process, but I landed in Homey Pro since I really don't want to be coding and debugging a lot since I work as a developer/programmer/coder and already spend my entire work days coding and debugging, also getting my girlfriend involved/interested in HA would probably be an even greater obstacle, Homey Pro flows is MUCH easier and intuitive.
My understanding atleast was that Homey Pro was a lot more "plug and play" but so far I have been doing a lot of debugging and by the looks of it, I have to also start scripting stuff, sigh. If google home just worked none of this would have been an issue. Everything else that I can automate directly through Homey Pro works great, its just this 1 device that i'm having a real hard time with since it is only controllable by Google Home (which obviously doesn't wanna play nice)

[patrikwa]

Ok, so I made an attempt of doing it through the script editor, but I got stuck on a line where a "device" is supposed to be called together with the okGoogle command, not sure what to do here...Anyone?

The problem is that I want to simulate telling google assistant to "Close door" through my phone, but the script editor wants me to tell it what device to run google assistant on, I have no such device (other than my phone), how can I just run the command? I tried using the "device.command.OpenClose" action but it is not allowed on door type devices... which in itself is super weird since i'm allowed to do so by telling the assistant to do it 🙄

# Full description:
# Coop door is added to Google Home (with name 'door'), but cannot be opened/closed by Google Home through device commands (due to security reasons according to google), it can however be opened/closed by simply saying "close door" to the google assistant.
# Coop door cannot be added to Homey Pro so instead I've added a virtual device (type kettle) with an on/off state inside Homey Pro, this device can be seen by Google Home.
# The idea is that when I toggle the virtual device off in Homey Pro, Google Home should see that and then issue the command "Close door" to actually close the coop door. (And vice versa)
metadata:
  name: Close coop door
  description: When Homey Pro virtual device is toggled OFF, send "Close door" through the Google Assistant to actually close the door
automations:
  #When the Homey Pro virtual device is toggled off
  - starters:
      - type: device.state.OnOff
        device: Hönshusdörren (virtual) - Hönshus
        state: on
        is: false
    #Send "Close door" voice command to close the actual door
    actions:
      - type: assistant.command.OkGoogle
        devices: [Device] # Can this be nullptr? I have no device that acts as a speaker, I just want to simulate someone telling the Google Assistant to "Close door"
        okGoogle: Close door

[Fkw31er]

Same Issue here. I am using a Philips hue door sensor to open or close the blinds. It's programmed in the Google home script. Unfortunately it suddenly stopped working and only works when I open the Google home app or ask Google Nest if the door is open or closed. Anyone else who has the problem that the Google automations can't be triggered by a Philips Hue devices anymore?

[dles]

Any update on this? Having the same issue with a routine not starting until I open the Google Home app (I have a rule set that once the indoor temperature drops below a certain temp, to change the set temp on my AC unit).

[patrikwa]

I think this is just by design from google, I gave up on using Google Home to try and automate anything and just bought a Homey Pro instead, it was expensive but allowed me to actually start automating things based on triggers and other devices states etc. 
I don't think Google Home aims to be a smart home controller but rather an easy way of turning on a couple of light bulbs with voice command or simple stuff like that. 

The issues I had with controlling some Google Home compatible devices got solved by writing scripts using the manufacturers own API, not really a standard user approach but luckily for me I am a c++ developer and didn't have a super hard time learning what I needed in the end. 

[Knordor]

Hi,

this issue appeard yesterday in my routines. Is there still no solution to this topic?