New openHab2 EnOcean binding

dirkdirk · November 25, 2021, 6:31pm

I tried different gateways for enocean. The easiest to setup is an USB 300 stick. It is plug and play (auto detected by binding) and you can buy it from time to time for about 20€ when buying it second hand.

Your needed EEP is supported as a smoke detector… so there should be no problem using it with your device.

DrRSatzteil · November 25, 2021, 6:40pm

Yes that’s of course even better if your OH machine is close to your sensor. Unfortunately my server is in the basement so I had to come up with something else.

dav · November 26, 2021, 8:13am

Thanks a lot Dirk, I saw the smoke detector EEP at enOceans list but wasn’t quite sure if the openHab binding would support it since the manuel didn’s mention this EEP family.
Thanks for clarifying!
Price of the enOcean gateway stick wasn’t my concern. But if I had to use the wibuttler gateway eg. this would exceed my budget.
@DrRSatzteil
Yes the Hab is close so no Problem there. Even it’s just one sensore there will be much of a benefit cause it’s detecting leakage an malfunction of a pump in the basement which would be quite a desaster if it’s not working properly
Thanks for your advice.
Since I have no experience in coding an openHab binding this could be a challenge, but coding in general should be no problem.

DrRSatzteil · November 26, 2021, 8:41am

Well as Dirk pointed out your device should be supported so apparently I was wrong and no coding should be necessary. I just did not find this information in the documentation.

dav · November 26, 2021, 9:25am

It’s definitely not in documentation but I was curious, so went looking for a point to start implementing missing parts in fruggy83s openocean (this is the source for the openHab enocean binding right?) and was very happy to find a “MultiChannelSmokeDetector” definition and the EEP A5_30_03 class right next to it.
So @dirkdirk was totally right in the first place. Thanks very much u2!

DrRSatzteil · November 26, 2021, 11:07am

Yes that’s fruggy‘s repository for the binding. However if it is not on the official documentation then this feature was probably not merged to the official OH repo. You should be aware that eventually you need to download and install the addon from this repository and cannot use the official one that is provided through the OH GUI.

Ratiomatic · December 2, 2021, 1:35pm

Hi,
I am having troubles with the Trigger channel B of rocker switches right now. They worked fine using the official binding.
thingTypeUID: enocean:rockerSwitch
receivingEEPId: F6_02_01

When Channel A Up is pressed:

14:34:39.038 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchA triggered DIR1_PRESSED
14:34:39.263 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchA triggered DIR1_RELEASED

When Channel A Down is pressed:

14:34:53.134 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchA triggered DIR2_PRESSED
14:34:53.309 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchA triggered DIR2_RELEASED

When Channel B Up is pressed:

14:35:07.404 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchA triggered DIR2_RELEASED
14:35:07.405 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchB triggered DIR1_PRESSED
14:35:07.612 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchB triggered DIR1_RELEASED

When Channel B Down is pressed:

14:35:10.396 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchA triggered DIR2_RELEASED
14:35:10.398 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchB triggered DIR2_PRESSED
14:35:10.604 [INFO ] [openhab.event.ChannelTriggeredEvent  ] - enocean:rockerSwitch:[GATEWAYID]:[ENOCEANID]:rockerswitchB triggered DIR2_RELEASED

Why would the “rockerswitchA triggered DIR2_RELEASED” get triggered when channel B is pressed? This makes no sense.

fruggy83 · December 2, 2021, 3:33pm

Hi Tanel,
I added a new channel to handle a second pressed action (CHANNEL RockerSwitchAction). So you can toggle up to 8 switch items with a single rocker switch. However current openocean release is a WIP release. This error is fixed in the oficial binding. I will try to release a new openocean version tonight.

Best regards
Daniel

fruggy83 · December 2, 2021, 4:12pm

Hi Silas,

EEP A5_30_03 is not documented yet, as it is not fully implemented. Currently it just handles the temperature part of the EEP but not the 4 contacts and the wake up part. It is just used as a base class for an Eltako smoke detector which uses a slightly different implementation of this EEP.

Best regards
Daniel

fruggy83 · December 2, 2021, 10:46pm

HI Tanel,

I have uploaded a new openocean release, which fixes your rockerswitch problems.

Best regards
Daniel

dav · December 3, 2021, 8:24am

Hi Daniel,
thanks for the clarification. The sensor has arrived by now and the basic feature “Smoke detection” and temperature worked like a charm. This special device has also implemented the wake state and i think one of the contacts serve as a battery state signal but I’m not quite shure about that, cause documentation on the manufacturers side lacks this information. Since they recommend using it with a list of approved gateways this might not be a problem for them.
Thanks for your work on the enocean binding!

Ratiomatic · December 8, 2021, 5:37pm

Hi Daniel,

Thanks, the pushbutton triggers work fine now!

Is there any chance to get the D2-11-02 (Thermokon SR06 thermostat with humidity) fully implemented? Right now it gets recognized and taught in, thing updates these channels:

There are some problems that need resolving:

Humidity not getting any values- always NULL
Occupancy has value OFF, should be ON
Setpoint can not be set from OpenHab to display corrrectly on the thermostat (It should be bidirectional)

Have you gotten any of the D2-11 profiles to actually give feedback to thermostat ie updating setpoint?

flysl88 · December 12, 2021, 7:37am

Hi everybody,

I have a question regarding an issue I discovered during a long term test period with an eltako/openhab 3 testbench setting. I have several Eltako devices installed (FAM14, FGW14-USB, FUD14, FSB14, FSR14-4x, FTS14EM) and those are connected to OH3 via the FGW14-USB Gateway. With one rocker switch connected to the FTS14EM I created a scene switch to count through different light scenes (managed by rules, in principle like here). So far this setting works very good without any problems.

Anyway, sometimes when i press the rocker switch to change the scene, or another switch (controls also a rule) which is connected to the FTS14EM nothing happens. When I look to the log there is really “nothing”. I get no “PRESSED” or “RELEASED” state in the log. The small status LEDs on the Eltako devices show me, that the button press is recognized by the FTS14EM and send via the RS485 bus to the FGW14-USB.

As mentioned above, another switch (no scene button) does also not response. I can’t detect no pattern behind the behaviour.

I changed the log already to DEBUG but there are also no entries.

More curious, changing the scene states from within OH3 Main UI is further possible.

Rebooting the Raspberry or restarting openhab service solve the issue, but this can’t be the final solution.

I don’t know if this is important, but yesterday before this happend i got an Log entry from the HP Printer Binding as follows:

2021-12-11 18:33:40.913 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR): Total timeout 10000 ms elapsed

2021-12-11 18:33:40.983 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from OFFLINE (COMMUNICATION_ERROR): Total timeout 10000 ms elapsed to ONLINE

2021-12-11 18:33:45.156 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from ONLINE to OFFLINE

2021-12-11 18:33:45.161 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from OFFLINE to OFFLINE

2021-12-11 18:33:45.210 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from OFFLINE to ONLINE

2021-12-11 18:33:55.210 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from ONLINE to OFFLINE

2021-12-11 18:33:55.213 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from OFFLINE to OFFLINE

2021-12-11 18:33:55.291 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from OFFLINE to UNINITIALIZED

2021-12-11 18:33:55.308 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hpprinter:printer:77c1526f6b' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)

Does anyone observed a same behaviour or has anyone an idea whats might the problem?

Hardware/Software information:
Raspberry Pi 4 Model B Rev 1.1
Eltako (see above)
Openhab 3.1.0 stable release
Enocean Binding 3.1.0 (official from OH3)

Best regards and many thanks in advance
Stefan

execcr · December 12, 2021, 9:07pm

Hi, someone have the NodeOn MSP-2-1-x1 Micro Plug (EEP; D2-01-0E)?
I have trouble to get it working with my OH3 setup.
I find the Device in discovery mode and add it as a thing on OH.

OH receives status changes when i manual press the switch button on the micro plug, but i cannot control the plug from openhab. During the pairing procedure, i flip the switch ON and OFF on webgui but the pairing light stay red and does not pair.

The pairing is working if i use a physical rocker switch (ie the Nodon SIN-2-2-01 Acutator)

Any help is very appreciated

dirkdirk · December 12, 2021, 9:15pm

Is there a teachin channel for you thing in openhab within channels (need to click show all)?
If yes you need to use this channel for learning.

execcr · December 12, 2021, 9:17pm

No, there isn’t:

execcr · December 12, 2021, 9:54pm

Ok just found that maybe is not supported …

github.com/fruggy83/openocean

NodOn MSP-2-1-11 MicroSmartPlug

opened 01:39PM - 03 Apr 20 UTC

HarterHorst

