Closed GoogleCodeExporter closed 9 years ago
Hello,
I'm also very interested in an i2c binding for openhab.
I've found some probably helpful code here:
http://www.horter.de/i2c/i2c-beispiele/beisp_java_1.html
best regards
Marko
Original comment by marko.ka...@gmx.de
on 25 Dec 2012 at 1:58
[deleted comment]
Hi
i2c will give openhab more power, specially when it comes to power line
communication based home automation, was it open standard or proprietary
so Amen to that !
Meshx86
Original comment by mohs...@gmail.com
on 8 Mar 2013 at 5:50
unassigned to make current state more transparent
Original comment by teichsta
on 21 May 2013 at 9:17
Original comment by kai.openhab
on 22 May 2013 at 8:13
Original comment by teichsta
on 23 May 2013 at 3:49
I2C is just a synchronous serial communication protocol, which it self does not
specify any device support. Device interface is manufacture specific (e.g.
register structure), so it's pretty difficult to implement generic i2c binding.
Well it's easy to implement binding which can be used to read/write bytes from
i2c device, but it's not very user friendly.
Probably most users which need i2c support will run OpenHAB on raspberry pi and
Linux.
Linux kernel have very good i2c support. Kernel support huge amount of
different i2c devices already, so If OpenHAB is running on linux and e.g.
raspberry pi, i2c devices can be access via command line using exec binding:
1) directly via /sys/class/...
2) using i2c-tools
3) using python, etc ...
My 2 cents
Pali
Original comment by pauli.an...@gmail.com
on 27 May 2013 at 6:29
Original comment by teichsta
on 5 Nov 2013 at 10:47
This issue has been migrated to Github. If this issue id is greater than103 its
id has been preserved on Github. You can open your issue by calling the URL
https://github.com/openhab/openhab/issues/<issueid>. Issues with ids less or
equal 103 new ids were created.
Original comment by teichsta
on 17 Nov 2013 at 8:08
see above!
Issue has been migrated to Github and should be discussed there.
Original comment by teichsta
on 21 Nov 2013 at 1:51
Original issue reported on code.google.com by
cbb7...@gmail.com
on 22 Dec 2012 at 4:12