pfeerick

Thanks ; it is working
Regards

I also started to get the cheap nrf24l01 boards to work. when I followed this tutorial, I always get the error that something with the gpio was wrong.
mysgw: Starting gateway... mysgw: Protocol version - 2.2.0-beta mysgw: MCO:BGN:INIT GW,CP=RNNG----,VER=2.2.0-beta mysgw: TSF:LRT:OK mysgw: TSM:INIT mysgw: TSF:WUR:MS=0 mysgw: Could not open /sys/class/gpio/gpio24/direction
Using this configuration settings showed that the nrf24l01 should work on orange pi zero side:
root@orangepizero:/home/opi/MySensors# ./configure --spi-spidev-device=/dev/spidev1.0 --my-transport=nrf24 --my-rf24-ce-pin=2 --my-rf24-cs-pin=13 --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 followed by make should give you something like this:
The evening would show if I also get it to run on the sensor node side (don't have time at the moment).

For those of you who are interested in using a OPI zero as a small IoT-Server. I have some hints to get it working. It's more or less a lmgtfy How To plus some arduino code to test if it works.
Hardware:
OrangePi 0 with Armbian 5.25 connected over lan to my router DHT11 Module on a Wemos D1 mini (a small cheap wlan MCU for ~3$ which can be programmed via the Arduino IDE) Installation:
First of all we install node-red on the OPI. Instead of rewrite how to do that again I just give you the link who to do that: Node-Red on armbian
Second we install Mosquitto as a mqtt broker. If I have it right in mind I followed this instructable (I'm not shure, it's more than 2 weeks ago and I didn't save the link then): Mosquitto
To represent the data of our DHT sensor-node graphically we install the node red dashboard module in: /usr/lib/node_modules/
with npm i node-red-dashboard
If everything goes right you should have access to node-red via browser on port 1880:
192.168.1.xx:1880
and to the UI of dashboard:
192.168.1.xx:1880/ui/
Setting up everything:
Now we're setting up the Wemos D1 mini. DHT11 wiring (DHT-->Wemos):
VCC -->3.3V 
Signal --> D4
GND -->GND
Some of the Wemos pins are capable for 5V (A0 definitly not!) but the DHT readings gets noisier when the device is powered through 5V (don't ask me why, I'm not en electronic engineer...)
For the testprogramm we need two libraries which can be installed via the arduino IDE lib manager (+ ESP8266WiFi.h which comes when adding the generic ESP8266 board via Boardmanager):
PubSubClient.h (PubSubClient by Nick O'Leary) DHT.h (DHT sensor library by Adafruit) And here comes the simplyfied code publishing to the mqtt broker:
The code is more or less a combination of the examples which comes with the PubSubClient & DHT libraries + throw away all the stuff that we don't need (I had also a version of code where the Wemos D1 mini subscribe to the mqtt broker and gets a timestamp injected from node-red which was then added to the published sensor data).
Humidity data is stored in the "hum" topic, temperature in "temp". Keep in mind that if you plan use more than one senor-node, you should name the topics properly (see: MQTT topics best practices for more information about proper topic nameing)
We can now generate our test-flow on the node-red webpage (See printscreen). Subscribe to the mqtt topics and publish it on the chart and gauge (more information about Dashboard can be found on: Node-Red & Dashboard). 
Powering the Wemos and deploy the created flow shoud show us the graphs on 192.168.1.xx:1880/ui/ (see picture)
To call me an IoT expert is like someone calling tkaiser a fan of micro USB powered SBCs. According to the MIT licence this HowTo  is provided "as is", without warranty etc.

You'll find that this community is still relatively small, imo. Some posts can go longer than 3 days without a response. Please keep duplicate questions to a minimum.

That being said I've only tinkered with RetroOrangePi a couple times so I'm not gunna be the one to help you. The very (and I mean very) little knowledge I have tells me editing boot.cmd would be easiest. Don't quote me.
I do remember having resolution issues on a 720p TV (Opi PC+) though and this thread helped me customize the settings for a fix. Good luck.
 

I would suggest that you look at getting a different power supply, as mobile phone chargers are notorious for being unreliable for SBCs. They tend to either not provide their full current until the phone has *handshaked/negotiated* with the charger, are noisy, or drop their voltage they are loaded to below usable levels (as phone charging needs aren't that demanding). I would suggest you look at getting something like the white power supply (with interchangeable international plugs) for the raspberry pi. 
 
Also, please refrain from making multiple posts... someone *will* reply eventually

Nope, I was aware that 'sometimes in the future' there will be a new Armbian major release exchanging Firefox with Chromium. To my surprise it 'happened' few days ago, now we're at 5.30 and ship with a new default browser on new desktop images and a default config that is slightly more insecure than 'needed'.
 
I was asking for opinions since our current 'style' of development (anyone with commit rights to Armbian repo does whatever he wants) is not that great IMO. I was waiting for something like 'yes, let's do it this or that way' to start working on it (changing kernel configs for the affected arm64 platforms, then testing). But then 5.30 happened without any announcement so there was not even an opportunity to check open issues that need to be fixed prior to release.

Absolutely! I would call this a show-stopper that can happen in early development situation and invalidates all 'in theory' considerations before. But IMO this shouldn't change a bit how we deal with board additions in the future.
 
Please remember situation with OPi Zero: we (some from the inner circle) were excited, added the board, improved settings like crazy. Later we discovered unfortunate Wi-Fi power management settings, then Wi-Fi here being somewhat crappy anyway. If there would have been a rather clean 'board bring up' thread such findings would have been documented (adjusting post #1 in the respective thread), board support rating would have been adjusted and post #1 of the thread could act as something like a landing page for the specific device (moderators pushing newbies to this 'page' for example).

Hi devs,
you are complaining about support nightmare. Microsoft had it much worse, with all possible shitty hardware being introduced without drivers and users expecting it to be supported. Their anwer: "Certified for Windows Vista" with a nice icon to be printed on the sales page. Conditions for the hardware vendor to include the icon was defined by Microsoft.
 
No hardware vendor will read the complaints in your forum. Armbian on the other side has quite the reputation. Do the same, define conditions for boards to be "Certified for Armbian" and push the vendors your way.
 
best,
gnasch

Yes, it is a reflex that a hobbyist has, "to collect all the things".  Especially when one looks like it should be shinier than the others.  BSP's, true performance, driver catastrophes, kernel defilement doesn't show up in the advertisements for these devices.  It is not helped that the "flagship" SBC in most people's minds out there is the Pi 3, a micro-usb powered usb-hub throttled VPU-constrained machine with very poor resources.  Compared to that, anything with high clock numbers or extra "RAM Chips" looks like an amazing deal, people tend to take the community support over there for granted.
 
I do like the Wiki idea, however in a less ambitious sense:  We should list, with no "rose-colored glasses", exactly what the pros and cons are of each board supported, discrepancies between hardware specification and advertised capability, and recommended use cases for each board.  For those use cases, I would personally require a definition of minimum requirements and recommended requirements per use case, and those would live on their own pages.
 
 

Watch out or the next thing we will have is.....
 
"End-users talking to developers, manufacturers talking to consumers, dogs and cats living together, Mass Hysteria, human sacrifice"....
....Jonathan Peterson, Technical Consultant, IBM eBusiness Services
 

If it's an obvious spam - just use The Banhammer, full swing, straight to the head (aka "Flag as spammer" function). Sometimes spam is not obvious, but if content in question contains suspicious external links or just doesn't make any sense, you can just skip it and leave for somebody else to make a decision.
 
I don't think we have any rules set up regarding signature and topic bumping.

Is it the one we all know ?

But leaving a link messes with the unread status ("star") for subforums, so I prefer to move without leaving a link. Users can easily find moved stuff via their profile pages or "Find Content" function.

Yes, I figured out when I came back to the original thread ...

No worries there... I only edit when it's some thing silly like those quote-within-quote-within-quote posts (which don't seem to happen here), or code formatting hasn't been used. Basically readability stuff, and I make it known that is why the edit was done.  And point taken, all hail the mighty Igor! 
 
@Igor When it's obvious human spam, do we temporal ban or just kick? Case in point: jessica951 Just want to ensure I toe the company line!

Granted! Thank you.
 
Some more general thoughts:

We have a very strong spam protection, so you won't have much job dealing with robots, but human creations which sometimes are spam. Since our moderator team got stronger now, we can keep forum in better condition - keeping posts on topics, which was somehow neglected.
 
Our job is also to limit down repeated questions the best way possible with as little impact as possible - with tools mentioned above and procedures which should be summed above. You have right for post editing - use it to update "Moderator duties", when we come up with something to add. I'll do so, but sometimes I won't be able to react promptly. Don't edit other people posts unless it's really necessary.
 
And remember we need to stay humble. We are all just people with ability to make certain moves, which shall be in common interest. Authority will be needed in case of troubles.
 
Prohibiting (ban) and deleting content should be last option - if warnings does not produce any effect - our forum is in general very good in this manner - we issued one temporal ban and currently we don't have banned users. 

I'll bite. I did say I was willing to help out any way I can. If it means spam control, so be it!  And thanks for the link to the article... I'll have to ram that down the throat of another "moderator" that I know someday...

https://forum.armbian.com/index.php?/topic/4519-moderator-duties/

More volunteers for this job? Not much to do but still it's better if load is shared.

A20 boards are generally just fine, while R1 ... we all know it's shitty by design and If we had EOS section since start, it would be already long gone simply because it sucked so much of our time, more than any other board, without any point & value.
 
There are four images for R1 for download - all are working now - I remake last image with last working mainline kernel (4.9.7) and that's all. EOS means we will officially not deal anymore with the board, but this does not prohibit anyone to make moves. Kernel updates will continue to run out so their is still hope for the board.

I also added two A10 boards there too. Why? They are working O.K., they are stable, but make just enough troubles on upgrades. Do we need to deal with them? No. They are rare and we don't have more than one sample around.
 

Well, I would complain too, but it doesn't make any good
 

Yes, I'll update and make it more visible asap. In any case nothing major before September.

Launch --- Due in 149 Days (or when it is ready)
 
and please put that somewhere were we can see that, like here (it is already written just needs a link to the lines above) 
    Countdown instead of frozen numbers ?
 

Really R1 ?
I know TK smashes on it by every chance, but
- no one ever beside TK complained about the design problem (just some speed junkies how want to have real Gigabit)
- short cable and IKEA PowerSupply I still power mine via MicroUSB - works like a charm other can use battery adapter explained on sunxi.
- it runs an A20  which is better supported than any other (which is the greenest in the table H3, H5??    NOOOO  it is the A10 A20)
- nowhere you find this 'smart design' HDD attached on the board.
- Igor ran the forum on an A20
I have no clue, why it didn't turn on the network properly after the changes, but it always did in the past.
 
And you want to kick this board - beside me there are many who use it and willing to test. Btw, even a customer of TK is having an R1 running, unless he replace the HW.
The loudest is not necessarily right.
 

I would prefer to adjust milestones to kernel and u-boot releases so we can migrate with the mainline and still have enough time to test and fix possible issues.
 
The wiki idea was discussed before, having a wiki means spending time in updating it, fixing possible issues from other people edits, managing access permissions, etc.
And regarding supported features - this example is far from complete but is already almost unreadable for an average user: https://linux-sunxi.org/Table_of_Allwinner_based_boards
And this is only Allwinner based boards.
 
And regarding the 5.30 networking issue - the problem exists in mainline u-boot since April, at least 2 people missed this issue completely, and we are talking about u-boot with more or less strict review procedures for patches and basic automated testing set up AFAIK. So even strict rules don't save from (kind of obvious to me) failures. And now we will be sitting on top of the fix (and another fix for H3/H5 I2C copy-paste issue in the DT) because we don't have a person who is willing to relay these bugs upstream or has a proper environment set up to send a patch.

OK, understood. Everything is fine, no need to improve (and yeah, really no need to babble any more since useless)

Thank you for this... This is a quite valuable resource...

Put up a "bounty" have those who wish to have a board supported or a feature added, have them put up some funds, plus the boards.
I donated because I find the process entertaining, gives my brain something to do, but if I had a project I could see paying for a feature or 2.
 
You guys need to offer more "fun", ...more projects which will draw in programmers and end users.
I see a bunch of folks hoping to do projects that are really pushing these boards, how about some IOT projects, Magic mirror, leggo bots an so on.
 
Igor's menu is a good start for those just starting out (reminds of Doug's menu for IBM DOS).
 Maybe offer access to the scripts, so folks can alter / add to it.