Growatt Nexa 2000 - Parsing warnings 'NoneType' object has no attribute 'size' every hour

[super-sonic-zero]

In Home Assistant, I am getting this warning in the Addon log every hour.

With log level INFO:

2026-06-16 21:20:27,151 [WARNING] Parsing GrowattModbusBlock:
2026-06-16 21:20:27,152 [WARNING] parsing GrowattModbusMessage: 'NoneType' object has no attribute 'size'
2026-06-16 22:20:27,141 [WARNING] Parsing GrowattModbusBlock:
2026-06-16 22:20:27,142 [WARNING] parsing GrowattModbusMessage: 'NoneType' object has no attribute 'size'
2026-06-16 23:20:27,195 [WARNING] Parsing GrowattModbusBlock:
2026-06-16 23:20:27,195 [WARNING] parsing GrowattModbusMessage: 'NoneType' object has no attribute 'size'
2026-06-17 00:20:27,188 [WARNING] Parsing GrowattModbusBlock:
2026-06-17 00:20:27,188 [WARNING] parsing GrowattModbusMessage: 'NoneType' object has no attribute 'size'
2026-06-17 01:20:27,180 [WARNING] Parsing GrowattModbusBlock:
2026-06-17 01:20:27,181 [WARNING] parsing GrowattModbusMessage: 'NoneType' object has no attribute 'size'

I have captured a message with log level DEBUG, with XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX being the representation of the serial number
Please let me know if there is something else that should be censored.

2026-06-16 20:20:27,151 [DEBUG] Received message (None): ...
2026-06-16 20:20:27,153 [DEBUG] Received: ... same data as below
2026-06-16 20:20:27,154 [WARNING] Parsing GrowattModbusBlock:
2026-06-16 20:20:27,154 [WARNING] parsing GrowattModbusMessage: 'NoneType' object has no attribute 'size'
2026-06-16 20:20:27,155 [DEBUG] Received modbus message: None
2026-06-16 20:20:27,155 [DEBUG] Unknown msg_type 259:
00010007033f0103XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX0000000000000000000000000000XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX00000000000000000000000000001a0610161410030000007c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000075760000001a0006001000160014001000000000000000000000003150434755323330303134323332303132323331303134323133303131000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007d00f90000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000fa01760064000f000000000000173b00020000000100000000000000c8000000000000000000c8000000000000000000c8000000000000000000c8000000000000000000c8000000000000000000c8000000000000000000c8000000000000000000c8000003200000000000010001000100000000000000000000000000090001000000000000000000000000000000000000006400000000000000010000392e302e302e300000000000000000000000000000000000000000000000006400000064000000640000006400000064000000640000006400000064000000000000000000000000000000000000000000000000000000000000000000007794

[robertzaage]

This message type falls through all parsers and ends in our modbus parser, which can't handle it.

[robertzaage]

@super-sonic-zero Can you test change 30fc0b9 using the dev container?

[super-sonic-zero]

I couldn't figure out where to set the dev version in time, but I saw that you published a new version 2.7.3.

Will report later if those warnings disappear. Thank you.

[super-sonic-zero]

The warnings seem to be gone, however there is a new hourly error in the Home Assistant system protocol:

Logger: homeassistant.components.mqtt.number
Quelle: components/mqtt/number.py:188
Integration: MQTT (Dokumentation, Probleme)
Erstmals aufgetreten: 12:04:07 (2 Vorkommnisse)
Zuletzt protokolliert: 13:04:07

Invalid value for number.growatt_serial_number_charge_limit: 0 (range 70.0 - 100.0)

---

At the same time, several control elements were set to 0 (in Home Assistant, not in the ShinePhone app):

Growatt Nexa 2000 Default Out Power geändert zu 0 13:04:07 - Vor 8 Minuten

Growatt Nexa 2000 Slot 1 Enabled ausgeschaltet 13:04:07 - Vor 8 Minuten

Growatt Nexa 2000 Slot 1 Mode geändert zu 0 13:04:07 - Vor 8 Minuten

Growatt Nexa 2000 Slot 1 End Time geändert zu 0 13:04:07 - Vor 8 Minuten

Growatt Nexa 2000 Grid Power Allowed ausgeschaltet 13:04:07 - Vor 8 Minuten

Growatt Nexa 2000 Discharge Limit geändert zu 0 13:04:07 - Vor 8 Minuten

[criticallimit]

Same here on Noah. Slot1 Mode is disabled periodically

[robertzaage]

I pushed a fix - the message internally took the wrong route.

[criticallimit]

Fix installed, everything back to normal. Thanx!

[super-sonic-zero]

For me with 2.7.4 this repeats every hour

Growatt Nexa 2000 Serial Part 2 geändert zu 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Battery Count geändert zu 1 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Battery Charging Status geändert zu Discharging 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Battery Cycle Count geändert zu 10 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 1 geändert zu 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Register No 71 geändert zu 0.0 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 3 geändert zu 18:04:10 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 4 geändert zu 18:04:10 - Vor 33 Minuten

Growatt Nexa 2000 Work Mode geändert zu Load First 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 2 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Battery Count geändert zu 31744 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Battery Charging Status wurde unbekannt 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Battery Cycle Count geändert zu 0 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 1 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Register No 71 geändert zu 21810.0 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 3 18:04:08 - Vor 33 Minuten
Growatt Nexa 2000 Serial Part 4 18:04:08 - Vor 33 Minuten

Also there seem to be hourly drops to 0 for entities like this:

[robertzaage]

I just reverted the bug fix for this issue.