Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Entwicklung
    4. Adapter: Worx Landroid v2.x.x

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Adapter: Worx Landroid v2.x.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • Meistertr
      Meistertr Developer last edited by

      Der Worx server scheint zur zeit offline zu sein

      1 Reply Last reply Reply Quote 0
      • lobomau
        lobomau last edited by

        @Meistertr:

        Der Worx server scheint zur zeit offline zu sein `
        Ah. Deswegen. Da ich über app auch keine Verbindung bekomme, war schon klar, dass es nicht am Adapter liegt.

        Aber trotzdem steht auch im log "logged in as XXXX - user token retrieved from API." Deswegen dachte ich, es findet schon eine Verbindung zum worx server statt.

        landroid-s.0	2017-10-05 08:03:38.709	info	Downloaded guest token
sql.0	2017-10-05 08:03:38.596	info	enabled logging of landroid-s.0.mower.totalTime
sql.0	2017-10-05 08:03:38.596	info	enabled logging of landroid-s.0.mower.totalBladeTime
sql.0	2017-10-05 08:03:38.582	info	enabled logging of landroid-s.0.mower.totalDistance
landroid-s.0	2017-10-05 08:03:38.484	info	starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.landroid-s, node: v6.11.4
host.brix-3150	2017-10-05 08:03:37.195	info	instance system.adapter.landroid-s.0 started with pid 26579
host.brix-3150	2017-10-05 08:03:07.182	info	Restart adapter system.adapter.landroid-s.0 because enabled
host.brix-3150	2017-10-05 08:03:07.182	error	instance system.adapter.landroid-s.0 terminated with code 0 (OK)
Caught	2017-10-05 08:03:07.182	error	by controller[0]: at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38) code: 'CERT_HAS_EXPIRED' }
Caught	2017-10-05 08:03:07.182	error	by controller[0]: at TLSSocket._finishInit (_tls_wrap.js:610:8)
Caught	2017-10-05 08:03:07.182	error	by controller[0]: at TLSSocket.emit (events.js:185:7)
Caught	2017-10-05 08:03:07.181	error	by controller[0]: at emitNone (events.js:86:13)
Caught	2017-10-05 08:03:07.181	error	by controller[0]: at TLSSocket. (_tls_wrap.js:1092:38)
Caught	2017-10-05 08:03:07.181	error	by controller[0]: at Error (native)
Caught	2017-10-05 08:03:07.180	error	by controller[0]: { Error: certificate has expired
landroid-s.0	2017-10-05 08:03:07.142	info	terminating
landroid-s.0	2017-10-05 08:03:07.130	info	cleaned everything up...
landroid-s.0	2017-10-05 08:03:07.128	error	at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
landroid-s.0	2017-10-05 08:03:07.128	error	at TLSSocket._finishInit (_tls_wrap.js:610:8)
landroid-s.0	2017-10-05 08:03:07.128	error	at TLSSocket.emit (events.js:185:7)
landroid-s.0	2017-10-05 08:03:07.128	error	at emitNone (events.js:86:13)
landroid-s.0	2017-10-05 08:03:07.128	error	at TLSSocket. (_tls_wrap.js:1092:38)
landroid-s.0	2017-10-05 08:03:07.128	error	at Error (native)
landroid-s.0	2017-10-05 08:03:07.128	error	Error: certificate has expired
landroid-s.0	2017-10-05 08:03:07.128	error	uncaught exception: certificate has expired
        1 Reply Last reply Reply Quote 0
        • B
          bku last edited by

          Hi,

          meine App funktioniert (jetzt) aber, aber der iobroker-Adapter nicht und auch Eisha's Win-App geht nicht.

          Gruß Bernd

          1 Reply Last reply Reply Quote 0
          • lobomau
            lobomau last edited by

            @bku:

            Hi,

            meine App funktioniert (jetzt) aber, aber der iobroker-Adapter nicht und auch Eisha's Win-App geht nicht.

            Gruß Bernd `
            Stimmt. Bei mir geht jetzt die Handy App, aber nicht der Adapter. Ist es normal, dass da zwei verschiedene API token geholt werden (beispielhaft 111111… und 22222...)?

            host.brix-3150	2017-10-05 12:54:15.115	info	Restart adapter system.adapter.landroid-s.0 because enabled
host.brix-3150	2017-10-05 12:54:15.114	error	instance system.adapter.landroid-s.0 terminated with code 0 (OK)
host.brix-3150	2017-10-05 12:54:15.114	error	Caught by controller[0]: at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38) code: 'CERT_HAS_EXPIRED' }
host.brix-3150	2017-10-05 12:54:15.114	error	Caught by controller[0]: at TLSSocket._finishInit (_tls_wrap.js:610:8)
host.brix-3150	2017-10-05 12:54:15.114	error	Caught by controller[0]: at TLSSocket.emit (events.js:185:7)
host.brix-3150	2017-10-05 12:54:15.114	error	Caught by controller[0]: at emitNone (events.js:86:13)
host.brix-3150	2017-10-05 12:54:15.114	error	Caught by controller[0]: at TLSSocket. (_tls_wrap.js:1092:38)
host.brix-3150	2017-10-05 12:54:15.114	error	Caught by controller[0]: at Error (native)
host.brix-3150	2017-10-05 12:54:15.113	error	Caught by controller[0]: { Error: certificate has expired
landroid-s.0	2017-10-05 12:54:15.072	error	uncaught exception: certificate has expired
landroid-s.0	2017-10-05 12:54:14.846	info	Connecting to MQTT broker
landroid-s.0	2017-10-05 12:54:14.420	info	Fetching root CA
landroid-s.0	2017-10-05 12:54:14.345	info	Certificate retrieved
landroid-s.0	2017-10-05 12:53:57.095	info	API token set to 22222222222222222
landroid-s.0	2017-10-05 12:53:57.094	info	Logged in as email@email.com - user token retrieved from API
landroid-s.0	2017-10-05 12:53:42.939	info	API token set to 111111111111111111
landroid-s.0	2017-10-05 12:53:42.936	info	Downloaded guest token
            1 Reply Last reply Reply Quote 0
            • Meistertr
              Meistertr Developer last edited by

              Die App geht aber auch nicht vollkommen rund. Habe gerade gelesen dass das neu einrichten der App wohl auch zz nicht geht das ist das was die winapp und Adapter beim Start machen. Ich schau es mir noch genauer an, aber ich glaube die haben da gerade einfach nur Serverprobleme. Beim Start werden mehrere Server kontaktiert da die Daten dezentral sind. Das token sich ändert sollte normal sein.

              Gesendet von meinem Handy

              1 Reply Last reply Reply Quote 0
              • Meistertr
                Meistertr Developer last edited by

                Bitte den Landroid-S Adapter updaten (Installieren über url und den Github Link angeben). Worx hat Heute nacht den Server umgestellt

                1 Reply Last reply Reply Quote 0
                • lobomau
                  lobomau last edited by

                  Und Grad kam ein android App Update. Man erkennt jetzt ein Batterie und WiFi symbol.

                  1 Reply Last reply Reply Quote 0
                  • lobomau
                    lobomau last edited by

                    @Meistertr:

                    Bitte den Landroid-S Adapter updaten (Installieren über url und den Github Link angeben). Worx hat Heute nacht den Server umgestellt `
                    Hat leider noch nichts gebracht:

                    landroid-s.0	2017-10-05 18:32:57.471	info	Downloaded guest token
landroid-s.0	2017-10-05 18:32:57.284	info	starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.landroid-s, node: v6.11.4
sql.0	2017-10-05 18:32:57.352	info	enabled logging of landroid-s.0.mower.totalTime
sql.0	2017-10-05 18:32:57.347	info	enabled logging of landroid-s.0.mower.totalBladeTime
sql.0	2017-10-05 18:32:57.337	info	enabled logging of landroid-s.0.mower.totalDistance
host.brix-3150	2017-10-05 18:32:55.905	info	instance system.adapter.landroid-s.0 started with pid 26024
host.brix-3150	2017-10-05 18:32:25.895	info	Restart adapter system.adapter.landroid-s.0 because enabled
host.brix-3150	2017-10-05 18:32:25.895	error	instance system.adapter.landroid-s.0 terminated with code 0 (OK)
host.brix-3150	2017-10-05 18:32:25.895	error	Caught by controller[0]: at Timer.listOnTimeout (timers.js:214:5)
host.brix-3150	2017-10-05 18:32:25.894	error	Caught by controller[0]: at tryOnTimeout (timers.js:250:5)
host.brix-3150	2017-10-05 18:32:25.894	error	Caught by controller[0]: at ontimeout (timers.js:386:11)
host.brix-3150	2017-10-05 18:32:25.894	error	Caught by controller[0]: at Timeout.checkStatus [as _onTimeout] (/opt/iobroker/node_modules/iobroker.landroid-s/main.js:682:14)
host.brix-3150	2017-10-05 18:32:25.894	error	Caught by controller[0]: at LandroidCloud.sendMessage (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud.js:274:16)
host.brix-3150	2017-10-05 18:32:25.893	error	Caught by controller[0]: TypeError: Cannot read property 'publish' of undefined
landroid-s.0	2017-10-05 18:32:25.840	info	cleaned everything up...
landroid-s.0	2017-10-05 18:32:25.840	error	TypeError: Cannot read property 'publish' of undefined at LandroidCloud.sendMessage (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud.js:274:16) at Timeout.checkStatus [as _on
landroid-s.0	2017-10-05 18:32:25.839	error	uncaught exception: Cannot read property 'publish' of undefined
                    1 Reply Last reply Reply Quote 0
                    • Meistertr
                      Meistertr Developer last edited by

                      Bitte einmal die 1.1.4 über url installieren:

                      https://github.com/MeisterTR/ioBroker.l … withoutssl

                      befindet sich gerade im test. Bei mir läuft sie gerade auf 4 Systemen ohne probleme

                      1 Reply Last reply Reply Quote 0
                      • P
                        poessi last edited by

                        Mit der 1.1.4 funktioniert es wieder einwandfrei.

                        Vielen Dank für das schnelle Update.

                        1 Reply Last reply Reply Quote 0
                        • R
                          R32er last edited by

                          und ich habe mich schon gewundert das keine mails mehr kommen. Danke für das update 🙂

                          1 Reply Last reply Reply Quote 0
                          • B
                            bku last edited by

                            Läuft, Danke!

                            1 Reply Last reply Reply Quote 0
                            • B
                              bku last edited by

                              Hallo,

                              habe seit 01:06h keine Verbindung mehr: Nach der DSL-Provider-Zwangstrennung ist die Verbindung weg.

                              • im Netz ist der Landi,

                              • Eishas-App läuft (jetzt wieder, ging auch heute früh nicht)

                              • Android-App geht (jetzt wieder, ging auch zwischendurch mal nicht)

                              Nur: iobroker-Adapter bekomm ich nicht zum Laufen (Versionen: 1.0.3, 1.0.4, 1.1.6)

                              Kannst Du helfen?

                              Gruß Bernd

                              ! host.DiskStation 2017-10-11 10:54:21.462 info Restart adapter system.adapter.landroid-s.0 because enabled
                              ! host.DiskStation 2017-10-11 10:54:21.462 error instance system.adapter.landroid-s.0 terminated with code 0 (OK)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at IncomingMessage.emit (events.js:166:7)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at emitNone (events.js:72:20)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at IncomingMessage. (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:179:37)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:71:14
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at LandroidCloud.retrieveAwsCert (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:84:10)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at LandroidCloud.worx (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:200:21)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at Object.socket.once.exports.request (https.js:189:15)
                              ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at Object.exports.request (http.js:31:10)
                              ! host.DiskStation 2017-10-11 10:54:21.461 error Caught by controller[2]: at new ClientRequest (_http_client.js:79:14)
                              ! host.DiskStation 2017-10-11 10:54:21.461 error Caught by controller[2]: at ClientRequest.OutgoingMessage.setHeader (_http_outgoing.js:354:11)
                              ! host.DiskStation 2017-10-11 10:54:21.460 error Caught by controller[2]: 2017-10-11 10:54:21.421 - landroid-s.0 Error: value required in setHeader("X-Auth-Token", value).
                              ! host.DiskStation 2017-10-11 10:54:21.460 error Caught by controller[1]: 2017-10-11 10:54:21.416 - landroid-s.0 uncaught exception: value required in setHeader("X-Auth-Token", value).
                              ! host.DiskStation 2017-10-11 10:54:21.460 error Caught by controller[0]: [Error: value required in setHeader("X-Auth-Token", value).]
                              ! landroid-s.0 2017-10-11 10:54:21.433 info cleaned everything up…
                              ! landroid-s.0 2017-10-11 10:54:21.427 error Error: value required in setHeader("X-Auth-Token", value). at ClientRequest.OutgoingMessage.setHeader (_http_outgoing.js:354:11) at new ClientRequest (_http_client.js:79:14) at Object.ex
                              ! landroid-s.0 2017-10-11 10:54:21.427 error uncaught exception: value required in setHeader("X-Auth-Token", value).
                              ! landroid-s.0 2017-10-11 10:54:21.426 info undefined
                              ! landroid-s.0 2017-10-11 10:54:21.426 info CA certificate done
                              ! landroid-s.0 2017-10-11 10:54:21.252 info Mqtt Server: undefined
                              ! landroid-s.0 2017-10-11 10:54:21.251 info Logged in as xxxxxxxx API Token Set to : undefined
                              ! landroid-s.0 2017-10-11 10:54:20.998 info
                              ! landroid-s.0 2017-10-11 10:54:20.998 info post:{"email":"xxxxxxxx","password":"xxxxxxxx","uuid":"c591d8e0-ae61-11e7-8faf-63fa9536b470","type":"app","platform":"android"}
                              ! landroid-s.0 2017-10-11 10:54:20.998 info API token set to
                              ! landroid-s.0 2017-10-11 10:54:20.997 info Downloaded guest token
                              ! landroid-s.0 2017-10-11 10:54:20.841 info UUID: c591d8e0-ae61-11e7-8faf-63fa9536b470
                              ! landroid-s.0 2017-10-11 10:54:20.841 info starting. Version 1.1.6 in /opt/iobroker/node_modules/iobroker.landroid-s, node: v4.8.0
                              ! host.DiskStation 2017-10-11 10:54:19.842 info instance system.adapter.landroid-s.0 started with pid 30447
                              ! host.DiskStation 2017-10-11 10:53:49.832 info Restart adapter system.adapter.landroid-s.0 because enabled

                              1 Reply Last reply Reply Quote 0
                              • Meistertr
                                Meistertr Developer last edited by

                                @bku:

                                Hallo,

                                habe seit 01:06h keine Verbindung mehr: Nach der DSL-Provider-Zwangstrennung ist die Verbindung weg.

                                • im Netz ist der Landi,

                                • Eishas-App läuft (jetzt wieder, ging auch heute früh nicht)

                                • Android-App geht (jetzt wieder, ging auch zwischendurch mal nicht)

                                Nur: iobroker-Adapter bekomm ich nicht zum Laufen (Versionen: 1.0.3, 1.0.4, 1.1.6)

                                Kannst Du helfen?

                                Gruß Bernd

                                ! host.DiskStation 2017-10-11 10:54:21.462 info Restart adapter system.adapter.landroid-s.0 because enabled
                                ! host.DiskStation 2017-10-11 10:54:21.462 error instance system.adapter.landroid-s.0 terminated with code 0 (OK)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at IncomingMessage.emit (events.js:166:7)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at emitNone (events.js:72:20)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at IncomingMessage. (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:179:37)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:71:14
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at LandroidCloud.retrieveAwsCert (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:84:10)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at LandroidCloud.worx (/opt/iobroker/node_modules/iobroker.landroid-s/lib/landroid-cloud-2.js:200:21)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at Object.socket.once.exports.request (https.js:189:15)
                                ! host.DiskStation 2017-10-11 10:54:21.462 error Caught by controller[2]: at Object.exports.request (http.js:31:10)
                                ! host.DiskStation 2017-10-11 10:54:21.461 error Caught by controller[2]: at new ClientRequest (_http_client.js:79:14)
                                ! host.DiskStation 2017-10-11 10:54:21.461 error Caught by controller[2]: at ClientRequest.OutgoingMessage.setHeader (_http_outgoing.js:354:11)
                                ! host.DiskStation 2017-10-11 10:54:21.460 error Caught by controller[2]: 2017-10-11 10:54:21.421 - landroid-s.0 Error: value required in setHeader("X-Auth-Token", value).
                                ! host.DiskStation 2017-10-11 10:54:21.460 error Caught by controller[1]: 2017-10-11 10:54:21.416 - landroid-s.0 uncaught exception: value required in setHeader("X-Auth-Token", value).
                                ! host.DiskStation 2017-10-11 10:54:21.460 error Caught by controller[0]: [Error: value required in setHeader("X-Auth-Token", value).]
                                ! landroid-s.0 2017-10-11 10:54:21.433 info cleaned everything up…
                                ! landroid-s.0 2017-10-11 10:54:21.427 error Error: value required in setHeader("X-Auth-Token", value). at ClientRequest.OutgoingMessage.setHeader (_http_outgoing.js:354:11) at new ClientRequest (_http_client.js:79:14) at Object.ex
                                ! landroid-s.0 2017-10-11 10:54:21.427 error uncaught exception: value required in setHeader("X-Auth-Token", value).
                                ! landroid-s.0 2017-10-11 10:54:21.426 info undefined
                                ! landroid-s.0 2017-10-11 10:54:21.426 info CA certificate done
                                ! landroid-s.0 2017-10-11 10:54:21.252 info Mqtt Server: undefined
                                ! landroid-s.0 2017-10-11 10:54:21.251 info Logged in as xxxxxxxx API Token Set to : undefined
                                ! landroid-s.0 2017-10-11 10:54:20.998 info
                                ! landroid-s.0 2017-10-11 10:54:20.998 info post:{"email":"xxxxxxxx","password":"xxxxxxxx","uuid":"c591d8e0-ae61-11e7-8faf-63fa9536b470","type":"app","platform":"android"}
                                ! landroid-s.0 2017-10-11 10:54:20.998 info API token set to
                                ! landroid-s.0 2017-10-11 10:54:20.997 info Downloaded guest token
                                ! landroid-s.0 2017-10-11 10:54:20.841 info UUID: c591d8e0-ae61-11e7-8faf-63fa9536b470
                                ! landroid-s.0 2017-10-11 10:54:20.841 info starting. Version 1.1.6 in /opt/iobroker/node_modules/iobroker.landroid-s, node: v4.8.0
                                ! host.DiskStation 2017-10-11 10:54:19.842 info instance system.adapter.landroid-s.0 started with pid 30447
                                ! host.DiskStation 2017-10-11 10:53:49.832 info Restart adapter system.adapter.landroid-s.0 because enabled `

                                Bitte noch einmal updaten, der Accesskey war abgelaufen, habs gefixed

                                1 Reply Last reply Reply Quote 0
                                • B
                                  bku last edited by

                                  Läuft - Danke!

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Stoni last edited by

                                    Hallo, ich habe auch auf 1.1.6 geupdatet, nachdem der Landi auf Alexa nicht reagiert hat. Tut sich immer noch nichts. Die Instanz sagt:

                                    Verbunden mit Host falsch

                                    Lebenszeichen falsch

                                    Verbunden Landroid s wahr

                                    Die Apps für Android und iOS funktionieren beide…

                                    Gruß Stoni

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bku last edited by

                                      Mit diesem Link updaten:

                                      https://github.com/MeisterTR/ioBroker.landroid-s

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Stoni last edited by

                                        @bku:

                                        Mit diesem Link updaten:

                                        https://github.com/MeisterTR/ioBroker.landroid-s `

                                        Danke. Habe es über github geupdatet. Hat funktioniert.

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          R32er last edited by

                                          ist wieder was mit dem Adapter? habe keine Verbindung über iobroker.

                                          1 Reply Last reply Reply Quote 0
                                          • Meistertr
                                            Meistertr Developer last edited by

                                            Kommt drauf an wann das letzte Update war. Installiere mal von git und schau ob es geht…

                                            Gesendet von meinem Handy

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.0k
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            121
                                            1194
                                            355750
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo