EnOcaen and generic thing, how to use?

Add-ons Bindings
,
1

Hi there,

I’m using openhab3 and the EnOcean binding. My goal is to control the ventilation system in my house. The EEP D2-50-00,01 is currently not supported by the binding, therefore the fallback “genericThing” is used but I cannot get it to show any data whatsoever.

This is the thing configuration, all devices are listed as online.

Bridge enocean:bridge:gtwy "EnOcean Gateway" [ path="/dev/ttyUSB0" ] {
        Thing genericThing air_bad_og "Lüftung Bad OG" @ "Bad OG" [enoceanId="050ADC06", senderIdOffset=1, sendingEEPId="D2_FF_FF", receivingEEPId="D2_FF_FF", broadcastMessages=false, suppressRepeating=false]
        Thing genericThing air_hwr "Lüftung HWR" @ "HWR" [enoceanId="050CD588", senderIdOffset=2, sendingEEPId="D2_FF_FF", receivingEEPId="D2_FF_FF", broadcastMessages=false, suppressRepeating=false]
        Thing genericThing air_wohn "Lüftung Wohnen" @ "Wohnzimmer" [enoceanId="050ADD71", senderIdOffset=3, sendingEEPId="D2_FF_FF", receivingEEPId="D2_FF_FF", broadcastMessages=false, suppressRepeating=false]
        Thing genericThing air_schlaf "Lüftung Schlafzimmer" @ "Schlafzimmer" [enoceanId="050CC375", senderIdOffset=4, sendingEEPId="D2_FF_FF", receivingEEPId="D2_FF_FF", broadcastMessages=false, suppressRepeating=false]
}

In the debug log I can see data being received:

2021-04-20 12:29:08.807 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 20 optional length 7 packet type 1
2021-04-20 12:29:08.808 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG VLD for 050CC375 payload D24103000F00AD5000003C0F2281E6050CC3750000FFFFFFFF4D00 received
2021-04-20 12:29:09.301 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-04-20 12:29:09.302 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 20 optional length 7 packet type 1
2021-04-20 12:29:09.318 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG VLD for 050CC375 payload D260D8124A00000000000000000000050CC3750000FFFFFFFF4D00 received
2021-04-20 12:29:36.032 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-04-20 12:29:36.033 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 20 optional length 7 packet type 1
2021-04-20 12:29:36.033 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG VLD for 050ADC06 payload D24103000F009D4800003C0F21620A050ADC060000FFFFFFFF4A00 received
2021-04-20 12:29:36.528 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-04-20 12:29:36.529 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 20 optional length 7 packet type 1
2021-04-20 12:29:36.545 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG VLD for 050ADC06 payload D260D8124A00000000000000000000050ADC060000FFFFFFFF4A00 received

I tried adding an item to the genericString channel but the value is always NULL. I also tried adding a JS mapping with some dummy function which just returns the data as string but I still only see NULL.
Am I missing something here? My assumption was I can receive the raw data in the JS map and transform it into something usable but to my it looks like the map is not even called.

2

According to the binding-docs D2-50-00 as well as D2-50-01 (and others) are supported as a “heatRecoveryVentilation” thingtype.
Not sure when it was introduced, you might need to test with M 3 (latest milestone) release

3

Thanks, it’s indeed working in M3

4

Glad it solved your original problem.

Only thing left open: why did the genericThing not work ? I did not see errors on what you did compared to the documentation.
Perhaps the new D2-50-xx implementation broke the D2-FF-FF genericThing stuff. I did not use it personally so I think only Daniel @fruggy83 as the binding developer could check.

Perhaps you can open an issue on Github so that he can have a look at the genericThing.

5

Not sure, but I found a bug in the M3 release with the discovery of the devices.

Would be great if this could be fixed before the release as otherwise it’s not possible to add any new devices @fruggy83