Ok, will attach a classic switch to try.
It is set to bistable. Momentary does not even light up the O1 attached lamp…
I “think” my sensor is providing a signal like a classic switch. Not impulse.
if you keep a momentary switch pressed, you’ll get the same effect, just for testing purposes ofc, not a convenient daily use XD
and yes those sensors are bistable in nature
if lifeline is set up correctly when S1 receives voltage(the circuit before it is closed/opened either by a relay or a switch) it should turn on/off almost immediately - not only physically but also in OpenHab. If the output on Q1 is turned ON immediately when S1 changes state, then it’s a transmission/range/lifeline issue.
If you ask me, this is the issue. But what is the right config? If I leave Switch 1 and 2 blank and then set Controller update to “controller”, this does not work as supposed…is this setup so that the FGS211 needs to be in range to controller and that might be the issue ?
s1 and s2 association blank
controller updates to controller(lifeline)
then create an item linked to the switch channel,
then test the timing of actuation if you command it from paper ui
then test the timing of representation in paper ui if s1 changes state.
If you have the option to move the controller near the fgs211 (with a power strip or smth) you can also see if it is a range issue.
Same if you can ,move the fgs 211 closer to the controller (don’t electrocute yourself in the process or leave exposed cables hanging or touching each other- rather isolate them)
Ok, so range might be the problem. You say that if set to “Controller” in controller updates. It does need to be in range for the controller ?
There is then no “mesh-magic” happening ? And there is no possibility to make it mesh ?
It is possible to heal single devices (habmin>setup>things>top right corner show advanced>top right corner again heal device -they say that it can slow the network down tho, i have never experienced it but it’s not advised) .
You can also let the network heal itself day by day.
By doing so the list of z-wave neigbours for weach node is refreshed.
Check in habmin>tools>view z-wave network to see your current topology.
If a node is out of range should be quite apparent.
Also, so far you didn’t mention having other z-wave devices nearby, so it looked as though you had only controller +1x fgs211
Sorry, I have 20 other z-wave devices. All in range. Network is healed every night. Also tried manually for this specific node.
I dont think this node is out of range. Could it be 8-10 meters with 3 wooden walls in between.
if all the above are true, lifeline is set correctly and in habmin your z-wave network shows the specific node as in range, could really be a also a faulty device as mstormi pointed out earlier.
I suggest checking your z.wave network representation in habmin and doing the above mentioned tests before drawing conclusions thoug.
btw, i’ve had some walls unexpectedly screening the signal way closer than that.
I just need to ask this again and clarify.
The DEBUG section in my first post is immidiately posted in openhab.log using “tail -f /var/log…” when convering my dusk/dawn sensor by hand. The light connected to O1 is also lit up immidiately.
What does that DEBUG log say ? Is this node in contact with my z-wave controller/network/other ?
How can I use this piece of information to continue my search for the cause of this issue. I mean, it does communicate at the point of activation from my sensor.
Yeah, I tried it but it didnt output any “blocks”. Dont know why, maybe to little information.
Did some more research. This is what z-wave log viewer translates the signal given from my node 24 which is the number now after exclusion/inclusion (before it was node 3).
So this is what is sent when dusk sensor triggers S1
And this is my configuration for Node 24:
And here is my network map:
And yes, the distance between the malfunctioning Node24 and the controller is about 8 meters with some walls in between. Is there no mesh magic happening in lifeline association ? That is, does it have to have direct contact with controller ?
EDIT: Moved my controller around in house, no change in behaviour. Still, all (see below) FGS211 does not seem to report their status.
Playing around. Let’s say I have 4 FGS211 1x3kw Fibaro units. None of them seem to be reporting status back to controller.
They all seem to report in the way described above when toggling manually on physical switch. Even though they have their lifeline set to Controller.
Then everything works as it is supposed to, or am i missing something?
Your network map shows node 24 already communicating in mesh to both the controller and node 23 (at the least. by selecting it you could see ticker lines to the nodes that it commmunicates with. that is mirrored also in the habmin>config>items>node24>attributes>neighbours voice) so there should be no real communication issues, which is confirmed by your previous statement as well.
Before talking about other devices:
What isn’t happeneing that you are expecting to happen in regards to this device?
Is there a ruule not being triggered? if the switch item linked to the switch channel changes istantaneously with the physical change, everything should be working just fine… no?
Thankyou for your time!
The problem is that is not updating the state of its item (or any of the items linked to my FGS211 devices) :
Switch SW_GARAGE_SKYMNING_1 "Switch1 Skymning" <garage_detached> (Switches) { channel="zwave:device:XXXXXXX:node3:switch_binary1" }
It catches the state update first when polling, every half hour or so (dont know where that is set either for that sake).
It is not reporting it’s state back to openhab. Should be association/lifeline issue…this only applies to my FGS211 devices 4 or 5 in total. Every other device in my zwave network is reporting its status instantaneously.
Lifeline is set and re-set numerous times. HEAL is done on every single device multiple times, whole network heal is done. Controller is moved around the house and so on…
Atm i’m not in the condition to check any of my items definitions for any fibaro switch, but if i am not mistaken, fibaro switches have 3 switch channels- switch, switch1 and switch2.
Again, if i am not mistaken (going on some kind of memory of mine here) the “Switch” channel is the one that you want to have linked to your switch item, not Switch1.
For simplicity’s sake, I would suggest deleting the textual items that aren’t working, going into paperUI, and from within your things panel, connecting each of the switch channels to a new automatically created item(you can always remove them and it’s much quicker than writing an items file). then change physically the status of your device a few times and see if any of the above respond as intended.
I’m thinking your issue isn’t with Z-wave but with Items and link to channels.
Once you sort out one of them, you just need to rinse and repeat with the other fgs 211, 213 etc
With the possibility that I’m wrong. These devices FGS211 do only have 2 channels. Switch1 and Switch2. At least, there is nothing else to choose from in PaperUI for this “thing”. FGS221 do have 3 channels, Switch, Switch1 and Switch2. But this is FGS211. A 1x3kW relay.
And fact is, the state of “Switch 1” get’s updated to “On” when polled after a while when the S1 has been triggered.
So. Sort of back to square one, they are not being updated automatically.
a quick search on the forum returned this
I am not sure about whether the author of that thread solved his issue (maybe try contacting him).
It is possible that the fgs 211 might not be fully implemented as of yet, in which case i would suggest contacting Chris Jackson (the developer of the binding himself)
it is also possible that there are some steps that i dont’ know about.
I do not own an fgs211, but an nuber of 212, which have the 3 switch channels i described and work well with the Switch channel…
That thread is spot on my problem.
Will go ahead and check it out and maybe talk to them. Thankyou!