Quick Charge #180

Philip-Hel · 2023-07-31T14:49:42Z

Philip-Hel
Jul 31, 2023

Hi I'm trying to get the same behaviour as the quick charge button in the luxpower app in home assistant.
been trying to see if I activate it in the luxpower app what changes in mqtt.
Didn't see anything. not sure what I am missing.

Has anyone figured it out?

Answered by jacovt

Aug 16, 2023

Maybe I can help a little here as I have SNA5000's. I have implemented this functionality before there was this "quick charge" thing on the luxpower app.

I am guessing both @Philip-Hel and @Sboshoff76 are South Africans and have to deal with our version of rotational power cuts (LoadShedding) at all weird hours of the day and that's why we need this functionality. :)

Right now I have a little flow set up in Node-Red that gets triggered via MQTT from Home Assistant based on the LoadShedding calendar. It does the following to start the "quick charge":

Enables the AC charge, based on SOC levels. Do this by sending a payload of 150 to holding register 120 (lxp/cmd/all/set/hold/120 on MQTT).
S…

View full answer

celsworth · 2023-08-01T08:53:16Z

celsworth
Aug 1, 2023
Maintainer

First thing to check would be turn on debug logging and see what lxp-bridge logs when you press the Quick Charge button.

This will be more revealing than just watching MQTT as it'll tell us what packets are coming from the inverter in response to the commands Luxpower sends. Unfortunately it's a lot more involved to see the actual commands sent but we can usually work it out from the inverter responses we do see.

I've never actually pressed the Quick Charge so not sure of its exact behaviour. Does it just enable AC Charge for a certain time period then turn it back off?

0 replies

Sboshoff76 · 2023-08-13T14:06:01Z

Sboshoff76
Aug 13, 2023

This is what I can see happen in the GUI when I click the quick charge button:

AC Charge field changes from whatever setting you were on to "According to Time".
AC Charge start time 3 changes from whatever it was to the current time.
AC Charge end time 3 changes from whatever it was to the current time + 1 hour.

When the 1 hour elapses or the stop quick charge button is pressed, the fields return to their previous values that were set before the quick charge button was pressed.

2 replies

celsworth Aug 16, 2023
Maintainer

Hm, this "AC Charge" "According to Time" is new to me, this must be something in newer inverters/firmwares. For my (getting very old now) ACS3600 I just have to set start/end times and then flip the AC Charge boolean bit in Register 21.

I wonder what register is changed when you set "According to Time" (and what to? and what other values could it have?)

Sboshoff76 Aug 16, 2023

Yeah this is what is available to me for the SNA5000

And here are the options for AC Charge

jacovt · 2023-08-16T15:07:19Z

jacovt
Aug 16, 2023

Maybe I can help a little here as I have SNA5000's. I have implemented this functionality before there was this "quick charge" thing on the luxpower app.

I am guessing both @Philip-Hel and @Sboshoff76 are South Africans and have to deal with our version of rotational power cuts (LoadShedding) at all weird hours of the day and that's why we need this functionality. :)

Right now I have a little flow set up in Node-Red that gets triggered via MQTT from Home Assistant based on the LoadShedding calendar. It does the following to start the "quick charge":

Enables the AC charge, based on SOC levels. Do this by sending a payload of 150 to holding register 120 (lxp/cmd/all/set/hold/120 on MQTT).
Sets the SOC End Change value to 95%. Do this by sending a payload of 95 to holding register 161 (lxp/cmd/all/set/hold/161 on MQTT)
Sets the SOC Start Charge value to 90%. Do this by sending a payload of 90 to holding register 160 (lxp/cmd/all/set/hold/160 on MQTT)

It does the following to stop the "quick charge":

Disables the AC charge. Do this by sending a payload of 144 to holding register 120 (lxp/cmd/all/set/hold/120 on MQTT).
Sets the SOC End Change value to 20%. Do this by sending a payload of 20 to holding register 161 (lxp/cmd/all/set/hold/161 on MQTT)
Sets the SOC Start Charge value to 15%. Do this by sending a payload of 15 to holding register 160 (lxp/cmd/all/set/hold/160 on MQTT)

On the HA side, I have 2 simple buttons - 1 to start the charge and one to end the charge. These are used for when I manually want to quickly flip the switch to stop consuming from battery and start the AC charge and vice versa. All these buttons do is a very simple MQTT publish which then gets picked up by Node Red to start the relevant flow.

For the automated charge from HA, I use the LoadShedding calendar and trigger a quick charge ~2 hours before the LoadShedding is scheduled to start, only when the sun is no longer shining and the batteries are < 40% charged.

Here is what that automation looks like in Node-RED, but you could actually do this straight from HA:

And the flows for easy import into Node-RED:
quickcharge.json.txt

What I will do tonight is maybe just do a dump of what modbus commands the "Quick Charge" button on the app sends and compare to what I already do and then post back with those details.

Hope this helps.

5 replies

Philip-Hel Aug 16, 2023
Author

You are spot on and this is extremely useful. Thank you, yes this is indeed for rolling blackouts. Just sometimes need a "topup", if I see the batteries are too low and have a risk of not making it. This setup is perfect for my needs.
You've saved me many hours. Thank you Sir!

Sboshoff76 Aug 16, 2023

Hehehe Jaco jou doring!

Loadshedding is not a major concern for me as I'm just about off grid but I would like to flesh out this integration as much as possible and have most of the website features and data available in HA.

celsworth Aug 17, 2023
Maintainer

Legend @jacovt! Thanks for posting this. I've added a few details about this register 120 at https://github.com/celsworth/lxp-bridge/wiki/Holdings#register-120.

For those interested in the numbers 150 and 144 being sent to it, they set bits 1&2 on and off respectively. So when off those bits are 0 = disable, and when both on they are 3 = according to SOC.

The only small thing to be aware of is by sending 150 and 144 specifically you will set other bits of this register regardless of what they were before, in particular GenChargeType will be set to "according to SOC", and DischgCtrlType will also be set to "according to SOC". Most likely this is absolutely fine but if you've changed those bits previously you'll need to adapt the integers you send.

jacovt Aug 18, 2023

Took a bit longer than expected, but here are the details of what the LuxPower servers sends back to your inverter when you hit the "Quick Charge" button:

lxp-bridge  | [2023-08-18T10:04:22.138 DEBUG lxp_bridge::lxp::packet_decoder] 49 bytes in: [161, 26, 5, 0, 43, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 29, 0, 1, 3, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 68, 0, 12, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 69, 180]
lxp-bridge  | [2023-08-18T10:04:22.138 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: ReadHold, inverter: 2263038013, register: 68, values: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] })
lxp-bridge  | [2023-08-18T10:04:22.138 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/68 = 0
lxp-bridge  | [2023-08-18T10:04:22.138 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/69 = 0
lxp-bridge  | [2023-08-18T10:04:22.139 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/70 = 0
lxp-bridge  | [2023-08-18T10:04:22.139 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/71 = 0
lxp-bridge  | [2023-08-18T10:04:22.139 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/72 = 0
lxp-bridge  | [2023-08-18T10:04:22.139 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/73 = 0
lxp-bridge  | [2023-08-18T10:04:22.139 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/68, Pkid = 45, Payload Size = 1
lxp-bridge  | [2023-08-18T10:04:22.139 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/69, Pkid = 46, Payload Size = 1
lxp-bridge  | [2023-08-18T10:04:22.139 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/70, Pkid = 47, Payload Size = 1
lxp-bridge  | [2023-08-18T10:04:22.140 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/71, Pkid = 48, Payload Size = 1
lxp-bridge  | [2023-08-18T10:04:22.140 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/72, Pkid = 49, Payload Size = 1
lxp-bridge  | [2023-08-18T10:04:22.140 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/73, Pkid = 50, Payload Size = 1
lxp-bridge  | [2023-08-18T10:04:23.504 DEBUG lxp_bridge::lxp::packet_decoder] 39 bytes in: [161, 26, 5, 0, 33, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 19, 0, 1, 3, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 120, 0, 2, 144, 0, 155, 107]
lxp-bridge  | [2023-08-18T10:04:23.504 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: ReadHold, inverter: 2263038013, register: 120, values: [144, 0] })
lxp-bridge  | [2023-08-18T10:04:23.504 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/120 = 144
lxp-bridge  | [2023-08-18T10:04:23.504 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/120, Pkid = 51, Payload Size = 3
lxp-bridge  | [2023-08-18T10:04:24.324 DEBUG lxp_bridge::lxp::packet_decoder] 38 bytes in: [161, 26, 5, 0, 32, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 18, 0, 1, 16, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 72, 0, 2, 0, 198, 122]
lxp-bridge  | [2023-08-18T10:04:24.325 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: WriteMulti, inverter: 2263038013, register: 72, values: [2, 0] })
lxp-bridge  | [2023-08-18T10:04:25.117 DEBUG lxp_bridge::lxp::packet_decoder] 38 bytes in: [161, 26, 5, 0, 32, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 18, 0, 1, 6, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 120, 0, 146, 0, 51, 116]
lxp-bridge  | [2023-08-18T10:04:25.117 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: WriteSingle, inverter: 2263038013, register: 120, values: [146, 0] })
lxp-bridge  | [2023-08-18T10:04:25.118 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/120 = 146
lxp-bridge  | [2023-08-18T10:04:25.118 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/120, Pkid = 52, Payload Size = 3

And then when you turn it off again:

lxp-bridge  | [2023-08-18T10:10:47.244 DEBUG lxp_bridge::lxp::packet_decoder] 38 bytes in: [161, 26, 5, 0, 32, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 18, 0, 1, 16, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 72, 0, 2, 0, 198, 122]
lxp-bridge  | [2023-08-18T10:10:47.244 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: WriteMulti, inverter: 2263038013, register: 72, values: [2, 0] })
lxp-bridge  | [2023-08-18T10:10:48.218 DEBUG lxp_bridge::lxp::packet_decoder] 39 bytes in: [161, 26, 5, 0, 33, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 19, 0, 1, 3, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 120, 0, 2, 146, 0, 154, 11]
lxp-bridge  | [2023-08-18T10:10:48.219 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: ReadHold, inverter: 2263038013, register: 120, values: [146, 0] })
lxp-bridge  | [2023-08-18T10:10:48.219 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/120 = 146
lxp-bridge  | [2023-08-18T10:10:48.219 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/120, Pkid = 38, Payload Size = 3
lxp-bridge  | [2023-08-18T10:10:49.047 DEBUG lxp_bridge::lxp::packet_decoder] 38 bytes in: [161, 26, 5, 0, 32, 0, 1, 194, 66, 65, 49, 50, 50, 48, 48, 50, 56, 53, 18, 0, 1, 6, 50, 50, 54, 51, 48, 51, 56, 48, 49, 51, 120, 0, 144, 0, 50, 20]
lxp-bridge  | [2023-08-18T10:10:49.047 DEBUG lxp_bridge::coordinator] RX: TranslatedData(TranslatedData { datalog: BA12200285, device_function: WriteSingle, inverter: 2263038013, register: 120, values: [144, 0] })
lxp-bridge  | [2023-08-18T10:10:49.047 INFO lxp_bridge::mqtt] publishing: lxp/BA12200285/hold/120 = 144
lxp-bridge  | [2023-08-18T10:10:49.047 DEBUG rumqttc::state] Publish. Topic = lxp/BA12200285/hold/120, Pkid = 39, Payload Size = 3

To sum up, when turning on Quick Charge:

It reads holding registers 68-73 to get the values for AC Charge Time 1, 2 and 3.
It reads holding register 120 to get the value for AC Charge.
It issues a WriteMulti for holding register 72+73 (AC Charge Time 3 Start and End). I cannot see based on the debug logs what the actual data is, maybe @celsworth can help me open my eyes here, but looking at the values populated in the app again, it writes the current time as a start value and the end value is set to start value + 1 hour.
It issues a WriteSingle for holding register 120 and sets the value to 146. This translates to "AC Charge according to Time".

When you turn off Quick Charge:

It issues a WriteMulti for holding register 72+73 (AC Charge Time 3 Start and End). Again, cannot see the actual values sent, but in my case they got zeroed out as they were before in the Luxpower app. I have not tested if it restores any previously set values before Quick Charge was started.
It reads holding register 120 to get the value for AC Charge.
It issues a WriteSingle for holding register 120, setting the value to 144. This translates to "AC Charge Disabled".

Unrelated to the Quick Charge interaction, I have done some additional settings for the AC Charge Type to get the values that goes into holding register 120:

AC Charge According to Time - 146
AC Charge According to Battery Voltage - 148
AC Charge According to Battery SOC - 150
AC Charge According to Battery Voltage and Time - 152
AC Charge According to Battery SOC and Time - 154

@celsworth - I am not sure if these are based specifically on the inverter model, but maybe we can add these to the documentation as well.

Hope this helps!
---Jaco

Philip-Hel Aug 20, 2023
Author

Thanks everyone! Sharing my implementation for Quick Q, I have 2 inverters I control separately:

Summary:
Went with keeping ac charge time to 24 hours for slot 1 as I just toggle between Time and Battery_SOC. So Just a single register to change.
I topup on SOC 40% to 50% as I have a unique critical req, may not applicable.
Lastly I have an automation to disable after an hour.

Details on config:

My luxpower config:
Configuration.yaml
mqtt:
switch:
- name: "Quick Charge"
  unique_id: quick_charge
  optimistic: false
  state_topic: "lxp/BA********/hold/120"
  command_topic: "lxp/cmd/BA********/set/hold/120"
  payload_on: "146"
  payload_off: "150"
- name: "Quick Charge"
  unique_id: quick_charge_2
  optimistic: false
  state_topic: "lxp/BA********/hold/120"
  command_topic: "lxp/cmd/BA********/set/hold/120"
  payload_on: "146"
  payload_off: "150"
Automation example to switch off after an hour:
alias: Quick Charge auto off
description: Quick Charge auto off
trigger:

platform: state
entity_id:
- switch.quick_charge
  to: "on"
  for:
  hours: 1
  minutes: 0
  seconds: 0
  condition: []
  action:
service: switch.turn_off
data: {}
target:
entity_id: switch.quick_charge
mode: single

Hope this further helps someone in the future

JINXz · 2023-09-17T23:07:09Z

JINXz
Sep 17, 2023

Really healpful!

0 replies

jonny190 · 2024-03-13T13:09:58Z

jonny190
Mar 13, 2024

Hey Guys, had a read over the above but from my playing around i get the blow options, i've tried manually setting them in MQTT but nothing seems to change. Any pointes on what i'm doing wrong

Quick Charge Start
lxp-bridge | [2024-03-13T12:53:15.450 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/68 = 7703
lxp-bridge | [2024-03-13T12:53:15.450 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/69 = 15127
lxp-bridge | [2024-03-13T12:53:15.450 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/70 = 0
lxp-bridge | [2024-03-13T12:53:15.450 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/71 = 7685
lxp-bridge | [2024-03-13T12:53:15.450 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/72 = 0
lxp-bridge | [2024-03-13T12:53:15.450 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/73 = 0
lxp-bridge | [2024-03-13T12:53:16.258 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/21 = 56021
lxp-bridge | [2024-03-13T12:53:16.258 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/21/bits = {"eps_en":"ON","ovf_load_derate_en":"OFF","drms_en":"ON","lvrt_en":"OFF","anti_island_en":"ON","neutral_detect_en":"OFF","grid_on_power_ss_en":"ON","ac_charge_en":"ON","sw_seamless_en":"OFF","set_to_standby":"ON","forced_discharge_en":"OFF","charge_priority_en":"ON","iso_en":"ON","gfci_en":"OFF","dci_en":"ON","feed_in_grid_en":"ON"}
lxp-bridge | [2024-03-13T12:53:17.313 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/67 = 100
lxp-bridge | [2024-03-13T12:53:18.454 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/72 = 13580
lxp-bridge | [2024-03-13T12:53:19.023 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/inputs/1 = {"status":12,"v_pv_1":429.7,"v_pv_2":13.8,"v_pv_3":0.2,"v_bat":53.3,"soc":55,"soh":100,"internal_fault":11521,"p_pv":950,"p_pv_1":948,"p_pv_2":2,"p_pv_3":0,"p_battery":483,"p_charge":483,"p_discharge":0,"v_ac_r":240.8,"v_ac_s":25.7,"v_ac_t":0.0,"f_ac":49.89,"p_inv":446,"p_rec":0,"pf":1.0,"v_eps_r":240.8,"v_eps_s":5247.3,"v_eps_t":1542.7,"f_eps":49.89,"p_eps":0,"s_eps":0,"p_grid":8361,"p_to_grid":0,"p_to_user":8361,"e_pv_day":3.6,"e_pv_day_1":3.6,"e_pv_day_2":0.0,"e_pv_day_3":0.0,"e_inv_day":2.9,"e_rec_day":3.5,"e_chg_day":5.3,"e_dischg_day":0.9,"e_eps_day":0.0,"e_to_grid_day":0.1,"e_to_user_day":27.8,"v_bus_1":433.9,"v_bus_2":203.7,"time":1710334399,"datalog":"BA30500205"}
lxp-bridge | [2024-03-13T12:53:19.537 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/73 = 13581
lxp-bridge | [2024-03-13T12:53:20.085 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/inputs/2 = {"e_pv_all":85.1,"e_pv_all_1":85.0,"e_pv_all_2":0.1,"e_pv_all_3":0.0,"e_inv_all":209.5,"e_rec_all":146.8,"e_chg_all":158.5,"e_dischg_all":139.5,"e_eps_all":0.0,"e_to_grid_all":12.1,"e_to_user_all":508.6,"fault_code":0,"warning_code":0,"t_inner":63,"t_rad_1":57,"t_rad_2":51,"t_bat":0,"runtime":1300548,"time":1710334400,"datalog":"BA30500205"}
lxp-bridge | [2024-03-13T12:53:20.626 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/inputs/all = {"status":12,"v_pv_1":429.7,"v_pv_2":13.8,"v_pv_3":0.2,"v_bat":53.3,"soc":55,"soh":100,"internal_fault":11521,"p_pv":950,"p_pv_1":948,"p_pv_2":2,"p_pv_3":0,"p_battery":483,"p_charge":483,"p_discharge":0,"v_ac_r":240.8,"v_ac_s":25.7,"v_ac_t":0.0,"f_ac":49.89,"p_inv":446,"p_rec":0,"pf":1.0,"v_eps_r":240.8,"v_eps_s":5247.3,"v_eps_t":1542.7,"f_eps":49.89,"p_eps":0,"s_eps":0,"p_grid":8361,"p_to_grid":0,"p_to_user":8361,"e_pv_day":3.6,"e_pv_day_1":3.6,"e_pv_day_2":0.0,"e_pv_day_3":0.0,"e_inv_day":2.9,"e_rec_day":3.5,"e_chg_day":5.3,"e_dischg_day":0.9,"e_eps_day":0.0,"e_to_grid_day":0.1,"e_to_user_day":27.8,"v_bus_1":433.9,"v_bus_2":203.7,"e_pv_all":85.1,"e_pv_all_1":85.0,"e_pv_all_2":0.1,"e_pv_all_3":0.0,"e_inv_all":209.5,"e_rec_all":146.8,"e_chg_all":158.5,"e_dischg_all":139.5,"e_eps_all":0.0,"e_to_grid_all":12.1,"e_to_user_all":508.6,"fault_code":0,"warning_code":0,"t_inner":63,"t_rad_1":57,"t_rad_2":51,"t_bat":0,"runtime":1300548,"max_chg_curr":100.0,"max_dischg_curr":100.0,"charge_volt_ref":57.0,"dischg_cut_volt":40.0,"bat_status_0":0,"bat_status_1":0,"bat_status_2":0,"bat_status_3":0,"bat_status_4":0,"bat_status_5":192,"bat_status_6":0,"bat_status_7":0,"bat_status_8":0,"bat_status_9":0,"bat_status_inv":3,"bat_count":1,"bat_capacity":50,"bat_current":0.0,"bms_event_1":0,"bms_event_2":0,"max_cell_voltage":0.0,"min_cell_voltage":0.0,"max_cell_temp":0.0,"min_cell_temp":0.0,"bms_fw_update_state":0,"cycle_count":19,"vbat_inv":52.6,"time":1710334399,"datalog":"BA30500205"}
lxp-bridge | [2024-03-13T12:53:20.626 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/inputs/3 = {"max_chg_curr":100.0,"max_dischg_curr":100.0,"charge_volt_ref":57.0,"dischg_cut_volt":40.0,"bat_status_0":0,"bat_status_1":0,"bat_status_2":0,"bat_status_3":0,"bat_status_4":0,"bat_status_5":192,"bat_status_6":0,"bat_status_7":0,"bat_status_8":0,"bat_status_9":0,"bat_status_inv":3,"bat_count":1,"bat_capacity":50,"bat_current":0.0,"bms_event_1":0,"bms_event_2":0,"max_cell_voltage":0.0,"min_cell_voltage":0.0,"max_cell_temp":0.0,"min_cell_temp":0.0,"bms_fw_update_state":0,"cycle_count":19,"vbat_inv":52.6,"time":1710334400,"datalog":"BA30500205"}

Quick Charge Stop
lxp-bridge | [2024-03-13T11:39:36.613 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/72 = 0
lxp-bridge | [2024-03-13T11:39:37.908 INFO lxp_bridge::mqtt] publishing: lxp/BA30500205/hold/73 = 0

2 replies

jacovt Mar 14, 2024

Hello @jonny190 ,

Just looking through your logs, I am not seeing any change to holding register 120, which controls the Charge Option (AC Charge in this case). It seems like the AC charge time gets adjusted though (holding registers 67-73).

Are you sure you are setting the values for register 120?

Also, just to confirm, what model inverter are you using?

Another thing that you can do to double check if things are happening as you expect them to, is to have a look at the LuxPower app for your inverter and see if the values have changed in there (you will have to do a read values to get the updates).

jacovt Mar 14, 2024

@jonny190 ,

Maybe try @Philip-Hel 's approach above initially as it only requires you to change one register (120). Keep in mind that for this approach to work, you will have to set the time frame for AC charge to start at 00:00 and end at 23:59. He does have a screenshot to show what that looks like in the Luxpower app.

Philip-Hel · 2024-03-14T07:07:08Z

Philip-Hel
Mar 14, 2024
Author

Yeah the one register solution as I implemented above still going strong so far

0 replies

jonny190 · 2024-03-14T09:10:47Z

jonny190
Mar 14, 2024

My inverter is the 5Kw variant of this one https://luxpowertek.com/lxp-hybrid-3-6k
That could be it, I've currently got the timers set to only charge over night 1130 to 0530 when its 7.5p per unit

0 replies

EddieSpaghettie · 2024-10-07T18:47:01Z

EddieSpaghettie
Oct 7, 2024

Hi. Sorry to ask in this thread but seems you guys know about what registers do what. I cant find the register that needs to be changed to turn export to grid on/off. I want to use it in order to see what the excess pv is available as I'm building a device that will control my geyser element output so want to use the export number as the same Watt amount to be sent to my geyser for heating.

1 reply

aviateur17 Oct 8, 2024

funcen_feedingriden is Holding Register 21 bit 15 (starting bit is 0)
functionen1_ubfastzero_export is Holding Register 110 bit 1 (starting bit is 0)

Grid Export Disable, Fast Zero Export Enable

funcen_feedingriden = 0 // Disable Export
functionen1_ubfastzero_export = 1 // Enable Fast Zero Export

Fast Zero Export Disable, Grid Export Enable

functionen1_ubfastzero_export = 0 // Disable Fast Zero Export
funcen_feedingriden = 1 // Enable Export

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Quick Charge #180

{{title}}

Replies: 8 comments 10 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Quick Charge #180

Replies: 8 comments · 10 replies

celsworth Aug 1, 2023 Maintainer

celsworth Aug 16, 2023 Maintainer

Philip-Hel Aug 16, 2023 Author

celsworth Aug 17, 2023 Maintainer

Philip-Hel Aug 20, 2023 Author

Philip-Hel Mar 14, 2024 Author

Replies: 8 comments 10 replies

celsworth
Aug 1, 2023
Maintainer

celsworth Aug 16, 2023
Maintainer

Philip-Hel Aug 16, 2023
Author

celsworth Aug 17, 2023
Maintainer

Philip-Hel Aug 20, 2023
Author

Philip-Hel
Mar 14, 2024
Author