This is true for (some) local devices. It is not the case for the above poster, both because it is cloud rather than local and because it is hitting an app endpoint, not communicating directly to a driver. The port is for unsolicited inbound communication from such devices. You'll see a different error when that is the case.
This seems likely to be the issue then. The general problem with this kind of error is that you have some sort of cloud service set up to connect to your hub, but the app you had on the hub to receive that communication is no longer there. (The previous app ID is in that log entry, should you have a backup you could use to confirm, but it seems like you have a good idea already.)
Normally, you'd be able to just figure out whatever that is and remove it on the other side, that being the Life360 side in your case. However, it seems others have not had luck trying (though you certainly could try). For example: [RELEASE] Life360+ (BROKEN) - #241 by ritchierich. Ultimately, something like that will have to be the solution, however.
I don't see any errors in the log entries above. 
(Just a warning--it's letting you know this traffic is coming in but won't cause problems on its own, just a reminder to remove the other thing to keep your hub a bit happier and probably also Hubitat's cloud servers these requests route through.)
