No matter whether I change something in the instance settings, the Save/Save+Close buttons are always grayed out/not available.
js-controller 3.1.6
nodejs 12.20.0
npm 6.14.9

Think about update stable version to 1.1.4

Version: stable=1.1.0 (180 days old) => latest=1.1.4 (15 days old)
Installs: stable=3614 (74.36%), latest=722 (14.86%), total=4860
Click to edit

with js-controller 3.1.4, node 12.6.3, linux mint 18.3, npm 6.14.5, fb-checkpresence v1.0.1, and fritzos 7.19-78939Beta this error appears:

`

`

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/afuerhoff/ioBroker.fb-checkpresence

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.fb-checkpresence"

I have also found warnings that may be fixed if possible.

• [W400] Cannot find "fb-checkpresence" in latest repository

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Habe den Adapter seit ein paar Tagen installiert und mich gewundert, dass nach mehreren Tagen immer noch im Log folgenden Eintrag finde:

Habe darauf in der Datenbank nachgesehen und festgestellt, dass die Daten nicht per Alias, sondern als Datenpunkt gespeichert werden

obwohl es wie folgt im Adapter hinterlegt ist:

Wenn ich dann den Adapter neustarte, sieht es folgendermaßen aus:

Er schmeisst den Alias raus!

Der Adapter ist wie folgt konfiguriert:

Mein System:

FB reboot dont Work again
Iobroker Reboot dont Work again
Raspi Reboot dont Work again
fritzbox 6490 Fritz os 7.20

(32726) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.20.2, js-controller: 3.1.6

Hi .. I restored my installation on another machine .. now I get loads of messages like this in the log file:

(1143) : No history before this day is available (lastVal = null)

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

Describe the bug
When using the same member name on multiple devices, the "presence flag" and associated information is only taking into consideration the last device for that member.

To Reproduce
Steps to reproduce the behavior:

1. Go to Adapter settings'
2. Add 2 entries for different devices for the same member
3. Attempt to offline/online either device. Only the last device in the list changes the status.

Expected behavior
If at least one device is present, it should react from the first available device until the last available device for the same family member name.

Versions:

• Adapter version: 10.3
• JS-Controller version: 3.1.4
• Node version: v10.21.0
• Operating system: Debian 10.0 running on x86_64 (LXC Container)

Additional context
The behaviour onfortunately complicates automation based on family member presence.

Thanks for your great work

Describe the bug
The adapter starts with a wrong configured IP, so there is no FB at the IP it tries to reach, then the adapter crashes with uncaught error messages.

To Reproduce
Steps to reproduce the behavior:

1. Install adapter & create instance
2. Have your Fritzbox not running on default of 192.168.178.1 but something else ;-)
3. See errors in log fie

Expected behavior
The adapter should catch the errors and print a human readable error in the log indicating it did not find a fritzbox at the specified IP and either exit cleanly or do nothing at all. Crashing the adapter will lead to ugly errors, does not make clear what the issue is and will let js-controller restart the adapter over and over.

Screenshots & Logfiles

2020-02-13 11:24:00.236  - info: fb-checkpresence.0 (4290) starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v10.18.0
2020-02-13 11:24:00.268  - info: fb-checkpresence.0 (4290) start fb-checkpresence: ip-address: 192.168.178.1 polling interval: 1 Min.
2020-02-13 11:24:11.620  - error: fb-checkpresence.0 (4290) onMessage: Cannot read property 'length' of undefined
2020-02-13 11:26:09.930  - error: fb-checkpresence.0 (4290) uncaught exception: Cannot read property 'search' of undefined
2020-02-13 11:26:09.931  - error: fb-checkpresence.0 (4290) TypeError: Cannot read property 'search' of undefined
    at /opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:37:57
    at Parser.<anonymous> (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:308:18)
    at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:327:16)
    at Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:5:59)
    at exports.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:369:19)
    at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:36:17)
    at self.callback (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:185:22)
    at Request.onRequestError (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:877:8)
2020-02-13 11:26:09.932  - info: fb-checkpresence.0 (4290) cleaned everything up...
2020-02-13 11:26:09.933  - error: fb-checkpresence.0 (4290) onReady: connect ETIMEDOUT 192.168.178.1:49000
2020-02-13 11:26:09.937  - info: fb-checkpresence.0 (4290) terminating
2020-02-13 11:26:09.938  - info: fb-checkpresence.0 (4290) Terminated (NO_ERROR): Without reason
2020-02-13 11:26:11.254  - error: host.Server Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:37:57
2020-02-13 11:26:11.254  - error: host.Server Caught by controller[0]:     at Parser.<anonymous> (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:308:18)
2020-02-13 11:26:11.254  - error: host.Server Caught by controller[0]:     at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:327:16)
2020-02-13 11:26:11.254  - error: host.Server Caught by controller[0]:     at Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:5:59)
2020-02-13 11:26:11.254  - error: host.Server Caught by controller[0]:     at exports.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:369:19)
2020-02-13 11:26:11.254  - error: host.Server Caught by controller[0]:     at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:36:17)
2020-02-13 11:26:11.255  - error: host.Server Caught by controller[0]:     at self.callback (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:185:22)
2020-02-13 11:26:11.255  - error: host.Server Caught by controller[0]:     at Request.onRequestError (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:877:8)
2020-02-13 11:26:11.255  - info: host.Server instance system.adapter.fb-checkpresence.0 terminated with code 0 (NO_ERROR)
2020-02-13 11:26:11.255  - info: host.Server Restart adapter system.adapter.fb-checkpresence.0 because enabled
2020-02-13 11:26:41.271  - info: host.Server instance system.adapter.fb-checkpresence.0 started with pid 12590
2020-02-13 11:26:42.369  - info: fb-checkpresence.0 (12590) starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v10.18.0
2020-02-13 11:26:42.394  - info: fb-checkpresence.0 (12590) start fb-checkpresence: ip-address: 192.168.178.1 polling interval: 1 Min.
2020-02-13 11:28:51.728  - error: fb-checkpresence.0 (12590) uncaught exception: Cannot read property 'search' of undefined
2020-02-13 11:28:51.729  - error: fb-checkpresence.0 (12590) TypeError: Cannot read property 'search' of undefined
    at /opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:37:57
    at Parser.<anonymous> (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:308:18)
    at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:327:16)
    at Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:5:59)
    at exports.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:369:19)
    at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:36:17)
    at self.callback (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:185:22)
    at Request.onRequestError (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:877:8)
2020-02-13 11:28:51.729  - info: fb-checkpresence.0 (12590) cleaned everything up...
2020-02-13 11:28:51.730  - error: fb-checkpresence.0 (12590) onReady: connect ETIMEDOUT 192.168.178.1:49000
2020-02-13 11:28:51.733  - info: fb-checkpresence.0 (12590) terminating
2020-02-13 11:28:51.734  - info: fb-checkpresence.0 (12590) Terminated (NO_ERROR): Without reason
2020-02-13 11:28:52.400  - error: host.Server Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:37:57
2020-02-13 11:28:52.401  - error: host.Server Caught by controller[0]:     at Parser.<anonymous> (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:308:18)
2020-02-13 11:28:52.401  - error: host.Server Caught by controller[0]:     at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:327:16)
2020-02-13 11:28:52.402  - error: host.Server Caught by controller[0]:     at Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:5:59)
2020-02-13 11:28:52.402  - error: host.Server Caught by controller[0]:     at exports.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:369:19)
2020-02-13 11:28:52.402  - error: host.Server Caught by controller[0]:     at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:36:17)
2020-02-13 11:28:52.402  - error: host.Server Caught by controller[0]:     at self.callback (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:185:22)
2020-02-13 11:28:52.402  - error: host.Server Caught by controller[0]:     at Request.onRequestError (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/request/request.js:877:8)
2020-02-13 11:28:52.402  - info: host.Server instance system.adapter.fb-checkpresence.0 terminated with code 0 (NO_ERROR)
2020-02-13 11:28:52.402  - info: host.Server Restart adapter system.adapter.fb-checkpresence.0 because enabled
2020-02-13 11:29:03.581  - info: host.Server instance system.adapter.fb-checkpresence.0 started with pid 19959

Versions:

• Adapter version: 0.2.2
• JS-Controller version: 2.2.8
• Node version: 10.18.0
• Operating system: linux / ubuntu

