(Last Updated: May 22, 2020)

Vera firmware update



  • Can anyone remind me the trick to stop Vera nagging me about the firmware 'upgrade' that's available. Apart from the move to OpenLuup 😉

    C



  • ahhh I am trying to remember.... (I nuked my vera and it has become very non vera, much more like a ramips openwrt router)
    I had a script to run on cron to copy the content of the current firmware info file into the firmware latest file.
    I think you are plenty capable of reproducing it:
    The files name is self explanatory and are stored in the /etc/cmh folder. All you need to do is

    cp /etc/cmh/version /etc/cmh/version_latest
    

    and put that in /etc/crontab/* to run every hour or so. Verify the file names too because this is all out of memory.



  • Move to zway + openLuup 😉



  • Cheers!

    C



  • Ok even better:

    this will disable the automated version checking from the vera:
    edit /www/cgi-bin/cmh/get_version
    and add "return" after the bracket of line 24.

    Now you only need to copy the "version" file once.
    This script runs once a day.



  • Your memory is correct 🙂
    ...or very nearly. Actually version_latest 😉

    C



  • Interestingly altering the get-version file seems to throw a bit of a cureveball in terms of not thinking you're logged in.

    C



  • Uhh I think I even hacked that back then... Since I had removed my vera from my account for ages to prevent errant cmh reloads signals sent from their servers, I could never be logged in. So I hacked the webserver to assume that I always am. I am surprised the two would be related though. Let me see how I did this.

    Probably best to stick with the crontab way for now. It is the least intrusive.



  • @CatmanV2 said in Vera firmware update:

    stop Vera nagging me about the firmware 'upgrade'

    So that’s only an issue if you use Vera’s own interface, yes? I really can’t remember the last time I needed to do that, since I always ran (indeed, still run) AltUI as my everyday interface to Vera.



  • @akbooer said in Vera firmware update:

    @CatmanV2 said in Vera firmware update:

    stop Vera nagging me about the firmware 'upgrade'

    So that’s only an issue if you use Vera’s own interface, yes? I really can’t remember the last time I needed to do that, since I always ran (indeed, still run) AltUI as my everyday interface to Vera.

    Force of habit. Fair point, though. Plus the alerts....

    C



  • While looking into SFTPing into my vera I found out that in order to save some minute storage space, they removed SFTP from the vera firmware. You could connect with SSH, SCP but not SFTP. I highlighted this before in the old place but I didn't know how. I just fixed it.
    So basically dropbear lacks an sftp server and this tiny program is fairly easy to add back.:
    You just need to install the openssl-sftp-server package and get it launched right after dropbear at startup.
    I vaguely remember to have forced the webserver to act as if it was logged by editing the /www/cgi/js/interface.js file and changing the value of "this.userAuthenticated" to 1 from !1.



  • OK, cheers. No real panic 🙂

    C



  • There was a script that did that.
    I used it so it wasn't a myth. .

    I've searched for it endlessly but suspect it was removed for reasons unknown.



  • @Black-Cat

    It is more than likely one of my technical posts they deleted without telling me.
    It is this:

    os.execute("cat /etc/cmh/version > /etc/cmh/version_latest")
    

    This needs to be run every day though so you could potentially put in a timer triggered scene instead of my crontab idea.
    There are so many ways to do this... I think this would be the easiest.



  • @rafale77 said in Vera firmware update:

    @Black-Cat

    It is more than likely one of my technical posts they deleted without telling me.
    It is this:

    os.execute("cat /etc/cmh/version > /etc/cmh/version_latest")
    

    This needs to be run every day though so you could potentially put in a timer triggered scene instead of my crontab idea.
    There are so many ways to do this... I think this would be the easiest.

    No it wasn't this one. The one I used was and os.execute, but only needed to be run once. It worked flawlessly until I ran an update. Probably the only thing that did run without constant attention.



  • @Black-Cat

    Then I don't know.
    Another way to make it permanent (until the next upgrade) is to run this:

    os.execute("sed  -i 's/upgradeAvailable=1/upgradeAvailable=0/g' /www/cgi-bin/cmh/get_version.sh|cat /etc/cmh/version > /etc/cmh/version_latest")
    
    


  • @rafale77 said in Vera firmware update:

    @Black-Cat

    Then I don't know.
    Another way to make it permanent (until the next upgrade) is to run this:

    os.execute("sed  -i 's/upgradeAvailable=1/upgradeAvailable=0/g' /www/cgi-bin/cmh/get_version.sh|cat /etc/cmh/version > /etc/cmh/version_latest")
    
    

    That could be it, however, it's a moot point if you have updated to the latest (&Last) FW version.


Log in to reply