I have the Raspberrymatic add-on installed on my HA (RB3) and I need to use/create a virtual button to switch an Homematic IP actuator (HmIP-FSM) for 3 sec. The actuator controls a magnetic lock for my pedestrian gate. I have to mention that I am a fresh user of HA and I don’t have any code porgraming knoledge. So, that being said… could someone help me with some detailed instructions?
Thanks in advance
Cosmin
hm… I don’t have an HmIP-FSM running atm… so I don’t know what entities this device already provides to HomeAssistant…
This would be a good information to check, if there’s already something
Anyway - WHAT I do know, since I just switched to RaspberryMatic, the RaspberryMatic does provide virtual keys … which you could use.
Now, you do have two options:
Do the programming in RaspberryMatic itself → Configure the actions there for one of the virtual keys and just display the entity in your HomeAssistant
or - implement an automation inside of HomeAssistant directly…
I already tried to make the automation in Raspberrymatic, but it doesn’t show in HA… Maybe I don’t know were to look for it. Tried direct connection and programming.
each of the devices will provide 100 entities (50 short press, 50 long press)
By default, they are hidden in the configuration:
So… now, you can create your program in RaspberryMatic - and assign it to one of the virtual keys.
In HomeAssistant, these entities are type Button - so you can just place it on your dashboard, and when pressed, it will trigger the program setup in your Raspberry matic
You created a direct connection or a program with conditions? I need it to switch on for short period of time, say 3 seconds and then go off, because it switches an electromagnetic lock, and the coil will fail if it’s powered for a long period of time.
I created the automation in Raspberrymatic, and it works as it should but in HA when I press the virtual button I created as you indicated, it does nothing.
You are absolutely right. By mistake I’ve activated a BidCos RF instead a HmIP-RCV. Now I activated the correct one and it works as you said. Many thanks! Much apreciated.
If I may add my recommendation: you should probably switch to a “Direktverknüpfung”. If done properly, the turn on command includes the duration for which the switch should be turned on. So even if the automation would start and for some reason abort within this short time period, the actor would still switch off again. Actually I’m doing the same thing with my door-buzzer, which also would be fried if powered on for too long.
This is how the “Direktverknüpfung” looks like in my case:
@danielperna84 Thanks for the tip. I made the direct connection last night, as a test, and it worked for me, so now I am using it with the virtal button.