Hello and thanks for the tradfri innovation.
I have a bunsh of lights active thru openhab on my qnap nas.
What I’am missing since the 0.9.0. snapshot is the avalability of the (0820) items(remote controls).
They looked like this:
Livingroom
Tradfri Group
tradfri:group:gwa0cc2bf85xxx:162430
I’am turning always back to the old build due to the fact that I can’t see my remotes anymore.
Can someone please let the (0820) items return into the actual snapshot.
Thanks!
Is anyone experiencing stability and delay issues after adding the binding?
I have latest stable openhab and android ikea app (i can check versions if that help), binding is installed via paperUI, and things added via paperUi. Items are added in the files.
I have 4 bulbs in two groups. I had gateway running for few days without the binding, and via the app all works instantaneous. When I install the binding, both the ikea app and commands from the openhab start to have 4-6 (sometimes up to 8) seconds delay. Sometimes would the Ikea app disconnect while trying, saying there is timeout or something.
I do not see anything suspicious in the openhab2/events.log except that the
2017-10-29 20:19:05.622 [ItemCommandEvent ] - Item ‘OfficeLight_Brightness’ received command 86
2017-10-29 20:19:05.623 [ItemStateChangedEvent ] - OfficeLight_Brightness changed from 54 to 86
2017-10-29 20:19:09.113 [ItemCommandEvent ] - Item ‘OfficeLight_Brightness’ received command 38
2017-10-29 20:19:09.115 [ItemStateChangedEvent ] - OfficeLight_Brightness changed from 86 to 38
Entries in the log are instantaneous, but then there is the delay before the lights react. Same goes for ikea app.
First I thought I made some stupid rule, so I removed the binding and reset both the openhab and gateway, and all started working fine via the ikea app. Then I added the binding, all worked fine for a day or two, but then the delay started to show again 
Any advice on where to start checking?
Thanks!
I got a bit more testing, and it is definitely something with a binding, as soon as I reboot openhab server, binding works fine again both from the openhab and from the ikea native app.
Looks like binding is bombarding the gateway with requests or something, since it also influences native app from working. I will try to determine what is exactly going on and try to get some info out of the logs.
Same Problem here … I run Openhab 2.2.0 Build 1069… The Tradfri Gateway stop working after few Minutes 
191 │ Active │ 80 │ 0.9.0.201710240931 │ TRÅDFRI Binding
After reboot the Tradfri Gateway … it works for few Minutes …
try restarting openhab and see if stability is longer, for me it is stable some time, but I guess after a bit fiddling with items or rules it just stops
Yes … and I think only the RGB Bulb is the Problem …
I found this information in a home automation group on Facebook. I am not sure where to post this information to make sure it is received by the right person but I hope someone here can help.
Fredrik
I now found the text just not a picture.
"Hi,
We at IKEA would like to inform you about a change to our TRÅDFRI Gateway. We are very happy to see your interest in our gateway and have seen that you are using the CoAP interface. We consider the CoAP interface as our internal interface not developed for third party usage and therefore we do not offer any technical support for this usage. However that does not mean that we want to hinder your work in any way.
There are some security improvements in a soon coming update that we would like to inform you about since it will break your implementation. Technically the improvement is that the TRÅDFRI Gateway will start using DTLS Identities which you will need to handle in your application.
Please use the Following string to connect to the TRÅDFRI Gateway and create a new DTLS Identity.
coap-client -m post -u “Client_identity” -k “SECURITY_CODE” -e ‘{“9090”:“IDENTITY”}’ “coaps://IP_ADDRESS:5684/15011/9063”
SECURITY_CODE is what is labelled on the Gateway label, IDENTITY is any string that is representing the connection.
You will then get back a PRE_SHARED_KEY that can be use in all traffic after that.
coap-client -m get -u “IDENTITY” -k “PRE_SHARED_KEY” “coaps://IP_ADDRESS:5684/15001”
We also would like to request that the SECURITY_CODE that is printed on the gateway is never stored permanently in your application.
Best regards
IKEA of Sweden Trådfri team"
The Gateway Update is now released …Firmware 1.2.42
Perhaps this Firmware solves the Problem … my Gateway is now 30 Minutes up without a Crash …
If the Gateway crashed I reply here 
EDIT: The Gateway crashed 
have you tried restarting openhab/binding?
For me the Ikea gateway works fine, but it is actually openhab that “brakes” it somehow.
Last time all froze, i just restarted openhab server and ikea android app and gateway started working fine (after few minutes of initialization). Then I tested sliders and switched from openhab and there has been no delays/crashes from yesterday. I am suspecting that some process in openhab is disturbing the connection and the gateway, either updating some items, or rules, or maybe network connections fails and when it recovers then the gateway gets bombed by openhab, not sure…
p.s. I do not have any (full) color lights.
I have created https://github.com/eclipse/smarthome/issues/4479 - please follow up on that issue, if you have any specific input on the topic. Thanks!
Haven’t read the whole thread, but are you aware of this?
If you haven’t changed the patch cable, give it a try. Worked for me.
I’m thinking about to integrate Tradfri into my home automation.
I’m especially interested in integration the motion detector, the remote control and the dimmer handle to control my existing infrastructure. I saw some hints how to integrate the motion detector.
Is an integration of the remote control and dimmer handle possible, too? Can you please share your experience?
You can not detect the remote or motion detection inside openhab but what I am doing is to monitor the lamp that the remote is controlling and in that way I can control other things outside the trådfri system.
Ah OK, I see. The controls signals are not received by the gateway, right?
Yes that is correct with the exception that in the latest version you should now be able to monitor the battery status of the remote but I have not tried that yet.
Just a heads up, Tradfri users… I had to re-scan the QR code on the back of my Tradfri hub this weekend, which seemed like bad news until I connected the dots - it appears Ikea has upgraded the iOS app to include intregration with Amazon Alexa and Apple HomeKit. Potentially helpful timing, since discounted Amazon Echo units tend to rain down like manna from heaven on Black Friday…
Hello,
I would only give a information that I can manage osram ligthify Plug with remote control of tradfri!!
With that connection the Plug it self is also seen in the Tradfri app as “Plug 01” but it is grayed out.
I can switch the plug on and off over the remote control and if I switch on or off a group in the openhab the plugs
do the same as the lamps do!!!
What I can’t do is to check the id out of the gateway for the device… maybe some one can investigate that…
Reg
Lars
You are lucky Lars,
my osram smart+ plugs can be paired with tradfri remotes and can be controlled. But as soon as I pair them to the tradfri gateway, they start to switch on/off for about ten times and then get greyed out in the app. They also appear as Plug 01.
Cheers, David
Did you try with a bulb controlled by the remote too? It could be that this is needed to get signals sent from the Trådfri Gateway to react.
