Describe the bug
Before v4 my fritzbox showed up, since v4 is does not. Config checked and valid!

Is your feature request related to a problem? Please describe.
Currently I'm not able to use a Fritz!Box 5490 as master - it looks like that a new type of device "fiber" (beside dsl, cable, repeater) needs to be introduced

When running in debug mode the log shows
[TR064 Debug] FritzBox5490 api request 10: Ok (authenticated)
[TR064 Debug] FritzBox5490 api request 10: get /upnp/control/wanipconnection1
[TR064 Debug] FritzBox5490 api request 11: Ok (authenticated)
[TR064 Debug] FritzBox5490 api request 11: get /upnp/control/wanipconnection1
[TR064 Debug] FritzBox5490 api request 12: Ok (authenticated)
[TR064 Debug] FritzBox5490 api request 12: get /upnp/control/wanipconnection1
[TR064 Debug] FritzBox5490 api request 13: Ok (authenticated)
[TR064 Debug] FritzBox5490 api request 13: get /upnp/control/wanipconnection1
[TR064 Debug] FritzBox5490 api request 13: Ok (authenticated)
[TR064 Debug] FritzBox5490 api request 13: get /upnp/control/wanipconnection1
[TR064 Debug] FritzBox5490 api request 13: Ok (authenticated)
[TR064 Debug] FritzBox5490 api request 13: get /upnp/control/wanipconnection1

Describe the solution you'd like
new type "fiber" to be supported

Describe alternatives you've considered
Tried with "repeater" as type but this won't work for the master
Skipping the looping part for fiber models to get information on WAN connection would be a workaround that would it do for me

Nach dem Austausch meiner FritzBox kann ich meine FRITZ!DECT 210 Steckdose nicht mehr schalten.

Die Konfiguration ist unverändert:

"Espressomaschine":
{
"active": true,
"ain": "1234567890123",
"tempSensor": true,
"devType": "switch"
}

Im Log kommt aber permanent der Fehler:

FritzPlatform Espressomaschine Temperature: No device with AIN: 1234567890123 found or not intialized yet!

Ich habe das Modul auch schon neu installiert und die gesamte Konfiguration neu durchlaufen. Das hat aber leider nicht geholfen.

Es sieht aber auch so aus, als würde die grundsätzliche Kommunikation mit der Fritzbox Schwierigkeiten bereiten. Zwar steht im Log die Meldung "Successfully logged in", es kommen aber auch Fehler:

FritzPlatformTR064 [TR064 Debug] FRITZ!Box 6591 Cable api request 1: Error
[6/17/2019, 9:30:58 AM] [FritzPlatform] [ERROR] Smarthome List: An error occured while generating smarthome list!
2019-06-17T09:30:58.275Z FritzPlatform Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
2019-06-17T09:30:59.296Z FritzPlatformTR064 [TR064 Debug] FRITZ!Box 6591 Cable api request 1: Error
[6/17/2019, 9:30:59 AM] [FritzPlatform] [ERROR] FritzBox: An error occured while checking firmware!
2019-06-17T09:30:59.297Z FritzPlatform Error: read ECONNRESET

Der Unterschied zwischen alter und neuer Box ist

ALT: 6590, FritzOS 7.10
Neu: 6591: FritzOX 7.04 (die neuere gibt es noch nicht...)

Welche weiteren Analysemöglichkeiten gibt es?

Grüße
Bernd

Describe the bug
Incompatibility with 3490, not found tr64desc.xml

To Reproduce
Steps to reproduce the behavior:

1. Go to configure with the following "config.yaml"
   " "platform": "FritzPlatform",
   "disableAutoSearch": true,
   "devices": {
   "FritzBox router": {
   "active": true,
   "host": "192.168.2.1",
   "port": 80,
   "username": "username",
   "password": "pwd",
   "type": "cable",
   "master": false,
   "mesh": false,
   "readOnly": false,
   "options": {
   "reconnect": false,
   "wifi2": [
   true,
   false
   ],
   "wifi5": [
   true,
   false
   ],
   "wifiGuest": [
   true,
   false
   ],
   "wps": [
   true,
   false
   ]
   }
   }
   },
   "smarthome": {},
   "callmonitor": {},
   "presence": {},
   "wol": [],
   "phoneBook": {},
   "alarm": {},
   "wakeup": {},
   "ringlock": {},
   "broadband": {},
   "extReboot": {},
   "telegram": {},
   "polling": 10,
   "timeout": 10,
   "clearCache": false,
   "debug": true,
   "disableAutoConfig": false
   },"

Expected behavior
works

Desktop (please complete the following information):

• OS: Raspbian

