Closed KingKahn123 closed 4 years ago
Most likely an issue with the MQTT Broker integrated in IPSymcon. We also had issue reports from FHEM Users since their Broker was broken (as in: not standard compliant) as well. See: https://github.com/Hypfer/Valetudo/commit/28149f098fe13930c48611b74373210719027ba4
The bytes you've posted decode to a chunk of comma-separated arrays of two numbers each. That's the map data format you're seeing there. Pixel-coordinates to be precise
My assumption is that the broker can't handle large MQTT messages properly . They most likely didn't add those as a test case because afaik they don't appear often in the wild :)
You might want to report this to Symcon GmbH. According to the mqtt spec, the maximum payload size is 256mb and this is far below that limit.
Ok, the issue is solved. Not quite sure what the reason was, but now it is working without crashing my system...
Hi,
I have activated the MQTT function of Valetudo. In my IPSymcon MQTT Server I see 3 attributes coming from Valetudo "attributes", "map data" and "state". "attributes" is regularly updated. When I start a cleaning session Valetudo is sending continously following MQTT messages:
These continuously messages crashing my IPSymcon system. Do you have any clue what the problem with my installation is?