just for information, I’ve updated my Busch Jäger SysAp to version 3.2.1 and it works with the binding.
Busch Jäger FW 3.2.1
Openhab 4.0.3
1 Like
Thank you the test.
I was pretty lost in the last time. But I am also using the binding with an older SysAP since 1.5 years without any issues. Even the complete kitchen lighting is solved with this binding an OpenHAB by us.
Could you give some hint of your config?
sorry for that… I do not have this issues. I do not know why. But the scan is Working on my side
You can find the latest update with all fixes and tested in OpenHAB 4.x
1 Like
I had to remove and add the gateway after the update, but now it works fine.
The bug where the bindings were no longer listed in the “Add Thing” menu has also been fixed.
Here my setup:
Busch Jäger 3.2.3
openHAB 4.1.0 Release Build
Thank you
Hi @UhA,
do you have a timetable for the “channel for blind position is missing” Bug ?
This is probably a key feature for me…
Thx Stephan
I have updated to the latest version of SysAp and everything seems to be working.
Version 3.2.4 Revision 11428
One Sideeffect:
The web interface of the SysApp itselfs only works with Edge. Chrome is no longer supported, because Chrome redirects automatically to https, and https doesn’t work anymore.
@UhA Is there any news about the “channel for blind position is missing" bug?
I’ve just updated the SysApp to 3.3.2 and it is still working.
Warning: The Binding here ist deprecated, the binding has been moved to official Add-Ons.
But be careful it has a new name “freeathome” which is the same name as the other free at home binding, see:
https://community.openhab.org/t/busch-jaeger-free-home/
Hello,
I’m new to the community and I’m not quite sure if this is the right way to ask my questions, if not, please advise me on the correct way to proceed.
First of all, the freeAtHome binding is exactly what I needed. Unfortunately, I am having some difficulty getting the binding to work correctly. During my attempts I have encountered various error messages which I do not know whether they are due to my system, my configuration or the binding.
The first problem occurs when I create the free@home gateway as a bridge. I then find the following message in the log:
– 2024-10-02 12:53:53.386 [WARN ] [org.eclipse.jetty.client.HttpClient ] - Calling setExecutor() while started is deprecated
Is this already a problem or can I disregard this as a warning?
PS: Other bindings I have tested my environment with, e.g: Automover Binding, work
Thank you for any info
freeET
Raspberry pi5 | openhabian (64 bit) | SysApp 3.2.2 | openHAB 4.2.1
hello @freeET,
I also have
Calling setExecutor() while started is deprecated
in my logfiles, but the binding runs.
Could you provide a screenshot of your ree@home gateway configuration?
Hello ML 1982,
sorry for late reply. is that what you mean?
Unfortunately, I don’t understand how this can be related to the message in the log.
The gateway is online, so the next step would be to add things. Did you try it?
I can’t help you with the warning, but in my opinion you can ignore it for now. We can investigate that later.
Try to add some Busch-Jäger Things.
Thanks for your help.
I have done this. I used the scan function and then selected a single Thing. A simple on-off switch.
Then I added a link. When I press the switch via this link, the light goes on and off as desired. This is as desired, but the following messages appeared in the log during this process.
2024-10-06 16:27:17.204 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI ‘channel-type:freeathome:config’
2024-10-06 16:27:17.205 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI ‘channel-type:freeathome:config’
2024-10-06 16:27:17.207 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for new thing during update ‘freeathome:device:cbd055e90d:ABB700CBBE5E’: {thing/channel=Config description channel-type:freeathome:config for freeathome:device:cbd055e90d:ABB700CBBE5E:ch0000#switch-on-off not found, although we checked the presence before.}
2024-10-06 16:27:17.209 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI ‘channel-type:freeathome:config’
2024-10-06 16:27:17.209 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI ‘channel-type:freeathome:config’
2024-10-06 16:27:17.210 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI ‘channel-type:freeathome:config’
2024-10-06 16:27:17.210 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI ‘channel-type:freeathome:config’
2024-10-06 16:27:17.213 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for new thing during update ‘freeathome:device:cbd055e90d:ABB700CBBE5E’: {thing/channe
Obviously everything seems to be working up to this point, as no further warnings appear in the log when the switch is used.
Next, I created a dimmer switch from the inbox as a thing.
Unfortunately, I cannot select any channels for this thing to add a link.
This is the case with some things, but not with others. What could be my fault?
@freeET I just tried it, and it seems that it works.
but lets compare the dimmer within the Busch Jäger system:
