Installed on my Vera3 system that I use as a development sandbox. Bricked. Flashing orange/green. Off to boot my old XP laptop!
EDIT: Before hitting it with the big bat, I tried two full power-off resets. On the second, it came back up. Whew!
ran the upgrade too as I somehow got my 7.0.26 suddenly corrupted by editing a scene and ended up having to do a factory reset… I have not observed any changes.
Managed to install it on VerLite after manually making sufficient flash space available. If there is not sufficient space it quietly fails to do anything.
Seems to be running fine still.
Cheers Rene
I upgraded on of my Plus’es. Controller needed manual reboot after upgrading (it was stuck with BT/Z-wave/Zigbee lights off), except that everything is fine.
I have an impression that it is a little faster, (at least some scene triggered by remote controller seem to react faster than before) but it might be temporary.
I didn’t notice any significant change in storage memory or RAM after upgrading
Day 5 with this firmware on my Vera3. So far, no functional problems, but, I am now noticing two UI oddities, and these occur on both Firefox and Chrome, so I don’t think it’s a browser issue:
-
Very frequently, the dashboard device display mixes up the icons for devices, and multiple devices will get the icon of some other device; occasionally, a default icon will be assigned to a device. A short time later, the problem rights itself, and then some time after that, the problem repeats itself. Once this begins, it is not a steady state, right or wrong;
-
With alarming frequency, clicking the “Advanced” tab will display the data for a completely different device from the one you are in. There is no warning of this, and no rhythm to it.
In both cases, browser refreshes and Luup reloads do not consistently solve the problem. In fact, the problem seems to occur most often after a Luup reload with a non-refreshed browser (that is, Luup reloads but you don’t do a refresh after, which is common because you never really know when Luup is going to reload on its own).
@Sorin, I think this is something you guys need to look into before releasing.
I’m seeing this in the latest non-beta release, at least to some degree. Many times a device name will change after visiting the Advanced section. The names are like “Zigbee Network”. Very odd. So, this may have started partially in the last stable version.
EDIT: I’m now seeing icons change, too. My thermostat shows as a camera, etc.
This latest firmware broke support for the Jasco 45602W dimmers. Some zwave communications from the vera seem to eventually make the dimmer unresponsive and hang.
[quote=“rigpapa, post:5, topic:199365”]Day 5 with this firmware on my Vera3. So far, no functional problems, but, I am now noticing two UI oddities, and these occur on both Firefox and Chrome, so I don’t think it’s a browser issue:
-
Very frequently, the dashboard device display mixes up the icons for devices, and multiple devices will get the icon of some other device; occasionally, a default icon will be assigned to a device. A short time later, the problem rights itself, and then some time after that, the problem repeats itself. Once this begins, it is not a steady state, right or wrong;
-
With alarming frequency, clicking the “Advanced” tab will display the data for a completely different device from the one you are in. There is no warning of this, and no rhythm to it.
In both cases, browser refreshes and Luup reloads do not consistently solve the problem. In fact, the problem seems to occur most often after a Luup reload with a non-refreshed browser (that is, Luup reloads but you don’t do a refresh after, which is common because you never really know when Luup is going to reload on its own).
@Sorin, I think this is something you guys need to look into before releasing.[/quote]
Thanks, rigpapa, giving a heads up to the team as we speak. However, if you have ongoing trouble with your setup, I advise logging a ticket with our Customer Care team as well.
OK. Child devices seem to be the culprit here. Now that I’m digging into it more, I’m seeing some of the same thing on my Plus with 3232… if I click on a child device, it gives me the attributes of a completely different (non-child) device. If I refresh the browser, I can get it work once, but then it goes off the deep end again. I’ve been able to reproduce this with the built-in support for Aeotec Multisensor 6 (creates child devices for temperature, humidity, etc.), as well as various plugins that create children (Sonos, HTD, and my own).
I don’t have such issues with child devices (Vera Plus)
@Nameless reported similar issues after instaling your Reactor plugin (though he blamed Vera’s UI, later mentioning that uninstalling the plugin cured the issue).
Maybe this is not related to beta but to your plugin somehow?
Indeec. I’m hoping he’ll confirm his issues have abated, but I haven’t heard. Tnis seems to rsolve the issues with the Advanced tab. It has not resolved the issue of the icons changing, howver.
[quote=“rigpapa”]Indeec. I’m hoping he’ll confirm his issues have abated, but I haven’t heard. Tnis seems to rsolve the issues with the Advanced tab. It has not resolved the issue of the icons changing, howver.[/quote]I haven’t had much time to research, but can say I am not having the problems after removing the plugin. I am not on the Beta firmware, just the standard version.
I plan to further test the plugin when I have some free time.
Icon problems have gone away for me, so there may be a correlation existing with the Beta firmware, but I cannot confirm.
Sent from my LGUS992 using Tapatalk
I don’t have icon problems on beta, but I don’t look much at UI recently, and I don’t have much devices on the controller where beta is installed.
@Sorin, it looks like the UI trouble was caused by an error on my part in the JavaScript tab for a plugin. I was sorting the array returned by api.getListOfDevices(), assuming it would already be a clone of the UI’s official list, but it’s clear that it’s actually a reference and sorting that list disrupts the UI’s expected order of things. Wrapping it in api.cloneObject() easily fixes that issue.
Sorry for raising a false alarm.
will qubion ZMNHXD1 be supported in the next version ??
Any word on this? Could you pair Qubino ZMNHXD1 using wizard for ZMNHTD1 and then modify parameters?