Thanks! That's what I was looking for, so I needed to replace ow.init('u')
with ow.init('-s serverIP:4304'), so that it accesses owserver instead of
the hardware directly. I've seen from looking around that some guys have set
their servers up to have a custom name instead of the IP address, how do I
do that/set a name for my server? 

And on the side, I can't open the file 'list' (at /settings/alias/list)
using sftp, but when I try ssh'ing into it I can open the file in nano (but
it's empty) and when I try to write to it I get 'Error: Operation not
supported". I can change the alias from the owhttpd server page, but not
from python... for instance if I go  <sensor object>. alias = 'EEPROM_1' in
python it changes the alias name in python, but not on the server, but
conversely if I change the name on the http server it changes in python.

Also, how do you write a value to EEPROM memory at a particular offset? I
can write using <sensor object>.memory = 0x45, but what happens if I want to
write another value at an address 4 bytes higher? Like the OW_lwrite
function in the C API.



--
View this message in context: 
http://owfs-developers.1086194.n5.nabble.com/Diagnosing-disappearing-devices-adapters-tp10045p10084.html
Sent from the OWFS Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to