Additional context
log of error:
ug 31 16:41:41 raspberrypi homebridge[8050]: 2019-07-31T14:41:41.378Z FritzPlatform Found following devices:
lug 31 16:41:41 raspberrypi homebridge[8050]: 2019-07-31T14:41:41.412Z FritzPlatform [ { name: 'FritzBox router',
lug 31 16:41:41 raspberrypi homebridge[8050]: address: '192.168.2.1',
lug 31 16:41:41 raspberrypi homebridge[8050]: port: 80,
lug 31 16:41:41 raspberrypi homebridge[8050]: location: 'http://192.168.2.1:80/tr64desc.xml',
lug 31 16:41:41 raspberrypi homebridge[8050]: serial: 'FB-19216xxx' } ]
lug 31 16:41:41 raspberrypi homebridge[8050]: [2019-7-31 4:41:41 PM] [FritzPlatform] [INFO] Initializing config...
lug 31 16:41:43 raspberrypi homebridge[8050]: [2019-7-31 4:41:43 PM] Homebridge is running on port 51826.
lug 31 16:41:43 raspberrypi homebridge[8050]: 2019-07-31T14:41:43.980Z FritzPlatform Initializing extra accessories...
lug 31 16:41:44 raspberrypi homebridge[8050]: 2019-07-31T14:41:44.015Z FritzPlatform Initializing extras...
lug 31 16:41:44 raspberrypi homebridge[8050]: 2019-07-31T14:41:44.023Z FritzPlatform Initializing telegram...
lug 31 16:41:44 raspberrypi homebridge[8050]: 2019-07-31T14:41:44.029Z FritzPlatform Initializing callmonitor...
lug 31 16:41:44 raspberrypi homebridge[8050]: [2019-7-31 4:41:44 PM] [FritzPlatform] [INFO] Auto config generator disabled.
lug 31 16:41:44 raspberrypi homebridge[8050]: [2019-7-31 4:41:44 PM] [FritzPlatform] [INFO] Found 1 active devices...
lug 31 16:41:44 raspberrypi homebridge[8050]: 2019-07-31T14:41:44.066Z FritzPlatform Checking master device...
lug 31 16:41:47 raspberrypi homebridge[8050]: [2019-7-31 4:41:47 PM] [FritzPlatform] [ERROR] An error occured while checking config!
lug 31 16:41:47 raspberrypi homebridge[8050]: 2019-07-31T14:41:47.077Z FritzPlatform { status: 404,
lug 31 16:41:47 raspberrypi homebridge[8050]: message: 'Not Found',
lug 31 16:41:47 raspberrypi homebridge[8050]: config:
lug 31 16:41:47 raspberrypi homebridge[8050]: { url: 'http://192.168.2.1:80/tr64desc.xml',
lug 31 16:41:47 raspberrypi homebridge[8050]: headers:
lug 31 16:41:47 raspberrypi homebridge[8050]: { Accept: 'application/json, text/plain, /',
lug 31 16:41:47 raspberrypi homebridge[8050]: 'User-Agent': 'axios/0.19.0' },
lug 31 16:41:47 raspberrypi homebridge[8050]: transformRequest: [ [Function: transformRequest] ],
lug 31 16:41:47 raspberrypi homebridge[8050]: transformResponse: [ [Function: transformResponse] ],
lug 31 16:41:47 raspberrypi homebridge[8050]: timeout: 0,
lug 31 16:41:47 raspberrypi homebridge[8050]: adapter: [Function: httpAdapter],
lug 31 16:41:47 raspberrypi homebridge[8050]: xsrfCookieName: 'XSRF-TOKEN',
lug 31 16:41:47 raspberrypi homebridge[8050]: xsrfHeaderName: 'X-XSRF-TOKEN',
lug 31 16:41:47 raspberrypi homebridge[8050]: maxContentLength: -1,
lug 31 16:41:47 raspberrypi homebridge[8050]: validateStatus: [Function: validateStatus],
lug 31 16:41:47 raspberrypi homebridge[8050]: method: 'get',
lug 31 16:41:47 raspberrypi homebridge[8050]: data: undefined },
lug 31 16:41:47 raspberrypi homebridge[8050]: data:
lug 31 16:41:47 raspberrypi homebridge[8050]: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<title>FRITZ!Box</title>\n\n\n

Hello,

question: why you cannot just keep the previous versions alive if there are significant changes on any new version?

For example for me and some others the V3.x worked very well and with V4.x there has been so many issues that I am really thinking to remove the plugin fully.
To be honest, it is really a great plugin and thanks for your effort but if the plugin or newer version are raising more issues than bringing solutions it will not be helpful for anyone.

Currently I think the best work was with V2.x and V3.x but
V4.x is really a pain.

Just something to think about.

Thx

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

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

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

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi,

today after I restart of my homebridge I saw the following in the log:

[2019-3-30 22:42:46] [FritzPlatform] [ERROR] Fritz!Box: An error occured while getting WIFI WPS state!
[2019-3-30 22:42:46] [FritzPlatform] [ERROR] {
"error": "ESOCKETTIMEDOUT",
"errorCode": "ESOCKETTIMEDOUT",
"serviceType": "urn:dslforum-org:service:WLANConfiguration:1",
"action": "X_AVM-DE_GetWPSInfo"
}
[2019-3-30 22:42:46] [FritzPlatform] [ERROR] Fritz!Box: An error occured while getting Answering Machine state!
[2019-3-30 22:42:46] [FritzPlatform] [ERROR] {
"error": "ESOCKETTIMEDOUT",
"errorCode": "ESOCKETTIMEDOUT",
"serviceType": "urn:dslforum-org:service:X_AVM-DE_TAM:1",
"action": "GetInfo"
}

Do not know if this is critical and where it comes from.

Sometimes i get this error, when i want to switch on / off a DECT Plug (homeApp):

[FritzBox] [ERROR] Ventilator: An error occured by turning off Ventilator
[FritzBox] [ERROR] {
"response": "OK",
"responseCode": 200,
"tr064": "Auth. failed",
"tr064code": "503",
"fault": "UPnPError",
"faultcode": "s:Client",
"serviceType": "urn:dslforum-org:service:X_AVM-DE_Homeauto:1",
"action": "SetSwitch"
}

After toggling several times (3 to 5 times) the error message doesn't occur anymore and everything works fine. After some hours the error occurs again.

FritzBox 7590
Firmware 7.01

Thanks for your support
M.

Hi there,

I just played around with your plugin and tried to add a presence sensor without the "type": "motion" property (works fine with it) and got the following error:

/usr/lib/node_modules/homebridge-fritz-platform/src/accessory.js:2266
    const totallength = accessory.context.fakegatoService.history.length - 1;
                                                          ^

TypeError: Cannot read property 'history' of undefined
    at Fritz_Box.getMotionLastActivation (/usr/lib/node_modules/homebridge-fritz-platform/src/accessory.js:2266:59)
    at Fritz_Box.getService (/usr/lib/node_modules/homebridge-fritz-platform/src/accessory.js:683:63)
    at new Fritz_Box (/usr/lib/node_modules/homebridge-fritz-platform/src/accessory.js:66:85)
    at FritzPlatform.configureAccessory (/usr/lib/node_modules/homebridge-fritz-platform/src/platform.js:501:7)
    at Timeout._onTimeout (/usr/lib/node_modules/homebridge-fritz-platform/src/platform.js:503:34)
    at ontimeout (timers.js:498:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:290:5)

You might want to add a check before accessing the fakegatoService property (which is not available for occupancy sensors I guess).

Best regards

Fritzbox 7582 not working with the Plugin.
Firmware 7.08 BETA.

Any ideas?

[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] FritzBox: An error occured while fetching SID, trying again in 30 seconds...
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] {
"error": "ESOCKETTIMEDOUT",
"errorCode": "ESOCKETTIMEDOUT",
"serviceType": "urn:dslforum-org:service:DeviceConfig:1",
"action": "X_AVM-DE_CreateUrlSID"
}
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] FritzBox: An error occured while fetching SID, trying again in 30 seconds...
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] {
"error": "ESOCKETTIMEDOUT",
"errorCode": "ESOCKETTIMEDOUT",
"serviceType": "urn:dslforum-org:service:DeviceConfig:1",
"action": "X_AVM-DE_CreateUrlSID"
}
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] FritzBox: An error occured while getting host list, trying again in 30 seconds...
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] {
"error": "ESOCKETTIMEDOUT",
"errorCode": "ESOCKETTIMEDOUT",
"serviceType": "urn:dslforum-org:service:Hosts:1",
"action": "X_AVM-DE_GetHostListPath"
}
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] FritzBox: An error occured while getting host list, trying again in 30 seconds...
[5/7/2019, 7:16:22 PM] [FritzPlatform] [ERROR] {
"error": "ESOCKETTIMEDOUT",
"errorCode": "ESOCKETTIMEDOUT",
"serviceType": "urn:dslforum-org:service:Hosts:1",
"action": "X_AVM-DE_GetHostListPath"
}

