demolud2
(Maciek)
September 29, 2022, 6:42pm
1
Hi,
trying to trigger automation only when driving my car. I have a trigger when entering a zone.
I am checking if my mobile is connected with car via bluetooth:
condition: state
entity_id: sensor.mi_6x_polaczenie_bluetooth
attribute: connected_paired_devices
state: "74:D7:CA:AD:30:4C (Toyota Touch)"
Unfortunately when I check condition in GUI via test button, I always get Condition did not pass.
I was checking state of the attribute in Developpers tools with
{{ state_attr('sensor.mi_6x_polaczenie_bluetooth','connected_paired_devices') }}
and got above attribute as result.
What am I doing wrong with my automation?
Regards,
Maciek
krskrab
September 29, 2022, 7:32pm
2
Developpers tools
{{ '74:D7:CA:AD:30:4C (Toyota Touch))' in state_attr('sensor.mi_6x_polaczenie_bluetooth', 'connected_paired_devices') }}
demolud2
(Maciek)
September 29, 2022, 7:55pm
3
Perhaps I was not clear enough.
On DevTools all works fine. It is just automation I have problem with.
demolud2
(Maciek)
September 29, 2022, 8:17pm
5
Thanks. Tried value_template before, but it did not work, not work, not sure if it matters that attribute value is more than just MAC?
khvej8
(Khvej8)
September 29, 2022, 8:48pm
6
I think the automation should look something like this, of course with your own trigger and action.
The condition should be like this, to my best knowledge
description: "test automation"
mode: single
trigger:
- platform: state
entity_id:
- input_boolean.aa_test_boolean
condition:
- condition: template
value_template: >-
{{ '74:D7:CA:AD:30:4C (Toyota Touch))' in
state_attr('sensor.mi_6x_polaczenie_bluetooth',
'connected_paired_devices') }}
action:
- device_id: b81f18d9f8a302b925c324f95ce05f45
domain: button
entity_id: button.530e_flash_lights
type: press
123
(Taras)
September 29, 2022, 9:01pm
7
The Test button has a known bug that causes it to fail when testing Template Conditions. Until it’s fixed, I suggest you don’t rely on it to test your Template Conditions.
FWIW, there was a PR recently submitted to fix it but, due to some issues, it hasn’t been accepted yet.
home-assistant:dev
← d-walsh:template_improvements
opened 10:11PM - 11 Sep 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [x] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes [#12282](https://github.com/home-assistant/frontend/issues/12282)
- This PR is related to issue: [#12282](https://github.com/home-assistant/frontend/issues/12282)
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [x] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
krskrab
September 29, 2022, 9:30pm
8
- platform: template
sensors:
in_my_car:
friendly_name: "Connection to the car "
value_template: >
{% if "50:4F:B5:07:9C:CA (MB-7079CDA)" in state_attr('sensor.sm_g975f_bluetooth_connection', 'connected_paired_devices') -%}
on
{% else -%}
off
{% endif -%}
Automations
platform: state
entity_id:
- sensor.in_my_car
to: "on"
...
demolud2
(Maciek)
September 30, 2022, 8:39pm
9
Thanks, I didn’t know IT.
123
(Taras)
September 30, 2022, 8:44pm
11
For the record, you didn’t need to create a Template Sensor to solve the problem you originally reported.
krskrab
September 30, 2022, 9:49pm
12
automation
description: "test automation"
mode: single
trigger:
- platform: numeric_state
entity_id: sensor.sm_g975f_bluetooth_connection
value_template: >
{% if "74:D7:CA:AD:30:4C (Toyota Touch))" in
state_attr(sensor.mi_6x_polaczenie_bluetooth',
'connected_paired_devices') -%}
3
{% else -%}
1
{% endif -%}
above: 1
condition: []
action:
- device_id: b81f18d9f8a302b925c324f95ce05f45
domain: button
entity_id: button.530e_flash_lights
type: press
123
(Taras)
September 30, 2022, 10:14pm
13
That’s a curious application of a Numeric State Trigger. It’s simpler to use a Template Trigger.
alias: example
trigger:
- platform: template
value_template: >
{{ "74:D7:CA:AD:30:4C (Toyota Touch))" in state_attr(sensor.mi_6x_polaczenie_bluetooth', 'connected_paired_devices') }}
condition: []
action:
... actions go here ...
1 Like