Busch-Jaeger Free@Home

plugg3n · December 27, 2019, 1:19pm

Debug details:

==> /var/log/openhab2/openhab.log <==
2019-12-27 14:18:09.514 [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing ‘freeathome:bridge:933a1e30’ takes more than 5000ms.
2019-12-27 14:18:09.696 [WARN ] [home.handler.FreeAtHomeBridgeHandler] - rocks.xmpp.core.session.NoResponseException: Timeout while waiting on advertised authentication mechanisms.

==> /var/log/openhab2/events.log <==
2019-12-27 14:18:09.697 [hingStatusInfoChangedEvent] - ‘freeathome:bridge:933a1e30’ changed from INITIALIZING to OFFLINE (COMMUNICATION_ERROR): Can not connect to SysAP with address: 10.100.100.134

==> /var/log/openhab2/openhab.log <==
2019-12-27 14:18:09.700 [WARN ] [home.handler.FreeAtHomeBridgeHandler] - Could not successfully get the getAll.xml from sysAP. Can happen if connecting to server takes too long.

kjoglums · December 27, 2019, 2:23pm

Strange, based on your debug log, where you still have Timeout while waiting on advertised authentication mechanisms, it seems like you haven´t fully been able to clean cache.

For me, running OpenHabian, the following steps enabled me to run F@H binding successfully after downgrading from OH 2.5.0 to 2.4.0:

Delete F@H bridge from PaperUI
ssh into OpenHab service
Stop OpenHab service: sudo systemctl stop openhab2.service
Remove tmp files: sudo rm -rf /var/lib/openhab2/tmp/*
Remove cache files: sudo rm -rf /var/lib/openhab2/cache/*
Remove backup files: sudo rm -rf /var/lib/openhab2/jsondb/backup/*
Remove cache: sudo openhab-cli clean-cache
Restart OpenHab service: sudo reboot
Create new F@H bridge in PaperUI

plugg3n · December 27, 2019, 2:39pm

So i pretty sure i did the same thing last time, maybe not in the exact same sequence, anyhow. It now works for me, thanks for the help

Matthijs · December 28, 2019, 1:02pm

Thanks for the quick reply Stian!

Yes I am using OH 2.5, I think (latest OpenHabian release).

I am a bit confused when it comes to version numbers. OpenHabian (what I’m using) uses 1.x version numbers; now 1.5 is the latest version. But this contains OpenHab 2.5 I assume. But since I don’t know how to downgrade I just picked the OpenHabian v1.4.1 version for the RPI to see if that helps…

Matthijs · December 28, 2019, 2:53pm

Well, that didn’t help; downloaded an older OpenHabian (1.4.1) image but it still installs the latest OpenHab version (2.5); now the question is; how do I downgrade openHAB 2.5 to 2.4 ?

EDIT: Nevermind; a downgrade is more simple then I thought. Just had to run
sudo apt-get install openhab2=2.4.0-1

Now I’m running OpenHab 2.4 and configured the FreeAtHome bridge and it went online instantly :D.

kjoglums · January 4, 2020, 11:55pm

Then I finally believe I made a breakthrough to update/enable Free@Home binding for OH 2.5.0. I myself have been struggling getting the binding running with 2.5.0, and have been “stuck” at OH 2.4.0. If others would be willing to test, the jar file could be downloaded at:

https://1drv.ms/u/s!Aoa2B3iUQJCngoBIKRn58RgfxwCKzA?e=8lJY5o

Steps to follow (based on an existing F@H setup in OH using jar file in openhab2-addons folder and running OH from Raspberry):

Delete existing F@H bridge (note thing ID: to be used for “new” Bridge)
Remove jar file from openhab2-addons folder
ssh into OpenHab service (Raspberry PI)
Stop OpenHab service: sudo systemctl stop openhab2.service
Remove tmp files: sudo rm -rf /var/lib/openhab2/tmp/*
Remove cache files: sudo rm -rf /var/lib/openhab2/cache/*
Remove backup files: sudo rm -rf /var/lib/openhab2/jsondb/backup/*
Remove cache: sudo openhab-cli clean-cache
Restart OpenHab service: sudo reboot
Update OH to 2.5.0
Add jar file from link above to openhab2-addons folder
Try to create new bridge from PaperUI (using thing ID from before to enable automatic link to existing things)
If not able to establish connection, try rebooting OH once again
With successful connection, existing things should be automatically re-linked with the “new” bridge as long as the initial thing ID has been used during configuration in PaperUI.

Note
New OH 2.5.0 users, without having existing F@H setup in OH could do a fresh setup adding the jar file from link above into openhab2-addons folder and setting up bridge in PaperUI and performing an inbox scan for things to add.

Additional features from 2.4.0 version

Disovery/implementation of virtual switches as created from ABB development program
Disovery/implementation of motion detectors without relay

Jens_Hoffmann · January 6, 2020, 4:25pm

Hi Stian,

have you tried to create a virtual switch via fhapi (ABB developer programm)?

Every time when I try to register a virtual switch my access point do a restart. Thus the registration fails with error code 100A.

Thanks,

kjoglums · January 6, 2020, 5:44pm

Yes, I have successfully created virtual switches under F@H SysAp (following ABB developer program), and I have implemented the switches in OH through revised code (as implemented in jar file from previous post).

Although, I also struggled in the beginning, and was in dialogue with ABB developers to trouble shoot issues. This was in the phase between SysAp version 2.3.2 and 2.4.0, and the issues should be resolved for SysAp 2.4.0 (at least for me). My issue was that I did not get the correct setup for the fhapi “user” under SysAp setup (as illustrated in the ABB tutorial) although following ABB guide, and I was not able to write/put anything to SysAp (using Postman). Got it working, and still works.

Next challenge for me, after having created virtual switch from Postman, was to be able to operate the switch under SysAp. The switch was found and implemented in SysAp, but it was not possible to perform state change (ON/OFF). I had to reboot SysAp, and eventually was able to operate switch, and could then implement switch in OpenHab.

Cuver77 · January 7, 2020, 8:27pm

Thanks for your information.

So I have to contact the ABB developers to solve my issue. Which way did you use to contact the support? I didn’t find any contact information in the developer portal.

kjoglums · January 7, 2020, 9:27pm

I have been in contact with ABB via:
Smarter Home Developer --> DE-SmarterHomeDeveloper@abb.com

stemeda · January 11, 2020, 4:46pm

Hello, I’m using successfully this binding with SysAP 2.4. I’m new to OpenHab and I want to start a bash script if a scene in free@home is started.

So I created a new rule “test.rules” with content

rule "test"
when
  Item FFFF48000003 received update
then
  logInfo("test", FFFF48000003.state)
end

The rule is loaded without error. If I active the scene over the f@h Android App nothing is written to log.

Maybe the ID of the item is wrong. In PaperUI " TV_Neue Szene_4800_FFFF48000003" is shown as the name of the item.

In events.log file is not shown that the scene is activated in f@h. Is it already possible to fetch it in OpenHab?

Does anyone have a hint?
Thanks

kjoglums · January 11, 2020, 5:56pm

Well, actually, if the scene is activated on the F@H side (i.e. via F@H switch, action etc), the F@H SysAp does not report the actual update/state change for the scene, and will thus not be able to trigger a OpenHab rule as you try to achieve. If the scene is triggered from OpenHab side, the update/state change for the scene should be reported.

For my own setup, I have created virtual switches (using the ABB developer program), which again are linked to the scene in F@H SysAp (virtual switch ON/OFF). I.e. when scene is triggered from the F@H system, the belonging virtual switch is switched ON. The virtual switches are included in the OpenHab setup, and these switches report “ON/OFF”, and could be used to trigger rules similar to what you try to achieve.

Also, I see you are using “Item FFFF4800003”, but is this item actually linked to a channel of your scene thing?

For instance, for one of my scenes, I have linked an item AltAvActivate which is linked to my scene thing as follows:

Switch   AltAv_Activate   "Activate scene" <mediacontrol>  {channel="freeathome:scene:FFFF48000006:activate"}

stemeda · January 11, 2020, 7:15pm

@kjoglums thanks for your fast feedback!

Is it transmitted from f@h to OpenHab when a hardware button is pressed?

kjoglums · January 11, 2020, 7:53pm

When you activate a regular F@H switch (e.g. regular relay switch, dimmer switch etc), either via hardware switch or F@H app, the activation is reported by F@H SysAp (ON/OFF, dimmer value etc), and is transmitted from F@H to OH. However, scene activation itself on the “F@H side” (switch, F@H app etc) is not reported by the F@H SysAp (only state change of the things/channels involved in the scene), and there is thus “nothing” to transmit from F@H to OpenHab for scene activation, and one would therefore not be able to track/log scene activation as a ON/OFF feature. That is the reason why I have linked virtual switches to my scenes, to be able to detect actual scene activation from “F@H” side.

stemeda · January 12, 2020, 6:09pm

Okay, thanks again for feedback!

I read the documentation of ABB developer program (https://developer.eu.mybuildings.abb.com/getting-started). Am I right that you can only create virtual switches by connecting your SysAp to the cloud? I tried to use the URLs for local IP (eg. http://sysap/fhapi/v1/api/rest/configuration) but the response is HTTP 404

kjoglums · January 12, 2020, 8:45pm

That is true: You will only be able to create virtual switches by connecting to SysAp via cloud. I.e. you need to follow the 3 steps shown in the bottom of page Sign up / Request / Subscribe. Then you will need to download the Postman software and follow the ABB Tutorials.

The cloud connection is only required for the creation of the virtual switches. Once the switches are created, and recognised in the SysAp GUI, you can play around with the switches under regular running environment.

Joost85 · January 13, 2020, 7:26pm

Hi everyone, I’ve been messing around with the free @ home binding in OpenHAB for a while. And … by now I have reached the point where the binding is connected with my Sysap. Unfortunately I only see my BJ scenes in the list of Things. And adding a switch manually gives unfortunately no result. Is there anyone who can get me started? Do I have to configure something manually?

I am not very familiar with programming, so any explanation please in layman language;) Thanks in advance!

Ultimately, I want my free@home switches connect with Apple Homekit. Is there anyone who has this working already?

kjoglums · January 14, 2020, 7:26am

So, I understand you have your bridge Online.

However, are you not getting any autodiscovered things in PaperUI when you go to “Inbox” —> Add —> “Free@Home binding”? What is your log showing when you try to run autodiscovery from inbox?

Joost85 · January 14, 2020, 6:12pm

Hi Stian,

This is how the logs look like (sorry, as a new user i can’t upload files so I had to copy/paste):

2020-01-14 18:10:56.909 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘freeathome:switch:BEED7F330018_ch0000’ to inbox.