[FritzBox] [ERROR] {
"error": "Internal Server Error",
"errorCode": 500,
"tr064": "Invalid Action",
"tr064code": "401",
"serviceType": "urn:dslforum-org:service:WANPPPConnection:1",
"action": "GetStatusInfo",
"device": "FRITZ!Box 7490",
"host": "fritz.box"
}

Running new FritzOS 07.01

Hey SeydX,

For some days I always get the following error message. Also a restart of all devices had unfortunately no success.

2019-05-25T06:23:33.570Z FritzPlatformLUA [LUA Debug] FritzBox7580 api request 52: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.571Z FritzPlatformLUA [LUA Debug] FritzBox7580 api request 53: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.572Z FritzPlatformLUA [LUA Debug] FritzBox7580 api request 54: get /data.lua?sid=324c407f25dab2e7 (nightsetting)
2019-05-25T06:23:33.572Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-KAMMERL api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.573Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-ELTERN-2 api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.574Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-3000-WOHNZIMMER api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.574Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1160-TANKRAUM api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.583Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-KUECHE api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.584Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-3000-ESSZIMMER api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.585Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-ELTERN api request 10: get /data.lua?sid=324c407f25dab2e7
2019-05-25T06:23:33.747Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-3000-ESSZIMMER api request 10: Requesting new SID
[2019-5-25 08:23:33] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-3000-ESSZIMMER: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-05-25T06:23:33.757Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-3000-WOHNZIMMER api request 10: Requesting new SID
[2019-5-25 08:23:33] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-3000-WOHNZIMMER: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-05-25T06:23:33.802Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-KAMMERL api request 10: Requesting new SID
[2019-5-25 08:23:33] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-1750E-KAMMERL: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-05-25T06:23:33.813Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-KUECHE api request 10: Requesting new SID
[2019-5-25 08:23:33] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-1750E-KUECHE: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-05-25T06:23:33.834Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-ELTERN api request 10: Requesting new SID
[2019-5-25 08:23:33] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-1750E-ELTERN: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-05-25T06:23:33.968Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1750E-ELTERN-2 api request 10: Requesting new SID
[2019-5-25 08:23:33] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-1750E-ELTERN-2: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-05-25T06:23:34.012Z FritzPlatformLUA [LUA Debug] FritzBox7580 api request 52: Ok
2019-05-25T06:23:34.048Z FritzPlatformLUA [LUA Debug] FRITZWLAN-Repeater-1160-TANKRAUM api request 10: Requesting new SID
[2019-5-25 08:23:34] [FritzPlatform] [ERROR] FRITZWLAN-Repeater-1160-TANKRAUM: An error occured while getting state of device led!
TypeError: Cannot read property 'data' of undefined
at DeviceAccessory.getDeviceLED (/usr/local/lib/node_modules/homebridge-fritz-platform/src/accessories/device.js:883:31)
at process._tickCallback (internal/process/next_tick.js:68:7)

At the same time I get Fritz! Box Log the following error message with the IP address of my Homebridge:

