This parameter interests me a lot too!

Hello!

I can confirm that I updated to version 2.1.2.10605 yesterday and it seems I no longer have the problem with the devices disconnecting.

Cheers!

Hello eronodau,

In addition to the 300-user limit on the upcoming Discovery version, will there be any other limitations or missing features compared to the Enterprise version?

Hello,

indeed we wanted to restrict database access using WebSockets, but this is clearly causing problems.

Overall, we have an issue with the WebSocket library we're using.

While waiting for a patch (which should arrive shortly), you can use...

I see there are new nightly builds since jc35's test.
Personally, I don't feel like testing them...

Is there somewhere we can see the changes and fixes included in these nightly builds?

For example, in this release version changelog:
https://www.wapt.fr/fr/doc/wapt-changelog ...

Thanks for your help, jc35.

Hopefully, this problem will be resolved quickly by the WAPT Team...
In the meantime, I created a small batch file that allows me to remotely restart the WAPT services for each machine displaying "DISCONNECTED"...
But it's a pain.

Thanks for your feedback!

Yes, so in my opinion, my problem won't be solved since this is what happens in my case when the user leaves their docking station (connected via a network cable) and switches to Wi-Fi to go to the meeting room...

I suppose we'll have to wait for a...

Thanks for your reply jc35, I'm looking forward to your feedback on the Nightly build.

Cheers!

Hello,

I'd like to reiterate my question and ask again when this bug will be fixed?

It's becoming extremely annoying to have to restart the WAPT services on multiple machines every time a package update is deployed...

I'm not sure that reverting to version 2.0 is risk-free (and I don't see any other way to do so).

Do you think this problem will be resolved quickly?

It's quite frustrating not being able to deploy my updates to all the workstations simply because they aren't showing as reachable...

I checked on one of the affected workstations, and restarting the WAPT service resolved the issue.