Yeah, me too. It was driving me nuts trying to figure out why my scheduled job just silently stopped running.
BTW, yesterday both my unifi binding instances stopped running their scheduled job. Since they both point to the same Unifi controller, I'm assuming it was the same root cause. I have since installed your latest jar, which has the try/catch block. I'll post something if I see it happen again.
The only thing out of the ordinary yesterday is that I powered off the Unifi switch, which also took down one AC-LR that was getting PoE from the switch. (Once all the cables are run to the rack, all my APs will get PoE from the switch. )
The switch is still off, and I won't be in that location until next week. When I'm there I'll power on/off the switch to see if it causes the Unifi controller to report something you might not expect.
Edit: I did see this in one of the logs (for the site that's remote to the Unifi controller). I seem to recall that I had come back into the house from being away for about an hour.
2017-04-11 09:23:22.593 [WARN ] [ing.unifi.handler.UniFiClientHandler] - Unable to update channel 'site' : device == null
2017-04-11 09:23:22.596 [WARN ] [ing.unifi.handler.UniFiClientHandler] - Unable to update channel 'ap' : device == null
On this version of the binding.
2017-04-11 06:28:44.299 [INFO ] [unifi.handler.UniFiControllerHandler] - UniFi Binding v220.127.116.11704101808