Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter fb-checkpresence v1.1.x

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Test Adapter fb-checkpresence v1.1.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jukus100 @cb1 last edited by

      Hi,

      bei mir schmiert der Adapter andauernd nur noch ab. Verbindung wird kurzzeitig grün, und danach ist er wieder tot.

      fb-checkpresence.0	2021-06-09 10:52:57.029	info	(26921) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      fb-checkpresence.0	2021-06-09 10:52:57.027	info	(26921) terminating
      fb-checkpresence.0	2021-06-09 10:52:56.524	info	(26921) cleaned everything up ...
      fb-checkpresence.0	2021-06-09 10:52:56.521	info	(26921) Got terminate signal TERMINATE_YOURSELF
      fb-checkpresence.0	2021-06-09 10:52:56.315	warn	(26921) onReady: Fb init: getServices: Error timeout of 6000ms exceeded
      fb-checkpresence.0	2021-06-09 10:52:49.663	info	(26921) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.1, js-controller: 3.2.16
      fb-checkpresence.0	2021-06-09 10:51:51.146	info	(25914) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      fb-checkpresence.0	2021-06-09 10:51:51.142	info	(25914) terminating
      fb-checkpresence.0	2021-06-09 10:51:50.640	info	(25914) cleaned everything up ...
      fb-checkpresence.0	2021-06-09 10:51:50.636	info	(25914) Got terminate signal TERMINATE_YOURSELF
      fb-checkpresence.0	2021-06-09 10:51:50.529	warn	(25914) onReady: Fb init: checkServices: checkService Error service X_AVM-DE_HostFilter-DisallowWANAccessByIP is not supported! Can not find service file! Feature is deactivated
      fb-checkpresence.0	2021-06-09 10:51:17.645	error	(25914) onMessage: Cannot read property 'GETPATH' of null
      fb-checkpresence.0	2021-06-09 10:51:16.556	info	(25914) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.1, js-controller: 3.2.16
      fb-checkpresence.0	2021-06-09 10:51:07.877	info	(25421) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      fb-checkpresence.0	2021-06-09 10:51:07.874	info	(25421) terminating
      fb-checkpresence.0	2021-06-09 10:51:07.372	info	(25421) cleaned everything up ...
      fb-checkpresence.0	2021-06-09 10:51:07.369	info	(25421) Got terminate signal TERMINATE_YOURSELF
      fb-checkpresence.0	2021-06-09 10:51:07.207	warn	(25421) onReady: Fb init: checkServices: checkService Error service X_AVM-DE_HostFilter-DisallowWANAccessByIP is not supported! Can not find service file! Feature is deactivated
      fb-checkpresence.0	2021-06-09 10:50:40.051	error	(25421) onMessage: Cannot read property 'GETPATH' of null
      fb-checkpresence.0	2021-06-09 10:50:36.315	info	(25421) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.1, js-controller: 3.2.16
      fb-checkpresence.0	2021-06-09 10:50:30.350	warn	(25340) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
      fb-checkpresence.0	2021-06-09 10:50:30.243	error	(25340) adapter disabled
      fb-checkpresence.0	2021-06-09 10:50:24.271	info	(25068) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      fb-checkpresence.0	2021-06-09 10:50:24.268	info	(25068) terminating
      fb-checkpresence.0	2021-06-09 10:50:23.766	info	(25068) cleaned everything up ...
      fb-checkpresence.0	2021-06-09 10:50:23.762	info	(25068) Got terminate signal TERMINATE_YOURSELF
      fb-checkpresence.0	2021-06-09 10:50:04.935	info	(25068) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.1, js-controller: 3.2.16
      
      afuerhoff 1 Reply Last reply Reply Quote 0
      • afuerhoff
        afuerhoff Developer @jukus100 last edited by afuerhoff

        @jukus100
        Ist ein bekannter Fehler der mit der 1.1.5 behoben ist. Ist aber noch nicht im Stable.
        EDIT: Version müsste in Kürze im Stable sein.

        J 1 Reply Last reply Reply Quote 0
        • J
          jukus100 @afuerhoff last edited by

          @afuerhoff krieg immer noch ne ähnliche Fehlermeldung auch mit 1.1.5.

          
          fb-checkpresence.0	2021-06-10 15:30:10.867	error	(14313) onMessage: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
          fb-checkpresence.0	2021-06-10 15:30:10.673	debug	(14313) loop family ends after 6,157389090 s
          fb-checkpresence.0	2021-06-10 15:30:08.822	debug	(14313) system.adapter.admin.0: logging true
          fb-checkpresence.0	2021-06-10 15:30:03.652	info	(14313) state fb-checkpresence.0.reconnect changed: false (ack = true)
          fb-checkpresence.0	2021-06-10 15:30:03.610	info	(14313) state fb-checkpresence.0.reboot changed: false (ack = true)
          fb-checkpresence.0	2021-06-10 15:30:03.515	info	(14313) loop successfully started
          fb-checkpresence.0	2021-06-10 15:30:03.512	info	(14313) states successfully subscribed
          fb-checkpresence.0	2021-06-10 15:30:03.509	warn	(14313) infoNoFamilyMembers: no family members defined! Objects are not created!
          fb-checkpresence.0	2021-06-10 15:30:03.500	info	(14313) createGlobalObjects finished successfully
          fb-checkpresence.0	2021-06-10 15:30:02.720	warn	(14313) The state "devices" will not longer exist in a future version. Please use "fb-devices.count" instead!
          fb-checkpresence.0	2021-06-10 15:30:02.719	warn	(14313) The state "activeDevices" will not longer exist in a future version. Please use "fb-devices.active" instead!
          fb-checkpresence.0	2021-06-10 15:30:02.719	warn	(14313) The state "blacklist" will not longer exist in a future version. Please use "blacklist.presence" instead!
          fb-checkpresence.0	2021-06-10 15:30:02.718	warn	(14313) The state "guest" will not longer exist in a future version. Please use "guest.presence" instead!
          fb-checkpresence.0	2021-06-10 15:30:02.714	warn	(14313) You should then manually delete the old states!
          fb-checkpresence.0	2021-06-10 15:30:02.713	warn	(14313) In an future version some states are not more existent. Please use compatibility = false to switch to the new handling of the states!
          fb-checkpresence.0	2021-06-10 15:30:02.694	info	(14313) Layer3Forwarding1-GetDefaultConnectionService is supported
          fb-checkpresence.0	2021-06-10 15:30:02.693	info	(14313) LANConfigSecurity1-X_AVM-DE_GetCurrentUser is supported
          fb-checkpresence.0	2021-06-10 15:30:02.692	info	(14313) WANPPPConnection1-ForceTermination is supported
          fb-checkpresence.0	2021-06-10 15:30:02.690	info	(14313) DeviceConfig1-Reboot is supported
          fb-checkpresence.0	2021-06-10 15:30:02.689	info	(14313) DeviceInfo1-GetInfo is supported
          fb-checkpresence.0	2021-06-10 15:30:02.688	info	(14313) WLANConfiguration3-GetSecurityKeys is supported
          fb-checkpresence.0	2021-06-10 15:30:02.687	info	(14313) WLANConfiguration3-GetInfo is supported
          fb-checkpresence.0	2021-06-10 15:30:02.686	info	(14313) WLANConfiguration3-SetEnable is supported
          fb-checkpresence.0	2021-06-10 15:30:02.685	info	(14313) WANIPConnection1-GetInfo is supported
          fb-checkpresence.0	2021-06-10 15:30:02.683	info	(14313) WANPPPConnection1-GetInfo is supported
          fb-checkpresence.0	2021-06-10 15:30:02.682	info	(14313) WANCommonInterfaceConfig1-GetCommonLinkProperties is supported
          fb-checkpresence.0	2021-06-10 15:30:02.681	info	(14313) DeviceInfo1-GetSecurityPort is supported
          fb-checkpresence.0	2021-06-10 15:30:02.680	info	(14313) Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is supported
          fb-checkpresence.0	2021-06-10 15:30:02.679	info	(14313) Hosts1-GetSpecificHostEntry is supported
          fb-checkpresence.0	2021-06-10 15:30:02.678	info	(14313) Hosts1-X_AVM-DE_GetMeshListPath is supported
          fb-checkpresence.0	2021-06-10 15:30:02.676	info	(14313) Hosts1-X_AVM-DE_GetHostListPath is supported
          fb-checkpresence.0	2021-06-10 15:30:02.675	info	(14313) configuration default connection: 1.WANIPConnection.1
          fb-checkpresence.0	2021-06-10 15:30:02.673	debug	(14313) configuration filter delay: 15
          fb-checkpresence.0	2021-06-10 15:30:02.672	debug	(14313) configuration guest info: true
          fb-checkpresence.0	2021-06-10 15:30:02.671	debug	(14313) configuration qr code: false
          fb-checkpresence.0	2021-06-10 15:30:02.670	debug	(14313) configuration ssl: true
          fb-checkpresence.0	2021-06-10 15:30:02.669	debug	(14313) configuration compatibility: true
          fb-checkpresence.0	2021-06-10 15:30:02.667	debug	(14313) configuration whitelist: true
          fb-checkpresence.0	2021-06-10 15:30:02.666	debug	(14313) configuration mesh info: false
          fb-checkpresence.0	2021-06-10 15:30:02.665	debug	(14313) configuration fb-devices false
          fb-checkpresence.0	2021-06-10 15:30:02.664	debug	(14313) configuration familymembers: []
          fb-checkpresence.0	2021-06-10 15:30:02.663	debug	(14313) configuration familymembers count: 0
          fb-checkpresence.0	2021-06-10 15:30:02.662	debug	(14313) configuration dateformat: <yyyy.mm.dd HH:MM:ss>
          fb-checkpresence.0	2021-06-10 15:30:02.660	debug	(14313) configuration history: <>
          fb-checkpresence.0	2021-06-10 15:30:02.659	debug	(14313) configuration user: <jk>
          fb-checkpresence.0	2021-06-10 15:30:02.656	info	(14313) start fb-checkpresence.0: FRITZ!Box 6490 Cable version: 141.07.12 ip-address: "fritz.box" - interval devices: 1 min. - interval members: 60 s
          ecovacs-deebot.0	2021-06-10 15:30:00.096	info	(8471) Start cleaning spot area(s): 1,4,5
          fb-checkpresence.0	2021-06-10 15:29:46.937	info	(14313) service X_AVM-DE_HostFilter-GetWANAccessByIP is not supported! Can not find service file! Feature is deactivated
          fb-checkpresence.0	2021-06-10 15:29:46.935	info	(14313) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is not supported! Can not find service file! Feature is deactivated
          fb-checkpresence.0	2021-06-10 15:29:20.737	debug	(14313) system.adapter.admin.0: logging false
          fb-checkpresence.0	2021-06-10 15:29:16.261	info	(14313) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.1, js-controller: 3.2.16
          fb-checkpresence.0	2021-06-10 15:29:15.662	debug	(14313) statesDB connected
          fb-checkpresence.0	2021-06-10 15:29:15.660	debug	(14313) States connected to redis: 127.0.0.1:9000
          fb-checkpresence.0	2021-06-10 15:29:15.633	debug	(14313) States create User PubSub Client
          fb-checkpresence.0	2021-06-10 15:29:15.630	debug	(14313) States create System PubSub Client
          fb-checkpresence.0	2021-06-10 15:29:15.606	debug	(14313) Redis States: Use Redis connection: 127.0.0.1:9000
          fb-checkpresence.0	2021-06-10 15:29:15.601	debug	(14313) objectDB connected
          fb-checkpresence.0	2021-06-10 15:29:15.579	debug	(14313) Objects connected to redis: 127.0.0.1:9001
          fb-checkpresence.0	2021-06-10 15:29:15.540	debug	(14313) Objects client initialize lua scripts
          fb-checkpresence.0	2021-06-10 15:29:15.537	debug	(14313) Objects create User PubSub Client
          fb-checkpresence.0	2021-06-10 15:29:15.533	debug	(14313) Objects create System PubSub Client
          fb-checkpresence.0	2021-06-10 15:29:15.518	debug	(14313) Objects client ready ... initialize now
          fb-checkpresence.0	2021-06-10 15:29:15.423	debug	(14313) Redis Objects: Use Redis connection: 127.0.0.1:9001
          host.raspberrypi	2021-06-10 15:29:13.109	info	instance system.adapter.fb-checkpresence.0 started with pid 14313
          fb-checkpresence.0	2021-06-10 15:30:08.822	debug	(14313) system.adapter.admin.0: logging true
          
          afuerhoff 1 Reply Last reply Reply Quote 0
          • afuerhoff
            afuerhoff Developer @jukus100 last edited by

            @jukus100
            Timeout kann schon mal vorkommen. Wenn ständig, dann Fritzbox neu booten.
            Hat nichts mit der anderen Meldung zu tun.

            1 Reply Last reply Reply Quote 0
            • S
              SaiBot1981 last edited by

              Moin, ich hab da mal einen Frage bezüglich rebooten. Kannst du evtl auch eine Funktion einbauen durch die Man die FritzRepeater rebooten könnte?

              Danke

              afuerhoff 1 Reply Last reply Reply Quote 0
              • afuerhoff
                afuerhoff Developer @SaiBot1981 last edited by afuerhoff

                @saibot1981
                Fritz Repeater kann ich nicht rebooten

                B 1 Reply Last reply Reply Quote 1
                • B
                  bishop @afuerhoff last edited by

                  @afuerhoff

                  passt jetzt nicht zum Adaptername, aber ist es möglich ein Telefon zu sperren damit es nicht klingelt?
                  fritzbox-klingelsperre-rcm950x0u.jpg

                  oder wie müsste ich da den Command zusammenstricken!?!

                  afuerhoff 1 Reply Last reply Reply Quote 0
                  • afuerhoff
                    afuerhoff Developer @bishop last edited by

                    @bishop sagte in Test Adapter fb-checkpresence v1.1.x:

                    oder wie müsste ich da den Command zusammenstricken!?!

                    Du könntest hier mal schauen. Da gibt es auch für DECT ein Dokument
                    https://avm.de/service/schnittstellen/

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      bishop @afuerhoff last edited by

                      @afuerhoff

                      habe ich mir mal angeschaut die "x_dectSCPD.pdf", habe aber nicht wirklich Ahnung wie ich da ein DECT Telefon sperren soll.

                      afuerhoff 1 Reply Last reply Reply Quote 0
                      • afuerhoff
                        afuerhoff Developer @bishop last edited by

                        @bishop
                        Ich habe in der Doku auch nichts passendes gefunden

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          Pischleuder @afuerhoff last edited by

                          @afuerhoff

                          Hi,

                          Danke zunächst für den Adpater, den ich gegen den life360 tauschen möchte.
                          Beim starten erhalte ich folgende Fehlermeldung:

                          fb-checkpresence.0	2021-06-19 14:36:02.630	info	(29822) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          fb-checkpresence.0	2021-06-19 14:36:02.627	info	(29822) terminating
                          fb-checkpresence.0	2021-06-19 14:36:02.129	warn	(29822) State "fb-checkpresence.0.info.connection" has no existing object, this might lead to an error in future versions
                          fb-checkpresence.0	2021-06-19 14:36:02.125	info	(29822) cleaned everything up ...
                          fb-checkpresence.0	2021-06-19 14:36:02.121	info	(29822) Got terminate signal TERMINATE_YOURSELF
                          fb-checkpresence.0	2021-06-19 14:36:02.068	warn	(29822) onReady: Fb init: getSSLPort: DeviceInfo:1 GetSecurityPort timeout of 6000ms exceeded
                          fb-checkpresence.0	2021-06-19 14:36:02.066	warn	(29822) The user could have been blocked from the fritzbox due to authentification problems! Please stop the adapter and reboot the fritzbox. Then start and try again.
                          fb-checkpresence.0	2021-06-19 14:35:55.979	info	(29822) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.1, js-controller: 3.2.16
                          fb-checkpresence.0	2021-06-19 14:31:06.056	info	(26051) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          fb-checkpresence.0	2021-06-19 14:31:06.055	info	(26051) terminating
                          fb-checkpresence.0	2021-06-19 14:31:05.557	warn	(26051) State "fb-checkpresence.0.info.connection" has no existing object, this might lead to an error in future versions
                          
                          

                          User und Passwort stimmen.

                          Any idea ?

                          Gruss

                          P 1 Reply Last reply Reply Quote 0
                          • P
                            Pischleuder @Pischleuder last edited by

                            @pischleuder

                            Edit: Kommando zurück, nach zweimaligem Neustart der Fritzbox funktioniert es nun.

                            1 Reply Last reply Reply Quote 0
                            • MichMein
                              MichMein last edited by

                              Hi @afuerhoff,
                              seit einem gestrigen Update meiner 7490 auf 7.27 steht der Adapter auf dem orangenen Warndreieck (keine Verbindung zum Gerät).
                              Hier das normale Log,

                              2021-07-10 03:19:23.831 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:19:37.843 - warn: fb-checkpresence.0 (28047) getExtIp:
                              2021-07-10 03:19:43.849 - warn: fb-checkpresence.0 (28047) getGuestWlan WLANConfiguration:3 GetInfo timeout of 6000ms exceeded
                              2021-07-10 03:19:49.853 - warn: fb-checkpresence.0 (28047) checkDevices: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:24:48.173 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:30:00.508 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:30:14.522 - warn: fb-checkpresence.0 (28047) getExtIp:
                              2021-07-10 03:30:20.529 - warn: fb-checkpresence.0 (28047) getGuestWlan WLANConfiguration:3 GetInfo timeout of 6000ms exceeded
                              2021-07-10 03:30:26.535 - warn: fb-checkpresence.0 (28047) checkDevices: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:35:24.853 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:40:37.191 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:40:51.203 - warn: fb-checkpresence.0 (28047) getExtIp:
                              2021-07-10 03:40:57.210 - warn: fb-checkpresence.0 (28047) getGuestWlan WLANConfiguration:3 GetInfo timeout of 6000ms exceeded
                              2021-07-10 03:41:03.216 - warn: fb-checkpresence.0 (28047) checkDevices: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:46:01.539 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:51:13.858 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:51:27.870 - warn: fb-checkpresence.0 (28047) getExtIp:
                              2021-07-10 03:51:33.877 - warn: fb-checkpresence.0 (28047) getGuestWlan WLANConfiguration:3 GetInfo timeout of 6000ms exceeded
                              2021-07-10 03:51:39.884 - warn: fb-checkpresence.0 (28047) checkDevices: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 03:56:38.202 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 04:01:50.526 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 04:02:04.546 - warn: fb-checkpresence.0 (28047) getExtIp:
                              2021-07-10 04:02:10.550 - warn: fb-checkpresence.0 (28047) getGuestWlan WLANConfiguration:3 GetInfo timeout of 6000ms exceeded
                              2021-07-10 04:02:16.555 - warn: fb-checkpresence.0 (28047) checkDevices: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 04:07:14.894 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 04:12:27.231 - warn: fb-checkpresence.0 (28047) checkPresence: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              2021-07-10 04:12:41.244 - warn: fb-checkpresence.0 (28047) getExtIp:
                              2021-07-10 04:12:47.249 - warn: fb-checkpresence.0 (28047) getGuestWlan WLANConfiguration:3 GetInfo timeout of 6000ms exceeded
                              2021-07-10 04:12:53.254 - warn: fb-checkpresence.0 (28047) checkDevices: getDeviceList: Hosts:1 X_AVM-DE_GetHostListPath: timeout of 6000ms exceeded
                              

                              Und hier ein Debug-Log nach Adapterrestart,

                              2021-07-10 20:16:41.038 - info: fb-checkpresence.0 (28047) Got terminate signal TERMINATE_YOURSELF
                              2021-07-10 20:16:41.041 - info: fb-checkpresence.0 (28047) cleaned everything up ...
                              2021-07-10 20:16:41.542 - info: fb-checkpresence.0 (28047) terminating
                              2021-07-10 20:16:41.544 - info: fb-checkpresence.0 (28047) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2021-07-10 20:16:45.453 - debug: fb-checkpresence.0 (14943) Redis Objects: Use Redis connection: 127.0.0.1:9001
                              2021-07-10 20:16:45.496 - debug: fb-checkpresence.0 (14943) Objects client ready ... initialize now
                              2021-07-10 20:16:45.499 - debug: fb-checkpresence.0 (14943) Objects create System PubSub Client
                              2021-07-10 20:16:45.500 - debug: fb-checkpresence.0 (14943) Objects create User PubSub Client
                              2021-07-10 20:16:45.502 - debug: fb-checkpresence.0 (14943) Objects client initialize lua scripts
                              2021-07-10 20:16:45.524 - debug: fb-checkpresence.0 (14943) Objects connected to redis: 127.0.0.1:9001
                              2021-07-10 20:16:45.534 - debug: fb-checkpresence.0 (14943) objectDB connected
                              2021-07-10 20:16:45.536 - debug: fb-checkpresence.0 (14943) Redis States: Use Redis connection: 127.0.0.1:9000
                              2021-07-10 20:16:45.546 - debug: fb-checkpresence.0 (14943) States create System PubSub Client
                              2021-07-10 20:16:45.548 - debug: fb-checkpresence.0 (14943) States create User PubSub Client
                              2021-07-10 20:16:45.559 - debug: fb-checkpresence.0 (14943) States connected to redis: 127.0.0.1:9000
                              2021-07-10 20:16:45.560 - debug: fb-checkpresence.0 (14943) statesDB connected
                              2021-07-10 20:16:45.880 - info: fb-checkpresence.0 (14943) starting. Version 1.1.7 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.2, js-controller: 3.3.14
                              2021-07-10 20:16:52.290 - info: fb-checkpresence.0 (14943) start fb-checkpresence.0: FRITZ!Box 7490 version: 113.07.27 ip-address: "192.168.178.1" - interval devices: 10 min. - interval members: 300 s
                              2021-07-10 20:16:52.291 - debug: fb-checkpresence.0 (14943) configuration user:
                              2021-07-10 20:16:52.292 - debug: fb-checkpresence.0 (14943) configuration history:
                              2021-07-10 20:16:52.292 - debug: fb-checkpresence.0 (14943) configuration dateformat:
                              2021-07-10 20:16:52.293 - debug: fb-checkpresence.0 (14943) configuration familymembers count: 2
                              2021-07-10 20:16:52.294 - debug: fb-checkpresence.0 (14943) configuration familymembers: [{"familymember":"Michaels-iPhone","macaddress":"DA:5A:91:12:CF:B0","ipaddress":"192.168.178.75","useip":true,"comment":"Michaels-iPhone","enabled":true,"usefilter":false,"group":"","usage":"IP","devicename":""},{"familymember":"Yvonnes-iPhone","macaddress":"26:66:D0:15:4A:2F","ipaddress":"192.168.178.74","useip":true,"comment":"Yvonnes-iPhone","enabled":true,"usefilter":false,"group":"","usage":"IP","devicename":""}]
                              2021-07-10 20:16:52.294 - debug: fb-checkpresence.0 (14943) configuration fb-devices true
                              2021-07-10 20:16:52.295 - debug: fb-checkpresence.0 (14943) configuration mesh info: true
                              2021-07-10 20:16:52.295 - debug: fb-checkpresence.0 (14943) configuration whitelist: true
                              2021-07-10 20:16:52.296 - debug: fb-checkpresence.0 (14943) configuration compatibility: true
                              2021-07-10 20:16:52.297 - debug: fb-checkpresence.0 (14943) configuration ssl: true
                              2021-07-10 20:16:52.297 - debug: fb-checkpresence.0 (14943) configuration qr code: false
                              2021-07-10 20:16:52.297 - debug: fb-checkpresence.0 (14943) configuration guest info: true
                              2021-07-10 20:16:52.298 - debug: fb-checkpresence.0 (14943) configuration filter delay: 15
                              2021-07-10 20:16:52.298 - info: fb-checkpresence.0 (14943) configuration default connection: -
                              2021-07-10 20:16:52.298 - warn: fb-checkpresence.0 (14943) Hosts1-X_AVM-DE_GetHostListPath is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.299 - warn: fb-checkpresence.0 (14943) Hosts1-X_AVM-DE_GetMeshListPath is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.299 - info: fb-checkpresence.0 (14943) Hosts1-GetSpecificHostEntry is supported
                              2021-07-10 20:16:52.299 - warn: fb-checkpresence.0 (14943) Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.300 - info: fb-checkpresence.0 (14943) DeviceInfo1-GetSecurityPort is supported
                              2021-07-10 20:16:52.300 - warn: fb-checkpresence.0 (14943) WANCommonInterfaceConfig1-GetCommonLinkProperties is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.300 - warn: fb-checkpresence.0 (14943) WANPPPConnection1-GetInfo is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.301 - warn: fb-checkpresence.0 (14943) WANIPConnection1-GetInfo is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.301 - warn: fb-checkpresence.0 (14943) WLANConfiguration3-SetEnable is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.301 - warn: fb-checkpresence.0 (14943) WLANConfiguration3-GetInfo is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.301 - warn: fb-checkpresence.0 (14943) WLANConfiguration3-GetSecurityKeys is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.302 - warn: fb-checkpresence.0 (14943) DeviceInfo1-GetInfo is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.302 - warn: fb-checkpresence.0 (14943) X_AVM-DE_HostFilter-DisallowWANAccessByIP is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.302 - warn: fb-checkpresence.0 (14943) X_AVM-DE_HostFilter-GetWANAccessByIP is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.303 - warn: fb-checkpresence.0 (14943) DeviceConfig1-Reboot is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.303 - warn: fb-checkpresence.0 (14943) WANPPPConnection1-ForceTermination is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.303 - warn: fb-checkpresence.0 (14943) LANConfigSecurity1-X_AVM-DE_GetCurrentUser is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.304 - warn: fb-checkpresence.0 (14943) Layer3Forwarding1-GetDefaultConnectionService is not supported! Feature is deactivated!
                              2021-07-10 20:16:52.337 - warn: fb-checkpresence.0 (14943) In an future version some states are not more existent. Please use compatibility = false to switch to the new handling of the states!
                              2021-07-10 20:16:52.337 - warn: fb-checkpresence.0 (14943) You should then manually delete the old states!
                              2021-07-10 20:16:52.346 - warn: fb-checkpresence.0 (14943) The state "guest" will not longer exist in a future version. Please use "guest.presence" instead!
                              2021-07-10 20:16:52.347 - warn: fb-checkpresence.0 (14943) The state "blacklist" will not longer exist in a future version. Please use "blacklist.presence" instead!
                              2021-07-10 20:16:52.348 - warn: fb-checkpresence.0 (14943) The state "activeDevices" will not longer exist in a future version. Please use "fb-devices.active" instead!
                              2021-07-10 20:16:52.348 - warn: fb-checkpresence.0 (14943) The state "devices" will not longer exist in a future version. Please use "fb-devices.count" instead!
                              2021-07-10 20:16:52.899 - info: fb-checkpresence.0 (14943) createGlobalObjects finished successfully
                              2021-07-10 20:16:53.117 - warn: fb-checkpresence.0 (14943) The state "fb-checkpresence.0.Michaels-iPhone" will not longer exist in a future version. Please use "fb-checkpresence.0.Michaels-iPhone.presence" instead!
                              2021-07-10 20:16:53.259 - debug: fb-checkpresence.0 (14943) sendTo "getEnabledDPs" to system.adapter.influxdb.0 from system.adapter.fb-checkpresence.0
                              2021-07-10 20:16:53.274 - warn: fb-checkpresence.0 (14943) The state "fb-checkpresence.0.Yvonnes-iPhone" will not longer exist in a future version. Please use "fb-checkpresence.0.Yvonnes-iPhone.presence" instead!
                              2021-07-10 20:16:53.438 - debug: fb-checkpresence.0 (14943) sendTo "getEnabledDPs" to system.adapter.influxdb.0 from system.adapter.fb-checkpresence.0
                              2021-07-10 20:16:53.449 - info: fb-checkpresence.0 (14943) createMemberObjects finished successfully
                              2021-07-10 20:16:53.450 - info: fb-checkpresence.0 (14943) states successfully subscribed
                              2021-07-10 20:16:53.451 - info: fb-checkpresence.0 (14943) loop successfully started
                              2021-07-10 20:17:00.464 - debug: fb-checkpresence.0 (14943) loop family ends after 6,13882628 s
                              2021-07-10 20:17:14.481 - warn: fb-checkpresence.0 (14943) getExtIp:
                              2021-07-10 20:17:14.483 - debug: fb-checkpresence.0 (14943) loop main ends after 12,17266068 s
                              

                              Ich hoffe du kannst helfen, vielen Dank.

                              Wal 1 Reply Last reply Reply Quote 0
                              • Wal
                                Wal Developer @MichMein last edited by

                                @michmein ,
                                habe die 7.27 auf einer 6490 und den Adaptern tr-64, fb-checkpresence und Fritzdect ohne Probleme am Laufen.

                                MichMein 1 Reply Last reply Reply Quote 0
                                • MichMein
                                  MichMein @Wal last edited by MichMein

                                  @wal danke für die Rückmeldung, hilft mir persönlich aber leider nicht wenn es bei dir läuft 😉
                                  Ich versuche mal nen Neustart der Fritzbox.

                                  Wal 1 Reply Last reply Reply Quote 0
                                  • Wal
                                    Wal Developer @MichMein last edited by

                                    @michmein ,
                                    das denke ich mir auch, nur afuerhoff wird da auch nichts machen können. Ich lasse mich aber überraschen.

                                    MichMein 1 Reply Last reply Reply Quote 0
                                    • MichMein
                                      MichMein @Wal last edited by

                                      @wal @afuerhoff
                                      Ein Neustart hat das Problem leider nicht behoben, jedoch aber das neu eintragen des bereits korrekt gesetzten Passwortes. Der Adapter ist wieder grün.

                                      Schönes Wochenende noch!

                                      afuerhoff 1 Reply Last reply Reply Quote 1
                                      • afuerhoff
                                        afuerhoff Developer @MichMein last edited by afuerhoff

                                        @michmein
                                        Schön das es wieder läuft. Hab deine Message erst heute morgen gesehen. Ich hätte auch erstmal einen Reboot der Fritzbox vorgeschlagen. Wichtig ist dabei, dass der Adapter vorher gestoppt wird.
                                        Das mit dem Passwort kann ich mir nicht erklären.
                                        Die Konfiguration und somit das Passwort wurden ja nicht zwischenzeitlich verändert. Könnte evtl. mit ioBroker selbst zusammenhängen.
                                        Ich nutze die Passwort Funktionalität von ioBroker.

                                        1 Reply Last reply Reply Quote 0
                                        • MichMein
                                          MichMein last edited by

                                          Hi @afuerhoff,
                                          meine Aussage dass es klappt nach dem ich das Passwort neu eingegeben habe muss ich leider zurück nehmen.
                                          Folgendes habe ich gemacht nachdem ich gesehen hatte das der Adapter nicht lief,

                                          1. Adapter gestoppt, alle Objekte gelöscht, Adapter auf Debug gestellt, Passwort neu eingetragen, Adapter gestartet. Ergebnis > Adapter bleibt orange
                                          2. Adapter gestoppt, alle Objekte gelöscht, Adapter auf Debug gestellt, Eintrag unter Username gelöscht, Adapter gestartet. Ergebnis > Adapter wird grün aber die Objekte werden nicht aktualisiert
                                          3. Adapter gestoppt, alle Objekte gelöscht, Adapter auf Debug gestellt, neuen User in FritzBox angelegt und die Daten im Adapter neu eingetragen, Adapter gestartet. Ergebnis > Adapter bleibt orange

                                          So, während ich jetzt hier geschrieben habe, habe ich nebenbei noch etwas getestet und siehe da nachdem ich SSL deaktiviert hatte klappt es wieder alles und der Adapter wird grün und auch die Objekte werden erstellt und aktualisiert.

                                          Hast du eine Idee warum das so gewesen sein kann?
                                          SSL war sonst die ganze Zeit aktiv und es hat alles funktioniert bis zum kürzlich durchgeführten Update.

                                          Danke

                                          afuerhoff 1 Reply Last reply Reply Quote 0
                                          • afuerhoff
                                            afuerhoff Developer @MichMein last edited by

                                            @michmein sagte in Test Adapter fb-checkpresence v1.1.x:

                                            meine Aussage dass es klappt nach dem ich das Passwort neu eingegeben habe muss ich leider zurück nehmen.

                                            Hilfreich wäre noch die Log Ausgabe gewesen, damit man erkennen kann wo der Adapter hängen bleibt.
                                            Das mit dem SSL ist ein Workaround für einen anderen User gewesen, der auch Probleme hatte. Warum das so ist, kann ich nicht wirklich sagen.

                                            M 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            577
                                            Online

                                            31.8k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            avm fb-checkpresence fritzbox tr-064
                                            88
                                            947
                                            245350
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo