-
|
So i am trying to teach in a virtual switch as described in some topics here (and even the wiki). I my case (Eltako fj62/12-36V), i need to use different methods for different switches: 3 times short tap when using a universal button ("Taster") in German How can i do that? A script, a button in lovelace? I would be great if somebody could give me an example. Here my Config:
and my log when selecting A1/A0 via lovelace: |
Beta Was this translation helpful? Give feedback.
Answered by
cubertt
Apr 7, 2023
Replies: 3 comments 7 replies
-
0xFFF69B00 is your base id, right? In HA, once you have done this, you have to "tap" the button by selecting the state in the entity named like "e2m_myEmulatedRocker1_action". What is a bit unclear maybe is that the switch appear as a select. So to double tap you have to set the state to A1 for instance, then None, then A1 again. |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
Thanks, that helped to make the process clear! |
Beta Was this translation helpful? Give feedback.
-
|
It's available in the Device Info of the ENOCEANMQTT device. |
Beta Was this translation helpful? Give feedback.
-
|
It works! Changed the sender id to a different number (same base id) and followed the example here in the discussion () to add a mqqt switch. Perhaps this is not really needed (should be the same as the way you described, but i need them anyway to have nice controls in lovelace. Needed to press it 5 times instead of 3-4 and then the device was controllable. Thanks @mak-gitdev for the work and @tbarbette for the help! |
Beta Was this translation helpful? Give feedback.
Answer selected by
cubertt
-
|
Hello cubertt, i have the same problem. Did you use the same id as the base id or a different one? Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hi vbreit, here is explained how to get the base id: and i am using the sender id (0xFFF69B01) , that means i am adding at least 1 number to the base id (0xFFF69B00) (use excel to get the base id converted to dec , ad the numbers you want and then convert it back to hex (via hex2dec or dec2hex function in excel (e.g. :=hex2dec(your baseid)) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! i have changed the sender id to a new number and then it worked! |
Beta Was this translation helpful? Give feedback.
-
|
After playing with my devices and the virtuall switches, i got another question: Can i define the virtuall switch as a up/down switch? When i try the virtuall switches, they are only recognized as one switch, that means pressing it starts the blinds going down, pressing again stops it and pressing again starts the blinds going up. Lets say i use B0 to teach in, all the others (BI, A0,AI) are doing nothing. I would expect that BI should automatically added as down (or up). |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Check my solution at the end of #1 :) |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This is most likely not the solution for my problem....As i understood you want have the information which status the devices have. Do you use inly virtuall buttons or also real ones? I need to send a Signal: blinds down or blind up. So that i can start watching tv with one click on my remote: But i found a solution /workaround: There are 3 (4) Categories of switches:
Universaltaster (universal (push-)button ): blinds go up and down with the same button (and only for some seconds) So my workaround here is that: I create for every blind 2 mqtt buttons as shown somewhere here in the discussion thats all. ;-.) |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It works!
Changed the sender id to a different number (same base id) and followed the example here in the discussion () to add a mqqt switch. Perhaps this is not really needed (should be the same as the way you described, but i need them anyway to have nice controls in lovelace.
Needed to press it 5 times instead of 3-4 and then the device was controllable.
Thanks @mak-gitdev for the work and @tbarbette for the help!