Internet friends, do any of you have a Fronius Gen24 series solar inverter on the same network as a Linux computer?

EDIT: Thanks everyone, I've got a few solid samples back now! Much appreciated

If so, could I trouble you to please run the following two commands and send me back the output?

avahi-browse -rv _Fronius-SE-Inverter._tcp

avahi-browse -rv _Fronius-SE-SmartMeter._tcp

(If you've not got the "Smart Meter" addon then the second command might not do anything, not to worry if so.)

Is all in the aid of reverse engineering for interoperability. If what I'm trying to do works then it'll be open sourced. 💪

Boosts for reach appreciated!

@projectgus I have a Gen24 and just installed avahi on a Linux VM. I don’t see anything back from either of those commands and there’s nothing vaguely Fronius looking in “avahi-browse -a” either?
@projectgus Fwiw: Web interface is showing as Symo GEN24
10.0 GEN24 Software Version 1.38.7-1
@projectgus Looks like it takes a while to advertise. Just the Inverter so far, no SmartMeter yet: https://pastebin.com/W99tb4JM
$ avahi-browse -rv _Fronius-SE-Inverter._tcpServer version: avahi 0.8; Host na - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

Pastebin

@spudly Amazing, thank you! It's that big blob of pseudo-JSON in the txt record that I was hoping to get a sample of.

It's possible not all of them advertise the SmartMeter service, I don't really know

@spudly huh, I just managed to notice that somehow the response cuts "Manufacturer" in half (some at the top and some near the end.)

So maybe this isn't pseudo-JSON but actually longer JSON that's been somehow mangled by Avahi, lol.

(Anyway, that's not your problem! Thanks again)

@projectgus @spudly I'm hopefully getting a Gen24 next month or so

@spudly I worked out why the JSON looks mangled. It's cursed:

DNS-SD TXT records are optionally KEY=VALUE pairs. But Fronius want to pack a JSON object in there instead for some reason, and there's a length limit on each TXT record.

So the format Fronius picked for TXT records is:

00={<first part of JSON blob>
01=<second part of JSON blob>}\n

avahi-resolve reasonably prints the TXT records in an arbitrary order, which is why it looks like the output got mangled. 😆

@projectgus @spudly add a constraint and someone always finds a shitty workaround for it.