Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapter restarts if WLAN is deactivated #527

Open
mc-0815 opened this issue Jun 29, 2024 · 2 comments
Open

Adapter restarts if WLAN is deactivated #527

mc-0815 opened this issue Jun 29, 2024 · 2 comments

Comments

@mc-0815
Copy link

mc-0815 commented Jun 29, 2024

Describe the bug
When the adapter instance starts the SOAP Call for WLAN Configuration ends up with a 500 error, the adapter instance throws a fatal error and restarts. As my fritzbox 7412 has WLAN deactivated, I assume this is the cause of the error.

To Reproduce
Just deactivate your WLAN on your fritzbox and restart the adapter instance.

Expected behavior
Adapter is able to handle such configuration as those are quite common setups.

Screenshots & Logfiles
iobroker logs:

Error: sendSOAPActionRequest Error action=GetInfo serviceType=urn:dslforum-org:service:WLANConfiguration:1: 500 - {"code":500}

XML body of the SOAP response (via network capture)

    <?xml
        version="1.0"
        ?>
    <s:Envelope
        xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
        s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
        <s:Body>
            <s:Fault>
                <faultcode>
                    s:Client
                    </faultcode>
                <faultstring>
                    UPnPError
                    </faultstring>
                <detail>
                    <UPnPError
                        xmlns="urn:dslforum-org:control-1-0">
                        <errorCode>
                            820
                            </errorCode>
                        <errorDescription>
                            Internal Error
                            </errorDescription>
                        </UPnPError>
                    </detail>
                </s:Fault>
            </s:Body>
        </s:Envelope>

Versions:

  • Adapter version: 4.3.0
  • JS-Controller version: 5.0.19
  • Node version: v18.17.1
  • Operating system: Debian GNU/Linux 11 (bullseye)

Additional context
Add any other context about the problem here.

@Apollon77
Copy link
Member

Bitte einen Log von so einem Adapter crash inkl. Stack trace bitte posten.

@mc-0815
Copy link
Author

mc-0815 commented Jun 30, 2024

Da habe ich mich vielleicht falsch ausgedrückt, er crashed nicht, er startet (vermutlich aufgrund des 500er SOAP Error) neu:

2024-06-29 09:34:49.086  - info: host.iobroker Restart adapter system.adapter.tr-064.0 because enabled
2024-06-29 09:35:19.152  - info: host.iobroker instance system.adapter.tr-064.0 started with pid 3081703
2024-06-29 09:35:22.311  - info: tr-064.0 (3081703) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.tr-064, node: v18.17.1, js-controller: 5.0.19
2024-06-29 09:35:23.820  - error: tr-064.0 (3081703) Error: sendSOAPActionRequest Error action=GetInfo serviceType=urn:dslforum-org:service:WLANConfiguration:1: 500 - {"code":500}
2024-06-29 09:35:23.821  - error: tr-064.0 (3081703) ~
2024-06-29 09:35:23.822  - error: tr-064.0 (3081703) ~~ Fatal error. Can not connect to your FritzBox.
2024-06-29 09:35:23.823  - error: tr-064.0 (3081703) ~~ If configuration, network, IP address, etc. ok, try to restart your FritzBox
2024-06-29 09:35:23.824  - error: tr-064.0 (3081703) ~
2024-06-29 09:35:23.825  - warn: tr-064.0 (3081703) Terminated (JS_CONTROLLER_STOPPED): Fatal error. Can not connect to your FritzBox.
2024-06-29 09:35:24.398  - error: host.iobroker instance system.adapter.tr-064.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

@mc-0815 mc-0815 changed the title Adapter crashes if WLAN is deactivated Adapter restarts if WLAN is deactivated Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants