Autor Thema: Modul: 98_livetrackingconn.pm - zur Anbindung von livetracking an RESIDENTS  (Gelesen 12272 mal)

Offline binford6000

  • Tester
  • Hero Member
  • ****
  • Beiträge: 1255
  • 🏠⚙️💡🛠📱
Am Ende von Zeile 19 fehlt ein Leerzeichen vor dem "
Wer weiß wie das verschwunden ist

So ein Leerzeichen kann schon leicht verloren gehen...  ;D
Proxmox mit: nextcloud, fhem, pihole, docker, bitwarden, deconz, TasmoAdmin
fhem mit: deconz, SONOS, alexa-fhem, homebridge, TelegramBot mit msgDialog, livetracking
Testumgebung: docker pull fhem/fhem

Offline klausw

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1928
So ein Leerzeichen kann schon leicht verloren gehen...  ;D
ist korrigiert
RasPi B v2 mit FHEM 18B20 über 1Wire, LED PWM Treiber über I2C, Luchtdruck-, Feuchtesensor und ein paar Schalter/LED\'s zum testen
Module: RPI_GPIO, RPII2C, I2C_EEPROM, I2C_MCP23008, I2C_MCP23017, I2C_MCP342x, I2C_PCA9532, I2C_PCF8574, I2C_SHT21, I2C_BME280

Offline binford6000

  • Tester
  • Hero Member
  • ****
  • Beiträge: 1255
  • 🏠⚙️💡🛠📱
ist korrigiert

Danke! Ich war so frei und hab eins von meinen Leerzeichen eingefügt  ;)
VG Sebastian
Proxmox mit: nextcloud, fhem, pihole, docker, bitwarden, deconz, TasmoAdmin
fhem mit: deconz, SONOS, alexa-fhem, homebridge, TelegramBot mit msgDialog, livetracking
Testumgebung: docker pull fhem/fhem

Offline binford6000

  • Tester
  • Hero Member
  • ****
  • Beiträge: 1255
  • 🏠⚙️💡🛠📱
Moin Klaus,
jetzt scheint dir ein "m" abhanden gekommen zu sein - aber dafür hat sich ein "l" dazu gesellt  ;D
98_livetrackingconn.pl
Mit der letzten Verison habe ich wieder Stacktrace Meldungen im Log bei enter/leave einer Zone:
2019.09.21 08:00:34 1:  readingsUpdate(iphone5SE,place,home) missed to call readingsBeginUpdate first.
2019.09.21 08:00:34 1:  stacktrace:
2019.09.21 08:00:34 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1074)
2019.09.21 08:00:34 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.21 08:00:34 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (939)
2019.09.21 08:00:34 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (579)
2019.09.21 08:00:34 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.21 08:00:34 1:      main::CallFn                        called by fhem.pl (750)
2019.09.21 08:00:34 1:  readingsUpdate(iphone5SE,zone_0,active) missed to call readingsBeginUpdate first.
2019.09.21 08:00:34 1:  stacktrace:
2019.09.21 08:00:34 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1078)
2019.09.21 08:00:34 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.21 08:00:34 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (939)
2019.09.21 08:00:34 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (579)
2019.09.21 08:00:34 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.21 08:00:34 1:      main::CallFn                        called by fhem.pl (750)
2019.09.21 08:00:34 1:  readingsUpdate(iphone5SE,trigger,region) missed to call readingsBeginUpdate first.
2019.09.21 08:00:34 1:  stacktrace:
2019.09.21 08:00:34 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1103)
2019.09.21 08:00:34 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.21 08:00:34 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (939)
2019.09.21 08:00:34 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (579)
2019.09.21 08:00:34 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.21 08:00:34 1:      main::CallFn                        called by fhem.pl (750)
2019.09.21 08:00:34 1:  readingsUpdate(iphone5SE,distance,0) missed to call readingsBeginUpdate first.
2019.09.21 08:00:34 1:  stacktrace:
2019.09.21 08:00:34 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1147)
2019.09.21 08:00:34 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.21 08:00:34 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (939)
2019.09.21 08:00:34 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (579)
2019.09.21 08:00:34 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.21 08:00:34 1:      main::CallFn                        called by fhem.pl (750)

Irgendwas war doch da...  ???
EDIT: Hier gefunden:
https://forum.fhem.de/index.php/topic,93565.msg918444.html#msg918444

Die kommen aber von livetracking...  :o

VG Sebastian
« Letzte Änderung: 21 September 2019, 09:16:48 von binford6000 »
Proxmox mit: nextcloud, fhem, pihole, docker, bitwarden, deconz, TasmoAdmin
fhem mit: deconz, SONOS, alexa-fhem, homebridge, TelegramBot mit msgDialog, livetracking
Testumgebung: docker pull fhem/fhem

Offline binford6000

  • Tester
  • Hero Member
  • ****
  • Beiträge: 1255
  • 🏠⚙️💡🛠📱
Ich habe noch eine Frage:
goneradius funktioniert doch mit leavetounderway zusammen oder?

VG Sebastian
Proxmox mit: nextcloud, fhem, pihole, docker, bitwarden, deconz, TasmoAdmin
fhem mit: deconz, SONOS, alexa-fhem, homebridge, TelegramBot mit msgDialog, livetracking
Testumgebung: docker pull fhem/fhem

Offline klausw

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1928
Ich habe noch eine Frage:
goneradius funktioniert doch mit leavetounderway zusammen oder?

Es sollte auf alle Fälle.

jetzt scheint dir ein "m" abhanden gekommen zu sein - aber dafür hat sich ein "l" dazu gesellt  ;D
98_livetrackingconn.pl

es hat ne Weile gedauert bis ich es gesehen habe... oh mann  :o


Mit der letzten Verison habe ich wieder Stacktrace Meldungen im Log bei enter/leave einer Zone:

Irgendwas war doch da...  ???
EDIT: Hier gefunden:
https://forum.fhem.de/index.php/topic,93565.msg918444.html#msg918444

Die kommen aber von livetracking...  :o

Ja, kommen sie aber der Auslöser scheint ja im livetrackingconn Modul zu liegen.
Das Ganze überblicke ich noch nicht.
Hast Du noch die Version, bei der keine Stacktrace Meldung kam?
Dann würde ich mit mal die Unterschiede anschauen.
RasPi B v2 mit FHEM 18B20 über 1Wire, LED PWM Treiber über I2C, Luchtdruck-, Feuchtesensor und ein paar Schalter/LED\'s zum testen
Module: RPI_GPIO, RPII2C, I2C_EEPROM, I2C_MCP23008, I2C_MCP23017, I2C_MCP342x, I2C_PCA9532, I2C_PCF8574, I2C_SHT21, I2C_BME280

Offline binford6000

  • Tester
  • Hero Member
  • ****
  • Beiträge: 1255
  • 🏠⚙️💡🛠📱
Zitat
Hast Du noch die Version, bei der keine Stacktrace Meldung kam?
Dann würde ich mit mal die Unterschiede anschauen.

Nee die hab ich nicht mehr. Aber mit der aktuellen Version habe ich die Meldungen auch nicht mehr im Log.
Scheint also was anderes gewesen zu sein.

VG Sebastian
« Letzte Änderung: 25 September 2019, 07:52:43 von binford6000 »
Proxmox mit: nextcloud, fhem, pihole, docker, bitwarden, deconz, TasmoAdmin
fhem mit: deconz, SONOS, alexa-fhem, homebridge, TelegramBot mit msgDialog, livetracking
Testumgebung: docker pull fhem/fhem

Offline binford6000

  • Tester
  • Hero Member
  • ****
  • Beiträge: 1255
  • 🏠⚙️💡🛠📱
Moin Klaus,
vorhin habe ich wieder die stacktrace Meldungen im Log bemerkt:
livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:33:23 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:35:08 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:35:10 1:  readingsUpdate(iphone5se,zone_0,inactive) missed to call readingsBeginUpdate first.
2019.09.25 06:35:10 1:  stacktrace:
2019.09.25 06:35:10 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1087)
2019.09.25 06:35:10 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 06:35:10 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 06:35:10 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 06:35:10 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 06:35:10 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 06:35:10 1:  readingsUpdate(iphone5se,trigger,region) missed to call readingsBeginUpdate first.
2019.09.25 06:35:10 1:  stacktrace:
2019.09.25 06:35:10 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1103)
2019.09.25 06:35:10 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 06:35:10 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 06:35:10 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 06:35:10 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 06:35:10 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 06:35:10 1:  readingsUpdate(iphone5se,distance,0) missed to call readingsBeginUpdate first.
2019.09.25 06:35:10 1:  stacktrace:
2019.09.25 06:35:10 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1147)
2019.09.25 06:35:10 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 06:35:10 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 06:35:10 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 06:35:10 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 06:35:10 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 06:35:11 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:35:12 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:40:09 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:40:10 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:40:10 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:45:09 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:50:11 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 06:55:11 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:00:12 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:07:32 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:12:33 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:17:34 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:22:35 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:27:05 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:27:05 1:  readingsUpdate(iphone5se,place,xxxxxxx) missed to call readingsBeginUpdate first.
2019.09.25 07:27:05 1:  stacktrace:
2019.09.25 07:27:05 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1074)
2019.09.25 07:27:05 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 07:27:05 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 07:27:05 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 07:27:05 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 07:27:05 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 07:27:05 1:  readingsUpdate(iphone5se,zone_1,active) missed to call readingsBeginUpdate first.
2019.09.25 07:27:05 1:  stacktrace:
2019.09.25 07:27:05 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1078)
2019.09.25 07:27:05 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 07:27:05 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 07:27:05 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 07:27:05 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 07:27:05 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 07:27:05 1:  readingsUpdate(iphone5se,trigger,region) missed to call readingsBeginUpdate first.
2019.09.25 07:27:05 1:  stacktrace:
2019.09.25 07:27:05 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1103)
2019.09.25 07:27:05 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 07:27:05 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 07:27:05 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 07:27:05 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 07:27:05 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 07:27:05 1:  readingsUpdate(iphone5se,distance,39) missed to call readingsBeginUpdate first.
2019.09.25 07:27:05 1:  stacktrace:
2019.09.25 07:27:05 1:      main::readingsBulkUpdate            called by ./FHEM/98_livetracking.pm (1147)
2019.09.25 07:27:05 1:      main::livetracking_ParseOwnTracks   called by ./FHEM/98_livetracking.pm (1571)
2019.09.25 07:27:05 1:      main::livetracking_Webcall          called by ./FHEM/01_FHEMWEB.pm (940)
2019.09.25 07:27:05 1:      main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (580)
2019.09.25 07:27:05 1:      main::FW_Read                       called by fhem.pl (3752)
2019.09.25 07:27:05 1:      main::CallFn                        called by fhem.pl (750)
2019.09.25 07:27:06 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian
2019.09.25 07:27:39 3:  livetrackingcon: Found matching UUID at ROOMMATE device rr_Sebastian

Leavetounderway scheint er zu ignorieren - zumindest habe ich keinen Push nachricht bzw. Logeintrag dazu.
Hier mal die devices:

livetrackingconn:
Internals:
   FUUID      5d839ae8-f33f-0308-a4b4-d28f76724b99450b
   FVERSION   98_livetrackingconn.pm:?/2019-09-21
   NAME       livetrackingcon
   NOTIFYDEV  TYPE=livetracking
   NR         375
   NTFY_ORDER 999-livetrackingcon
   ROOMMATES  rr_Sebastian
   STATE      Initialized
   TYPE       livetrackingconn
Attributes:
   devStateIcon .*:ios-on-blue
   goneradius 100000
   group      Standort
   icon       location
   leavetounderway 1
   livetrackingDevice TYPE=livetracking
   room       90_System->91_Schnittstellen

iphone5se:
Internals:
   CHANGED   
   FUUID      5d864070-f33f-0308-1438-050526090524e2a4
   FVERSION   98_livetracking.pm:0.192570/2019-04-24
   NAME       iphone5se
   NOTIFYDEV  owntracks
   NR         382
   NTFY_ORDER 999-iphone5se
   STATE      Zone: home
   TYPE       livetracking
   READINGS:
     2019-09-25 07:27:38   accuracy        65
     2019-09-25 07:27:05   address         
55128 Mainz
Deutschland
     2019-09-25 07:27:38   altitude        140
     2019-09-25 07:27:38   batteryPercent  97
     2019-09-25 07:27:38   batteryState    ok
     2019-09-25 07:27:38   connection      mobile
     2019-09-25 07:27:38   distance        39
     2019-09-25 07:22:34   heading         122
     2019-09-25 07:27:38   id              SE
     2019-09-25 07:27:38   latitude        49.1234
     2019-09-25 07:27:38   location        49.1234,8.1234
     2019-09-25 07:27:38   longitude       8.1234
     2019-09-24 21:53:02   place           home
     2019-09-25 07:27:38   trigger         automatic
     2019-09-25 07:22:34   velocity        109
     2019-09-25 07:27:38   zone_0          inactive
     2019-09-25 07:27:38   zone_1          active
     2019-09-25 07:27:38   zone_2          inactive
     2019-09-25 07:27:38   zone_3          inactive
     2019-09-25 07:27:38   zone_4          inactive
   helper:
     lastOwnTracks 1569389258
Attributes:
   addressLanguage de
   addressReading 1
   batteryWarning 15
   group      Standort
   home       50.1234,8.1234
   icon       location
   osmandServer 1
   room       90_System->91_Schnittstellen
   roundAltitude 10
   roundDistance 0.5
   stateFormat Zone: place
   userattr   goneradius homeradius leavetounderway:0,1 wayhomeradius
   zonename_0 home
   zonename_1 vvvv
   zonename_2 wwww
   zonename_3 xxxx
   zonename_4 yyyy


VG Sebastian
« Letzte Änderung: 25 September 2019, 08:01:31 von binford6000 »
Proxmox mit: nextcloud, fhem, pihole, docker, bitwarden, deconz, TasmoAdmin
fhem mit: deconz, SONOS, alexa-fhem, homebridge, TelegramBot mit msgDialog, livetracking
Testumgebung: docker pull fhem/fhem

Offline pink99panther

  • Full Member
  • ***
  • Beiträge: 345
Hallo ihr Lieben,

bin bei der Suche nach einer Alternative für Egigeozone auf diese tolle Lösung gestossen.
Leider bekomme ich livetrackingconn (aus Post 1 hier) nicht ans laufen. Mein ROOMMATE erhält keine Änderung.
Wäre schön, wenn mir mal einer einen Schubs in die richtige Richtung geben könnte.

Und hier mein Devices:
Internals:
   CFGFN     
   CHANGED   
   FUUID      5e2731a1-f33f-f73e-9edd-2c4d6d92ff889b23
   NAME       mylivetrck
   NOTIFYDEV  MQTT2_OwnTracks
   NR         281
   NTFY_ORDER 999-livetracking
   STATE      5X.XXXXX,8.XXXXX
   TYPE       livetracking
   READINGS:
     2020-01-22 08:54:56   accuracy        15
     2020-01-22 08:54:56   altitude        180
     2020-01-22 08:54:56   batteryPercent  72
     2020-01-22 08:54:56   batteryState    ok
     2020-01-22 08:54:56   connection      wifi
     2020-01-22 08:54:56   distance        0
     2020-01-22 08:54:56   id              P1
     2020-01-22 08:54:56   latitude        5X.XXXXX
     2020-01-22 08:54:56   location        5X.XXXXX,8.XXXXX
     2020-01-22 08:54:56   longitude       8.XXXXX
     2020-01-22 08:54:56   trigger         ping
     2020-01-22 08:54:56   velocity        0
     2020-01-22 08:54:56   zone_0          active
   helper:
     lastOwnTracks 1579679696
Attributes:
   addressReading 1
   batteryWarning 15
   home       5X.XXXXX,8.XXXXX
   owntracksDevice MQTT2_OwnTracks
   room       Anwesenheit
   roundAltitude 10
   roundDistance 0.5
   stateFormat location
   zonename_0 HomeNdn
   
   Internals:
   DEF        OwnManfred
   FUUID      5e25da44-f33f-f73e-038a-47a8f2817451be92
   NAME       livetrackingcon
   NOTIFYDEV  TYPE=livetracking
   NR         215
   NTFY_ORDER 999-livetrackingcon
   ROOMMATES  Gabi,Manfred,OwnManfred
   STATE      Initialized
   TYPE       livetrackingconn
