oven-lab
commented
9 months ago This seems to be the way tuya cloud works. It only stores the latest couple hundred points. Then you have to get the rest locally.
Most vacuums seems to have a pathComm or rawComm DP, but I haven't tried getting the data from my vacuum yet.
You seem to be lucky, and your vacuum already spits this data out without having to ask for it. I could add a service or something of the kind to add position points through home assistant, until I get the whole localtuya protocol up and running. Perhaps during the coming week.
backcountrymountains
Unfortunately, the path information retrieved from the tuya cloud doesn't update frequently with my vacuum. For example, the last time I ran the vacuum it only updated the path once during the whole 40 minute cleaning time.
However, my vacuum does barf out a constant stream of base64-encoded json-formatted data while it's running. One part of that data is the vacuum's position:
returns a constantly updating stream of data:
I don't know what "phi" is.
I don't know if other vacuums also send out this data, but I was wondering how hard it would be to use the data directly sent from the vacuum to draw the path and mark the vacuum's current location on the map.
I've also noticed that when I look at the map in the tuya app, it seems to load path sections sequentially in order to display the combined most recent total path. That is, it loads the path from one area, and then another area, and another on top of the map. Perhaps, my vacuum has a weird way of storing the path data in the tuya cloud and this integration is only downloading the initial path segment and not subsequent path segments?