This morning I upgraded my VeraPlus to V. 1.7.3831
This was the first time everything went well after an upgrade. After the upgrade the memory usage is much more stable.
Looks promising… ;D
Updated my VeraEdge to 1.7.3830 a few days ago. The conversion went smoothly and so far, everything is working well - maybe even a bit better than before. I was concerned about my multiple virtual devices and the MyQ proxy going haywire, but everything is running without a hitch. 
I did have on of my battery sensors (a garage door tilt sensor) not reset after the upgrade, but cycling the door got it back in phase. I’ve had the same issue with prior UI7 firmware versions, so I don’t see this as an upgrade issue.
Melsman
I just updated my Euro VeraPlus from version 1.7.3532 to version 1.7.3831
Had a quick look over the devices and scenes in the UI7 web GUI and visually everything looks to be OK and present. Also checked over the installed plug-ins list which looks to be correct as well.
The firmware of the Z-Wave chip has been updated also from version 4.5 L:1 to version 6.1 L:1
I looked at the storage before and after see screen shots.
Before:
rootfs Used 6.3M - Available 2.3M - 73%
dev/mtdblock7 Used 6.3M - Available 2.3M - 73%
overlayfs:/overlay Used 6.3M - Available 2.3M - 73%
After:
rootfs Used 7.0M - Available 1.7M - 81%
dev/mtdblock7 Used 7.0M - Available 1.7M - 81%
overlayfs:/overlay Used 7.0M - Available 1.7M - 81%
tmpfs went from 1% to 3%
Will have to monitor to see if everything is actually still working OK, but looks good so far.
One thing I am noticing now, is that a new Fibaro FGS-223 double switch relay in the web GUI is showing two plug socket icons.
Its category number is 3 and the sub category is 1
However an older Fibaro FGS211 single relay is showing a light bulb icon.
Its category number is 3 and the sub category is 0
Both of these devices under Advanced are using the following:
Device Type: urn:schemas-upnp-org:device:BinaryLight:1
Device_File: D_BinaryLight1.xml
Device_Json: D_BinaryLight1.json
Not sure what type of icons they were before the update.
The latest firmware made some changes to categories and subcategories. For me, the changes more accurately reflect what is actually connected, especially for plug-in appliance modules. You can change the category and subcategory if you would like the older behavior.
Yeah for some of my appliance plugs and relays I changed their sub category from 0 to 1 and now they are also showing a “plug” icon instead of the light bulb icon. ;D
Since the firmware upgrade my Fibaro Dimmer 2 module is now showing “Can’t detect device” again :o
cw-kid did you manage to resolve that? I have the same with all my Fibraro 3in1 sensors and my front door sensor.
It’s been a problem on and off for a long time with the Fibaro Dimmer 2’s showing the “Can’t detect device” message.
I have other Fibaro relays and none of them have ever shown that message.
On the Dimmer 2 device yesterday in its settings I set “Automatically configure” to NO and so far the message hasn’t come back yet.
Can’t remember if I did that before the firmware upgrade to suppress the message appearing but maybe the update lost that setting.
Should mention I don’t have any battery operated Fibaro sensors only Fibaro Dimmer 2 and Fibaro Relay / RGBW modules on the mains.
I’ve bitten the bullet, and just updated to FW 1.7.3830… Appears that everything went good, except for my door sensors 
I have multiple Ecolink and Schlage door sensors (same model but different brands, some are Z-Wave Plus) they used to work real good, even at relatively far places from the controller. After the update, the door sensors that are far from the controller either fail to report their status or take a long time to report to the controller (LED indicator on the sensor turns on for a long time as opposed to before the updated where it blinks once quickly) also lots of wrong readings. This behavior only happened after the update… All my battery-powered sensors are surrounded by outlet-powered Z-Wave devices that support routing… Anyone facing a similar issue? I wonder if something is wrong with Z-Wave routing for battery-powered devices ?!
[quote=“capjay, post:130, topic:199090”]I’ve bitten the bullet, and just updated to FW 1.7.3830… Appears that everything went good, except for my door sensors
I have multiple Ecolink and Schlage door sensors (same model but different brands, some are Z-Wave Plus) they used to work real good, even at relatively far places from the controller. After the update, the door sensors that are far from the controller either fail to report their status or take a long time to report to the controller (LED indicator on the sensor turns on for a long time as opposed to before the updated where it blinks once quickly) also lots of wrong readings. This behavior only happened after the update… All my battery-powered sensors are surrounded by outlet-powered Z-Wave devices that support routing… Anyone facing a similar issue? I wonder if something is wrong with Z-Wave routing for battery-powered devices ?![/quote]
Wake them up and send the “Configure node right now” command. Fixed the issue for me.
I raised this concern in my open ticket and heard back that the icon change was intentionally done by the developers. I personally liked a Light Bulb for my in wall switches and not the Outlet module looking icon, but it is only cosmetic.
One thing I did notice though was that once you change the subcategory away from 0, you cannot set it back to 0. But I also wouldn’t want to. At least for my GE in wall switches, when they are a Category 3 subcategory 0, they are not included in the ALL ON/OFF button on the main dashboard.
I agree a bulb icon is better for in wall dimmer modules / switches.
But for my appliance plugs and some other relays I prefer the plug icon.
[quote=“cw-kid, post:133, topic:199090”]I agree a bulb icon is better for in wall dimmer modules / switches.
But for my appliance plugs and some other relays I prefer the plug icon.[/quote]
Couldn’t agree more. I suggested that Vera add an additional sub category to bring the light bulb as an icon into the selection. The response was that if I switched the subcategory to 4, it shows as a light bulb. To which my response was “Yes it does, but this is the “Refrigerator” category and again, would not participate in the ALL ON/OFF button on the dashboard.”
If you want to have it on the web interface, you just need to create a specific JSON file.
It will probably keep to have a switch icon in the mobile apps anyway.
Just an FYI that on my VeraPlus, this latest update sets your Net & Wifi setting to ?Automatically Configure?, and turns your Wifi radio on and broadcasting the ?MIOSxxdevicexxx? ssid. Believe this was also true in a recent, earlier update.
FWIW, I do not think it is good practice to turn on Vera?s Wifi without explicit user consent, hopefully the MCV folks can fix that asap. >:(
Rest of the update uneventful, except I had to reboot Vera via SSH after she became unresponsive - web ui hanging) during firmware update. This is typical, in my experience.
Onward.
.//A.
+1 - I have to turn this off after every update. Granted with the right tools, you could find the wireless, but it would slow the novice people/neighbors down.
+1 - I have to turn this off after every update. Granted with the right tools, you could find the wireless, but it would slow the novice people/neighbors down.[/quote]
My wifi was off before the upgrade. Just upgraded to 1.7.3831 and it did not turn it on.
The upgrade took about 7 minutes and the only issue I see so far is an Aeon light switch shows as a plug icon.
I had a lot of FortrezZ relays fail after the update as well as my Denon AVR Plugin and for a while the Harmony Hub Plugin too. This after having support perform the update due to self installs bricking my unit last update and having to spend 4 hours on a tech support call with the agent from Romania in a remote session on my laptop and a ssh session from there into my VeraPlus to get it going. I do not appreciate that at all.
Hello capjay,
I sent you an email, in case you would need assistance please reply.
Thank you!