Hmmm

Posted in C.H.I.P., Linux, Orange Pi on July 22, 2017 by asteriondaedalus

So, here it is Sunday.

Morning coffee in hand while I wake up.

Dogs still asleep but will be doing backflips once they hear me getting their leads out for the Sunday bush walk.

OPiZ still up, node-red console full of reports of reboot every 5 odd minutes.

Since it has been in this reboot cycle since Friday night I am happy enough the nodejs, node-red, npm combo is not the contributing factor to the ethernet and usb stopping.

After the walk I will … well I will have a nap.  But after the nap I will … well I will build another C.H.I.P. with shairpoint-sync for the second sound bar.

Later tonight I might have another go at the emqttd install on the OPiZ.

I am still not sure how that might induce the dropping  of devices, but it in hindsight there is a conspicuous connection since the problems seemed to start once I had installed and was running the emqttd – that observation holds over the at least a dozen times I re-burnt then setup a distro for the OPiZ.

Curious, because these are the exact same steps to set up a Raspingdoodleburry Pi or ODROID-W with the same combo of app – neither with any problems with devices dropping.

Pump up the volume

Posted in C.H.I.P., Embedded, Linux on July 22, 2017 by asteriondaedalus

So Target had finally dropped prices of sound bars with aux input to AUS$49 so I can deal with the wife’s nagging about the BOSE wifi sound system with a $9 C.H.I.P. and a $49 sound bar.

Voila!

thomson

Perfect for the bedhead in the main bedroom and the window sill in the guest bedroom or in the book case in the wife’s study.

I only bought two as we had the speaker tower in the backroom.

Now, given all the problems I had with Armbian.com debian server distro and the OPiZ, here I am using nmcli to setup the static IP for the wifi on the C.H.I.P. with no problems.

Given I had the 3-pin serial cable out, I just swapped it over to the C.H.I.P. from the OPiZ.

I flashed with the headless server version 4.4 of for the C.H.I.P..

I used nmcli to setup the wifi using the provided example.

I then used “sudo nmtui” and setup the static ip and then reboot.

I found the device on my gateway list of wifi devices … bute!

To install shairpoint-sync I simply followed the instructions at Hackster.

The trick is where the instruction asks for interpolation to be set to soxr I reset it back to basic.  I also set the alsa property:

audio_backend_buffer_desired_length_in_seconds = 0.5 (it was set to 0.15).

I did this because the audio would drop out briefly.  Evidence is the soxr interpolation takes a grunting cpu and there might have been some network problems.  So, between relaxing the interpolation and buffering more audio, the dropping of audio apparently has ceased – much to Madam’s delight.

The nuisance, the wife has given up her iPhone for a Samsung S8 – which she doesn’t like.

I found you can get Airplay running on Android so we could get by.  I bought her a new laptop but she hasn’t moved her iTunes to that yet.

She hasn’t installed iTunes on the PC that I built her.  iTunes is on her old laptop so there are some politics there to get that transferred – especially as I have my eye on her old laptop to be my 64bit Debian dev box.

So while the Airplay route is “comfortable” it is rather “complicated”.

However, she has an iPad that she now hardly if ever uses so it can be the server for the house music.

Too easy drill sergeant!

Too easy, that is, because even though I am using a debian based distro on the C.H.I.P., and essentially using the same tools to set up the C.H.I.P. as I was the OPiZ, I am having no problems with C.H.I.P. headless server.

What?

Oh … yes, if she asks BOSE was bought out by Thompson.

 

 

PEP

Posted in Arduino, IOT, MQTT, Networking, Wifi on July 20, 2017 by asteriondaedalus

So, following up after a previous promise I got myself a cheap arduino touch screen that was on sale, to act as a Programmable Entry Panel or PEP.

I will use the Wemos D1 and the Arduino core fore same to try to port the associated library onto Wemos D1. That way I can have a control panel via MQTT.

Yes, there wiĺl be a Android version as my wife got herself a Samsung – though so hates it.

Saves me the hassle of working in iOS.

Setting up node-red yet again

Posted in Linux, Orange Pi on July 20, 2017 by asteriondaedalus

Are you still with me? I wouldn’t be, it’s been such a pain. Because network manager appears flaky somehow.

On the Armbian.com distro the /etc/network/interfaces file told you directly to use network manager and nmtui. This intimated that you couldn’t edit up the interfaces file.

I got no joy when I edited the interfaces file, while trying to get around the flakiness that appeared to be incurred, but that could because network manager was the default service – and was not reading the file??

Now, on the orangepi.org distro, it looks like you can use nmtui/nmcli optionally but, of course, we have seen the network connection collapse.

Now I didn’t look to see if at some point /etc/resolv.conf was set by network manager to some flaky value and therefore breaking the connection.

Now we have that up our sleeves as we try try yet again again.

Yes, I have an alcoholic beverage on hand.

So orangepi.org distro installed and static IP setup.

First step, install node-red.

I will leave the system running until Sunday before I try installing emqttd as I want to give it a good burn in to make sure there isn’t something in the node-red install breaking the ethernet.

To stress the distro I set up a cyclic reboot in node-red with the following:

reboot

I just set an interval of 5 minutes on the injector.  The debug node will scribble the timestamp on the debug console when the interval lapses.  At the same time the OPiZ is rebooted.

Not a sausage?

Posted in Linux, Orange Pi on July 20, 2017 by asteriondaedalus

So, I reburnt the SD with the orangepi.org distro.

I gave up on nmcli/nmtui and I went back to the good ole /etc/network/interfaces edit, or at least I created:

/etc/networks/interfaces.d/eth0

Set the contents to:

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.100
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers …

When I set up I now happily get:

root@OrangePizero:~# ip addr show
2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether f6:78:ae:aa:0a:d8 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global eth0
inet6 fe80::f478:aeff:feaa:ad8/64 scope link
valid_lft forever preferred_lft forever

So, board seems to setup the eth0 as I want it to.

However, my network simply does not see the board.

I have a bag of short ethernet jumpers from aliexpress … hmmmm … nope.  I swap a few out so unless they have sent me a dozen dud ethernet cables it isn’t the ethernet cable.

So, it looks like the problem might have been that I had the following

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.100

I commented out the hotplug line, rebooted then voila!  My OPiZ was “seen” on my local lan again.

But …

… still can’t get out to the world???

Well, apt-get doesn’t resolve.  A ping to google.com fails.  A ping to 8.8.8.8 succeeds ???

root@OrangePizero:~# route -n
Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 1024 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

So, why am I not getting out?

root@OrangePizero:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr f6:78:ae:aa:0a:d8
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f478:aeff:feaa:ad8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1559 errors:0 dropped:172 overruns:0 frame:0
TX packets:489 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:246564 (240.7 KiB) TX bytes:37710 (36.8 KiB)
Interrupt:114

So, I note I can ping google.com from my PC and I can ping the OPiZ from my PC.

I can ping my PC from my OPiZ.

Ah ha.

/etc/resolv.conf

is set to:

#the following is set by network manager
nameserver 192.168.1.1

So, that won’t work on my network given the ISP router provides two nameserver addresses before you would bother with the free nameservers. Not to mention my gateway is 192.168.0.1 and so the dns requests were getting nowhere.

So I manually set up resolve.conf to two name servers given by my ISP and the two free ones (to be sure, to be sure).

Happily now pinging google.com.

I have run apt-get update again.

Ready to start all over again … again.

All this as the node-red was running fine but the network went kaput on the OPiZ somewhere in the middle of the emqttd install.

I can’t put my finger on when during the emqttd install, but there were all the problems with wget and then I did twiddle with certificates. However, why on earth would that blow away my network configuration???

No useful hypothesis as yet so I will check regularly during the emqttd install steps if see if/when the connection breaks.

I also installed a watchdog node into node-red and set up a 10 minute timer to reboot the OPiZ to stress it.  If it is up on Sunday after all those reboots we can likely discount the node-red and I guess the npm as the culprits.

Ultimate Insult

Posted in ODROID-W, Raspberry Pirate, RaspingBreathburryDOodlePi on July 16, 2017 by asteriondaedalus

Rasberry Pi community bullies hard kernel to drop ODOID-W through broadcom connection. Now comes out with RaspingBerryDoodlePi Zero W. 

They should be disqualified from using “W” annotation. 

Windoze 10 updates SUCK!

Posted in Sucky service Providers on July 14, 2017 by asteriondaedalus

So, you might recall a few months ago I complained because the Windoze 10 update on my PC hung 3/4 of the way through an update.  It just plain stopped.  Sat there for two days.

Well, I thought they would have had a un-admitted problem (Microsoft and McAffee at least being two orgs that roll out problems, deny their existence and then sneak a roll out that fixes the problem).

Who knows.

I bothered to accept an update, in the vain hope they had “fixed” their quality control problem.

Nope.

Hung again.

So I am stuck in limbo with no means to update my PC anymore.

Probably time for a new PC.