Invalid error message when gateway is unconfigured? about node-tradfri-client

[AlCalzone]

could it be, that this error message is wrong?

Maybe. To confirm please run your script with the following command-line and post the logs here:

# on linux:
DEBUG=node-*-client node main.js
# on Windows:
set DEBUG=node-*-client && node main.js

where main.js is your script name.

[neophob]

jep just did that:

  node-tradfri-client [DEBUG] Attempting connection. Identity = Client_identityfoo, psk = <redacted>, this.requestBase = coaps://gw-a0xx...:5684/ +4ms
  node-coap-client getConnection(coaps://gw-a0xx...:5684) => establishing new connection +4ms
  node-coap-client socket creation for origin coaps://gw-a0xx...:5684 failed: Error: getaddrinfo ENOTFOUND gw-a0xx... +11ms
  node-coap-client socket creation for origin coaps://gw-a0xx...:5684 failed: Error: getaddrinfo ENOTFOUND gw-a0xx... +2ms
  node-coap-client socket creation for origin coaps://gw-a0xx...:5684 failed: Error: getaddrinfo ENOTFOUND gw-a0xx... +1ms
  node-coap-client tryToConnect(coaps://gw-a0xx...:5684) => failed with error: Error: getaddrinfo ENOTFOUND gw-a0xx... +0ms
  node-tradfri-client [DEBUG] Connection failed. Reason: timeout +15ms

The (unconfigured) gateway works - at least the ios app can connect

[AlCalzone]

Well, the gateway is actually not being found. Try the IP address, afaik some users have trouble connecting by hostname, while some have trouble connecting by IP - might be related to the gateway revision.

[neophob]

Firmware version is - according to the mdns record v1.3.14.
You was right, connecting with the ip works like a charm.... wtf.

ping the gateway with the name does not work (also not using the .local suffix). now thats weird, i'll check with a second gateway where this worked.

I'll give feedback as soon as I know more.

[neophob]

Just one wild guess, running discovery, the gateway returns addresses: [ '10.0.0.94', 'fe80::a2cc:2bff:fef8:535d' ] } - it looks like it exposes its link-local ipv6 address, that might be an actual bug on the gateway

[AlCalzone]

it exposes its link-local ipv6 address, that might be an actual bug on the gateway

Mine does that too, but it only sends that to my PC's IPv6 address, so the current discovery doesn't work. What's the problem with exposing the IPv6 address? I'm not too familiar with that.

[neophob]

not sure, but the "fe80::" address is a link-local address (think the 127.0.0.1 of ipv6). so it might be that the name is mapped either to the working ipv4 address or to the non working ipv6 address. its not defined who "wins" when you query the name, so name resolution might work or not.
as a current workaround, I guess I stick to using the ipv4 address - then it at least works as long no ip change happens.

[neophob]

ok, second gateway works without any issues (ping gw-a0cc.. works, so is ping ip).

-> guess thats related to the gateway firmware