Motioneyeos: smbus not installed on 20170212?

[ccrisan]

I don't remember ever having added this package to motionEyeOS. You may want to use Raspbian + motionEye if you plan to do this kind of customizations.

[Snille]

Oh, hmm... It did work in the version before this one but maybe the smbus is the wrong way or not even needed? :)

What I really only need is the I2C interface to work, is that possible enabled some how?
My goal is simply to control this little thing: https://www.pi-supply.com/product/bright-pi-bright-white-ir-camera-light-raspberry-pi/

I really want to use your MotionOS because it's a read only system and when the appliance in this case is sitting in a bird nest in a tree outside. The risk of power loss is quite eminent. :)

[bromhexine]

I've got the exact same issue with bright pi. Wish i had read this before i upgraded. Any way to downgrade back remotely?

[ccrisan]

Downgrading is not (yet) possible. If this smbus is so important, I'll include it in the next builds. Honestly I had no idea it was part of the OS. It must have been pulled as a dependency for other package.

[Snille]

Hi! I ended up using modified versions of these scripts and scheduled with CRON instead. Works for me. :)

[bromhexine]

thanks snille i'll check em out and try to copy what you've done. I havent upgraded in a long long time and i actually did make a full backup but stupidly deleted it before making sure the i2c was working. i do have a settings backup though but i dont think that'll restore all the things i had to do to originally get i2c working with the bright pi. ccrisan it will be greatly appreciated if the new update magically fixes it. Been using your work for years now with great satisfaction! (i probably shoulda just bought those infrared 2 led 3 watt with the auto light sensor on ebay for $15 or whatever but i2c seemed like a cool idea since it was customizeable).

[ccrisan]

https://github.com/ccrisan/motioneyeos/commit/8a3638552c5c9901a73ae5550b607565ba6c0414 adds smbus package (available as of 20170329).

[Gun-neR]

Hello. I know this is an older topic... and that I should probably go the Raspbian + motionEye method... but I like the simplicity of using the motionEyeOS and just want to add basic control of my BrightPi... So going on the basis that this smbus has been added (whatever it is/does ;P ) I foraged ahead...

I added the /data/etc/modules as shown above and did get this result with _lsmod_

i2c_dev                 6674  0
i2c_bcm2708             5741  0

which tells me nothing :P except that it seems to "see" the i2c device?

Unfortunately all my limited existing knowledge on how to control the BrightPi seems nonfunctional in the Linux distro this uses.

For example... (also tried with sudo as well... even though already root)

[root@meye-847fb013 ~]# i2cset -y 1 0x70 0x00 0xa5
i2cset: write failed: Remote I/O error

@Snille I looked for your original script to work out how you did it, but the link is dead. I even looked at your 2nd option... see above for one of the commands... but obviously do not understand what modifications you tried to make it work with motionEyeOS

Am I missing something simple?

[Gun-neR]

OK... somehow I think I killed my Bright Pi and that is why it is giving the I/O error... as now it will not work in a known good scenario with another RPi. and _i2cdetect -y 1_ just shows this on any RPi I try it on:

[root@meye-847fb013 ~]# i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Oh well :(

[Snille]

@Gun-neR: Too bad your BrightPi died... However, I lust updated the link to the "new" scripts in the fist post. :)

[Gun-neR]

Well, turns out what appears to be some added resistor/diode/whoknowswhat (the little black thing closest to the GND pin) had somehow fell off along the way and broke the power connection. A solder blob where that mystery SMC was and it is all working again.

So... a quick test later and I can control the LEDs with i2cset commands while SSHed into motionEyeOS... YES! :D Amazing how the programming makes more sense when the hardware works ;)

@Snille Thank you for the new link... I shall proceed to follow your directions and add in the timed LED control