service: mqtt.publish
data:
topic: valetudo/Dustin/MapSegmentationCapability/clean/set
payload: '{"segment_ids": ["18"], "iterations": 1, "customOrder": true}'
Try now please 
and use the YAML editor to edit the serviceā¦
Itās still the same error.
But I have to create this in Automations and Scenes under the āScriptā tab, or am I completely off track?"
you just need the script and then expose it to Alexa.
alias: Clean the kitchen
sequence:
- service: mqtt.publish
data:
topic: valetudo/Dustin/MapSegmentationCapability/clean/set
payload: "{\"segment_ids\": [\"18\"], \"iterations\": 1, \"customOrder\": true}"
mode: single
This is what comes out from the editor I replaced the name of the vacuum to yoursā¦ but It works in my case. And I suppose it should be the same you haveā¦ if this do not work there could be another reasonā¦
1 Like
Okay, it works, thank you very much for the help again. Any idea why the other one didnāt work? Just so I might understand it.
I think it is related to the way Home Assistant share the data with Alexa. In any case the Service as per it call by Yaml format can need to be in the correct format. I donāt know the other test you did anyway as per now works with the script you can edit the room number and choose also to add multiple segments in thereā¦ Happy assist you, and have fun with your integration 
Here I am again. I must be doing something wrong again. But what?
sequence:
- service: mqtt.publish
data:
topic: valetudo/dustin/GoToLocationCapability/go/set
payload: |
{\"coordinates\": {"x": 3032, "y": 2844}}it is to go_to right?
"payload: {\"coordinates\": {\"x\": 3032, \"y\": 2844}}"
probably this?
Yes, itās āgo to.ā But itās not working; I thought I had understood it now. "
Home Assistant does that from my YAML.
alias: Auf zum MĆ¼ll
- service: mqtt.publish
data:
topic: valetudo/dustin/GoToLocationCapability/go/set
payload:
\"coordinates\":
\"x\": 3032
\"y\": 2844service: mqtt.publish
data:
qos: "0"
topic: valetudo/dustin/GoToLocationCapability/go/set
payload: "{\"coordinates\": {\"x\": 3032, \"y\": 2844}}"
This worked with my S5, I think you did not send a correct json format to the vacuum this is why it is not working on your serviceā¦
Home Assistant reports:
Message malformed: extra keys not allowed @ data[āserviceā]
Could something be wrong with my Home Assistant settings?
@Flodo1987 I just test it with my vacuum once again this is a script, when you open your script and edit it in Yaml you can simply copy past the below and change just the room name, this should work.
alias: vacuum go to kitchen
sequence:
- service: mqtt.publish
data:
topic: valetudo/Dustin/GoToLocationCapability/go/set
payload: "{\"coordinates\": {\"x\": 3032, \"y\": 2844}}"
mode: single
if the topic is ādustinā is wrong there should be no error but the vacuum probably donāt move in here I change the topic to āDustinā that as per you wrote above should be correct. Pay attention to the spaces and format. I repeat just copy the script as it is.
1 Like
did it work?
Thank you, it works. I just donāt understand why the previous one didnāt work. And yes, Iām doing nothing different than copy and paste 
.
Hi, could you please stop using the logo in your communication the way you do it right now?
Like with the banner on GitHub and here?
How it is now makes it look like itās something official which it simply isnāt. Itās a third-party project with different visions and goals - which is fine of course, but it should be clearly understandable as such by newcomers.
Right now itās very confusing and will likely lead to conflicts in the future which Iād very much want to avoid.
Thank you
@Hypfer done in hereā¦ I will remove it also form the GitHub if this is what you wantā¦ I simply wanted to sponsor your projectā¦ not make so that this āthird-parityā project as āofficialāā¦ it okay and understandā¦ I putted a lot of effort in creating this camera and the only goal I had was to make so that your work could be appreciated form the mostā¦ anyway thanks once again for giving us Valetudo
Thank you. Yeah that would be best.
Donāt get me wrong, I think itās cool what youāve built and I can see that quite a lot of effort went into that.
Please donāt let this demotivate you as this definitely brings value to people and even if it didnāt it seems that youāre having fun building it which is the only thing that matters
After half a decade of doing this, I just learned a few things; one of them being that autonomy is the sole driving force for me and so is avoiding any avoidable conflicts caused by confusion.
I can only do that by communicating as clear as possible, which is harder when there are other sources that at a quick glance look like official communication but donāt really line up in their messaging.
Which again doesnāt mean that you should change anything about your mission and goals. It should just be communicated in a way that - even to a very lazy user that just barely skims a text - it is clear that itās your mission and your goals which arenāt necessarily identical to those of Valetudo.
Again, thanks for this quick response!
Well Iām having / had fun building up this integrationā¦ and it is now in a quite stable level according to the stats.
Please understand, Iām having also some different communication ways that probably comes from my work environmentā¦ (I do not write code for livingā¦ form me this is just an hobby just for clarity).
I mean simply try to keep it as professional it can be and this I guess is the ācommunicationā issue between usā¦ too. as per it can feel āintimidatingā sometimes.
Autonomy wiseā¦ well I understand perfectly what you meanā¦ I had also a custom banner and icon for this component but in the last minute thoughtā¦ in the end the guys that did the job to create this alternative deserve for instance advertising (and I know alsoā¦ what are the Valetudo visions, also a big fun of what you guys are doing).
This replay is simply to ensure you there is no āconflictā intentionās hereā¦ but just collaboration spiritā¦ you care about the vacuum firmwares, we do whatever possible to make them easy to integrate, I guess this isnāt conflict of visions neither something wrongā¦ but just an attempt to somehow cooperate and speak out when concretely there is something to discuss.
As you statedā¦ not every one is willing neither having the know how toā¦ this is also because, honestly, myself didnāt get it rightā¦ and it can take some time to get the vacuums fully operating after āun-cloudā them in HA, sometimes this could be a little frustratingā¦ so letās put a little sugar on the āblue pillā and letās see how deep the rabbit hole isā¦ this project born mainly for this reason.
Anyhow, once again thanks, I had/have in plan to make so that HA would recognizes the vacuums with Valetudo firmwares and automatically configure this camera (this is because this will happen having an āofficialā Integration in HA, MQTT just give the basic vacuum functionality as you know), the camera simply render the mapsā¦ without additional workā¦ in the end also because Valetudo is indeed fully what Home Assistance stand for (or use to be)ā¦ a cloud free alternativeā¦ of course if you @Hypfer and Denis, actually also rand256 agreeā¦
If not, and this must be clearā¦ well Iāll keep this project as it is in a āthird-parityā level, the āCustom Componentā is a quite stable level. Could be possible to bring it at āIntegration levelāā¦ anyhow now not for ādemotivationā but just to confirmā¦ I guess your last replay give me the green light to go ahead with thatā¦ If notā¦ well letās keep all as it isā¦
Yeahā¦ please donāt. That would make things much more difficult and error-prone.
Right now, Valetudo publishes all its entities exactly how they should be to MQTT and its auto-discovery feature. This means that things just work, because the Valetudo version that publishes that auto-discovery data also knows exactly what it can do, what payloads it needs etc.
By having an integration, said integration then suddenly needs to be aware of subtle changes between Valetudo versions, handle all different ones and put in effort to stay in sync.
Furthermore, you then suddenly have multiple ways of integrating Valetudo into the same software that both do essentially the same thing. That would greatly harm the UX so Iād ask you to please not do that.
If there will ever be the need for an integration in Home Assistant for Valetudo, Iād like to be in control of that. For now though, MQTT Autodiscovery works more than fine so thereās really no reason to make things worse.
That said, you could probably build that camera renderer so that it autodiscovers autodiscovered Valetudo devices and augments them with the rendered image. That would definitely still be a custom_component though and not a mainline integration. e.g. like PowerCalc
@Hypfer well I had to read your comments several times anyhowā¦ I got it nowā¦ it is a good point what you raised. It works great as it is so we will keep all as it isā¦ thanks a lot once again for your time.
Very cool project, although I am noticing an odd issue. The map renders perfectly fine when the robot is docked but when the robot is cleaning, Home Assistant completely locks up and I can no longer access the front end. After the vacuum returns to the dock everything on Home Assistant returns back to normal. It seems like something might be happening on the main thread and the image is being re-rendered too frequently?