Giter Club home page Giter Club logo

iobroker.fb-checkpresence's Introduction

Logo

ioBroker.fb-checkpresence

GitHub license Downloads GitHub repo size

GitHub commit activity GitHub commits since latest release (by date) GitHub last commit GitHub issues Known Vulnerabilities

NPM

Number of Installations (latest) Stable version Latest NPM version

Tests: Test and Release

fb-checkpresence adapter for ioBroker

The adapter checks the presence of family members over the fritzbox. You must fill in the name of the family member and the mac-address (or ip-address) of the used device. The comment is optional and you can enable or disable the family member. The datapoint is based on the member name.

Used open source code

npm dateformat v4.5.3

(c) 2007-2009 Steven Levithan <stevenlevithan.com> npm: https://www.npmjs.com/package/dateformat github: https://github.com/felixge/node-dateformat license: MIT

Adapter pre conditions

For the correct function you have to install a history adapter. You can choose one of the following adapters:

  • History
  • SQL
  • InfluxDB

Used device

For this adapter the AVM Fritzbox is used. Here you can find informations about the Fritzbox https://avm.de/produkte/fritzbox/. The fritzbox services are used over the TR-064 protocol.

Fritzbox conditions

The used TR-064 interface from the fritzbox is described here: https://avm.de/service/schnittstellen/. Following TR-064 services and actions are used:

  • Hosts:1 - X_AVM-DE_GetHostListPath (supported since 2017-01-09)
  • Hosts:1 - X_AVM-DE_GetMeshListPath
  • Hosts:1 - GetSpecificHostEntry
  • Hosts:1 - X_AVM-DE_GetSpecificHostEntryByIP (supported since 2016-05-18)
  • DeviceInfo:1 - GetSecurityPort
  • DeviceInfo:1 - GetInfo
  • WANPPPConnection:1 - GetInfo
  • WANIPConnection:1 - GetInfo
  • WLANConfiguration3 - SetEnable
  • WLANConfiguration3 - GetInfo
  • WLANConfiguration3 - GetSecurityKeys
  • X_AVM-DE_HostFilter - DisallowWANAccessByIP
  • X_AVM-DE_HostFilter - GetWANAccessByIP
  • DeviceConfig:1 - Reboot
  • LANConfigSecurity1 - X_AVM-DE_GetCurrentUser

By default, the TR-064 interface is not activated. However, this can easily be changed via the FritzBox web interface. To do this log in into your FritzBox and ensure that the expert view is activated. Then you will find below "Home Network »Home Network Overview» Network Settings" the point "Allow access for applications". There you have to activate the checkbox and then restart the FritzBox once.

Hint: After changing the options, don't forget the restart of the Fritzbox !

Configuration dialog

General

The configuration values are validated and only correct values can be saved. Otherwise the save button is disabled.

Fritzbox IP-address, user and password

The configuration of ip-address, user and password is necessary to get the device data from the fritzbox. Therefore a user has to be created in the fritzbox. This is required with newer firmware version (>= 7.25)of the fritzbox. See here fore information: https://avm.de/fileadmin/user_upload/Global/Service/Schnittstellen/Empfehlungen%20zur%20Benutzerfu%CC%88hrung%20bei%20der%20Anmeldung%20an%20einer%20FRITZ%21Box_v1.1.pdf The password is encrypted and wasn't saved in clear text. The user name and password may have a maximum of 32 characters. See for information: https://service.avm.de/help/de/FRITZ-Box-Fon-WLAN-7490/014/hilfe_zeichen_fuer_kennwoerter#:~:text=Namen%20f%C3%BCr%20Benutzer,Kennwortfeld%20darf%20nicht%20leer%20sein. Hint: In some cases it could be that the fritzbox blocked the user if the password was not correctly inserted. Often a timeout message is in the log. Please check than the if you has insert the correct username and password.Then you have to reboot the fritzbox.

Ssl option

In some cases the adapter could not connect to the fritzbox. It could help to disable this option. In this case the adapter tries to connect without https.

Interval