25.05.19
08:23:35
Anmeldung an der FRITZ!Box-Benutzeroberfläche von IP-Adresse 192.168.1.109 gescheitert (ungültige Sitzungskennung). Zur Sicherheit werden alle noch gültigen Sitzungen zur IP-Adresse 192.168.1.109 beendet. [4 Meldungen seit 25.05.19 08:23:35]
25.05.19
08:23:33
[FRITZWLAN-Repeater-1750E-ELTERN-2] Anmeldung an der Benutzeroberfläche von IP-Adresse 192.168.1.109 gescheitert (ungültige Sitzungskennung). Zur Sicherheit werden alle noch gültigen Sitzungen zur IP-Adresse 192.168.1.109 beendet.
25.05.19
08:23:33
[FRITZWLAN-Repeater-1750E-ELTERN] Anmeldung an der Benutzeroberfläche von IP-Adresse 192.168.1.109 gescheitert (ungültige Sitzungskennung). Zur Sicherheit werden alle noch gültigen Sitzungen zur IP-Adresse 192.168.1.109 beendet.
25.05.19
08:23:33
[FRITZWLAN-Repeater-3000-ESSZIMMER] Anmeldung an der Benutzeroberfläche von IP-Adresse 192.168.1.109 gescheitert (ungültige Sitzungskennung). Zur Sicherheit werden alle noch gültigen Sitzungen zur IP-Adresse 192.168.1.109 beendet.

Can you please take a look at this error?

Many Thanks!

hey, I do get this warning:

Plugin /usr/lib/node_modules/homebridge-fritz-platform requires Node version of ^10.15.3 which does not satisfy the current Node version of v8.11.1. You may need to upgrade your installation of Node.

what could I do? how to update this. apt-get says it is uptodate. and I thought I installed it via apt-get.

thank you !!

dect 2 (as plug) start off also if on router config is off.
impossible to set users name of plugs

please give us plug temp and watt measure, your plugin is great but for me not usable for this reason
thanks for your work

Wenn durch Änderung der Temperatur auch automatisch der Modus geändert wird, ist die Target Temp die aktuelle Temperatur + heat oder coolValue und nicht die von mir eingestellte Temperatur.

Verschiedene Szenarien:

1. Im Raum sind es 20°, Target sind 20°, Modus ist Cooling
2. Target wird auf 22° gesetzt
3. Modus ändert sich auf Heating
4. Target ist nun 25° (aktuelle Temp + 5°)

1. Im Raum sind es 20°, Target sind 20°, Modus ist Heating
2. Target wird auf 22° gesetzt
3. Modus ändert sich nicht
4. Target bleibt bei 22°

Um also beim 1. Szenario die Temperatur auf 22° zu setzen muss man entweder zuerst den Heating Button drücken und dann die Temperatur einstellen oder die Temperatur 2x einstellen.
Das ist insbesondere bei Automatisierungen problematisch

Die ganze Funktionalität um die Modi erschließt sich mir auch nicht so wirklich.

Ich glaube ein relativ "einfacher" Fix wäre es die komplette Funktion mit dem heatValue und coolValue zu entfernen. Die Anzeige ob nun geheizt oder "gekühlt" wird ist ja an sich nicht schlecht, passt aber auch nicht wirklich zu einem Thermostat.

Oder es muss sichergestellt werden, dass zuerst der Befehl heating oder cooling gesendet wird und erst danach die eingestellte Temperatur.

Hey SeydX,

with me with outgoing calls in the Telegram message always only "Unknown" indicated. In the logfile, however, the number is displayed. Do you have to add another entry in the config? With incoming calls everything works perfectly.

Is it also possible that the name is displayed in the phone book even with outgoing calls? As with incoming phone calls.

Thank you for your help!

Describe the bug
I would like to limit the callmonitor to certain numbers only, but it is always triggered even on numbers not included in incomingTo.
Is there a certain format of the numbers expected? Only the number, including city prefix, including country prefix with 00 or +?
Any hints appreciated!

Hi,

ist es möglich die Energieanzeige in Eve darstellen zu lassen? Beispielsweise könnte man damit Push-Benachrichtigungen triggern, wenn die Energie an der Steckdose einen bestimmten Wert erreicht hat.

VG

Hello SeydX,

turning on the LEDs on the Fritz Repeater 3000 does not work.
The LEDs can be switched off but not switched on again.

It would be great if you could check that and fix it!

Would it also be possible to control the brightness of the Fritz 3000 LED's via the plugin?

Thank you for your great work!

Hi,

I updated yesterday to latest version.
It is running fine until now.
I used from history an additional plugin for fritz: homebridge-fritz for DECT 200.
But I want to get rid of this and use this instead.

My config is working fine, until I add the smarthome block.
If I add it I get the attached error .

My config is the following:
{ "platform": "FritzPlatform", "devices":{ "Fritz!Box":{ "host":"192.168.XX.XX", "master":true, "port":49000, "username":"USERNAME", "password":"PASSWORD", "type":"cable", "wifi2":true, "wifi5":true, "wifiGuest":true, "phoneBook":true, "wps":true, "aw":true, "deflection":false, "led": true, "lock":true, "beta":false, "mesh":false } }, "smarthome": { "Rack DECT 200":{ "ain":"111111111111", "type":"switch", "tempSensor":true, "unit":"celsius" } }, "broadband":{ "active":true, "measureTime":5, "polling":30 }, "delay":60, "polling":5, "timeout": 5 }

The error what I get is the following:

When I remove this block:
"smarthome": { "Rack DECT 200":{ "ain":"111111111111", "type":"switch", "tempSensor":true, "unit":"celsius" } },
...everything is working fine.

It seems to me that the plugin will not trigger an update.

Hallo nochmal,

der phoneBook-Config-Eintrag bleibt nicht bestehen. Ist das gewollt? (FB 6490 KDG)

Ich bilde mir ein, dass das mal funktionierte. Zumindest hatte ich irgendwann schon mal im Log "phonebook..." Einträge gesehen.

Hallo,

ist es mit V4 nötig, dass die Homebridge direkt mit der Fritzbox verbunden sein muss? Mein Setup ist nämlich: Homebridge --> Router --> Fritzbox statt Homebridge --> Fritzbox. In Version 3 hat das sehr gut so funktioniert. Mit V4 geht es nicht, trotz manueller Eingabe der devices. Sie werden nach jedem Homebridge Restart wieder gelöscht. Ein Test ohne den Router als Mittelglied hat gut funktioniert, nach Umstellung des WLAN der Homebridge wieder zurück auf den Router wurden die devices jedoch wieder automatisch gelöscht.

Hi there,

I tried out the presence feature (my main feature in this plugin), but sadly it does not work very well. It seems like only the first and the last device is updated correctly.

E.g.:

    "presence": {
        "anyoneSensor": true,
        "delay": 30,
        "type": "motion",
        "devices": {
          "Handy 1": "MAC", // connected -> plugin shows connected -> correct
          "Handy 2": "MAC", // connected -> plugin shows DISCONNECTED -> BUG
          "Handy 3": "MAC", // disconnected-> plugin shows disconnected -> correct
          "Handy 4": "MAC", // connected -> plugin shows DISCONNECTED -> BUG
          "Handy 5": "MAC"  // disconnected-> plugin shows disconnected -> correct
        }
      }

On startup I get the message [FritzBox] [INFO] Welcome at home Handy 1 and a few lines later it prints [FritzBox] [WARN] Handy 5: Switching to no presence.
The status is correct for these two ones, but your plugin does not detect (or even check) the other devices (Handy 2 and 4 were connected to the network as well).

Edit: Works fine on version 2.6.4, just not with the latest one.

Best regards

Describe the bug
not working switches,..

To Reproduce
Steps to reproduce the behavior:
I have pretty much the standard config

Screenshots

Desktop (please complete the following information):

• OS: [latest]
• Browser [eve app]

unclear statements:
incoming and outgoing calls shows yes or no,. it actually shows yes, but there have been none.
presences are shown as away, although all are present.

is there a possibility to add e.g. the GuestWifi tap to the generell screen. I can add it as a scene, but not as a switch/bottom in the home-screen of e.g. eve-app or apples home-app.

Config:
{ "platform": "FritzPlatform", "devices": { "FritzBox": { "name": "Fritz common name", "master": true, "host": "x.x.x.1", "username": "me", "password": "password", "type": "cable", "wifi2": false, "wifi5": false, "wifiGuest": true, "phoneBook": true, "wps": false, "aw": true, "deflection": false, "led": true, "lock": false, "strictSSL": true, "beta": false, "mesh": false, "presence": { "me": "10.0.1.15", "you": "10.0.1.3", "Anyone": "" }, "anyone": true, "delay": 90, "onDelay": 15 } } },

Do I have forgotten anything?

Hi @seydx.
Thanks for this really great plugin (like all of your plugins 😄).
For me the reboot toggle don’t work.
I have a 7590 with firmware 7.10.

Hey,

I setted up a new HomeBridge Server. After enabling all devices in config, all switches for "options" are not visible.

"options": {
"wifi2": [
true,
true
],
"wifi5": [
true,
true
],

These switches should enable it, right?? If so, then this doesn't work :-(

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
i add a FRTIZ!Powerline 1260E to the config but it does not work

"FRITZ!Powerline 1260E": {
"disable": false,
"ip": "192.168.10.4",
"port": 49000,
"username": "pi",
"password": "********",
"led": true,
"wifi": {
"2.4ghz": true,
"5ghz": true,
"guest": false
}
}

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.
her is the error from the homebridge log

[2018-7-12 11:29:24] [FritzBox] [ERROR] FRITZ!Powerline 1260E: An error occured by getting device state!
Jul 12 11:29:24 MiniServer homebridge[7530]: [2018-7-12 11:29:24] [FritzBox] [ERROR] {
Jul 12 11:29:24 MiniServer homebridge[7530]: "errorCode": "ESOCKETTIMEDOUT",
Jul 12 11:29:24 MiniServer homebridge[7530]: "serviceType": "urn:dslforum-org:service:WLANConfiguration:1",
Jul 12 11:29:24 MiniServer homebridge[7530]: "action": "GetInfo",
Jul 12 11:29:24 MiniServer homebridge[7530]: "device": "FRITZ!Powerline 1260E",
Jul 12 11:29:24 MiniServer homebridge[7530]: "host": "192.168.10.4"
Jul 12 11:29:24 MiniServer homebridge[7530]: }

Hi there,

could you please add an option that marks the power-switch of the Fritz!Box device as read-only. I do not need to switch it off remotely and I already pressed the switch once by accident 😛

I don't know if the HAP specification allows to revoke write-access to the On characteristic, but as a workaround you could just ignore the Set command in your plugin for this specific power switch.

Best regards

Good morning, I have tested version 2.6.2. It works all but deflection and it still can not be turned on or off. In the log it is displayed but nothing happens on the Fritzbox.

The new function refresh wifi canal also works, but maybe the name refresh wifi channel would be better here .-)?

Greeting Nastra

I have four DECT 301 Thermostats which are in two seperate Rooms. If I want to turn them on/off all together with just one command I need to put them in a group. Unfortunately there seems to be no grouping option for them.

I have all devices in the homekit visible, but all are greyerd out and not updated.
In the homebridge log I find this:
[2019-5-22 09:35:16] [FritzPlatform] [INFO] Adding new accessory: FRITZ!Box 6490 Cable (kdg)
[2019-5-22 09:35:16] [FritzPlatform] [INFO] FRITZ!Box 6490 Cable (kdg): Successfully logged in!
[2019-5-22 09:35:17] [FritzPlatform] [INFO] Configuring accessory from cache: Rack
[2019-5-22 09:35:18] [FritzPlatform] [INFO] Configuring accessory from cache: Rack Temperature

Seems to be working for me ....

