You can send text commands on the UART (or telnet) to interact with the charger while it is running. It is also suitable to implement automated tests.
Default baud rate is 115200. Terminate command with \n
or \r
(new line).
The charger confirms successful command with:
OK: <cmd>
wifi on
,wifi off
disable wifi and telemetry. disabled wifi usually increases the control loop rate.wifi-add <ssid>:<password>
restart
: reset the MCUspeed <float>
set tracking speed (default 1.0)fan <float>
set fan speed 0-100led <RRGGBB>
,led <RGB>
set the LED rgb color in hex or short hex (e.g.led 33ff33
orled 3f3
)sweep
: starts a global MPP scan / search+<int>
,-<int>
manual perturb the buck duty cycle (for testing)reset-lag
: resets max lag statisticscan-i2c
: run a i2c bus scanota <url>
: download and flash a new app image from a HTTP(S) URL.
dc <int>
set the buck duty cycle and put the charger in manual PWM mode. No tracking, protection only.+<int>
,-<int>
relative buck duty cycle perturbation step. be careful with large positive jumps, this can cause extreme current transients destroying the switches. also availble in tracking mode to test tracker recovery.ls-disable
,ls-enable
: disable/enable low-side switch (i.e. diode emulation, sync rectification).bf-enable
,bf-disable
: enable/disable the backflow switch. An enabled back-flow switch will allow current flow from the output to the input (bat to solar).mppt
switches back to MPP tracking mode
from Home Assistant:
- install "Terminal & SSH" add-on
- in add-on Configuration add
busybox-extras
to Packages