Jiri Mikulasek

Any update on this after several months?

Hello, thanks for reporting - first please try to setup logging on DEBUG or even TRACE to gather more info

Well, after some investigation it seems after disconnect when trying to reauthenticate for first time it seems there is some race condition and the session key is created twice, which...

I improved the unit test in #215 which is probably spotting the issue

On the debug level you should see `Sending websocket message: keepalive` it should occur every 4th minute

One more thing comes to my mind - may be it's the token expiration - do you use token autorefresh function? If not check the `LoxoneAuth` class API

Hi, thx for quick reaction, do you have any estimation? Or should I just provide some PR with fix triage?

So what do you prefer? Does it make sense to have the encoding optional/configurable via JsonApiConfiguration ? That's probably the easiest way.

@toedter I agree with @peter-plochan that auto-detection may lead to buggy behaviour - simply because the url decoding is not idempotent operation on all possible inputs. I got your point...

Well prepared a PR for 1., please check