PulsarFX

@microfrost1 and @pedro2d10 did you manage to move the robot from under the cabinet? I tried to call ``` service: xiaomi_vacuum.vacuum_remote_control_move_step data: entity_id: vacuum.dreame_f9 velocity: 100 rotation: 90 ``` but...

Hm, that's the same I use. May it be because of this warning? ``` [homeassistant.helpers.service] Unable to find services.yaml for the xiaomi_vacuum integration ``` edit: https://github.com/microfrost1/xiaomi_vacuum/issues/11

yes, doesn't move. What model is thor? with the services.yaml this is what I see: 

with the latest firmware 3.5.8_1050 it actually does respond :) note: for me 90° is 63.75 (64) which is 4 * 63.75 = 255 which is 1111 1111 for velocity...

had the same issues, which are now gone.

How does OsmAnd do this? You can use the map like it would be on the phone. 🤔

Oh good to know. And here we come back to the routing from charger to charger combined with feeding live data to EvMap we talked about once ;-)

For ease of maintenance, you could provide a simple API like ``` { "soc": "12.3", "speed": "45.6", "range": "78" } ``` whereas I am not sure about speed and range....

So what about a simpler approach for evmap: define some intents where evmap is listening for the required data values. Then, which ever App Broadcasts them is a valid data...

Ah this makes things clear ;-) I think having it in a public channel is not a problem anymore, nor would it brake anything. Users can change the lockscreen appearance...