You mean that in the UI you have onoff button for normal routine, onoff button for edge cut routine, and onoff for partymode as a selector?
Not really - two On/off buttons for either normal or edge routine, not sure this is possible but could work as well - eg. from VW integration -
(eg. that could work also for Party mode on/off button - if enabled, On/Off (Normal/Edge) will be blocked etc.) That would also probably require to change state of party button when not enabled anymore or disabled in the flow.
(I left out selector idea as On/Off buttons could be more user friendly maybe)
Today, when you would like to start edge routine, the only option is via flow.
@Martin_Verbeek , great update , thank you !!! 
First of all, thanks for the app, glad to see I can access my Landroid within brand new HomeyPro 
(new user here).
A question though. When I open the Homey app on my phone, the Timeline on the home page is totally ‘flooded’ with battery notifications from the Landroid. It of course makes sense that the mower battery fluctuates hugely, that’s simply how the device functions, recharging at the base station everytime, just like a robovac.
Is there a way to exclude the Landroid from sending notifications to the Timeline? Since they are unnecessary for this kind of device.
The only way I discovered to stop the Timeline being flooded by Landroid notifications, is by disabling the Energy notifications altogether. But that means I won’t get any useful Timeline notifications from any other devices either…
How could I solve this?
They should not appear on your device timeline. Have seen it once before, but that seemed to be an Athom error, not an app thing could you do a restart of your Homey and see if the problem persists
1 Like
Hey Martin,
I restarted the Homey and turned on the Energy updates in the Homey Timeline Settings to see what would happen.
And unfortunately the Landroid started reporting it’s battery status to the Homey Timeline again.
Okay. I see what is happening. Will fix.
Awesome!
after last update to 5.3.1 test version are my worx down in homey
Can it be fixet soon?
Same here with 5.3.1 test
undefined2023-10-03T04:59:35.986Z Error Initializing Driver landroid: Error: librt.so.1: cannot open shared object file
at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at Module.homeyRequire [as require] (/node_modules/@athombv/homey-apps-sdk-v3/index.js:12:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object.<anonymous> (/app/node_modules/aws-crt/dist/native/binding.js:92:19)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32) {
code: 'ERR_DLOPEN_FAILED'
}
</anonymous>2023-10-03T04:59:35.983Z Error Initializing Driver ferrex: Error: librt.so.1: cannot open shared object file
at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at Module.homeyRequire [as require] (/node_modules/@athombv/homey-apps-sdk-v3/index.js:12:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object.<anonymous> (/app/node_modules/aws-crt/dist/native/binding.js:92:19)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32) {
code: 'ERR_DLOPEN_FAILED'
}
</anonymous>2023-10-03T04:59:35.981Z Error Initializing Driver kress: Error: librt.so.1: cannot open shared object file
at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at Module.homeyRequire [as require] (/node_modules/@athombv/homey-apps-sdk-v3/index.js:12:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object.<anonymous> (/app/node_modules/aws-crt/dist/native/binding.js:92:19)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32) {
code: 'ERR_DLOPEN_FAILED'
}
</anonymous>2023-10-03T04:59:35.966Z Error Initializing Driver landxcape: Error: librt.so.1: cannot open shared object file: No such file or directory
at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at Module.homeyRequire [as require] (/node_modules/@athombv/homey-apps-sdk-v3/index.js:12:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object.<anonymous> (/app/node_modules/aws-crt/dist/native/binding.js:92:19)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32) {
code: 'ERR_DLOPEN_FAILED'
}
</anonymous>2023-10-03T04:59:35.962Z [log] [ManagerDrivers] [Driver:openmower] OpenmowerDriver has been initialized
2023-10-03T04:59:35.569Z [log] [WorxApp] registerFlowCards() Listeners
2023-10-03T04:59:35.560Z [log] [WorxApp] registerFlowCards() flows
2023-10-03T04:59:35.557Z [log] [WorxApp] Worx 5.3.1 is initialising.
2023-10-03T04:59:35.557Z [log] capturing stderr
2023-10-03T04:59:35.543Z [log] capturing stdout
2023-10-03T04:59:33.711Z [log] [WorxApp] app unload called
2023-10-03T04:59:33.708Z [log] [WorxApp] app unload called no worx object for openmower
Unfortunately also broken with 5.2.8 non-test
undefined2023-10-03T05:02:55.259Z [WorxApp] Unhandled Rejection at: Promise {
<rejected> Error: Invalid Capability: commandPartyMode
at Remote Process
at HomeyClient.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:126:50)
at LandroidDevice.addCapability (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:446:25)
at LandroidDriver.updateStatus (/app/drivers/WorxDriver.js:180:69)
at Worx.<anonymous> (/app/drivers/WorxDriver.js:84:22)
at Worx.emit (node:events:517:28)
at Worx.onMessage (/app/drivers/Worx.js:432:14)
at DeviceClient.<anonymous> (/app/drivers/Worx.js:387:26)
at DeviceClient.emit (node:events:517:28) {
statusCode: 404
}
} reason: Error: Invalid Capability: commandPartyMode
at Remote Process
at HomeyClient.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:126:50)
at LandroidDevice.addCapability (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:446:25)
at LandroidDriver.updateStatus (/app/drivers/WorxDriver.js:180:69)
at Worx.<anonymous> (/app/drivers/WorxDriver.js:84:22)
at Worx.emit (node:events:517:28)
at Worx.onMessage (/app/drivers/Worx.js:432:14)
at DeviceClient.<anonymous> (/app/drivers/Worx.js:387:26)
at DeviceClient.emit (node:events:517:28) {
statusCode: 404
}
</anonymous></anonymous></anonymous></anonymous></rejected>unhandledRejection:
Error: Invalid Capability: commandPartyMode
at Remote Process
at HomeyClient.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:126:50)
at LandroidDevice.addCapability (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:446:25)
at LandroidDriver.updateStatus (/app/drivers/WorxDriver.js:180:69)
at Worx.<anonymous> (/app/drivers/WorxDriver.js:84:22)
at Worx.emit (node:events:517:28)
at Worx.onMessage (/app/drivers/Worx.js:432:14)
at DeviceClient.<anonymous> (/app/drivers/Worx.js:387:26)
at DeviceClient.emit (node:events:517:28)
</anonymous></anonymous>2023-10-03T05:02:55.242Z [log] [ManagerDrivers] [Driver:landroid] updateStatus with MQTT message for 2021302672060014447B Landroid
2023-10-03T05:02:55.241Z [log] Worxcloud MQTT get Message for mower Landroid (REDACTED)
Go back to the non test release. No clue what is happening here. It works in development, not working when uploaded to test
Thanks Martin, that’s broken for me as well, I have shared both logs from test and non-test - probably due to the breaking changes in test ?
1 Like
5.2.8 dont work here to my worx mower.
5.3.2 should revert the mqtt V2 change
1 Like
Did the change work for you people? then i can submit to live.
I don’t know what I should be looking for (if anything) 
my app is at 5.2.8, and the mower is still reporting its battery status to the Homey Timeline. No idea of that’s for the app to decide, or just a core Homey feature. Maybe Homey should make it possible to exclude certain devices if desired?
There is a LOT going on in the log though, is it supposed to be that busy? Also, there may be a problem with the ‘Copy Log to Clipboard’ function.
It’s working for me like before, mower is reachable and app is not crashing ( 5.3.2 ).
Thank you Martin for quick fix !
Hello Martin,
Are you still planning to change the battery reporting, or is this something only Athom could do?
If not, I think I’ll turn it off again for all devices. It’s a bit much in the Timeline .
(on version 5.3.2 now)
This seems to be tightly linked with measure battery capability. I cannot turn off this because of that.
Strange thing is that I do not experience this behaviour, it just reports once for low and when battery is on level once again around the mowing work.
Okay, so it is not possible to have an option in the app settings like… “report battery status to Homey yes/no” 
?
My mower goes out to mow twice a day, so that doubles the amount of timeline notifications .
Of course it’s always fun to have every device ‘in’ the house connected to Homey, see the Insights for inclination and gradient etc. But frankly, I haven’t thought of any useful automation flows for the mower. It just does its thing, and the Landroid app works (worx 
) and reports okay on its own too (unlike many other manufacturer apps). So maybe… I’ll just disconnect the mower from Homey , so I don’t miss battery notifications for other devices.