You have separate intervals for family members and Fritzbox devices. The interval for Fritzbox devices can be configured from 10s to 3600s. Normally a value between 60 and 300 seconds is an optimal interval to read the fritzbox data. Family members could be configured from 10s to 600s. Every new cycle starts if the previous cycle is finished.

Filter time

If the filter time is greater than 0s the state of a family member is checked twice (after the filter time) if the state is changing to false. If the state is true the state is immediate set.

History adapter

Over the history adapter some values are calculated. You can choose, if the history, the sql or the influxdb adapter is used for this calculations. The history adapter must be installed preliminary and can then selected in the configuration dialog. If the history configuration is disabled then the calculation of some values could not be realized.

Dateformat

The date format mask options are described on this web page: https://www.npmjs.com/package/dateformat. The format mask is used for formatting the html and json table objects.

Creation of FB devices

If this option is checked, the objects for every device in the Fritzbox device list are created. If this option is disabled, then also the mesh informations are disabled.

Resynchronisation of FB device objects

If this option is checked, then the FB device object are re-synchronized with the device list fom Fritzbox.

Creation of mesh information

This option can be checked if the creation of FB devices is allowed. If this option is checked, the mesh objects for every device in the Fritzbox device list are created.

guest information

If this option is checked the states for guests are created.

qr-code generation

If this option is checked the qr-code from guest wlan is generated.

Family member settings

For a configured family member you should enter the member name, the hostname, the mac- and ip-address, a comment and you can enable or disable the member. A group is optional. If you leave the group empty and set the compatibility flag to true the behaviour is like an older version of the adaper. You can use the presence state from the family member or the state directly mapped to the family member name. In a future version you must use the presence state. This behaviour could be switched on/off with the compatibility checkbox: -> compatibility = true: behaviour as an older version with empty group. -> compatibility = true and group not empty: new behaviour. All states beneath the familymembers folder. -> compatibility = false: new behaviour. All states beneath the familymembers folder.

For every member the adapter creates a presence state and checks if the member is present or absent. The state was changed if the presence state changed. You can also enable the filtering for a member. If the state is true the state changes immediately to true. If it is false then the value will checked after the filter time again. If the state is in both cases false then the state changes to false. Otherwise it does not change.

To get the speed information in the objects you have to select fb-devices option.

Manually trigger presence

In javascript you can trigger the presence manually. When you send the message to the adapter every new message is blocked for 10 seconds. You receive a negative result (false) if the message is blocked. True if the message is received from the adapter. sendTo('fb-checkpresence.0', 'triggerPresence', {} , function (result) { log(result, 'info'); });

Whitelist settings

In the white list you can insert every known device. Any unknown devices are listed in the blacklist object. If you check the checkbox in the headline of the table all devices are selected.

Features

AVM support check

The function checks the availability of used fritzbox features. The availability is logged as info. If you have problems look if the features are all set to true. Also the access rights are checked for the user and the feature is set to false if the acces right is not correct.

Switch on / off the guest wlan

Under the folder guest you can set the state wlan to true or false and then the guest wlan switches on or off.

QR code of guest wlan

The QR code of the guest wlan is saved in the state wlanQR in the guest folder. The QR code can show in vis in the basic - Bool SVG widget.

Switch on / off the internet access of Fritzbox devices

Under the folder FB-devices you could set the disabled state to true or false and the the internet access of this device is blocked in the Fritzbox.

Get guests, blacklist

In this function it is checked if any user is logged in as guest. Also is checked if any device is not in the white list listed. This devices are added to the blacklist.

Get Active

For every family member the presence, the comming and going dates and several other infos are calculated and saved in the member object if a history adapter is selected.

Host number, active devices

The amount of devices and how many are active are get from the fritzbox.

Objects

Object presenceAll

If all family members are present then the object is true.

Object presence

If one family member ist present then the object is true.

Object devices

These are all listed devices in the fritzbox

Object activeDevices

These are the amount of all active devices in the fritzbox

Object html, json

These objects are tables (json and html) with the comming and going information of all family members in it.

Object info