My config is:
{
"platform": "FritzPlatform",
"devices": {
"FRITZ!Box 6490 Cable (kdg)": {
"active": true,
"host": "XXX",
"port": 49000,
"username": "XXX",
"password": "XXX",
"type": "cable",
"master": true,
"mesh": false,
"readOnly": false,
"options": {
"reconnect": true,
"wifi2": [
false,
false
],
"wifi5": [
false,
false
],
"wifiGuest": [
false,
false
],
"phoneBook": false,
"wps": [
false,
false
],
"aw": [
false,
false
],
"deflection": [
false,
false
],
"led": [
false,
false
],
"lock": [
false,
false
]
}
}
},
"smarthome": {
"Rack": {
"active": true,
"ain": "XXX",
"tempSensor": true,
"devType": "switch"
}
},
"broadband": {
"active": true,
"measureTime": 5
},
"callmonitor": {
"active": false,
"ip": "0.0.0.0",
"port": 1012,
"country": "",
"incomingTo": [],
"outgoingFrom": []
},
"presence": {
"user": [
{
"active": false,
"name": "Test User",
"address": "0.0.0.0"
}
],
"anyone": false,
"offDelay": 90,
"onDelay": 15
},
"wol": [
{
"active": false,
"name": "Test Device",
"address": "00:00:00:00:00:00"
}
],
"alarm": {
"active": false,
"telNr": "",
"duration": 30
},
"wakeup": {
"active": false,
"internNr": "",
"duration": 30
},
"ringlock": {
"active": false,
"DECTphones": 1,
"start": "11:00",
"end": "22:00"
},
"extReboot": {
"active": false,
"cmdOn": "",
"cmdOff": ""
},
"telegram": {
"active": false,
"token": "",
"chatID": "",
"presence": {
"in": "",
"out": "",
"anyoneIn": "",
"anyoneOut": ""
},
"callmonitor": {
"incoming": "",
"disconnected": ""
},
"alarm": {
"activated": "",
"deactivated": ""
},
"extReboot": {
"start": "",
"finish": ""
}
},
"delay": 60,
"OnDelay": 15,
"polling": 5,
"timeout": 5,
"clearCache": false,
"debug": true,
"disableAutoSearch": false,
"disableAutoConfig": false
},

I have in addition to that the plugin homebridge-fritz-eve installed and a FritzBox with 7.01 and am not able to update.

With using the debug I get:
2019-05-22T07:47:17.811Z FritzPlatform Rack Temperature: No device with AIN: 087610136610 found or not intialized yet!
2019-05-22T07:47:22.811Z FritzPlatform Rack: No device with AIN: XXX found or not intialized yet!

The number is correct....

It seems that there is for me a problem connecting to the box correct.

The rest of the Plugin works as expected, incoming calls are reported within seconds, but the Presence part doesn't update correctly. When I leave my home, my Fritzbox marks me as away but the change is not reported to the Home App, in there I am still at Home.

Scenario:
Raspberry 3b+ with Homebridge v0.4.46
Fritzbox 7590 (up-to-date)
Homebridge-Fritz-Platform (up-tp-date) with example Config (logins and Adress Changed)
Presence Plugin based on Mac-Adress

After updating to v4.x a SmartHome device (Fritz!Dect outlet) connected to the FritzBox is no longer avaiable.

The FritzBox itself is found.

In my configuration I added:

"smarthome": {
"Espressomaschine": {
"active": true,
"devtype": "switch",
"ain": "",
"tempSensor": true,
"unit": "celsius"
}
},

I tried "type": "switch" and "devtype": "switch"; found both in the documentation.
I tried with an without the "active" tag.

I use the oznu/homebridge docker image, the homebridge version is 0.4.49.

With 3.x I was able to use the outlet as expected.

Any idea how to analyze this further?

Regards
Bernd

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
I would like to have a switch to enable the Guest WiFi via HomeKit App without using any third party app.

Thanks for that plug-in, really nice work :)

Describe the bug
When running a HomeKit app and logging notifications, I see that the motion sensor that is installed as part of the presence function emits a motion detected notification once per second. I think this is not a good idea for the overall fidelity of a HomeKit installation, as HomeKit can't really deal well with too high traffic.

To Reproduce
Configure the presence feature with at least one device. I used a delay of 10, but that doesn't make a difference.

Expected behavior
See characteristic notifications in HomeKit when the state of the motion sensor changes, not on a regular interval, particularly not so often.

Hallo irgendwie will das plugin nicht mehr seit einem neuen update von der platform und ich bekomme die autoconfig Methode nicht hin und die alternativen bekomme ich in meine config.json nicht integriert. wenn ich meine alte config die funktioniert hat einfüge ändert er sie jedesmal wieder in diese hier

