-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fully support for Eltako FMS55ESB / STM 550 S6201-K516 Enocean Multisensor - EEP D2-14-41 #112
Comments
Hi Stefan, should not be a big problem. Could you just do me a favor and post a message of this device here. It is just for testing purposes. Regards |
|
Hi @tokest, I just finished implementation. I just need a message for verification. Regards |
Hi Daniel 2021-11-18 18:54:32.419 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte ==> /var/log/openhab/events.log <== Regards |
Hi Stefan, thanks a lot for this log entry. This is what I need. However it seems that you setup your sensor to use 4BS messages instead of VLD. As the D2-14 EEP does provide all sensor values in a single message, it would be nice to setup your sensor to use this profile. Regards |
Hi Daniel
It looks like there are some issues on github… Anyway, I got the messages with the new EEP D2-14-41:
2021-11-19 18:54:16.824 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-11-19 18:54:16.828 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 15 optional length 7 packet type 1
2021-11-19 18:54:16.834 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG VLD for 0413D1E2 payload D2A019000003D4F7D8A00413D1E28000FFFFFFFF5200 received
Beste regards,
Stefan
Von: Daniel Weber ***@***.***>
Gesendet: Freitag, 19. November 2021 07:17
An: fruggy83/openocean ***@***.***>
Cc: tokest ***@***.***>; Mention ***@***.***>
Betreff: Re: [fruggy83/openocean] Fully support for Eltako FMS55ESB / STM 550 S6201-K516 Enocean Multisensor - EEP D2-14-41 (Issue #112)
Hi Stefan,
thanks a lot for this log entry. This is what I need. However it seems that you setup your sensor to use 4BS messages instead of VLD. As the D2-14 EEP does provide all sensor values in a single message, it would be nice to setup your sensor to use this profile.
Regards
Daniel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#112 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQBRCMQDYNTYKDE3LWNWEOLUMXTVPANCNFSM5HJSSUJQ> . <https://github.com/notifications/beacon/AQBRCMXSAQ62FACYTCOBL6LUMXTVPA5CNFSM5HJSSUJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHIFMRWA.gif>
|
Hi Daniel |
Hi Daniel
I did some tests with the Eltako Enocean Multisensor FMS55ESB with the OH3 enocean-binding. I realized that only the EEP A5-04-03 (temperature/humidity) and A5-06-01 ELTAKO (lux) are working. But only one EEP can be configured on a thing. Also configuring 2 things with different EEPs are not supporting all sensor data (configuration is possible, but wrong data are received).
With the EEP D2-14-41 all sensors of the FMS55ESB data would be supported, but it is not supported from enocean-binding. Because I think this is a very interesting sensor for a lot of applications with a wide range of people, I would ask you if you could develope an additional function which is supporting this EEP.
Regards,
Stefan
The text was updated successfully, but these errors were encountered: