KH10 error reading registers after firmware update

[ApronCricket]

Hi,

I've only had my system for a month and very impressed so far.
I have just had my KH10 firmware updated by Fox Cloud (awesome service! Sorted within a few hours after waiting for a month for my installer to do it...).
Went from:
Manager:1.19>1.35
Master:1.27>1.39
Slave:1.01-

Now I'm not getting any reading in the modbus integration in HomeAssistant:
Error reading registers. Type: RegisterType.HOLDING; start: 31000; count: 55; slave: 247 from tcp://192.168.1.58:502: Exception Response(131, 3, IllegalAddress)

I did see an issue raised in GitHub, but it wasn't clear to me if this is something that has been resolved, or if I need to do something different to make it work again?
Modbus is definitely working on the inverter as I have a separate RPi that monitors and acts on Inverter/Battery temperatures with node-red (didn't want to rely on HA for this as I've had pretty poor stability recently).

I was just starting to get used to going to bed at night after looking at the HomeAssistant 'Energy Dashboard' with a smile, so it'd be a shame to give up on it.
I'm far from an expert in HomeAssistant, but if anyone has a link to a guide or any further advice, it would be really appreciated!

Thanks

[Dave Foster]

The latest KH firmware does indeed break the modbus, it is being worked - but I think there is a version on a github test branch that you can install.

William has been doing a lot of the testing as he has KH's so best to post this message over on the github thread and hopefully you'll get some guidance about how to get it working again (or an ETA on a release) https://github.com/nathanmarlor/foxess_ ... issues/678

[ApronCricket]

Thanks