Works fine after I changed the IP. Thanks. :-)

I have a mesh network here with AVW repeaters connected to the FB via LAN. My devices are logged periodically (about every hour) as "going", only to be logged again a few seconds later as "comming". The status itself is correct most of the time, but the timestamps are not usable.

I would expect devices to be logged as "going" only when they actually leave the mesh WLAN. In my case, however, the error described above also occurs with devices that are not moved and always have the best WLAN reception.

Versions:

• Adapter version: 1.10
• JS-Controller version: 3.1.6
• Node version: 12.18.4
• Operating system: Raspbian (Pi 4)

Hallo!

Ich benutze neben einer Fritz!box 6590 Cable noch einen Fritz!Repeater 3000, da das Netzwerk sonst nicht ausreicht.

Sofern die Gäste über den Repeater verbunden sind, werden keine Daten unter fb-checkpresence.0.guest gesetzt.

Angebunden ist der Repeater über Mesh mitteln LAN Kabel.. Konfiguration auch alles über die 6590.
Hinweis in Repeater: Dieser FRITZ!Repeater ist Teil des Heimnetzes einer FRITZ!Box (eines Routers).

Ein Versuch eine weitere Instanz des fb-checkpresence einzurichten scheitert.. Der Repeater kann vermutlich nicht direkt angesprochen werden.

Vielen Dank!

Es ist die selbe Konfiguration wie bei Neustart Problem, lediglich die Firmware der FB 7590 wurde auf 7.25 geupdated. Geräte bei Familien mitglieder werden die Stati nicht aktualisiert. Bei den FB devices schon...

Describe the bug
usage of deprecated node package [email protected]

To Reproduce
Steps to reproduce the behavior:
install from GitHub URL in IOBroker

Expected behavior
no error message during install

Screenshots & Logfiles
Install output:
`$ ./iobroker url "https://github.com/afuerhoff/ioBroker.fb-checkpresence" --debug
install https://github.com/afuerhoff/ioBroker.fb-checkpresence/tarball/master
npm install https://github.com/afuerhoff/ioBroker.fb-checkpresence/tarball/master --production --save --prefix "/usr/local/iobroker" (System call)
npm
WARN deprecated [email protected]: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.

• [email protected] 6 packages from 7 contributors and audited 4673 packages in 6.229s

found 60 vulnerabilities (43 low, 17 high) run npm audit fix to fix them, or npm audit for details

process exited with code 0`

Versions:

• Adapter version: 0.0.7
• JS-Controller version: 1.5.3
• Node version: 10.17
• Operating system: OSX

Additional context

Nach einem Neustart des Pi werden nach und nach alle Adapter gestartet. Nachdem alle Adapter laufen registriert der Adapter keine Statusänderung der FB Geräte (An- oder Abmeldung). Um dieses Problem zu beheben muss der Adapter einmal neu gestartet werden, danach funktioniert alles einwandfrei.

Adapter Version 1.1.0

Hi, the adapter shows the presence of wifi devices close to the main router but an iphone connected to a mesh device does not receive the present state.

after every start of the adapter, the warning "duplicate hostname device macaddress" is show in the logfile.
Sorry, thats normal, because a lot of devices must HAVE more network adapters and mac addresses... :-)
A Server have one Hostname, and 2 LAN devices and a wifi device, so it's not possible to change to every Mac Address the hostname.
Disable this warning, please, make no sense..

`

`

Hallo wäre es möglich den Gastzugang ein bzw. aus zuschalten.

laut API scheint es zu funktionieren: http://www.apfel-z.net/artikel/Fritz_Box_API_TR_064_via_PHP/ vlt hilft das :)

Vielen Dank!

Hallo, erstmal danke für den guten Adapter er funktioniert bei mir sehr gut.

es gibt ja den punkt presence der ja besagt das min 1 Familien Mittelglied anwesend ist
gut währe es wenn es noch einen "presence-name" wert geben würde um schneller festzustellen wer online ist (nur der name) ohne das man alle einzeln abfragen müsste zbs bei größeren Familien mit Kindern

Das selbe währe auch noch in umgekehrter Reihenfolge gut
presenceAll besagt ja das alle da sind, wenn false könnte man sagen wer nicht hier ist
das würde bei einer Visualisierung und Telegramm Benachrichtigung einiges erleichtern

Describe the bug
In der Funktion checkpresence gibt es in der Abfrage der History eine Abhängigkeit zur Instanz 0 des Adapters.

Hi There,

have a new iPhone 12 attached to my network. Adapter works fine with all other family members - After adding the iphone 12 it does not work with this device (Fixed MAC) - With this error:

[fb-checkpresence.0 | 2021-06-13 11:20:46.906 | warn | getActive Jan-neu: Warning: The configured mac-address for member Jan-neu was not found. Please insert a valid mac-address!
-- | -- | -- | --]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
after update from 1.1.0 to 1.1.4 (stable)
fritzbox 6820
testet with and without ssl
fritzbox reboot not help

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles

Versions:

• Adapter version:
• JS-Controller version:
• Node version:
• Operating system:

Additional context
Add any other context about the problem here.

The history adapter reports in the following in the logs:

Object fb-checkpresence.0.<deviceName> is invalid: obj.type has to exist.
This object will not be created in future versions. Please report this to the developer.

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Iobroker wurde schon neu gestartet, und Fritzbox (os 7.25) auch neu gestartet.

Alles kein Effekt.

• 2021-06-11 20:03:57.997 - info: host.Iobroker-Produktiv "system.adapter.fb-checkpresence.0" disabled
• 2021-06-11 20:03:57.999 - info: host.Iobroker-Produktiv stopInstance system.adapter.fb-checkpresence.0 (force=false, process=true)
• 2021-06-11 20:03:58.011 - info: fb-checkpresence.0 (27631) Got terminate signal TERMINATE_YOURSELF
• 2021-06-11 20:03:58.013 - info: fb-checkpresence.0 (27631) cleaned everything up ...
• 2021-06-11 20:03:58.014 - info: host.Iobroker-Produktiv stopInstance system.adapter.fb-checkpresence.0 send kill signal
• 2021-06-11 20:03:58.513 - info: fb-checkpresence.0 (27631) terminating
• 2021-06-11 20:03:58.514 - info: fb-checkpresence.0 (27631) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

Hi,

I have a problem with the start of the adapter. Everything worked well before, but now the adapter quits with a timeout:

_> fb-checkpresence.0 | 2020-10-27 15:20:30.902 | info | (20132) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

-- | -- | -- | --
fb-checkpresence.0 | 2020-10-27 15:20:30.902 | info | (20132) terminating
fb-checkpresence.0 | 2020-10-27 15:20:30.902 | info | (20132) cleaned everything up...
fb-checkpresence.0 | 2020-10-27 15:20:30.901 | info | (20132) Got terminate signal TERMINATE_YOURSELF
fb-checkpresence.0 | 2020-10-27 15:20:30.869 | error | (20132) createFbDeviceObjects -> can't read devices from fritzbox!
fb-checkpresence.0 | 2020-10-27 15:20:30.868 | error | (20132) soapAction X_AVM-DE_GetHostListPath status=ETIMEDOUT errNo=5 connect ETIMEDOUT 192.168.2.1:49443
fb-checkpresence.0 | 2020-10-27 15:20:09.655 | info | (20132) service GetInfo is supported
fb-checkpresence.0 | 2020-10-27 15:20:09.619 | info | (20132) service GetSecurityPort is supported
fb-checkpresence.0 | 2020-10-27 15:20:09.591 | info | (20132) service X_AVM-DE_GetSpecificHostEntryByIP is supported
fb-checkpresence.0 | 2020-10-27 15:20:09.565 | info | (20132) service GetSpecificHostEntry is supported
fb-checkpresence.0 | 2020-10-27 15:20:09.534 | info | (20132) service X_AVM-DE_GetHostListPath is supported
fb-checkpresence.0 | 2020-10-27 15:20:09.489 | info | (20132) start fb-checkpresence: ip-address: 192.168.2.1 polling interval: 1 Min.
fb-checkpresence.0 | 2020-10-27 15:20:09.461 | info | (20132) starting. Version 1.0.4 in C:/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.16.2, js-controller: 3.1.6_

