Adrian-Stefan Mares

> Hello, > > We had the same issue, the following command doesn't do the job: `$ ttn-lw-cli dev set $application $device --unset mac-state.pending-application-downlink` > > > > The commend...

It is indeed the case that for multicast devices we currently cannot schedule any downlinks via the Console, as the fixed downlink paths cannot be provided. We should consider adding...

The devil is unfortunately in the details. I agree that the middleware is inconvenient but it silently fulfills more roles than just doing remotes writes to a database. The middleware...

> > > For The Things Stack we should consider a platform integration with IFTTT, see https://platform.ifttt.com/docs > > If that’s not an option, we can go with the Webhooks...

> > > > I think the most elegant solution would indeed be an application package, with the only disadvantage of eating a random FPort. > > And a default...

I generally think in tables and buttons so my opinions on UX are to be taken with a gram of salt, but maybe we could have some check boxes for...

The context here is that accounts are polymorphic entities - they are either users _or_ organizations. It is possible search accounts, but the only thing which is returned back will...

In general I am on the same boat regarding the storage - it should stay in the Identity Server, and it probably should be under two forms: 1. A per...

> I think that `attributes` are very handy though, especially when going stateless. They could act as some sort of headers. Device name is more cosmetic. @adriansmares should we add...

> If I have to cache, I'm not stateless. Any recommendations here? I'm not keen to spin up a whole RDS or similar instance just to cache a few basic...