You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since changing to a new Worx Vision Mower (WR206E), schedules via "landroid_Cloud_schedule" are not visible in die Landroid Worx App on the Smartphone (Samsung S23+). With the Worx Mower WR105SI.1 (wire based) schedule could always be sent
What version of Home Assistant Core has the issue?
2024.3.3
What was the last working version of Home Assistant Core?
2024.3.3 (with old Mower WR105SI.1 )wire based
What version of the Landroid Cloud integration do you have installed
4.0.6
What type of installation are you running?
Home Assistant OS
Which make and model is the mower used for this integration?
Worx Vision WR206E
Diagnostics information (NOT log entries!)
schedule service does not throw an error. Finishes with "Aktion erfolgreich"
Relevant log entries
schedule service does not throw an error. Finishes with "Aktion erfolgreich"
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the issue
Since changing to a new Worx Vision Mower (WR206E), schedules via "landroid_Cloud_schedule" are not visible in die Landroid Worx App on the Smartphone (Samsung S23+). With the Worx Mower WR105SI.1 (wire based) schedule could always be sent
What version of Home Assistant Core has the issue?
2024.3.3
What was the last working version of Home Assistant Core?
2024.3.3 (with old Mower WR105SI.1 )wire based
What version of the Landroid Cloud integration do you have installed
4.0.6
What type of installation are you running?
Home Assistant OS
Which make and model is the mower used for this integration?
Worx Vision WR206E
Diagnostics information (NOT log entries!)
schedule service does not throw an error. Finishes with "Aktion erfolgreich"
Relevant log entries
Additional information
No response
The text was updated successfully, but these errors were encountered: