The Teach-in was recogniced, but i couldn´t do anything with it.
BUT, i did not give up and tried the âA5-38 - Central commandâ and it now works flawlessly with my dimmers . Of course i can´t retrieve the actual state (actor â unidirectional), but that is ok for me.
I also tested using the âEltako rollershutterâ-Thing and they are are working aswell. The only problem i have, only âupâ, âdownâ and âstopâ are working. When i try to set a value (e.g.: 50%), it does not work. No enocean-command gets send by the binding:
17:28:44.275 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Rollo_Schlafzimmer' received command 50
17:28:44.285 [INFO ] [smarthome.event.ItemStateChangedEvent] - Rollo_Schlafzimmer changed from 0 to 50
17:28:44.285 [DEBUG] [rnal.transceiver.OpenOceanTransceiver] - new request arrived
Best regards,
Alex
EDIT:
Oh my enocean-controlls are not working at all at the moment. I think setting the shutter to 50 killed it somehow. But there are no error-messages - nothing. Only with each command â â[DEBUG] [rnal.transceiver.OpenOceanTransceiver] - new request arrivedâ. Time to restart openhabian.
I implemented the EEP class A5-04, which is used by your temperature and humidity sensor. You just have to search for new things and push the teach in button of your sensor.
It would be nice if you could give me a feedback about your tests. I am thinking about a wikipage where I collect all supported and tested EEPs/devices including their teach in method.
maybe I should revise the documentation about the generic things and give more explanations and further examples. There is far too many information missing.
However the most important test for me went well =>
the teach in was recogniced
Good to know that the A5-38 EEP works with your dimmers. So I can add your dimmer actuator to the supported device list (see my last post).
I also tested using the âEltako rollershutterâ-Thing
Rollershutters are poorly implemented by Eltako (and therefore Opus as well). It is not possible to directly set your rollershutter to a certain percentage value, instead you have to tell it how long it has to drive in which direction To be able to set a percentage value I remember the last driving time (which is send by the actuator) and calculate how long and in which direction it has to drive to reach the percentage value. To do this calculation I need the driving time from up to completely down. This information can be set on channel level.
However as I cannot retrieve the current position of your rollershutter, I first have to move completely up and afterwards down to the percentage value. But let me think about it, maybe I find another solution for your unidirectional actuators. Did this work in fhem?
I think setting the shutter to 50 killed it somehow
You are absolutely right. As the binding could not retrieve a message with the current position or driving time, it was not able to do the driving calculation, so it tried to send a NULL message => fail. I fixed this, so it is no longer a problem if you set a percentage value.
Not really. It was also time-based. So i made it easy for me and just had these buttons: UP, DOWN, 50%, STOP. This should also be working now via rules. So i personaly can live with that.
sorry my fault, the calculation of the temperatur was wrong (division by zero). In all other temperature telegrams (A5-02, A5-10, âŚ) the min temperature is represented by 0xff and max temp by 0x0. However in this EEP it is the other way around
I have to test the temperature in the eveneing sensor
Could you test your temperature sensor? Does the binding show the correct values? Could you please tell me which sensor you use? I am working on a compat list. Thanks a lot in advance.
I am switching from PaperUI-Items to the .items-config, because i need to use tags.
Could you tell me, how i can link 2 items in config-form as i do i do it via paper-ui (item âRockerswitch channel B (Sensor)â to âSwitch channel B (Actuator)â of another item -> Wallrocker <-> Virtual-Rocker) ?
It is probably very easy, but i don´t get it at the moment.
sorry for my late answer, but fortunately you found the solution by yourself. Could you do me a favor and tell me which openhab version you are using. Furthermore it would be interessting what happens when you hit the wall rocker. I would suggest that your openhab rocker switch send a message, too. That should not be problem in this case. I would do it by myself, but I am currently on vacation. Many thanks in advance.
i am using openhabian with âopenHAB 2.2.0-1â. I installed everything 13 days ago and never did an update since (do not know if there is one). That is one aspect, i have not read about enough. I want to be sure und informed before i do my first update. Especially the backup-situation.
Exactly what happens. I tried using the fact and cleared my wallrocker from my actuator - so when i press the wallrocker, it sends a message to openhab and openhab to my actuator. But this was not really reliable. Only every second / third click worked.
After teaching in my wallrocker (to the actuator) again, everything works like a charme. Now the actuator does get send 2 signals, but as you said, this is not a problem. The fact that i can use my old unidirectional actuators in a semi-bidirectional way is good enough for me.
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
. Of course i can´t retrieve the actual state (actor â unidirectional), but that is ok for me.
To be able to set a percentage value I remember the last driving time (which is send by the actuator) and calculate how long and in which direction it has to drive to reach the percentage value. To do this calculation I need the driving time from up to completely down. This information can be set on channel level.
.
Thanks a lot in advance.