The ~24h connection drops I mentioned were from the old JS version, not v2.0. I only installed 2.0 yesterday, so I haven’t been able to reproduce anything on the new stack yet.
The changes in my fork are preventive — based on that old behaviour and how session/cookie refresh works in the Python rebuild. I’m running a 24h soak test on my Homey now and will post the results here either way.
If 2.0 stays stable as-is, that’s great — then it’s just an extra safety net, not a fix for a confirmed bug.
Thanks for calling that out.
