Missing Map #4
Comments
|
Try enable debug log in the integration. This will log all data received. |
|
There are some sensors missing for me: All mull_meter are distance clockwise along perimeter in cm to the zone entry point. Can later be used with map. I think they overrule the mul_zonX values. mul_proX is the percentage of time this zone is supposed to be used. 2024-04-21 07:41:38.272 DEBUG (Thread-3 (_thread. |
|
More unparsed data on mine. On_min/total_min is the same on mine. It is total time in minutes. One of them should be exposed. Cur_area seems to be increasing when mode = 1. Not sure about units. Could be 10* m2 mowed. Is 42 after 1 min - 210 after 5 min. With 1.2km/h = 0.33m/s we have max 18m/min. Multiply by 0.2m cutting diameter that is theoretical max of 3.2m2/min. My guess is that we are closer to 0.42m2 when it says 42. After 60 minutes it says 2520. Thus likely 25.2m2. After mowing 228 minutes it says 9492. Almost 4hours and less than 100m2 ?? I think the number might be too low. Say average is 3m before hitting something, that is 10s, then 5s to stop/turn be up to speed. It should have a cutting speed of 2/3 or at least half of max. Guess I have to do something manual. Say measure 10 or 20 meters. Let it cut/move straight and see result. 2024-04-21 10:52:14.388 DEBUG (Thread-3 (_thread |
|
And some data on my device om_components.sunseeker.sunseeker] MQTT message: /app/xxx |
|
I have forked the project, and will add support for more sensors. And found these keys in the JSON - I found no map. Number of times battery charged / discharged might be nice to have, as well as others. I will submit code back when I have added more sensors to my own fork.
|
|
There are a lot of sensor im not exposing. I'm only exposing sensors I think is relevant. |
|
Map status is queried by Map can de requested deleted in app. Deletes it on server as well Specific map version is retrieved by: and data is as below. I have no idea about message format. Cutting area is about 22m wide, and 25m heigh according to quick check on google maps Not sure if I will get obstaclesNum > 0 without Ultrasonic. |
|
Just a quick note. You have to find another way instead of pooling. You will be banned (and risk they block the integration) |
|
Some sensors like battery makes sense. Map metadata is queried once in a while - together with query for mower state - and if map updated (mapSn changes) another call is made to retrieve the map. Exposing a way to call check and update the map would be nice. I am working on it. Map status is where you get perimeter length and area as well. Area will be sent to MQTT as well after query. Map update (if updated) from an automation could run once a day. Distance to zone start and zone time % are sent to MQTT when updated. Not sure if there is a more passive way to get it. I think some sensors should be suppressed unless available. Like the map stuff. |
|
And relevant values that should be exposed are mul_pro1..mul_pro4 - they set the percentage of time that the mower should use that zone starting point. Thus you can set it to start at the backyard 10% of the time, one entry point where it rarely goes 20% of the time, and let the others at 0% (aka disabled), and it would likely start those at the base. Right now you force 25% at each zone point, destroying settings already set thru the app. The meters are nice, but could be read only. Not sure if you need to submit them. Meters/percent covers the same. Lawn area should be pretty static - ony updates with map aka border cut I think, but would be nice to have. But it is updated only in MQTT when the map version is requested (by GET /api/map/work-map/newest/1/$sn ) An exposed service to update values would be nice. Should poll data. And a comment not to call it often. Mapdata should be retrieved as part of this if map available. And could easily be rendered in SVG form as a path. |
|
Can you set the mul_pro1..4 in the app?. I need to submit all. Meter, mul_pro and start percentage. Area covered are updated every time the battery status change on my end. |
|
My Clever 1000 has the map. And below the map I can set frequency percent - one does not influence the other. Thus I can have all at 40%. Meter might be a calculated value. When I move a spot along the wire percent slider is moved as well and vice versa. |
|
My mower does not care about the mul_pro values. I can set mul_pro1 to 10% and it reads back 25. Can you please post you mqtt message with mul_pro values, so i can be sure to read the correct values, because i don't get them. I will do some more testing before commiting.
|
|
Sorry. You posted it earlier. "mul_pro1". |
I wanted to expose the values, but not knowing what they mean does not make any sense. on_area 139820 - 139461 = 359 I have 3591 units in 95 min. = 2268 in 60 minutes. |
|
Here is a screenshot of the app where I can change the time settings for the individual zones. Changing startpoint moves the zone dots on the map.
Here is raw MQTT log of me going to the map and adjusting some frequencies. |
|
As for on_area / cur_area, they are either measured or guessed/estimated areas (since on / current mowing process). 0.35m/s * 60s * 0.2m = 4.2m2 per minute. All too nice values to be a coincidence. And the 1.2km/h in the manual is 0.35m/s instead. But it is clear, that hitting obstacles or wire, stopping, turning, accelerating make it impossible to keep this speed. They could at some point take this into account. say pause their time component when not moving forward. |
I have a Grouw Clevr 1000. It has a map display after first edge cut. Showing length of perimeter and area as well as the map itself.
What can I do to help get it into HA ?
Is it just setting the phone to use a Burp or Fiddler proxy to log traffic ? Or is there any additional encryption layer, certificate pinning etc on top ? Or was the integration done by decompiling the Android App ?
The text was updated successfully, but these errors were encountered: