Help me love HA - first (failing) automation, Daikin AC with BRP069B45

fakemoth · July 4, 2021, 7:29pm

I read those, the AC unit is fine, and manually everything works. Even as an automation, it changes hvac states, it shuts down, tried all kind of stuff; except for starting up < doesn’t work. Can’t figure out what to invoke as a trigger, tried everything obvious.

123 · July 4, 2021, 7:33pm

I listed behavior that serves as a disincentive for me (and possibly others) to rush to your assistance.

I purposely omitted one and that’s where the user characterizes any disagreement with their stated opinions as “bashing”. So, your post has that one as well.

It’s the first day at your new job and the way you ask for help is to first perform “a small rant”. When informed that’s not the way to solicit help, you inform them not to “bash” you. Can you see how that wouldn’t be starting out on the right foot?

Based on a quick forum search of “BRP069B45”, the results indicate it’s supported by a custom component. Is that what you tried to use?

AllHailJ · July 4, 2021, 7:49pm

Here is how I would use the UI to set the automation. I don’t know how you named your entities.

My logic

Trigger: If my main floor sensor > 72 degrees
Action: Turn of the FR fireplace

obviously this is a fabricated automation.

Here is a screenshot of the automation.

Tinkerer · July 4, 2021, 8:01pm

Sadly, it’s really hard to help you. It’s not at all apparent what:

except for starting up < doesn’t work
means

Is the automation not running? Is the AC not running from the automation? Is the whale falling faster than the petunias?

To test an automation there’s three stages you can follow. Testing the action, the condition and action, and the whole automation:

Use Developer tools ()-> States to find the automation, click and then push Execute. If this fails your problem is in the action: section, and details should be found in your log file

Use Developer tools → Services and call automation.trigger on the automation with skip_condition: false . If the first passes but this fails then the problem is in your condition: block

Use Developer tools → States to find the trigger entity, click the name, then change the state (at the top) to something that’ll trigger the automation before pushing Set State. If this fails then the problem is with your trigger: section, or the automation is turned off (you can check that in Developer tools → States ).

You can also see this section in the docs and with HA 2021.4 onwards debug automations.

nickrout · July 5, 2021, 12:28am

You need to figure out “when do I want to turn the AC on?” - that is your trigger, and possibly your condition.

When the room is over 24 degrees.
When the room is over 24 degrees and it is daytime
When the room is over 25 degrees and someone is home
At 7:00 am during summer

We can’t guess what you are trying to automate, do tell us

tom_l · July 5, 2021, 1:11am

This model is not supported. See:

There is a solution in that topic. Install the older wifi controller which does still work:

So if you can currently control your AC from a thermostat card in Lovelace do not connect to the AC with the Daikin app and update its firmware or it may stop responding to home assistant.

fakemoth · July 5, 2021, 6:07am

Tried something like that, this is what seemed like a good option to me:

And I do have a card and its controls, in the dashboard are working fine, there are also sensors for the simplest automation ever
Also tried with different sensors in the trigger, tried with different actions (changing presets, hvac modes)
This is the code generated:

- id: '1625416471401'
  alias: Daikin_AC
  description: AC_Control_Daikin
  trigger:
  - type: temperature
    platform: device
    device_id: f9c4939f55a2c3b29341721af46814f8
    entity_id: sensor.daikinap84451_inside_temperature
    domain: sensor
    above: 20
  condition: []
  action:
  - service: climate.turn_on
    target:
      device_id: f9c4939f55a2c3b29341721af46814f8
  mode: single

fakemoth · July 5, 2021, 6:11am

Took a look at the post but I have the BRP069B45 controller, which seemed compatible, that is why I wrote, perhaps interpreted, that I didn’t buy something “better”. Was not blaming… anything really, was my decision, and that’s it.

Also it is weird in the way that I can control the AC from my dashboard, so HA talks fine and “everything” seems detected

Even more weird is that, if for example I set an automation to change modes, stop the ac, or other settings - it works. Except fort starting up, as I mentioned.

As you can see, the automation should be triggered at 20, but the card is greyed out (it changes blueish when it does), and the AC not starting.

Now, if I “RUN ACTIONS” in the automations page, the darn thing starts up just fine, so it is also able to start up. That’s why I am trying to set aside any diagnosis on my side, let the doctors draw their own conclusions Thought to start fresh, didn’t expect that many reactions, man this community is active.

Tinkerer · July 5, 2021, 6:29am

So, you say the automation doesn’t work, but when you run the actions it then it does. That points strongly to a problem with the trigger.

You’re using a numeric state trigger (in a different form), so the temperature has to start at 20 or below, and then rise to above 20 for the automation to run. That has to happen after the automation is loaded (so, when you edit any automation, restart HA, etc).

tom_l · July 5, 2021, 6:30am

Excellent! Don’t update the firmware in the wifi controller. In other words don’t ever connect to it with the official app as I think it happens automatically.

fakemoth · July 5, 2021, 6:33am

To finish my previous posts, sorry for the many screenshots, seemed easier to show the problem, here is the result when running the automation

In the logs I only have the occasional
2021-07-05 09:22:38 WARNING (MainThread) [homeassistant.components.daikin] Connection failed for 10.0.3.151 but the router just shows that all connections are getting through… and controlling the start up works. By hand in dashboard and/or via running manually the automation

fakemoth · July 5, 2021, 6:34am

Oh but I did update, and nothing happened, was the first major thing I tried after a day or two lol

The result is the same.

I will ask here the most stupid thing ever maybe, but just to rule it out: the automations are supposed to run by themselves, right, don’t have to configure some cron job or extra stuff ie when the trigger/conditions are met ? Might be some stupid operating mistake on my part, just thinking, but the docs seem to agree that it is not the case.

fakemoth · July 5, 2021, 6:47am

I always restart at least the automation, if not HA.

I also think it is the trigger but I am refraining myself, as I clearly don’t know exactly what it could be the issue.

tom_l · July 5, 2021, 6:52am

No need for anything other than reloading automations after you have written it.

Tinkerer has told you why it is not triggering:

If your temperature is already above 20 it won’t trigger.

fakemoth · July 5, 2021, 7:00am

I also did try that and everything in between ie set a higher temperature, wait to climb to that - yesterday it was set at 25, when the room was at 24; 26/25, 27/26 - I really tried to figure this.

So now I set this test automation at above 25, when in room there are 24. Will wait to crawl, and report back.

I did reload the automation, and also restarted HA.

Later edit: to 24 now as the temperature dropped

tom_l · July 5, 2021, 7:06am

You could try this trigger instead:

  trigger:
  - platform: numeric_state
    entity_id: climate.daikinap84451
    attribute: inside_temperature
    above: 20

Go to Developer Tools States and make sure the entity id and attribute are correct.

fakemoth · July 5, 2021, 9:24am

So I think we can conclude my experiment, the temp in the room is reported as 25 and stood an hour or so at 24. Automation was set at 24, when the temperature of the room was 23 Celsius. Didn’t touch anything in this period, log is empty.

It is not working as intended. A thought: maybe the “DaikinAP84451 Inside Temperature” sensor is not what I think it is, which is the room temperature (though it seems to behave accordingly), or at least somehow it can’t be used that way?

Edit: I also have a “DaikinAP84451” as you can see from the pic - will try that!

Tinkerer · July 5, 2021, 9:25am

You have an automation in automations.yaml. If you share the YAML I’m sure we can help further.

fakemoth · July 5, 2021, 9:27am

It was posted above. Have to go, in the meantime will chill the hell out of the room, for further experiments. Tks!

fakemoth · July 5, 2021, 7:22pm

Well good news, it works it just started this evening, and I kept thinking what I did different, as the trigger is pretty much the same. Thing is - this time I didnt’ touch anything in the interface or the remote; I remember after setting the automation I always somehow messed with temps in the dashboard, forcing the temperature to drop or increase, just to test. So the “tests” somehow screwed… the scope of tests.

Is this a thing? And I figured that it works somehow different than I would imagine, as it doesn’t check constantly? I mean if the temperature is at 24 in the room and the trigger at 24 - how is that working and why sometimes it’s not working when I set the trigger 1 celsius higher/lower?

Thank you all for the help and the patience!

Here is the end result now (what exactly is that “max: 3” doing there at the bottom?):

- id: '1625416471401'
  alias: Daikin_AC_Attic_Start
  description: Daikin_AC_Camera_Attic_Start
  trigger:
  - type: temperature
    platform: device
    device_id: f9c4939f55a2c3b29341721af46814f8
    entity_id: sensor.daikin_ftxp25m_inside_temperature
    domain: sensor
    above: 24
    for:
      hours: 0
      minutes: 0
      seconds: 0
      milliseconds: 0
  - type: temperature
    platform: device
    device_id: f9c4939f55a2c3b29341721af46814f8
    entity_id: sensor.daikin_ftxp25m_inside_temperature
    domain: sensor
    below: 17
  condition: []
  action:
  - choose:
    - conditions:
      - type: is_temperature
        condition: device
        device_id: f9c4939f55a2c3b29341721af46814f8
        entity_id: sensor.daikin_ftxp25m_inside_temperature
        domain: sensor
        above: 24
      sequence:
      - service: climate.turn_on
        target:
          device_id: f9c4939f55a2c3b29341721af46814f8
      - device_id: f9c4939f55a2c3b29341721af46814f8
        domain: climate
        entity_id: climate.daikin_ftxp25m
        type: set_hvac_mode
        hvac_mode: cool
    - conditions:
      - type: is_temperature
        condition: device
        device_id: f9c4939f55a2c3b29341721af46814f8
        entity_id: sensor.daikin_ftxp25m_inside_temperature
        domain: sensor
        below: 17
      sequence:
      - service: climate.turn_on
        target:
          device_id: f9c4939f55a2c3b29341721af46814f8
      - device_id: f9c4939f55a2c3b29341721af46814f8
        domain: climate
        entity_id: climate.daikin_ftxp25m
        type: set_hvac_mode
        hvac_mode: heat
    default: []
  mode: single
  max: 3
- id: '1625485504167'
  alias: Daikin_AC_Attic_Stop
  description: Daikin_AC_Camera_Attic_Stop
  trigger:
  - type: temperature
    platform: device
    device_id: f9c4939f55a2c3b29341721af46814f8
    entity_id: sensor.daikin_ftxp25m_inside_temperature
    domain: sensor
    for:
      hours: 0
      minutes: 30
      seconds: 0
      milliseconds: 0
    below: 23
  - type: temperature
    platform: device
    device_id: f9c4939f55a2c3b29341721af46814f8
    entity_id: sensor.daikin_ftxp25m_inside_temperature
    domain: sensor
    above: 19
    for:
      hours: 0
      minutes: 30
      seconds: 0
      milliseconds: 0
  condition: []
  action:
  - service: climate.turn_on
    target:
      device_id: f9c4939f55a2c3b29341721af46814f8
  mode: single
  max: 3