Posts made by crispyoz

@haythem Thanks for your contribution! Your Youtube work is also very good stuff.

@jossvall I wonder if removing the mmc kernel module would solve this issue without the need to modify your hardware design this late in the game.

@jossvall opkg install pciutils

@Zemlak How did you install python 3.6

@Russell-Pirie "...will they all fit??...." You'd need to be specific as to what they are and how they are configured in order to answer that.

I'm not sure you need to rewrite a bluetooth driver, most users would utilise "Bluez" package for bluetooth, perhaps take a look at that package and see if it meets your requirements, here's a link to the package:

https://openwrt.org/docs/guide-user/hardware/bluetooth/usb.bluetooth

I flash my devices using a bash script (well ash), it just connects to the device(s) using ipv6, uploads the firmware and then ssh's into the device and execute the firmware upgrade. You could tweak my script a bit to make it handle multiple devices at once. I did about 40 of them today using my exiting script, one by one while I was eating lunch and watching the news.

My script is here:

https://community.onion.io/topic/4483/script-to-deploy-firmware-to-device-using-ethernet-ipv6

The other option is to boot into u-boot and flash from USB.

@Chris-Morgan Since OpenWrt hasn't specified any release date for 21.x, I'm not sure this is a reasonable request of Onion as their release would obviously follow that of OpenWrt.

I can confirm that 21.02 RC3 does run on O2S+ but you need to manually configure the WiFi, same as 19.07. I've been running 21.x for 2 or 3 months on a POC custom board based on O2S+ and thus far no real issues. So far the only nagging concern is the WiFi connections seem to be a little slower than my 18.06 devices using Warp Core. Haven't had time to investigate in detail thus far so I may be wrong.

@Russell-Pirie Omega can run NodeJS, and there is an OLED expansion available so it's not difficult to build a POC. Omega doesn't have bluetooth however take a look at this project that explains how to use BLE on Omega devices:

https://docs.onion.io/omega2-project-book-vol1/bluetooth-audio-speaker.html

You probably don't need to boot from SD Card, my own Omega2S+ based devices use SD Card for data storage and SQLite3 database.

I think the main factor you will need to consider is if the Omega2S+ has sufficient computing power to meet your needs.

Omega devices run OpenWrt which is basically a cut down verison of Linux so porting is not typically a huge challenge. Configuration of items such as WiFi can be achieved using "UCI" and "UBUS" interfaces that you can intereact with using JSON, my own device configuration interface is based on PHP and utilises the CURL API to interact with UBUS and configure the WiFi, TimeZone etc. for user setup.

@Williamson Please tell me the mathematical answer to 28 div 14.

@Ioannis this thread may be of use to you:

https://community.onion.io/topic/2982/omega2-as-a-lorawan-node?_=1625750014313

The data sheet doesn't tell us a whole lot, have you contacted their support email address and asked them to provide further details?

@elPepino have you looked at the code for Omega Dash? The Dash uses a frame buffer to drive the screen and is based upon Omega2S+ and uses LVGL. I also wonder if you could use the Dash then use a USB LTE device

@Nagarjuna-Reddy https://openwrt.org/docs/guide-user/services/snmp/mini_snmpd

@optech Post your init script please, it will log whatever the script results are. Check the log again using:

logread | grep -i chirpstack

@optech add PROCD_DEBUG=1 to the top of your init script to log more info about the process

@optech Type logread and see what the service is reporting.

@optech @tjoseph1 is correct, this ipk is mispackaged. An IPK is just a set of tgz inside a tgz, so you can extract the files and run the binary and the error becomes self-evident. Best to contact the author or recompile the code.

@Ioannis post a datasheet so members can take a look and maybe give you some direction. I think the last Bosch device I used was a spark plug in my 1967 Morris Mini, but I am sure the RF96 is not dissimilar. At the end of the day it is just code, so once we can see a datasheet a design or solution usually becomes evident.

As a wise man once said, software development is all about 1's and 0's, the challenge is to get them in the correct order.

@Ioannis OpenWrt has a Lora gateway package https://github.com/xueliu/lora-feed

@Johann-Cunningham All the original documentation can be found here:

https://onioniot.github.io/wiki/

Since the device is quite old not many still use it so I would troubleshoot the device as I would any *nix device. If you follow the Getting Started Guide on how to connect to the console, then take a look at your network setup (ifconfig), do you have a valid IP, netmask? Can you ping your router? If yes to all of these, then can you ping 8.8.8.8, if yes then your DNS may not be configured, in which case you should check your /etc/resolv.conf for a valid DNS (nameserver) entry.

@Trystan This is a question best asked on a HORNET specific forum.

@TypeSeven fstab looks good to me. My suspicion is that if you look in your log you may find there was a file system problem that has now been resolved. When you restart it examines the file system and may correct it. If you examine o2-pro-init script it is setting up the file systems so it would seem that one of the commands was failing.