v3.2.13

Fixed

• Schedule writes now work on pre-6.11 Pulsar Plus firmware (e.g. 6.7.41, #50). That firmware predates the s_sch method and rejected every schedule write with "No dispatch method found", even though the official app writes schedules fine. The gateway now falls back to the legacy packed w_sch, with the format decoded on-device (thanks to @AJKoster): sid(2) + startHHMM + stopHHMM + days(3), days a zero-padded Sunday-first bitmask (Sun=1…Sat=64), start/stop HHMM UTC. Also: times wait for the charger timezone before converting; the enabled flag is inferred from the day mask when the firmware omits it (schedules no longer all show "Off"); and new schedules allocate from slot 1 (slot 0 is unusable on this firmware). Add/edit/delete work end-to-end.

Added

• Command source logging (#26). Every state-changing /api/command is logged as [CMD] <action> (met=… par=…) via HTTP <client-ip>, mirroring the MQTT path. Reads are skipped so status polls don't flood the log. Makes a stray external write (e.g. an HA automation publishing a stop) traceable to its source.

Also includes the v3.2.12 fix (authenticated writes on PIN-protected chargers) for anyone updating from an older build.