Tradfri Binding

Hello, I’ve used the instructions in the Tradfri Binding documentation to set up my Tradfri gateway as follows:

Things
Bridge tradfri:gateway:myTradfri [ host=“192.168.1.249”, code=“XXXXXXX” ] {
0220 ceilingLight [ id=65538 ]
}

Items
Dimmer Light_Bedroom_Ceiling “Ceiling Light [%.1f %%]” (Bedroom, Lights) { channel=“tradfri:0220:myTradfri:ceilingLight:brightness” }

The problem is that if I turn the light on in OpenHAB I get a load of endless errors which cause the gateway to crash and go offline:

2017-07-08 15:03:28.435 [WARN ] [pse.californium.core.network.Matcher] - Possible MID reuse before lifetime end: 11 expected MID 36061 but received 12682
2017-07-08 15:03:28.439 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.440 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.442 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.443 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.444 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.445 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.445 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.446 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.447 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.448 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.451 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.453 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.454 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.458 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.459 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.463 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.464 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.466 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.467 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.469 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.470 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.471 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.472 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.473 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.474 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.480 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.481 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.483 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]
2017-07-08 15:03:28.484 [WARN ] [e.californium.scandium.DTLSConnector] - Outbound message queue is full! Dropping outbound message to peer [/192.168.1.249:5684]

What am I doing wrong?

just a check: are you sure that the instance id (65538) is correct?

http://docs.openhab.org/addons/bindings/tradfri/readme.html#thing-configuration

@Dim Thank you so much. It turns out its instance ID is 65537. That seems to have fixed the issue.

1 Like

I just tried to get my tradfri gateway to work with OH2.
It’s found in the inbox.
Then I enter the securitycode in the Thing.
But then it’s always displayed as Status: OFFLINE - COMMUNICATION ERROR

Do I have to press a pairing button?
Or can I find further debugging-infos?

Thank you

Michael

Not to my knowledge. I actually entered the details in the demo.things file

Bridge tradfri:gateway:myTradfri [ host=“192.168.x.x”, code=“XXXXXXX” ]
{
0220 ceilingLight [ id=65537 ]
}

*note that the id of the light bulb depends on the one assigned to it by the gateway so check the ID in the “Inbox”

also try to restart the gateway (disconnect and reconnect the USB cable)

Thank you - it was a spelling in the code - 0 instead of O

Michael