# I2C-scan node reading different address than i2cdetect

**URL:** <https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582>\
**Category:** General\
**Created:** [18 August 2022 03:38 UTC](https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582 "2022-08-18T03:38:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![FeliceM](https://avatars.discourse-cdn.com/v4/letter/f/ec9cab/32.png) [@FeliceM](https://discourse.nodered.org/u/FeliceM)\
**Post date:** [18 August 2022 03:38 UTC](https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582/1 "2022-08-18T03:38:28Z")

</div>

Hi there,  
I am a bit confused. I am using the I2C scan node to detect the available addresses and I also checked with i2cdetect -y 01 directly from terminal.  
I get two different results:

 ![Schermata 2022-08-18 alle 05.34.14](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/2/623f5c67e9ff10be0f52c2bb033b093d61cca126.png)  
 ![Schermata 2022-08-18 alle 05.34.03](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/e/9e8bfb3f239bde70ace12aec9373edce5508e089.png)

How is that possible?  
Am I reading the results in the wrong way?

---

<div class="post-metadata">

**Author:** ![MecatronicaMADE](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@MecatronicaMADE](https://discourse.nodered.org/u/MecatronicaMADE)\
**Post date:** [18 August 2022 04:38 UTC](https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582/2 "2022-08-18T04:38:24Z")

</div>

Hi @FeliceM are you using a Rpi? and are you sure that your I2C connection is correct? SDA - SCL

---

<div class="post-metadata">

**Author:** ![MecatronicaMADE](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@MecatronicaMADE](https://discourse.nodered.org/u/MecatronicaMADE)\
**Post date:** [18 August 2022 04:43 UTC](https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582/3 "2022-08-18T04:43:00Z")

</div>

Sorry my bad, your I2C is okay, the address is the same, but it is in HEX:

**26 = 0x1A**  
**80 = 0x50**  
**81 = 0x51**  
**82 = 0x52**  
**83 = 0x53**  
**84 = 0x54**  
**85 = 0x55**  
**86 = 0x56**  
**87 = 0x57**

click on the msg.payload number to change to hex format.

---

<div class="post-metadata">

**Author:** ![FeliceM](https://avatars.discourse-cdn.com/v4/letter/f/ec9cab/32.png) [@FeliceM](https://discourse.nodered.org/u/FeliceM)\
**Post date:** [18 August 2022 04:59 UTC](https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582/4 "2022-08-18T04:59:34Z")

</div>

Silly me!  
I got it. Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 September 2022 05:00 UTC](https://discourse.nodered.org/t/i2c-scan-node-reading-different-address-than-i2cdetect/66582/5 "2022-09-01T05:00:33Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.