That explains why my Plus is now stable again after installing 7.31.
I must say, that 7.31 is extremely fast and responsive so far - just a shame it took so long to be released!
1 Like
I have a Vera Plus and the Beta is working well.
One improvement I reaaallly hope y’all can make - I have a Schlage BE469ZP firmware lock. Whatever you can do to permit scheduling of Pins would be most appreciated. I have an older Schlage as well and the scheduling works SUPER. The second lock with the “ZP” firmware is frustrating.
I finally did the upgrade from 7.29 to 7.31 beta on my Vera Plus.
Everything went well.
The only problem I found is from the support of Fibaro FGS213 (from previous 7.30 firmware): what I saw is that the device changed name (got a “1” added at the end of the name) and I now have a S1 Switch device (that prviously hided) that is actually driving the switch. This is a breaking change (and I think should be stated in the description) because I have all the connections to Home Assistant broken.
From what I have understood the devices have been rediscovered and got a brand new ID.
I am now on BETA 7.31, the only issue I am facing is that all time based scenes are not working at all.
Have you disabled restart on time jumps per the Z wave network explained thread? That will do it
C
That was the issue. Approaching 48 hours with no reloads.
The reason for me wanting to extroot is that my Vera has a massive 8 Mb of data, without extroot it just does nothing. it wont load the app store, i can’t run anything without it rebooting, when i start removing stuff this is when it starts to operate properly
My understanding is that the 7.30 and up firmwares fix that issue with the limitation of storage and makes nearly all of the onboard NAND available.
If you’re struggling to get to that point there’s also @rafale77’s Space script which increases the storage available. (Which is pretty much what’s been implemented in 7.30 and up)
As I say, that’s my understanding, you might want to wait for someone to confirm.
C
Yeah, It was supposed ti with 7.30 but for me it did not so i went back down to 7.29. i did the upgrade and it would even allow the app store to load because of the amount apps i currently had. and scripted scenes would fail mid way.
Most of my scenes and scripted lua rather than using the built in scene controller, and half way through running the scene it would just reboot. I started removing some apps and the system slowly became usable. at that point I figured i would just go back to 7.29
Ooh that’s nasty. Have you tried the space script on its own?
Otherwise I thought that a real donwgrade to 7.29 wasn’t possible. I guess:
Backup
Extroot
Test
and see?
Worst case you should be able to restore to your current situation.
You might want to post the output of df -h just to be sure
C
you can do a full downgrade to 7.29 but it would requite tftp and the firmware bin file
1 Like
Makes some sense.
We’re probably a bit OT here (bearing in mind @Sorin has just updated the forum rules…)
C
1 Like
The upgrade went smooth, I’ve had small issues with re-establishing connection over WiFi - choosing the proper network and entering password didn’t work, I had to put all settings, including channel, password security class, etc., manually.
But I have issues with two Zipato RGBW 2 bulbs (officially supported from firmware 7.30) in my setup. Both are stuck at “please wait, getting secure classes” stage. Both are not reporting their status if turned on or off by another device (wall switch,combined with them via group associations).
I have these bulbs for about a year now, and they had such issues but they were usually cleared overnight. Now they are stuck at this state permanently for last two days.
They can be switched on or off via app or web interface.
I’ve tried to exclude and include again one of these bulbs but with no luck
From the bright side, Heiman CO sensor works better than before (it was separated into two devices, sensor itself and tamper, and needed manually choosing proper json and xml to work, now I see only one integrated device configured properly).
Just a layman jumping in here, but all of my problems come from my Zigbee devices, not Zwave. The backbone of my Zigbee network is a series of Stelpro thermostats. They are all powered devices. As recently as yesterday, I had to remove one and re-add it to the system because it reclassified itself as something else and caused a series of Luup reloads, which of course I only noticed when my Reactor automations wouldn’t fire. I’m going on a few days without ‘unintended’ reloads, but must say that after resetting my ZWave netowrk, that side of the house has been working very well (albeit there are less than 10 devices on it). The zigbee side makes my blood pressure go up.
worked fine now, thanks.
That’s very possible. Just my experience with my setup has been that every problem I have had was caused by the device itself. Not the vera’s support. In your case, it appeared to be the same as well. It appears that your Stelpro thermostat are complex enough that their firmware can go bonkers and start going nuts. The proof of it is that they don’t all behave the same. It is also possible that the vera firmware was not well designed as we all know on the thermostat side and therefore are causing issues regardless of them being zigbee or zwave.
Huh… not quite. Savespace only opens up another storage partition and moves some of the static data which should never be overwritten into it and then creates a symbolic link. Humorously it is practically those same folders which have now been moved into the read only partition of the firmware in 7.31. It really doesn’t open up the full flash storage amount which is still limited to a meager ~8mb. It helps in the sense that it decreases the 5+mb of usage down to ~3mb leaving us with 5mb available to use. Savespace also moved the plugin data from that ~3mb available space into a 50MB storage partition. All this however is ridiculously small compared to what you can do with extroot where you can increase the storage space by 3-4 orders of magnitude. I am running mine on a 50GB which I obviously use less than 1% of but… it leaves a lot of space for wear leveling which the vera does not and will lead to eventual early failure even with SLC NAND which is rated to up to 100X more write cycles vs MLC or TLC. More likely 30-50X given these are Macronix flash.
3 Likes
Thanks for the clarification. Surely the partitioning can be fixed? Messy agreed, but?
C
@rafale77
There are quite a few threads going around about upgrading to Beta firmware and exrooting etc. What is the proper method to upgrade my Plus? I am currently running Firmware 1.7.4453 and my plus is exrooted. Any pointers would be appreciated.
Roger
Hi Roger,
In order to do this, one would have to have another vera, run the upgrade and reimage the virgin upgraded unit firmware back onto the extroot drive. I could fairly easily do this but am on honeymoon for another couple of weeks. I will provide that image and a script for folks to use to upgrade to 7.31 beta while extrooted. Again, as it was the case before, removing the usb drive will bring you back to 7.29 as the new firmware will only be loaded on the external drive.