Here are informations listed about the last update and the connection status from the adapter.

Object guest

Here are informations listed about the amount of active guests and table objects with the device information in it.

Object blacklist

Here are informations listed about the amount of unknown devices and table objects with the unknown device information in it.

Object member.present

Here you will find information about the presence of a member on the current day and how long the member has been the status true since the last change.

Object member.absent

Here you will find information about the absence of a member on the current day and how long the member has been the status false since the last change.

Object member.comming, member.going

Here you will find information when the family member arrives or leaving home.

Object member.history, member.historyHtml

Here you will find information about the history of the current day.

Changelog

WORK IN PROGRESS

1.2.4 (2024-02-09)

  • (afuerhoff) test code deleted #257
  • (afuerhoff) dependencies updated

1.2.3 (2024-01-18)

  • (afuerhoff) Readme updated
  • (afuerhoff) function jsontables optimized
  • (afuerhoff) non existent members set to false #253
  • (afuerhoff) optimization of log message #240

1.2.2 (2023-07-28)

  • (afuerhoff) bug fixed json tables #215
  • (afuerhoff) link feature optimized. See #206

1.2.1 (2023-07-14)

  • (afuerhoff) bug fixed property link

1.2.0 (2023-07-13)

  • (afuerhoff) dependencies updated
  • (afuerhoff) mesh link added to family members #206

License

MIT License

Copyright (c) 2019-2024 Achim Fürhoff [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.fb-checkpresence's People

Contributors

afuerhoff avatar apollon77 avatar dependabot[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

iobroker.fb-checkpresence's Issues

Neustart Problem

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

2021-02-26 07_08_14-info - ioBroker und 3 weitere Seiten - Profil 1 – Microsoft​ Edge

[Idee] presence name

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

warning: duplicate hostname

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..

`

fb-checkpresence.0 2020-05-04 13:36:27.397 warn (12616) dublicate fritzbox device item. Please correct the hostname in the fritzbox settings for the device -> Diskstation 00:11:32:A6:75:70
fb-checkpresence.0 2020-05-04 13:36:27.396 warn (12616) dublicate fritzbox device item. Please correct the hostname in the fritzbox settings for the device -> Diskstation 00:11:32:A6:75:6F
fb-checkpresence.0 2020-05-04 13:36:27.394 warn (12616) dublicate fritzbox device item. Please correct the hostname in the fritzbox settings for the device -> Android-5 8C:45:00:A8:75:83
fb-checkpresence.0 2020-05-04 13:36:27.394 warn (12616) dublicate fritzbox device item. Please correct the hostname in the fritzbox settings for the device -> Android-5 6C:56:97:54:C2:A2
fb-checkpresence.0 2020-05-04 13:36:27.393 warn (12616) dublicate fritzbox device item. Please correct the hostname in the fritzbox settings for the device -> Android-2 58:B1:0F:01:A7:2E
fb-checkpresence.0 2020-05-04 13:36:27.393 warn (12616) dublicate fritzbox device item. Please correct the hostname in the fritzbox settings for the device -> Android-2 20:47:DA:01:7B:93

`

fb-checkpresence.<x>.presence not correct

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.

BugReport FB-Presence

Compatibility check and testing for Node.js 14 and 16

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!

Instanz 0 Abhängigkeit

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

Request: less logging on insufficient permissions

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:
image

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:
image

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.

Mesh Status der Geräte als Objekt mit einfügen

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.

Devices "leaving" and "coming back" periodically

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)

Presence only using last device if a member has multiple devices

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

Adapter dont start Again

fb-checkpresence.0 2021-02-23 23:34:30.443 info (32454) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
fb-checkpresence.0 2021-02-23 23:34:30.442 info (32454) terminating
fb-checkpresence.0 2021-02-23 23:34:30.441 info (32454) cleaned everything up ...
fb-checkpresence.0 2021-02-23 23:34:30.440 info (32454) Got terminate signal TERMINATE_YOURSELF
fb-checkpresence.0 2021-02-23 23:34:30.396 error (32454) createFbDeviceObjects -> can't read devices from fritzbox! Adapter stops
fb-checkpresence.0 2021-02-23 23:34:30.396 error (32454) getDeviceList: "Can not read hostlist path"
fb-checkpresence.0 2021-02-23 23:34:30.395 error (32454) soapAction X_AVM-DE_GetHostListPath status=null errNo=0
fb-checkpresence.0 2021-02-23 23:34:29.779 info (32454) createMemberObjects finished successfully
fb-checkpresence.0 2021-02-23 23:34:29.408 info (32454) createGlobalObjects finished successfully
fb-checkpresence.0 2021-02-23 23:34:29.196 info (32454) service DeviceConfig1-Reboot is supported
fb-checkpresence.0 2021-02-23 23:34:29.181 info (32454) service X_AVM-DE_HostFilter-GetWANAccessByIP is supported
fb-checkpresence.0 2021-02-23 23:34:29.164 info (32454) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is supported
fb-checkpresence.0 2021-02-23 23:34:29.147 info (32454) service DeviceInfo1-GetInfo is supported

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

No history before this day

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)

Nach Neustart wird die Alias-ID für die Datenbank gelöscht

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

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

grafik

obwohl es wie folgt im Adapter hinterlegt ist:

grafik

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

grafik

Er schmeisst den Alias raus!

Der Adapter ist wie folgt konfiguriert:
grafik

Mein System:
grafik

presence immer "true"

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

Used invalid characters: fb-checkpresence.0.fb-devices.MyFRITZ!App 2....

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

Presence does not work when the device is connected via ethernet

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

Mesh seems to be probelmatic

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.

Statusupdate erst nach Restart der Instanz

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!

devices active, devices inactive not updated after reconnect of line

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..

grafik

Please check ioBroker.fb-checkpresence with js-controller 2.0

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.

error: soap action status 500

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:

`

fb-checkpresence.0 2020-05-14 07:43:24.797 debug (7833) checkPresence first run
fb-checkpresence.0 2020-05-14 07:43:24.797 error (7833) soapAction status 500
fb-checkpresence.0 2020-05-14 07:43:24.797 error </s:Envelope>
fb-checkpresence.0 2020-05-14 07:43:24.797 error </s:Body>
fb-checkpresence.0 2020-05-14 07:43:24.797 error </s:Fault>
fb-checkpresence.0 2020-05-14 07:43:24.797 error
fb-checkpresence.0 2020-05-14 07:43:24.797 error
fb-checkpresence.0 2020-05-14 07:43:24.797 error NoSuchEntryInArray
fb-checkpresence.0 2020-05-14 07:43:24.797 error 714
fb-checkpresence.0 2020-05-14 07:43:24.797 error
fb-checkpresence.0 2020-05-14 07:43:24.797 error
fb-checkpresence.0 2020-05-14 07:43:24.797 error UPnPError
fb-checkpresence.0 2020-05-14 07:43:24.797 error s:Client
fb-checkpresence.0 2020-05-14 07:43:24.797 error <s:Fault>
fb-checkpresence.0 2020-05-14 07:43:24.797 error <s:Body>
fb-checkpresence.0 2020-05-14 07:43:24.797 error <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
fb-checkpresence.0 2020-05-14 07:43:24.797 error (7833) soapAction mesg
fb-checkpresence.0 2020-05-14 07:43:23.950 debug (7833) history Bernd true time: Thu May 14 2020 07:43:23 GMT+0200 (Central European Summer Time)
fb-checkpresence.0 2020-05-14 07:43:23.949 debug (7833) history Bernd true time: Thu May 14 2020 07:43:23 GMT+0200 (Central European Summer Time)

`

Verify Compact mode for your adapter

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.

getGuest error

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

can't start the adapter Error: Can not read hostlist path

since today I have a problem with the adapter.

