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

[FR]: reenable torque setting #620

Open
Crashman1983 opened this issue May 19, 2024 · 16 comments
Open

[FR]: reenable torque setting #620

Crashman1983 opened this issue May 19, 2024 · 16 comments

Comments

@Crashman1983
Copy link

Describe the feature you wish to make a request for

Please reenable the currently disabled torque setting!

Describe alternatives you've considered

Only special setting, enabled by user if wanted

Additional context

No response

@MTrab
Copy link
Owner

MTrab commented May 19, 2024

It will be reenabled when I have a solution for the issues it caused

@mklik
Copy link

mklik commented May 21, 2024

This is probably not a problem with the landroid_cloud integration, but with the Vision mower itself.
There are many people in a german forum who claim that their mower has been "offline" since the beginning of May 2024. Yet they don't use the Home Assistant at all.

I rely heavily on the torque setting for my fairly varied lawns and make extensive use of the automatic setting for the mower.

@MTrab
Copy link
Owner

MTrab commented May 21, 2024

Still the mowers went offline as soon as the torque setting was used.
So for now this feature is disabled, until there is a solution to this. Either by firmware in the mowers or until I figure out if it's only some specific models

@mklik
Copy link

mklik commented May 21, 2024

Thanks for the information.
I still use v5.02 of the landroid-cloud integration with my M700 plus (WR167E) with no issues.
Hope this helps ...

@MTrab
Copy link
Owner

MTrab commented May 21, 2024

Seems like this may be related to a firmware issue

@qu4nd
Copy link

qu4nd commented May 24, 2024

Just fyi, torque worked fine with my M500 (WR141E) on firmware version 3.32.0+1

@DerAutomatiker
Copy link

also working on WR161e M500 Plus on FW 3.32.0+1

@Salrok
Copy link

Salrok commented Jun 7, 2024

In the few days the torque feature was available, it worked fine with my M500 (WR141E) on firmware version 3.32.0+1.

@Ammby
Copy link

Ammby commented Jun 9, 2024

Hi there. Any news to this. I reduced the torque of my Landroid mower a few weeks ago and want to increase it again a bit because the mower now gets stuck sometimes. Thanks

@MTrab
Copy link
Owner

MTrab commented Jun 9, 2024

Nothing new from Positec, unfortunately

@wizu
Copy link

wizu commented Jun 10, 2024

Could it be reenabled for for not vision models only? Or this problem affects old models too?

@MTrab
Copy link
Owner

MTrab commented Jun 10, 2024

As far as I know, it's a hit and miss if it crashes the devices or not.

I haven't found a clear pointer to the problem, other than others having confirmed it's a firmware bug

@DandeMC
Copy link

DandeMC commented Jul 21, 2024

I downgraded from 5.05 to 5.02 to have access. Now it works with my M500 Plus.

@MTrab MTrab mentioned this issue Aug 8, 2024
@mkaiser
Copy link

mkaiser commented Aug 20, 2024

it works for my M500 (WR141E).

as a temporary workaround you can re-enable it with the current version by manually reverting the commit https://github.com/MTrab/landroid_cloud/pull/607/files

just unomment the lines 37-53 in config/custom_components/landroid_cloud/number.py and restart HA.

@Bailey0721
Copy link

Bailey0721 commented Aug 24, 2024

Is there anything new here? Unfortunately, we haven't heard anything since May. It was a great solution to control the torque via Home Assistant. I wish it would work again. The workout from #672 works great, but an official release would of course be better :-)

@MTrab
Copy link
Owner

MTrab commented Aug 24, 2024

This is a very low priority issue for positec, so nothing new to this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests