First, let me describe the situation: this module is located outside, about 15m away from my Homey Pro 2026. A similar module was installed for years, but unfortunately, it was damaged by moisture.
I have gone through the pairing procedure several times, even with the Homey just 10cm away.
The problem immediately starts with the Fibaro app. There are 4 possible junction boxes available. First, I chose the Double Smart Module.
Going through the procedure 2 steps goes well. After a while, a message appears about something like “safety negotiating S2,” followed by a message that a connection cannot be established.
When I then look at the node list in the Homey Developer tool, an unknown node has been added. If I test this, a message appears stating that a connection has been established with the node. After an update of the route, it reports that the node is unreachable.
I went through the same procedure with the 3 other junction boxes in the Fibaro app, with roughly the same results each time. Sometimes I have to enter the code listed on the module. In the community, it is suggested to try the code 00000. Unfortunately, that didn’t work either.
However, sometimes it is reported that there are problems with associations.
In the Developer section, I removed the unknown node each time.
I hope someone can help me get that module paired after all.
In any case, in practice, it doesn’t matter which module you select. The correct device driver is automatically selected based on the manufacturer and device IDs stored in the module.
However, the instructions on how to put the device into pairing mode may be incorrect.
After all those attempts and deleting unknown nodes, have you ever restarted your Homey?
I have the same problem, can’t add any FGS-224’s anymore (I have dozens working perfectly).
I think its related to the recent update of Z-Wave (I have Homey 2023, with 13.2.0, where a major update for Z-Wave is mentioned). I added one last week without any problems.
I tried several FGS-224 devices, Secure S2/ unsecure S0 (‘00000’), via mobile app and web app, all same result with different error messages:
Can’t connect, try again later
Device needs a secure connection, but is connected without security (never a problem before)
Something went wrong, association-group 4 not found
Also restarted Homey several times. After unsuccessful pairing, Z-wave also works very poorly for a while.
I have submitted a support ticket to Homey (since Fibaro has an ‘official’ status)
Jag har provat det mesta i dag när jag fick hem min fgs-224 för att få in den i Homey pro. Det går inte att få in den i Homey varken med z-wave eller Fibaros app. Jag har provat med pin-koden som finns och även med 00000. Tagit bort noden flera gånger. startat om Homey flera gånger, provat att lägga in den som z-wave. Homey verkar inte godkänna den i installationsfasen så det är troligen någon säkerhetsfunktion som inte är rätt
Thanks for the homey update. This issue was very annoying, I had to call my electrician, I thought it was a wider issue, I expect stable release to be stable without this kind of major issues.
Try to connect my new FGS-224 module unsecured using PIN 00000 … but without succes.
Similar error as described above: “Unable to connect. Device requires secure pairing but was paired without security. For older devices try enabling S0 in the advanced options. Or click ‘Remove device’ to remove the device from Homey.”
Tried to connect with S0 security (by flagging the S0 option in the advanced options) but also that doesn’t work.
FYI: Using Fibaro app vs 3.8.7 and latest Homey vs 13.3.0-RC16 and restarted.
Have several FGS-224 already connected unsecured and they still working fine
Anyone recently connected unsecured the FGS-224 ?
Does it requires a different process to include a device unsecured (other than using PIN 00000) ?
I can no longer add FGS-224s as unsecure either. I reported this to Athom and this was their response:
It is still possible to add Z-Wave devices unsecured by using 00000, but for this device and only this device, since 2021 there is a setting called “requiresecure” We don’t know why this is en it has been added at that time deliberately apparently, but you are right that adding this device unsecured is not possible.
That being said, since the new Z-Wave updates, there should no longer be a need to add devices un secured.
Apparently, there is a specific setting for the FGS-224 that enforces secure. maybe this was bypassed (or not implemented) before the latest update, but that is no longer possible in the new Z-wave setup.
But according to the last comment, adding the device as unsecure yields no benefit (anymore). I asked for the reason behind this, but I have not received an answer yet.
Hi Flodur,
The answer from Homey support is hard to believe: I bought 3 x FGS-224 at the same time. They have all the same firmware version 5.0 and hardware version 4. I’ve connected 2 of them successfully unsecured about 2 months ago … now I wanted to connect the 3rd … but without succes.
The argument that there is no reason anymore to connect these devices unsecured is not correct. I need to separate the Input from the Output of the FGS-224 and use the proper ZWave Configuration Commands that are only allowed on unsecured devices. Unfortunately this doesn’t work anymore. I’ve of course tried to send these these Configuration commands on the secured connected FGS-224 … but it doesn’t work (as expected).
I have the same experience; I have dozens of FGS 224s unsecured in Homey via the code 00000 method. But this isn’t possible since the last update. I even removed an existing unsecure module that was working fine, but I couldn’t register that one either (only S2 secure)
Fibaro also explicitly offers the option to register them unsecure; they even have a separate confirmation color for it (green, instead of purple).
So it doesn’t seem like we should just accept this. I have sent a reminder to Athom for a response to my ticket.
I would advise reporting this to Athom as well via Support | Homey (it is an official app); the more people do it, the more seriously they have to take it.
I have to complete/detail a bit more the installation method I’ve used in the past to connect the FGS-224 in unsecured mode: I used the normal method to add a Fibaro device, but it failed when selecting the the device type “Double Smart Module” when trying to connect it unsecured ( same as now). However, when I selected the device type “Double Relay Switch”, it connected smoothly unsecured! Even more: when looking to the device details in the “Homey Developper - Devices” it showed for the the FGS-224 the correct driver. So it has all the correct functionalities. It is now almost 2 years that I have informed Support of this bug … but never received a decent answer.
So, made a ticket for support and followed their standard questions/answers … but all without any result (= accepting that there is an issue) up to now.
Today, I’ve tried the following with succes:
I’ve used the ‘Z-Wave PC Controller’ software from Simplicity Studios (Developer/Producer of Z-Wave) on my PC.
The Z-Wave PC Controller acts as a secondary controller.
I’ve included the FGS-224 device using the Z-Wave PC Controller in my Z-Wave network.
Homey detected this inclusion and asked the PIN code.
I entered 00000 to include it unsecured.
Homey added the FGS-224 as standard Z-Wave devices … but these were un-usable as they didn’t offered all the functionalites of the FGS-224.
So, I’ve removed these devices from the Z-Wave network via Homey-Devices-Delete.
I started again the standard installation process in Homey: Add a Device-Fibaro-Double Smart module. As of that moment, the FGS-224 installation process finished successful and the FGS-224 was included unsecured with all functions and with the possibility to send RAW Configuration Commands !
There must have been somewhere a setting in the FGS-224 that prevents the inclusion unsecured.
By adding it unsecured via the Z-Wave PC controller, this setting has been reset and now the device can be included again by Homey ‘unsecured’ via the normal standard Homey installation process.
I’ve reported my findings to Support … now waiting again and see what they will respond.
I don’t understand everything you’re writing, but maybe it’s possible that adding unsecure is possible again since the Fibaro app update earlier today (version 3.8.9. was installed on my system 8 hours ago.)
I had also received a response from support a couple of days ago and received an invitation to install the app test version. I was indeed able to add the FGS-224 unsecure (code 00000), but it kept flashing yellow after Homey said it was succesful. After a few minutes everything worked fine unsecure (and still does). I think they fixed this last issue now (but haven’t tested it yet).
