Closed nevermind2001 closed 11 months ago
Seeing the same issue. It looks like the timeout has been introduced by node-unifi version 2.4.1: https://github.com/jens-maus/node-unifi/commit/8ccb7523110962dd928a3fb39d60502c3a8e0d0d
The updated node-unifi is part of ioBroker.unifi 0.6.5: https://github.com/iobroker-community-adapters/ioBroker.unifi/commit/5da321c74411e18239d723c34d7677ba7d61a641
The adapter should probably identify the timeout and trigger an update anyway.
Changing line 265 (and following) in main.js to the following code works for me (warning: this is not a recommended patch, since it will hammer the target in case of a login failure):
try {
await defaultController.login();
} catch (err) {
this.handleError(err, undefined, 'updateUnifiData-login');
this.queryTimeout = setTimeout(() => {
this.updateUnifiData();
}, this.settings.updateInterval);
return;
}
with V3.2.5 on UDM Pro the login is with the adapter not possible any more.. any ideas? The change above is not working here.
with V3.2.5 on UDM Pro the login is with the adapter not possible any more.. any ideas? The change above is not working here.
If 3.2.5 is not working with node-unifi, please report your issue there, This is nothing that have to be handled in ioBroker.unifi separately. However, please note that v3.2.5 is still a beta version known to have severe issues as it seems (https://ubiquiti-networks-forum.de/board/thread/8516-unifi-os-3-2-5-ein-totaler-flopp/?postID=103950).
Since maybe a few weeks i have the following error in my iobroker log. after this error happens, the adapter stops working which means, that the datapoints are not updated anymore, for example is_online or last_seen (which i use for presence). The instance is still green.
After a restart it worked again until the error occurs again.
(is_online has to be false^^)
Yesterday i updated my Unifi-Controller to 7.5.187 but the error was also on the previous Controller Version.