not sure why you did not need to connect gpio … that is surely only possible if you used a core image with pre-defined interface connections (some custom created appliance image or whatnot) … i think even the store auto-connections wouldnt blindly work for gpio’s since the slots have per-device naming.
I followed your instructions and using snappy-i2c-tools now works as expected. (FYI I use the raspberry pi Ubuntu core image)
But I thought that if the app requests i2c in the plugs section of it’s snapcraft.yml that it would then automatically connect to it when installed?
I’ve been testing a script that uses other GPIO pins to switch relays on/off and those work fine, and I never had to use snap connect ... for any of those; Which is why I was surprised to find out I have to connect this.
as for mysensor, doesn’t seem to be picked up at all. I suspect it’s faulty so I’ll need to get my hands on a cheap oscilloscope to see if it’s actually working.
Ok so the plugins and interfaces are now functioning correctly, but i2cdetect doesn’t find any sensor on any of the addresses (See the output on my original post). Is there a easy way to test if the sensor is actually working?
I do have a logic analyzer connected in parallel with the sensor data and clock lines going to the PI.
I can see activity in Pulseview (from Sigrok) when I run i2cdetect but I don’t know how to interpret the results, if the sensor received anything, or if it’s actually responding etc.
