Strange operation of Modbus sensors with "0" values after updating to 2025.10.1

Configuration
1

After upgrade to 2025.10.1, Modbus sensors display the “unknown” status when reading the “0” register value.
Power measurement sensor (as example):


#======= MODBUS HUB-1 PE11-H =========#
modbus:
  - name: PE11-H
    type: tcp
    host: 192.168.2.38  #power meter
    port: 502
    delay: 0
#--------------------------------------------------------#
...   
#===== Slave 3.   2-d Floor Heaters&Light (HL)========#
#===== 2-nd Floor HL Active Power (W) =============#
       - name: em3_2floor_hl_w
         unique_id: em3_2floor_hl_w
         slave: 3
         address: 12
         scan_interval: 5      
         input_type: input
         data_type: float32
         device_class: power
         unit_of_measurement: W
         nan_value: 0x0000
         precision: 2
#===========================================#

If the power consumption is “0”, the sensor displays the “Unknown” status.
If any load is turned on (read register > 0), the sensor shows the correct value.
All the “non-zero” sensors (> 30) work fine.
Everything worked fine for years before the update.
I did not find any errors in the logs.
Cleared the cache, reload HA, reboot host - nothing helped.
Tell me what to watch, where to dig.
Thanks!

2

I found the reason - it’s because of the nan_value.
My sensor configuration specifies nan_value: 0x0000.
I always thought that nan_value setting gives a value to the sensor when its real value cannot be received correctly or missed.
I was wrong.
The value in nan_value determines when the sensor will become Unknown.
That is, in my case, when the register value is 0, the sensor becomes Unknow by design and in accordance with the configuration!
https://github.com/home-assistant/core/pull/153352
Honestly, I don’t understand at all why this was done such way, and what the reason for such design and where it can be applied…