Weird… I’ll do some tests when I get home.
I’m thinking it shouldn’t be 0, because 0 is also an error code according to the API documentation;
0 Unexpected error
What number/sign do you get when you have no error? Is it 0? Or [null]?
In the picture below, only a minus sign is displayed for the error code.
Thanks for the app and the work you put in! 
The API actually return 0 when it is no error.
Could you give the new 1.3.3 version deployed to test that has a fix that could solve your issues with 1.3.0. Thanks! 
After updating to 1.3.2, the error code appears! 
I disconnected the limitation loop and got No loop signal:
State shows current state. 
Activity shows ongoing activity.
And apparently now the error code works.
Even the error with the flow that repeated itself every 10 minutes is gone. Now the flow works as it should.
I keep testing and keeping an eye on things.
Many thanks Magnus! 
Thanks @Andreas_310 for that information. I found one scenario that could require a restart after installation and have fixed that in the new version currently in test.
Sounds great, a big thanks for helping with the testing @Krisstenswe. Then i think i am very close to releasing 1.3.3 after some additional tests on my end.
Suggestions for improvement;
Today, the label Errorcode, which is used in flows, contains only a number. It would have been much better if it had instead contained the text for the error.
In my previous flow above, it only shows the number 2. I would have liked to see that it instead contained what is shown in the app, No loop signal.
Hope you can fix this! 
Sure, we can do that now. I added a flow token called error description. As it does change some logic in the code it would be great if you could run some tests on the new version (1.3.4) similar to the ones you made on the other test versions.
I notified Husqvarna of the error in the documentation and got confirmation today that they will update it.
Now there is a new release (1.3.5) with both new features and bugfixes.
Bugfixes:
New features:
Thanks @Andreas_310 and @Krisstenswe for help testing.
Another release (1.4.2) today that includes a bugfix but also a cool new geolocation feature
Bugfixes
Improved handling when adding missing capabilities.
Changes
Errorcode capability now support unknown errorcodes needed when Husqvarna add new ones between releases
Features Added
Geopositioning Condition Flow Card: ‘Last Position is Inside Any Polygon’. A new geopositioning condition flow card has been introduced, enabling conditional checks against an array of polygons. This feature allows flows to determine if the mower is located within specific areas of your garden. Polygons should be created as GeoJSON structures and passed as an argument to the condition
By using polygons you can define any shape or shapes you want. You can create these manually or by a 3rd party site such as https://geojson.io where you just copy the ready to go json when done and paste it into the condition flow card.
If anybody uses the new ‘Last Position is Inside Any Polygon’ condition in a cool flow please let me know.
Here is a screenshot from my tests:
And here is a video: https://www.youtube.com/watch?v=zXCuQn05Fuk
@BufferOverflow,
Hi Magnus!
Since the last updates, the app works perfectly for me in my usage! - Many thanks!
A suggestion for improvement; Under “AND” flowcards there are today, among other things, “Activity is” and “State is”. I wish “Mode is” would also be selectable.
I will try to explain why it had helped me; When you park the mower with “Parked” (Until further notice), the Mode changes to HOME from MAIN_AREA. I would like to test in a flow if the mower is in “Parked” (Until further notice) by reading Mode in order to be able to activate the mower again.
The function “Mode is” as a flowcard under AND would solve my problem.
TIA!
Great app!
Here’s some suggestions for a future update…
Is it possible to add:
Undock and park at service point
(Don’t know if it is called this in English, translated from Swedish)
This way it is possible to save the automovers life if its lightning on the way, so it’s not parked if there are a lightning strike
You should be able to do this already today with a flow and i think its a pretty common usecase. One idea is to just start the mower and a short while later pause it. Or have you tried something like this and not managed to get it working?
Thanks, nice to hear its working.
That would be an easy addition and i will add it to the list.
Is it not possible to Add the limited Automower Connect@Home Bluetooth variant?
Quoted from post #1.
So sorry if this is not the right place to ask questions but…After adding the App key and app secret it is not possible to clic on save changes. Thoughts?
Hi, this is the correct place to ask 
The button does not clearly indicate successful saving the settings, but it does save them. So after pressing save just exit from the dialogue and you should be good to go.
You can verify this by exiting and then go back again and you should see the saved app key. To really verify try adding any character in the app key - save - exit - settings and verify that the character is there.
Sometimes it is easier to enter the credentials via the web ui instead of the mobile app.
Let us know on how it works out.
Hi,
Thank you so much for the quick response.
I gave it a couple of min and the app showed up and works as expected. Thank you for your support.
