Cielo control unreliable within automation

[andypnz]

@bodyscape I have been using your custom integration for a while now - it is truly great!

One issue I wonder if you can help with? I have noticed when I include Cielo commands in automations they often do not work. Using the Cielo controls in a dashboard always works. Using Cielo commands in a script works if the script is run from the dashboard, but often they don’t work if the script is called from within an automation. The automations clearly run (lights on, etc) but the Cielo calls don't make any changes on the Cielo device.

Any thoughts / trouble shooting?

[bodyscape]

The cielo command execute the same code of the ui button

[andypnz]

I would expect the same… however I get 100% reliability sending commands within the HA UI, but maybe 50% reliability when a command is within an automation. I will try changing my automations (perhaps to only issue one heat pump command per automation) to see if that makes any difference….

[jduff001]

maybe this will help. I notice about a two second delay for the cloud to respond. So try sending just one command and then a wait delay... then the next command

[bodyscape]

That's a good idea, put a little delay between the call. Fast back to back call can cause problems, i'll check on it.

[andypnz]

Recently UI commands also stopped working for a few days - started working again after yesterdays update to 1.7.6 (coincidence?).

Here is an example of an automation that does not turn down the heat pump. I do receive the notification to my phone - so overall, it is 'working', just not the Cielo Home part.... No errors on Trace.

Here I am calling a script to set the temp. The script works fine from the UI, but not within the automation. Does not work calling the temp change directly either (I was testing using the script in case it worked).

`alias: "Heatpump: Left turned up at 2300hrs!"
description: ""
trigger:

• platform: time
  at: "23:00:00"
  condition:
• condition: and
  conditions:
  • condition: state
    entity_id: switch.heat_pump_power
    state: "on"
  • type: is_temperature
    condition: device
    device_id: b4049f004387b4ef17e5bdxxxxxxxxxx
    entity_id: 64fafd3df23808984530bcxxxxxxxxxxx
    domain: sensor
    above: 16
    action:
• service: climate.set_hvac_mode
  target:
  device_id:
  - b4049f004387b4ef17exxxxxxxxxx
  data:
  hvac_mode: heat
  enabled: false
• delay:
  hours: 0
  minutes: 0
  seconds: 10
  milliseconds: 0
  enabled: false
• service: number.set_value
  data:
  value: "16"
  target:
  device_id: b4049f004387b4ef17xxxxxxxxxxxx
  enabled: false
• service: script.set_heat_pump_to_heat_16_degrees
  metadata: {}
  data: {}
• service: notify.mobile_app_arp_iphone
  data:
  message: Heat pump was left turned up! Heat pump now set to 16
  title: Heat Pump
  mode: single
  `

`alias: Set heat Pump to Heat, 16 Degrees
sequence:

• service: climate.turn_on
  metadata: {}
  data: {}
  target:
  device_id: b4049f004387b4ef17xxxxxxxxxxx
• delay:
  hours: 0
  minutes: 0
  seconds: 10
  milliseconds: 0
• service: climate.set_hvac_mode
  metadata: {}
  data:
  hvac_mode: heat
  target:
  device_id: b4049f004387b4ef17xxxxxxxxxxxxx
  enabled: true
• delay:
  hours: 0
  minutes: 0
  seconds: 10
  milliseconds: 0
• service: number.set_value
  target:
  entity_id: number.heat_pump_target_temperature
  data:
  value: "16"
  mode: single
  icon: mdi:heat-wave
  `

[bodyscape]

@andypnz do you still have problems?

[andypnz]

@bodyscape Yes, issue persists…
Within the automation I have a delay, then command
Then actually repeat the sequence - doing this, it works 95% of the time
Other bits of the automation work - it seems to only be the Cielo part that sometimes does not… no error, etc….

[bodyscape]

@andypnz honestly i have no idea what's going on your side... everything work 100% of the time... try version 1.7.7 maybe....

[MikeDembek]

I've experienced something very similar and I suspect it's related to some sort of server-side load or rate-limiting condition.

I'd see this frequently over the summer with an automation I had running at 7:00am - it'd appear to run successfully in HA but silently fail at least a couple of times a week. Other automations triggering on non-time-based circumstances didn't seem to have this issue, or at least not as much (ie. a temperature threshold-based trigger).

That's anecdotal, but if your automations are configured to fire at round numbers (ie. 7:00), consider offsetting them a little bit - if that substantially improves the behavior it might help us identify a condition with Cielo server load that causes issues during intervals of high usage.

[andypnz]

Interesting thought… and the automation is at ‘round hour’ times… it is summer here, so the heat pump is off… but will keep this in mind as winter approaches!