Since you’re starting out with this, start using the edge drivers, which is what’s going to exist in the near future.
Edge drivers are controllers that are used to manage the devices that are installed in the hub.
The driver has to be installed on your hub from a web channel where the drivers are stored.
There are several channels, there is the official smartthings and many more. Each user or developer can create and share their channel with other users.
To enroll your hub in an edge driver channel you have to enter the invitation link to the channel and accept use it and press enroll for access to drivers.
Once hub enrolled you will see all the drivers available in the channel. Install only the drivers you are going to use on your hub.
Once the driver is installed on your hub, you can add the device from the app with the option to search for nearby devices.
Open this link to the post where it is explained which fibaro Z-wave drivers are available on my shared channel.
At the end of post you will find the invitation link to the channel so you can install the Z-wave Window Treatment Mc driver
This the link to smartthings tutorial for Edge drivers
I’m still having issues connecting to Smartthings. I have accepted the invation and added the Z-wave Window Treatment Mc driver and then done a scan to search for nearby devices and nothing shows up.
Let me mention the set up I have inherited and maybe that will help identify potential issues. There are 4 windows and each window has been set up with Fibaro FGR 222 units attached to Dooya motors. I have opened up one switch unit and can see the FGR 222 unit wired in, but not connected to S1 or S2, I’m not sure if this matters. I will have to open the others and see how they are wired. My Assumption that all four are somehow linked and only once connection is to be made to one of the FGR units. However this is a totally guesss from me, with not much knowledge on this.
Can you think of anything else as to why I cant seem to add the unit(s) to smartthing?
Device Type Handlers written in the Groovy programming language are part of the old architecture. They are still available but due to be discontinued at the end of September. So at this point it’s best to just start with the new architecture, Edge Drivers, as @Mariano_Colmenarejo suggested.
If you want to read more details about this transition, see the community FAQ:
As far as your current issue, it’s very likely that you need to clear out the old network information from each device before it will accept being added to a new hub. In zwave, this process is called “exclusion.” It is different from just “resetting” the device. If you don’t have access to the original hub, that’s fine: zwave has a special utility called “general exclusion” which allows ANY certified zwave hub to issue an exclusion command to ANY certified zwave device even if they were never on the same network before.
It is likely that your new ST hub can’t find your Fibaro devices because your Fibaro devices think they still belong to their old network, so they are not responding to the scan. Only devices that are available to join a new network show up in the scan list. A general exclusion will clear out the old network information, so then the device should show up in the scan as available.
I am tired today so I will leave it to others to help you with the details. But your next step should be to issue a “general exclusion” to each of your Fibaro devices to get them ready to join a new network.
Many zwave device manufacturers use “reset” to mean “reset all the optional parameter settings to their default values” but NOT to “clear the old network information.”
This is probably because, according to the Zwave Alliance, over half of zwave devices are professionally installed.
Individual customers are allowed to reset all the optional parameters like dim rate on a light switch, but the manufacturer didn’t want them to accidentally change the network settings the professional installer had set up. So those are handled with a different set of utilities, in this case general exclusion.
Also, as a network function, exclusion requires having both the hub and the end device do something at the same time. Any “reset” instruction for a zwave device which only talks about doing something with the end device and doesn’t also mention having the hub do something is not doing an exclusion.
Zwave is very different from Zigbee in this regard.
With your kind and very informative advice I have managed to now exclude the Fibara Roller Shutters (FGR 222) from Z Wave and have successfully adding them to my hub.
Both your advice, help and links to drivers and guides has been invaluable to a beginner such as me. I very much appreciate you helping me.
I have a couple of further queries please?
As mentioned earlier, there are four curtains in my family room. 3 of them connected as expected with a roller switch. One of them however connects as a switch only, which can be switched on or off. Any ideas as to why this would be happening? And how I could correct it? I’ve added a screenshot image below
This is the new driver date version.
You need wait 12 hr maximum for driver updated automatically in your Hub.
When you see this version date 2022-08-21T20:05:52.13402359 in the two others devices driver menu, then you will can uninstall de device with zwave exclusion and now will could re-pair with the edge driver
│ Driver Id │ 79679b70-6c89-4efa-a711-e5f6fa6f657e │
│ Version │ 2022-08-21T20:05:52.13402359 │
Several users have already offered it to me and I am very grateful for it, but I had not thought about accepting donations or gifts, unless my family wants to kick me out of the house for spending too much time on smartthings instead of them