Console: All of my gateways except one are "gone" - multiple different error conditions

cslorabox
Thu, 25 Feb 2021 00:45:55 +0000

dellekom:

I install gateways for third parties, I may manage them in the TTN console but if customers don’t allow access to their device, there is nothing I can do.

I see it as part of reality that needs to be accepted.

Indeed, if your customer’s won’t allow someone(either you or them) to have a remote access channel, the boxes in the field are unmaintainable short of a very expensive physical site visit by qualified staff. It only takes once incident for customer to understand why this is important.

It is also true that one should not leave rarely needed services open.

You don’t leave things open; most connectivity solutions for a gateway wouldn’t support inbound connections anyway. What you do do is either have a reverse tunnel or a VPN.

If the customer says neither is an option, and firewalling the gateway off away from all of their other things still won’t make it one, then that customer has said loudly and clearly that they do not care about reliability.

Regardless, remote access and custom telemetry while both present in any sane deployment, aren’t the same thing. You could have either without the other… but you really should think about field deploying without both.

You could have telemetry this week if you do it.

If you want to make feature requests of TTN, you first have to switch to the version of TTN that will see future development.