I have read hopefully everything here in the forum but I still wasn´t able to get a status from the door contact. What I am trying to do is to not allow the shutters to close when the door is open. But I guess once I get a status of the door the rest is easy. I am trying right now to move the shutter a little but once the contact changed it status.
rule "Kontakt test"
when
Item Door_Wohnzimmer changed
then
sendCommand(Shutter_Wohnzimmer_1, 5)
end
Sitemap:
sitemap demo label=“Arendelle” {
Frame label=“Datum” {
Text item=TimeSunrise
Text item=TimeSunset
Text item=Uhrzeit
}
Frame label=“Wohnzimmer” {
Switch item=Shutter_Kueche_1
Switch item=Shutter_Kueche_2
Switch item=Shutter_Wohnzimmer_1
Contact item=Door_Wohnzimmer
}
}
I found out that the door contact has the firmware version 3.2. In the HABMIN it shows as great and connected. I´ve updated the newest release of openhab on my Rasberry 3.
I hope and guess I am missing a stupid thing but since days I cannot find a solution. Hope somebody can give me a hint.
I have the exact same setup and it is working fine. What does your event.log tell you? You should see something like:
2017-06-04 18:07:57.262 [ItemAddedEvent ] - Item 'FibDWS1_C_IN1' has been added.
2017-06-04 18:10:24.429 [ItemChannelLinkAddedEvent ] - Link 'FibDWS1_C_IN1-zwave:device:158b44ebf65:node27:sensor_door' has been added.
2017-06-04 18:11:14.465 [ItemStateChangedEvent ] - FibDWS1_C_IN1 changed from NULL to CLOSED
after a restart of openHAB.
This is one of my first zwave sensors and it has been working with all stable and snapshot zwave binding releases.
Because that device shows all green the only thing I can imagine is that you did not correctly configure your channels. Double check if everything is correct:
It looks as if you are using the (meanwhile) old release version from January. My FGK-101 did not work with this old version but only with the more recent snapshot versions. So maybe you consider to switch to the Snapshot, for me it helped.
thank you for your constant help!
It seems that finally the solution was really the update to the recent snapshot version.
The first tests worked immediately. Thanks again!