Well after reading some more of the notes here I tried a “configure the device now” command in advanced on my door and motion sensor and surprise surprise - the motion sensor configured. The door sensor also configured - but as a generic - I then modified the parent device for it as a motion sensor with anti-tamper per the manufacturers instructions and reconfigured it again - and now the extra child devices are gone and the parent devices for these sensors are setup and I can arm and disarm them. I still don’t know if they will -work- and if the tampering notifications are gone but we’ll see.
These are BeSense sensors. Perhaps they were added to the list!
That’s funny! Added to my joke file! BTW you forgot “dig out Support’s 800 number hours of operation” and “Stop at Dollar General and stock up on Jolt Cola”
Lots of people who encountered “Out of Space” issues were told by Customer Support over the years to remove extraneous files from their Vera units, using the following steps, to be executed one at a time in Apps > Develop Apps > Test Luup code:
I’m certain others will chime in with their favorite additions to this “bloatware removal” list. (Running the above on my Vera Plus got my ‘rootfs’ folder down from 93% usage to a saner 73%!)
UPDATE – IT GETS EVEN BETTER!
Following today’s upgrade of my Vera Plus unit to the new 7.0.31 firmware, its ‘rootfs’ usage again dropped dramatically, to 16%!
root@MiOS_50001183:~# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 10.6M 1.7M 8.9M 16% /
I spoke too soon. It seems my binary sensors (both wired and wireless) are missing updates, resulting in false alarms for doors/windows/gates/alarm left open (or closed) when not. Anyone else with these kind of problems?
Occasional motion sensor updates for me. When I’ve been able to get to my Vera fast enough after I notice it to see the logs, it appears @rafale77 's much discussed (and deservedly derided) post-CAN deafness may be related. This isn’t new, though; it’s been this way for years.
Sorry guys, but I think a forum is to share experiences and I want to share mine. I am a noobie, I like tech stuff as probably all of you and like to discover new things. I began with Vera Lite and then went to Vera Plus. I try to read more than I write and learned a lot from you. I never use beta software for a reason.
And some days ago I upgraded my Vera Plus from last stable (7.0.29) to this new one (7.0.31) as I saw reports of successful instalations. So, I thought I would not have any problem. I only had 4 plug ins, which only two were in use. I do have a lot of devices (I believe no more than 60), mostly lights and outlets.
But after doing the upgrade process, I waited for 65 minutes until I decided to unplug it and plug it back as the screen didn’t change after the upgrade process. Right before, only the power light was on. I had faith after doing the unplug/plug back my VeraPlus would come back. But it didn’t.
I contacted support. No response. Than, after @Sorin gave a little help, someone contact me and offered some advice about pressing the reset button 3 times. If it didn’t work, to schedule a phone meeting. Well, it didn’t work and I asked for the phone meeting to be the next day. as I really need my VeraPlus back on order. Nothing, not even a reply saying that would not be possible. I wrote again asking for tomorrow. Let’s see. Anyway, I may have a bricked VeraPlus now. There is no way, at my present knowledge, I can access the unit. I even pressed the reset button and then plugged it, but only to get all lights on and power light blinking and nothing else.
I am very worried and scared. Really. Is this the type of support a customer deserves? Maybe they are overwhelmed with so many assistances from this last update, I don’t know. But I can’t help feeling I am alone.
Really disappointed…
Does anyone know anything about bringing VeraPlus back when it only has the power light on? I really hope someone can help me…
Updated my VeraPlus. Positive experience. All seems to work including the Hue2 app. PLEG fired the laundry light to turn on when motion was detected, etc.
I had a fairly clean and stable unit. So I backup up the unit, went to the firmware screen, and selected update, since I did not have any memory issues.
After about 16 minutes of updating and the Vera not telling me it was done, I looked at the unit and the power light was flashing. So I unplugged and replugged in the Vera.
I noticed a solid power light, then the Internet light. After a few minutes a solid power light - perhaps it rebooted. Then the Internet light. Another couple of minutes, solid power light, then internet light, then z-wave and ZigBee lights. Went to the UI, and it seems to be working fine.
I reset my LUUP startup counter to see if I get less than 1 or 2 restarts a day.
I really think the secret to my success - I brought out my Relaxing Lavender candle this morning. The wife was thankful. Perhaps the Vera was thankful as well
It indeed seems to be akin to that. It is seemingly random and can be vary a lot in frequency and intensity… And the more I think about it the more I am floored by how they managed to get away with such an absurd design for so many years and apparently have had patches and patches building code working around this thing instead of addressing it. I digress. Smoke is coming off of my head. Sorry
For those who want to be sure not to have the “device reconfiguration surprise” for devices which have been recently “officially supported” run a backup, run this code in the lua test screen:
for k, v in pairs(luup.devices) do
if v.device_num_parent == 1 then
luup.variable_set("urn:micasaverde-com:serviceId:HaDevice1", "AutoConfigure", "0", k)
end
end
Reload luup, Run another backup before the upgrade. It should prevent the vera from reconfiguring your devices post upgrade. There are a lot of new devices supported between 7.29 and 7.31. It should alleviate problems with these previously working devices.
Another recommendation is to run upgrades with a factory reset and restore from your backup. It should make things cleaner.
I must confess that I’m not seeing a huge incentive to upgrade. That my be limited on my part, but I see none of the issues (*) and don’t seem to need any of the benefits.
C
(*) Issues I have are limited to slow response on the network and Alexa commands not getting to Vera
I may have spoken too soon. Although it seems stable (not much going around the house to really test things), I am noticing a number of Vera Reboot notifications from Pushover. And it is reported as 2 reboots within 1 minute, but System Monitor reports 1 reboot and 1 restart. I suppose that is a away to reduce LUUP restarts. Since the update at 3:45, 7 Reboots as of 5:08.
I’ll give it a little more time to settle down before I open a ticket with support - maybe this weekend unless a real workout tonight and in the morning really impacts the WAF.
These are the steps that I have performed
• backup
• factory reset
• update the empty unit
• restore from backup
After upgrade to 7.31 all zwave devices have disappeared! My RFXCOM devices are visible and working correctly. Who can help me to get all my devices back? I also sent an email to support.
I’ve raised everything you posted here to the technical team to be included in the scope for the 7.32 release.
If there are other minor items that were reported/requested and are not yet solved please ping me (PM or in this post) to make sure I’ll bring them into discussion.
