Maurice Faber

using `2.4.0` and this is still an issue...

Same here. Login is successful but redirects to`/login` ;(

I solved it indeed by setting `NEXTAUTH_SECRET` which seems needed for JWT enc/dec

I think the error is very explicit, and we send a very long bearer token. Is there a limit to that? Maybe it can be stretched?

Aha, but theoretically it might very well be a bug in vscode itself then.

This error is coming from the debug console when the explorer runs the tests: ``` Could not read source map for file:///xx/src/api/apps/%7BteamId%7D.ts: ENAMETOOLONG: name too long, open '/xx/api/apps/{tdata:application/json;charset=utf-8;base64,eyJ2...[rest of beare...

As you can see the filename contains brackets: `{teamId}.ts`. That is probably not handled well.

I saw only two occurences of `ENAMETOOLONG` in the vscode repo, but none referring to reading source map files.

Hi @iMicknl, any progress here? Would it be possible at some point to read battery level of the nest protects with this?

Or is it only reporting the voltage? That might not be meaningful enough for most of us I assume. A derivate binary_sensor could be created that computes the level perhaps?