Thanks for your help Rafale77.
I did a restore but… no real effect : those 2 fibaro devices are “on” again, but temperature and luminosity aren’t back… Shit !!!
You will need to reconfigure the device unfortunately.
It isn’t on the manual but this autoconfiguration is really a plague on the vera.
The mechanism is that if you had it setup before and that the new firmware suddenly added official support for this particular device, and you have auto configuration turned on, it will deem the device as unconfigured and will want to reconfigure it from scratch during the luup engine loading, wiping out your data in the process. While the intention is good, the real life application is stupid. It assumes itself to be smarter than the user which is arrogant of the devs and annoying. It is treating the user data as if they could manipulate it at will without user inputs. The result is that it breaks things which were working perfectly fine, attempting and failing to do things the users have done successfully (configuring the device). This is over automation of the configuration and something I have requested them to stop without much success. It goes in the same bucket as the auto deletion of device and scenes, the spamming prompts for firmware upgrades and the virus like insertion of unwanted plugins, making the whole platform less stable and less user friendly.
The workaround is to disable all auto configuration flags on your devices once you have them configured.
I understand your explanations but the auto configuration is already disabled (I follow your recommendations, tips and tricks for a long time).
And this doesn’t explain why a very simple scene (at the moment, only one scene) refuse to execute even if I delete and re-create it…
Well this is weird indeed but I don’t think there was any change in the scene area of this firmware. What messages are you getting back when you try to execute it? By any chance, is it a timer based scene?
When I manually execute the scene, it does.
This scene should execute every day (except two days) at a certain time.
I could exclude and include my missing devices again (lot of work for that as I would have to rewrite scenes they are used in), but if the result is the same as deleting and re-creating a scene without success…
Ok. So it is because you likely ran the disabling of luup reload on time jump code. This disables the timer based scenes. Enable it again and these scenes will start running.
To do that rerun the code like this:
luup.attr_set("ReloadOnTimeJumps",1,0)
and reload luup
Done. I’ll see tomorrow morning if the scene run.
But wait… I just looked into luup files and… wow, what are all those files I never download or install ? It seems that all luup files have been downloaded ???
Not sure which files you are referring to. A very large number of luup files are native to the firmware and are supporting your devices. Some are from plugins. This firmware added a bunch of “virus” plugins which are hard to get rid of. Even if you delete them from the plugin page, the files will still be on your vera until you manually delete them.
If i give you access to my computer (team viewer), could you have a look ?
I have to go to work now. So let’s talk of that later.
To be fair, you can finally blacklist them. Just ho to app, uninstall and you should be good.
True except for one which I had to use ALTUI to uninstall. Point being that I feel like I am (was) constantly chasing fixes and as we were getting some, some other new unrelated junk kept coming in. We had some stability problems and improvement came with 7.0.29 but they added forced plugin installations, 2 versions later we have blacklist, (instead of reverting the nonsensical behavior) now at the same time they blocked extroot. I found a workaround and… who knows what they’ll do next. I am just so happy to be done with with this time pit.
A screenshot of what you see will do or even a copy paste of the files you have concerns about. A bit overkill to use team viewer for this.
If you guys are using different email addresses on the forum, other than the tickets you’ve logged, please let me known in private the ticket numbers, otherwise we’re gonna find them.
Just got a response from customer support. Thanks @Sorin! Of course, I now understand why people complain about the customer service. They had the gall to state this:
It is expected for some devices to turn unresponsive or some minor issues to appear after a firmware upgrade
as well as implying that doing a restore from backup should be a standard operating procedure. Wow. Just…wow. In my world, firmware upgrades are “expected to fix minor issues and improve responsiveness of some devices” (not the opposite), and restores from backups are for disaster scenarios, not standard upgrades. Oh well, I’m sure we’ll get this resolved - off to do a restore of my unit!
1 Like
The Customer Care team are there to help by any means they have, giving this specific scenario. But the possible firmware issues are a different matter and it’s not on their plate. The product team is aware of this matter and I hope lessons are learned.
Indeed, and in general I’m quite happy with the work you guys are doing. I have what I would consider a fairly expansive setup with many dozens of devices, plugins, and scenes, and things have been working quite well up till now. I also understand that bugs happen (I’m a developer myself, and can’t claim to have released anything bug-free), so it doesn’t bother me that there were issues with this release - I assume they will be fixed, and life goes on. It was just that response of “this is expected” that was a bit off-putting to me 
2 Likes
[quote=I just upgraded my Vera Edge from 1.7.3500 to 1.7.4969 (7.31 incl hotfix). Before I did the upgrade I have set all my devices to autoconfigure = OFF using your code.
All went fine! I did some checks and everything seems to be working.
[/quote]
So in my case the upgrade went very good. But please take into account that it concerns a Vera Edge where I installed recently 31 zwave nodes and these plugins: Reactor, Switchboard, Housemode and AltHue (next to the annoying plugins that are preinstalled by Vera Sercomm camera, Apexis camera, Ezlo camera, Amazon Alexa and Google Home…)
Also I did all my automations so far in Reactor.
So no old plugins and no scenes had to be transformed to the new firmaware.
I notice someting very odd though: at all the child devices I suddenly cannot change the room anymore in the usual way. This field just dissappeared ??? I only can change room now via advanced → params and enter the room number here in the field room (after checking the correct room number that vera has assigned). This is applicable for all the zwave devices, not for child devices created by plugins.
So not very user friendly and again workarounds needed
I also hope lessons are learned and also from the learned lessons.
Can someone point to the code for disabling autoconfig on existing devices in bulk? Couldn’t find it via a few different searches.