Hi Nace,
No, the I2C Grove doesn’t care which I2C port you’re connecting it to, your problem might be caused by bad network communication to the Azure, in which case the program will throw an exception which is not catch-ed. I’ve updated the code to catch these exceptions. Please try our latest App bundle with instructions here: <LINK_TEXT text=“https://github.com/Seeed-Studio/AzureGr … /README.md”>AzureGroveKit/README.md at master · Seeed-Studio/AzureGroveKit · GitHub</LINK_TEXT>