Vera firmware 7.32 beta
-
I’m running it since the first alpha. Never been so happy.
To be honest, I asked for a couple of things to be fixed and they did. Specifically, I had problems with mongoose crashing and now I’m at 5-6 days of luup uptime. I still have a load of virtual devices and most of the lua logic running on my Vera (now plus, edge before). They also changed the disk partition and I must say it’s really night and day.
I’m running decoupled and all is good, so I could just improve my setup with others systems.
@therealdb, so you first did recouple, then upgrade and decouple again? I'm also running decouple by @toggledbits and liking it a lot.
Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT
-
@therealdb, so you first did recouple, then upgrade and decouple again? I'm also running decouple by @toggledbits and liking it a lot.
@tunnus I've update various builds while decoupled, it'll work. after the update, you'll need to decouple again. it's probably better to just recouple, update and then decouple again, because after each update the apps will need to get restored from the app store. I'm working on completely remove them (and copy the files by hand, when needed) to further improve my setup and completely avoid anything from their cloud just in case they'll eventually turn it off/remove something. My system has never been so stable, partially thanks to no unneeded services running in the background, and the updated they did to all the components. It's really a huge release and it's a shame they took almost 6 months to release it, but I'm starting to think it's all calculated. But I digress.
tl;dr; go for it, it's better than 7.31 even if in beta
-
Is it only when you edit a scene the sunrise/sunset bug appears or are all scenes containing that trigger affected regardless of editing?
@crille only on edit, or fw upgrade. I’ll probably just remove them and move to my own engine for that too.
--
On a mission to automate everything. -
I have been waiting for 7.32 to try out @therealdb 's alexa plugin to finally use Alexa in multiple rooms for synced TTS. WIll install fingers crossed it goes well!
-
I am heartened to see the pivot MCV had made, back on the old Foum, with regard to corporate responsiveness. Never expected to see staff answering questions, trouble tickets being written up quickly, much less talk of a new firmware for <gasp> Vera!
Then again, I'll believe it once it leaves beta... something I've never seen an ezlo product yet achieve.
-
I have been waiting for 7.32 to try out @therealdb 's alexa plugin to finally use Alexa in multiple rooms for synced TTS. WIll install fingers crossed it goes well!
@pabla said in Vera firmware 7.32 beta:
I have been waiting for 7.32 to try out @therealdb 's alexa plugin to finally use Alexa in multiple rooms for synced TTS. WIll install fingers crossed it goes well!
Works A1 on Openluup
C
-
I have been waiting for 7.32 to try out @therealdb 's alexa plugin to finally use Alexa in multiple rooms for synced TTS. WIll install fingers crossed it goes well!
-
@crille only on edit, or fw upgrade. I’ll probably just remove them and move to my own engine for that too.
@therealdb Ok, thank you. I’ll wait till that one is squished then.
-
Classic...
For one minute I was thinking of testing it for kicks. well...
I have no idea why it is trying to reconfigure every device. There is no situation where this should ever be automated unless the database is wiped and even then it should be trying to get configurations from the devices, not configuring them. The logic is just broken. Vera at its best.
-
Too bad Pabla and Crille (and I plus a dozen others) can't participate on the MCV forum where feedback like that would be invaluable. Are you both still on their Jira bug tracker, though?
-
Classic...
For one minute I was thinking of testing it for kicks. well...
I have no idea why it is trying to reconfigure every device. There is no situation where this should ever be automated unless the database is wiped and even then it should be trying to get configurations from the devices, not configuring them. The logic is just broken. Vera at its best.
-
@rafale77 its all the same Zooz devices having this issue, weirdly this is the variable thats not configuring. Every time I try to delete it or set it to 0 after a reload it comes back. I have never even set this device config before either
@pabla ... sigh. Sorry to see this. Though I am glad to never have to deal with this type of nonsense anymore, I am saddened by the absurdity of the vera device management. I suppose you see this problem at every luup reload then? The vera has hardcoded in its firmware that it is expected to see this configuration parameter for this device it recognized. The problem is that it is likely wrong. Thus the absurdity of the whole "device support list". They should just be supporting zwave by supporting all the command classes and representing them accordingly and stop trying to be smarter than the users. Worst case, if it is a very unusual device, let the user community create the virtual devices for them like hubitat does. Oh well enough of my ranting. There isn't an easy way I know of to get rid of this besides "hacking" the device registry file in the vera, which I have done in the past... This is hardcoded stupidity.
-
There’s now a new flag to avoid children recreation. I’ve applied it and my system is rock solid. I updated 3-4 times for the beta. They even decoupled the engine and it’s updatable via opkg. can’t say Edward and his team aren’t working to improve things, but there are fundamental flaws for sure.
All that said, my system is quite perfect since the first build of this beta.
--
On a mission to automate everything.
