Can't access TTN Console, ttnctl fails, TTN Node-RED library fails, and Kickstarter gateways get stuck after daily reboot

[arjanvanb (Arjan)]

@65sc02

I am surprised that there isn’t a bigger outcry if everyone (?) is affected?

Though TTN Console is great for debugging (especially to debug OTAA Join problems, or to see the gateway’s Traffic page when one does not have access to the gateway’s raw logs), many of us simply don’t need it every day as more reliable alternatives exist:

• Unfortunately, right now ttnctl is failing too:

  ttnctl gateways status 19711137
  INFO Discovering Router...
  FATAL Could not get Router from Discovery      error=Internal error: [Unavailable] transport is closing
  

  But often that works when TTN Console does not.

• The TTN Node-RED library is reported to be failing too, but it seems it’s time to migrate to a regular Node-RED MQTT Input node anyhow.

• Data is being delivered just fine using the MQTT Data API and the HTTP Integration (and likely other integrations as well). An MQTT command line interface might be more reliable than the application/device’s Data page in TTN Console anyhow:

  mosquitto_sub -h eu.thethings.network -t +/# -u haarlem-app-1 -P ttn-account-v2.ko3<redacted>fyr-A
  

  See also A Python program to listen to your devices with MQTT.