admin/lib/tariff changes with FW D8.3.5289

[pngaudioguy]

I realize that this hasn't been actively developed for a couple years, and I wish there was a way to lock the device at a FW version to prevent what I consider to be feature regressions, but I wanted to share my experience with my Envoy that was recently updated to D8.3.5289.

Previously, based on hints from looking through issues others had on here, I was able to modify the values below in "tariff.json" and use a PUT with my token to adjust my battery SOC (where res = the desired set value between 10 and 100) - it was working perfectly for the last few months - but no longer.

msg.payload.schedule.override = true;
msg.payload.schedule.reserved_soc = res;
msg.payload.tariff.storage_settings.reserved_soc = res;

Have you found an alternative access method, or is this just one more step in Enphase removing local control?

I was using "Self-consumption" mode and simply adjusting the battery value previously. I changed my cloud setting to "Full Backup" and pulling the .json again shows still "self-consumption". I then put my system back to Self-consumption and attempted to adjust with my MQTT GUI, and saw the PUT output match what was expected, but the GET a minute later still showed the previous value. Changing the reserve SOC in the cloud controls the gateway and uses/charges the battery as expected, but no changes are reflected on the JSON and can't seem to control anymore. I even attempted a power cycle to see if it just needed a full reset, but same result.

Extremely disappointed at this loss of local control. I don't like having to rely on cloud connections for local utility type devices.

Edit to add build info from the bottom of my info.xml

	<build_info>
		<build_id>-FRA-799-merge-master-enable-prod:pkg-Apr-17-26-14:30:07</build_id>
		<build_time_gmt>1776436703</build_time_gmt>
		<release_stage>700-GA</release_stage>
		<release_ver>02.00.1508</release_ver>
	</build_info>