alexkn / node-red-contrib-valetudo

A Node-RED node to convert Valetudo map_data to a png image wich can be send to a dashboard template node.
Apache License 2.0
14 stars 3 forks source link

Valetudo RE: Incorrect Header Check #11

Closed nicedevil007 closed 3 years ago

nicedevil007 commented 3 years ago

Hey @alexkn

tested your node again after switching from my old node-red installation to my new integrated one in ioBroker. I get this error:

image

I'm using ValetudoRE so I tryed to use valetudo-parse-binmap in front of the valetudo-map-png and the opposit as well. Still this error.

Like so: image

And here an example what valetudo is offering:

image

alexkn commented 3 years ago

Feel free to send a pull request.

nicedevil007 commented 3 years ago

Sry don't know what you mean :( Or how to do this. So it is Valetudo RE related and won't be fixed in a future patch/release?

alexkn commented 3 years ago

I will not fix it, because I don't use RE. Probably I will remove RE support completely at some point, as the map format is too different now.

alexkn commented 3 years ago

Something is wrong with your map data. Valetudo RE should send gziped data which should start with 1F8B instead of 1FEF in your data.

hoyohayo commented 3 years ago

Acutally this is not only happening with Valetudo RE. I am on a Roborock S5 Max with Valetudo Version 2021.03.0 my output of the Map Data is starting as followed:

Node_Red_Valetudo

My debug from the output node is showing the same thing "incorrect header". I am not really sure where the problem is...

alexkn commented 3 years ago

@hoyohayo Disable Homeassistant Map Hack in Valetudo MQTT Settings

hoyohayo commented 3 years ago

@hoyohayo Disable Homeassistant Map Hack in Valetudo MQTT Settings

Thanks for the update! That actually helped a lot!

alexkn commented 3 years ago

@nicedevil007 The EF BF BD in your map data indicates a failed utf-8 encoding as described here: https://stackoverflow.com/a/6544206

I assume with your switch to ioBroker you switch to a bad mqtt broker which destroys the binary map data. You have to fix your mqtt setup. So this is not a problem of this node.

miguelpruivo commented 2 years ago

@alexkn all of a sudden I started to experience this issue with a S50. It was working great before. Do you know what it could be? Thanks!