I2C problem with remote Raspberry pi

edit

My guess is when you're logged into the Raspberry Pi you are running the code with sudo and this is not being done by Wing's remote agent.  Probably the solution is setting access permissions so the user can access it without sudo.  The selected answer for http://stackoverflow.com/questions/34... and the document it links to may be what you need.

Actually I'm not running as sudo. Earlier i2c implementations did require sudo or equivalent but I'm just running the program using: python test-prog.py as per normal. It's 3am in the UK so I'm off top bed now but, when I return to the problem later today I will just check the permissions. 

The article you referenced is dated 12/2015 and that referred to a 2012 article so it is probably before the later smbus implementation but I will check and report back.

Thanks for a speedy reply BTW.

David

When the current user lacks the necessary permissions to access a file or directory. To resolve this issue, you can check the file or directory permissions, ensuring that the user has appropriate read, write, or execute permissions. Verify ownership, making sure the user is the owner or belongs to a group with sufficient permissions. If accessing system files, run the program or script with administrative privileges. Check if the file is currently in use by another process and close any applications that might have it locked. Ensure that the parent directory allows write access if you are creating or modifying a file within it. Antivirus or security software can also restrict access, so temporarily disable or configure it accordingly.