v0.5.0

⚠️ Breaking: new MQTT output format

ecoflowd --broker now publishes two JSON telegrams instead of one topic per value:

<topic>/state   {"sn":"HC31…","timestamp":"2026-09-22T09:13:16Z","pv":975,"house":-459,"battery":515,"grid":0,"soc":63}
<topic>/energy  {"sn":"HC31…","timestamp":"2026-09-22T09:13:18Z","pv":3301,"house":3206,"batteryIn":1545,"batteryOut":1562,"gridIn":62,"gridOut":175}

• Removed: ecoflow/<SN>/pv, /house, /battery, /grid, /dcdc, /soc, /measured, /energy/… and the retained ecoflow/<SN>/status with its last will. Consumers subscribed to ecoflow/<SN>/+ must switch; the README has evcc (jq:) and Home Assistant (value_template) examples.
• The serial is in the payload, not in the topic. With more than one device, give each instance its own --topic in /etc/ecoflowd/<SN>.env.
• timestamp is the device's measurement time. Check its age instead of an availability topic: timeout in evcc, expire_after in Home Assistant.
• dcdc is no longer published until its meaning is established.

Upgrading: the old retained status stays on the broker. Delete it once v0.5.0 is running, not before, because v0.4.x rewrites it:

mosquitto_pub -h <broker> -r -n -t ecoflow/<SN>/status

What's Changed

• Point the install examples at v0.4.2 by @womat in #45
• Answer two of the three questions a capture could settle by @womat in #46
• Settle the PV string report, and say why 110 is stuck by @womat in #47
• The portal's day total agrees after all - once the day is over by @womat in #48
• Retract a rate claim that was wrong, and read the night by @womat in #49
• Fetch the unit alongside the binary, and say why it stays in /usr/local/bin by @womat in #50
• Write down why the output is one topic per value, and why JSON would be better by @womat in #51
• Require go 1.27 rather than 1.27.1, and update x/net and x/sync by @womat in #53
• Publish two JSON telegrams instead of one topic per value by @womat in #52

Full Changelog: v0.4.2...v0.5.0