Basic service has nothing to do with SLA
- do you really think there should be 24 / 7, highly skilled personnel available for the free of charge community network / gateway ?
- realise that this is a new product and we are probably the first group in the world to test this hardware/software … sure something can go wrong (and it did) but its still an amazing product !
- better communication I agreed before
just had contact with Krishna - Stack Engineer and Operations The Things Industries, and he is working on it right now. So let’s watch our consoles …
never told this!
basic service = 1 (good)
basic service = 0 (bad)
that’s the simple truth
Okay, so it does not match the channel number from the LoRaWAN Regional Parameters document. (And if it should, then TTN would not have added the value to each gateway, as then it should be the same for all.) Does anyone know what’s the use of the channel number in the metadata then?
No SLA thats true. I cannot argue otherwise. Also I have no choice but to use TTN because I cannot configure the product I ourchased.
Future gateways are not free.
When I pay for a product (any) I may expect that is works. TTIG is fixed to TTN so the rule that I may expect a product to work propagates to TTN. Our so SLA does not break (Dutch) laws I expect.
When my product fails (becaus of TTN?) I may return it under Ditch law.
I have my conserns. This is food for thougt for lawyers.
agree, that should be clarified in the future… you buy the hardware (TTIG) now what level of network service you may expect, will it be free for ever ect ect.
Looking at the Basic Station software it seems no longer to be present in the uplink data. So it probably wasn’t/isn’t useful.
The issue in the US region should be resolved.
On EU, most gateways should be working. I’m adding a couple of fixes to make sure all of them are working.
Berlin? Not yet
So after a long battle, the EU gateways must also be working now. If your gateway is not sending uplinks, please send message me your EUI via slack or via a direct message to me.
As some of you might know, our V2 stack does not support the new BasicStation protocol and hence we have a temporary/experimental BasicStation-Bridge that bridges the TTIG to our V2 routers. This bridge is functional but breaks at scale which is what’s happening here). I have added some load-balancing in the backend which should keep it functional.
In the next few weeks, we will be replacing this bridge with a native, highly scalable component which will ensure that these kinds of outages don’t happen.
With regards to the delay; we do our utmost best to make sure that the network and the gateways are running without issues (regardless of SLAs). This has no other reason other than the fact that the intermediate bridge is quite difficult to work with and that this happened to be on a weekend when most of us did not have access to resources. I, myself, have spent the best part of my Sunday trying to fix this.
We do understand that these disruptions can be quite frustrating for the users and we will always do our best to keep these issues minimal.
do you have to check 'Beta Updates ’ on TTIG ?
And in the UK for £60.12 including VAT:
I apologize, but I can’t find it and I’m anxious to order - is there a hard date on release (US)?
Availability from June according the RS UK
They told us: February, 1 week after TTNConf19…
Any official information about delivery ?
But you may subscribe into a special mailing list.
They told us about just doing some paperwork…
Must be a lot of paperwork…
You may enrole there:
I’ve removed my links because these products seems to be offline.
As with all TTN projects, they over promise, and under deliver on time and cost… so I expect this will be delayed for many weeks more…
They need better communication skills as it effect their customer… keeping the customer up to date, keep them in the know and happy.