Any news on the progress?
Hello,
We’ve released a new beta version.
UI7 - Vera Firmware Update (Open Beta 3)
Firmware versions:
Vera Edge: [deprecated link]
Vera Plus: [deprecated link]
Vera Secure: [deprecated link]
Fixes:
Fixed the issue with duplicate init scripts
2 Likes
@edward Indeed the multiple init scripts issue seems to be fixed. The mios_fix_time script is still linked (at least, on Edge).
To recap on that, this script relies on a mechanism that isn’t implemented properly on Plus or Edge, so it malfunctions on these platforms and its effect on “fixing” time during a restart without Internet is actually worse than what OpenWrt itself does in its own script that runs earlier (so fix_mios_time is even undoing something more useful). Either the mechanism needs to be made to work properly on these platforms, or the script should be removed/unlinked entirely.
1 Like
I intend to wait on installing any further revisions of 7.32b until this and any other long-known issues get worked out. Thanks again for the heads up.
@edward I think I found an additional issue new to these two Beta releases…
The problem is that arming/disarming of Door Sensors, specifically, is not performing as expected when changing house modes. Motion sensors work as before, it only seems to be Door Sensors with a behavior change. Consider the following configuration:
In this configuration, Virtual Motion will arm when the house mode is changed to Away or Vacation, as expected, and will disarm when the mode is Home or Night, again as expected.
Virtual Door 1 and 2, however, become ARMED in all house modes other than Home. No changes to the configuration in “My Modes” or the ModeSettings state variable repairs this. So even in house modes where the device is set to be disarmed, it becomes armed. Based on the configuration above, I would expect “Virtual Door 1” to arm identically to “Virtual Motion” (armed only in Away and Vacation modes), and “Virtual Door 2” to never arm in any mode. But this is not the case.
This is reproducible as shown (tested on Edge), and applies to both this latest Beta build and the prior one. It looks like something changed between 5350 and these Betas.
4 Likes
Hi
yesterday I wanted to add my first zigbee device to VeraPlus v7.31 but nothing worked, Bitron video AV2010 / 25 in generic zigbee.
Are you having kind of problem with this version?
She looked for the device without finding it while the ezloplus found it without any problem …
I have 2 Securifi ZigBee sensors, which were working on my previous 7.31 Vera Plus. I could not get them to pair on new box, but have not investigated yet whether that was due to replacing the plus or upgrading to 7.32 open beta.
Octo
Vera hubs never worked properly with Zigbee devices, it was always hit and miss.
2 Likes
did this fix the google home issue?
Good question I’d forgot about this.
Can anyone confirm?
It wasn’t working last time I tried it, should test it again I guess.
I just updated my lab Vera Edge to version 1.7.5379.
However I cannot select / tick any devices from my Vera Edge to expose to Google Home because of this new problem here “You cannot select more than 300 devices”. I have 80 devices and scenes currently selected not 300 so its a bug.
Its one thing after another with Vera 
And they still haven’t fixed the voice assistant portal pages as described here and here.
And on going issues with Alexa and “Device is unresponsive” here.
@melih who is in charge of the voice assistant portal web pages ? Things are very broken now !
I’ve deleted some devices off my lab Vera Edge to get me below this 300 “devices” limit bug.
I then tried to select just one device from my lab Vera Edge to expose that device to Google Home etc.
First attempt I got this after pressing the Save button
I then refreshed the web page and tried to save again and the second time it seemed to work.
I then asked Google Home to “update devices” and my new device from the Vera Edge was added in to the Google Home app.
I then found this “Test Bulb” in the Google Home app and it does seem to be working now, I can turn it on and off OK, either via the Google Home app or via a voice command.
It no longer says “Not Responding” for this device in the Google Home app like it did when I tested this previously on the last 7.32 firmware version.
So tentatively I am going to say they have fixed it.
However there remains many problems all round with voice assistants and Vera and Ezlo firmware hubs as I just stated in the post above and I don’t know about you guys but I am fed up with it.
Here is the Jira ticket for the voice assistants portal pages mess:
https://jira.mios.com/servicedesk/customer/portal/72/ECS-420
Can we have an update on this please ???
Another bug here for Ezlo hubs and Alexa, just tested it again and its still not fixed.
Jira ticket for it here:
https://jira.mios.com/servicedesk/customer/portal/72/ECS-419
1 Like
Is a third beta version available for trial at this time and is there a revised timeline for go-live at this time?
Thanks much
3 Likes
Would be nice to see some feedback from the project management team on the status of this release.
Agreed. It’s been stone silent around here lately.
Hi!
Not any of the links to beta versions works. Is there any new versions in the horizon?