fb-checkpresence.0 2021-02-17 08:17:21.100 error (4980) createFbDeviceObjects -> can't read devices from fritzbox! Adapter stops
fb-checkpresence.0 2021-02-17 08:17:21.100 error (4980) getDeviceList: "Can not read hostlist path"
fb-checkpresence.0 2021-02-17 08:17:21.099 error (4980) soapAction /upnp/control/hosts X_AVM-DE_GetHostListPath status=ETIMEDOUT errNo=5 connect ETIMEDOUT 192.168.178.1:49443

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

Adapter 1.1.5 wird von Iobroker beendet und lässt sich nicht mehr starten

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

Problem after update my Fritz.Box to version 7.25

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

Compatibility check to js-controller 3.3 and Admin5 React UI

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!

adapter termination after upgrade 1.1.4

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

fb-checkpresence.0 2021-06-02 19:45:33.431 info (8948) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
fb-checkpresence.0 2021-06-02 19:45:33.430 info (8948) terminating
fb-checkpresence.0 2021-06-02 19:45:32.928 info (8948) cleaned everything up ...
fb-checkpresence.0 2021-06-02 19:45:32.927 info (8948) Got terminate signal TERMINATE_YOURSELF
fb-checkpresence.0 2021-06-02 19:45:32.851 warn (8948) onReady: Fb init: checkServices: checkService Error service WLANConfiguration3-SetEnable is not supported! Can not find service file! Feature is deactivated
fb-checkpresence.0 2021-06-02 19:45:32.325 info (8948) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v10.24.1, js-controller: 3.2.16
fb-checkpresence.0 2021-06-02 19:45:32.116 debug (8948) statesDB connected
fb-checkpresence.0 2021-06-02 19:45:32.115 debug (8948) States connected to redis: 127.0.0.1:9000
fb-checkpresence.0 2021-06-02 19:45:32.109 debug (8948) States create User PubSub Client
fb-checkpresence.0 2021-06-02 19:45:32.108 debug (8948) States create System PubSub Client
fb-checkpresence.0 2021-06-02 19:45:32.101 debug (8948) Redis States: Use Redis connection: 127.0.0.1:9000
fb-checkpresence.0 2021-06-02 19:45:32.098 debug (8948) objectDB connected
fb-checkpresence.0 2021-06-02 19:45:32.087 debug (8948) Objects connected to redis: 127.0.0.1:9001
fb-checkpresence.0 2021-06-02 19:45:32.072 debug (8948) Objects client initialize lua scripts
fb-checkpresence.0 2021-06-02 19:45:32.072 debug (8948) Objects create User PubSub Client
fb-checkpresence.0 2021-06-02 19:45:32.071 debug (8948) Objects create System PubSub Client
fb-checkpresence.0 2021-06-02 19:45:32.067 debug (8948) Objects client ready ... initialize now
fb-checkpresence.0 2021-06-02 19:45:32.021 debug (8948) Redis Objects: Use Redis connection: 127.0.0.1:9001

Versions:

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

Additional context
Add any other context about the problem here.

Checkpresence does not accept MAC from an Iphone 12

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!
-- | -- | -- | --]

Datenpunkt presence auch für guest einfügen

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.

Guest Presence und Daten werden nicht gesetzt, sofern Gäste über Repeater angemeldet sind

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.

222

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!

Diverse Errors

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

Adapter crashes if no fritzbox at ip

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. :-)

Fritzbox 7581(fw7.14) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

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:

fb-checkpresence.1 2021-05-23 11:56:09.125 info (5544) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
fb-checkpresence.1 2021-05-23 11:56:09.124 info (5544) terminating
fb-checkpresence.1 2021-05-23 11:56:08.622 info (5544) cleaned everything up ...
fb-checkpresence.1 2021-05-23 11:56:08.620 info (5544) Got terminate signal TERMINATE_YOURSELF
fb-checkpresence.1 2021-05-23 11:56:08.470 warn (5544) 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.1 2021-05-23 11:56:07.143 info (5544) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.21.0, js-controller: 3.3.10

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

adapter quits with timeout

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!

usage of deprecated node package [email protected]

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.

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

Wrong typ nach Umstellung auf js-controller 3.3.4

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.

image

Think about to fix the issues found by adapter checker

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

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.