devaskim

``` admin@ssdnodes-den:~/affine$ curl http://[::1]:80 Hostname: e6b185f04069 IP: 127.0.0.1 IP: ::1 IP: 172.17.0.2 IP: 2001:db8:1::242:ac11:2 IP: fe80::42:acff:fe11:2 RemoteAddr: [2001:db8:1::1]:50140 GET / HTTP/1.1 Host: [::1] User-Agent: curl/7.81.0 Accept: */* ```

There are no changes, because I use default bridge network ``` services: affine: image: ghcr.io/toeverything/affine-graphql:stable container_name: affine_selfhosted command: ['sh', '-c', 'node ./scripts/self-host-predeploy && node ./dist/index.js'] ports: - '3010:3010' - '5555:5555'...

@fourdim do you have any other ideas?

@DuXiaoChuang According to your gateway config, MQTT config is in mqtt.json

@AlexDoanTB Think about putting the disclaimer at the top of the template at least for some time. As deeper it, as more problems will be...

Are there any plans to let configuring BDT with public library's API ? @envas Did you solve the implementation issue and how?

Attribute should be places in `msg`, not in `metadata`. Also there is no need to setup attribute scope, because this is done in `Save Attributes` node.

Seems like your `Save attribute` node has wrong configuration (save to server attribute)

Maybe [this anwer](https://github.com/thingsboard/thingsboard/issues/9783#issuecomment-1893773252) will help you

@Backdraft007 agree. @gcorthey From my experience it is more reliable to use a packet sniffer (tcpdump, WireShark and et.c) on a server side and filter traffic by mqtt protocol. Knowing...