Add Firmware Register for Nexa and Noah

[super-sonic-zero]

Adds sensors for the firmware of Noah and Nexa devices.

It could be used to build a full version string in the future, see #200

Note that Noah firmware has 3 parts and Nexa firmware has 4 parts.

Nexa:

[criticallimit]

For Noah I have made a Sensor with the 3 parts in one sensor:

If it is wnted I can make a Pull Request

[super-sonic-zero]

Added a sensor with the combined firmware version parts

[robertzaage]

Added a sensor with the combined firmware version parts

Thanks for your contribution! I‘m glad we finally found the missing BMC firmware version. Two things:

I would name the new registers to contain the word „version“ and I would propagate the version not only as new combined sensor, but in the HA device metadata as well.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[criticallimit]

Why you prefer single parts published to HA when there is a functional single sensor for the firmware version?
We had that with the serial number parts and as soon you combined them to one single sensor the parts are no longer published. And in my options it´s making sense. Just to avoid having useless entities in HA that you can´t delete or use.
Is there another reason to have these single Parts I don´t see?

[criticallimit]

For Noah Registers:
Is the offset for Part1 is correct in your PR? When I read the log Reg119 it is 00 12 and Reg120 is 11 0b on my side.

... 00 00 00 00 00 00 00 12 11 0b 00 00 00 00 00 00 00 00 ...

On Nexa Reg 119 and 120 are completly used (4 Parts), but on Noah only 3 Parts are used so Part1 needs a Offset of 1 when size: 1 is used
"fw_part_1": {
"growatt": {
"position": {
"register_no": 119,
"offset": 0,
"size": 1

Does it make sense? Or do I miss something?

[super-sonic-zero]

Why you prefer single parts published to HA when there is a functional single sensor for the firmware version? We had that with the serial number parts and as soon you combined them to one single sensor the parts are no longer published. And in my options it´s making sense. Just to avoid having useless entities in HA that you can´t delete or use. Is there another reason to have these single Parts I don´t see?

I don't know about your Noah, but for my Nexa the 4 parts of the serial are published to Home Assistant as well. You can disable entities if you don't want to see them

For Noah Registers: Is the offset for Part1 is correct in your PR? When I read the log Reg119 it is 00 12 and Reg120 is 11 0b on my side.

... 00 00 00 00 00 00 00 12 11 0b 00 00 00 00 00 00 00 00 ...

On Nexa Reg 119 and 120 are completly used (4 Parts), but on Noah only 3 Parts are used so Part1 needs a Offset of 1 when size: 1 is used "fw_part_1": { "growatt": { "position": { "register_no": 119, "offset": 0, "size": 1

Does it make sense? Or do I miss something?

Hard to tell without the full message. Would you mind testing my changes in growatt_noah_registers.json? If you are correct then all parts are off by one.

[robertzaage]

Why you prefer single parts published to HA when there is a functional single sensor for the firmware version? We had that with the serial number parts and as soon you combined them to one single sensor the parts are no longer published. And in my options it´s making sense. Just to avoid having useless entities in HA that you can´t delete or use. Is there another reason to have these single Parts I don´t see?

No, I don’t prefer single parts - I would be happy if we add a combined firmware version of the device + datalogger to the device info section in HA. We currently derive the datalogger version from config messages and update the device metadata then.

[criticallimit]

@super-sonic-zero

You are right. For Parts1 it doesnt matter if offset is set to "0" or "1". It shows correct value in both cases.

[super-sonic-zero]

Firmware version parts won't be published to Home Assistant anymore.

Can we merge this as is? The datalogger version from config messages is not available for Nexa yet, so I am unable to properly test combining these into one version.