Hi, I try to teach-in the NodOn MicroSmartPlug without any success for hours …now. I hope you can help. openHAB: 2.5.3 212 │ Active │ 80 │ 2.5.3 │ org.openhab.binding.enocean The EEP is D2_01_0E and from the first impression the teach-in process works fine via paperUI. I have factory reset the plug prior to the teach-in so all learned ID should be gone. Here is the log:tail. ```` 15:23:20.879 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Stopping EnOcean discovery scan 15:23:20.887 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Starting EnOcean discovery and accepting teach in requests 15:23:24.364 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:24.371 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5600 15:23:24.378 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:24.402 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:24.412 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'enocean:measurementSwitch:9d601285:0582F709' to inbox. 15:23:24.414 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID 'enocean:measurementSwitch:9d601285:0582F709' has been added. 15:23:27.338 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:27.342 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:27.347 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:27.374 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:30.347 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:30.353 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:30.359 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:30.383 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:33.322 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:33.327 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:33.334 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:33.363 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:36.328 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:36.333 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:36.339 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:36.363 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:39.305 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:39.310 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:39.317 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:39.342 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:42.310 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:42.315 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:42.321 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:42.342 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:45.304 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:45.309 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:45.317 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:45.343 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:48.292 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:48.298 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5600 15:23:48.305 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:48.333 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:23:51.285 [INFO ] [ternal.transceiver.EnOceanTransceiver] - Received teach in message from 0582F709 15:23:51.290 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - EnOcean Package discovered, RORG UTE, payload D4A00146000E01D20582F70900, additional 00FFFFFFFF5500 15:23:51.297 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Sending UTE response to 0582F709 15:23:51.323 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Teach in response for 0582F709 with new senderId FFDEC801 (= offset 1) sent 15:24:20.886 [INFO ] [scovery.EnOceanDeviceDiscoveryService] - Stopping EnOcean discovery scan ```` I would expect the Plug to stop sending EEP teach-in queries after receiving a EEP Teach-in Response. That how the plug behaves when I teach-in a rocker directly. But the plug continues to send out queries. Hmm? When I continue with the OH configuration (links, items, etc.) all is good to the point where I use the switch on the control panel. Nothing happens. So I setup a second raspi to actually see the telegrams flying through the air with node-enocean-utils. Here's one teach-in Query and Teach-in Response dialogue. ```` ================================================================================================================================================= [Summary] - HEX |55 00 0D 07 01 FD D4 A0 01 46 00 0E 01 D2 05 82 F7 09 00 03 FF FF FF FF 30 00 13 - Packet Type |RADIO_ERP1 (Radio telegram) - Device Name |Unknown - Device ID |00000582F709 - Manufacturer |ID_RF - EEP |D2-01-0E - RORG |VLD Telegram - FUNC |Electronic switches and dimmers with Energy Measurement and Local Control - TYPE |Type 0x0E - Data |Unknown - Learn |true - Known |false - RSSI |-48 dBm - CRC |invalid ------------------------------------------------------------------------------------------------------------------------------------------------- [Telegram] - Sync. Byte |55 |55 - Header |00 0D 07 01| - Data Length |00 0D |13 byte - Optional Length |07 |7 byte - Packet Type |01 |RADIO_ERP1 (Radio telegram) - CRC8H |FD |valid - Data |D4 A0 01 ..| - R-ORG |D4 |Universal Teach-In EEP based (0xD4) - Data_DL |A0 01 46 ..| - Uni-bi-directional comm..|01 |Bidirectional communication (EEP opeartion) - EEP Teach-In-Response m..|00 |EEP Teach-In Response message expected - Request accepted |02 |Request accepted, deletion of teach-in successful - Command identifier |00 |EEP Teach-In Query - No. of individual chann..|01 |1 - Manufacturer ID |0046 |ID_RF - TYPE |0E |0E - FUNC |01 |01 - RORG |D2 |D2 - Originator-ID |05 82 F7 09|05 82 F7 09 - Status |00 |Original sender, 0 - Optional Data |03 FF FF ..| - SubTelNum |03 |3 - Destination ID |FF FF FF FF|FF FF FF FF - dBm |30 |-48 dBm - SecurityLevel |00 |0 - CRC8D |13 |valid ================================================================================================================================================= [Summary] - HEX |55 00 0D 07 01 FD D4 91 01 46 00 0E 01 D2 FF DE C8 01 8F 01 05 82 F7 09 56 00 6C - Packet Type |RADIO_ERP1 (Radio telegram) - Device Name |Unknown - Device ID |0000FFDEC801 - Manufacturer |ID_RF - EEP |D2-01-0E - RORG |VLD Telegram - FUNC |Electronic switches and dimmers with Energy Measurement and Local Control - TYPE |Type 0x0E - Data |Unknown - Learn |true - Known |false - RSSI |-86 dBm - CRC |invalid ------------------------------------------------------------------------------------------------------------------------------------------------- [Telegram] - Sync. Byte |55 |55 - Header |00 0D 07 01| - Data Length |00 0D |13 byte - Optional Length |07 |7 byte - Packet Type |01 |RADIO_ERP1 (Radio telegram) - CRC8H |FD |valid - Data |D4 91 01 ..| - R-ORG |D4 |Universal Teach-In EEP based (0xD4) - Data_DL |91 01 46 ..| - Uni-bi-directional comm..|01 |Bidirectional communication (EEP opeartion) - EEP Teach-In-Response m..|00 |EEP Teach-In Response message expected - Request accepted |01 |Request accepted, teach-in successful - Command identifier |01 |EEP Teach-In Response - No. of individual chann..|01 |1 - Manufacturer ID |0046 |ID_RF - TYPE |0E |0E - FUNC |01 |01 - RORG |D2 |D2 - Originator-ID |FF DE C8 01|FF DE C8 01 - Status |8F |Telegram shall not be repeated, 15 - Optional Data |01 05 82 ..| - SubTelNum |01 |1 - Destination ID |05 82 F7 09|05 82 F7 09 - dBm |56 |-86 dBm - SecurityLevel |00 |0 - CRC8D |6C |valid ================================================================================================================================================= ```` And here is the switch on/off dialogue that happens when i press the button on the control panel. ```` ================================================================================================================================================= [Summary] - HEX |55 00 09 07 01 56 D2 01 1E 01 FF DE C8 01 80 01 05 82 F7 09 56 00 8A - Packet Type |RADIO_ERP1 (Radio telegram) - Device Name |Unknown - Device ID |0000FFDEC801 - Manufacturer |Unknown - EEP |Unknown - RORG |Unknown - FUNC |Unknown - TYPE |Unknown - Data |Unknown - Learn |Unknown - Known |false - RSSI |-86 dBm - CRC |invalid ------------------------------------------------------------------------------------------------------------------------------------------------- [Telegram] - Sync. Byte |55 |55 - Header |00 09 07 01| - Data Length |00 09 |9 byte - Optional Length |07 |7 byte - Packet Type |01 |RADIO_ERP1 (Radio telegram) - CRC8H |56 |valid - Data |D2 01 1E ..| - R-ORG |D2 |Variable length data telegram (0xD2) - Data_DL |01 1E 01 | - Originator-ID |FF DE C8 01|FF DE C8 01 - Status |80 |Original sender, 0 - Optional Data |01 05 82 ..| - SubTelNum |01 |1 - Destination ID |05 82 F7 09|05 82 F7 09 - dBm |56 |-86 dBm - SecurityLevel |00 |0 - CRC8D |8A |valid ================================================================================================================================================= [Summary] - HEX |55 00 09 07 01 56 D2 01 1E 00 FF DE C8 01 80 01 05 82 F7 09 56 00 1E - Packet Type |RADIO_ERP1 (Radio telegram) - Device Name |Unknown - Device ID |0000FFDEC801 - Manufacturer |Unknown - EEP |Unknown - RORG |Unknown - FUNC |Unknown - TYPE |Unknown - Data |Unknown - Learn |Unknown - Known |false - RSSI |-86 dBm - CRC |invalid ------------------------------------------------------------------------------------------------------------------------------------------------- [Telegram] - Sync. Byte |55 |55 - Header |00 09 07 01| - Data Length |00 09 |9 byte - Optional Length |07 |7 byte - Packet Type |01 |RADIO_ERP1 (Radio telegram) - CRC8H |56 |valid - Data |D2 01 1E ..| - R-ORG |D2 |Variable length data telegram (0xD2) - Data_DL |01 1E 00 | - Originator-ID |FF DE C8 01|FF DE C8 01 - Status |80 |Original sender, 0 - Optional Data |01 05 82 ..| - SubTelNum |01 |1 - Destination ID |05 82 F7 09|05 82 F7 09 - dBm |56 |-86 dBm - SecurityLevel |00 |0 - CRC8D |1E |valid ```` I assume that the teach-in process is not complete. I compared the communication with an old trace from a FHEM - Switch learn-in process and discovered the following differences in the teach-in response telegram. Status: FHEM sends 80. OH sends 8F. SubTelNum: FHEM sends 00. OH sends 01. I you want i can send the FHEM trace as well. thanks Horst

fruggy83 · December 13, 2021, 9:47pm

HI Tanel,

humidity channel should get values now. Occupancy status should be fixed too. The bidir part is still in WIP. The device does not react as it should according to the docs. I suspect a timing issue. Maybe I find some time during holiday to finish this.

Best regards

fruggy83 · December 13, 2021, 10:13pm

Hi Frederico,

as I mentioned in the issue, I will change the UTE teach in respone and test it with my UTE devices. However until now all my UTE devices could be teached in. Even NodOn devices like SIN-2-1-01.

Best regards

fruggy83 · December 13, 2021, 10:25pm

HI Stefan,

I do not own a FGW14-USB nor FTS14EM, I could just test the RS485 implementation with my FAM. So there could still exist some bugs in the implementation
Do you still receive message from your other devices like your FUD when this problem occurs? Maybe the receive threads gets an unexpected message and breaks Do you find error message in your logs before this happens?

Best regards
Daniel