Update to new Worx-API

[cm86]

Hello would this become updated for the new api from worx!?
I've had the docker running for a day and I have been banned for 24h.

Mfg
Chris

[int5749]

Hi,
would appreciate this to, as it's no longer possible to connect :-/
Appreciate an updat on this ;-)
Regards
Joerg

[riker09]

The guy who wrote the initial adapter (NPM package iobroker.landroid-s) has handed the code over to the community. The new repository is https://github.com/iobroker-community-adapters/ioBroker.worx and the new package name is iobroker.worx.

Since I recently moved my Landroid-S from my shed to its base station I wanted to re-integrate it into my Home Assistant configuration. But I ran across several errors and now I'm in knee-deep. I hopefully can make it work again and will post my findings here, maybe even create a PR for it.

[int5749]

But there seems to be a difference as this bridge from virtualzone is based on iobroker code, but different. this bridge is not iobroker and no iobroker is required while this bridge is between OpenHab and Landroid. Same issue was last year and a swift update solved the issue. looking forward that Heiner is still active.

[riker09]

Yes, I have come to the same conclusion. While some portions of the code is similar, the new NPM package seems to have a much tighter integration with ioBroker. I think it would be a good start to write a generic package that can connect to the landroid worx cloud. However, my time for this is rather limited.

I'm facing the same connection issues, though, so this ticket is still valid and any solution would be highly appreciated.

[riker09]

here is my setup:

# file: docker-compose.yml
version: '3'

services:
  landroid:
    image: virtualzone/landroid-bridge
    container_name: landroid
    restart: unless-stopped
    ports:
      - "3000:3000"
    volumes:
      - ./config.json:/usr/src/app/config.json

File config.json

{
    "http": {
        "port": 3000
    },
    "landroid-s": {
        "enable": true,
        "email": "[REDACTED]",
        "pwd": "[REDACTED]",
        "dev_sel": 0
    },
    "mqtt": {
        "enable": true,
        "url": "mqtt://10.0.0.55",
        "topic": "landroid"
    },
    "scheduler": {
        "enable": false,
        "cron": false,
        "weather": {
            "provider": "wunderground",
            "apiKey": "YOUR_API_KEY",
            "latitude": 50.00,
            "longitude": 8.00
        },
        "db": "./scheduler.db",
        "earliestStart": 10,
        "latestStop": 15,
        "startEarly": true,
        "offDays": 2,
        "squareMeters": 200,
        "perHour": 50,
        "mowTime": 60,
        "chargeTime": 60,
        "daysForTotalCut": 4,
        "rainDelay": 90,
        "threshold": 30
    }
}

These messages appear in the container log:

[2020-02-26T18:40:50.511] [INFO] IoBrokerAdapter - mower 0 selected
[2020-02-26T18:41:48.976] [INFO] LandroidS - Could not finish initialization, retrying...
Mqtt url: undefined
[2020-02-26T18:41:50.640] [INFO] IoBrokerAdapter - mower 0 selected
[2020-02-26T18:42:48.976] [INFO] LandroidS - Could not finish initialization, retrying...
Mqtt url: undefined
[2020-02-26T18:42:50.521] [INFO] IoBrokerAdapter - mower 0 selected
[2020-02-26T18:43:48.976] [INFO] LandroidS - Could not finish initialization, retrying...

I have found out that the Mqtt url: undefined is harmless, this is a debug message from the used library. There is an issue for that, but development seems to have moved on so I wouldn't hold my breath waiting on a fix.

[int5749]

Yes, I have come to the same conclusion. While some portions of the code is similar, the new NPM package seems to have a much tighter integration with ioBroker. I think it would be a good start to write a generic package that can connect to the landroid worx cloud. However, my time for this is rather limited.

I'm facing the same connection issues, though, so this ticket is still valid and any solution would be highly appreciated.

Yes, also from my end

It looks like only link to AWS has changed, but no idea how to change this in the distribution :-/

[riker09]

Do you know which link has changed? If so, a simple search and replace could make it work again. I have a little bit experience with programming in TypeScript and Docker.

[int5749]

That's what I've got from the desktop App to manage Landroid
a1optpg91s0ydf-ats.iot.eu-west-1.amazonaws.com

I made a brief check to the files from this bridge and found ASW links pointing to east-x.amazonaws.com, so this might be the one. As I'm not experienced enough, I left it ;-)
Happy if you find a way to change this?

[riker09]

Sorry, but where did you find links to east-x.amazonaws.com in this repository? When I search for aws this issue right here is the only occurence.

[int5749]

This is e.g. from aws4.js
RequestSigner.prototype.createHost = function() { var region = this.isSingleRegion() ? '' : (this.service === 's3' && this.region !== 'us-east-1' ? '-' : '.') + this.region, service = this.service === 'ses' ? 'email' : this.service return service + region + '.amazonaws.com' }
I simply used totalcommander search in files for amazonaws.com and found various occurence, not sure if this can be changed?

[riker09]

Did you grep your local files with Total Commander? If so, did you include your node_modules folder? Could you post the path to the file with the match, please?

[KaaNee]

Hi guys,
trying the same. changed log-level to debug and here is what i found out:

bridge is using "old" api or better: old iobroker.library for worx (https://github.com/MeisterTR/ioBroker.landroid-s) and tries to get some parameters which aren't there, so it's logging "board undefined selected":

https://github.com/MeisterTR/ioBroker.landroid-s/blob/master/lib/mqttCloud.js
Line 135 it tries to get "mqtt_topic_prefix" which was provided by a "board" which were get before (list of boards). MAYBE this could be fixed because the mower in your profile does provide mqtt informations.
But also found out, that there is a new "library" for worx, but only used in a iobroker-adapter - or just only implemented in:

https://github.com/iobroker-community-adapters/ioBroker.worx/blob/master/lib/api.js

So this has to be taken and implemented in an own running bridge (which i prefer because it's open to all apps, like openhab, other mqtt handling app).

Done for today.

[riker09]

This is a good sum up of my own findings. Thank you for putting them into words, @KaaNee . I did a quick compare of the two files mentioned (ioBroker.landroid-s/blob/master/lib/mqttCloud.js, ioBroker.worx/blob/master/lib/api.js) and tried to use the newer one with virtualzone/landroid-bridge but have not gotten very far. I'll talk to @MeisterTR and see wether it is possible to move the landroid API to its own package.

[EDIT]
For reference: Here's the issue in the old repository: https://github.com/MeisterTR/ioBroker.landroid-s/issues/34

[int5749]

Sorry, but where did you find links to east-x.amazonaws.com in this repository? When I search for aws this issue right here is the only occurence.

Hi, sorry was busy over past day(s) :-/

Here is result from my TotalCommander
\landroid-bridge\node_modules\aws4\aws4.js
\landroid-bridge\node_modules\aws4\README.md
\landroid-bridge\node_modules\es6-promise\README.md
\landroid-bridge\node_modules\mqtt\README.md
\landroid-bridge\node_modules\node-pre-gyp\lib\info.js
\landroid-bridge\node_modules\node-pre-gyp\lib\publish.js
\landroid-bridge\node_modules\node-pre-gyp\lib\unpublish.js
\landroid-bridge\node_modules\node-pre-gyp\README.md
\landroid-bridge\node_modules\psl\data\rules.json
\landroid-bridge\node_modules\psl\dist\psl.js
\landroid-bridge\node_modules\psl\dist\psl.min.js
\landroid-bridge\node_modules\spdx-license-ids\README.md
\landroid-bridge\node_modules\sqlite3\package.json

Regards
Joerg

[MeisterTR]

should be fixed now

[cm86]

So I've tried to use the docker image...
But it's still saying mqtt url undefined.
Where did you solve the issue!?
Do I have to use locally!?

Thanks in advance.
Chris

[MeisterTR]

i think you have to reinstall to get the changes

[int5749]

i think you have to reinstall to get the changes

Thanks for you effort and support on this.
Just to be precise, it's now included in this landroid-bridge and I shall be able to "simply" download this new version and install?

I just ask as I don't see any files updated when I'm on main page of this distr.

Regards
Joerg

[KaaNee]

i think you have to reinstall to get the changes

Hi, thanks @MeisterTR for applying these changes (nearly the same i did locally) :-)
May you please publish the npm package ?
https://www.npmjs.com/package/iobroker.landroid-s

It should be compatible with 2.5.5 (i'm not sure how to flag this in npm), as the dependency in landroid-bridge is "^2.5.5" (^= compatible with ).

Thanks in advance. If i can help or take some work, just let us know.

Regards,
Kai

[riker09]

Until these changes are published as an individual NPM package you can use the following Dockerfile to get a working image again (tested succesfully in my local HA setup):

FROM node:11-alpine AS prod

WORKDIR /usr/src/app

# Add package.json
COPY package*.json .

RUN apk add --no-cache git

# Restore node modules
RUN npm install --production



## BUILD STEP
FROM prod AS build

# Add everything else not excluded by .dockerignore
COPY . .

# Build it
RUN npm install && \
    npm run build-prod



## FINAL STEP
FROM prod as final

RUN apk del git

COPY --from=build /usr/src/app/dist ./dist

EXPOSE 3000
CMD [ "node", "dist/server.js" ]

[riker09]

I have created PR #89 that contains the multi-staged builds from the above Dockerfile. I will wait on @MeisterTR and see if he creates a new NPM package in the next few days. If not, above file will probably make it into another PR. 🙂

[int5749]

Until these changes are published as an individual NPM package you can use the following Dockerfile to get a working image again (tested succesfully in my local HA setup):

FROM node:11-alpine AS prod

WORKDIR /usr/src/app

# Add package.json
COPY package*.json .

RUN apk add --no-cache git

# Restore node modules
RUN npm install --production



## BUILD STEP
FROM prod AS build

# Add everything else not excluded by .dockerignore
COPY . .

# Build it
RUN npm install && \
    npm run build-prod



## FINAL STEP
FROM prod as final

RUN apk del git

COPY --from=build /usr/src/app/dist ./dist

EXPOSE 3000
CMD [ "node", "dist/server.js" ]

Hi Riker,
again thanks a lot for your effort and support. I modified both docker files
Dockerfile
Dockerfile.rpi

but, it's still not working :-/ Probably I made something wrong? Happy for any advise/help

Regards
Joerg

[cm86]

Yes i also can't get it to work.

What i've done:

• Cloned this repo
• edited the Dockerfile to

Until these changes are published as an individual NPM package you can use the following Dockerfile to get a working image again (tested succesfully in my local HA setup):

FROM node:11-alpine AS prod

WORKDIR /usr/src/app

# Add package.json
COPY package*.json .

RUN apk add --no-cache git

# Restore node modules
RUN npm install --production



## BUILD STEP
FROM prod AS build

# Add everything else not excluded by .dockerignore
COPY . .

# Build it
RUN npm install && \
    npm run build-prod



## FINAL STEP
FROM prod as final

RUN apk del git

COPY --from=build /usr/src/app/dist ./dist

EXPOSE 3000
CMD [ "node", "dist/server.js" ]

• Build the container with docker build -t landroid-bridge .
• run the container with docker run -d -p 3000:3000 --name landroid_bridge -v /opt/landroid-bridge/config.json:/usr/src/app/config.json --restart=unless-stopped landroid-bridge

Looked at the docker logs...
[2020-03-04T18:15:03.908] [INFO] LandroidS - Initializing Landroid Cloud Service... Mqtt url: undefined [2020-03-04T18:15:05.458] [INFO] IoBrokerAdapter - mower 0 selected

Maybe i'm doing something wrong?

mfg
Chris

[riker09]

Sorry, yeah. Actually I forgot to add my modified package.json. Remember, MeisterTR has updated the ioBroker.landroid-s repository? You need to build the Docker image with these changes.

These are the steps required:

1. Clone this repository
2. Update Dockerfile (see above)
3. Modify package.json

@@ -34,7 +34,7 @@
     "cache": "^2.1.0",
     "cron": "^1.7.1",
     "express": "^4.17.0",
-    "iobroker.landroid-s": "^2.5.5",
+    "iobroker.landroid-s": "github:MeisterTR/ioBroker.landroid-s#bc5bda3a495a87105bb4723b472c15846aec8e4e",
     "log4js": "^4.3.0",
     "moment": "^2.24.0",
     "mqtt": "^2.18.8",

4. Build Docker image

This is the reason why the Dockerfile above has apk add --no-cache git in it (and later the removal of that package) and the Dockerfile from my PR does not.

[cm86]

So I have this too.
But I ran into this error
`[root@HomeAssistant landroid-bridge]# docker build -t landroid-bridge . Sending build context to Docker daemon 1.435MB
Step 1/13 : FROM node:11-alpine AS prod
---> f18da2f58c3d
Step 2/13 : WORKDIR /usr/src/app
---> Using cache
---> e07cf2732dc9
Step 3/13 : COPY package*.json .
---> Using cache
---> aad89be759ff
Step 4/13 : RUN apk add --no-cache git
---> Using cache
---> f18cc0133cda
Step 5/13 : RUN npm install --production
---> Running in 838249831e04
npm ERR! file /usr/src/app/package.json
npm ERR! code EJSONPARSE
npm ERR! JSON.parse Failed to parse json
npm ERR! JSON.parse Unexpected token
npm ERR! JSON.parse in JSON at position 101 while parsing '{ "name": "landroid-bridge", "version": '
npm ERR! JSON.parse Failed to parse package.json data.
npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-03-05T21_22_26_313Z-debug.log
The command '/bin/sh -c npm install --production' returned a non-zero code: 1`

[int5749]

And I've never used Docker before, was happy to have it installed with NPM :-/
Just to ask: is there a brief decription how to use Docker to package this?
I think I have Git installed already, but as I said: I'm not a programmer :-(

[Saboti]

Hi,
I just updated the package.json with the github link to the updates Repo from @MeisterTR .
Like the example from @riker09 .
Than I build it localy and start it.
Shortly after the start it shows the Error:
[2020-03-06T09:00:09.847] [INFO] LandroidS - Could not finish initialization, retrying...

Did someone successfully run it without docker or can me help with this error?

regards Saboti

[riker09]

We all have very different backgrounds and I tend to forget that. Sorry for that! 😅

So, bear with me, be patient, and I believe we can pull it off together. Regarding the question from @int5749 here's the command to build a Docker container:

docker build --tag virtualzone/landroid-bridge:YOURTAG .

This command must be issued inside the folder where the Dockerfile is located. Note the dot at the end of the line, it is very important and easy to forget. Also, you can tag your image any way you see fit. You don't need the virtualzone/ prefix in the image name. You can just name it landroid-bridge and omit the :YOURTAG, Docker automatically tags the image with :latest in this case. You only need to make sure you're actually using the image you have build:

docker run \
    -p 3000:3000 \
    --name landroid_bridge \
    --link mqtt:mqtt \
    -v /tmp/config.json:/usr/src/app/config.json \
    virtualzone/landroid-bridge:YOURTAG

This command is taken from the README.md of this repository. I have only added the :YOURTAG.

[riker09]

@Saboti Yes, landroid-bridge is working for me. Are you running the code locally (with node dist/server.js or inside a docker container?

[simikuen]

The Dockerfile was updated two hours ago. Maybe a wrong COPY. From my point of view it should be without *. But be carefull, the package.json includes a old ioBroker-Landroid-s package. Pull this docker kaareseras/landroid-bridge and everything works.

[freekeys]

Hi all, just bought a Landroid so am new to this thread! It looks like a lot of progress has been made but is this specifically Docker (manually HA installation) rather than Hassio at this stage?

[hirschy81]

@simikuen Could you point me to the repo - I would like to try the new docker image, as I also encountered the reconnection issues with the current update (as mentioned by youreself). Thx

[simikuen]

For me it runs with this docker kaareseras/landroid-bridge.

[hirschy81]

I have updated to the latest version of @stefanlaheij but unfortunately still no connection: [2020-04-09T15:13:19.508] [DEBUG] IoBrokerAdapter - Worxcloud MQTT offline

[nicoh88]

@hirschy81 Same here. 👎

[2020-04-09T15:30:48.073] [INFO] IoBrokerAdapter - mower 0 selected
[2020-04-09T15:30:48.073] [DEBUG] IoBrokerAdapter - Mac adress set to: 98D86331XXXX
[2020-04-09T15:31:18.086] [DEBUG] IoBrokerAdapter - Worxcloud MQTT offline
[2020-04-09T15:31:46.600] [INFO] LandroidS - Could not finish initialization, retrying...

[simikuen]

I reconfigured the WiFi from the mower. After that I got a connection.

[simikuen]

Mower is connected to the WiFi and is online. Means reachable via Worx app.

[hirschy81]

Same for me - i noticed that after reconnecting the mower the App also asked for a new Login. After that i can confirm that now the Connection ist working

[hirschy81]

One thing I mentioned: I now can connect and also read all values (coming in, are consumed and published via MQTT) -
[2020-04-10T16:17:01.767] [DEBUG] IoBrokerAdapter - Landroid status: {"cfg":{"id":1,"lg":"it","tm":"16:17:01","dt":"10/04/2020","sc":{"m":1,"p":0,"d":[["09:00",0,0],["09:00",210,1],["09:00",210,0],["09:00",210,0],["09:00",210,0],["09:00",210,1],["09:00",0,0]]},"cmd":0,"mz":[0,0,0,0],"mzv":[0,0,0,0,0,0,0,0,0,0],"rd":180,"sn":"XXXXXXXXXXXX","modules":{"US":{"enabled":1}}},"dat":{"mac":"XXXXXXXXXXXXXXX","fw":3.07,"bt":{"t":34.5,"v":20.2,"p":90,"nr":33,"c":1,"m":0},"dmp":[-0.1,-0.9,357.6],"st":{"b":2099,"d":31440,"wt":2280,"bl":90},"ls":1,"le":0,"lz":1,"rsi":-64,"lk":0,"act":1,"tr":0,"conn":"wifi","modules":{"US":{"stat":"ok"}}}}
[2020-04-10T16:17:01.771] [INFO] Mqtt - Publishing MQTT message to topic landroid/status/dateTime: 2020-04-10 16:17:01
[2020-04-10T16:17:01.772] [INFO] Mqtt - Publishing MQTT message to topic landroid/status/batteryVoltage: 20.2
[2020-04-10T16:17:01.773] [INFO] Mqtt - Publishing MQTT message to topic landroid/status/batteryLevel: 90

but I cannot write back (e.g. changes of schedules, starting the mower etc.)
For every action I receive:
[2020-04-10T16:16:58.891] [INFO] Mqtt - Incoming MQTT message to topic landroid/set/start: on
[2020-04-10T16:16:58.892] [INFO] LandroidS - Sending to landroid cloud: {"cmd":1}
[2020-04-10T16:16:58.893] [DEBUG] IoBrokerAdapter - Sending Message: {"cmd":1}
[2020-04-10T16:16:58.950] [DEBUG] IoBrokerAdapter - Worxcloud MQTT offline
[2020-04-10T16:17:00.309] [DEBUG] IoBrokerAdapter - Mqtt connected!

[riker09]

@hirschy81 Yeah, same here. I never got the bridge to the point where I could send commands to the mower and figured its not worth my investigation time since I'm quite happy with the schedule I've setup in the Landroid App on my Android.

@freekeys This "thread" is a collection of my findings (and those of others) about how to make the virtualzone/landroid-bridge Docker image run again. There was is an outdated dependency in the package.json file that got fixed upstream. This repository seams to be no longer maintained anymore. At this point somebody should fork it, apply the fixes and effectively become the new maintainer. I have read a few posts above about the kaareseras/landroid-bridge repo. I have not looked at it yet, maybe that's what happened there.
To answer your question: This is not about Hassio, but a standalone Docker image. It could be used as a base to create a Hassio image/package from it, however.

[EDIT]
It seems the kaareseras/landroid-bridge repository does not exist (anymore).

[simikuen]

It seems there is an problem with the worx cloud. It’s also not possible to control the mower via app. Just get status information.

[virtualzone]

Should be fixed with the commit of @theWaldschrat

[riker09]

Thanks for the PR @theWaldschrat this helps a lot of people.

And maybe there was a fix in the repository by MeisterTR (see here) that re-enables sending commands to the mower. I will have to make some tests, but that will take a while due to the current worldwide pandemic situation.

[MindFreeze]

Yes, I can confirm commands work with the latest iobroker

"iobroker.landroid-s": "github:MeisterTR/ioBroker.landroid-s#40bf869b5f9e0936af26a226b4bb251f950e9d49"

[holgerpieta]

It might also be a good idea to remove all the old images from Docker Hub, because they won't help people in the slightest but might get them banned.

[riker09]

This would have to be done by the owner of the Docker Hub account. My guess is @virtualzone ?

[rosscullen]

Thanks to everyone who contributed above. Like many of you, this was working perfect last season.

After much piecing of information together, I've managed to build my container through Portainer on a Synology (x64 hardware). Still running into an issue, hoping someone can point me in the right direction. Attached are my log files:

[2020-04-19T01:00:09.419] [INFO] server.ts - Starting Landroid Bridge...
[2020-04-19T01:00:09.421] [INFO] server.ts - Setting port to 3000...
[2020-04-19T01:00:09.442] [INFO] Mqtt - Connecting to MQTT Broker...
[2020-04-19T01:00:09.443] [INFO] App - Adding static files path /usr/src/app/www
[2020-04-19T01:00:09.444] [INFO] Scheduler - Creating SQLite database at /usr/sr c/app/scheduler.db
[2020-04-19T01:00:09.449] [INFO] Mqtt - Successfully connected to MQTT Broker!
[2020-04-19T01:00:09.451] [INFO] LandroidS - Initializing Landroid Cloud Service ...
[2020-04-19T01:00:11.866] [INFO] IoBrokerAdapter - mower 0 selected
[2020-04-19T01:01:09.451] [INFO] LandroidS - Could not finish initialization, retrying...
[2020-04-19T01:01:10.627] [INFO] IoBrokerAdapter - mower 0 selected
[2020-04-19T01:02:09.451] [INFO] LandroidS - Could not finish initialization, retrying...
[2020-04-19T01:02:10.812] [INFO] IoBrokerAdapter - mower 0 selected
[2020-04-19T01:03:09.453] [INFO] LandroidS - Could not finish initialization, retrying...
[2020-04-19T01:03:10.499] [INFO] IoBrokerAdapter - mower 0 selected
[2020-04-19T01:04:09.453] [INFO] LandroidS - Could not finish initialization, retrying...
[2020-04-19T01:04:10.617] [INFO] IoBrokerAdapter - mower 0 selected

Any suggestions greatly appreciated :-)

[simikuen]

You can try to reconfigure the WiFi from the mower.

[holgerpieta]

Can you control (start, stop...) the mower from the official app?
If yes, I don't know what's wrong unfortunately. Maybe wrong username and password?
If not, you have been banned, maybe for using the old API, maybe for connecting too often. Then just stop the bridge, wait 24 hours (and if possible, get a new IP address for your internet access) and see if you can control the mower again via the official app. If yes, restart the bridge and it should connect successfully.
If you still cannot control the mower with the official app after waiting 24 hours, again something else is wrong. Mower offline, Wifi wrong or something like that.

[rosscullen]

Can you control (start, stop...) the mower from the official app?
If yes, I don't know what's wrong unfortunately. Maybe wrong username and password?
If not, you have been banned, maybe for using the old API, maybe for connecting too often. Then just stop the bridge, wait 24 hours (and if possible, get a new IP address for your internet access) and see if you can control the mower again via the official app. If yes, restart the bridge and it should connect successfully.
If you still cannot control the mower with the official app after waiting 24 hours, again something else is wrong. Mower offline, Wifi wrong or something like that.

Thanks for the tips @theWaldschrat @simikuen . When using the app, I'm getting notifications and status but not able to start the mower from the app.... hmm...

[simikuen]

@rosscullen: same issue on me. The successful solution for me was to create a new account here https://account.worxlandroid.com/. Change the owner from your mower to the new account and use this new account in your app and Landroid bridge. In the old account is a function to change the owner to the new account. Very simple.

[holgerpieta]

Maybe it's possible to get banned for life, I don't know. For me it was enough to shut-down the bridge and wait 24 hours. After that time I was again able to control the mower via the app. After verifying that I started the bridge again and things are working fine since then.

[MindFreeze]

24 h didn't work for me at first and is the minimum. I had to wait 48h without opening the app or starting the bridge.

[simikuen]

I didn’t use the bridge for more then 48h. But not the app. From time to time I use the app for checking. Maybe the important thing is to don’t use BOTH for more the 24h.

[KoKia13]

@rosscullen
Thx for the tips, I'm banned since minimum one month now. Ticket to Worx support doesn't change anything. Curl commands where working few times, but since... No apps can push.

Edit: tested and now I can push via the Android app, thx a lot.

[holgerpieta]

@KoKia13 What did you do in the end? Make a new account?

It's good to know that the ban can also be longer then 24 hours. But at least for me trying the app every couple of hours didn't make things worse and I was still unbanned after 24 hours. In the end it's the same as for all bans everywhere: They intentionally don't give you enough information to increase the fear-factor. You never know what might happen if you get to the wrong end of the stick.

[KoKia13]

Yes banned since the change of the auth ~1 month. I've created a new worx account, and changed the mower to the new. And I was able to push planning, raidelay... from the Android app. I've completely disabled the bridge.