Huskylens no I2C data on multiple devices?
prok 2026-02-18 11:05:38 369 Views7 Replies Hello, I have a huskylens 2 and i've been struggling. I believe I may have a faulty I2C bus on the huskylens itself as 3 different pi devices all return nothing but FFFF for any data which indicates no real response at all. It's there on I2C bus 1 on 0x50 but no variation of any python script or basic i2c test script is able to connect at all. Any suggestions? Is there perhaps a known working project out there to test with?
Is there a solution to this? I'm facing the same problem: firmware 1.2.2, I2C enabled, HuskyLens connected to Raspberry Pi 4. The HuskyLens show up using i2cdetect on bus #1, address 0x50, yet all example programs return 0xff. Same result using i2cdump:
$ i2cdump -y 1 0x50
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
…
Solaria Hi, getting all 0xff with i2cdump is completely normal for HuskyLens!
It uses a custom private I2C protocol and does not support standard I2C register reading, so generic tools like i2cdump/i2cget will always return 0xff — this is NOT a hardware failure.
Could you let me know what error message appears when you try to run the example code?
OK… I was using: https://github.com/HuskyLens/HUSKYLENSPython.git. That's for V1 HuskyLens. It's not going to work with V2. (I wonder if that's the answer to the other complaints about 0xff?) The correct library is: https://github.com/DFRobot/DFRobot_HuskylensV2.git.
Unfortunately, that library doesn't work either:
The selected development board is RPI
The development board found is None
The development board does not match !!!
I spent some time debugging, and found that when you specify a board type “RPI”, it checks to see if the hostname is “raspberrypi”. If it isn't, you get that error message. Hostname, as in: “$ sudo hostname raspberrypi”. I guess that works if it's the only RPI on the network and you just accepted defaults, but otherwise?
Thanks for your valuable findings! HUSKYLENS 2 must use its dedicated library and is incompatible with the V1 library.
And we greatly appreciate your feedback on the custom hostname issue. We have verified that the problem can be solved by using the smbus2 native I2C library instead of the pinpong library, and modifying the program to adapt to the HUSKYLESN 2 communication protocol. We will release the tested code to GitHub for your reference later.
FFFF usually means the HuskyLens 2 is detected but not actually communicating—often due to wrong mode or wiring.
Make sure it’s set to I2C mode, wired correctly (SDA/SCL, GND, 3.3V), and try adding pull-up resistors.
If multiple Pis still fail, test with DFRobot’s example code—otherwise the unit may be faulty.
parker.king Hello! Regarding your issue with the HUSKYLENS 2 I2C bus communication failure:
First, please ensure your HUSKYLENS 2 has been updated to firmware version 1.2.2. This version fixes multiple communication instability issues, and updating the firmware is a mandatory prerequisite for resolving the problem.
Firmware update tutorial: https://wiki.dfrobot.com/sen0638/docs/22673
Next, you can directly test the sample programs on our GitHub repository — these programs have undergone thorough testing and are confirmed to work properly.
https://github.com/DFRobot/DFRobot_HuskylensV2/tree/master/python/pinpong/examples
Yx 
