ok thank you.
Is in future a official binding planed ?
As mentioned previously in this forum, due to the usage of an external library, which is customised to work with Free@Home (thus not approved by the official OH repo), there are no immediate plans to do a pull request for the official binding repo.
Hello,
im working on my installation with f@h binding.
Now i see that my wallswitches (Sensoreinheit 2 Fach) also found by the binding.
Im a little bit confused because they found as :raffstore ?
Also nothing happens when i switch anything by the binding thing ?
Is there a wallswitch implementation planed ?
Or is it perhabs found by the binding ?
Thanks
Stephan
Hello,
I’m still on openhab 2 org.openhab.binding.freeathome-2.5.1-SNAPSHOT.jar - will this version work with the freeathome firmware 2.6 ?
More details would be required to help you further.
Are you running a wireless og wired setup? What is the DeviceTypeId as recognised from autodiscovery in openHAB?
Will not give a definite answer, but later 2.5 versions of the binding is confirmed to work with firmware 2.6: E.g. Link
I have firmware 2.6.1 now and it works. I have the very first hardware revision of the AP (1.0 I guess).
I have a wired installation.
This Things found by Auto Scan:
When i create a thing with linked channel, i cannot switch via raffstore items the Sensoreinheit.
Following Post, we did an effort to implement the 1002 devices, but did not manage to identify the correct channels and idps/odps.
You could try to play around to identify correct input. Try creating 2 switch things manually for each device serial. For example, as listed below:
- Switch: ABB700D2581E / ch0000 / idp0000 / odp0000
- Switch: ABB700D2581E / ch0001 / idp0000 / odp0000
Ok, i tried around and the created switch was updated by channel 0000 when i switch the Sensoreinheit.
But only updated, i cannot switch via thing/item the Sensoreinheit.
The Log in f@h shows an info Tag:
Instead of an switch tag from the Sensoreinheit itself:
Are you looking to use your sensor rockers as “binary trigger” inside openhab regardless of how they are configured and paired inside free@home?
So for example on my Sensor/dimming (Busch-Jaeger - Sensor/Dimmaktor 2/1-fach, Wireless für Busch-free@home®) units the model is like this:
"ABB700CB4BB5": {
"floor": "01",
"room": "03",
"interface": "RF",
"displayName": "Schalter AZ",
"unresponsive": false,
"channels": {
"ch0000": {
"displayName": "Schalter AZ",
"functionID": "1",
"inputs": {
"idp0000": {
"pairingID": 256,
"value": "0"
},
"idp0001": {
"pairingID": 18,
"value": "0"
},
"idp0002": {
"pairingID": 273,
"value": "0"
},
"idp0003": {
"pairingID": 257,
"value": "0"
},
"idp0004": {
"pairingID": 261,
"value": "0"
},
"idp0005": {
"pairingID": 278,
"value": "0"
},
"idp0006": {
"pairingID": 262,
"value": "0"
},
"idp0007": {
"pairingID": 1120,
"value": "0"
},
"idp0008": {
"pairingID": 61698,
"value": "0"
},
"idp0009": {
"pairingID": 272,
"value": "0"
},
"idp000a": {
"pairingID": 277,
"value": "0"
},
"idp000b": {
"pairingID": 354,
"value": "0"
},
"idp000c": {
"pairingID": 355,
"value": "0"
}
},
"outputs": {
"odp0000": {
"pairingID": 1,
"value": "0"
},
"odp0001": {
"pairingID": 16,
"value": "0"
},
"odp0002": {
"pairingID": 32,
"value": "0"
},
"odp0003": {
"pairingID": 33,
"value": "0"
},
"odp0004": {
"pairingID": 2,
"value": "0"
},
"odp0005": {
"pairingID": 3,
"value": "0"
},
"odp0006": {
"pairingID": 4,
"value": "0"
},
"odp0007": {
"pairingID": 40,
"value": "0"
},
"odp0008": {
"pairingID": 1088,
"value": "0"
},
"odp0009": {
"pairingID": 1089,
"value": "0"
},
"odp000a": {
"pairingID": 1090,
"value": "0"
},
"odp000b": {
"pairingID": 1091,
"value": "0"
},
"odp000c": {
"pairingID": 1094,
"value": "0"
},
"odp000d": {
"pairingID": 1098,
"value": "0"
},
"odp000e": {
"pairingID": 61697,
"value": "0"
},
"odp000f": {
"pairingID": 352,
"value": "0"
},
"odp0010": {
"pairingID": 353,
"value": "0"
}
}
},
"ch0003": {
"displayName": "Schalter AZ",
"functionID": "1",
"inputs": {
"idp0000": {
"pairingID": 256,
"value": "0"
},
"idp0001": {
"pairingID": 18,
"value": "0"
},
"idp0002": {
"pairingID": 273,
"value": "0"
},
"idp0003": {
"pairingID": 257,
"value": "0"
},
"idp0004": {
"pairingID": 261,
"value": "0"
},
"idp0005": {
"pairingID": 278,
"value": "0"
},
"idp0006": {
"pairingID": 262,
"value": "0"
},
"idp0007": {
"pairingID": 1120,
"value": "0"
},
"idp0008": {
"pairingID": 61698,
"value": "0"
},
"idp0009": {
"pairingID": 272,
"value": "0"
},
"idp000a": {
"pairingID": 277,
"value": "0"
},
"idp000b": {
"pairingID": 354,
"value": "0"
},
"idp000c": {
"pairingID": 355,
"value": "0"
}
},
"outputs": {
"odp0000": {
"pairingID": 1,
"value": "0"
},
"odp0001": {
"pairingID": 16,
"value": "0"
},
"odp0002": {
"pairingID": 32,
"value": "0"
},
"odp0003": {
"pairingID": 33,
"value": "0"
},
"odp0004": {
"pairingID": 2,
"value": "0"
},
"odp0005": {
"pairingID": 3,
"value": "0"
},
"odp0006": {
"pairingID": 4,
"value": "0"
},
"odp0007": {
"pairingID": 40,
"value": "0"
},
"odp0008": {
"pairingID": 1088,
"value": "0"
},
"odp0009": {
"pairingID": 1089,
"value": "0"
},
"odp000a": {
"pairingID": 1090,
"value": "0"
},
"odp000b": {
"pairingID": 1091,
"value": "0"
},
"odp000c": {
"pairingID": 1094,
"value": "0"
},
"odp000d": {
"pairingID": 1098,
"value": "0"
},
"odp000e": {
"pairingID": 61697,
"value": "0"
},
"odp000f": {
"pairingID": 352,
"value": "0"
},
"odp0010": {
"pairingID": 353,
"value": "0"
}
}
},
"ch0008": {
"floor": "01",
"room": "03",
"displayName": "Arbeitszimmer Decke",
"functionID": "12",
"inputs": {
"idp0000": {
"pairingID": 1,
"value": "0"
},
"idp0001": {
"pairingID": 16,
"value": "0"
},
"idp0002": {
"pairingID": 17,
"value": "16"
},
"idp0003": {
"pairingID": 2,
"value": "0"
},
"idp0004": {
"pairingID": 3,
"value": "0"
},
"idp0005": {
"pairingID": 4,
"value": "0"
},
"idp0006": {
"pairingID": 18,
"value": "0"
},
"idp0007": {
"pairingID": 6,
"value": "0"
}
},
"outputs": {
"odp0000": {
"pairingID": 256,
"value": "0"
},
"odp0001": {
"pairingID": 272,
"value": "0"
},
"odp0002": {
"pairingID": 273,
"value": "0"
},
"odp0003": {
"pairingID": 257,
"value": "0"
}
}
},
"ch000b": {
"displayName": "Schalter AZ",
"functionID": "1",
"inputs": {
"idp0000": {
"pairingID": 256,
"value": "0"
},
"idp0001": {
"pairingID": 272,
"value": "0"
},
"idp0002": {
"pairingID": 354,
"value": "0"
},
"idp0003": {
"pairingID": 288,
"value": "0"
},
"idp0004": {
"pairingID": 257,
"value": "0"
},
"idp0005": {
"pairingID": 273,
"value": "0"
},
"idp0006": {
"pairingID": 261,
"value": "0"
},
"idp0007": {
"pairingID": 277,
"value": "0"
},
"idp0008": {
"pairingID": 355,
"value": "0"
},
"idp0009": {
"pairingID": 293,
"value": "0"
},
"idp000a": {
"pairingID": 262,
"value": "0"
},
"idp000b": {
"pairingID": 61698,
"value": "0"
},
"idp000c": {
"pairingID": 1120,
"value": "0"
}
},
"outputs": {
"odp0000": {
"pairingID": 1,
"value": "0"
},
"odp0001": {
"pairingID": 16,
"value": "0"
},
"odp0002": {
"pairingID": 352,
"value": "0"
},
"odp0003": {
"pairingID": 32,
"value": "0"
},
"odp0004": {
"pairingID": 33,
"value": "0"
},
"odp0005": {
"pairingID": 2,
"value": "0"
},
"odp0006": {
"pairingID": 3,
"value": "0"
},
"odp0007": {
"pairingID": 4,
"value": "0"
},
"odp0008": {
"pairingID": 40,
"value": "0"
},
"odp0009": {
"pairingID": 353,
"value": "0"
},
"odp000a": {
"pairingID": 61697,
"value": "0"
},
"odp000b": {
"pairingID": 1088,
"value": "0"
},
"odp000c": {
"pairingID": 1089,
"value": "0"
},
"odp000d": {
"pairingID": 1090,
"value": "0"
},
"odp000e": {
"pairingID": 1091,
"value": "0"
},
"odp000f": {
"pairingID": 1094,
"value": "0"
},
"odp0010": {
"pairingID": 1098,
"value": "0"
}
}
}
}
},
So as I have two sensor rocker it would be ch0000/opd0000 to listen if left rocker was switched and ch0003/opd000 for the right rocker. If there is only one rocker it would be simply ch0000/opd0000. The sensor rockers are represented by functionID 01. The ch0008 is representing the dim actuator behind the 2-fold sensor.
BTW: @kjoglums if helpful I could share to quite comprehensive models from free@home systems with you (json).
If you would like to use the LED Status of your rocker 2-fach switch.
This will work as a thing:
// Schalter 2-fach
Thing switch ABB700xxx_ch0000 "Status LED links" @ "Toberaum" [ deviceId="ABB700xxx", channelId="ch0000", dataPointId="idp0000", dataPointIdUpdate="odp0000" ]
Thing switch ABB700xxx_ch0003 "Status LED rechts" @ "Toberaum" [ deviceId="ABB700xxx", channelId="ch0003", dataPointId="idp0000", dataPointIdUpdate="odp0000" ]
If someone know how to read out scenes from free@home and use it as a trigger in OH. This would be helpfull to me. Best Regards
As F@H scenes are not published on the bus (i.e. the scene triggering itself is not reported), I have not found a direct way to identify if/when a scene is triggered.
Thus, I have ended up creating virtual switches under F@H sysap (ABB developer program), and then included the virtual switches as part of the different scenes. Virtual switches are identified by the OH binding, and state changes are reported on the bus, thus enabling a way to identify when a F@H scene is triggered (as the connected virtual switch will change state).
Having the virtual switches, I have created scenes under F@H which I have access to from my touch panels, enabling me to control OH devices outside F@H. E.g. Volvo scene pressed from touch panel —> start heater.
Thank you, with channel 0000 and 0003 it works.
So i can switch with the rockers other devices (e.g shelly) via openhab.
I have AP from 1st generation, so i cant get the abb developer programm …
So i use the “hue emulation” from openhab to create virtual switches/lights in f@h.
This virtual light i can use like stian to link/create scenes in f@h and oh.
Thank you for your hints, so it works also for me.
Can you explain me how i use ch0008?
Have i create a dimmer thing ?
I also have the 1st gen sysap, and use the ABB developer program with cloud API.
I just found out, that this thing configuration is not working for the wireless comfort thermostat but works fine for a wired thermostat. Does anyone know the reason ?
//Thermostat FAN
Thing thermostat ABB700xxx “Therm. Kellereingang” @ “Keller” [ deviceId=“ABB700xxx”, channelId=“ch0000”, dataPointIdSwitch=“idp0012”, dataPointIdSwitchUpdate=“odp0008”, dataPointIdTarget=“idp0016”, dataPointIdTargetUpdate=“odp0006”, dataPointIdEcoUpdate=“odp0009”, dataPointIdEco=“idp0011”, dataPointIdRoomUpdate=“odp0010” ]
Back to the topic before:
I think there must be a way to catch the signal “SceneControl” from the rocker switch if you double click on the switch or even the Switch On/Off from the rocker. In the free @ home monitor I can see the signal. → see attached picture.exclamation point. However with the settings I posted before I can only read and write the yellow marked adress → Info LED on/off. Does anyone know what to change to read/write the adresses with the exclamaton mark ?
1 Like
How you managed this ?
I have in the next app no settings with local/cloud api like explained in the documentation.
And by /swagger i get this error:
Cloud API is not swagger compatible. And it seems like cloud API is still available.
-
Become an ABB developer partner in 4 steps:
https://developer.eu.mybuildings.abb.com -
Documentation/tutorials
- How to
https://developer.eu.mybuildings.abb.com/fah_cloud/ - Tutorial for setting up Postman software (used to create virtual switches etc)
https://developer.eu.mybuildings.abb.com/tutorials