Build and printed a little case or holder or what ever you would like to call it. this is a simple one and I plan on changing it a bit but you can see and download at http://www.thingiverse.com/thing:1176699
have fun.
Build and printed a little case or holder or what ever you would like to call it. this is a simple one and I plan on changing it a bit but you can see and download at http://www.thingiverse.com/thing:1176699
have fun.
So I have pulled my omega 1 off the wall and wanted to give it a bit of a refresh. It has been about a year of just sitting around doing nothing and when I factory reset and update the firmware I am not getting any new features that I know had come out.
I have a few questions about this
I was looking at using my omega as an IoT hub and also wanted to install a free cert with lets encrypt, I have domains to use and map to this device and a static IP to my home but I was looking for how to install the cert on the device as I cannot find anything on the omega or openWRT installs. A link to the right direction is all I need.
Thanks.
Re: Driver for 1-Wire sensor bus
Working with DHT22 one wire and I have done https://wiki.onion.io/Tutorials/Reading-1Wire-Sensor-Data
and I have gone thru everything on this community pages here. It seems as if my w1_slave is missing?
when I run this command
cat /sys/devices/w1_bus_master1/00-180000000000/w1_slave
I get this.
cat: can't open '/sys/devices/w1_bus_master1/00-180000000000/w1_slave': No such file or directory
@Kit-Bishop That is helpful. so testing with a pin that I am not using it reads the value, my plan is I have a few relays that I am controlling and I would like to know if one of the pins is set high to trigger the relay? I have the pin connected to an NPN transistor and that might be the issue?
EDIT: adding a resister fixed the reading. thanks for clearing that up.
I am not able to get the current status of a gpio pin, I am typing fast-gpio read 0 and it will return 0 even if I just set the pin high with fast-gpio set 0 1.
Not sure where to look to resolve this issue
Thanks
This is exactly what I needed. I am using a generic OLED screen and it works like a charm!
Thanks for the update. waiting sucks but I know you guys are working hard on getting everything out.
Has anyone documented the client side JavaScript api used?