Incorrect Power State Reported for MELCloud Air Conditioner in Automation Scripts

[AutomationCiika]

I'm having trouble retrieving the correct power state of my MELCloud air conditioner when using home automation scripts via Works with Google Home.

- The MELCloud account is linked to Google Home.

- I can control the air conditioner using voice commands and via the Google Home app device controls.

- When I ask the voice assistant for the current power state, it responds with correct power state.

- The Google Home app device also displays the correct power state.

The problem rises with the automation script editor. It always reports the AC as on, even when it's off. The incorrect power state prevents me from using the power status as a condition in my automations.

Has anyone experienced this issue? Any known workarounds? I’d like to use the AC’s power state in my scripts.

[Suc1 · Accepted solution]

Thanks for sharing these details. Based on your description, this seems like a potential issue related to how Google Home Automation Script Editor queries real-time device states from MELCloud.

• This may suggest that:

  • The Automation Script Editor might be using cached or delayed state data.
    
    
  • MELCloud’s state reporting may not fully propagate in real-time to Google Home's scripting engine.
    
    

  You can try:

  1. Adding a small delay before reading the power state in your script (if supported).
     
     
  2. Verify MELCloud's support for real-time state updates via Google Home integration.
     
     
  You can also manage your scripts here:
  https://home.google.com/automations