With the familiar Fibaro single and double switches, associations can be defined in the Things section. There are selection menus for this. The desired nodes can be selected simply by clicking on them.
This no longer seems to be the case with the Fibaro Smart Module FGS-214 v5.0. My question: Has anyone already defined an association with this Smart Module? How and where is this done?
Thanks in advance for your ideas.
Eventually it’s so new that it’s not in the zwave device database that the zwave binding uses yet. I’m not up to date on that part so search the forum for more information how to get it in there.
The only version in the ZW DB is this (and it has two association groups). What are the deviceID and DeviceType in the Thing properties dropdown? Also are you using the traditional OH ZW binding or the new (with 5.0) zwave-js?
As usual, I was looking for a Z-Wave switch on Amazon. The Fibaro FGS-214 was a bit cheaper than the Fibaro Double Switches, and like the Fibaro Switches, it can also control 230-volt devices. So I bought the FGS-214. Like all Fibaro devices, it was immediately recognized and integrated by openHAB. It works perfectly. Unfortunately, you can’t control associations. This isn’t available in the Things menu. The section where you can select which adjacent node should be controlled is missing. This is possible with the other Fibaro Switches.
A brief description of the specific application:
I’ve made a motion detector at the garden gate smart using the Fibaro FGS-214. The motion detector controls a light and the FGS-214. When someone appears at the garden gate, the light turns on, and via an openHAB rule, another light at the front door, which is controlled by a Fibaro Single Switch, also turns on. This works well, but is significantly slower than associations. Associations work noticeably faster.
I’m using Z-Wave binding version 5.0.0.
The Fibaro FGS-214’s device ID is 46. During inclusion, it was assigned device ID 228. However, I’ve assigned ID 46. Only the Z-Wave network overview still displays ID 228.
The configuration menu I see is exactly the same as in your link – two association groups without a selection menu for nodes to be associated.
So there is no little > at the end that pops ups with a node list? Could try another browser or worse case use the REST api to modify the configuration (pattern after node with an association)
Good idea to try a different browser. I tried it right away. Unfortunately, the result was the same: no selection menu for the nodes.
Tested on PCs with Linux Mint and Firefox, and a brand new HP notebook from Black Friday with Windows 11 and Bing.
The other thing that strikes me is your comment about changing the node ID. I didn’t think you could do that. Isn’t the Thing UID still zwave:device:xxxxxxxxxx:node228? I don’t have the device so can’t test. You could try the API option
I wanted to post a screenshot, but couldn’t find a way to do so. Therefore, here it is in text form:
Thing UID: zwave:device:Razberry2:node046
Label: Z-Wave Node 046: FGS214 Single Switch 1x1.5KW Gate
In the Thing configuration, everything looks familiar. Just like with the Fibaro switches.
Perhaps mstormi is right and the Smart Module is simply too new. If that’s the case, I’ll wait for better times. The second light also switches on reliably via a rule. – But using an association would be significantly faster.
Don’t know if you tried the API, but here is an example of the “GET”. Make the change and use the “PUT”
I’ve never used the API Explorer before. However, based on your example, I displayed the thingUID of the Fibaro FGS-214 (zwave:device:Razberry2:node046). Everything looks fine to me.
Then, as a test, I also checked the ID 228, which was previously assigned during the openHAB include. – Response: Error: response status is 404.
The idea was to use the API to add (PUT) a node to group 2 following an example from another device.
Also the FGS-214 has been in the ZW DB since 2021-01-16. I don’t know why the UI is not working for you.
I understand your approach. However, since I’ve never worked with the API Explorer, I’d rather steer clear of it. With openHAB, I see myself more as a user than a developer. Therefore, I can’t possibly assess any side effects. I’d rather wait until other buyers of the Fibaro Smart Module also stumble across the missing associations in openHAB. I suspect that the professional developers at openHAB will then address the problem. Until then, I’ll live with controlling my front door light via a slow rule instead of the fast association. – Thank you for your answers, though. It’s always a pleasure to see how friendly and helpful everyone is here!
Understood. FWIW- I don’t think it is a ZW issue. There have been a number of UI issues related to a software package issue that are being worked. It will probably just fix itself when you upgrade. One other thing to try from the thing ui page is to Reinitialize Device.
