The link in the first post is not longer valid:
I found a new link - maybe the fw is released now?
https://dl.mios.com/firmware/mt7621/mios/release/mt7621_Luup_ui7-1.7.5364-en-mios.squashfs
The link in the first post is not longer valid:
I found a new link - maybe the fw is released now?
https://dl.mios.com/firmware/mt7621/mios/release/mt7621_Luup_ui7-1.7.5364-en-mios.squashfs
Curious to know how you “found” such a link? lol
I’ve gotta say 7.32 (beta) has been rock solid for me this past month, so I’ll happily jump on board the official release.
Once @Oscar.Morales , @Sorin et al say it’s official.
As I discovered the broken beta link, I just followed the logic from previous official fw links and it works…
7.32 is installed on 2 machines without problems. Even when you reset to factory settings, the 7.32 is installed.
The links for the download at the top don’t work
i.e. [broken link removed]
Hello,
We’ve released a new beta version.
UI7 - Vera Firmware Update (Open Beta 2)
Firmware versions:
VeraEdge: [deprecated link]
VeraPlus: [deprecated link]
VeraSecure: [deprecated link]
Fixes:
@edward Noticed on Edge (5372), install with factory reset:
lrwxrwxrwx 1 110 1003 26 Apr 21 12:09 K95-mios_fix_time -> ../init.d/mios_fix_time.sh
lrwxrwxrwx 1 root root 26 Apr 21 12:12 K95-mios_fix_time.sh -> ../init.d/mios_fix_time.sh
lrwxrwxrwx 1 110 1003 26 Apr 21 12:09 S021-platform_init -> ../init.d/platform_init.sh
lrwxrwxrwx 1 root root 26 Apr 21 12:12 S021-platform_init.sh -> ../init.d/platform_init.sh
lrwxrwxrwx 1 110 1003 27 Apr 21 12:09 S03-backup-restore -> ../init.d/backup-restore.sh
lrwxrwxrwx 1 root root 27 Apr 21 12:12 S03-backup-restore.sh -> ../init.d/backup-restore.sh
lrwxrwxrwx 1 110 1003 26 Apr 21 12:09 S115-mios_fix_time -> ../init.d/mios_fix_time.sh
lrwxrwxrwx 1 root root 26 Apr 21 12:12 S115-mios_fix_time.sh -> ../init.d/mios_fix_time.sh
lrwxrwxrwx 1 110 1003 30 Apr 21 12:09 S47-backup-restore-nc -> ../init.d/backup-restore-nc.sh
lrwxrwxrwx 1 root root 30 Apr 21 12:12 S47-backup-restore-nc.sh -> ../init.d/backup-restore-nc.sh
lrwxrwxrwx 1 110 1003 27 Apr 21 12:09 S480-provision_vera -> ../init.d/provision_vera.sh
lrwxrwxrwx 1 root root 27 Apr 21 12:12 S480-provision_vera.sh -> ../init.d/provision_vera.sh
In light of this revelation, am now adopting an even stricter “wait and see, and then wait some more” stance on installing beta (really, any) firmware onto daily driver Vera.
I’ve updated to the latest beta and it’s working ok for me, but I’m decoupled and I’ve removed the scripts mentioned by @rigpapa anyway. I’ll report back in case of errors.
is only the “Edge” affected?
Edge and Plus versions are affected.
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
@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.
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.
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 …
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules