FritzSmart and FritzBox does not ring the phones on Trixie

Begonnen von HarryT, 27 April 2026, 13:07:35

Vorheriges Thema - Nächstes Thema

HarryT

Hi

The fritzbox module does not ring the phone with my latest installation on RaspberryPi/Trixie. On bookworm it rings fine. So I decided to try on FritzSmart but with the same result. 

The command used is

set FritzSmart ring 9 5
call instead of ring gives the same result.

My definitions:
define FritzSmart FritzSmart nnn.nnn.nnn.nnn
attr FritzSmart room Hardware
attr FritzSmart verbose 3


In the logging I get:

2026.04.27 12:54:19 3: [FritzSmart | 7490 | 113.07.62 | Set_Modul.2386] - BASIC:set FritzSmart ring - 9 5
2026.04.27 12:54:24 2: [FritzSmart | 7490 | 113.07.62 | Set_ring_Phone.12809] - SIGNIFICANT:(set ring): $VAR1 = {
          'X_VoIP:1' => {
                          'X_AVM-DE_DialSetConfig' => {
                                                        'response_code' => 'http-code:500',
                                                        'ErrLevel' => '5',
                                                        'faultstring' => 'UPnPError',
                                                        'detail' => {
                                                                      'UPnPError' => {
                                                                                       'errorCode' => '866',
                                                                                       'errorDescription' => 'second factor authentication required',
                                                                                       'xmlns' => 'urn:dslforum-org:control-1-0'
                                                                                     }
                                                                    },
                                                        'response_error' => '500 Internal Server Error',
                                                        'faultcode' => 's:Client'
                                                      }
                        }
        };

Anybody understands the problem and knows how to solve it?
FHEM 6.4 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz), Raspberry Pi4 and RaspberryPi 5 for testing
German reading skills are good.

JoWiemann

Hi Harry,

As the maintainer of the modules, I'm not currently using the Raspberry Pi/Trixie combination. Therefore, I can't help you with that.

However, after starting FHEM, you could check the log for error messages related to 72_FRITZBOX or 72_FritzSmart. For example, missing Perl modules will be listed there.

Regards, Jörg
Jörg Wiemann

RPi 4 B mit 4 GByte bookworm, COC (868 MHz), CUL V3 (433.92MHz SlowRF); FHEMduino, Aktuelles FHEM; zigbee2mqtt

ioBroker als Datenlieferant für z.B. Anker, Samsung

RalfRog

I'm using debian trixie on Proxmox and ring works fine => Module FRITZBOX, VERSION 08.20.10 frozen
Can't test FritzSmart as it is remote.

to compare -> log says:
2026.04.27 15:57:28.886 3: [Fritzbox | 7590 | 154.08.20 | Set.2130] - BASIC:set Fritzbox ring - 611 5
Regards Ralf
FHEM VM Debian13 (trixie) auf Proxmox VE9  (Futro S740) - nanoCUL, HM-MOD-RPI-PCB und MAX!Cube über LAN
HM- Fensterkontakte, UP-Schalter, Bewegungsmelder und ein Rauchmelder sowie Shelly 3EM, 1PM, PlugS und IT Schaltsteckdosen

RalfRog

Also "ring 9 5" lets all DECT-Phones and internal SIPs ring.
FHEM VM Debian13 (trixie) auf Proxmox VE9  (Futro S740) - nanoCUL, HM-MOD-RPI-PCB und MAX!Cube über LAN
HM- Fensterkontakte, UP-Schalter, Bewegungsmelder und ein Rauchmelder sowie Shelly 3EM, 1PM, PlugS und IT Schaltsteckdosen

RalfRog

uuups..  meine 7590 mal schnell mit FritzSmart definiert und "ring 9 5" abgesetzt  ==> Restart von FHEM. Blöd - config noch nicht abgespeichert.

Log:
...
2026.04.27 16:35:39.209 3: [FritzboxS | 7590 | 154.08.20 | Attr_Modul.2097] - BASIC:Attr set INTERVAL -> Neustart internal Timer - APICHECKED = 1
2026.04.27 16:35:39.245 3: [FritzboxS | 7590 | 154.08.20 | Attr_Modul.2097] - BASIC:Attr set disable -> Neustart internal Timer - APICHECKED = 2
2026.04.27 16:35:39.246 3: [FritzboxS | 7590 | 154.08.20 | Readout_Start.5309] - BASIC:Old readout process still running. Killing old process HASH(0x557c95913990)
2026.04.27 16:35:39.246 3: Timeout for Fritz::Fritz_Readout_API_Check reached, terminated process 19134
2026.04.27 16:35:39.246 2: [FritzboxS | 7590 | 154.08.20 | Readout_Aborted.9474] - SIGNIFICANT:Error: [285 | BlockingKill] Timeout during API check.
2026.04.27 16:35:58.814 3: [FritzboxS | 7590 | 154.08.20 | Readout_API_Check.10521] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200
2026.04.27 16:36:14.870 3: [FritzboxS | 7590 | 154.08.20 | Set_Modul.2176] - BASIC:set FritzboxS ring - 9 5
2026.04.27 16:36:15.686 2: [FritzboxS | 7590 | 154.08.20 | Set_ring_Phone.12640] - SIGNIFICANT:(set ring): $VAR1 = {
          'X_VoIP:1' => {
                          'X_AVM-DE_DialSetConfig' => {
                                                        'response_code' => 'http-code:500',
                                                        'detail' => {
                                                                      'UPnPError' => {
                                                                                       'errorDescription' => 'second factor authentication required',
                                                                                       'xmlns' => 'urn:dslforum-org:control-1-0',
                                                                                       'errorCode' => '866'
                                                                                     }
                                                                    },
                                                        'ErrLevel' => '5',
                                                        'faultcode' => 's:Client',
                                                        'response_error' => '500 Internal Server Error',
                                                        'faultstring' => 'UPnPError'
                                                      }
                        }
        };

2026.04.27 16:36:46.402 3: [FritzboxS | 7590 | 154.08.20 | Set_Modul.2176] - BASIC:set FritzboxS ring - 611 5
2026.04.27 16:36:46.403 3: [FritzboxS | 7590 | 154.08.20 | Readout_SetGet_Start.9637] - BASIC:restarting internal Timer: next set/get: ring will be processed
Undefined subroutine &main::Fritz_Readout_SetGet_Start called at fhem.pl line 3528.
2026.04.27 16:38:18.037 1: Including fhem.cfg
2026.04.27 16:38:19.254 2: DBLogging - Subprocess >19216< initialized ... ready for non-blocking operation
2026.04.27 16:38:19.421 3: WEB: port 8083 opened
2026.04.27 16:38:19.424 3: WEBTAB: port 8084 opened
...

Dann nachher nochmal mit Ruhe.
FHEM VM Debian13 (trixie) auf Proxmox VE9  (Futro S740) - nanoCUL, HM-MOD-RPI-PCB und MAX!Cube über LAN
HM- Fensterkontakte, UP-Schalter, Bewegungsmelder und ein Rauchmelder sowie Shelly 3EM, 1PM, PlugS und IT Schaltsteckdosen

RalfRog

I just defined my 7590 (154.08.20) with FritzSmart. To be honest not the latest module version (-> 26.03.31).
With ...ring 611 5...  I got a similar output as HarryT. WebIF says "Fritz_Readout_SetGet_Start done":
2026.04.27 17:08:09.344 3: [FritzboxS | 7590 | 154.08.20 | Set_Modul.2176] - BASIC:set FritzboxS ring - 611 5
2026.04.27 17:08:10.608 2: [FritzboxS | 7590 | 154.08.20 | Set_ring_Phone.12640] - SIGNIFICANT:(set ring): $VAR1 = {
          'X_VoIP:1' => {
                          'X_AVM-DE_DialSetConfig' => {
                                                        'faultcode' => 's:Client',
                                                        'faultstring' => 'UPnPError',
                                                        'detail' => {
                                                                      'UPnPError' => {
                                                                                       'errorCode' => '866',
                                                                                       'errorDescription' => 'second factor authentication required',
                                                                                       'xmlns' => 'urn:dslforum-org:control-1-0'
                                                                                     }
                                                                    },
                                                        'response_error' => '500 Internal Server Error',
                                                        'ErrLevel' => '5',
                                                        'response_code' => 'http-code:500'
                                                      }
                        }
        };


I'll update the module and check again.
FHEM VM Debian13 (trixie) auf Proxmox VE9  (Futro S740) - nanoCUL, HM-MOD-RPI-PCB und MAX!Cube über LAN
HM- Fensterkontakte, UP-Schalter, Bewegungsmelder und ein Rauchmelder sowie Shelly 3EM, 1PM, PlugS und IT Schaltsteckdosen

JoWiemann

Hello,

I can reproduce the error now. It will take some time, though.

Greetings Jörg
Jörg Wiemann

RPi 4 B mit 4 GByte bookworm, COC (868 MHz), CUL V3 (433.92MHz SlowRF); FHEMduino, Aktuelles FHEM; zigbee2mqtt

ioBroker als Datenlieferant für z.B. Anker, Samsung

JoWiemann

Hello,

to ensure that the phone connection is only established to the selected phone, the module switches the port for 'click to dial' to the specified phone as the call destination. Since 2017, this change has been protected by an additional confirmation prompt. Therefore, only the target phone specified in the Fritz!Box web interface can be used. I have now commented this out in the program code. No solution for this behavior is known.

Translatet by Google

Greetings Jörg
Jörg Wiemann

RPi 4 B mit 4 GByte bookworm, COC (868 MHz), CUL V3 (433.92MHz SlowRF); FHEMduino, Aktuelles FHEM; zigbee2mqtt

ioBroker als Datenlieferant für z.B. Anker, Samsung

passibe

#8
Given that the error message is:
Zitat von: RalfRog am 27 April 2026, 16:48:36'errorDescription' => 'second factor authentication required',
have you tried simply disabling the "extra confirmation" feature (see here)?
Should be possible from the web interface at System -> FRITZ!Box-Users.

Of course, technically this makes the box less secure.
Although I don't really see a lot of risks with this, unless you give untrusted people access to your non-guest WiFi and/or expose the FB's web interface to the public internet (imo you shouldn't do both things, regardless of "extra confirmation" being enabled; better to use guest WiFi and/or WireGuard instead).

EDIT: Never mind, it seems like the option to disable it was removed: https://fritz.com/en/apps/knowledge-base/FRITZ-Box-7490/3709_Can-additional-confirmation-be-disabled-in-the-FRITZ-Box

If this appears in other places as well, maybe some implementation of oathtool could be added to compute the TOTP from the secret on the fly, just like openconnect does it for accessing a 2FA/TOTP-secured VPN without having to enter the token manually every time.

JoWiemann

A new version will be available via update starting tomorrow.
Jörg Wiemann

RPi 4 B mit 4 GByte bookworm, COC (868 MHz), CUL V3 (433.92MHz SlowRF); FHEMduino, Aktuelles FHEM; zigbee2mqtt

ioBroker als Datenlieferant für z.B. Anker, Samsung