When I use a command like this:
coap-client -m put -u "USER" -k "KEY" -e '{ "3311": [{ "5850": 1 }] }' "coaps://192.168.2.1:5684/15004/195019"

The response is always just:
v:1 t:CON c:PUT i:8894 {} [ ] decrypt_verify(): found 24 bytes cleartext decrypt_verify(): found 4 bytes cleartext

And nothing happens....
Getting the data from my light does work:
{"9001":"NAME","9002":1542748695,"9003":195019,"9039":226934,"5850":1,"5851":0,"9108":0,"9018":{"15002":{"9003":[65579,65581,65580]}}}

Does somebody have an idea to try?

Hey Glenn,
Your documentation is by far the best I have found on the internet, amazing work.

However, one thing is still unclear to me. How to set a custom time interval for the motion sensor? or even read the current values mentioned in https://github.com/glenndehaan/ikea-tradfri-coap-docs#sensor-parameters ?

Thanks!

coap-client v4.1.2 -- a small CoAP implementation

GW Version: 1.11.51

Hi,
calling "coaps://$IP:5684/15011/9030" (gateway reboot) returns a 4.05 which is from my understanding a Method Not Allowed Error.
Calling other methods like /15011/15012 works fine.

Please let me know, if you need any kind of other output or other information.

Thanks & cheers,
Lennart

I had a question regarding the numbers that are as key mentioned in the retrieval of the groups.
For instance I've got the following list already:

{
    5850: "status"
    5851: "brightness"
    9001: "name"
    9002: "???"
    9003: "group_id"
    9018: { // items in group
        15002: {…} // 15002 is what then? Sub group? No endpoint for that
    }
    9039: "???"
    9108: "???"
}

Maybe you can clearify some data? It's sad that there's no proper documentation for this yet.

Hi,

I discovered that the google assistance can turn on/off bulbs even if the wifi is off. And the outside internet shouldn't have a direct connection into my home network. So there seems to exist a connection from the gateway into internet. Otherwise I cannot think of how the google assistance can access my bulbs.

I found out that there is a amazonaws url in the coaps://$TF_GATEWAYIP:5684/15011/15012 | Gateway details endpoint. Did you by chance had a look?

Best
Dongha

Hi Glenn,
at first I'd like to thank you for this excellent guide. It helped me a lot to understand how the Tradfri gateway works, the meaning of the properties and how to send values!

I've written an "add-on" guide about Debugging COAPS with IKEA Tradfri gateway - my first work on Github!

In the last part of that guide there is a section that explains how to get the pre-shared key from the IKEA Home Smart app to be able to read all CoAP communication between the IKEA Home Smart app and the Tradfri gateway with Wireshark in clear text.

Example for a air purifier status:

{
  "3": {
    "0": "IKEA of Sweden",
    "1": "STARKVIND Air purifier",
    "2": "",
    "3": "1.0.033",
    "6": 1,
    "7": 4364,
    "8": 0
  },
  "9001": "Luftreiniger",
  "9003": 65545,
  "9002": 1643891791,
  "9020": 1644770699,
  "9054": 0,
  "5750": 10,
  "9019": 1,
  "15025": [
    {
      "5900": 20,  # mode: 0: off, 1: auto, 10 to 50: power levels
      "5902": 6992,  # unknown
      "5903": 0,  # unknown, (completely guessed: maybe filter lifetime LED?)
      "9003": 0, 
      "5904": 259200,  # Filter maximum lifetime minutes (= 180 d)
      "5910": 252208,  # Minutes until filter replacement
      "5908": 20,  # effective mode of operation
      "5905": 0,  # 0: Control panel enabled, 1: control panel locked
      "5906": 0,  # 0: Control panel light: 0: enabled, 1: disabled
      "5907": 9,  # Air quality, turns to 65535 when device is disabled
      "5909": 7021 # unknown, similar value to 5902
    }
  ]
}

Thank you for sharing your work!!

The string interpolation of $TF_USERNAME in section Authenticate of README does not work because of it is wrapped by a single quote.

It should like following:
% coap-client -m post -u "Client_identity" -k "$TF_GATEWAYCODE" -e "{\"9090\":\"$TF_USERNAME\"}" "coaps://$TF_GATEWAYIP:5684/15011/9063"

Hi,

Is there a way to get "notified" when the status (scene, on/of, dimmer) of a lightbulb change. Or is it necessary to constantly ask the endpoint what the status is?

Want to use this on my smart mirror to display the light status, I have seen some apps where it updates almost immediately after you press the hardware IKEA button.

Hello Glenn,

I'm still working on my module.
In the category there are Bulb with different white, Bulb with Colors or transformers.

Is it possible to find out, which device is connected without analyze the parameter from device Info:
[3] => stdClass Object
(
[0] => IKEA of Sweden
[1] => TRADFRI bulb E14 CWS opal 600lm
Maybe I can read the "CWS" to know this bulb can colors and the "WS" when it is only different white but that look not very professional.
I want to change the controls dependent of the exact device...
Here a big list: http://sprunge.us/CCQF
But I don't find what I'm searching for, do you know whats the best way?

Joachim

Hi Glenn,

I was wondering if you have ever looked into the DEVICE (3) key; each device has an extra data array 3, with some device data.
By looking at different sources and common sense I documented the following items myself;

    // 3.0 = Manufacturer
    // 3.1 = Product name
    // 3.2 = always empty?
    // 3.3 = firmware version
    // 3.6 = 1 or 3? (looks to be 3 always whenever a battery is present on my devices. 1 when not)
    // 3.7 = Product group ID? (this is a guess)
    // 3.9 = Battery level

If you like I can give you some additional data about my smart home devices.

Hello,

The HEX colors doesn't work by me. How can I fix this?

Endpoint id should be 15004 instead of 15001 on "Get info about a specific group"

Hey, I'm trying to install libcoap on Windows right now. I have VisualStudio 2019 and OpenSSL installed. Unfortunately, I always get the error that the following file is missing.

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(240,5):

Probably the error is on my side. Can someone help me with this? Thanks a lot

There may be a bug in the latest firmware of the RGB Bulb "TRADFRI bulb E14 CWS opal 600lm" that causes it to completely turn off when setting red colours via HSV (as used by the Home Assistant Tradfri integration). I'm not sure how they calculate the HSV values but I suspect that they use the UINT16 range as a scale (0 = 0%, 65535 = 100%). However, when passing any value above 65278 for Hue ("5707"), it just turns off. I detected that because Home Assistant always uses HSV values and passes e.g. '5708': 65279, '5707': 65535 for full red colour.

My assumption is that they use this convention to calculate HSV values:

HUE = VAL_5707 / 65535 * 360
SAT = VAL_5708 / 65535 * 100

Example:

$ coap-client -m put -u "$COAP_USER" -k "$COAP_PW" "coaps://$TF_GATEWAY/15001/65540" -e '{"3311": [{"5850": 1, "5708": 65535, "5707": 65279}]}'

Ideally this would set the bulb to a deep red, instead it will lead to the bulb being physically off but reporting as on ("5850": 1):

$ coap-client -m get -u "$COAP_USER" -k "$COAP_PW" "coaps://$TF_GATEWAY/15001/65540"
{
  "9001": "TRADFRI bulb 3",
  "3": {
    "0": "IKEA of Sweden",
    "1": "TRADFRI bulb E14 CWS opal 600lm",
    "2": "",
    "3": "2.3.086",
    "6": 1,
    "7": 10243,
    "8": 3
  },
  "9003": 65540,
  "9002": 1629536890,
  "9020": 1644754054,
  "9054": 0,
  "9019": 1,
  "5750": 2,
  "3311": [
    {
      "5710": 0,
      "5850": 1,
      "5849": 2,
      "5851": 224,
      "5707": 65279,
      "5708": 65535,
      "5709": 0,
      "5706": "f1e0b5",
      "9003": 0
    }
  ]
}

Also note the HEX color code "5706": "f1e0b5", which is something like beige (maybe a default colour).

They must have introduced this behaviour in the last FW update because until then my automations were working.

Maybe this would be worth mentioning in the documentation?

Hello Glenn,

many thanks for your very good documentation and the examples!

Is it possible to get the Preshared Key for a given Username or to control if the Preshared Key for the given Username is still guilty?

Joachim

Awesome, thanks for this info.
I found that unfortunately only the hex values listed seen to be supported - writing any other value defaults to 'efd275': 'Warm glow',

But querying the bulb also gives changing values for 5707, 5708, 5709, 5710 - using a "remote control"'s )>) button to change color, I get these 9 settings:

"3311":[{"5850":1,"5851":254,"5707":5309, "5708":52400,"5709":32886,"5710":27217,"5706":"efd275","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":4980, "5708":62974,"5709":35848,"5710":26214,"5706":"ebb63e","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":4137, "5708":65279,"5709":38011,"5710":24904,"5706":"e78834","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":1490, "5708":61206,"5709":40632,"5710":22282,"5706":"da5d41","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":59789,"5708":65279,"5709":32768,"5710":15729,"5706":"d9337c","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":55784,"5708":44554,"5709":22282,"5710":12452,"5706":"c984bb","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":47324,"5708":51774,"5709":13107,"5710":6554, "5706":"6c83ba","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":5427, "5708":42596,"5709":30015,"5710":26870,"5706":"f1e0b5","9003":0}]
"3311":[{"5850":1,"5851":254,"5707":5800, "5708":24394,"5709":25022,"5710":24884,"5706":"f5faf6","9003":0}]

Changing 5707 and 5708 does not seem to have an effect.
5709 seems to affect warmth, i.e. higher values approach red.
5710 seems to affect green, i.e. higher values approach green.

The app "Hue Essentials" must have figured it out, as it allows specifying a (HEX) color, achieving what could be a full red (#ff0000):

"3311":[{"5850":1,"5851":254,"5707":0,"5708":65279,"5709":45914,"5710":19615,"5706":"0","9003":0}]

    public static final String COLOR = "5706";
    public static final String COLOR_X = "5709";
    public static final String COLOR_Y = "5710";

Which probably is CIE xy chromaticity - https://en.wikipedia.org/wiki/CIE_1931_color_space#CIE_xy_chromaticity_diagram_and_the_CIE_xyY_color_space

Hi,

Transitions are ignored when sending commands to Tradfri lights with transition times as float values eg. 10.5 - the light jumps to the specified setting instantly. Integer values work fine.

This leads me to believe that the Transition Time (key 5712) is of type Int and not Float (as written in the documentation), like most of the other parameters.

Hello @glenndehaan,

That you for the docs, they have been very useful!

A bit of context: I have 2 scenes, both belong to the "SuperGroup". First of all, the status of the scenes always comes as "active - true", which when all lights are off, I would assume that is wrong. But I have the idea that you have mentioned this somewhere in the docs that is a common bug.

The problem that i am encountering is that when i activate one scene, all devices seem to be affected, not only the ones listed in the scene... But when I activate the scene from the IKEA app, the scene behaves as expected.

In your experience, do you know what could be happening?

Please note: this key will expire if you don't use it in 6 weeks from activation. Every time you use this key the time will be extended accordingly.

Although I use the key twice each day, every 6 weeks I get

Jun 30 11:09:28 ALRT 115 invalidate peer
Jun 30 11:09:28 WARN received alert, peer has been invalidated
Aug 18 12:00:00 ALRT 115 invalidate peer
Aug 18 12:00:00 WARN received alert, peer has been invalidated

and I have to add another user. Am I missing something?

Hello Glenn,

may be you see want is wong, but for me the RGB-command failed.
I try your example:
coap-client -m put -u "$TF_USERNAME" -k "$TF_PRESHARED_KEY" -e '{ "3311": ["5709": 65535, "5710": 65535] }' "coaps://$TF_GATEWAYIP:5684/15001/$TF_DEVICEID"
to adapt for me:
coap-client -m put -u "myusername" -k "mykey" -e '{ "3311": ["5709": 65535, "5710": 65535] }' "coaps://192.168.178.52:5684/15001/65538"
but I get this return:
v:1 t:CON c:PUT i:2312 {} [ ] decrypt_verify(): found 24 bytes cleartext decrypt_verify(): found 15 bytes cleartext 5.00 {"r":"07"}
I think that 5.00 {"r":"07"} should show me that something is wrong, but I don't see it...

Joachim

I tried changing the link to the 4.3.0 release.
But the script doesn't work with that version.
Building the RC version works fine.
Can the script be changed to work with the 4.3.0 final version?

Maybe this thread helps implemting shortcut Button?
https://community.home-assistant.io/t/ikea-shortcut-button/214998

Hello Glenn,

do you know the maximum-value for the Blinds? Is it 0.0 to 100.0?

Joachim