The Log-Function is used in the code, though it is recommended to use the newer Log3-function.
Migrate it

Valid for v1

See:
https://forum.fhem.de/index.php/topic,70653.msg676392.html#msg676392

Valid for dev-cf

User reported, that FHEM shows messages like this:

TradfriGW: Unknown code subscribedDeviceUpdate::65555::{"lastSeenAt":1502202743,"createdAt":1498833388,"c, help me!
TradfriGW: Unknown code subscribedDeviceUpdate::65559::{"lastSeenAt":1502205382,"createdAt":1499181237,"color":"f5faf6","reachabilityState":1,"name":"...","dimvalue":254,"type":"TRADFRI bulb GU10 WS 400lm","deviceid":65559,"version":"1.2.217","manufacturer, help me!

Looks like the messages transmitted from JTradfri are not transmitted entirely, or FHEM calls _Parse before the full message was received?

Valid for dev-cf

JTradfri stops to receive updates from the gateway after some time. Reason is most likely the system's firewall, that is closing the UDP port after some inactivity.

Bug has been seen on Windows and Linux systems with a custom configured firewall.

Workaround: None yet.

Fix: Ping the gateway periodically in order to keep the port open. The ping feature isn't implemented in the stable Californium yet.

Hey Peter,

thanks for this fantastic peace of work.
As an enhancement it would be nice if the controller could be read and used as a control device.

Thanks,
Michael

Is this project dead or can you give us an eta when you might implement the missing features?

Exception at readline function:

Exception in thread "main" java.lang.NullPointerException
at net.kappelt.JTradfri.Commands.Commandline.run(Commandline.java:26)
at net.kappelt.JTradfri.JTradfri.startThreadHandler(JTradfri.java:62)
at net.kappelt.JTradfri.JTradfri.main(JTradfri.java:48)

Valid for dev-cf
Toggle command not doing anything

I could not find a documentation how to use the switch/dimmer as fhem control device.
I am new to fhem and it could absolutely be that I missed it.
This should be possible because the group state is updated in the app in real-time. Therefore the gateway must send something to the network on which we should be able to react.

Have you done any work in this direction? Otherwise I will try to use wireshark to reverse the protocol.

Thanks in advance for any directions.

Changes in DTLS handshake

Please do not update, otherwise this module won't work

When I try to get the Device List or Group List it won't work, but when I try to get the coapClientVersion I become the following text "coap-client v4.1.2 -- a small CoAP implementation"

Could you please make the hostname configurable?

# @todo make user settable
$hash->{DeviceName} = "localhost:1505";

I tried to change this line with another hostname, but it doesn‘t work.
Thank you very much.

when i try to fetch my devices, i always get this error message : "Error while trying to fetch devices!". With "get coapClientVersion" i resive the message "coap-client v4.1.2 -- a small CoAP implementation".
And if i run "coap-client -m get -k PSK -u Client_identity coaps://IP/15001" in my commandline" i get this output:
v:1 t:CON c:GET i:24f3 {} [ ]
decrypt_verify(): found 24 bytes cleartext
decrypt_verify(): found 4 bytes cleartext
4.01

i guess i did all the steps of your tutorial without any mistakes..

ty for your help
greetings Stimming

Under some (unlikely) circumstances, there might be a division by Zero:

TradfriLib.pm / Line 202

Only valid for current master/ not development version