Actually, this is related to something I'm trying to work out.
What I want to do is run the Omega in a remote location. I can run the Omega off of a remote battery pack, but I want to be able to charge the pack either off of a solar panel or some other energy harvesting device.
Any ideas on how I can solve the power bit?
Now there's an idea. Take the Bluetooth dongle to bits and wire it off the expansion board. Frees up the USB port for a memory stick. Nice.
@Victor-Quintanilha - working on something similar myself. Have a Bluetooth dongle connected to the expansion board and can access Bluetooth after installing the bluez package.
The beacon is a RealTag which I can see and interrogate manually from the command line using hcitool and gattool.
What I want to be able to do is run a python BLE scanner but am stuck because there is not enough memory on the omega to add the Bluetooth Python module (PyBluez).
Which page? Am running latest firmware but am unable to see my Bluetooth dongle (a Trend dongle that works on a Pi).
Actually, this is related to something I'm trying to work out.
What I want to do is run the Omega in a remote location. I can run the Omega off of a remote battery pack, but I want to be able to charge the pack either off of a solar panel or some other energy harvesting device.
Any ideas on how I can solve the power bit?
Better idea - get one of those emergency battery packs you can get for charging a mobile phone. Have the car charge the battery pack and run the Omega off the pack. You've still got a battery pack that way if you go off anywhere.
Whilst not wanting to sound detrimental to Onion, have got an Omega working with Xively, and it works well.
Think I've just encountered a variant of this. My current onion has an external USB drive that I am using as extroot with /overlay, as per the tutorials I.e. pivot-overlay. All was fine.
I've just done a firmware upgrade and "lost" my external drive. In fact I was able to initially get it back by manually mounting the USB drive and all my old data was present. What I had to do to fix it was re-install the tools needs to create the external drive then just recreate the fstab using the block detect and edit. On reboot all the data is back.
Except that the onion is now saying that it is running the previous version of the firmware...
So not sure what's going on. As I understood it, using pivot-overlay should have updated the firmware but everything else shouldn't have been touched. That clearly didn't happen. Should one unmount any external drive before doing a firmware upgrade?
temp_f = (( temp_c * 9) / 5) + 32
return temp_f
@Kit-Bishop In the mosquitto.conf file, there is an option for a pid file. Set that up then send a SIGHUP to the existing broker. It should re-read the conf file. You can now kill the broker whenever you want.
As far as using mosquitto goes, I wouldn't run the broker on the Omega. I've always regarded the Omega as an edge device rather than a micro server (like a pi).
Now there's an idea. Take the Bluetooth dongle to bits and wire it off the expansion board. Frees up the USB port for a memory stick. Nice.
@Matt-Ogborne I've got a DS18B20 connected to a GPIO that I sample periodically.
@Victor-Quintanilha - working on something similar myself. Have a Bluetooth dongle connected to the expansion board and can access Bluetooth after installing the bluez package.
The beacon is a RealTag which I can see and interrogate manually from the command line using hcitool and gattool.
What I want to be able to do is run a python BLE scanner but am stuck because there is not enough memory on the omega to add the Bluetooth Python module (PyBluez).
Current running a project using mosquito. The actual broker is running on a pi. The omega has the mosquito client package installed. Got a cron job that reads a temperature sensor on a GPIO then publishes to a topic. Omega talks to the pi over wifi.
Works fine.