I am migrating from domoticz to openHAB2 with my zwave devices.
It works great so far. But one thing I cannot figure out…
I would like to make an association from a aeotec multisensor 6 (node 11) to a fibaro double relay switch (node 10).
In habmin2 I can set the association to “Node 10” under Configuration->Things->my_motion_sensor->Association Groups. This seems to work.
When I look at the association config in the paper UI I see a association to “node_10_0”.
But I need an association to “node_10_1”, which is the endpoint for the first (of two) relay switches of the fibaro double relay switch.
How can I set this association?
In habmin2 I can only choose “Node 10” (which results in node_10_0).
In the paper UI I can choose “node_10_1”, but I can’t save it. The save pencil icon is inactive.
root@raspberrypi:~# dpkg -l | grep openhab2
ii openhab2 2.1.0~20170501000831-1 all openhab2
ii openhab2-addons 2.1.0~20170501000831-1 all openhab2-addons
ii openhab2-addons-legacy 2.1.0~20170501000831-1 all openhab2-addons-legacy
I don’t know exactly is it similar problem, but I notice same behaviour with Fibaro Door sensor FGK 101.
In habMIN at zwave map I see this sensor as not connected. When I check the properties in associating groups, I see the openhab controller at first group.
But in PaperUI when I want to check it associating group is empty. When I choose the openhab controller, I cannot save. Parameter 70 - Scene activation functionality - is underline at red, and suggestion is to change form 0.
But in Fibaro manuals there is 0 assign as no scene activation.
In logs I can see some WARN lines regarding this node:
[class.ZWaveMultiInstanceCommandClass] - NODE 11: Originating Command Class ALARM (0x71) was on the root node.<
Is it something known? What should I do to include fully this sensor.
I use last snapshot for openhab and addons.
Openhab works at latest development (Snapshot release) version.
I add via habMIN all devices, but only one in PaperUI shows that one parameter (Fibaro door sensor no. 70) is wrongly set up.
The only open point which interesting me a bit is why this one sensor gives warn log “on the root node”. I thought that this is due to fact that it seems like this sensor, when looking for zwave map, is not connected.
I have few of Fibaro device and this one is only one which report strangely
[WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Originating Command Class SENSOR_MULTILEVEL (0x31) was on the root node.
Today i switched to the unstable version and i am now on openHAB 2.3.0 Build #1219.
I can´t see more nodes as before. Nothing really changed for me. One thing i recognized is, that
i now can set the association directly through the Paper UI and saving will work.
But no new endpoints in Paper UI or HABmin. Any ideas?