Google Analytics

Wednesday, February 17, 2016

Home Security/Automation System - New Design!

Design Update  (February 17, 2016)
Previous     Next     Table of Contents

Well, if you've been following this blog from the start, then you know that I've had a lot of hurdles to overcome!

My background in programming, while extensive (beginning in 1977) and including many programming languages, did not have any real front-end presentation layer activities.  So, with no front end stuff, then no HTML, no Javascript, no Nodejs, no Express, no Jade.....just a lot of "no's!".

Since I had a lot of Java background, that was my first approach.  But it was just too heavy for my target hardware - a Beaglebone Black.  Also, I was tired of programming in it!  Since I was now retired, I decided I wanted something more efficient than Java, both from a programming standpoint, as well as a system load standpoint (Beaglebone remember!).

My search led me to Python.  I considered Scalia and Ruby, but Python looked good to me, and was something I could easily use on future code for around the house.  So, I started planning on Python.  But I ran into a problem on the front end presentation layer - not much better than what I was used to in Java!   But I kept going...see my posts on Kivy on this blog.

Life intervened, and I had to stop the project for a while.  But I kept occasionally researching, and somewhere came across nodejs.  This really peaked my interest.

I dug into nodejs (note: this is the new, correct spelling for this product; after their recent merger, then changed the name from node to nodejs).  I really liked what I saw.  That, along with the ability to push data to a HTML5 browser (I refused to do polling) meant I could move off of Kivy etc. bandwagon, and move to a browser, which would simplify a lot of things, particularly with respect to system monitoring while away from home via the internet.

So, I started leaning Nodejs, which begat getting a firmer knowledge in Javascript.  Then backtracking to HTML, then CSS - none of which I needed in my professional life before; well, OK, I did some stuff, but barely anything.  Then came Jade, and document databases, and Nedb.  Then somewhere Express.  I stayed away from CSS, Express, Jade for a while, because I was concerned about the Beaglebone being able to host all of this, but it turned out not to be a problem.

So, if you were like me, experienced programmer, but needing web based knowledge, then I was suggest the following learning path, in this order:

  1. HTML
  2. CSS
  3. Javascript
  4. Nodejs
  5. Express
  6. Jade


So, my redesign!

  • Uses the Beaglebone Black.  I'm going to also develop on the Raspberry PI 2; will update with that info.
  • Hosts a web server via Nodejs
  • Uses the Google Chrome browser.  Others may work, but I'm not testing or programming to those other platforms.
  • Provides dynamic web page security updates.
  • Displays current weather information while no security work or events taking place.

Since the base display is weather displays, and I needed somewhere to start, I first programmed the weather display system.  The design for this is:

  • Runs on Beaglebone
  • Hosts a web server via Nodejs
  • Uses the Google Chrome browser.
  • Provides dynamic web page weather updates.
  • Obtains live data from wunderground.com for my local, every 5 minutes.
  • Obtains static radar jpg images from weather.gov and wunderground.
  • Displays a digital clock, data from the Beaglebone pushed to web page.  If the network drops, the Beaglebone freezes, the server freezes, the browser freezes - then the seconds no longer update.  In the future, the time will also change color, and maybe an alarm is generated.
  • Will switch to security mode on work or event.
The weather system is functional.  I'm currently refactoring the code and adding a few new features.

When those updates are complete, I will publish.

Banjo

Nodejs: Passing values from Express to jade to javascript!

Passing values from Express to Jade to Javascript

Note: jade version 1.11.0
Today's date: 2/17/16
Note: assumes you are somewhat familiar with the technologies mentioned (nodejs, jade, express, javascript, html)

I've been hard at work on my security system, but came across an issue that took several hours to resolve.  I'm a very experienced programmer (C, C##, Java, Python, assembly, Fortran, Basic, etc), but almost all of that development has been done on back-end stuff; not much GUI front end stuff, no HTML stuff.  So, I'm somewhat weak on the front-end stuff; just now leaning nodejs, jade, express, javascript, html!

The security system I'm designing and building requires a lot of front-end stuff; it's showing the status via sms text messages and the browser.  This means the architecture is going to make use of:

  • Nodejs (note this is now the correct spelling for this product)
  • Jade (used with Nodejs)
  • Express (used with Nodejs)
  • Javascript
  • HTML

Instead of having an image of the current security system on display in the browser all of the time, I decided to have the current weather shown, along with the current time.  Weather in the Southeastern US can be quite volatile, so I have kept a radar image up on an old laptop in our living room for years, so weather is important to me to keep aware of.

The idea is the weather will be shown until either I select to view/work on the security system, or a security event occurs, in which cases the browser will display the appropriate security screen.  As part of the weather, I'm getting current weather information from the Wunderground.com API.  For items such as radar images, I'm looping through some current jpg files that are offered from weather.gov and wunderground.com

Now - the problem I was encountering.

In looping through the various web pages, I have to have a delay between pages in seconds.  I want this value to be passed in at the time the application is started, for the default value.  Later, I intend to add a change that will let me interactively change the delay time.

The current architecture, using Nodejs and Express, renders a loopingPages.jade file.  I'm passing the the DELAY value obtained at startup via process.env.DELAY in app.js, where it stores the value, before rendering the looping pages.  So, the DELAY value is passed from the startup command line to the app.js (the server), then to the jade rendered page via:

     app.get('/loopingPages', function(req, res) {
          res.render('loopingPages', {delay:DELAY}
     });

The jade file loopingPages.jade includes a script file.  So, to be clear, the value that is originating from app.js server (using Express), needs to be passed to the rendering jade file loopingPages.jade, and this file includes a javascript file loopingPages.js, where the DELAY is actually used.

Well, I couldn't get it to work.  I could get the DELAY value from the environment variable passed at startup using the 'process.env.DELAY' term, but I could not get it to propagate properly.

After a lot of searching on the internet, I was unable to find an example that matched the one I needed, and most were old.  Seems this was an exercise in futility and esoteric programming!

But, I finally got it to work!

Below is a simplified version, which I was able to get to work.  It assumes you have created a fresh nodejs Express architecture for using this, which creates the proper directory structure and contents that I'll add to.  All directory locations are relative to your base directory for the application where app.js is located.

1. Modify routes/index.js to add name:'Banjo'
        res.render('index', {title: 'Express', name: 'Banjo' });

2. Modify views/index.jade to add p My name is index.jade #{name}
It should look like this:
     h1= title
     p Welcome to index.jade #{title}
     p My name is index.jade #{name}

The #{name} will show the name value passed from the app.js on the web page.  The #{title} was already available from the initial build.

3. At the bottom of index.jade (above), add the following inline script and script src:
     script.
          var theName = "#{name}"
          var theTitle = "#{title}"
          console.log("name passed in to index.jade is " + theName)
          console.log("title passed in to index.jade is " + theTitle)
     script(src="/javascripts/indexInclude.js")

Note the new file indexInclude.js which you will create next.

4.  Using your programming editor, create the file
           public/javascripts/indexInclude.js
It should have the following content:
     console.log("This is from indexInclude.js");
     console.log("+++++++++++FINAL: IF Banjo SHOWS THEN SUCCESS!+++++++");
     console.log("indexInclude.js theName is " + theName);
     console.log("+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++");

5. Run the app.js server
6. Open your browser to your localhost:port needed for nodejs
7. Confirm you see 'Banjo' printed on the page
8. Right-click on the page, then do 'inspect element' or similar for your browser.
9. Select 'console' tab
10. The console.log item should show text that includes the above (step 4) Banjo.

I hope this has helped you!

Banjo


Saturday, September 19, 2015

Python and Kivy: out of here!

Home Security System
Previous     Next     Table of Contents
Date: 9/19/15

A while back I started a Home Security project.  After examining several different approaches, I settled on Beaglebone Black for the hardware, programming with Python and presentation using Kivy.

After much work on Kivy, and continuing issues with the Linux Angstrom that was on the Beaglebone, I came to the conclusion that it just wasn't ready for prime time, and I suspended my project waiting for the technology to catch up.  This was easy to do, as I always have more to do on my plate than time to do it!

Recently, I decided it was time to take another look at this project.  I purchased a new Rev C Beaglebone Black, then started working with it.  This was a major improvement, as this version also moved from Linux Angstrom to Debian.  I was unwilling to try and work with Angstrom again, so the move to Debain was great news.

I became convinced that the pyvenv development environment would work best, but that entailed moving to Debian release 8 or 8.1 instead of the current 7x version, and Python 3.4.  So I quickly got well acquainted downloading and installing various test releases of Debian 8.1 for the Beagle.

Once the OS and Python versions issue was resolved, I set up the project on GitHub, and started moving forward, with the first task to set up do to builds on the Beaglebone while using pycharm as the IDE on my host Ubuntu system.  I mounted a host directory onto the Beagle using sshfs, so that code changes I made within pycharm would be directly available for code running on the Beagle via the shared directory.  I would edit in the IDE on my host, then use a terminal session that was logged into the Beagle to run and test the code.   This worked really well, and all my source code was maintained on my host and pushed to github as well.

With those issues resolved, I began to look into the presentation layer.  I really was concerned about trying to use Kivy after all the disappointment from a while back.  Looking at the emails from the Kivy group - there were still a lot of issues.

All of my previous work in IT had primarily been devoted to development on the back end, with very little work on front end presentations.  However, I had come across some articles regarding html5 and it's ability to work with websockets, so I wanted to take this opportunity to do a little deep dive into html5 to see how that might better fit my presentation layer problem.

The first thing was to take a look at the Beagle's onboard webserver.  I had not really taken a look at that in the past, but now with all presentation options on the table, I did take a look.

Wow!  What an insight that was!  A little bit of nodejs code, and batta-bing, I was serving up simple web pages!  And there was a direct ability to push data from the Beagle to the presentation via a web page.  This really looked like the approach I had been seeking: a user has a web page up (a security monitor), the Beagle first supplies the current state of all sensor elements, then pushes any updates (sensor state change) to be displayed on the web page without the user having to refresh the web page.

This was it!  While I was happy to drop Kivy, it also looked like the easiest approach would be to move totally away from Python and over to JavaScript as well!  That was a shock!  This also meant I no longer needed pycharm; I no longer needed the sshfs (well, it may be a little early yet to decide that), I no longer needed pyvenv, so I no longer needed Python 3.4, and that meant I no longer needed Debian 8.1 either.......holly cow!  The last weeks worth of changes to the OS, pyvenv, pycharm, Python - all now relegated to the trash heap!

I'm going to take a look at Debian, nodejs, and JavaScript to see if there's any benefits to staying with Debian 8.1 (which at this time is in 'test' mode; prelease), but I'm hoping it's not needed, so I can stay with the standard deployment.

So: this project has abandoned Python and Kivy!!!

Moving to JavaScript and Nodejs!!!

I will be documenting the development of the Beagle project, utilizing JavaScript, nodejs and bonescript here.  Stay tuned for updates!

I will be placing my detailed notes on setting up a development environment for the Beagle for Python here on this blog at a later date, as they may be of use to someone doing Python development for use on a Beagle for their project.



Wednesday, September 2, 2015

February 2016 update:  Recently, TOS pushed an update out that moved from Java 1.7 to Java 1.8.  This has corrected most, if not all, problems outlined below.  I do not think the information below is still needed, but will leave it here in case it helps someone now or in the future.
Thanks,
Banjo


ThinkOrSwim (TOS) on Linux!

Please check the date you are reading this - because TOS makes frequent changes, the information I'm providing here may not work for you.

I'm currently running TOS on three (3) different platforms: Ubuntu 14.04, Windows 7 (on VirtualBox in Ubuntu 14.04), and on LinuxMint 17.02.

All are working, although the Windows version is, by far, working the best.  There just doesn't appear to be much interest from TOS in making this a quality experience on a Linux based machine!

I'm not going to detail any installation on Windows - the TOS installation is fine.

Instead, these are are my 'notes' from installing on LinuxMint - it was the same as on Ubuntu.

- from a terminal, verify the version of Java you are running, using the command
        java -version

The response to this on my machine is: "build 1.7.0-88-b15".

The main thing here is that it must be version 1.7.......!  TOS will not work with 1.8..... or newer!   If you aren't running version 1.7, then you will need to resolve this before you go any further.  In my case, it took me a while to resolve, but ultimately I ended up (first) verifying I didn't have any applications using Java 1.8, (next) I uninstalled Java 1.8, then I obtained Java 1.7 from Oracle and installed it.

The following assumes you running 1.7...!


- pull the Linux distribution down from TOS website.  Specify the Ubuntu/Debian version.

- save it to your download folder.

- run the TOS install, being sure to install for just yourself, not for all users (this is very critical) at the popup window.  We won't be launching via the desktop icon, so there's no need to let it install this.  Instead, we will be launching from via a terminal shell command.

- once installed, you'll have to make some mandatory edits to some of your TOS files.

- the first edit change is associated with the amount of memory that can be used by the Java Virtual Machine.  It comes preconfigured with a really low value.  So, we're going to change this.  I'm using a starting value of 1024 MBytes, and a max value of 2048 MBytes.  That means TOS will start with a minimum of 1.024 GBytes of memory allocated, and can consume up to 2.048 GBytes.  Make sure you have enough memory to support those values, or set to your own system capabilities!

- in terminal, enter: cd  #to make sure we are starting at your home directory
- in terminal, enter: cd thinkorswim
- in terminal, enter: cp thinkorswim.vmoptions thinkorswim.vmoptions.bak #to make a backup copy you can revert to if needed.
- in terminal, enter: gedit thinkorswim.vmptions
- in gedit, find the line: -Xmx<>m  , and change the value to -Xmx2048m # I no longer know what my original values were, but seems like it was 512m
- in gedit, find the line: -Xms<>m  , and change the value to -Xms1024m #remember - adjust these values so as not to exceed the amount of free memory you have available, or else you will start swapping, and the system will be too unresponsive for you to use at that point.
- exit and save from gedit.



- the next edit change is associated with changing the TOS shell script that launches TOS.  It's located in the same directory you were in above (~/thinkorswim).  So, you are going to gedit the directory/file ~/thinkorswim/thinkorswim

- in terminal, find out where the Java executable is located, by issuing the following command in the terminal: whereis java
- my response to this contains multiple fields, separated by 'space'.  The installation on my machine makes use of file links, so I'm going to show you how mine resolved.  The first field response to 'whereis java' is the important field.  On my machine, it begins with /usr/bin/java

-- Steps to see linkage:
-- in terminal, enter: ls -al /usr/bin/java   #responds /usr/bin/java -> /etc/alternatives/java

-- in terminal, enter: ls -al /etc/alternatives/java #responds /etc/alternatives/java -> /usr/lib/jvm/java-7-oracle/jre/bin/java

--this is the actual location of the file.  You should be able to use any of these values in your thinkorswim shell script, but if you have problems, use the last one - the actual file and location.

- Verify this on your system!  If it doesn't resolve to Java version 7, then you can't use it.  I haven't tested it, but even if you have a Java version 8 installed, if you point to this final location of Java 7, then it probably should work.

- in terminal, enter: cp thinkorswim thinkorswim.bak #making a backup copy you can revert to if needed.
- in terminal, enter: gedit thinkorswim
- in gedit, find the line:  #INSTALL4J_JAVA_HOME_OVERRIDE
- you are going to remove the comment (#) character, so do that!
- next, you will need to enter (assuming you are going to use the final location from above), or the links (if they are all set up properly): /usr/lib/jvm/java-7-oracle/jre/bin/java   
- Your line should look like this:
 
INSTALL4J_JAVA_HOME_OVERRIDE=/usr/lib/jvm/java-7-oracle/jre/bin/java

(unless you used your verified link /usr/bin/java instead.  Note that these links can change if Java updates to 1.8 or newer on you at some point, so a good reason to use the hard coded version until TOS ever gets around to upgrading their JVM version reliance.)

- At this point, the changes required to get going should be complete.

- However, this would not work correctly on either my Ubuntu system, nor my LinuxMint system, if I used the desktop launcher for TOS.  However, if I opened a terminal, and from the ~/thinkorswim directory entered:
   sh thinkorswim
then my system would work correctly.  If I did it from the launcher, it may work for a while, then crash, or not work at all......no idea what the issue was.

The TOS system on my Linux based machines are not as robust nor as reliable as running on Windows, even though it is running inside of a VirtualBox instance on the Ubuntu machine!  However, it does work.  I use it on the LinuxMint node to display some graphs, while on the Ubuntu/VirtualBox/Windows node I do my trading, with a total of 4 monitors - 2 on Ubuntu/VirtualBox/Windows, and 2 on LinuxMint.

Hope this helps!!!

BBQ


Monday, May 12, 2014

Learning Kivy - Part 6

Prev

Table of Contents



  • Learning Kivy - Part 1
  • Learning Kivy - Part 2
  • Learning Kivy - Part 3
  • Learning Kivy - Part 4
  • Learning Kivy - Part 5
  • Learning Kivy - Part 6



  • After a LOT OF WORK, I was finally able to get some code working that incorporates the following:


    • Thread, with a simulation of a Socket.  This writes to a Queue.
    • Main thread - Kivy GUI thread, that reads from the Queue
    • Queues
    Where I've been having issues is:
    • Getting both threads up and running (Thread for Socket simulation, thread for main Kivy GUI), while not causing either thread to block.  Over the years, I've written a lot of Thread software, yet there still issues.  I still don't know what the problem was.
    • Getting both threads to use the same Queue.  For some brain-fart reason, I was creating two (2) Queues, one in each thread, then was surprised that the data I was pushing into the Queue wasn't available to be read on the other Queue!  Clearly a misunderstanding on my part.  I've used Queues before, and knew how they worked, so I don't even have the excuse of ignorance to justify this - it was just a plain brain-fart.  In the code, I create a global variable that has the Queue, which makes it available for each thread.  I'm not saying that's the best approach, but I wasn't trying to research the best approach for Queues, I was trying to get Kivy going.
    • These were the two (2) main problems.

    Here's the code.  It does the following:
    1. Builds a simple Kivy Language BoxLayout (via my ShowGUI class) via the 'Bulder.load_string' command.
    2. Creates a global variable q and assigns Queue instance to it.
    3. Creates an instance of my SimSocket class.  The class has methods that will create some data, then push it onto the Queue.
    4. Creates a Thread named 'simSocket' that links to the callback SimSocket method "put_on_queue".
    5. Starts the 'simSocket' thread.
    6. Runs Kivy.
    Once running, the following takes place:
    1. On the Terminal, initialization messages, followed by comments that say data is being written to the Queue, and shows the data.
    2. A pop-up GUI appears.
    3. Data is read from the queue.
    4. The GUI updates with the  the data that is being pulled from the queue, at a rate of 1/60 of a second.
    5. It continues to run until you stop it, or it reaches 1 million messages.
    ======Python Code Follows=========

    #!/usr/bin/env python
    # -*- coding: utf-8 -*-
    #
    #  threads_and_kivy.py
    #  
    '''threads_and_kivy.py
    Trying to build up a foundation that satisfies the following:
        - has a thread that will implement code that:
            - simulates reads data from a Python socket
            - works on the data
            - puts the data onto a Python Queue
        - has a Kivy mainthread that:
            - via class ShowGUI
                - reads data from the Queue
                - updates a class variable of type StringProperty so it will
                    update the label_text property.
              
    '''

    from threading import Thread
    from Queue import Queue, Empty
    import time


    from kivy.app import App
    from kivy.uix.boxlayout import BoxLayout
    from kivy.properties import StringProperty
    from kivy.lang import Builder
    from kivy.clock import Clock


    kv='''

    :
        Label:
            text: str(root.label_text)
    '''

    Builder.load_string(kv)

    q = Queue()    

            
    class SimSocket():
        global q

        def __init__(self, queue):
            self.q = queue

        def put_on_queue(self):
            print("<----- ..threaded..simsocket.put_on_queue="" entry="" font="">
            for cntr in range(1000000):
                print(".....threaded.....SimSocket.put_on_queue(): Loop " + str(cntr))
                self.some_data = ["SimSocket.put_on_queue(): Data Loop: cntr: " + str(cntr)]
                self.q.put(self.some_data)
            print("..threaded..SimSocket.put_on_queue(): thread ends")

    class ShowGUI(BoxLayout):
        label_text = StringProperty("Initial - not data")
        global q
        
        def __init__(self):
            super(ShowGUI, self).__init__()
            print("ShowGUI.__init__() entry")
            Clock.schedule_interval(self.get_from_queue, 1.0 / 60.0)

        def get_from_queue(self, dt):
            print("---------> ShowGUI.get_from_queue() entry")
            try:
                queue_data = q.get(timeout = 5)
                self.label_text = queue_data[0]
                for qd in queue_data:
                    print("SimKivy.get_from_queue(): got data from queue: " + qd)
            except Empty:
                print("Error - no data received on queue.")
                print("Unschedule Clock's schedule")
                Clock.unschedule(self.get_from_queue)
        
        
    class KivyGui(App):
        def build(self):
            return ShowGUI()
        

    def main():

        global q
        ss = SimSocket(q)
        
        simSocket_thread = Thread(name="simSocket",target=ss.put_on_queue)
        simSocket_thread.start()
        
        
        print("Starting KivyGui().run()")

        KivyGui().run()
        
        
        return 0

    if __name__ == '__main__':

        main()