-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two B+'s, automation assigned to B+ nr. 1 is also triggered by B+ nr. 2 #37
Comments
Can you check for me what MQTT topics are on the Button 6 inside the web interface of both Button+ devices? It should look something like this: The idea was to use the unique Button+ device in all MQTT topics and in the entity names of HASS so that this shouldn't happen. Could you also check the debug log when the button is pressed? It should look something like this in the log if you press buttons:
|
Could this be the problem? |
Describe the bug
I added first B+ with ID 45_a450 to HA.
Then added second B+ with ID 45_a5d0.
I created an automation for lowering my Luxaflex screens, made sure that this automation is triggered by button/btn_45a450/button/6 (checked with MQTT-explorer).
Same automation is triggered when clicking button from second B+ (ID 45_a5d0).
(This is done with Button+ integration v0.0.6 installed, integration reloaded and devices re-added)
To Reproduce
Expected behavior
Different B+'s with different ID's not to influence each-other, not to trigger each-others actions.
Automation:
alias: B+LuxStdkOpen
description: ""
trigger:
entity_id:
condition: []
action:
metadata: {}
target:
entity_id: scene.std_open
mode: single
No automation exists for B+ with id 45_a5d0 on button-6
The text was updated successfully, but these errors were encountered: