Lovelace: Landroid card

Frank_Beetz · October 4, 2022, 4:37pm

My Worx S500 is up and running again - thanx a million for your work!

A-Jey · October 8, 2022, 1:11am

Hi there.

After updating to the new landroid cloud version (coming from 1.8.2) and to the new card
i see that all sensors are gone and now there are attributes only.
In addition to that it’s one attribute for several states.

I created this complete page for the old versions and I got no idea how to get this working again now:

At the moment I am trying to figure out how to get template sensors for these attributes running,
but i stumble upon this:

For example, when I enter the following into developer template
{{ states.vacuum.robby.attributes.firmware.version }}
i got the result: “3.27”
but if I enter it this way:
{{ state_attr(‘vacuum.robby’, ‘firmware.version’) }}
the result is: “none”
If I only enter firmware (without.version),
both results are “{‘auto_upgrade’: False, ‘version’: 3.27}”

Same problem if I use attribute on an entities-card:

type: entities
- type: attribute
  entity: vacuum.robby
  name: Firmware Version
  attribute: firmware.version

it doesn’t work.

Is there anybody who can help me with this issue?

Thank you.

Frank_Beetz · October 8, 2022, 9:04am

Make template sensors like this:

Version → value_template: “{{ state_attr(‘vacuum.robby’, ‘firmware’).version }}”
Auto Upgrade → value_template: “{{ state_attr(‘vacuum.robby’, ‘firmware’).auto_upgrade }}”
Bladetime → value_template: “{{ state_attr(‘vacuum.robby’, ‘blades’).current_on }}”
etc. etc.

Barmalej · October 8, 2022, 9:16am

And

{{ state_attr('vacuum.robby', 'schedule').primary.monday.start }}
{{ state_attr('vacuum.robby', 'capabilities')[0] }}

→

11:00
Edge Cut

A-Jey · October 8, 2022, 11:37am

Thanks a lot for your help.
I tried everything except the point after the closed bracket.

Any idea about the correct syntax for the attribute on the entities card?

I made use of it before the update and there was no need to add template sensors.
Here’s an example of the old config.

Frank_Beetz · October 8, 2022, 1:58pm

No idea how to deal with nested attributes in an Entity Card, but you could create sensors for all the items you are interested in (Batteriespannung, Batterietemperatur, Ladezyklen, etc.) and then put them as entities in an Elements Card,

dumber · October 22, 2022, 8:35am

Hi

Since some days I have a problem communication with my robot. In android app everything ok. I can see robot status and I can send any commands to it.
In Hassio something went wrong. Landroid Coluds connected to Worx server. Integration can read robot name. (if I change in the android app also change in Hassio to.). But thats all.
Status is : Initializing.
No information about moving, charging, blade time . etc. Also can’t send commands to the robots. I get MQTT connection issue…
I already deleted all parts, and reinstall again. Robot was repairing too. No solution.

Does anyone have similar problems?

I know this forum for Lovelace card, but I not found better forum.
(All parts are up to date)

Thanks.

Smartzeug · November 9, 2022, 7:52am

Hi there,
I created a video for the worx landroid using the updated method with the landroid cloud and the landroid card. In case you need video guidance jut have a watch.

It is in german though, but you can use auto subtitle from youtube

Hope it helps

BlackChart · November 19, 2022, 6:40pm

Any wishes for Landroid_Cloud v3?
I’m currently doing the finishing touches for making the pyWorxCloud module fully compliant with the API as documentented by Positec.

Shortly I’ll begin adapting this to the Landroid_Cloud integration, so if you have some wishes for the new major overhaul of the integration, speak up now

QbaF · April 28, 2023, 6:38am

I read carefully this and previous thread and have a few questions for you, more experienced already in using HA with Landroid:

If you are using Landroid with HA do you switch off all Landroid automatics (schedulers, rain-delay, etc…) and made it fully automated by HA or leave something for Landroid (e.g. mowing time)?
What does exactly Play/Start do? Is it just start or start for calculated by Landroid time (for defined lawn area, grass species, soil, fertilizers)?
Do you experience sometimes problems with multi-minute lags in gathering data for HA from Landroid? Or is it just now when the Landroid_Cloud is in its new beta version?
What does trigger data import from Landroid to HA? Maybe it is a question of how it is planned to be in Landroid_Cloud v3?

ilgio · May 7, 2023, 3:37pm

The zone with new update. Doesn’t work

ilgio · May 12, 2023, 4:47pm

@Barmalej can you help me?

klogg · May 12, 2023, 4:53pm

I was wondering if it would be possible to expose the One Time Schedule?

Whatever the answer, thanks for this integration!

BlackChart · May 16, 2023, 7:16am

No - barmalej can’t help you, as it’s a bug in the Landroid_Cloud integration and not the card.
I’m pretty sure it’ll be working for you when I get the time to investigate why it’s not mapped/interpreted the right way

ilgio · May 16, 2023, 8:08am

ok thanks very much
I wait

ilgio · May 29, 2023, 12:55pm

there have been updates to the landroid integration, but the zones still don’t work

Barmalej · June 17, 2023, 8:50pm

Finally a new release

ilgio · June 19, 2023, 2:56pm

wowww…
what is Torque?
and Time extension?

Barmalej · June 19, 2023, 3:43pm

In simple terms, you can increase or decrease the power of the motor.

This is increasing your Auto Schedule time

Vatte · June 27, 2023, 9:39am

I’m missing the attribute values on the landroid card. I can’t tell if it’s since the update to 2023.6.3 or if it has a different cause.

Landroid card 0.2.7:

image: default
image_size: '3'
show_animation: true
show_status: true
show_toolbar: true
compact_view: false
show_name: true
show_configbar: true
type: custom:landroid-card
entity: vacuum.kr113_pelle
stats:
  default:
    - attribute: blades.total_on
      subtitle: Total Messer Laufzeit
      value_template: '{{ as_timedelta((value | float(0) * 60) | string) }}'
    - attribute: blades.current_on
      subtitle: Aktuellle Messer Laufzeit
      value_template: '{{ as_timedelta((value | float(0) * 60) | string) }}'
    - attribute: statistics.worktime_blades_on
      subtitle: Mähzeit
      value_template: '{{ as_timedelta((value | float(0) * 60) | string) }}'
    - attribute: statistics.distance
      value_template: '{{ (value | float(0) / 1000) | round(3) }}'
      unit: km
      subtitle: Distanz
  mowing:
    - attribute: orientation.yaw
      subtitle: Fahrtrichtung
      unit: °
    - attribute: orientation.roll
      subtitle: Seitenneigung
      unit: °
    - attribute: orientation.pitch
      subtitle: Anstieg/Gefälle
      unit: °
shortcuts:
  - name: Notification
    service: automation.toggle
    icon: mdi:bell
    service_data:
      entity_id: automation.mower_notify_status
image_left: false

Does anybody have an idea what could I check to solve this problem.