I get your point Peter, not arguing with your guidance.
The problem I'm having is that the GW did exclude the device properly, not a single problem.
The device I excluded was a Vitrum 3-way dimmodule, included in a Vera system. The Vera system is no longer wanted by the client and they wanted everything included in the Fibaro system wich was running the screens.
This client wasn't mine from the start, so I couldn't have updated the system any sooner, but the system was still running on 3.560.
In order to be able to include the Vitrum modules, the system needed to be above 4.0. I've tested the exclusion and inclusion on my own testsystem which is running on 4.150 and there were no issues at all.
With this in mind I was pretty confidend that this switching of systems would be an easy task.
When accessing the system and finding out is was still running on 3.560 I was a bit sceptical that the task would be even possible, knowing that trying to update from 3.560 to 4.xxx has had many different problems in the past such as removing your entire devicelist...
Still needing to update I started with the update-proces.
After the update-proces was completed to 4.0x I checked the existing devicelist in order to see if everything was still there, no problems detected.
Then I updated to the last stable version (4.150) and tried to exclude 1 device with the Fibaro GW, because I didn't have the proper login credentials for the Vera.
no propblems so far.
After the succesful exclusion I then tried to include the device in the Fibaro GW, and thats when the probles started.
The first time I tried to include, the system stuck on the inclusion-screen. No way this ended properly, not even after 5 minutes.
Force stopped the inclusion process and removed the device using the exclusion-proces. No harm done.
After that I tried to re-include the device, only to find out that after pushing the inclusion button the topscreen said LEARNING MODE error, please try again.
Rebooting doesn't seem to help, going to ask the client tomorrow to unplug the GW for at least 1 hour, maybe the system hangs on the z-wave chip trying to rebuild the network.
Will keep you informed.
With kind regards,
René van Meulenbroek
ReMi ProduXions