homebridge-people
homebridge-people copied to clipboard
PeteLawrence
If plugin people is installed, Homebridge getting stuck in startup process
After installing the Plugin in latest version. Homebridge is getting stuck until the startup process.
The plugin is loaded an registred, but the startup stops after the Initializing of my Netatmo Platform and noting happens anymore... No error... the startup get simple stuck a this place.
If i uninstall the people plugin, my homebridge is starting without problems.
Has anyone a Idea what can cause the failure?
I have no error massages, because the process simple stops. Or where can i search for error reports, for posting here.
which method did you use to log your errors? also, do you run homebridge as a systemd service or do you just start it manually via terminal?
This is usually an error in your config. Please double check and post it here if priblem persists.
I run homebridge as a service.
I have no methode to log errors. If homebridge isn't starting i only check the starting routin.
Maybe it is the config file, but I can't see any failure.
Here it is:
{
"platform": "People",
"threshold" : 15,
"anyoneSensor" : true,
"nooneSensor" : true,
"webhookPort": 51828,
"cacheDirectory": "./.node-persist/storage",
"pingInterval": 10000,
"ignoreReEnterExitSeconds": 0,
"people" : [
{
"name" : "Andi",
"target" : "Andis-iPhone-7",
"threshold" : 15,
"pingInterval": 10000,
"ignoreReEnterExitSeconds": 0
},
{
"name" : "Sylvi",
"target" : "Sylvis-iPhone-7",
"threshold" : 15,
"pingInterval": 10000,
"ignoreReEnterExitSeconds": 0
}
]
}
Sorry :-) without the part of the people Plugin everything works fine.
I'd rally like to use this Plugin, because this is the feature which HomeKit is missing for automation...
First come home... last gone...
That is elementary.
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 42531,
"pin": "031-45-154"
},
"platforms": [
{
"platform": "netatmo",
"name": "netatmo platform",
"ttl": 5,
"auth": {
"client_id": "xxxx",
"client_secret": "xxxx",
"username": "xxxx",
"password": "xxxx"
},
"deviceTypes": [
"weatherstation",
"welcome"
]
},
{
"platform": "HarmonyHub",
"name": "Harmony Wohnzimmer"
},
{
"platform": "LiftMaster2",
"username": "xxx",
"password": "xxx"
},
{
"platform": "Vera",
"name": "Vera",
"veraIP": "192.168.178.37",
"includesensor": false,
"ignorerooms": [20,21,22],
"securitypoll": 2000,
"dimmertest": false
},
{
"platform": "People",
"threshold" : 15,
"anyoneSensor" : true,
"nooneSensor" : true,
"webhookPort": 51828,
"cacheDirectory": "./.node-persist/storage",
"pingInterval": 10000,
"ignoreReEnterExitSeconds": 0,
"people" : [
{
"name" : "Andi",
"target" : "Andis-iPhone-7",
"threshold" : 15,
"pingInterval": 10000,
"ignoreReEnterExitSeconds": 0
},
{
"name" : "Sylvi",
"target" : "Sylvis-iPhone-7",
"threshold" : 15,
"pingInterval": 10000,
"ignoreReEnterExitSeconds": 0
}
]
}
],
"accessories": [
{
"accessory": "Roomba",
"name": "Staubsauger unten",
"ip_address": "192.168.178.84",
"dock_on_stop": "true"
},
{
"accessory": "Roomba",
"name": "Staubsauger oben",
"ip_address": "192.168.178.93",
"dock_on_stop": "true"
},
{
"accessory": "FakeBulb",
"name": "Andi",
"bulb_name": "Andi ist zuhause"
},
{
"accessory": "FakeBulb",
"name": "Sylvi",
"bulb_name": "Sylvi ist zuhause"
},
{
"accessory": "Sonos",
"name": "Lautsprecher Küche",
"room": "Küche"
},
{
"accessory": "Sonos",
"name": "Lautsprecher Esszimmer",
"room": "Esszimmer"
},
{
"accessory": "Sonos",
"name": "Lautsprecher Dusche",
"room": "Dusche"
},
{
"accessory": "Sonos",
"name": "Lautsprecher Bad",
"room": "Bad"
}
]
}
type sudo journalctl -e in terminal and post a portion of the last logs - I for myself am running homebridge as a systemd service and had the problem that homebridge couldn't access the persist folder of homebridge-people
But post the logs, maybe they tell us what's wrong
Here we go. I don't know if this is the Section you want, if not I will post more of the Log...
[2017-01-15 22:30:15] Loaded plugin: homebridge-fakebulb [2017-01-15 22:30:15] Registering accessory 'homebridge-fakebulb.FakeBulb' [2017-01-15 22:30:15] --- [2017-01-15 22:30:15] Loaded plugin: homebridge-harmonyhub [2017-01-15 22:30:18] Registering platform 'homebridge-harmonyhub.HarmonyHub' [2017-01-15 22:30:18] --- [2017-01-15 22:30:19] Loaded plugin: homebridge-liftmaster2 [2017-01-15 22:30:19] Registering platform 'homebridge-liftmaster2.LiftMaster2' [2017-01-15 22:30:19] --- [2017-01-15 22:30:20] Loaded plugin: homebridge-netatmo [2017-01-15 22:30:20] Registering platform 'homebridge-netatmo.netatmo' [2017-01-15 22:30:20] --- [2017-01-15 22:30:22] Loaded plugin: homebridge-people [2017-01-15 22:30:22] Registering platform 'homebridge-people.People' [2017-01-15 22:30:22] Registering accessory 'homebridge-people.PeopleAccessory' [2017-01-15 22:30:22] Registering accessory 'homebridge-people.PeopleAllAccessory' [2017-01-15 22:30:22] --- [2017-01-15 22:30:23] Loaded plugin: homebridge-sonos [2017-01-15 22:30:23] Registering accessory 'homebridge-sonos.Sonos' [2017-01-15 22:30:23] --- [2017-01-15 22:30:24] Loaded plugin: homebridge-thinkingcleaner [2017-01-15 22:30:24] Registering accessory 'homebridge-thinkingcleaner.Roomba' [2017-01-15 22:30:24] --- [2017-01-15 22:30:25] Loaded plugin: homebridge-vera VeraLink initializing [2017-01-15 22:30:25] Registering platform 'homebridge-veralink.Vera' [2017-01-15 22:30:25] --- [2017-01-15 22:30:25] Loaded config.json with 8 accessories and 5 platforms. [2017-01-15 22:30:25] --- [2017-01-15 22:30:25] Loading 5 platforms... [2017-01-15 22:30:25] [netatmo platform] Initializing netatmo platform... [2017-01-15 22:30:25] [netatmo platform] Creating NetatmoPlatform... [2017-01-15 22:30:26] [Harmony Wohnzimmer] Initializing HarmonyHub platform... [2017-01-15 22:30:26] Initializing LiftMaster2 platform... [2017-01-15 22:30:26] [Vera] Initializing Vera platform... [2017-01-15 22:30:26] Initializing People platform... Process Device 27: Haustüre [2017-01-15 22:30:27] [Vera] Initializing platform accessory 'Haustüre'... [2017-01-15 22:30:27] [netatmo platform] refreshing welcome device 5694e6c2cce37c4875834d91 (Kamera Wohnraum) [2017-01-15 22:30:27] [netatmo platform] refreshing weatherstation device 70:ee:50:19:e5:fa (Lichtenauer Straße Wohnzimmer) [2017-01-15 22:30:27] [netatmo platform] refreshing weatherstation module 02:00:00:19:b9:20 (Lichtenauer Straße Garten) [2017-01-15 22:30:27] [netatmo platform] refreshing weatherstation module 03:00:00:02:8e:6c (Lichtenauer Straße Schlafzimmer) [2017-01-15 22:30:28] [netatmo platform] Initializing platform accessory 'Lichtenauer Straße Wohnzimmer'... [2017-01-15 22:30:28] [netatmo platform] Initializing platform accessory 'Lichtenauer Straße Garten'... [2017-01-15 22:30:28] [netatmo platform] Initializing platform accessory 'Lichtenauer Straße Schlafzimmer'... [2017-01-15 22:30:28] [netatmo platform] Initializing platform accessory 'Kamera Wohnraum'... ^C[2017-01-15 22:31:10] Got SIGINT, shutting down Homebridge... pi@homebridge:~ $ sudo journalctl -e Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** The program 'node' called Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** Please fix your applicati Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** For more information see Jan 15 22:30:25 homebridge sshd[5237]: pam_unix(sshd:auth): authentication failu Jan 15 22:30:28 homebridge sshd[5237]: Failed password for root from 112.85.42.1 Jan 15 22:30:30 homebridge sshd[5237]: Failed password for root from 112.85.42.1 Jan 15 22:30:39 homebridge sshd[5245]: pam_unix(sshd:auth): authentication failu Jan 15 22:30:41 homebridge sshd[5245]: Failed password for root from 112.85.42.1 Jan 15 22:30:42 homebridge sshd[5237]: Failed password for root from 112.85.42.1 Jan 15 22:30:42 homebridge sshd[5237]: Received disconnect from 112.85.42.110: 1 Jan 15 22:30:42 homebridge sshd[5237]: PAM 2 more authentication failures; logna Jan 15 22:30:43 homebridge sshd[5245]: Failed password for root from 112.85.42.1 Jan 15 22:30:45 homebridge sshd[5245]: Failed password for root from 112.85.42.1 Jan 15 22:30:46 homebridge sshd[5245]: Received disconnect from 112.85.42.110: 1 Jan 15 22:30:46 homebridge sshd[5245]: PAM 2 more authentication failures; logna Jan 15 22:31:02 homebridge sshd[5253]: pam_unix(sshd:auth): authentication failu Jan 15 22:31:04 homebridge sshd[5253]: Failed password for root from 112.85.42.1 Jan 15 22:31:06 homebridge sshd[5253]: Failed password for root from 112.85.42.1 Jan 15 22:31:08 homebridge sshd[5253]: Failed password for root from 112.85.42.1 Jan 15 22:31:09 homebridge sshd[5253]: Received disconnect from 112.85.42.110: 1 Jan 15 22:31:09 homebridge sshd[5253]: PAM 2 more authentication failures; logna Jan 15 22:31:24 homebridge sudo[5262]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root Jan 15 22:31:24 homebridge sudo[5262]: pam_unix(sudo:session): session opened fo lines 979-1001/1001 (END) Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** The program 'node' called Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** Please fix your applicatio Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** For more information see < Jan 15 22:30:25 homebridge sshd[5237]: pam_unix(sshd:auth): authentication failur Jan 15 22:30:28 homebridge sshd[5237]: Failed password for root from 112.85.42.11 Jan 15 22:30:30 homebridge sshd[5237]: Failed password for root from 112.85.42.11 Jan 15 22:30:39 homebridge sshd[5245]: pam_unix(sshd:auth): authentication failur Jan 15 22:30:41 homebridge sshd[5245]: Failed password for root from 112.85.42.11 Jan 15 22:30:42 homebridge sshd[5237]: Failed password for root from 112.85.42.11 Jan 15 22:30:42 homebridge sshd[5237]: Received disconnect from 112.85.42.110: 11 Jan 15 22:30:42 homebridge sshd[5237]: PAM 2 more authentication failures; lognam Jan 15 22:30:43 homebridge sshd[5245]: Failed password for root from 112.85.42.11 Jan 15 22:30:45 homebridge sshd[5245]: Failed password for root from 112.85.42.11 Jan 15 22:30:46 homebridge sshd[5245]: Received disconnect from 112.85.42.110: 11 Jan 15 22:30:46 homebridge sshd[5245]: PAM 2 more authentication failures; lognam Jan 15 22:31:02 homebridge sshd[5253]: pam_unix(sshd:auth): authentication failur Jan 15 22:31:04 homebridge sshd[5253]: Failed password for root from 112.85.42.11 Jan 15 22:31:06 homebridge sshd[5253]: Failed password for root from 112.85.42.11 Jan 15 22:31:08 homebridge sshd[5253]: Failed password for root from 112.85.42.11 Jan 15 22:31:09 homebridge sshd[5253]: Received disconnect from 112.85.42.110: 11 Jan 15 22:31:09 homebridge sshd[5253]: PAM 2 more authentication failures; lognam Jan 15 22:31:24 homebridge sudo[5262]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root Jan 15 22:31:24 homebridge sudo[5262]: pam_unix(sudo:session): session opened for
lines 979-1001/1001 (END) Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** Please fix your application to use the native API of Avahi! Jan 15 22:30:11 homebridge node[5217]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister Jan 15 22:30:25 homebridge sshd[5237]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root Jan 15 22:30:28 homebridge sshd[5237]: Failed password for root from 112.85.42.110 port 17606 ssh2 Jan 15 22:30:30 homebridge sshd[5237]: Failed password for root from 112.85.42.110 port 17606 ssh2 Jan 15 22:30:39 homebridge sshd[5245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root Jan 15 22:30:41 homebridge sshd[5245]: Failed password for root from 112.85.42.110 port 22630 ssh2 Jan 15 22:30:42 homebridge sshd[5237]: Failed password for root from 112.85.42.110 port 17606 ssh2 Jan 15 22:30:42 homebridge sshd[5237]: Received disconnect from 112.85.42.110: 11: [preauth] Jan 15 22:30:42 homebridge sshd[5237]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root Jan 15 22:30:43 homebridge sshd[5245]: Failed password for root from 112.85.42.110 port 22630 ssh2 Jan 15 22:30:45 homebridge sshd[5245]: Failed password for root from 112.85.42.110 port 22630 ssh2 Jan 15 22:30:46 homebridge sshd[5245]: Received disconnect from 112.85.42.110: 11: [preauth] Jan 15 22:30:46 homebridge sshd[5245]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root Jan 15 22:31:02 homebridge sshd[5253]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root Jan 15 22:31:04 homebridge sshd[5253]: Failed password for root from 112.85.42.110 port 25001 ssh2 Jan 15 22:31:06 homebridge sshd[5253]: Failed password for root from 112.85.42.110 port 25001 ssh2 Jan 15 22:31:08 homebridge sshd[5253]: Failed password for root from 112.85.42.110 port 25001 ssh2 Jan 15 22:31:09 homebridge sshd[5253]: Received disconnect from 112.85.42.110: 11: [preauth] Jan 15 22:31:09 homebridge sshd[5253]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root Jan 15 22:31:24 homebridge sudo[5262]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -e Jan 15 22:31:24 homebridge sudo[5262]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
ok this is pretty hard to read as it is just one text instead of line by line
Is homebridge starting automatically after every reboot or do you start it by hand?
If it starts automatically, please reboot your device, what for half a minute, then type sudo journalctl -b and post the logs here - and try to put them in here line by line like you see them in terminal - makes it a lot easier to read ;-)
EDIT: ah nevermind, i just saw that my browser didn't show it line by line - reboot and post the logs as I stated above
Ok...
> pi@homebridge:~ $ sudo journalctl -e
> Jan 15 22:51:44 homebridge bluetoothd[707]: Endpoint unregistered: sender=:1.23 path=/MediaEndpoint/A2DPSource
> Jan 15 22:51:44 homebridge bluetoothd[707]: Endpoint unregistered: sender=:1.23 path=/MediaEndpoint/A2DPSink
> Jan 15 22:51:45 homebridge sshd[1075]: Failed password for root from 112.85.42.110 port 45073 ssh2
> Jan 15 22:51:45 homebridge kernel: EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
> Jan 15 22:51:45 homebridge udisksd[1151]: Mounted /dev/mmcblk0p5 at /media/pi/SETTINGS on behalf of uid 1000
> Jan 15 22:51:45 homebridge org.gtk.Private.UDisks2VolumeMonitor[931]: index_parse.c:191: indx_parse(): error opening /media/pi/SETTINGS/BDMV/index.bdmv
> Jan 15 22:51:45 homebridge org.gtk.Private.UDisks2VolumeMonitor[931]: index_parse.c:191: indx_parse(): error opening /media/pi/SETTINGS/BDMV/BACKUP/index.bdmv
> Jan 15 22:51:48 homebridge sshd[1075]: Failed password for root from 112.85.42.110 port 45073 ssh2
> Jan 15 22:51:52 homebridge sshd[1075]: Failed password for root from 112.85.42.110 port 45073 ssh2
> Jan 15 22:51:53 homebridge sshd[1075]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 22:51:53 homebridge sshd[1075]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:52:02 homebridge sshd[1255]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:52:03 homebridge sshd[1255]: Failed password for root from 112.85.42.110 port 34750 ssh2
> Jan 15 22:52:07 homebridge sshd[1255]: Failed password for root from 112.85.42.110 port 34750 ssh2
> Jan 15 22:52:11 homebridge sshd[1255]: Failed password for root from 112.85.42.110 port 34750 ssh2
> Jan 15 22:52:11 homebridge sshd[1255]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 22:52:11 homebridge sshd[1255]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:52:47 homebridge sshd[1268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:52:49 homebridge sshd[1268]: Failed password for root from 112.85.42.110 port 50156 ssh2
> Jan 15 22:52:50 homebridge sshd[1270]: Connection closed by 112.85.42.110 [preauth]
> Jan 15 22:52:51 homebridge sshd[1268]: Failed password for root from 112.85.42.110 port 50156 ssh2
> Jan 15 22:52:54 homebridge sshd[1268]: Failed password for root from 112.85.42.110 port 50156 ssh2
> Jan 15 22:52:54 homebridge sshd[1268]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 22:52:54 homebridge sshd[1268]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:53:13 homebridge sshd[1277]: Accepted password for pi from 2a02:810d:640:a18:1cd3:44e5:6f65:c694 port 50856 ssh2
> Jan 15 22:53:13 homebridge sshd[1277]: pam_unix(sshd:session): session opened for user pi by (uid=0)
> Jan 15 22:53:13 homebridge systemd[1]: Starting Session c4 of user pi.
> Jan 15 22:53:13 homebridge systemd-logind[327]: New session c4 of user pi.
> Jan 15 22:53:13 homebridge systemd[1]: Started Session c4 of user pi.
> Jan 15 22:53:13 homebridge sudo[1303]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/grep -E ^pi: /etc/shadow
> Jan 15 22:53:13 homebridge sudo[1303]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
> Jan 15 22:53:13 homebridge sudo[1303]: pam_unix(sudo:session): session closed for user root
> Jan 15 22:53:16 homebridge sshd[1289]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:53:18 homebridge sshd[1289]: Failed password for root from 112.85.42.110 port 21258 ssh2
> Jan 15 22:53:20 homebridge sshd[1289]: Failed password for root from 112.85.42.110 port 21258 ssh2
> Jan 15 22:53:23 homebridge sshd[1289]: Failed password for root from 112.85.42.110 port 21258 ssh2
> Jan 15 22:53:24 homebridge sshd[1289]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 22:53:24 homebridge sshd[1289]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:53:32 homebridge sudo[1329]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -e
> Jan 15 22:53:32 homebridge sudo[1329]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
> Jan 15 22:54:03 homebridge sudo[1329]: pam_unix(sudo:session): session closed for user root
> Jan 15 22:54:07 homebridge sshd[1339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 22:54:08 homebridge sudo[1341]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -e
> Jan 15 22:54:08 homebridge sudo[1341]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Those logs contain no traces of homebridge - so it looks like it didn't start
Whiteout the Plugin the autostart works. I start homebridge from hand. And post the log. ... stay tuned :-)
> *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
> *** WARNING *** Please fix your application to use the native API of Avahi!
> *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
> *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
> *** WARNING *** Please fix your application to use the native API of Avahi!
> *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
> [2017-01-15 23:04:23] Loaded plugin: homebridge-fakebulb
> [2017-01-15 23:04:23] Registering accessory 'homebridge-fakebulb.FakeBulb'
> [2017-01-15 23:04:23] ---
> [2017-01-15 23:04:23] Loaded plugin: homebridge-harmonyhub
> [2017-01-15 23:04:26] Registering platform 'homebridge-harmonyhub.HarmonyHub'
> [2017-01-15 23:04:26] ---
> [2017-01-15 23:04:27] Loaded plugin: homebridge-liftmaster2
> [2017-01-15 23:04:27] Registering platform 'homebridge-liftmaster2.LiftMaster2'
> [2017-01-15 23:04:27] ---
> [2017-01-15 23:04:29] Loaded plugin: homebridge-netatmo
> [2017-01-15 23:04:29] Registering platform 'homebridge-netatmo.netatmo'
> [2017-01-15 23:04:29] ---
> [2017-01-15 23:04:30] Loaded plugin: homebridge-people
> [2017-01-15 23:04:30] Registering platform 'homebridge-people.People'
> [2017-01-15 23:04:30] Registering accessory 'homebridge-people.PeopleAccessory'
> [2017-01-15 23:04:30] Registering accessory 'homebridge-people.PeopleAllAccessory'
> [2017-01-15 23:04:30] ---
> [2017-01-15 23:04:32] Loaded plugin: homebridge-sonos
> [2017-01-15 23:04:32] Registering accessory 'homebridge-sonos.Sonos'
> [2017-01-15 23:04:32] ---
> [2017-01-15 23:04:32] Loaded plugin: homebridge-thinkingcleaner
> [2017-01-15 23:04:32] Registering accessory 'homebridge-thinkingcleaner.Roomba'
> [2017-01-15 23:04:32] ---
> [2017-01-15 23:04:34] Loaded plugin: homebridge-vera
> VeraLink initializing
> [2017-01-15 23:04:34] Registering platform 'homebridge-veralink.Vera'
> [2017-01-15 23:04:34] ---
> [2017-01-15 23:04:34] Loaded config.json with 8 accessories and 5 platforms.
> [2017-01-15 23:04:34] ---
> [2017-01-15 23:04:34] Loading 5 platforms...
> [2017-01-15 23:04:34] [netatmo platform] Initializing netatmo platform...
> [2017-01-15 23:04:34] [netatmo platform] Creating NetatmoPlatform...
> [2017-01-15 23:04:34] [Harmony Wohnzimmer] Initializing HarmonyHub platform...
> [2017-01-15 23:04:34] Initializing LiftMaster2 platform...
> [2017-01-15 23:04:34] [Vera] Initializing Vera platform...
> [2017-01-15 23:04:34] Initializing People platform...
> Process Device 27: Haustüre
> [2017-01-15 23:04:35] [Vera] Initializing platform accessory 'Haustüre'...
> [2017-01-15 23:04:36] [netatmo platform] refreshing weatherstation device 70:ee:50:19:e5:fa (Lichtenauer Straße Wohnzimmer)
> [2017-01-15 23:04:36] [netatmo platform] refreshing weatherstation module 02:00:00:19:b9:20 (Lichtenauer Straße Garten)
> [2017-01-15 23:04:36] [netatmo platform] refreshing weatherstation module 03:00:00:02:8e:6c (Lichtenauer Straße Schlafzimmer)
> [2017-01-15 23:04:36] [netatmo platform] refreshing welcome device 5694e6c2cce37c4875834d91 (Kamera Wohnraum)
> [2017-01-15 23:04:36] [netatmo platform] Initializing platform accessory 'Lichtenauer Straße Wohnzimmer'...
> [2017-01-15 23:04:36] [netatmo platform] Initializing platform accessory 'Lichtenauer Straße Garten'...
> [2017-01-15 23:04:36] [netatmo platform] Initializing platform accessory 'Lichtenauer Straße Schlafzimmer'...
> [2017-01-15 23:04:36] [netatmo platform] Initializing platform accessory 'Kamera Wohnraum'...
> ^C[2017-01-15 23:04:58] Got SIGINT, shutting down Homebridge...
> pi@homebridge:~ $ sudo journalctl -e
> Jan 15 23:02:36 homebridge sshd[1485]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:02:39 homebridge sudo[1380]: pam_unix(sudo:session): session closed for user root
> Jan 15 23:02:42 homebridge sudo[1495]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -e
> Jan 15 23:02:42 homebridge sudo[1495]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
> Jan 15 23:02:56 homebridge sshd[1502]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:02:58 homebridge sshd[1502]: Failed password for root from 112.85.42.110 port 27563 ssh2
> Jan 15 23:03:00 homebridge sshd[1502]: Failed password for root from 112.85.42.110 port 27563 ssh2
> Jan 15 23:03:03 homebridge sshd[1502]: Failed password for root from 112.85.42.110 port 27563 ssh2
> Jan 15 23:03:03 homebridge sshd[1502]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 23:03:03 homebridge sshd[1502]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:03:04 homebridge sudo[1495]: pam_unix(sudo:session): session closed for user root
> Jan 15 23:03:10 homebridge sshd[1511]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:03:12 homebridge sshd[1511]: Failed password for root from 112.85.42.110 port 46593 ssh2
> Jan 15 23:03:15 homebridge sshd[1511]: Failed password for root from 112.85.42.110 port 46593 ssh2
> Jan 15 23:03:17 homebridge sshd[1511]: Failed password for root from 112.85.42.110 port 46593 ssh2
> Jan 15 23:03:18 homebridge sshd[1511]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 23:03:18 homebridge sshd[1511]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:03:32 homebridge dhcpcd[334]: eth0: Router Advertisement from fe80::3681:c4ff:fed0:1c71
> Jan 15 23:03:33 homebridge dhcpcd[334]: eth0: Router Advertisement from fe80::3681:c4ff:fed0:1c71
> Jan 15 23:03:36 homebridge dhcpcd[334]: eth0: Router Advertisement from fe80::3681:c4ff:fed0:1c71
> Jan 15 23:03:40 homebridge dhcpcd[334]: eth0: Router Advertisement from fe80::3681:c4ff:fed0:1c71
> Jan 15 23:04:11 homebridge sshd[1582]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:04:13 homebridge sshd[1582]: Failed password for root from 112.85.42.110 port 33700 ssh2
> Jan 15 23:04:15 homebridge sshd[1582]: Failed password for root from 112.85.42.110 port 33700 ssh2
> Jan 15 23:04:18 homebridge sshd[1582]: Failed password for root from 112.85.42.110 port 33700 ssh2
> Jan 15 23:04:18 homebridge sshd[1582]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 23:04:18 homebridge sshd[1582]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:04:19 homebridge node[1587]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
> Jan 15 23:04:19 homebridge node[1587]: *** WARNING *** Please fix your application to use the native API of Avahi!
> Jan 15 23:04:19 homebridge node[1587]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
> Jan 15 23:04:19 homebridge node[1587]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer
> Jan 15 23:04:19 homebridge node[1587]: *** WARNING *** Please fix your application to use the native API of Avahi!
> Jan 15 23:04:19 homebridge node[1587]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
> Jan 15 23:04:38 homebridge sshd[1612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:04:40 homebridge sshd[1612]: Failed password for root from 112.85.42.110 port 23446 ssh2
> Jan 15 23:04:43 homebridge sshd[1612]: Failed password for root from 112.85.42.110 port 23446 ssh2
> Jan 15 23:04:46 homebridge sshd[1612]: Failed password for root from 112.85.42.110 port 23446 ssh2
> Jan 15 23:04:46 homebridge sshd[1612]: Received disconnect from 112.85.42.110: 11: [preauth]
> Jan 15 23:04:46 homebridge sshd[1612]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:04:56 homebridge sshd[1620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.110 user=root
> Jan 15 23:04:58 homebridge sshd[1620]: Failed password for root from 112.85.42.110 port 35516 ssh2
> Jan 15 23:05:00 homebridge sshd[1620]: Failed password for root from 112.85.42.110 port 35516 ssh2
> Jan 15 23:05:02 homebridge sudo[1624]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -e
> Jan 15 23:05:02 homebridge sudo[1624]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
This is all what the Logs putting out... :-(
Homebridge stops starting after a while... I wait for 60-120 sec then I press ctrl C thats all what I can do and type sudo journalctl -b and thats is all what comes around...
try to remove this line completely from you config:
"cacheDirectory": "./.node-persist/storage",
it sure did solve my problem
try to remove this line completely from you config: "cacheDirectory": "./.node-persist/storage", it sure did solve my problem
Will this give other problems?
No the Plugin works great, but only because I#m intressted in...
For which function is "cacheDirectory": "./.node-persist/storage", for?
You can configure the location where the data to store, i.e. Last successful ping.
Is this useful, except for error searching. Should I change the directory to a path that work instead of the default configuration, which doesn't work on my setup?
In another plugin of mine, there was an issue that someone couldnt store it in the default location due to permissions. That is why it is configureable.
Wehre get the Data stored if the line is deleted or didn't get the data stored at all, when the line is deleted?
One more question:
In the config.json is the line ignoreReEnterExitSeconds if i right I can setup a delay time for fire the trigger, gut in the explanation is not clear, is the parameter for the delay in minutes or seconds.
optional, in minutes, default: 0, if set to 0 than every enter/exit will trigger state change otherwise the state will only change if no re-enter/exit occurs in specified number of seconds
And if I right, I can chose the trigger delay in the header global for all people and in the people settings for each people seperatly. Right?
Sorry for all the questions, but, this plugin is the Killer-Feature for homekit:-)
a) Default is here: HomebridgeAPI.user.persistPath() No clue where this is, it was defined as default before.
b) It is in seconds.
c) true
Grat, thanks for your Help!
So, now i ran some tests I've set ignoreReEnterExitSeconds to 180 sec.
One last Question :-)
And after the test it seems, that the delay only is activated by leaving my location. I have installed and configured the locative app which works fine and after the App triggers leaving my Home-Zone I can see the configured delay of 180 sec before the trigger fires.
But when I'm arriving at home, the trigger fires immediately when my phone get a connection to my Wifi. There is no delay at all. It's that right? Or should there be a delay too? Or is the delay only for exiting an reentry?
The reason I ask: I want one Trigger which activate several things (lights, TV,...) when the first person arrive at home. But this trigger should not be activated by the people plugin, This trigger should be activated by my motion sensor which is near the front door. The people plugin should only garant, that the trigger only fires when noone is at home.
In this use case I can enclosure, the delay of my Wifi recognize my iPhone. Sometimes my iPhone is recognized before I open my door (what would work for me) But sometimes it take a while until my Phone is recognized by my Wifi, and in this case I stand in my dark house and have to wait until, my Phone connects to my Wifi.
So it would be great when the trigger noone home is delayed for 180 sec so that the motion sensor could fire the trigger every time when the front door gets opened by the first person comes home.
Is this possible, or is the delay only by leaving my home?
The setting is just for ReEnter with the specified time and only for webhooks. This was done in case you use beacons and this issue occurs. Its not a general delay.
Thanks for the answer.
Because of the inconstancy of the connection from my Phone to my Wifi. Sometimes it connect correct when I'm close to my front door , so that all actions are started when im entering my house. But sometimes, the connection to my Wifi happens a while after entering my House. So when its dark outside I stand in the dark and have to wait until my Phone connect to my Wifi.
So for me it would be great if the motion Sensor fire the trigger, when noone is at home.
But if that isn't possible I have to think about the geofence option of the people plugin.
why not using GeoFence when entering home area?
also, making what you want is totally possible, just set it on the "Eve" app or "Hesperus", There you can set exactly: IF (trigger) motion sensor is triggered AND (condition) NoOne is "Home" Then your scene.
@nitaybz: In think his problem is, that sometime people plugin is triggered before motion sensor and sometimes the other was around.
@benzman81 and therefor using geofence is the best solution to handle it. then the diameter of the geofence ring can be set to the right position where you want the automation to trigger (after testing different positions for days (: ).
anyway I just mentioned it cause @andijegg said:
So for me it would be great if the motion Sensor fire the trigger, when noone is at home.