I tested the new binding and discovery works very good but unfortunately not for my rocker ELTAKO FTKE.
The openocean-binding discovered it as a „F6-02 - Rocker Switch“ (as ist should be), so far so good. But when I toggle the switch there is a message in the log, but no action for the item.
14:22:27.531 [TRACE] [rnal.transceiver.OpenOceanTransceiver] - Received Sync Byte
14:22:27.631 [TRACE] [rnal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
14:22:27.933 [TRACE] [rnal.transceiver.OpenOceanTransceiver] - publish event for: fefa77a4
14:22:27.945 [TRACE] [rnal.transceiver.OpenOceanTransceiver] - f6f0fefa77a42001ffffffff4400
14:22:27.970 [DEBUG] [ean.handler.OpenOceanBaseThingHandler] - ESP Packet f6f0fefa77a420 for fefa77a4 received
14:22:27.982 [DEBUG] [ean.handler.OpenOceanBaseThingHandler] - ESP Packet f6f0fefa77a420 for fefa77a4 received
14:22:27.992 [DEBUG] [ean.handler.OpenOceanBaseThingHandler] - ESP Packet f6f0fefa77a420 for fefa77a4 received
btw:
I use the new jar file, definded the OpenOcean Bridge as discribed and discovered the new thing.
My Hardware is a USB300 running on a Raspberry Pi3 gateway and the obenhab-server is connected to this gateway over tcp (socat).
Any idea where the problem could be?
Thanks in advance.
the problem here is, that your FTKE and a rocker switch use the same EEP group F6. This EEP group does not know a teach in telegram like a 4BS message. So I have do guess which type of thing send such a F6 message. To make it easy for me, I create always a rocker switch thing when I receive a F6 message during discovery. However I already have an idea how I can differentiate between a rocker switch message and an FTKE message. Maybe I find some time to implement this idea tomorrow.
Meanwhile you can just create a F6-10 mechanicle handle manually (thing id: fefa77a4). This thing uses the same telegrams for Open and Close.
What worries me is, that I can only find F6F0 (closed) messages in your log and no F6E0 (open). Or do you find such messages later in your log?
thanks for your quick response.
Yes, there is a closed message later in the log.
I’m trying now to add it manually and waiting for your new implementation .
when you are back from vacation, i would appreciate if you could help me again.
I can´t teach-in this rollershutter-actuator: Opus 561.314.
I probably need to use the generic-thing, but i have no idea, what to put into the mapping-file.
// Alexa Voice-Control of Rollershutter "Rollo"
rule "Rollo Voice-Control"
when
Item Rollo_Alexa received command
then
if (receivedCommand == 0) {
sendCommand(Rollo, 100)
} else {
sendCommand(Rollo, 0)
}
end
With this rule you can use these alexa commands (i only tested the german ones), instead of 0% and 100%:
“Alexa, Rollo runter” (Alexa, Rollo down)
“Alexa, Rollo hoch” (Alexa, Rollo up)
To elaborate on that: If you tell Alexa “Rollo runter” it sends the command “0” to openhab. With “Rollo hoch” it is “25”.
I improved the discovery of F6 devices. I do not automatically create a rocker switch during discovery any longer, when I receive a F6 message. Instead I first analyse the payload and decide which thing type should be created. However as a FHF (classical window handle with tilted state) and a FTKE nearly send identical messages, I treat them as the same thing type.
So you should now be able to auto discover your FTKE device. Could you do me favor and send me a picture of your FTKE? I am interested in such a device too, but I cannot image how to integrate this sensor in a door or window Thanks a lot in advance.
Today i implemented an autonomous setup for my Rollershutters via the “Astro Binding”. This means the rollershutters automatically go up at sunrise (or later - you can change the time) and down on sunset.
Here is my setup-guide:
Install “Astro Binding”
Manually add the thing “Astro sun data” via PaperUI (it does not get discovered on its own)
Go to this website: mapcoordinates.net to get your exact geolocation (latitude, longitude and altitude)
Open the “Astro sun date” Thing configuration and put in your location-information.
Change the time-settings in the channels Sunrise-“Range event” and Sunset-“Range event” to your liking as discribed here: Openhab Guide
home.items (only needed if you want to see the sunrise / sunset time on your sitemap):
// Autonomous Rollershutters via Astro-Time
rule "Rollershutter_Sunrise"
when Channel 'astro:sun:XXXXXXXX:rise#event' triggered START
then
sendCommand(Rollershutter_1, 0)
sendCommand(Rollershutter_2, 0)
end
rule "Rollerhutter_Sunset"
when Channel 'astro:sun:XXXXXXXX:set#event' triggered START
then
sendCommand(Rollershutter_1, 100)
sendCommand(Rollershutter_2, 100)
end
thanks for your improvement. Now my FTKE works as aspected
Unfortunatly, I have not installed the switch itself yet. As soon as I have done this, I will gladly send you some photos.
EDIT:
Now I have a similar problem with the ELTAKO FTK-rw :
The contact is recognized by the binding (D5-00 - Single input contact) but again: no action for the item.
First of all: thanks a lot for this work. I really apprechiate it. I had FHEM running and was never satified with it. So I am going to move to Openhab. I started to define my eltako FSR12 actors using the generic thing which worked fine. However I wonder if I can use files to define the things and items because I have a lot of them. Is this possible or can I somehow copy things and items?
glad to hear that your FTKE and FTK work now. However it should not be necessary to restart openhab. Maybe there is still another bug. Can you describe which steps you made to setup your FTK? Do you have “simple item linking” activated?
glad to hear that you can control your FSR12 actors with this binding.
I could not find a lot of information about your FSR12 actor, but I think it should be nearly the same as my FSR14 (except for the bidirectional communication). So you should also be able to use a A5-38 central command thing for your actor (I know the wording of the thing types is not really clear). With this thing type you do not need a mapping file.
I also own a lot of eltako actors (light, dimmer and rollershutter, aprox 50 enocean things). It is definitely possible to define your things and items with files. I created an excel file for this. If you want I can share it with you.
No, “simple item linking” is not enabled.
I’ve created the Things manually (as D5-00 - Single input contact) and also added an Item manually to my first contact.
My second contact, was linked to a new created Item by using the “Create a new Item” function - it also worked
Now I’m perfectly happy - everything works as it should.
Another improvement I could imagine if there will be a transceiver bridge in future for using enocean devices over a TCP / IP connection (as the rfxtcom-binding has)
Really great work - thanks a lot. I have been waiting for such a solution for a long time!
thanks for the hint. I will try the A5-38 at the weekend. And you are right, according to the eltako documentation the FSR12 and the FSR14 are using the same codes. For me it worked with 4BS 0000000F:on,4BS FFFF000F:off,4BS 18080D87:teach. I can send you the documentation where the old components are listed if you are interested. In the current documentation they are removed.
I would really appreciate to get your Excel. What is the way to exchange files?
It would be nice, if you could upload the documentation (pdf should be allowed), as I only have a newer one, which only includes the 14 series.
I started to create a wiki for this binding to document the supported devices. There you can find the excel.
As I am using a FAM14 which generates the EnoceanIds of my actuators, I can easily calculate them. For sensors or if you do not use a FAM, you have to set the thing Ids manually. If I setup all the formulas correctly, it should be no problem to copy them and create new lines for more devices. However I “optimized” this sheet just for my devices.
If I find time, I try to add more devices to the wiki and sync the excel file with the table.
thanks for the link to the Excel. This definitely helps because I was not sure how the syntax looks like. Unfortunattely I cannot upload the old Eltako documentation here because I am a new member. I have done this as item under your github project.
actually I found my old mails from 2013 where I discussed the FSR12 behavior with somebody who owned and FSR14 like you. He also proposed to use the A5-38-08 which worked for him. But when I tried it, I was only able to switch the light on but not off. The same when I try it now using openhab. So A5-38 does not work for the FSR12 I think. On the other hand your codes 0100000F:on und FFFF000E:off does the job.
The reason why I send 0F instead of 0E for off is the following. I was using an TCM in repeater mode for sending the signals. However the TCM also repeats the signals it sends. This was not rejected in the fhem code and causes troubles for my rules because they are triggered twice. 0F I think indicates that the repeater should ignore the telegram.
Do you have any idea why A5-38 might not work otherwise I think I have to stick with the generic genric thing.
to be honest, I really do not have any idea why EEP A5-38 does not work with your FSR12. According to the docs the FSR12 and FSR14 use the exactly same messages/EEP.
Do you own the Eltako PCT14 software? You can read the config of your FAM12 and all your actuators and do the teach in/pairing with this tool. Maybe you should try this tool and look how your FSR12 is configured.
sorry this might be a dumb question, but why don´t you use the “F6-02 - Rocker Switch” ? I have a pretty simular actuator from Opus -> CLICK and the F6-02 works just fine. I just had to teach in ON and OFF.
I must apologize but I have forgotten some important details on my setup. After setting it up five year ago I was so happy that everything was running that I never touched the system afterwards. But now looking at my notes I remember why I had the problems with the FSR12. I think the main reason is that I own FSR12-12V modules with one exception and not FSR12-4x12V. The FSR12-12V is not documented in the Eltako telegram definition. I have tried a lot things for the FSR12-12V. The only way to run it with a A5-38 is teaching in with a central on/off but then both channels are switched simultaneously.
Because I need a well defined on/off (not a toggle) I mimiced a FAH light sensor which eventually worked for me. In addition using a raw 4BS signal allows me to define that the signal is ignored by my two repeaters (but this is just a side note).
To be honest I don’t want to change the settings, because everything is already teached in and running under FHEM. For OpenHab I bought a new Raspberry with an Enocean Pi where I set the base ID to the base ID of my running FHEM system. So for the migration from FHEM to OpenHab I don’t have to teach in anything. I just have to use the same telegrams which saves a lot of time for me.
In any case I am happy to try alternative setting. So I will try the rocket switch. On the other hand I spent a lot of time to get the FSR12-12V running and it works for me with the generic 4BS command. Apart from this, I also don’t like the idea to teach in all my components again. I hope you can understand this.
.
Thanks a lot in advance.
