Is the InkyPHAT compatible with other I2C devices on the bus?


I am trying to add an InkyPHAT display to a Raspberry Pi Zero W with other devices on the I2C bus (specifically, a Sensirion SEN55 and a GPS unit from Adafruit). I notice that the mere presence of the InkyPHAT on the bus doesn’t affect the operation of the other devices, but the moment I load the InkyPHAT driver in Python every other device on the bus is no longer detected, even with i2cdetect from the CLI.

Is this expected behavior? It doesn’t seem necessary that the InkyPHAT should have to completely own the I2C bus over all other devices.

Inky pHAT at Raspberry Pi GPIO Pinout
0x50: Inky ID EEPROM
I’m thinking that is happening because the Inky software is using the bus to ID what Inky is attached? Somebody from Pimoroni will have to confirm that though.
@hel @Matt
Thats usually done on i2c0, not i2c1?
GPIO 0 and GPIO 1 - I2C0 - can be used as an alternate I2C bus, but are typically used by the system to read the HAT EEPROM.
I2C at Raspberry Pi GPIO Pinout

Not sure what the answer is?