The problem occurs on two of my installations with windows10 2004 home edition.
Additional Fritzbox user is created with password (access for all applications is also set within FB7590 with Fritz!OS 7.2.1)

My configuration:

• TR-064 adapter V4.1.0 (is configured and works well)
• fb-checkpresence V1.0.4
• iobroker v4.1.10
• JS controller 3.1.6

Thanks in advance!

Version 1.03; Erstmal Danke für die Adapterentwicklung! Leider erfolgt der Statusupdate der Anwesenheit jeweils erst nach Restart der Instanz, obwohl Zeitintervall 1 Minute ausgewählt ist. Bitte um Info wenn LOGS benötigt werden und welche. Danke!

Hello, I have 3 instances of the adapter running. See the following error descriptions. All Fritz boxes are configured in the same way and enabled for access.
The Fritzbox is connected over the WAN-Port to a Fiber-Modem, therefore DSL is deactivated.

Adapter version is 1.1.4 - what's going wrong?
Thanks in advance!

Instance 1: 7590 (fw7.21) works fine

Instance 2: 7581 (fw7.14) I see the following entries in the log:

**------------------------------------------------------------------------------------------------------------
Instance 3: 7530 (fw7.25) Works only with disable "SSL" Flag

Adapter geht immer wieder auf Rot, Hatte den js.contoller geupdatet, dachte daran lag es . Hatte ein rollback des js.controlers auf 2.2.1 gemacht, dies brachte aber kein erfolg.
Der adapter lief vorher.
liegt der Fehler bei mir?

fb-checkpresence.0 2020-02-18 22:25:10.124 info (10521) start fb-checkpresence: ip-address: 192.168.158.1 polling interval: 1 Min.
fb-checkpresence.0 2020-02-18 22:25:10.108 info (10521) starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v10.19.0
host.iobroker 2020-02-18 22:25:09.319 info instance system.adapter.fb-checkpresence.0 started with pid 10521
host.iobroker 2020-02-18 22:24:39.313 info Restart adapter system.adapter.fb-checkpresence.0 because enabled
host.iobroker 2020-02-18 22:24:39.313 info instance system.adapter.fb-checkpresence.0 terminated with code 0 (NO_ERROR)
host.iobroker 2020-02-18 22:24:39.313 error Caught by controller[0]: at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:881:8)
host.iobroker 2020-02-18 22:24:39.313 error Caught by controller[0]: at Request.emit (events.js:198:13)
host.iobroker 2020-02-18 22:24:39.313 error Caught by controller[0]: at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
host.iobroker 2020-02-18 22:24:39.313 error Caught by controller[0]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:36:17)
host.iobroker 2020-02-18 22:24:39.313 error Caught by controller[0]: at exports.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:369:19)
host.iobroker 2020-02-18 22:24:39.312 error Caught by controller[0]: at Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:5:59)
host.iobroker 2020-02-18 22:24:39.312 error Caught by controller[0]: at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:327:16)
host.iobroker 2020-02-18 22:24:39.312 error Caught by controller[0]: at Parser.emit (events.js:198:13)
host.iobroker 2020-02-18 22:24:39.312 error Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:308:18)
host.iobroker 2020-02-18 22:24:39.312 error Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:37:57
host.iobroker 2020-02-18 22:24:39.312 error Caught by controller[0]: TypeError: Cannot read property 'search' of undefined
fb-checkpresence.0 2020-02-18 22:24:38.802 info (8903) Terminated (NO_ERROR): Without reason
fb-checkpresence.0 2020-02-18 22:24:38.801 info (8903) terminating
fb-checkpresence.0 2020-02-18 22:24:38.798 error (8903) onReady: read ECONNRESET
fb-checkpresence.0 2020-02-18 22:24:38.797 info (8903) cleaned everything up...
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:881:8)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Request.emit (events.js:198:13)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:36:17)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at exports.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:369:19)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:5:59)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:327:16)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Parser.emit (events.js:198:13)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at Parser. (/opt/iobroker/node_modules/iobroker.fb-checkpresence/node_modules/xml2js/lib/parser.js:308:18)
fb-checkpresence.0 2020-02-18 22:24:38.796 error at /opt/iobroker/node_modules/iobroker.fb-checkpresence/lib/fb.js:37:57
fb-checkpresence.0 2020-02-18 22:24:38.796 error (8903) TypeError: Cannot read property 'search' of undefined
fb-checkpresence.0 2020-02-18 22:24:38.796 error (8903) uncaught exception: Cannot read property 'search' of undefined

Hi!

I don't feel comfortable providing the admin password of my Fritz!Box to ioBroker/fb-checkpresence. To me, this is a sensitive account with very high privileges. But that high privileges are not needed for just reading the devices and determining the presence status.

For that reason, I added a dedicated (service) account on my Fritz!Box with limited permissions:

Everything is working fine with these settings. It's ok for me, that I cannot make changes in ioBroker that require higher privileges on my Fritz!Box.

The only annoying thing is, that fb-checkpresence writes the "insufficient" permissions quite often to the log file:

Could you please reduce the amount of logging in this case? Would it not be sufficient, if it's logged just one time on adapter startup or one time each day?

I really would appreciate a cleaner and smaller log file. And also a little less load on my system.

Thank you.

Es wäre schön, wenn man die Zugangsprofile von Geräten per Adapter ändern könnte.
( Fritzbox -> Internet -> Filter -> Kindersicherung -> Internet sperren / Profil wechseln )

Hello!
Even with presenceAll = true the object presence is set to false since last update to 1.1.4

Danke für einen schnellen Fix!
PhG

Es wäre super wenn bei den Geräten der jeweilige Mesh Access Point mit angezeigt wird über den sie gerade verbunden sind.
Damit könnte man das Geräte Orten wo es sich im Haus gerade ca. befindet.

my password in the fritzbox have an " inside. But it is not possible so save an password in the adapter.
--> save button will disabled as soon as I type "

I have tested with beta and github version

allowed should be
_ - ! " # $ % & ' ( ) * + , . / : ; < = > ? @ [ \ ] ^ ` { | } ~

please see https://service.avm.de/help/de/FRITZ-Box-Fon-WLAN-7490/014/hilfe_zeichen_fuer_kennwoerter

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Hi,
not a bug report, but important for Beta-Testers and the future development,
in FritzOS 7.24 and higher are a change was done, take a look here, please:

https://avm.de/fritz-labor/frisch-aus-der-entwicklung/bekannte-probleme/

I have update my Fritz.Box 7590 from 7.21 to version 7.25. Now the adapter stops and I found the following in the log-file:

fb-checkpresence.0
2021-02-28 18:21:09.134 | error | (32512) createFbDeviceObjects -> can't read devices from fritzbox! Adapter stops
2021-02-28 18:21:09.134 | error | (32512) getDeviceList: "Can not read hostlist path"
2021-02-28 18:21:09.132 | error | (32512) soapAction X_AVM-DE_GetHostListPath status=null errNo=0

I have dobbel checked the authentication data, but all is ok.

Adapter version: 1.1.0
Plattform: linux
Betriebssystem: linux
Die Architektur: arm
CPUs: 4
Geschwindigkeit: 1500 MHz
Modell: ARMv7 Processor rev 3 (v7l)
RAM: 3.7 GB
System-Betriebszeit: 6 T. 08:30:45
Node.js: v12.20.1
NPM: 6.14.10
Datenträgergröße: 109.7 GiB
Datenträger verfügbar: 99.0 GiB

In my installation the indicator "fb-checkpresence.0.presence" ist set to "false" although "fb-checkpresence.0.presentMembers" is filled with two - all family - devices. Even "fb-checkpresence.0.presenceAll" ist set to "true", which actually is true. I guess that "fb-checkpresence.0.presence" should also be "true".

To reproduce:
One Device has to be present - then watch flag "fb-checkpresence.0.presence" being shortly true, then changing to false.

2020-12-10 05:41:06.687 - info: host.ioBroker-Server stopInstance system.adapter.fb-checkpresence.0 (force=false, process=true) 2020-12-10 05:41:06.688 - info: host.ioBroker-Server stopInstance system.adapter.fb-checkpresence.0 send kill signal 2020-12-10 05:41:06.690 - info: fb-checkpresence.0 (20150) Got terminate signal TERMINATE_YOURSELF 2020-12-10 05:41:06.691 - info: fb-checkpresence.0 (20150) cleaned everything up ... 2020-12-10 05:41:06.691 - info: fb-checkpresence.0 (20150) terminating 2020-12-10 05:41:06.691 - info: fb-checkpresence.0 (20150) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-12-10 05:41:10.654 - info: fb-checkpresence.0 (20280) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v10.23.0, js-controller: 3.1.6 2020-12-10 05:41:10.664 - info: fb-checkpresence.0 (20280) start fb-checkpresence: ip-address: "192.168.178.1" - interval devices: 1 Min. - interval members: 10 s 2020-12-10 05:41:10.751 - info: fb-checkpresence.0 (20280) service Hosts1-X_AVM-DE_GetHostListPath is supported 2020-12-10 05:41:10.758 - info: fb-checkpresence.0 (20280) service Hosts1-X_AVM-DE_GetMeshListPath is supported 2020-12-10 05:41:10.766 - info: fb-checkpresence.0 (20280) service Hosts1-GetSpecificHostEntry is supported 2020-12-10 05:41:10.772 - info: fb-checkpresence.0 (20280) service Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is supported 2020-12-10 05:41:10.779 - info: fb-checkpresence.0 (20280) service DeviceInfo1-GetSecurityPort is supported 2020-12-10 05:41:10.788 - info: fb-checkpresence.0 (20280) service WANPPPConnection1-GetInfo is supported 2020-12-10 05:41:10.796 - info: fb-checkpresence.0 (20280) service WLANConfiguration3-SetEnable is supported 2020-12-10 05:41:10.806 - info: fb-checkpresence.0 (20280) service WLANConfiguration3-GetInfo is supported 2020-12-10 05:41:10.817 - info: fb-checkpresence.0 (20280) service DeviceInfo1-GetInfo is supported 2020-12-10 05:41:10.822 - info: fb-checkpresence.0 (20280) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is supported 2020-12-10 05:41:10.828 - info: fb-checkpresence.0 (20280) service X_AVM-DE_HostFilter-GetWANAccessByIP is supported 2020-12-10 05:41:10.834 - info: fb-checkpresence.0 (20280) service DeviceConfig1-Reboot is supported 2020-12-10 05:41:10.953 - info: fb-checkpresence.0 (20280) createGlobalObjects finished successfully 2020-12-10 05:41:11.162 - info: fb-checkpresence.0 (20280) createMemberObjects finished successfully 2020-12-10 05:41:13.085 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra) changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra) 2020-12-10 05:41:13.086 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).meshstate changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).meshstate 2020-12-10 05:41:13.086 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).macaddress changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).macaddress 2020-12-10 05:41:13.086 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).ipaddress changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).ipaddress 2020-12-10 05:41:13.086 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).active changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).active 2020-12-10 05:41:13.086 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).disabled changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).disabled 2020-12-10 05:41:13.086 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).interfacetype changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).interfacetype 2020-12-10 05:41:13.087 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).speed changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).speed 2020-12-10 05:41:13.087 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).guest changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).guest 2020-12-10 05:41:13.087 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).whitelist changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).whitelist 2020-12-10 05:41:13.087 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).blacklist changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).blacklist 2020-12-10 05:41:15.789 - info: fb-checkpresence.0 (20280) createFbDeviceObjects finished successfully 2020-12-10 05:41:16.566 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0 changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0 2020-12-10 05:41:16.567 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0.name changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0.name 2020-12-10 05:41:16.567 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0.link changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0.link 2020-12-10 05:41:16.567 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0.rx_rcpi changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0.rx_rcpi 2020-12-10 05:41:16.567 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0.cur_data_rate_rx changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0.cur_data_rate_rx 2020-12-10 05:41:16.567 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0.cur_data_rate_tx changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0.cur_data_rate_tx 2020-12-10 05:41:16.567 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).0.type changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).0.type 2020-12-10 05:41:19.216 - info: fb-checkpresence.0 (20280) createMeshObjects finished successfully 2020-12-10 05:41:26.125 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra) changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra) 2020-12-10 05:41:26.125 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).meshstate changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).meshstate 2020-12-10 05:41:26.126 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).macaddress changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).macaddress 2020-12-10 05:41:26.126 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).ipaddress changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).ipaddress 2020-12-10 05:41:26.126 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).active changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).active 2020-12-10 05:41:26.126 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).disabled changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).disabled 2020-12-10 05:41:26.127 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).interfacetype changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).interfacetype 2020-12-10 05:41:26.127 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).speed changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).speed 2020-12-10 05:41:26.127 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).guest changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).guest 2020-12-10 05:41:26.127 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).whitelist changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).whitelist 2020-12-10 05:41:26.128 - warn: fb-checkpresence.0 (20280) Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F, Marco Guerra).blacklist changed to fb-checkpresence.0.fb-devices.MyFRITZ!App 2 (Samsung SM-G928F_ Marco Guerra).blacklist

lt. Community sollen Meldungen die sich aus der Umstellung des js-controller auf die Version 3.3.4 ergeben bei den entsprechenden Adaptern gemeldet werden.

Der Adapter funktioniert Augenscheinlich normla, jedoch wird das LOG mit WARN Meldungen übersäät.

Describe the bug
Sometimes a getGuest error was reported in the log.

To Reproduce
The items in the Fritzbox device list are changing over time. These behaviour triggers the error.

Expected behavior
No error happens

Versions:

• Adapter version: 0.1.0, 0.20

Wäre es möglich 2 neue states anzulegen "absend und absentAll" wie bereits für prensent und presentAll?

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Ich steuere einige Sachen über die Logik Gast anwesend ja/nein.
Natürlich kann ich mir einen eigenen Datenpunkt erzeugen, der bei guest; count >0 auf true geht.
Fände es komfortabler wenn der Adapter auch unter guest einen presence true/false wie bei den Familienmitgliedern erzeugen würde.

FritzBox 7560, UniFi AP-nanoHD
2 SmartPhones im Gastnetz 192.168.179.xxx, deshalb Ident über MAC Adresse, eingetragen
als "Familienmitglied" und in der "Whitelist"

Wenn diese 2 SmartPhones abgemeldet sind und weder in der FritzBox noch im UniFi AP
als aktiv aufgeführt sind,
erscheinen aber auch nach 1 Std. immer noch in den Objekten:

fb-checkpresence.0.Galaxy-S7-edge.presence: true
fb-checkpresence.0.Samsung-Dani.presence: true

FritzBox 7590, OS 7.21 release
fb-checkpresence Adapter Version 1.10 latest from Github
js-controller 3.16, linux debian 10 in lxc on proxmox.

Every night after the internet reconnect the adapter don't update the active devices, inactive devices any more.
A restart only of the adapter solves the problem.

I found it with logging my devices, after the reconnect the line is eval... thats not normal, because some devices are going off or on automatically..
In the picture you see the lines toggles around the measurements, but after the reconnect time in the night the line goes straight ahead. Than I restart the Adapter, thats the big break you see..

Think about update stable version to 1.0.1

Version: stable=0.3.0 (57 days old) => latest=1.0.1 (15 days old)
Installs: stable=1204 (58.79%), latest=663 (32.37%), total=2048
Click to edit

So i had the idea to automate something when switch my pc on. I create a new familymember and so on. But the problem is that my PC is always "presence" even when disonnected or switched off. So i looked into my fritzbox and found the problem. Even here the PC was listed under active devices.

But there was a difference. In my FritzBox i can see the data rate of the PC when it's connected and the data rate is not shown when its disconnected. Unfortunately this information cannot be viewed in the tool.

So my question is, if you can add the information (if available) to your tool.

• Adapter version: 0.3.0
• JS-Controller version: 4.3.4
• Node version: 12.16.1
• Operating system: raspery pi

Your adapter is already in ioBroker latest repository available to be used by testwilling users. In order to make your adapter also available for the wide user base which uses the stable repository you should also add your adapter to the stable repository. Please see instructions at https://github.com/ioBroker/ioBroker.repositories#requirements-for-adapter-to-get-added-to-the-stable-repository

Thank you for your support.

since today I have a problem with the adapter.

I try to reinstall die adapter but it doesn't work.