Combisteamer - invalid JSON responses

[Scott Gerring]

On the API endpoint ai?command=getLastPUSHNotifications, I've started getting incomplete JSON responses. This breaks the device in Homeassistant completely (as well as v-zug device website and app).

[{"date":"2024-03-25T16:07:36Z","message":"Der Betrieb wurde beendet."} ,{"date":"2024-03-25T15:17:47Z","message":"Das Vorheizen wurde beendet. Bitte schieben Sie das Gargut ein."} ,{"date":"2024-03-25T14:26:00Z","message":"Der Betrieb wurde beendet."} ,{"date":"2024-03-25T12:27:47Z","message":"Aufgeheizt"} ,{"date":"2024-03-21T16:53:09Z","message":"Aufgeheizt"} ,{"date":"2024-03-21T10:28:02Z","message":"Aufgeheizt"} ,{"date":"2024-03-18T16:31:15Z","message":"Aufgeheizt"} ,{"date":"2024-03-18T14:18:39Z","message":"Der Betrieb wurde beendet."} ,{"date":"2024-03-18T14:13:18Z","message":"Der Wasserbehälter ist leer. Bitte füllen Sie ihn mit frischem Wasser auf. Sonst kann das Gerät den Prozess nicht fortsetzen."} ,{"date":"2024-03-18T14:11:]

I will write V-Zug about this as it's obviously a bug on their end! In the meantime 1/ are you aware of any tricks to get the device back into a good state and 2/ if this is a common problem, is it worth wrapping the JSON parsing up in a try/catch to soldier on when V-Zug misbehaves?

Cheers and thanks for the great work!

Scott

[Simon]

Oh wow that's an interesting bug. I haven't encountered this one yet so I unfortunately don't have an idea how to fix it.
I noticed that with one of my devices (adorawash) fully power-cycling it by completely unplugging it helped resolve an issue related to a different API issue.

As for handling this kind of issue gracefully, I believe that's something I implemented in the pre-release version of the extension which I haven't gotten around to releasing yet. Maybe give that version a shot?