Smart load grid always on button

[brendonlobo123]

Problem or Use Case

Looking to set the grid always on button from HA

Proposed Solution

Expose the option

Alternatives Considered

No response

Affected Device Model(s)

12000XP

[btli]

Implemented and merged (#496) — but please treat this as needing your confirmation before it counts as fixed.

A Grid Always On switch now appears on inverters. It writes through the EG4 cloud exactly as the portal's Maintenance → Remote Set page does. It ships disabled by default, so you will need to enable it in the entity settings first.

What is verified, and what is not

I confirmed the read side against live hardware: FUNC_ON_GRID_ALWAYS_ON comes back as a named parameter on an 18KPV, a GridBOSS and a FlexBOSS21, and it is present in the register range the integration actually uses to build its parameter cache. So the switch should reflect your inverter's real state.

The write has never been tested on an inverter. It sends the same call the portal sends, but no unit has been observed acting on it — so toggling it is the unknown part. That is exactly what would be useful from you: enable the entity, toggle it, and check whether the portal page agrees afterwards. If it does not take effect, please say so and I will dig further rather than leave it looking supported.

Leaving this issue open until you have had a chance to try it.

Why it is cloud-only

The function lives in holding register 179, but which bit has never been confirmed. Guessing is not a safe failure here: the firmware acknowledges the write either way, so the integration could not detect the mistake and might silently flip an unrelated setting. If anyone can capture a raw register-179 read before and after toggling Grid Always On in the portal, that pins the bit and the local path can be added — until then the cloud is the only route known to hit the right thing.

Practical consequence: the switch is not created on Local-only connections, or on Hybrid connections with a local transport attached, because there its state could not be read at all. Where the state genuinely is unknown it reports unavailable rather than showing a misleading "Off".

Not included

The same portal section has a Smart Load Enable toggle, which reads identically. I deliberately left it out: nobody has asked for it, its write path would be just as unverified, and it repurposes the physical port rather than adjusting behaviour within it. Happy to add it if it is useful to you — worth its own issue so the two can be confirmed independently.

[brendonlobo123]

Hi Bryan, I was able to toggle the switch off and on, and refreshing the portal confirmed that it is in sync. Thank you, Brendon Book with me <https://calendar.app.google/sqymqbycKJdV8y1j6>

…

On Mon, Jul 27, 2026 at 10:24 AM Bryan Li ***@***.***> wrote: *btli* left a comment (joyfulhouse/eg4_web_monitor#484) <#484 (comment)> Implemented and merged (#496 <#496>) — but *please treat this as needing your confirmation before it counts as fixed.* A *Grid Always On* switch now appears on inverters. It writes through the EG4 cloud exactly as the portal's Maintenance → Remote Set page does. It ships *disabled by default*, so you will need to enable it in the entity settings first. What is verified, and what is not I confirmed the *read* side against live hardware: FUNC_ON_GRID_ALWAYS_ON comes back as a named parameter on an 18KPV, a GridBOSS and a FlexBOSS21, and it is present in the register range the integration actually uses to build its parameter cache. So the switch should reflect your inverter's real state. *The write has never been tested on an inverter.* It sends the same call the portal sends, but no unit has been observed acting on it — so toggling it is the unknown part. That is exactly what would be useful from you: enable the entity, toggle it, and check whether the portal page agrees afterwards. If it does not take effect, please say so and I will dig further rather than leave it looking supported. Leaving this issue open until you have had a chance to try it. Why it is cloud-only The function lives in holding register 179, but *which bit* has never been confirmed. Guessing is not a safe failure here: the firmware acknowledges the write either way, so the integration could not detect the mistake and might silently flip an unrelated setting. If anyone can capture a raw register-179 read before and after toggling Grid Always On in the portal, that pins the bit and the local path can be added — until then the cloud is the only route known to hit the right thing. Practical consequence: the switch is not created on Local-only connections, or on Hybrid connections with a local transport attached, because there its state could not be read at all. Where the state genuinely is unknown it reports *unavailable* rather than showing a misleading "Off". Not included The same portal section has a *Smart Load Enable* toggle, which reads identically. I deliberately left it out: nobody has asked for it, its write path would be just as unverified, and it repurposes the physical port rather than adjusting behaviour within it. Happy to add it if it is useful to you — worth its own issue so the two can be confirmed independently. — Reply to this email directly, view it on GitHub <#484?email_source=notifications&email_token=APOBEFJX45QBBKM6IW7S5S35G5QYRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGI2TKMRVGMYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5092552530>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APOBEFI3ICVKF7WEVV26JGD5G5QYRAVCNFSNUABGKJSXA33TNF2G64TZHMYTANJTG44DCNBVGE5US43TOVSTWNBZG42TOMBUGY3DDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/APOBEFN2FJPTVZSCI2IDGKD5G5QYRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGI2TKMRVGMYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/APOBEFOLTEKKTJIFCXZMKWD5G5QYRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGI2TKMRVGMYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>