Wow, thank you Stian.
i have created a virtual switch:
i can switch it, on “idp0000” i see the value change (in cloud api).
but i dont get a reply in f@h (also in OH3) if the switch is on (“odp0000” in cloud api).
My question is, how you handle the virtual switch in combine with oh ?
Have you a additional tool (node red etc.) to update the switch status for f@h ?
Try to reboot f@h access point. This helped me to get it working
i reboot already but it doesnt work.
i dont know how the virtual switch should work without odp feedback ?
i think i need there a script or something else to give a feedback to switch ?
Have you create a virtual switch and can also switch them in f@h (incl. feedback with status changes - on/off), so you can get it into openhab ?
As pointed out, I also had to do a couple of sysap reboots to get the virtual switches working. Then I included the switches in the sysap room layout, and verified operable within sysap (able to switch on/off and also get the actual state display).
Virtual switches are autodiscovered by the openHAB binding, and thus enable regular operation from within OH.
As a last measure, if still not able to get your virtual switches working within sysap, you could try the following (although not recommended by ABB):
virtualDeviceTTL="-1" and virtualDeviceEmulation="SwitchingActuator"
<device zombie="false" serialNumber="6000________" virtualDeviceType="SwitchingActuator" nativeId="_____________" virtualDeviceTTL="-1" virtualDeviceLastRegistered="1613406919" interface="vdev:___________" virtualDeviceEmulation="SwitchingActuator"/>
Here is my virtual switch, can you take a look at it, if i make everything right ?
{
"46____________________": {
"devices": {
"60001_____": {
"channels": {
"ch0000": {
"displayName": "Badfenster gr. Sensor",
"floor": "02",
"functionID": "0007",
"inputs": {
"idp0000": {
"pairingID": 1,
"value": "0"
},
"idp0001": {
"pairingID": 2,
"value": "0"
},
"idp0002": {
"pairingID": 3,
"value": "0"
},
"idp0003": {
"pairingID": 4,
"value": "0"
},
"idp0004": {
"pairingID": 6,
"value": "0"
},
"idp0005": {
"pairingID": 48,
"value": ""
},
"idp0006": {
"pairingID": 323,
"value": ""
},
"idp0007": {
"pairingID": 333,
"value": ""
},
"idp0008": {
"pairingID": 334,
"value": ""
}
},
"outputs": {
"odp0000": {
"pairingID": 256,
"value": "0"
},
"odp0001": {
"pairingID": 257,
"value": "0"
},
"odp0002": {
"pairingID": 273,
"value": ""
},
"odp0003": {
"pairingID": 305,
"value": ""
},
"odp0004": {
"pairingID": 321,
"value": ""
},
"odp0005": {
"pairingID": 335,
"value": ""
},
"odp0006": {
"pairingID": 336,
"value": ""
}
},
"room": "09"
}
},
"displayName": "Badfenster gr. Sensor",
"floor": "02",
"interface": "vdev:_______________",
"nativeId": "abc124",
"room": "09",
"unresponsive": false
}
}
}
}
I have 5 times restart my sysap and nothing changes.
This is the backup file:
<device softwareId="0001" softwareVersion="0.1" deviceId="0001" nameId="0001" domainAddress="BAE7" isExternal="true" individualAddress="A17E" profile="0810" maxAPDULength="37" compilerVersion="00000000" buildNumber="00000000" iconId="FFFF" protocolVersion="00FF" minConfigVersion="0000" deviceFlavor="00" functionId="FFFF" interface="vdev:_____________" heartbeatInterval="02D0" serialNumber="6000_____" commissioningState="ready" copyId="5">
<attribute name="displayName">Badfenster gr. Sensor</attribute>
<attribute name="lastReset">20210521100333536</attribute>
<attribute name="nativeId">abc124</attribute>
<channels>
<channel mask="FFFFFFFF" nameId="0001" sameLocation="true" i="ch0000" cid="60000148">
<attribute name="functionId">7</attribute>
<attribute name="selectedIcon">b</attribute>
Seems about right, but in your backup file, you should find the part to update by searching for devices manufacturer="6000".
Then ensure to update with virtualDeviceTTL="-1" and virtualDeviceEmulation="SwitchingActuator". I.e. similar to
<device zombie="false" serialNumber="6000________" virtualDeviceType="SwitchingActuator" nativeId="_____________" virtualDeviceTTL="-1" virtualDeviceLastRegistered="1613406919" interface="vdev:___________" virtualDeviceEmulation="SwitchingActuator"/>
ahh ok, thank you.
my backup shows everything except: virtualDeviceEmulation=“SwitchingActuator”
<device zombie="false" serialNumber="6000________" virtualDeviceType="SwitchingActuator" nativeId="abc124" virtualDeviceTTL="-1" virtualDeviceLastRegistered="1621663984" interface="vdev:____________" virtualDeviceEmulation=""/>
Anyway i’m litte afraid to change the backupfile …
Is there no chance with postman to write this Datapoint ?
Not aware of any Postman input to achieve virtualDeviceEmulation=“SwitchingActuator” , so I believe updating the backup file is the only way.
If you take a fresh back up before changing the backup file, you should have a fallback option if you still don’t get the virtual setup to work. I did change the backup file, and got my virtual switches working, and the overall system was working as before.
Perfect, i did the backup way, and it works now 
A big thank you !!!
One last question:
Have you virtual devices like window sensor ?
When yes, have i put “WindowSensor” in the virtualDeviceEmulation ?
Or can i do every Device:
Hi Janno,
can you explain how you use ch0008 ?
I have no idea ho it works (Dimmer thing ?)
Have testet the window sensor.
But the sensor only have opd points. So i cant write there with oh…
Ah, true, the binding is currently set up to autodiscover all virtual devices as virtual switches.
However, you should be able to create a manual window sensor in OH, pointing to the virtual window sensor you have created under F@H / Postman by using the device serial. Windos sensors in the binding is set up default with ch0001 and odp0000 and odp0001.
Hello at all,
today i install openhabian3 (Openhab3) and I want to Connect my Free@Home. Version 3.1. Yesterday I try it with openhab2 and older version of free@home, but nothing. I cannot connect my free@home with openhab2 /3. Always: Initializing… I use my Username from my Web Plattform Free@Home and my password. IP Adress = this ip, where I can connect to free@Home on Web. What I do wrong? And what’s this: Unique ID? Can I ignore this? I connect sucsellfully Homebridge with Free@Home, but I want to install Netatmo etc on Free@Home and there I must use Openhab. Please help me. Thx so much
Hey Andreas,
whats your setup ? Do you use OH3 on raspberry ?
Point 1: you have to use “Installer” as login name and your password.
Point 2: have you create a free@home bridge as thing ? There you have to sign in (Point 1) ?
Point 3: Where you read unique id ?
And like always, do you already restart openhab after installing the binding ?
May Way is:
Settings, things, plus, free@home Binding, free@home Bridge, Name installer Passwort my Password like web and app. Ip Adresse like Web See Screenshot. And reboot Over
And it is OHP3 raspberry 4
You should not be using “Installer” as username, rather a user name which has installer user rights (as shown under the sysap interface).
Under Bridge settings, you could also try to disable Console Debugger.
It would also be useful if you provide relevant log details as part of the “initializing” process.
