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

Device is not updating after a while #615

Open
nbai777 opened this issue May 11, 2024 · 22 comments
Open

Device is not updating after a while #615

nbai777 opened this issue May 11, 2024 · 22 comments
Labels
bug Something isn't working

Comments

@nbai777
Copy link

nbai777 commented May 11, 2024

Describe the issue

After a while the device does not updates itself in HA, and I'm unable to send command to the lawnmower.
This happens sometimes after a few hours, sometimes after days. If I reload the integration it fixes itself but only for limited time again.

What version of Home Assistant Core has the issue?

core-2024.4.2

What was the last working version of Home Assistant Core?

Before winter sleep of the mower.

What version of the Landroid Cloud integration do you have installed

v5.0.4

What type of installation are you running?

Home Assistant OS

Which make and model is the mower used for this integration?

Landroid WR130E

Diagnostics information (NOT log entries!)

config_entry-landroid_cloud-57a834ba16175855420d56dbe839fb24 (1).json

Relevant log entries

None

Additional information

No response

@nbai777 nbai777 added the bug Something isn't working label May 11, 2024
@MTrab
Copy link
Owner

MTrab commented May 13, 2024

Have been trying for a while to fix bugs like this - I do not see this when I test, so it's pretty difficult to fix.

I have no idea what I can do, unfortunately

Repository owner deleted a comment from Hrast100 May 13, 2024
@nbai777
Copy link
Author

nbai777 commented May 14, 2024

I see, but you know since I posted this issue the integration is working fine without any problem :)

@tomek550
Copy link

tomek550 commented May 17, 2024

Having same issue on my WR167. Are there some debug logs I could check?

@sithmein
Copy link

I had similar problems when my internet connection dropped.
I have created an automation that reloads the integration after one hour with no update.

alias: Restart Landroid Cloud Integration
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.mower_last_update
    to: null
    for:
      hours: 1
      minutes: 0
      seconds: 0
condition: []
action:
  - service: homeassistant.reload_config_entry
    target:
      device_id: 99c934e66ccd6e6c211515a345965aaa
    data:
      entry_id: abc8adb6e3837e5375be0b7d5474dc16
mode: single

@johngianni
Copy link

Same Here... No updates after sometime.... Normal conditions. Thanks for the workaround @sithmein

@ra1do
Copy link

ra1do commented Jun 4, 2024

I see no updates at all (not regularly, not when refreshing status in app). Only when reloading integration. Last update 16 hours ago while mower is mowing, charging, I am using app. I was hoping to do some automations according to mower real-time behavior, but that needs much more frequent updates than once in hour. I'd love to monitor traffic or debug some other way to understand why it does not update automatically. Would it be ok to reload integration once every 5 minutes?
I have several tasks in my mind:

  • detect when mower is not mowing while it should move. Probably it has run onto something and wheels are not getting good touch. Or maybe just front wheels are stuck and back wheels just dig holes or some other case when mower thinks its moving, but it's not. If ha detects that mower is in the same spot I would like to initiate pause-start or baseboard restart or smth like that to get out of the trap.
  • log wifi signal strength to see how good is wifi coverage
  • If it is possible to get the border wire signal strengths (lcd shows) I could log them and try to estimate where could mower be (near the border or not for example) and locate it more easily when it's stuck. Ok, that one is not so dependent on frequent updates.

@sithmein
Copy link

sithmein commented Jun 6, 2024

As far as I know you cannot poll updates too frequently otherwise Worx will lock your account.

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

I noticed that update was a bit erratic, saw it once get to 15 minutes. I created an Automation that writes 181 to the rain delay, then 5 minutes later I set the rain delay back to 180 then repeat 5 minutes later. Doing a write forces the rest of the data to update. That seemed to work, so I then added some smarts around what the mower was doing, if docked then don't do the update; if mowing then force read every 5 minutes. Not tried shorter times yet; anyone know what the rate is to get a ban?

@MTrab
Copy link
Owner

MTrab commented Jun 12, 2024

DO NOT do that! You will end up in a ban!
Let the integration handle this

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

Interesting, thanks, but its OK to reload the Integration once an hour; I can just change the 5 minutes to once an hour. Do you know what the max rate is before you get a ban?

@MTrab
Copy link
Owner

MTrab commented Jun 12, 2024

Positec will not reveal.

But why force a refresh or even reload, when the integration handles this for you?

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

I've only had my Landroid a few days and I felt the update frequency was too slow as I said sometimes 15 minutes and was looking for a way to control this. I also notice that the Landroid never shows as Disconnected. I had it switched off all night and showed Connected all the time.

@MTrab
Copy link
Owner

MTrab commented Jun 12, 2024

The state updates when the mower publishes data to the API - that differs depending on the state of the mower, but most regular update interval is 15 minutes when charging. Nothing can change this, not even a forced refresh or reload

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

OK we are reliant on Positec.

But looks like they don't report a Disconnect ?

@MTrab
Copy link
Owner

MTrab commented Jun 12, 2024

If the mower is offline for an extended amount of time, it will report disconnected.
Awaiting data update is not equal to a disconnect

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

It doesn't report disconnected. I had mine off over night and was still showing as connected.

@MTrab
Copy link
Owner

MTrab commented Jun 12, 2024

That might be a bug from the API then. The availability state is what the API reports, so as long as that reports online, then that's what Home Assistant shows

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

OK thanks, is it possible to report back to Positec and get the API updated? It would be really useful to know if the Lardroid has disappeared.

@MTrab
Copy link
Owner

MTrab commented Jun 12, 2024

I can try, but issues like this is VERY low priority

@IanJS46
Copy link

IanJS46 commented Jun 12, 2024

Thanks; no worries; be good if it can be fixed.

Thanks for your help today

@luzik
Copy link

luzik commented Jul 10, 2024

This looks like #351 , maybe main bug is still there.

I have trouble too, and I'am ready to assist, but for now, don;t have anything new to add

@ra1do
Copy link

ra1do commented Sep 11, 2024

I see no updates at all (not regularly, not when refreshing status in app). Only when reloading integration. Last update 16 hours ago while mower is mowing, charging, I am using app. I was hoping to do some automations according to mower real-time behavior, but that needs much more frequent updates than once in hour. I'd love to monitor traffic or debug some other way to understand why it does not update automatically. Would it be ok to reload integration once every 5 minutes? I have several tasks in my mind:

YES! Finally integration started to update status automatically few days ago. Now I can move forward with automations. I have not done anything unusual. Just updating HA and restarting as I have done several times after landroid installation without any change. If there is someone like me who has installed landroid months ago and never got any automatic status updates maybe it is time to try again. It might work now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants