Archive for the Sucky Wucky RaspingBreathBurry Category

Bad Broadcom, bad, bad!

Posted in ODROID vs RaspingBreathburry, RaspingBreathburryDOodlePi, Sucky Wucky RaspingBreathBurry on May 20, 2019 by asteriondaedalus
Bad Bad Broadcom

So, with antitrust investigations, including accusations of monopoly practices by Broadcom, does anyone remember ODROID-W?

I do.

The rants in the Raspingdoodleberry Pi community about ODROID cheating, even though RPi comes under Creative Commons were interesting.

The gotcha appeared to be the documentation was Creative Commons (CC), even the design documentation, but building hardware based upon the design documents was not (apparently) acceptable to some.

The notion of opensource hardware appears, in fact, to be PCB level and not schematic level. So, without specific restrictions in place, building a PCB from the supplied schematic is a remix, in tune with the CC offered by the rasping lot.

So, the idea that can remix the schematic design, as you may or may not have had to to come up with ODROID-W, but you can’t build hardware from that schematic to get remixed PCB design is curious? What is the point then of that CC?

The variant of CC applied by The Rasping (is that a better jibe) should have been Non-Commercial, No Derivatives. Since The Rasping did NOT apply that restriction THEN all the bleating by members of The Rasping was unkempt, uncalled for and The Rasping should have culled the conversation and educated its members. In fact, it may draw attention by any investigation into Broadcom, since the banter was likely monopolistic in intent, especially where Broadcom employees joined in the discussion on The Rasping.

All the gaff about using the poor Raspingdoodleberry software developers efforts, when the software was offered opensource! Suck it up Princesses. You only asked for attribution. You got it.

So, is this just monopolising by Raspberry Pi community? How connected is that practice with accusations about Broadcom practices?

The more interesting thing is, apart from potty talk from the Raspingdoodlebury community, there appeared no other action directly on their part. The action on behalf of the Raspingdoodlebury Pi was apparently taken by Broadcom (according to some viewpoints).

Its hard to unpick the Broadcom/Raspberry Pi think.

Interesting, all very interesting.

I wonder how broadly the investigation into Broadcom, and monopoly practices, will look?


Posted in Docker, Sucky Wucky RaspingBreathBurry, The downside of Opensource, thingbox on August 24, 2018 by asteriondaedalus

Alright, so I gave up on the OrangePI as my house server because it would clap out after a week and need a reboot.

I swallowed my pride and bought a raspingdoodleburry pi and tried to set up with node-red and mqtt.  Got boring trying to sought problems with install and setup again, after all the crap I went through soughting the OPi.  So, I relented and decided to cheat and use thingbox or TB as it is affectionately euphemised.

Problems so far.

  1. It took a prompt from me to get TB owners to eventually build distro that would support rpi 3B+.   That is support is now the TB 3 beta Docker based image.
  2. Burnt a SD card with TB 3 beta Docker based image and verified by Etcher, inserted SD card into Pi3B+ and booted rpi,  found the “thingbox.local/” on my network and web browsered in, setup my own server name at initial prompt, fell into node-red editor, and all worked fine until I tried to do more that say hello TB.
  3. Tried to download modules using module manager to find most all the google assistant based modules failed to install.  There might be more, who knows.
  4. I found one module that installed, but it was lost on reboot which is not supposed to happen.
  5. I tried setting up wifi but after reboot the wifi configuration was lost and I had to go back to hardwired ethernet.  TB won’t even keep preferred language option after reboot.  Since it saves host name after initial start up, something is likely locking out saving post initial TB setup, before it drops into node-red editor.  Whether that is before or after the Docker daemon is started on first use of TB would be interesting.
  6. I find .local only works between rpi and my PC which are both hardwired to a wifi extender.  Local seems to really mean physically local?  The rpi cannot otherwise be seen on the wifi using .local.  It may be seen using raw IP but I got bored with debugging the TB distro.
  7. Why use an abbreviation for your product that is also used for Tuberculosis?

Since this is a Docker based image, and you cannot adulterate the Docker session without cracking into Docker session, and I have not ssh’d into the board since it was setup with TB image, therefore I have not touched any settings nor configuration.  It is safe to say there is something funky about the Docker image.  This is safe to say because of the promise Docker provides around container assembly and distribution.

So, I am likely back to having to go through by hand and set up the rpi with node-red and mqtt myself.   I have started playing with Docker so I might as well look at this as my Docker exam.

Gag and double frack!

Posted in Sucky Wucky RaspingBreathBurry, The downside of Opensource, The Downside of software development on March 28, 2018 by asteriondaedalus

I have officially given up on the OrangePi Zero as the server for my house.  The system drops off the LAN after a week or two of running, which is no good if its running sprinklers and lights etc.

I regretfully inform I have chosen to get a RaspingDoodleBerryPi to drop TheThingBox onto it.

I don’t otherwise have to admit having one.

I got a black case and I will mount it out of sight on back of a black WiFi router.

It will be between you and me.

At least I can give up on this time wasting debugging.

I did almost steal an Odroid C1 off my cluster.  Almost.

Still, I have two small linux boards now.

I am going to re-burn SD and try to build moos-ivp on one of them.

Why not, worked a treat on my BBB.



Posted in Sucky Wucky RaspingBreathBurry, The downside of Opensource on November 27, 2016 by asteriondaedalus

The RaspingBreathBurry my mate gave me, though I appreciate the gesture, I can sense his reason was as it is such a slug.

I FINALLY seem to have 2.4.o of TheThingBox sluggishly wasting bit traffic on my lan.

5 minutes of “busy” gadget spinning and it managed to display the red-node title bar but it did not draw gadgets, or canvas, or properties panel.

I think I will have to press a precious ODROID C1 into service.


What a waste of a Sunday Afternoon!

The Google Calendar that comes out of the box with TheThingBox may be a knobbled version of the node-red-node-google suite.  Go figure then, as the 2.4.0 of TheThingBox includes the 0.15.2 update it has a palate manager.  Yes, you guessed it, as hard as I tried to update the palette with node-red-node-calendar it would not install.

That might have to do with nodes from ttb-node-google-calendar in use.  Who knows.

Certainly you cannot remove a palate if anything off the palate is on a canvas.  So I cleared of the canvas to un-ghost the “remove” button for ttb-node-google-calendar and … yes, you guessed it tens of minutes later the “busy” gadget is still ticking over.  So, I may not be able to clear out the unwanted palate nor add the node-red-node-google palate to the RaspingBreathburry.


So painful.

So, I jumped on the bike sitting on its trainer and span for half an hour while letting the “busy” gadget spin.

Came back … doh!

I found the palette up again and thought someone was finally smiling down on me.

I spent another couple of hours with spinning “busy” gadgets, thinking about how my Grand Father used to fix everything with a 5lb sledge hammer and an angle grinder, and what a lovely gesture of remembering those times with him it would be if I took a 5lb sledge hammer to this useless RaspingBreathBerry.

Eventually, after a reboot or three having tried fruitlessly to either remove or disable the ttb-node-google-calendar and install the node-red-node-google palate, the expected nodes were in the palate.

So, I sheepishly added a calendar object and YES! it was the node-red-node-google calendar.  So I went to register it and … kaput.

Long story short the google api won’t accept  http://thebox.local/google-credentials/auth/callback as the callback.

I assume then that is why the ttb-node-google-calendar nodes were created??? Who knows, they wouldn’t connect, the node-red-node-google nodes wouldn’t connect.  Since there is no real documentation in and around that ttb junk the canned TheThingBox seems to be no help.

So we are back to setting up an ODROID C1.

Before that I will try the red-node I have running on my ODROID-W as I had not upgraded that yet nor have I used the google gadgets on it.  It was handbuilt using node.js, npm etc.   I also was using  emqttd instead of mosquitto so it might as well be a handbuilt system – it actually took far less time to set that up than to try to track down the problems with the RaspingBreathburry.

Certainly after the 5 minutes it took to sort out node-red-node-goggle connection to api and getting my calendar to ping the node-red on my PC, the nuisance in and around TheThingBox approach still needs work – but not from me.


Posted in OpenSprinklette, Rant, Sucky Wucky RaspingBreathBurry, The downside of Opensource on November 27, 2016 by asteriondaedalus

So, I ripped out node-red from my PC and re-installed.  I then re-added node-red-node-google.

Now the behaviour of google nodes in the PC variant was different to the google nodes on TheThingBox.  When I went to the properties of the PC variation I got the following:


So it turns out you clip the redirect URI into the google api credentials info:cred2

And voila!


Two events from google calendar, one at start of event and the other at the end.  So good enough to turn sprinklers on and off.  Yes, I just set up a calendar on google called “sprinkler” – too easy.

Doesn’t help, though, getting the RaspingBreathBurry going.  But may mean I need build node-red onto the RaspingBreathBurry and avoid TheThingBox install.  The problem is either they “adjusted” it for TheThingBox as an app OR it’s broken.  Either way, if I can’t connect readily to the google calendar then too much code need be written.

Now, spread out over internet is the problem of which api to enable.  The guidance says “Directions API” which doesn’t make sense for Calender events.  All forms of dribbling all over the place.    Turns out you want to enable Calendar and Google+.  Not even sure that you really need Google+ for calendar things but it is enabled.

Niggly I know but courtesy would be to just list the api required and the steps to boot.   This “you are stupid if you can’t work things out” bullshit of opensource flies in the face of application of learning theory from educational science.   I guess it is also a passive form of bullying by anti-social gimps.