The WORKBENCH part 1


Really? Do I need to change GW Shield to have holes to fix this display that I love so much :wink:

PS : Take care that 2 SPI devices on same SPI bus with 2 different process may cause trouble (both process accessing SPI bus at the same time). I do not know if Debian has a kind of build in semaphore to prevent this to happen?


LOL… no I wasn’t talking about a gateway display so you don’t have to design a new PCB :rofl:

(but technically it’s possible to control 2 spi devices on one bus… but that’s another story)

TTN GATEWAY central 2

woke up with an idea this morning :

create an (esp) webserver that transmits a webpage with the TTN’s gateway UART debug data, so you can check on a browser (phone/laptop ) the uart output messages wireless.

just a little tool that you plugin the TTN gateway and it works.
but I realize that the TTN gateway power supply is possibly not strong enough ?

a serial to wifi bridge, any input / ideas very welcome :sunglasses:

---------------------- HAPPY EASTER WEEKEND ------------------------------


And this one with a browser terminal interface


we want only to remotely read out the gateway’s uart debug messages in a browser and no programming on the gateway’s side :roll_eyes:


Yes got it, that what’s it basic does :wink:


got it to … I put it in the hackable usefull list tnx Charles :wink:

  • what do ya think… is it feasable ?


For sure, I’ve updated the repository

  • put in the sketch your SSID/PASSWORD here

  • Select correct Flash size from Arduino IDE (example for a WeMos) usually (4M / 1M SPIFFS)

  • just flash the SPIFFS file system from Arduino IDE (contains webserver) to ESP8266 (From Tools ESP8266 Sketch Data Upload, see pictures above)

  • then just flash the sketch above with classic upload button

  • once flashed connect TTN GW TX to ESP8266 RX (GPIO3)

  • connect to http:/your_ESP_IP/ then on terminal type connect

  • take care serial port used for upload is the same so to update firmware of ESP8266 so you have 3 choices:

    • you need to remove TTN GW TX when flashing
    • use OTA to update
    • connect TTN TX pin to GPIO13 and use swap to swap serial pins

Picture does not show data because I have not connected GW to ESP8266 so it’s empty
Have fun


wow a complete tutorial… great tnx Charles… I’ll try later today :sunglasses:


oh no, far from complete :wink:






waited over a month for some new knobs… they are here but still not happy :sunglasses:




found another nice indoor ridgid blue node enclosure



merci @Charles


You’re welcome,
Took 3 days coming from France to NL with 1€ basic post enveloppe, not bad at all :wink:
Have fun

(Duineuk) #682

Wondering how to get accurate UV and lux measurements from a sensor, while still protecting the electronics :thinking: A piece of glass would be the obvious thought, but glass is pretty good at blocking UV.

Started thinking about using flexible TPU to print a “snug” case for the sensors themselves - needs some alignment still but I can see how you might want to assemble most of the case internals like this. (I don’t think it’ll provide much environmental protection tho).

How do other folks do this?



@Amedee the work you do to split up the docker in looks really great! Could you describe a little bit how to setup prometheus, collectd and how to get the status data? I am running a typical RasPi3 + IMST IC880a Gateway and your last development for the fan control is for the original ttn gw, or? I got a VM with Node-RED/Grafana/InfluxDB and would love to get the status data visualised by trying your build on my gateway - if you can help connect it, or tell me how to reach the status data your build provides!



(Amedee) #684

It is still work in progress, I try to do some cleanup this Easter week-end, but it already runs on my 2 gateways – one with, the other with standard raspbian and docker.

My objective is to maintain something that can run seamlessly in both or docker – some people being reluctant to move to (either because they don’t want to involve a cloud 3rd party, or just because they run other things on their Pi).

My current monitoring setup is Collectd/InfluxDB/Grafana – I am not using Prometheus for now; Prometheus is in the setup because it was in JPM’s repo, but if you look in my fork I also have a docker-compose-collectd.yml file.
So basically:

  • docker-compose.yml is for a Prometheus Exporter / Prometheus / Grafana stack (exporter code is the one from Jac)
  • docker-compose-collectd.yml is for a Collectd / InfluxDB (or Graphite if you prefer) / Grafana stack

Both are reporting the same info in term of gateway statistics, so it is a matter of taste.
(I also have a nginx/Node-Red/InfluxDB/Grafana docker setup for the ‘client’ side, but I need to push that one to GitHub…)

Regarding the fan control is only for @dbrgn 's RPi3/IC880a backplane (It can probably easily re-used on other hardware, but this is the only one I have :wink: )

(Duineuk) #685

So I’ve built this distro and downloaded it to my dev gateway… I should just be able to point Grafana to either the public device URL, or my local IP?

(Amedee) #686

There is no Prometheus server running on the node, only the “exporters” so you need “something else” between Grafana and the node (Prometheus or InfluxDB depending on your what you choose)

But you could use the public IP, I use the local IP to get a direct connection.

While we could run Prometheus/InfluxDB on the node, I don’t think it is a great idea, because the SD-cards do not like to much writes…
And I also prefer to consolidate the data of all my (2) nodes in one place.