From d98263cd9979ff444475aed1030cef79b3c3d224 Mon Sep 17 00:00:00 2001
From: Claudio Ruggeri - CR-Tech <41435902+crug80@users.noreply.github.com>
Date: Mon, 26 May 2025 21:32:46 +0200
Subject: [PATCH] ModBus Sensor marked unknown if getting NaN (#38235)

---
 source/_integrations/modbus.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_integrations/modbus.markdown b/source/_integrations/modbus.markdown
index c6ea3c3b051..f1895983b8b 100644
--- a/source/_integrations/modbus.markdown
+++ b/source/_integrations/modbus.markdown
@@ -1434,7 +1434,7 @@ sensors:
       required: false
       type: float
     nan_value:
-      description: If a Modbus sensor has a defined NaN value, this value can be set as a hex string starting with `0x` containing one or more bytes (for example, `0xFFFF` or `0x80000000`) or provided as an integer directly. If triggered, the sensor becomes `unavailable`. Please note that the hex to int conversion for `nan_value` does currently not obey home-assistants Modbus encoding using the `data_type`, `structure`, or `swap` arguments.
+      description: If a Modbus sensor has a defined NaN value, this value can be set as a hex string starting with `0x` containing one or more bytes (for example, `0xFFFF` or `0x80000000`) or provided as an integer directly. If triggered, the sensor becomes `unknown`. Please note that the hex to int conversion for `nan_value` does currently not obey home-assistants Modbus encoding using the `data_type`, `structure`, or `swap` arguments.
       required: false
       type: string
     zero_suppress: