Luxpower Invertor Control problem - Warn: Inverter 0 write to scheduled_charge_enable failed

[bounderboy]

I have had Predbat running for months and it has been superb.. Last few days I am getting this error..

Getting this over and over in PredBat log.

52101 2026-04-05 22:42:22.778342: Completed run status Exporting with Errors reported (check log)

It works for most of the day but then this happens.. Rebooting doesn't seem to be make a difference..

From logs I am seeing this..

Logger: custom_components.lxp_modbus.classes.modbus_client
Source: custom_components/lxp_modbus/classes/modbus_client.py:322
integration: LuxPower Inverter (Modbus) (documentation, issues)
First occurred: 22:19:56 (60 occurrences)
Last logged: 22:47:54

Failed to write register 21 after 7 attempts.

I wonder if it is a predbat issue or actually a Luxpower integration issue?

Thanks for any help on how to troubleshoot - I am a bit of a newbie.

[matthewbhudson]

Exactly the same issue here, any fix?

[bounderboy]

I reverted to the previous version - and all fine

[matthewbhudson]

Previous version of what sorry, home assistant or predbat? Thanks!

[bounderboy]

Apologies - I reverted to previous version of Luxpower Modbus integration

[DJBenson]

@bounderboy is there any chance you can share your apps.yaml - I have set up the lxp-modbus integration but used the guide from the Predbat repo as a template and given they are totally different integrations I'm not convinced I've set it up correctly. It's still running in read only mode right now but I want to let the leash off but a bit worried it might not work as expected.

Here's mine for reference: https://pastebin.com/00anu8rP

[bounderboy]

Apologies about delay... here is my YAML... but it is best to set it up yourself from scratch..

…

On Mon, 25 May 2026 at 20:13, DJBenson ***@***.***> wrote: @bounderboy <https://github.com/bounderboy> is there any chance you can share your apps.yaml - I have set up the lxp-modbus integration but used the guide from the Predbat repo as a template and given they are totally different integrations I'm not convinced I've set it up correctly. It's still running in read only mode right now but I want to let the leash off but a bit worried it might not work as expected. Here's mine for reference: https://pastebin.com/00anu8rP — Reply to this email directly, view it on GitHub <#3745?email_source=notifications&email_token=BI2BJ5EGUHFBPK5FWGC3QBL44SLNZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQGUZTGMZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17053334>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BI2BJ5GFUM5IT7PIKIJOJ4T44SLNZAVCNFSM6AAAAACXNQJMAKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMBVGMZTGNA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.*** com>