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
Describe the solution you'd like
A clear and concise description of what you want to happen.
Not sure what's the best way, but for example like this:
configure vacuum entity - either by sensor entities for x,y,z or by vacuum entity itself (latter one would be more generic for other systems as well, e.g. person tracking)
add transformation for coordinates from robo coordinate system to flat coordinate system
take the robot model group object_id
When the position of the sensors update, the position of the model also is moved accordingly
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Seems like there are not really other solutions at the moment
Additional context
Add any other context or screenshots about the feature request here.
Use Cases:
Visualize moving persons, e.g. with data from camera/beacon tracking
Visualize vacuum robots based on their position in their own map
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It's somewhat possible to get the coordinates of xiaomi/roborock vacuums (https://github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor).
I'd like to use those to visualize a 3d model of the vacuum in the 3d model of the flat.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Not sure what's the best way, but for example like this:
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Seems like there are not really other solutions at the moment
Additional context
Add any other context or screenshots about the feature request here.
Use Cases:
The text was updated successfully, but these errors were encountered: