Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve support for Peha bi-directional actuators. #49

Open
unf opened this issue Jan 8, 2019 · 4 comments
Open

Improve support for Peha bi-directional actuators. #49

unf opened this issue Jan 8, 2019 · 4 comments

Comments

@unf
Copy link

unf commented Jan 8, 2019

Hi Daniel @fruggy83,

you may remember I have some issues with my Peha EBI actuators, "451 FU-EBI o.T." & "452 FU-EBI o.T.". They are discovered by openhab2 @ openocean, using EEP D2-01-08 afterwards, but don't do anything then. Means, I cannot switch my lights from OH2, but I get correct status of the switch channel.

I called Peha product support and got some helpful information:

  • The "Easyclick Gateway Application Note" is only applicable from Firmware Version 3.x and further. This will enable UTE using EEP A5-38-08 resp. -09 for these actuators. I guess two different EEP for 1- resp. 2-channel devices.
    => Here I'm now waiting for additional information, howto find out the FW version for the own actuators ...
  • If the actuator doesn't provide UTE, so, below FW 3.x, like mine, the teach in method is similar to the Eltako TF61L. Means, enable "normal" teach in mode and send a specific teach in telegram from gateway using EEP A5-39-08 and I also guess -09.
    => Here I'm now waiting for additional information, howto distinguish between 1- and 2-channel devices.
    => I got a screenshot showing these telegrams for A5-39-08:
Teach-In as a gateway controller (4BS): E0 40 00 83
Switch off (4BS): 01 00 00 08
Switch on (4BS): 01 00 00 09
Statusabfrage (4BS): 00 00 00 0A

Any chance to get my Peha actuators supported with openocean?

Cheers
Frank

@fruggy83
Copy link
Owner

fruggy83 commented Jan 8, 2019

Hi Frank @unf,

first sorry for my late answer in the community, you can ignore my last reply there 😉

  • One advantage of the UTE is, that the actuator tells us, which EEP should be used to control it. So when openhab detects it with UTE as a D2-01-08 device, the actuator gave us the information to use this EEP. Maybe you actuator sends two UTE messages, the first with D2-01 and a second with A5-38? Could you please look into the log and activate the teach in of your Peha. But do not start the discovery in openhab, otherwise the binding will directly answer to the D2 UTE.
  • In most cases such actuators do have two different EnOceanIds, one for each channel. For example my Eltako FSR14-4 have 4 channels with individual Ids. They are also controlled by EEP A5-38 with the exact same messages for Switch off/on. However the Statusabfrage message is not mentioned in the official EnOcean docs. So if you want you could try to use a Switching/Dimming Actuator and send a teach in message E0 40 00 83 like you did in Support for Eltako TippFunk EnOcean devices #17.

Best regards
Daniel

@unf
Copy link
Author

unf commented Jan 8, 2019

Hi Daniel @fruggy83,

will answer your question from the community thread quickly. OH2 @ openocean does discover the Peha actuators with D2-01-08 and the Nodon actuators with D2-01-[0F|12]_NODON. But D2-01-08 doesn't seem to be the best choice according to the information from Peha.

The Peha "451/452 FU-EBI o.T." do also offer 2 EnoceanIDs per switch channel, one for 4BS and one for VLD.

I thought about to try to teach in the 1-channel Peha, like I did with the Eltako TF61L actuator in #17, but I didn't found a hint that EEP A5-39-08 is supported. It may look like a typo, but isn't according to the email by Peha product support ... ?

Cheers
Frank

PS.: On the other side, A5-39-08 doesn't exist according to the Enocean Docs ... tststs

@unf
Copy link
Author

unf commented Jan 8, 2019

Hi Daniel @fruggy83,

so, followed the path used with the "Eltako TF61L" and my non-UTE 1-channel Peha "451 FU-EBI o.T." does work now.

I defined the Thing like this, using EnoceanID for "4BS" and sending the specific teach in telegram:

Thing centralCommand XXXXXX00 "Schlafzimmer OG Aktor (EEP A5_38_08_01)" @ "Schlafzimmer OG" [
   enoceanId="XXXXXX00",
   senderIdOffset=5,
   sendingEEPId="A5_38_08_01",
   broadcastMessages=true,
   receivingEEPId="A5_11_04",
   suppressRepeating=false,
   pollingInterval=300 ]

I set the receiving EEP according to the information in devices manual.

So, for a 2-channel actuator I need to define 2 Things that way, is that right?

Thanks for your great work.

Cheers
Frank

@unf
Copy link
Author

unf commented Jan 9, 2019

Ok, so got the feedback of Peha product support. Dual channel actuators are not distinguished with different profiles like Nodon. Dual channel actuators need to be defined as 2x 1-channel actuators in the gateway, old or new firmware.

They also certified that the classic teach in with teach in telegram are using the 4BS EnoIDs, like I have done. For UTE with newer actuator firmware the VLD EnoIDs are used.

Firmware version is mentioned on a sticker on the device, according to Peha product support, need to verify that the next days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants