Archive for the Sucky Wucky RaspingBreathBurry Category

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.

 

Advertisements

Grrrrrrrrrrr

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.

rprndud

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.

POST SCRIPT

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.

DOH! DOH! DOH! and FRACK!

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:

cred

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

And voila!

cred3

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.