Attributes:
   livetrackingDevice TYPE=livetracking
   room       Anwesenheit
   verbose    3
   
   Internals:
   AUTOGONE   1579734326
   DEF        Bewohner
   DURATIONTIMER 1579681772.68555
   FUUID      5e26a727-f33f-f73e-d482-eb6c13eb72511d60
   FVERSION   20_ROOMMATE.pm:0.195330/2019-06-02
   NAME       OwnManfred
   NOTIFYDEV  global,
   NR         217
   NTFY_ORDER 50-OwnManfred
   READY      1
   RESIDENTGROUPS Bewohner
   STATE      absent
   SUBTYPE    adult
   TYPE       ROOMMATE
   READINGS:
     2020-01-22 09:28:32   durTimerAbsence 21:23:06
     2020-01-22 09:28:32   durTimerAbsence_cr 1283
     2020-01-21 08:24:38   durTimerPresence 00:00:00
     2020-01-21 08:24:38   durTimerPresence_cr 0
     2020-01-21 08:24:38   durTimerSleep   00:00:00
     2020-01-21 08:24:38   durTimerSleep_cr 0
     2020-01-21 12:05:26   lastDeparture   2020-01-21 12:05:26
     2020-01-21 12:05:26   lastLocation    undefined
     2020-01-21 12:05:26   lastState       initialized
     2020-01-21 12:05:26   location        underway
     2020-01-21 12:05:26   presence        absent
     2020-01-21 12:05:26   state           absent
     2020-01-21 12:05:26   wayhome         0
   TIMER:
     OwnManfred_AutoGone:
       HASH       OwnManfred
       MODIFIER   AutoGone
       NAME       OwnManfred_AutoGone
     OwnManfred_DurationTimer:
       HASH       OwnManfred
       MODIFIER   DurationTimer
       NAME       OwnManfred_DurationTimer
Attributes:
   alias      OwnManfred
   devStateIcon .*home:user_available:absent .*absent:user_away:home .*gone:user_ext_away:home .*gotosleep:scene_toilet:asleep .*asleep:scene_sleeping:awoken .*awoken:scene_sleeping_alternat:home .*:user_unknown:home
   group      Familie
   icon       people_sensor
   room       Residents
   rr_geofenceUUIDs mylivetrck
   rr_locationHome HomeNdn
   rr_realname group
   sortby     1
   webCmd     state

LG
Manfred

EDIT1: noch ein Logauszug mit Verbose5:
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: latitude: 5X.XXXXX
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: longitude: 8.XXXXX
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: location: 50.XXXXX,8.XXXXXX
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: altitude: 180
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: id: P1
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: accuracy: 15
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: velocity: 0
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: batteryPercent: 71
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: batteryState: ok
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: connection: wifi
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: trigger: ping
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: zone_0: active
2020.01.22 10:35:43 5: livetrackingcon: Notify from mylivetrck: distance: 0
2020.01.22 10:35:43 4: livetrackingcon: Notify from mylivetrck: distance: 0 -> using it
2020.01.22 10:35:43 5: livetrackingcon : Checking r*_geofenceUUIDs for Gabi
2020.01.22 10:35:43 5: livetrackingcon : Checking r*_geofenceUUIDs for Manfred
2020.01.22 10:35:43 5: livetrackingcon : Checking r*_geofenceUUIDs for OwnManfred
2020.01.22 10:35:43 3: livetrackingcon: Found matching UUID at ROOMMATE device OwnManfred
« Letzte Änderung: 22 Januar 2020, 11:11:07 von pink99panther »

Offline klausw

  • Developer
  • Hero Member
  • ****
  • Beiträge: 1928
Hallo ihr Lieben,

bin bei der Suche nach einer Alternative für Egigeozone auf diese tolle Lösung gestossen.
Leider bekomme ich livetrackingconn (aus Post 1 hier) nicht ans laufen. Mein ROOMMATE erhält keine Änderung.
Wäre schön, wenn mir mal einer einen Schubs in die richtige Richtung geben könnte.


habe Deinen Post übersehen...

Auf die schnelle finde ich keinen Fehler.
Ich nutze derzeit nur die Radiusfunktion.
Ich schaue es mir die Tage mal an.

Klaus
RasPi B v2 mit FHEM 18B20 über 1Wire, LED PWM Treiber über I2C, Luchtdruck-, Feuchtesensor und ein paar Schalter/LED\'s zum testen
Module: RPI_GPIO, RPII2C, I2C_EEPROM, I2C_MCP23008, I2C_MCP23017, I2C_MCP342x, I2C_PCA9532, I2C_PCF8574, I2C_SHT21, I2C_BME280

 

decade-submarginal