Other LAN Edge drivers have reported issues with the new hub update (0.54.10).
The culprit appears to be the getpeername() function which I can confirm is being called in the watch_socket function (line 188) of the LAN Motion Driver.
It appears @TAustin isn’t actively monitoring these threads but is there someone on the Dev Team (@nayelyz can you help?) that knows why this call to getpeername() appears to cause things to “blow up” since the 0.54.10 hub update?