{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "Home Smart Home",
"platforms": [
{
"platform": "Hue",
"users": {
"XXXXXXXX": "XXXXXXXX"
},
"lights": true,
"hosts": "192.168.5.8"
},
{
"platform": "Logi Circle Controls",
"name": "Logi Circle Controls",
"email": "XXXXXXXX",
"password": "XXXXXXXX",
"accessories": [
{
"deviceId": "XXXXXXXX",
"name": "Wohnzimmer Camera",
"camera": {
"name": "Camera",
"disabled": false
},
"led": {
"name": "LED",
"disabled": true
},
"privacyMode": {
"name": "Privat Modus",
"disabled": false
},
"recording": {
"name": "Aufzeichnung",
"disabled": true
},
"nightVisionMode": {
"name": "Night Vision",
"disabled": true
},
"nightVisionIR": {
"name": "Night IR",
"disabled": true
}
}
]
},
{
"platform": "FritzPlatform",
"devices": {},
"smarthome": {
"Test Contact Sensor": {
"active": false,
"ain": "01234567890",
"devType": "contact"
},
"Test Thermostat Device": {
"active": false,
"ain": "01234567890",
"heatValue": 5,
"coolValue": 5,
"windowSensor": false,
"devType": "thermostat"
},
"Test Outlet Device": {
"active": false,
"ain": "01234567890",
"tempSensor": false,
"devType": "switch"
}
},
"callmonitor": {
"active": false,
"ip": "0.0.0.0",
"port": 1012,
"country": "",
"incomingTo": [],
"outgoingFrom": []
},
"presence": {
"user": [
{
"active": false,
"name": "Test User",
"address": "0.0.0.0"
}
],
"anyone": false,
"offDelay": 90,
"onDelay": 15,
"ping": false
},
"wol": [
{
"active": false,
"name": "Test Device",
"address": "00:00:00:00:00:00"
}
],
"phoneBook": {
"active": false,
"blacklists": []
},
"alarm": {
"active": false,
"telNr": "",
"duration": 30
},
"wakeup": {
"active": false,
"internNr": "",
"duration": 30
},
"ringlock": {
"active": false,
"DECTphones": 1,
"start": "11:00",
"end": "22:00"
},
"broadband": {
"active": false,
"measureTime": 5
},
"extReboot": {
"active": false,
"cmdOn": "",
"cmdOff": ""
},
"telegram": {
"active": false,
"token": "",
"chatID": "",
"presence": {
"in": "",
"out": "",
"anyoneIn": "",
"anyoneOut": ""
},
"callmonitor": {
"incoming": "",
"disconnected": ""
},
"alarm": {
"activated": "",
"deactivated": ""
},
"extReboot": {
"start": "",
"finish": ""
}
},
"polling": 10,
"timeout": 10,
"clearCache": false,
"debug": false,
"disableAutoSearch": false,
"disableAutoConfig": false
},
{
"platform": "MiLight",
"name": "MiLight",
"bridges": [
{
"ip_address": "192.168.5.12",
"version": "v6",
"lights": {
"rgbw": [
null,
"Flur Licht",
null,
null
],
"bridge": [
null
]
},
"repeat": 1,
"delay": 50
}
]
},
{
"name": "Config",
"port": 8080,
"auth": "form",
"theme": "dark-mode",
"restart": "sudo -n systemctl restart homebridge",
"temp": "/sys/class/thermal/thermal_zone0/temp",
"tempUnits": "c",
"sudo": true,
"log": {
"method": "systemd",
"service": "homebridge"
},
"platform": "config"
}
],
"accessories": [
{
"accessory": "RaspberryPiTemperature",
"name": "RaspberryPi CPU Temperature"
},
{
"timeout": 5000,
"mac": "XXXXXXXX",
"version": 6,
"secure": false,
"disabled": [],
"password": "XXXXXXXX",
"pollingInterval": 240,
"accessory": "Synology",
"doPolling": true,
"ip": "192.168.5.9",
"account": "XXXXXXXX",
"name": "Server",
"port": "5000"
},
{
"ip": "192.168.5.2",
"accessory": "lgtv-2012",
"max_volume": 15,
"on_command": "MUTE",
"min_volume": 2,
"pairingKey": "XXXXXXXX",
"name": "TV"
},
{
"accessory": "marantz-volume",
"name": "Denon X4300H",
"host": "192.168.5.7:8080"
}
],
"id": "config"
}

Homebridge: Version 0.4.50
Node: node.js v10.16.0
Fritz Platform: 4.1.0

ich hoffe ihr könnt mir helfen am 10.6 hatte alles noch funktioniert

Hello,
my Homebridge runs on a Synology NAS. This plugin only works after deactivating the Synology Firewall. I could open some ports on the NAS but I couldn't figure out witch port (range).
Do you know what port has to be opened? If it helps, I'am using a FritzBox 7490.

Hey there,

thanks for your work on this!
It seems like in the most recent version DECT200's temperature readings are broken.
The switch itself seems to be working, however temperature readings are a constant 0.0 with no data points in the Fakegato history.

Is it possible for you to add the markdown feature for the telegram notifications?
Would be really nice.

The status of my Fritzbox in HomeKit stayed ON, although the internet connection was down for several hours.
The status should switch to OFF without Internet imho.

Hey SeydX,

thanks for your great work. I control my three fritz boxes with your great plugin. In the beginning I reboot some boxes, when tuning all lights off... For now I'm in read only mode. Is there a way, which don't show the toggles in ro-mode in Homekit?

Would be a small but great imporvement.

Best regards,
patrick

Hey everyone,

as some of you may know, I am currently working on the v4 of my Fritz Platform plugin. Most of it is already done. Currently I'm looking for beta testers to wipe out the remaining bugs and / or incorporate new requests.

Note: Before you install the new plugin, I recommend you to delete the old plugin and remove it from HomeKit! And also delete the accessories and persist folders (only if u are using the v3.x)

The new version is completely rewritten, supports async/await and should be faster than the previous versions. It has a auto config generator and detects automatically all FRITZ!Box devices in the network. I fixed also some bugs and improved i.e smarthome etc (i can‘t test smarthome properly due to the reason i don‘t have smarthome devices here, so every bug is welcome)

The plugin supports at the moment only devices with MESH! Devices without MESH will be added very soon!

To install the beta version, run following command

sudo npm i -g homebridge-fritz-platform@dev

Here you will find some information about first steps with version 4

https://github.com/SeydX/homebridge-fritz-platform/blob/dev/FIRSTSTART.md

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

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

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

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Describe the bug
When removing the Fritz-Platform details from the config.json file it shows still after a restart
all the devices from the previous config.json. It is not possible to clear all the devices which had been added to config.json even not after a full uninstall of Fritz-Platform.

To Reproduce
Steps to reproduce the behavior:

1. Go to –> remove all details in "FritzPlatform' in the config.json file and after a restart of the homebridge it will show you all the FritzPlatform devices/sensors again which should not happen actually.

Expected behavior

1. a way to clear the FritzPlatform sensors totaly if want to refresh all the sensors in FritzPlatform
2. recognition of the "devices" does not work when there are more than 2 devices (smartphones)
3. Uninstallation of the full FritzPlatform

Hi,

I get this error

Aug 31 10:37:26 homebridge homebridge[18129]: [2018-8-31 10:37:26] [FritzBox] [INFO] Incoming call from: to 0314567890
Aug 31 10:37:27 homebridge homebridge[18129]: HAP Warning: Characteristic undefined not in required or optional characteristics for service 67bc5512-9024-45e5-a0ef-6302b7785bef. Adding anyway.
Aug 31 10:37:27 homebridge homebridge[18129]: ^ For: UV Sensor
Aug 31 10:37:37 homebridge homebridge[18129]: [2018-8-31 10:37:37] [FritzBox] [INFO] Call disconnected
Aug 31 10:37:45 homebridge homebridge[18129]: [2018-8-31 10:37:45] [FritzBox] [ERROR] FritzBoxAn error occured by getting device state!
Aug 31 10:37:45 homebridge homebridge[18129]: [2018-8-31 10:37:45] [FritzBox] [ERROR] {
Aug 31 10:37:45 homebridge homebridge[18129]: "response": "OK",
Aug 31 10:37:45 homebridge homebridge[18129]: "responseCode": 200,
Aug 31 10:37:45 homebridge homebridge[18129]: "tr064": "Auth. failed",
Aug 31 10:37:45 homebridge homebridge[18129]: "tr064code": "503",
Aug 31 10:37:45 homebridge homebridge[18129]: "fault": "UPnPError",
Aug 31 10:37:45 homebridge homebridge[18129]: "faultcode": "s:Client",
Aug 31 10:37:45 homebridge homebridge[18129]: "serviceType": "urn:dslforum-org:service:WANPPPConnection:1",
Aug 31 10:37:45 homebridge homebridge[18129]: "action": "GetStatusInfo"
Aug 31 10:37:45 homebridge homebridge[18129]: }

I don't know which authentication is failing. the call monitor does work

See config.json part.
{
"platform": "FritzPlatform",
"name": "FritzBox",
"host": "192.123.4.5",
"port": 49000,
"type": "dsl",
"timeout": 5,
"username": "user",
"password": "pasword!",
"polling": 10,
"callmonitor": {
"disable": false,
"ip": "192.123.4.5",
"port": 1012,
"telegram": false,
"token": "TOKENHERE",
"chatID": "CHATIDHERE",
"messages": {
"incoming": "Incoming call from @ to %",
"disconnected": "Incoming call from @ was disconnected!"
},
"presence": {
"anyoneSensor": true,
"delay": 30,
"type": "motion",
"telegram": false,
"token": "TOKENHERE",
"chatID": "CHATIDHERE",
"messages": {
"sensorOn": "Welcome at home @",
"sensorOff": "Bye bye @",
"anyoneOn": "Prsence detected at home!",
"anyoneOff": "No one at home!"
},
"devices": {
"Peter": "00:11:22:33:44.55",
"Rien": "192.123.4.6"
}
}
}
},

Any clues?

The call monitor-function would be great for auto-pause/mute tv on incoming calls or other actions/automations. But as we have several handsets with different numbers, I'd like to have selective actions for the different numbers/lines for automation like mute the tv in the living room when incoming call on line 1 / living room, telegram for incoming calls on line 2 when away, ...

Hi SeydX,

It seems that the phonebook data is not stored or not being used.
What is it I am doing wrong?
Please help.

I have correctly activated the "phoneBook": true,
Also the CallMonitor is activated combinded with Telegram, which is working fine.

Incoming call! 012345678 ( No name )
Incoming call - 012345678 ( No name ) - was disconnected!

Thank you,
Pit

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
LED on off switch for the main Router

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
when i add the main router as repeater it work for now.
can you at the led var to the main router config too please?

Additional context
Add any other context or screenshots about the feature request here.

Hallo,

ich habe 3 iPhones bei mir als Presence Sensoren eingerichtet. Nun gibt es in der Fritzbox das Problem, dass WLAN-Geräte, die sich gar nicht am Router befinden, trotzdem noch als verbunden angezeigt werden. Das lässt natürlich das Plugin fälschlicherweise annehmen, dass das Gerät noch im Haus präsent ist.

Kann hier weitere Abfrage in Form eines Ping eingebaut werden? Denn anpingen kann man das Gerät auf seine IP nicht mehr, auch wenn es die Fritzbox noch als verbunden anzeigt.

I get the following error:

[2018-8-9 16:32:47] [FritzBox] [ERROR] An error occured by initializing device, trying again...
[2018-8-9 16:32:47] [FritzBox] [ERROR] {
"errno": "ECONNRESET",
"code": "ECONNRESET",
"syscall": "read"
}

Probably, I've done something wrong. :-) I'm rather new to this.

My platforms section in config.json:
"platforms": [
{
"platform": "FritzPlatform",
"name": "FritzBox",
"host": "192.168.77.1",
"port": 444,
"type": "cable",
"timeout": 5,
"username": "pi",
"password": "test",
"polling": 5
}
]

Hey SeydX,

Unfortunately I have to ask you for help again.
Recently I get the same error message again and again and then the respective function can not be executed anymore. Even a restart of the Homebridge or the Fritz devices has not been able to fix the error.
The following error messages I get displayed again and again:

[2019-6-6 9:10:01 PM] [FritzPlatform] [ERROR] FritzBox7580 Deflection: An error occured while getting new state!

[2019-6-6 9:10:01 PM] [FritzPlatform] [ERROR] FritzBox7580 WifiGuest: An error occured while getting new state!