WoL constantly checking status, insanity in logs #89
Comments
|
This is not default behaviour but intended behaviour. Something is trigging the debug logs to activate. This can happen if your environment contains the environment variable It can also happen if a log mode is activated in the homebridge-wol configuration. Read the configuration documentation in the README file and ensure that you accessory configuration does not activate any of the log modes. I can not recommend downgrading the plugin as there are known issues. The newest version is tested and has no known issues. |
|
I don't see any debug mode enabled. What wonders me that you have added pinginterval default is 2. [1/14/2020, 17:28:00] Plugin /usr/lib/node_modules does not have a package name that begins with 'homebridge-'. |
|
Could you post your entire configuration file? From the error log above it seems as if it is badly written. |
{
"bridge": {
"name": "Homebridge",
"username": "mac",
"port": 51826,
"pin": "123-61-123"
},
"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"accessories": [
{
"accessory": "Xbox",
"name": "XboxOne",
"ipAddress": "192.168.0.11",
"liveId": "redacted"
},
{
"accessory": "NetworkDevice",
"name": "BartekPC",
"mac": "redacted",
"ip": "192.168.0.1",
"shutdownCommand": "net rpc shutdown --ipaddress 192.168.0.1 --user homebridge%password"
},
{
"accessory": "NetworkDevice",
"name": "MichalPC",
"mac": "redacted",
"ip": "192.168.0.3",
"shutdownCommand": "net rpc shutdown --ipaddress 192.168.0.3 --user homebridge%password"
},
{
"accessory": "NetworkDevice",
"name": "Dodo",
"mac": "redacted",
"ip": "192.168.0.7",
"shutdownCommand": "net rpc shutdown --ipaddress 192.168.0.7 --user homebridge%password"
},
{
"accessory": "NetworkDevice",
"name": "Tiny",
"mac": "redacted",
"ip": "192.168.0.8",
"shutdownCommand": "net rpc shutdown --ipaddress 192.168.0.8 --user homebridge%password"
},
{
"accessory": "NetworkDevice",
"name": "ESXi",
"mac": "redacted",
"ip": "192.168.0.9",
"shutdownCommand": "ssh root@192.168.0.9 halt"
}
],
"platforms": [
{
"name": "config.json",
"port": 8080,
"auth": "form",
"theme": "dark-mode",
"restart": "/etc/init.d/homebridge restart",
"tempUnits": "c",
"sudo": true,
"debug": false,
"log": {
"method": "file",
"path": "/var/log/homebridge.log"
},
"platform": "config"
},
{
"platform": "cmdSwitch2",
"name": "CMD Switch",
"switches": [
{
"name": "Backup 7 Days To Die",
"on_cmd": "/home/pi/Backup_7_Days_To_Die.sh",
"off_cmd": ".",
"state_cmd": "/home/pi/alwaysoff.sh",
"polling": true,
"interval": 3
},
{
"name": "Backup Conan Exiles",
"on_cmd": "/home/pi/Backup_Conan_Exiles.sh",
"off_cmd": ".",
"state_cmd": "/home/pi/alwaysoff.sh",
"polling": true,
"interval": 3
},
{
"name": "Backup Space Engineers",
"on_cmd": "/home/pi/Backup_Space_Engineers.sh",
"off_cmd": ".",
"state_cmd": "/home/pi/alwaysoff.sh",
"polling": true,
"interval": 3
},
{
"name": "Backup Medieval Engineers",
"on_cmd": "/home/pi/Backup_Medieval_Engineers.sh",
"off_cmd": ".",
"state_cmd": "/home/pi/alwaysoff.sh",
"polling": true,
"interval": 3
},
{
"name": "Backup The Forest",
"on_cmd": "/home/pi/Backup_The_Forest.sh",
"off_cmd": ".",
"state_cmd": "/home/pi/alwaysoff.sh",
"polling": true,
"interval": 3
}
]
}
]
}That config was working yesterday. I've only stopped homebdrige |
|
You've configured a platform called Homebridge also warns that you've got no plugins installed. Basically, re-read your configuration, ensure that you've got all the plugins installed and that everything is up-to-date. |
|
Well, I have done no changes, the plugis are there. No touching config and it started yesterday. /usr/var/node_modules/ I have all plugins that I'm trying to load. |
|
The log you posted says otherwise. Could you try to restart Homebridge in debug mode and post the full log from the start of its execution? |
|
pi@Homebridge:~ $ DEBUG=* homebridge -D the config registered by https://github.com/oznu/homebridge-config-ui-x |
|
I've read that after updating node, you need to rebuild modules but apparently that's also no go:
prebuild-install WARN install EACCES: permission denied, access '/root/.npm' npm ERR! A complete log of this run can be found in: |
|
So for the first issue, you'll have to check in with https://github.com/oznu/homebridge-config-ui-x. I have never used that package so I cannot help you with it. The issue you're facing with Homebridge is currently not related to this plugin. As for not being able to update, you're facing privilege issues which you'll have to debug. This could be a good place to start: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally. You can also try this: https://npm.community/t/eacces-permission-denied-access-root-npm/5667. Basically, from what I can see you only have issues related to other packages or Node / NPM itself and I can't be much of assistance there. If you do resolve these issues and are able to start Homebridge but still face issues related to this package, please get back and I'll try to help you. |
|
Yesterday after long fight I was able to repair and bring back homebridge back to life. |
|
Great! The logs still isn’t intended behaviour. We’re you able to find if there were any mention of DEBUG in your environment? As for the second issue, it’s described here: #85. Basically it’s an unfixable issue where you need to decide between two semi-working solutions. |
|
I'm still looking for anything in Debug mode. |
|
@bbaraniec It was working, but only to a point. Basically the code was handing over the execution to Homekit as soon as possible because it knew no better. This could result in inaccurate values given back to Siri. With the new version, all of the asynchronous code has been rewritten to greatly simplify the plugin in terms of readability and control flow complexity to update it for the coming years, this also resulted in a more "proper" solution for when execution was handed back to Homekit. But as you can tell from #85, Siri does not like waiting for too long which made me implement both modes - the old and imperfect one which is fast enough for Siri and the new which properly waits for shutdown commands etc. to be accurate. |
|
If you don't find what's causing the debug mode to trigger, you could manually override the logging in order to prevent all logs. These lines to these: this.log = () => {};
this.debugLog = () => {};
this.pingLog = () => {};Closing this for now as it cannot be replicated. |
After upgrading to latest version I'm getting spammed in logs, by spammed I mean wall of text like this:
[1/14/2020, 00:32:42] [xxx] Attempting to ping "xxx" (ip..7)
[1/14/2020, 00:32:42] [yyy] Result of pinging "yyy" (ip..8): offline
[1/14/2020, 00:32:43] [bbb] Result of pinging "bbb" (ip..9): offline
[1/14/2020, 00:32:43] [zzz] Attempting to ping "zzz" (ip..1)
[1/14/2020, 00:32:43] [zzz] Result of pinging "zzz" (ip..1): online
[1/14/2020, 00:32:43] [aaa] Attempting to ping "aaa" (ip..3)
[1/14/2020, 00:32:43] [yyy] Attempting to ping "yyy" (ip..8)
[1/14/2020, 00:32:43] [xxx] Result of pinging "xxx" (ip..7): offline
[1/14/2020, 00:32:44] [bbb] Attempting to ping "bbb" (ip..9)
[1/14/2020, 00:32:44] [aaa] Result of pinging "aaa" (ip..3): offline
[1/14/2020, 00:32:44] [xxx] Attempting to ping "xxx" (ip..7)
[1/14/2020, 00:32:44] [yyy] Result of pinging "yyy" (ip..8): offline
[1/14/2020, 00:32:45] [zzz] Attempting to ping "zzz" (ip..1)
[1/14/2020, 00:32:45] [zzz] Result of pinging "zzz" (ip..1): online
[1/14/2020, 00:32:45] [aaa] Attempting to ping "aaa" (ip..3))
It doesn't stop.
The text was updated successfully, but these errors were encountered: