Great! And thanks again!! No need to apologise for a delayed reply. You have no obligation to help us!
So the first thing worked - changing to F6_02_02 did it. So now I can ask Google to turn it on and it turns on instead of off.
But for some reason the listener component is not working.
To determine the Id, I used the paper ui to add a thing, and it gave me a simple push button. I used that id and made the changes you said.
[Edit] I actually got it working, but to do so had to go into paper ui and link the listener to the husa device. Is that supposed to be necessary? It worked, but now I have two items in the control panel. And it seems that my ability to control or over Google Assistant is a bit laggy now. But that could be unrelated.
Thoughts?
Thanks again for everything! Youâre quite awesome for being willing to help.
Hi Daniel.
I found a solution for the reconnect problem.
One of my enocean components is a psc234 measurementSwitch.
When I define the component, the instantpower channel automatically starts a polling interval (D2_01_04). So a lost connection can be detected and the state of the bridge goes to offline. Than a reconnect starts automatically.
@fruggy83
The binding is great. I use it with all my fsr14, fsb14 and fud14.
Thank you for the hard work!
Next step is to bind my Eltako FUTH65D.
Are they already supported? Because when I use the Enocean room Control Panel thing there is no Channel for humidity. Also the Channel for teach in is missing. (The openhab needs to be learned into the futh to overwrite the setpoint temperature, or am I wrong?)
Will they work when I link the setpointTemperature and Temperature Channel to a number:Temperature item?
Hello fruggy83,
I need the following EEPâs to control my âPanasonic Etheraâ-air conditioner (control via an âIntesisBox PA-AC-ENO-1iâ interface box), âKieback&Peter RBW322-FTLâ room control panels and âKieback&Peter MD15-FTLâ heating valve: D2-10-01 (room control panel) 07-10-03 (air conditioner) 07-20-01 (heating valve) 07-20-10 (air conditioner) 07-20-11 (air conditioner)
In addition, there must be the possibility to teach the EnOcean controller into the IntesisBox PA-AC-ENO-1i" interface box (the complete teach-in process is described in chapter 4.2.2 and 4.3.2 in the manual).
I actually got it working, but to do so had to go into paper ui and link the listener to the husa device
Do you have a mixed setup (file based and directly through paperui) now? I would not recommend this kind of setup. Could you please post (or pm) your config? I would update it afterwards to include the listener.
It worked, but now I have two items in the control panel
That is a âproblemâ of PaperUI. PaperUI evaluates the channel links to create the control panel. As you have two links now, it display also two items. Because of this (and other reasons) I am using the BasicUI. BasicUI just displays the items.
And it seems that my ability to control or over Google Assistant is a bit laggy now. But that could be unrelated.
I am using Alexa, so I cannot really confirm this. However I would also think that this is unrelated.
nice to hear that this binding works for you Do have a wired (directly connected to your FAM14) or wireless setup?
The FUTH65D should be already supported as a sensor. So you should be able to receive the temperature and humidity values and the setpoint. I would also expect that it should be detected automatically when you send a teach in telegram from your FUTH65D. If you set it up manually, you should use the EEP A5_10_12. However according to the official specs, the setpoint channel is a simple number channel, it sends values between 0 and 255. You have to transform this value into a temperature value by yourself. 0 => 8°C, 255 => 40°C.
Also the Channel for teach in is missing
Currently this device is not supported as an actuator thing, so you cannot send messages to this device yet. I will add this to my todo list. How do you plan to determine the setpoint? Is the measured temperature of the FUTH not accurate enough?
You should be already able to control your Panasonic Ethera, at least On/Off, as it accepts simple rocker switch messages [05-02-01] (=> F6-02-01). EEP 07-10-03 (=> A5-10-03) is also supported by Room operating panel. I will put the other EEPs on my todo list.
@fruggy83
I use a wireless connection. Raspi + gpio Board.
I will try to discover the device, I only tried the manual way. Thank you for the hint
I am new to openhab and enocean, so maybe I donât understand this correct, but the setpoint is the âshould beâ temperature (Solltemperatur) right?
Example: The temperature reading shows 20°. I want the temperature to be 22°. So I will set the temp to 22°, this will be send to the Futh, the Futh will send it to the f4hk14 and this will adjust the temperature in my room. So the Futh in the room and the openhab readings are the same. Right or am I totally wrong?
I also try to get the values of my weatherstation, an Eltako multisensor. It is connected to a fwg14ms.
As enoceanID I used the Fam14+address from the fwg14ms. But I doesnât get any data shown.
The pct14 shows that the multisensor sends all data into the bus.
And my window contacts should be also supported. They are reed contacts, connected to Fts14em. At the end of the bus is a fts14FA so that the open/closed Status will be send wireless.
How can I get the enoceanID from the contact sensors? They are working, I see the fts blinking, but I doesnât get any telegrams in the pct14?
Sorry for all the newbe questions, but maybe you can help me there also?
I also try to get the values of my weatherstation, an Eltako multisensor
This multisensor in conjunction with fwg14ms should be already supported. At least somebody here in this forum has a working setup. This device should be automatically detected too. If you want to set it up manually you have to use the Environmental Sensor. Maybe you enable the debug logging of the binding and watch the incoming messages.
The pct14 shows that the multisensor sends all data into the bus.
Maybe your FAM does not send bus telegrams into the wireless bus Do you get responses from your FSR14?
And my window contacts should be also supported.
Your window contacts do not work wireless? You have a wired connection from your windows to a FTS14EM? Nice setup In this case your FTS14EM should send simple rocker switch messages into the bus which are send into the wireless bus by your FTS14FA. In this case auto detection should be also possible. Just open the discovery page and open/close a window. You will get a push button thing. Just ignore it and keep the EnOceanId. Afterwards you create a rocker switch thing with this EnOceanId.
Hi there,
I am trying to use my window and door contacts with the enocean binding. They get send via a fts14fa.
I find them in the discovery. But they doesnât work.
When I look into the log it says:
[INFO ] [ernal.transceiver.EnOceanTransceiver] - Discard message because this is a teach-in telegram from FFEF3D32!
What can I do that the telegrams from my contacts doesnât get discarded?
I am new to the whole topic. I have an eltako enocean setup in my house. In detail:
Light:
-Dimmer: TF61D-230V
-switch: TF61L-230V
roller shutter: TF61J-230V
Window contacts: TF-FKB
Adapter plug: TF100L-230V
Smoke detector: FRW-ws
Gateway: Eltako MiniSafe
What does the binding support? How do I find the EEPs from the actuators out? I have the EnoceanIDs visible via the minisafe gateway. Can I forward all functionalities from this binding to homekit via the homekit integration binding?
I plan to run openhab on a pi. Looking for a pi4 with 8gb, is a fan needed? Or would passive cooling be enough?
Hello everyone,
I hope someone can help me.
I have also bought the following setup. (All for testing purposes only):
eltako ft55
fud61npn
And naturally openhab on raspi 3b+ + EnoceanPi
The EnoceanBridge is on-line. The teach-in of âOpenhabâ in the FUD61NPN and the switch FT55 in the FUD61NPN has also worked and I can control the light via both ways.
I put on both for the light actuator (FUD61NPN), and for the switch FT55 in OH a âThingâ.
As I said, the TeachInCMD in the FUD61NPN also worked and the actuator was activated for confirmation telegrams.
But now, I have the big problem - like so many others - that I donât get any updates in the Openhab when the light changes.
According to the manual it says: "If you want to receive messages of your EnOcean devices you have to set the enoceanId to the EnOceanId of your device.
But which means exactly: "set the enoceanId to the EnOceanId of your device.
Could someone explain this to me in a little more detail?
Iâd be happy to give you some sample values, but Iâm afraid Iâm not quite sure.
Thank you very much for your effort.
Many greetings
Marcel
The EnOceanID (0590B02B) is the ID of the actor. Thank you for your help!
The Item i currently use is:
Dimmer C_Buero_Light âLichtâ (C_Buero, gLight) {channel=âenocean:centralCommand:ad68db90:dimmerâ, homekit=âLightingâ, ga=âLightâ}
Ok guys. I will try to install openhab on my pi and then try to add the binding. what else do I need? Goal is to control the stuff through homekit. Do I need soemthing else?
What exactly is your goal? You want to control your things with your apple devices through openhab?
therefore you need to install the homekit binding, pair your devices (openhab + homekit) and than declare all items you want to control with a special tag âhomekit=Lightingâ (for lamps) as you can see in my post above. Best wishes.
Marcel
my goal is to control my enocean eltako devices through openhab/homekit, yes.
I will set up this as soon as I find some time and I will come back to you with my questions .
Edit: I will use homebridge, can I install openhabian as well? I mean is openhabian including the whole rasperry pi ios? Or should I just install openhabian. I tested a bit on my mac and found out that homebridge is very easy to use.
Do have a wired (directly connected to your FAM14) or wireless setup?
Do you get responses from your FSR14?