@crispyoz I was already at a point of unable to duplicate. Turns out I did some of the same actions you did, so between us I think we've figured this out to the extent it needs to be figured out. Have a great day!
The details of my life are quite inconsequential... very well, where do I begin? My father was a relentlessly self-improving boulangerie owner from Belgium with low grade narcolepsy and a penchant for buggery. My mother was a fifteen year old French prostitute named Chloe with webbed feet. My father would womanize, he would drink. He would make outrageous claims like he invented the question mark. Sometimes he would accuse chestnuts of being lazy. The sort of general malaise that only the genius possess and the insane lament. My childhood was typical. Summers in Rangoon, luge lessons. In the spring we'd make meat helmets. When I was insolent I was placed in a burlap bag and beaten with reeds- pretty standard really. At the age of twelve I received my first scribe. At the age of fourteen a Zoroastrian named Vilma ritualistically shaved my testicles. There really is nothing like a shorn scrotum... it's breathtaking- I highly suggest you try it.
@Maurizio-Messa Here is grasping at straws, but..... The time or three I've seen a failure to sync I was able to fix the problem by reflashing the device. See https://docs.onion.io/omega2-docs/factory-reset.html. Ought to take just a few minutes.
Again, grasping at straws. If that doesn't help I'll take a more detailed look at it.
Additionally, messages not being received seems to bring up troubleshooting tip #1, that being, are messages being sent. Have you validated messages are still being sent after the stoppage of receipt?
@Chris-H Regarding biasing LED, making a guess on voltage drop is not a bad deal as you can get to a solution fast....or slow....depending on the guess. On the other hand a more design-forward approach would certainly get you to a solution on first try. Here's what I would do.....
Find the data sheet on the LED. Among all of the tech data you will find a V-I curve (at voltage x you expect current y). Now guess (yes - guess!) at a sensible voltage to turn on the display. Better yet, if you have a variable voltage supply, apply it to the diode at near zero volts and increase until you have the brightness you desire (or until it explodes). Now with your guess from whichever path you chose, the remainder of the voltage drop must be across the resistor. With the measured or graph derived current you can select a ballpark resistance value. Find the nearest off-the-shelf resistance value you have and you'll be good to go.
I'd like to test this. I'm motivated as I have field deployed units that will fail, making me very unpopular with my client.
I probably have all of the test equipment required to create an automated test that could execute tens of thousands of test permutations with no human in the loop.
Do any of the Onioneers have any interest in collaborating with me in creating a test plan and test procedure, perhaps writing a few lines of code, etc.? My up front view is to do it in public view on this forum, unless our friends at Onion suggest otherwise. If the latter, we'd collaborate in some other fashion.
See http://community.onion.io/topic/2042/openwrt-and-lede-agree-on-linux-for-routers-peace-plan/5 as @Lazar-Demin indicates open source is the current regime. You can find a link to the repository at that link.
I posted a message a few weeks ago related to this topic. There were many readers of the topic, but no responders. Interesting....
Within days I'm going to design a sensor data and status reporting regime for field deployed Omega2+ (O2+) devices. Implementation would shortly follow.
It seems every device I run in my house (office is at house as well) will come up with a IPv6 GUA address, with the exception of the O2+ devices. What is the significance of this? Every device (desktops, telephones, RPi's and others) come up globally routeable. I can sit at the pub (not that I ever do that) and ssh into the Pi or one of the Linux servers using a IPv6 address with total disregard to the IPv4 NAT reality of most home and office environments. The O2+ devices are not automatically generating IPv6 GUA addresses and are therefore cannot be routed to from the outside of a NAT environment.
What config parameters need to be changed, and in which files, to "encourage" the O2+ devices to compute their IPv6 GUA addresses?
Here are some thoughts.
Hold off on re-flashing, if you can, until this forum has done what it can to help out. The folks here are pretty awesome!
When hooking up Tx and Rx lines, don't forget the ground/return line. This ensures the tranceivers are playing in the same playground.
Time and again I will hook up a Tx at one end that is a Tx at the other end, which of course won't work. Write down your circuit diagram and don't actually wire it up until you are happy with it....on paper.
If possible avoid soldering until you need something "permanently" connected. The double quotes to indicate sentiment, not literal behavior. Do what you need to do. Think forward.
Do you have other docks (e.g. Expansion) that may be usable in troubleshooting?
This is possibly a storage space problem. A bare bones O2+ doesn't have the storage space to accommodate python3, if I remember correctly(????). Run 'df -h' and 'free -h' to check on current mountings and free space, respectively.
Has storage been upgraded?
Not a big deal, AFAIK, but after the Monday upgrade some things are squirrely. Load most recent items from most recent icon. Refresh page. Do each a number of times, repeatedly or alternatively (actually, do both as the inconsistency becomes evident).
Reflash the device. If you have an expansion dock, hold the reset button until the device amber LED starts flashing rapidly, perhaps 8 to ten seconds, then await a reboot. You ought to be good to go, but starting over with a virgin device. Would then need to go through the process of connecting WiFi, etc.
I've built on over a dozen O2+ devices. Have not damaged a single one to the point I couldn't recovery it with a factory boot. HOWEVER, I have indeed fried five expansion docks with nothing other than a USB connection! That's right! Not something boneheaded like setting a power supply to 50.0V instead of 5.0V. Just a USB connection from a PC! The symptoms you describe may just be a fried expansion dock.
Please also, as expeditiously as possible, delete the offending accounts.
Looks like your connection to Community was lost, please wait while we try to reconnect.