Hi, I was wondering if anyone has any experience with the Busch-Jaeger free@home system and the implementation into OpenHAB?
From what I have seen, there is almost no support for it and since I have NO idea on how to implement it into OpenHAB, I was wondering if anyone could maybe implement it for me or help me with the implementation.
I would be glad to help as much as possible, but I, unfortunately, can’t write the binding myself since I don’t know how to.
I found the following threads where some user found out, that it runs on an XMPP-Server which is maybe a starting point.
I don’t have saved the code, as I switched to HASS. Here are some sample links for blinds/shutters in Stadlberger’s “home” project (replace with your actuator IDs and base URL):
Implementation in Openhab is quite easy once the Stadlberger API is running.
If you need more instructions I can help with some examples.
Currently I have implemented rollershutters, thermostats (read temperature only), normal lights and dimming lights.
I am working on full control for thermostats and it seems also possible to add the switches, e.g. to see if a switch has been pressed (maybe interesting for scenes).
I have implemented a Busch & Jaeger Free@Home binding for my personal usage.
I currently supports
Free at home bridge
Raffstores / Blinds (stepwise/complete)
Scene activation
No discovery is implemented, but you can add things via PaperUI if you extracted the DeviceIds from BJ AccessPoint.
I would be happy to share the code if someone supports me in extending it for discovery and additional things.
As I do not have other devices available, it will be difficult for me to test further devices.
Based on the great work of Stadlberger, it should not be a big deal to integrate further thing types to the binding.
@Kurtus thanks so much for the offer to help. I actually got it more or less running, but it’s really dirty, so I’m now looking forward to the possibility of creating a more presentable solution!
I think it would definitely be interesting to see if a switch is pressed so you could trigger different scenes depending on, for example, time of day.
I think the main advantages of a native openhab2 binding would be that you could easily control the devices via PaperUI and Discovery could be implemented.
It would be a solution without file configuration, but with the proper openhab ui.
Unfortunately, I do not have the time to further extend the binding for a more convenient usage.
Although personally, I prefer configuration with text file, because I have more control over that.
Still, a proper integration with all feautures is easier to handle also in the case of file configuration.
great if you push the further development of f@h for openhab. I am happy to support you.
I will clean up the code a little bit and then publish it via github.
Hi,
installed BJ Free@Home 2 years ago in our house. As I am not satisfied with the BJ software and Android app I am looking forward to use openhab. Recently bought a Raspberry Pi an installed openhab.
I can support testing bindings ect… I also have basic programming skills…and interested to help here as well… looking forward to test the binding from @ruebox.